Cisco Cisco Aironet 1522 Lightweight Outdoor Mesh Access Point 문제 해결 가이드

Configuration change.

Reason given: Image upgraded.

1) An image upgrade was initiated from the 
controller or Cisco WCS and was sent to the 
AP.

After the AP image upgrades, the 
AP reboots.

Configuration change.

Reason given: Controller reboot command.

1) A controller reboot request was initiated 
from the controller.

Configuration changes. 

Reason given: Did not get config response.

When a configuration change 
occurs, an AP should signal back 
and acknowledge it has gotten the 
configuration change.

Problem is mostly likely caused by poor 
SNR between APs or packet lost in the 
airwaves.

1) Run a link test between the two APs 
from the controller or WCS.

2) In Cisco WCS, run the Mesh Packet 
Error Rate Report (Path: Reports > Mesh 
Reports > Mesh Packet Error Stats).

If SNR is good but there is a high 
PER, then check for 
interference.

3) Verify load in the network.

Link failure. 

Reason given: ECHO_REQUEST.

LWAPP connection did not 
receive the acknowledgment 
(ACK) and the APs are 
disassociating because they are 
unable to reach the controller.

1) Lack of connectivity between the 
controller and the access points could be 
tied to either problems with network 
elements (wireless backhaul, switches, or 
routers) or because of low SNR.

Refer to the beginning of this 
document, and begin step-by-step 
troubleshooting.

Link failure. 

Reason given: RRM_DATA_REQ.

1) Error message indicates LWAPP did not 
receive an ACK form the AP; and the APs 
are disassociating because the controller is 
unable to reach them. 

1) Check network connections (wireless 
backhaul, switches, routers).

2) Check link for low SNR.

Link failure. 

Reason given: STATISTICS_INFO.

Error message indicates that 
LWAPP could not pull statistical 
information from the AP. This 
could be due to low SNR or just 
packet lost in the airwaves from 
802.11 behavior.

1) Run a link test between the two APs 
from the controller or WCS.

2) In Cisco WCS, run the Mesh Packet 
Error Rate Report (Path: Reports > Mesh 
Reports > Mesh Packet Error Stats).

If good SNR but high PER, then 
check for interference.

3) Verify load in the network.