LWAPP Access Points

Guys,
I have an issue in our Lightweight Access Points, we have 1242AG, the strange thing happen is, when I connect to the console to configure the access point, the text are garbled, I tried another access point but I got the same result, I used different hyperterminal application, change my console cable but still the same.
Anybody who can share the same experience what I have.
I check the Cisco Tac site maybe someone has already raise this issue but I did not find any.
Thank you.

I've had a lot of oddities with AP console connections as well (works fine on routers, switches, etc.) but not on AP's.
Using Putty - http://www.chiark.greenend.org.uk/~sgtatham/putty/
is your best bet if you aren't already using it.

Similar Messages

LWAPP Access Point IOS Upgrade?

Using a 4400 Wireless Controller and WCS how do you upgrade the LWAPP IOS on Access Points to the latest version or is this even necessary? My LWAPP access points are fully functional 1131's and converted 1230's, but I would like to know what the procedure to update ios's are when a new one comes out. Do these automatically install when you update the controller software or do I need to download new IOS periodically and copy it to the controller or WCS, etc? What do you think?

Hi Jim,
When a Lightweight AP is connected to the WLC it has the same Version as the WLC. For example if the WLC is running 4.0.155.1 the AP is running 4.0.155.1. If you upgrade the WLC to a new version the AP's are upgraded at the same time. There is no need to do anything with the AP's themselves.
Hope this helps!
Rob

LWAPP Access points flapping

Hi,
I have 1252 and 1260 LWAPP access points in 20 sites connected to a 5500 controller over WAN through flexconnect.
Last two weeks, i noticed that the access points associated to the primary controller keeps flapping.(ie) it stay in primary controller for a minute or two and then it goes off again and again. Moved the APs to the secondary controller. Again i see the same issue. Noticed that there is no issue with the bandwidth.
This issue happened so far in two sites. The issue happens with all the access points at both of these sites. Replaced the access points. Still no luck. So converted the APs to autonomous mode as a temporary fix. Please let me know the suggestions.
Thanks,
Abinaya

Hi Scott,
Thanks for your reply...me and abinaya with in same team
yes we have a huge gap between the AP up time and Joining time
Let me tel you in how we are connected...
We have 1000's of WAN link(MPLS) connected to Data Center.
In Data Center we have this WLC 5508
20 Locations are added to this WLC(Flex Connect), each location has 4-5 AP's
Points we observed.
When we change this AP's to Autonomus mode,its working fine. Even in autonomus mode AP has to reach DC for AAA
If the WAN link has some problem, it should effect other devices which connect to DC.
We replaced AP's...but no luck.
This happened with different locations,different controllers.
We found the below logs in all the AP's which met this problem.
Dec 11 05:42:21.375: %DTLS-3-BAD_RECORD: Erroneous record received from X.x.x.x: Duplicate (replayed) record
*Dec 11 05:42:42.971: %LWAPP-3-CLIENTEVENTLOG: Switching to Standalone mode
*Dec 11 05:42:43.011: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to X.x.x.x:5246
*Dec 11 05:42:43.055: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Dec 11 05:42:53.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: x.x.x.x peer_port: 5246
*Dec 11 05:42:53.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Dec 11 05:42:53.863: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: x.x.x.x peer_port: 5246
*Dec 11 05:42:53.863: %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
*Dec 11 05:42:53.863: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Dec 11 05:42:54.055: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Dec 11 05:42:54.239: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Dec 11 05:42:54.247: %LWAPP-3-CLIENTEVENTLOG: OfficeExtend Localssid saved in AP flash
*Dec 11 05:42:54.395: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller Cont-Name
*Dec 11 05:42:54.439: %LWAPP-3-CLIENTEVENTLOG: Switching to Connected mode
Please suggest if you observe some thing.
Regards,
Satya.M

LWAPP access points are unregistering from the controller

Our wireless controller network designed with one 4402 controller and 30 LWAPP 1000 series access points.
all lwapp access points are suddenly unregistering from the controller and registering with controller after few minutes. It was happen randomly 2 to 4 times in a day.
I am adding the attachment of log file please help me anyone know identified this problem.
Thanking you,
Regards,
Ranga Kishore
9959344436

