Hi - Our company deployed WiSM's at key points across the country and has the individual site LAP's associate to them using DHCP option 43. The site I am at has a 4402 WLC, so we are moving off this to be assimilated with the rest. The problem is that the LAP's will not associate to the WiSM. (I should note that a new LAP has no problem) The Clear Config button in the WLC GUI apparently does NOT reset the LAP to factory standards. Our answer was to make Mobility Peers between the WiSM and the WLC then move the AP's over - this works fine, but I need to remove the 4402 but the AP's lose their way home then. I got out a ladder and consoled into one device and tried to add the "lwapp ap controller ip address 137.xx.xx.xx" command, but it will not allow it as the config is locked.
The "lwapp ap controller ip address X.X.X.X> will only work if the AP is running the RCV (aka "lite") IOS.
If you still have the ladder and console in place, what you can do (not try since I know this will work) is to delete the LWAPP IOS. But before you do so, make sure that the RCV IOS is available.
After you've deleted the LWAPP IOS, you have but a short window to type the "lwapp ap controller ip address x.x.x.x" on the AP before the AP starts downloading the firmware (this will make it difficult to type the command in).
IntroductionHow to use the Wireless LAN Controller Configuration Analyzer (WLCCA)
Javier Contreras is a Senior Tech Lead for the Wireless Business Unit in Cisco, with over 2 decades of experi...
< PRE >
(#)For this reason being that : - application that doesn't use multicast, sends one copy of each packet ( data unit of traffic at layer 3 ) to each client (" who seeks the traffic ).- application that does use multicast, sends ...
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...