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

Lightweight AP won't associate to WLC module

I'm a first-timer LAP/WLC guy. My LAP is on a remote switch from the ISR with the WLC-NM. I have my DHCP pool set up on the ISR with option 43 pointing to the WLC management IP address. The AP recieves an address and can ping the WLC management interface and the WLC can ping the AP. However, the AP does not associate. I also have Layer three chosen for LWAPP. I must be missing something simple. Your assistance is appreciated!

Mike.

5 REPLIES
New Member

Re: Lightweight AP won't associate to WLC module

O.K., I've gotten to the point where my LAP indicates it has gone into a LWAPP join state but then reboots with a message:

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

remain.

The entire log is:

*Mar 1 00:00:19.154: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power s

ource

*Mar 1 00:00:25.302: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY

*Mar 1 00:00:35.440: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned D

HCP address 192.168.6.13, mask 255.255.255.0, hostname AP001a.a219.a376

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

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

ieve the Join response

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

remain.

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

ason: DID NOT GET JOIN RESPONSE.

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

I've created a dhcp pool on the WLCM for the subnet which my WLCM manager and AP-manager reside but the problem continues.

Can anyone provide a suggestion?

Thanks!

Mike.

New Member

Re: Lightweight AP won't associate to WLC module

My problem ended up being that I hadn't set the clock on the WLCM! I had it set for NTP, but my NTP server was set up yet. Debug LWAPP on the WLCM stated something about the certificate was invalid and to make sure the clock was set on the controller.

New Member

Re: Lightweight AP won't associate to WLC module

I have almost the exact problem, did you ever find a solution?

*Mar 1 00:00:45.647: LWAPP_CLIENT_ERROR_DEBUG: spamHandleDiscoveryTimer : Found

the discovery response from MASTER Mwar

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

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

ieve the Join response

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

remain.

*Mar 1 00:00:51.657: LWAPP_CLIENT_ERROR_DEBUG: spamHandleDiscoveryTimer : Found

the discovery response from MASTER Mwar

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

ieve the Join response

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

remain.

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

ason: DID NOT GET JOIN RESPONSE.

*Mar 1 00:00:56.690: %LWAPP-5-CHANGED: LWAPP changed state to DOWNXmodem file s

ystem is available.

New Member

Re: Lightweight AP won't associate to WLC module

I am having a simlar problem. Were you able to resolve your problem?

*Mar 1 00:00:45.647: LWAPP_CLIENT_ERROR_DEBUG: spamHandleDiscoveryTimer : Found

the discovery response from MASTER Mwar

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

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

ieve the Join response

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

remain.

*Mar 1 00:00:51.657: LWAPP_CLIENT_ERROR_DEBUG: spamHandleDiscoveryTimer : Found

the discovery response from MASTER Mwar

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

ieve the Join response

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

remain.

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

ason: DID NOT GET JOIN RESPONSE.

*Mar 1 00:00:56.690: %LWAPP-5-CHANGED: LWAPP changed state to DOWNXmodem file s

ystem is available.

Hall of Fame Super Red

Re: Lightweight AP won't associate to WLC module

Hi Jeremy,

This is a pretty common problem that is usually associated with one of 2 things;

1. The time setting on the WLC and the PC running the upgrade tool (must be in sync).

2. A problem with the SSC (Self Signed Certificate).

Have a look at these great threads from last year that provide answers to both problems. Perhaps you could also let us know what WLC Model and what version you are running.

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddb4d26

http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=Getting%20Started%20with%20Wireless&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddaba5b

Hope this helps!

Rob

869
Views
0
Helpful
5
Replies
CreatePlease to create content