Hi,
What's the specific model of your 4402? How many access points do your controller support?
Can you also check if the uplink or distribution ports on your WLC goes up and down. Thanks.
Regards

Autonomous vs LWAPP access point

I am new to these 2 terms.
What's the main difference between autonomous and LWAPP access point?
Autonomous AP can work on it's own, while LWAPP need to be used with WNC?
If I need to deploy an wireless enironment, I should use LWAPP, right?

The main difference is autonomous do not require a controller to control the AP and it use WLSE for management software; the LWAPP require a WLC wireless controller to control all of the AP but provide ease of management for the communication / setting between APs, it use another management software call WCS.
If you will deploy many APs, LWAPP will be better for easier management. If only a few APs, autonomous is fine because do not require additional WLC.
LWAPP info. :
http://www.cisco.com/en/US/netsol/ns340/ns394/ns348/ns337/networking_solutions_white_paper0900aecd802c18ee.shtml
Hope this helps.

Switchport setup for lwapp access point running several ssid's

Hi all
when setting up an lwapp acces point, do I need to trunk all the vlans on the port to the ap? or do I only need to enable the management vlan to the acces point ? ie 1 vlan and normal access port ?
cheers
Carl

If its a LWAPP AP, then the switchport should be a ACCESS PORT.. this is just to get the IP address to the AP, then the AP wil try to join the WLC.. once the AP joins, the SSID and rest flow through the LWAPP tunnel..
Regards
Surendra

How can I verify CAPWAP/LWAPP access point?

Hello,
I wonder how can I check / what command shoul I use on non-autonomous access points to see wether they are support capwap or they support lwapp??
Thank you folks..

Hello,
I think Leo means how to distinguish by autonomous and lightwieght. not between LWAPP and CAPWAP.
Autohomous APs have in their image nam: K9W7 while lightweight APs have K9W8. That is correct. But I think this is not the answer.
In order to distinguish if an AP uses LWAPP or CAPWAP you have first to know that:
- Some old APs support only LWAPP. They do not support CAPWAP (1010 and 1030 for example).
- CAPWAP started with WLC version 5.2. If you have 5.2 or later then your AP supports CAPWAP. (old APs metnioed above are not supported on 5.x. they are supported on up to 4.x).
- Some APs support CAPWAP only. They work onlyh on WLCs with version 5.2 and above that supports capwap. (1140 for example does not work with 4.x, 5.0 or 5.1). While some other APs may work with either lwapp or capwap (1240 works with lwapp if it joing WLC running 5.0 while it works with capwap if it joins WLC that runs 7.x).
Now, in order to know if your AP supports capwap or lwapp:
- You need to know if your AP has any limitation (if it is capwap only, lwapp only or can run on both).
- if your AP can run on both lwapp and capwap you can do follow the follownig steps:
* show version from the AP to know the IOS version running on it.
* Go to this link (wireless compatibility matrix): http://tiny.cc/k08thw
* in the page, look for your IOS versoin that you knew from show version command.
* find what is WLC version that your AP version corresponds to.
* If the corresponding WLC version is 5.2 or later then you are running CAPWAP. If your WLC runs 5.1 or earlier then you are running lwapp.
HTH
Amjad

LWAPP Access point wont advertise SSID's

I have a 4402 WLC and LWAPP AIR-LAP1131AG-E-K9 connected to it.
I have been wrestling with the config for sometime now.
I have a laptop right next to it that wont see the SSIDs I have configured being broadcast.
I have no idea why but I do have the following errors in the log.
Apr 17 11:37:59.091 sim.c:913 SIM-3-GW_MISMATCH: MAC address of the GW 00:0f:f7:32:c1:80 recieved in the JOIN Request differs from the cached MAC addr 00:00:0c:07:ac:64 of the Gw. Deleting the Gw IP 10.45.50.97 for the AP Mgr & sending ARP req. for resolv
Apr 17 11:37:49.080 spam_lrad.c:1107 LWAPP-3-DISC_INTF_ERR2: Ignoring discovery request received on a wrong VLAN (70) on interface (1) in L3 LWAPP mode
I notice the first error related to the GW IP, but I am not sure where this is specified and why it is mismatched.
I also dont know what the second error means either about the wrong VLAN.
Please can anyone help!
Many thanks,
Neil

