Cisco Cisco Aironet 1522 Lightweight Outdoor Mesh Access Point Guía Para Resolver Problemas

After an access point has connected to the controller over LWAPP, a logical connection is created. This 
logical connection may shut down for a variety of reasons. A number of the more typical events reported 
and behaviors associated with LWAPP failures are noted in the table below. 

LWAPP connection failures are generally caused by something other than RF, but intermittent 
interference or poor link SNR can be the cause of these failures.

To find information for the following LWAPP failures, refer to either the Trap Logs or Msglogs on the 
controller:

In the controller GUI, refer to the Trap Log (Management > SNMP > Trap Logs) for messages of 
the following type: “AP Interface: 0 (802.11a) Operation State {Up | Down}.”

In the controller CLI, enter show msglogs. Refer to the associated LWAPP troubleshooting 
messages below for more guidance on debugging.

Access point resets.

1) Power or manual reset of the AP has 
occurred. 

2) AP has not been connected to a controller 
for 30 minutes or longer and the AP will 
reboot automatically.

Configuration changes.

Reason given: Did not get a join response.

In LWAPP there is a LWAPP join 
reply message for every join 
request. If the AP does not receive 
a join reply message, the LWAPP 
does not form and the above error 
message is reported. 

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.

Configuration changes.

Reason given: Found configured or master 
controller.

With a master controller set, if the 
AP does not have a primary or 
secondary controller name 
pre-configured, an AP will 
associate with the master 
controller.

1) Limit the number of associated APs on 
the master controller, to allow for initial 
association of such “strays.” 

2) AP might have switched from a 
secondary, tertiary (or other) controller to 
a master controller that was inactive when 
the AP first joined.