Troubleshooting the Access Point Join Process
Access points can fail to join a controller for many reasons: a RADIUS authorization is pending;
Using the access point GUI, you can view join process failures in the AP Join Stats page. To view this page, select Monitor > Statistics > AP Join, and then click the MAC address of the AP.
Alternatively, you can use the following CLI command to get a list of all APs that attempted to join the controller:
show ap join stats summary all
To view details of a join process failure, use the following command:
show ap join stats detailed <ap base radio MAC address>
Controller software enables you to configure the access points to send all
The state of the access point is not maintained on the controller until it receives a CAPWAP join request from the access point. Therefore, it can be difficult to determine why the CAPWAP discovery request from a certain access point was rejected. In order to troubleshoot such joining problems without enabling CAPWAP debug commands on the controller, the controller collects information for all access points that send a discovery message to it and maintains information for any access points that have successfully joined it.
The controller collects all
You can view
Note The maximum number of access points varies for the Cisco WiSM2, depending on which controller software release is being used.
When the controller is maintaining
An access point sends all syslog messages to IP address 255.255.255.255 by default when any of the following conditions are met:
22