Ok I now understand why I am not seeing any SSID's
I am actually troubleshooting this remotely and have a laptop sat next to the AP. The laptop has a hard wired connection that when connected disables the Wireless adpater. Its a HP nc6400 laptop. I am not sure if it is a laptop setting or a GPO.
So the not seeing the SSID is fixed.
When I shutdown the switchport for the laptop. I did see the laptop pick up a DHCP address in the wireless scope I configured.
However this actually only worked once which was wierd.
I solved the gateway mismatch by actually putting the correct gateway address into ap-manager interface.
But I am still left with the message
Apr 17 11:37:49.080 spam_lrad.c:1107 LWAPP-3-DISC_INTF_ERR2: Ignoring discovery request received on a wrong VLAN (70) on interface (1) in L3 LWAPP mode
However this has been joined with another log entry;
Apr 17 21:05:38.734 1x_auth_pae.c:2510 DOT1X-3-MAX_EAP_RETRIES: Max EAP identity request retries (21) exceeded for client 00:1b:77:31:9d:72
The Mac address here is the Wireless Adapter of my test laptop.
The information of the WLC is
Product Identifier Description
AIR-WLC4402-25-K9
Version Identifier Description
V04
Possibly this is not what you are after but if you show me where to look that would be great.
It might be relevant but I have joined the AP to the switch with
switchport access vlan 70
switchport mode access
The config to the WLC is on a Gi port
switchport trunk encapsulation dot1q
switchport trunk allow vlan 2,11,70,80
switchport mode trunk
I am wondering if I should have
switchport trunk native vlan 70 in here?
The interface config on the controller is
(Cisco Controller) >show interface SUMM
Interface Name                   Port Vlan Id IP Address      Type    Ap Mgr Gu
est
ap-manager                       1    2        10.45.50.111    Static Yes    No
management                       1    2        10.45.50.110    Static No     No
service-port                     N/A N/A      10.44.48.214    Static No     No
virtual                          N/A N/A      1.1.1.1         Static No     No
york-vlan70                      1    70       10.44.51.1      Dynamic No     No
Many thanks,
Neil

LWAPP Access Point support of Cisco compatible Extension ?

Hi,
does the LWAPP AP support CCX ???
Which version 1,2 or 3 ?
Omar

Nice find Saurav.
You will not be able to add newly purchased Prime Infrastructure lifecycle or assurance licenses until you first apply a Prime Infrastructure 1.2 base license._ You can order the Prime Infrastructure 1.2 base license at no charge using regular ordering or the product upgrade tool if you have a valid service contract._ For regular ordering, order the top level part number R-PI12-K9 with base option R-PI12-BASE-K9._ When using the product upgrade tool order R-PI12-BASE-K9=.
Sent from Cisco Technical Support iPad App

Wireless Access Points Specs.

Hello guys,
i need to ask about the different between SAP vs LAP vs CAP ( Wireless Access Points )
thanks in advanced
i hope that you help me out :)

Hope this helps:
SAP=Standalone (Autonomous AP)
LAP=LWAPP Access Point
CAP=Capwap Access Point
Q. What is CAPWAP?
A. In controller software release 5.2 or later, Cisco lightweight access points use the IETF standard Control and Provisioning of Wireless Access Points protocol (CAPWAP) in order to communicate between the controller and other lightweight access points on the network. Controller software releases prior to 5.2 use the Lightweight Access Point Protocol (LWAPP) for these communications.
CAPWAP, which is based on LWAPP, is a standard, interoperable protocol that enables a controller to manage a collection of wireless access points. CAPWAP is being implemented in controller software release 5.2 for these reasons:
To provide an upgrade path from Cisco products that use LWAPP to next-generation Cisco products that use CAPWAP
To manage RFID readers and similar devices
To enable controllers to interoperate with third-party access points in the future
LWAPP-enabled access points can discover and join a CAPWAP controller, and conversion to a CAPWAP controller is seamless. For example, the controller discovery process and the firmware downloading process when you use CAPWAP are the same as when you use LWAPP. The one exception is for Layer 2 deployments, which are not supported by CAPWAP.
You can deploy CAPWAP controllers and LWAPP controllers on the same network. The CAPWAP-enabled software allows access points to join either a controller that runs CAPWAP or LWAPP. The only exception is the Cisco Aironet 1140 Series Access Point, which supports only CAPWAP and therefore joins only controllers that run CAPWAP. For example, an 1130 series access point can join a controller that runs either CAPWAP or LWAPP whereas an 1140 series access point can join only a controller that runs CAPWAP.
For more information, refer to the Access Point Communication Protocols section of the configuration guide.

