We installed this AP at a client about 4 months ago. It ran fine for about 3 months and now it kicks everyone off the network. I tried to troubleshoot it in its current installed state but couldn't get into the unit. Nothing had changed with the defaults (IP address was still at 192.168.1.245). The only way I could communicate with it was by plugging the Cat5 directly into my laptop and giving my NIC a static IP.
I updated firmware and was still getting no connection. I finally changed the IP address to .210 and was able to get into it without it being plugged directly into my PC. Now the client states the issue is back and the only way to get it working again is to power cycle the unit. However, I can't justify a client having to power cycle the unit 3 times a day.
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...