Cisco AIR-LAP1141N-A-K9 Getting Started Guide - Page 16

Troubleshooting the Access Point Join Process - ios

Page 16 highlights

Table 1 LED Status Indications (continued) Message Type Boot loader warnings Boot loader errors Cisco IOS errors Status LED Blinking blue Red Blinking green Red Blinking red and blue Blinking red and off Red Cycling through blue, green, red, and off Message Meaning Configuration recovery in progress (MODE button pushed for 2 to 3 seconds) Ethernet failure or image recovery (MODE button pushed for 20 to 30 seconds) Image recovery in progress (MODE button released) DRAM memory test failure FLASH file system failure Environment variable failure Bad MAC address Ethernet failure during image recovery Boot environment failure No Cisco image file Boot failure Software failure; try disconnecting and reconnecting unit power General warning; insufficient inline power 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 16

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34

16
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
Boot loader warnings
Blinking blue
Configuration recovery in progress (MODE
button pushed for 2 to 3 seconds)
Red
Ethernet failure or image recovery (MODE
button pushed for 20 to 30 seconds)
Blinking green
Image recovery in progress (MODE button
released)
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,
green, red, and off
General warning; insufficient inline power
Table 1
LED Status Indications (continued)
Message
Type
Status
LED
Message
Meaning