IOS to LWAPP for 1130AG Access Points

We have initially installed IOS-based 1130 APs. If we would be upgrading it to LWAPP mode, could we pushed IOS-to-LWAPP upgrade thru the network? what procedures are required?

Hi Leopoldo,
This is possible and fully supported and can be done using the "LWAPP Upgrade Tool". Have a look at the following;
LWAPP Upgrade Tool Troubleshoot Tips
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a008072d9a1.shtml
Access points must run Cisco IOS Release 12.3(7)JA or later before you use the upgrade tool.
System Requirements
You can use the Autonomous to Lightweight Mode upgrade tool to install Cisco IOS Release 12.3(11)JX on these access points:
All 1100 series access points containing MP21G (802.11g) radios
***All 1130, 1230, and 1240 series access points
All modular 1200 series access points running Cisco IOS software and containing these supported radios:
802.11g: MP21G, MP31G
802.11a: AIR-RM21A-x-K9, AIR-RM22A-x-K9
All 1300 series access points in access point mode
http://www.cisco.com/en/US/docs/wireless/access_point/ios/release/notes/b311jx1.html
Cisco has released a free tool called the "Autonomous to Lightweight Mode Upgrade Tool" that allows selected Cisco Aironet autonomous access point models to be configured for lightweight mode operation.
The Autonomous to Lightweight Mode Upgrade Tool supports the following models:
Cisco Aironet 1240AG Series access points
Cisco Aironet 1230AG Series access points
Cisco Aironet 1200 Series access points that contain 802.11g (AIR-MP21G-x-K9) and/or second-generation 802.11a radios (AIR-RM21A-x-K9 or AIR-RM22A-x-K9)
Cisco Aironet 1130AG Series access points
**Cisco Aironet 1100 Series Access Points that contain 802.11g radios (AIR-AP1121G-x-K9)
Cisco Aironet 1300 Series Access Points/Bridges (AIR-BR1310G-x-K9 or AIR-BR1310G-x-K9-R). A Cisco Aironet 1300 Series operating in Lightweight Access Point Protocol (LWAPP) mode only operates as an access point. This series does not support LWAPP bridging mode.
The Autonomous to Lightweight Mode Upgrade Tool supports a process to migrate an autonomous access point from autonomous mode to lightweight mode. Unlike a VxWorks to Cisco IOS Software upgrade, this process is a Cisco IOS Software upgrade to the existing Cisco IOS Software image-not an operating system "swapout". In converted access points operating in lightweight mode, Cisco IOS Software continues to run on the access point, while LWAPP is used to communicate with a wireless LAN controller. Since LWAPP supports automatic access point configuration, there is no need to retain or convert the original autonomous Cisco IOS Software access point configuration.
http://www.cisco.com/en/US/netsol/ns340/ns394/ns348/ns337/networking_solutions_white_paper0900aecd804f1a23.shtml
Cisco Aironet Access Point Support for Lightweight Access Point Protocol
http://www.cisco.com/en/US/products/ps6521/prod_bulletin0900aecd80321a2c.html
Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode
http://www.cisco.com/en/US/products/hw/wireless/ps430/prod_technical_reference09186a00804fc3dc.html#wp157147
Hope this helps!
Rob

Unable to stop the event logs on access point console

Hi team,
I have an AIR-LAP1131AG-E-K9 access point having ios c1130-k9w8-mx.124-21a.JHB1.
When I am trying to take the console of it there are many logs generated like LWAPP ...Go join the controller, Discover controller etc. and the ap is unable to register to the controller(2112 with ios version 6.0.199.4). I'm trying to enter the command but there are many event msg generated....How do i stop this event log. I tried entering the command no debug all. but still there are many logs...
I want to enter the the following commands
#lwapp ap ip address <ip addr>.
#lwapp a pip default-gateway <gateway ip addr>
#lwapp ap controller ip addr <controller ip>
#wr me
Revert me back on urgent basis
Thanks in advance..

