Cisco Systems 1260 specifications Troubleshooting the Access Point Join Process

Page 18

Table 1

LED Status Indications (continued)

 

 

 

 

 

Message

 

Status

Message

Type

 

LED

Meaning

 

 

 

Boot loader errors

Red

DRAM memory test failure

 

 

 

 

 

 

Blinking red and blue

FLASH file system failure

 

 

 

 

 

 

Blinking red and off

Environment variable failure

 

 

 

 

 

 

 

Bad MAC address

 

 

 

 

 

 

 

Ethernet failure during image recovery

 

 

 

 

 

 

 

Boot environment failure

 

 

 

 

 

 

 

No Cisco image file

 

 

 

 

 

 

 

Boot failure

 

 

 

Cisco IOS errors

Red

Software failure; try disconnecting and

 

 

 

reconnecting unit power

 

 

 

 

 

 

Cycling through blue,

General warning; insufficient inline power

 

 

green, red, and off

 

 

 

 

 

Troubleshooting the Access Point Join Process

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’s and controller’s 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 the following numbers of access points:

18

Image 18
Contents Cisco Aironet 1260 Series Lightweight Access Point Safety Instructions About this Guide20A. Statement Unpacking OverviewAccess Point Ports and Connections, Bottom Configuring the Access Point Controller Discovery ProcessPreparing the Access Point Installation Summary Performing a Pre-Installation ConfigurationPre-Installation Configuration Setup Controller Layer 3 devices Cisco Aironet access pointsPage Page Configuring Security Settings Page Mounting the Access Point Deploying the Access Point on the Wireless NetworkTroubleshooting Using Dhcp OptionChecking the Access Point LED Shows the location of the access point Status LEDLED Troubleshooting the Access Point Join Process Page Declarations of Conformity and Regulatory Information Vcci Statement for Japan 03-6434-6500 Statement 371-Power Cable and AC Adapter Industry CanadaModels Page Page Declaration of Conformity for RF Exposure United StatesChinese Translation English Translation Operation of Cisco Aironet Access Points in Brazil Declaration of Conformity Statements Portuguese TranslationCisco AP c1260 Access Point Specifications Category SpecificationAccess Point Specifications