Troubleshooting; Troubleshooting The Access Point To Cisco Controller Join Process - Cisco Catalyst 9124AX Series Hardware Installation Manual

Troubleshooting

•
•
•
Troubleshooting the Access Point to Cisco Controller Join
Process
AP can fail to join a controller for many reasons: a RADIUS authorization is pending; self-signed certificates
are not enabled on the controller; the AP and the controller regulatory domains do not match, and so on.
Controller software enables you to configure the AP to send all CAPWAP-related errors to a syslog server.
You do not have to enable any debug commands on the controller. View all the of the CAPWAP error messages
from the syslog server itself.
The AP is not maintained on the controller until it receives a CAPWAP join request from the AP. Therefore,
it can be challenging to determine why the CAPWAP discovery request from a particular AP was rejected.
To troubleshoot such joining problems without enabling CAPWAP debug commands on the controller, the
controller collects information for all APs that send a discovery message and maintains information for any
AP that has successfully joined it.
The controller collects all join-related information for each AP that sends a CAPWAP discovery request to
the controller. The collection begins with the first discovery message received from the AP and ends with the
last configuration payload sent from the controller to the AP.
When the controller maintains join-related information for the maximum number of APs, it does not collect
information for any more APs.
An AP sends all syslog messages to IP address 255.255.255.255 by default.
You can also configure a DHCP server to return a syslog server IP address to the AP using option 7 on the
server. The AP then starts sending all Syslog messages to this IP address.
When the AP 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 AP. After that, the AP sends all Syslog messages to this IP address until it
is overridden by one of the following scenarios:
• The AP is still connected to the same controller, and the global syslog server IP address configuration
Troubleshooting the Access Point to Cisco Controller Join Process, on page 65
Important Information for Controller-based Deployments, on page 66
Configuring DHCP Option 43, on page 66
on the controller has been changed using the config ap syslog host global syslog_server_IP_address
command. In this case, the controller sends the new global syslog server's IP address to the AP.
Cisco Catalyst 9124AX Series Outdoor Access Point Hardware Installation Guide
6
C H A P T E R
65