Thanks Rashika,
Now the access point got registered to the controller..This happened becuse of country Code..
I have changed the country code to UK, Belgium it started working fine.
Initially when it was IN the access point was not getting register..
But now the problem which arised is that the user is unable to get authenticated to the radius server.
Radius server is reachable and we have done every changes required for radius server authentication.
Users are getting rejected.
Customer is saying that the radius server is in IN domain and the WLC/access point is in UK,BE and hence the users are unable to connect..
Is it so??
Rply
Thanks in advance...

Steps to convert access point from LightWeight mode to Autonomous mode

I need steps to convert the following access point from Lightweight mode to Autonomous mode
AIR-AP1242AG-E-K9
Regards,
Majid

Hi Majid,
The method is just hidden a little further down the doc that Scott linked (+5 points Scott :)
Using a TFTP Server to Return to a Previous Release
Note This section does not apply to Cisco C3201WMIC and Cisco C3201LAP.
Follow these steps to revert from LWAPP mode to autonomous mode by loading a Cisco IOS release using a TFTP server:
Step 1 The static IP address of the PC on which your TFTP server software runs should be between 10.0.0.2 and 10.0.0.30.
Step 2 Make sure that the PC contains the access point image file (such as c1200-k9w7-tar.122-15.JA.tar for a 1200 series access point) in the TFTP server folder and that the TFTP server is activated.
Step 3 On the PC where the TFTP server is located, perform these steps:
a. Disable any software firewall products, such as Windows firewall, ZoneAlarm firewall, McAffee firewall, or others.
b. Ensure all Windows files are visible. From Windows Explorer, click Tools > Folder Options > View > Show hidden files and folders.
Step 4 Rename the access point image file in the TFTP server folder to c1200-k9w7-tar.default for a 1200 series access point, c1130-k9w7-tar.default for an 1130 series access point, c1240-k9w7-tar.default for a 1240 series access point, and c1250-k9w7-tar.default for a 1250 series access point.
Step 5 Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable.
Step 6 Disconnect power from the access point.
Step 7 Press and hold MODE while you reconnect power to the access point.
Step 8 Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds) and then release.
Step 9 Wait until the access point reboots, as indicated by all LEDs turning green followed by the Status LED blinking green.
Step 10 After the access point reboots, reconfigure it using the GUI or the CLI.
http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html#wp160918
Hope this helps!
Rob

Problem with Cisco 1240AG Access Points

I have a Cisco 1240AG Access point (P/N ? AIR-LAP1242AG-A-K9).
It has come in the lightweight mode.
I just want to know whether I can put it to the autonomous mode.

Hi Indika,
Here is a conversion method (look most of the way down the attached doc);
Reverting the Access Point Back to Autonomous Mode
http://www.cisco.com/en/US/products/hw/wireless/ps430/prod_technical_reference09186a00804fc3dc.html#wp161272
You can convert an access point from lightweight mode back to autonomous mode by loading a Cisco IOS Release that supports autonomous mode (Cisco IOS release 12.3(7)JA or earlier). If the access point is associated to a controller, you can use the controller to load the Cisco IOS release. If the access point is not associated to a controller, you can load the Cisco IOS release using TFTP.
Using a TFTP Server to Return to a Previous Release
Follow these steps to revert from LWAPP mode to autonomous mode by loading a Cisco IOS release using a TFTP server:
Step 1 The static IP address of the PC on which your TFTP server software runs should be between 10.0.0.2 and 10.0.0.30.
Step 2 Make sure that the PC contains the access point image file (such as c1200-k9w7-tar.122-15.JA.tar for a 1200 series access point) in the TFTP server folder and that the TFTP server is activated.
Step 3 Rename the access point image file in the TFTP server folder to c1200-k9w7-tar.default for a 1200 series access point, c1130-k9w7-tar.default for an 1130 series access point, and c1240-k9w7-tar.default for a 1240 series access point.
Step 4 Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable.
Step 5 Disconnect power from the access point.
Step 6 Press and hold MODE while you reconnect power to the access point.
Step 7 Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds) and then release.
Step 8 Wait until the access point reboots, as indicated by all LEDs turning green followed by the Status LED blinking green.
Step 9 After the access point reboots, reconfigure it using the GUI or the CLI.
From this doc;
http://www.cisco.com/en/US/products/hw/wireless/ps430/prod_technical_reference09186a00804fc3dc.html#wp161272
Hope this helps!
Rob

