AP not getting associated while moving from one WLC to another WLC in mobility group.
This problem occurs if the AP moves between WLCs that are running different WLC software versions. Ensure that WLCs are running the same version to solve the problem.
Also it is recommended, that High Availability (HA) is configured on all the APs, in order to decrease the time that it takes to move to a another controller and for wireless service to resume after a controller associated with another WLC.
High Availability Enhancements in Wireless LAN Controller Software Release 5.0
In wireless network deployments that run controller versions earlier than 5.0, when a controller goes down, it takes a long time for all the APs and the associated clients to move to a backup controller and for wireless service to resume.
The features discussed in the document are implemented on the controller CLI in WLC software release 5.0 in order to decrease the time that it takes for access points and their associated clients to move to a backup controller and for wireless service to resume after a controller goes down:
In order to reduce the controller failure detection time, you can configure the heartbeat interval between the controller and access point with a smaller timeout value.
In addition to the option to configure primary, secondary, and tertiary controllers for a specific access point, you can now also configure primary and secondary backup controllers for a specific controller. If the local controller of the access point fails, it chooses an available controller from the backup controller list in this order:
The access point maintains a list of backup controllers and periodically sends primary discovery requests to each entry on the list. You can now configure a primary discovery request timer in order to specify the amount of time that a controller has to respond to the discovery request of the access point before the access point assumes that the controller cannot be joined and waits for a discovery response from the next controller in the list.
Mobility group will only let the joined APs learn the WLC IPs on that mobility domain, for WLC selection you need to have HA configured on all the APs, without that configured APs will try to join least loaded wlc/master/backup wlcs that learnt through different mechanism however test capwap controller ip should let join the specific wlc.
We recently expanded our AP count from around 150 to 320 due to a building expansion. After looking at some survey results, I saw a good deal of channel contention issues. Surprisingly, 115 of my APs are using channel 36 while no other channel...
Hi I would like to ask a question regarding command "capwap ap ip address 10.0.1.111 255.255.255.0". what is difference between the command above and command ip address 10.0.1.111 255.255.255.0 under interface G? Thanks
Hello. I'm having a similar problem to another thread, but it's fairly old, and I didn't want to resurrect a dead thread. (For reference, the discussion thread is at Cisco CAP3702i Web Gui Does Not Work) I have a CAP3702i that has been flas...
HI The AP3802i used to join the wlc, but now it cannot join. Both ap and wlc can ping each other. Below show logging. Anyone can help to take a look at it? Thank you AP11#show loggingSystem logging:Mar 1 19:02:25 kernel: [*03/01/2021 19:02...