Troubleshooting The Access Point To Controller Join Process - Cisco Catalyst Wireless 9163E Manual

Troubleshooting the Access Point to Controller Join Process

Note
Troubleshooting the Access Point to Controller Join Process
Note
Access points can fail to join a controller for many reasons—a RADIUS authorization is pending, self-signed
certificates are not enabled on the controller, the access point and the controller regulatory domains do not
match, and so on.
Controller software enables you to configure the access points to send all CAPWAP-related errors to a syslog
server. All the CAPWAP error messages can be viewed from the syslog server itself.
When the ordered AP is a CW9163E-MR model, or the AP is in Meraki Management mode, it will not attempt
to join the Cisco 9800 Wireless Controller. Contact the Meraki support team to perform the migration procedure
on the AP.
The state of the access point is not maintained on the controller. It can be difficult to determine why the
discovery request from a certain access point was rejected. In order to troubleshoot such joining problems,
we recommend that you run traces commands on the Cisco Catalyst 9800 Wireless Controller.
The controller collects all the join-related information for each access point that sends a CAPWAP discovery
request to the controller. Collection begins with the first discovery message received from the access point
and ends with the last configuration payload sent from the controller to the access point.
When the controller is maintaining join-related information for the maximum number of access points, it does
not collect information for any more access points.
An access point sends all the syslog messages to the IP address 255.255.255.255 by default.
You can also configure a DHCP server to return a syslog server IP address to the access point using Option
7 on the server. The access point then starts sending all the syslog messages to this IP address.
When the access point joins a controller for the first time, the controller sends the global syslog server IP
address (the default is 255.255.255.255) to the access point.
The access point sends all the syslog messages to this IP address until it is overridden by the following
configuration:
• The access point is still connected to the same controller, and the global syslog server IP address
Cisco Catalyst Wireless 9163E Access Point Hardware Installation and Deployment Guide
54
• If the Mode button is pressed for more than 30 seconds, but less than 60 seconds, the FIPS mode flag is
also cleared during the full factory reset of the AP. If the FIPS flag is set, the console access is disabled.
• The AP status LED changes from blue to red, and all the files in the AP storage directory are cleared.
• If you keep the Mode button pressed for more than 60 seconds, the button is assumed as being faulty
and no changes are made.
As specified in the Cisco Wireless Solutions Software Compatibility
running Cisco IOS XE Dublin 17.13.1 or a later release to support the Cisco CW9163E AP.
configuration on the controller has been changed using the syslog host <ip address> command. In this
case, the controller sends the new global syslog server IP address to the access point.
Troubleshooting
Matrix, ensure that your controller is