Image Recovery for Cisco Aironet 1300 Outdoor Access Point

We purchased two 1300 APs for outside. There is a new release for the image that we wanted to use so, we have the latest security updates. We downloaded, logged onto the access point just fine, but the image never took. After four hours with a direct connection, it was still going and this morning we came in and it just keep rebooting. Our network guy states it looks like a corrupt image. We can barely do anything and since there is no "mode" button like the earlier models, I have not found anything on web sites or forums to help us reload a good image to the access point. I would appreciate any insight someone has and/or where to look for this. I logged on and downloaded about every manual on the 1300 I could find, but have not found a good way to fix this. Not even the upgrade tool will connect since it just keeps rebooting.

Hi Bruce,
Because (as you correctly noted) the 1300 does not have a mode button you could try this method;
Complete the steps in this section in order to reset Cisco IOS Software-based bridges:
If the privileged command prompt ap# is available in the CLI, the write erase command and the reload command erase the startup configuration and reset the unit.
If the GUI is available, choose System Software > System Configuration. Press the Reset to Defaults button.
Aironet 1300 Series Bridges do not have a MODE button to reset the AP to factory defaults. So, if neither the GUI or CLI is available with sufficient privileges, complete these steps to delete the current configuration and return the entire bridge settings to the factory defaults using the CLI.
Open the CLI with a Telnet session or a connection to the bridge console port.
Reboot the bridge by removing and reapplying power.
Allow the bridge to boot until the command prompt appears and the bridge begins to inflate the image.
Press ESC when you see lines that are similar to these on the CLI:
Loading "flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_ja.20040314"
...#############################################################################Note: In order to access the boot loader, you must press ESC twice. But this action depends on the terminal-emulation software that you use.
Messages that are similar to these appear:
Error loading "flash:/c1310-k9kw-7mx.v122_15_ja.200040314-k9w7-mx.v122_15_
ja.20040314"
Interrupt within 5 seconds to abort boot process.
Boot process terminated.
The system is unable to boot automatically. The BOOT environment variable needs to
be set to a bootable image.
C1310 Boot Loader (C1310-BOOT-M), Version 12.2 [BLD-v122_15-ja_throttle.20040314 100]
bridge:At the bridge: prompt, issue the dir flash: command in order to view a directory of the Flash file system.
The directory is similar to this directory:
bridge: dir flash:
Directory of flash:/
2 -rwx 0 env_vars
5 drwx 384 C1310-k9w7-mx.v133_15_JA.20040314
3 -rwx 1128 config.txt
4 -rwx 5 private-config
3693568 bytes available (4047872 bytes used)
bridge:Delete or rename the files config.txt and env_vars, and reboot the bridge.
Note: Do not forget the / character before the filenames.
bridge: delete flash:config.txt
Are you sure you want to delete flash:/config.txt (y/n)?y
File "flash:/config.txt" deleted
bridge: delete flash:/env_vars
Are you sure you want to delete "flash:/env_vars" (y/n)?y
File "flash:/env_vars" deletedIssue the boot command in order to reboot the bridge at the bridge: prompt, or simply power cycle the bridge.
After the bridge reboots, reconfigure the bridge with the web browser interface, the Telnet interface, or Cisco IOS Software commands.
Note: The bridge is configured with the factory default values that include:
The IP address, which is set to receive an IP address with DHCP. If you do not have a DHCP server, you can access the bridge using the default IP address of 10.0.0.1 using HTTP/HTTPS or Telnet. Once you gain access to the bridge via Telnet or GUI, you can modify the IP address of the bridge.
Note: This default IP address of 10.0.0.1 becomes available only for a short period. So, make sure that you assign your own IP address to the bridge within that period of time.
The default username and password, "Cisco".
From this doc;
http://www.cisco.com/en/US/products/hw/wireless/ps430/products_password_recovery09186a00800949d0.shtml#ca_1310_ser
One other thing, be careful with the new IOS that you aren't loading a LWAPP Recovery Image. (it almost sounds like what may have happened)
Hope this helps!
Rob

LWAPP Access Points

Similar Messages

Maybe you are looking for