Getting Started Guide
Table Of Contents
- Cisco Catalyst 9120AX Series Access Points
- 1 About this Guide
- 2 About the Access Point
- 3 Safety Instructions
- 4 Unpacking
- 5 AP Views, Ports, and Connectors
- 6 Preparing the AP for Installation
- 7 Installation Overview
- 8 Performing a Pre-Installation Configuration
- 9 Mounting the Access Point
- 10 Grounding the Access Point
- 11 Powering the Access Point
- 12 Configuring and Deploying the Access Point
- 13 Self-Identifying Antennas
- 14 Checking the Access Point LEDs
- 15 Miscellaneous Usage and Configuration Guidelines
- 16 FAQs
- 17 Related Documentation
- 18 Declarations of Conformity and Regulatory Information
- Manufacturers Federal Communication Commission Declaration of Conformity Statement
- VCCI Statement for Japan
- Guidelines for Operating Cisco Catalyst Access Points in Japan
- Statement 371—Power Cable and AC Adapter
- Industry Canada
- Canadian Compliance Statement
- European Community, Switzerland, Norway, Iceland, and Liechtenstein
- Declaration of Conformity for RF Exposure
- Generic Discussion on RF Exposure
- This Device Meets International Guidelines for Exposure to Radio Waves
- This Device Meets FCC Guidelines for Exposure to Radio Waves
- This Device Meets the Industry Canada Guidelines for Exposure to Radio Waves
- Cet appareil est conforme aux directives internationales en matière d'exposition aux fréquences radioélectriques
- Additional Information on RF Exposure
- Administrative Rules for Cisco Catalyst Access Points in Taiwan
- Operation of Cisco Catalyst Access Points in Brazil
- Declaration of Conformity Statements
- Communications, Services, and Additional Information
- Cisco Bug Search Tool
22
Cisco Catalyst 9120AX Series Access Points
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 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 controller software Release 8.9.111.0 or later as specified in see the
Cisco Wireless Solutions Software Compatibility Matrix.
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.
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 syslog messages to IP address 255.255.255.255 by default when any of the following
conditions are met:
An access point running software release 8.2.110.0 or later has been newly deployed.
An existing access point running software release 8.2.110.0 or later has been reset after clearing the configuration.
If any of these conditions are met and the access point has not yet joined a controller, 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 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. After that, the access point sends all syslog messages to this IP address
until it is overridden by one of the following scenarios:
The access point is still connected to the same controller, and the global syslog server IP address configuration 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 IP address to the access point.
The access point is still connected to the same controller, and a specific syslog server IP address has been
configured for the access point on the controller using the config ap syslog host specific Cisco_AP
syslog_server_IP_address command. In this case, the controller sends the new specific syslog server IP address
to the access point.
The access point is disconnected from the controller and joins another controller. In this case, the new controller
sends its global syslog server IP address to the access point.