18
Cisco Catalyst 9117AX Series Access Points
13
Miscellaneous Usage and Configuration Guidelines
Using the Mode Button
Using the Mode button (see
) you can:
Reset the AP to the default factory-shipped configuration.
Clear the AP internal storage, including all configuration files.
To use the mode button, press, and keep pressed, the mode button on the access point during the AP boot cycle. Wait
until the AP status LED changes to Amber. During this, the AP console shows a seconds counter, counting the number
of seconds the mode button is pressed. Then:
To reset the AP to the default factory-shipped configuration, keep the mode button pressed for less than 20
seconds. The AP configuration files are cleared.
This resets all configuration settings to factory defaults, including passwords, WEP keys, the IP address, and the
SSID.
To clear the AP internal storage, including all configuration files, keep the mode button pressed for more than 20
seconds, but less than 60 seconds.
The AP status LED changes from Amber 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 mode button is assumed faulty and no changes are
made.
Troubleshooting the Access Point to Cisco Controller Join Process
Note
Ensure that your controller is running the latest Cisco Wireless Controller Software Release as specified in
the access point data sheet.
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 don’t match, and so on.
Controller software enables you to configure the access points to send all CAPWAP-related errors to a syslog server.
You do not need to enable any debug commands on the controller because all of the CAPWAP error messages can be
viewed from the syslog server itself.
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 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.
You can view join-related information for up to three times the maximum number of access points supported by the
platform for the 2500 series controllers and the Controller Network Module within the Cisco 28/37/28xx Series
Integrated Services Routers.
