Configuring Wireless Cisco Networks and Wireless Controllers.
I only see that when the upgrade got corrupted on the LAP. You will need to convert it to IOS and then back to LWAPP. What you can try is to load the rcv image back on. If you console into the lap and hold the reset button for about 20 seconds, it should show you the file name the LAP is trying to find via tftp. You can look at this link:http://www.cisco.com/en/US/docs/wireles ... l#wp160918
Hi Michael,You will never be able to ping the AP-Manager IP Address. Can you please post the "dir" output?How many AP's can your WLC control and how many AP's are there now in?
HiWe have 2 WS-SVC-WISM-1-K9 modules. Each able to handle 300 AP's. At the moment only one of the modules are in real production. Each module contains two WLC's (WISM controllers) each capable of 150 APs. At the moment we have 32 AP on WISM-1A and 75 AP on WISM-1B. All WiSM controllers are managed from a WCS with 500 APs licensed at the moment.Output from dir:AP001d.e556.bf84#dirDirectory of flash:/ 3 -rwx 88598 Apr 22 2009 15:00:14 +00:00 event.log 4 drwx 128 Jan 1 1970 00:02:01 +00:00 c1130-rcvk9w8-mx 9 drwx 256 Apr 22 2009 12:15:03 +00:00 c1130-k9w8-mx.124-18a.JA1 7 -rwx 5144 Apr 22 2009 15:18:20 +00:00 private-multiple-fs 8 -rwx 232 Apr 22 2009 15:18:20 +00:00 env_vars15998976 bytes total (9431040 bytes free)In the last days I have tried deleting env_vars, private-multiple-fs and event.log. It seemed to remove the hostname previously configured on the AP, but didn't solve the problem...
Hi Michael, Thanks for the output. I propose for you to delete the LWAP image (delete /f /r flash:c1130-k9w8-mx.124-18a.JA1), reboot the AP, and during the search for a WLC controller, delete the LWAP configuration (clear lwapp private), reboot the AP again and when the AP's searching for the WLC, force it to the WLC of your choice "lwapp ap controller ip address <Management IP Address>".Hope this will work for you.
Hi,I have now tried to hardreset the AP, and load an autonomious (non LWAP image).I was able to load the image, and can now talk (via telnet and console) to the AP.What I notice is that the AP seem to not have any Dot11Radio interfaces. show interfaces does not mention any interfaces but BVI1 and FastEthernet0.When tryint to add the autonomious AP using the WCS, I get:Autonomous AP Failed to add device to WCS Reason: SNMP operation to Device failed: Too few VarBinds in response Could my problem be that I'm experiencing 2 APs (of 100+ deployed) that have somehow lost their dot11 radios ?Regards and thanks for the help so far-Michael