Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

LWAPP AP unable to Join controller

I had 6 LWAPP AP's confgiured with primary and secondary controllers. I shut down primary controller - 5 AP's swapped over to secondary controller - 1 couldnt join. Turned primary back up and the 5 moved back and the 1 LWAPP AP still couldn't join. I consoled into the AP and got the following error messege.

Mar 1 00:00:37.167: %LWAPP-5-CHANGED: LWAPP changed state to JOIN

*Mar 1 00:00:37.168: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to a

dministratively down

*Mar 1 00:00:38.168: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio

0, changed state to down

*Mar 1 00:00:42.167: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not rec

ieve the Join response

*Mar 1 00:00:42.167: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses

remain.

*Mar 1 00:00:42.172: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Re

ason: DID NOT GET JOIN RESPONSE.

*Mar 1 00:00:42.172: %LWAPP-5-CHANGED: LWAPP changed state to DOWN

****

Does anyone what this error means ?

LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses

remain.

2 REPLIES
Community Member

Re: LWAPP AP unable to Join controller

It's interesting that only one AP couldn't join.

The error message basically tells you that the AP has gone thru its discovery/hunting process and did not find a controller to join.

This appears to be a connectivity issue with the port your AP is connecting to.

I would try using a port from one of the working AP's, if possible.

Also, make sure DHCP/OPtion43 and/or DNS CISCO-LWAPP-CONTROLLER@ entries are configured.

Community Member

Re: LWAPP AP unable to Join controller

it was working prior to the downing of the primary controller.

dns is configured correctly.

277
Views
0
Helpful
2
Replies
CreatePlease to create content