Joining WLC Issues

Question

Hi,
I'm having difficulty with a lwapp joining our WLC.  The error mesage is:
*Mar  1 00:00:44.284: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar  1 00:00:50.285: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response
*Mar  1 00:00:50.285: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.
*Mar  1 00:00:50.285: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN RESPONSE.
*Mar  1 00:00:50.285: %LWAPP-5-CHANGED: LWAPP changed state to DOWNXmodem file system is available.
Searched and found out that this would be related to the AP being not authorized.  So I went ahead and added it via the GUI the AP mac and the SSC key.
It shows up in the GUI and in the command line. 
However it still does not join.  I have applied the changes.  The AP keeps rebooting with the same error message.  I just don't know why it will not join the WLC.  Is there something else I'm missing?
I've enabled the following debugging:
debug mac addr <ap-mac-address>
    (in xx:xx:xx:xx:xx format)
    debug client <ap-mac-address>
    debug lwapp events enable    debug lwapp errors enable    debug pm pki enable
And the debug:
Hi,
I'm having difficulty with a lwapp joining our WLC.  The error mesage is:
*Mar  1 00:00:44.284: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar  1 00:00:50.285: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response
*Mar  1 00:00:50.285: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.
*Mar  1 00:00:50.285: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN RESPONSE.
*Mar  1 00:00:50.285: %LWAPP-5-CHANGED: LWAPP changed state to DOWNXmodem file system is available.
Searched  and found out that this would be related to the AP being not  authorized.  So I went ahead and added it via the GUI the AP mac and the  SSC key.
It shows up in the GUI and in the command line. 
However  it still does not join.  I have applied the changes.  The AP keeps  rebooting with the same error message.  I just don't know why it will  not join the WLC.  Is there something else I'm missing?
I've enabled the following debugging:
debug mac addr <ap-mac-address>
    (in xx:xx:xx:xx:xx format)
    debug client <ap-mac-address>
    debug lwapp events enable    debug lwapp errors enable    debug pm pki enable
And the debug:
Hi,
I'm having difficulty with a lwapp joining our WLC.  The error mesage is:
*Mar  1 00:00:44.284: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar  1 00:00:50.285: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response
*Mar  1 00:00:50.285: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.
*Mar  1 00:00:50.285: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN RESPONSE.
*Mar  1 00:00:50.285: %LWAPP-5-CHANGED: LWAPP changed state to DOWNXmodem file system is available.
Searched  and found out that this would be related to the AP being not  authorized.  So I went ahead and added it via the GUI the AP mac and the  SSC key.
It shows up in the GUI and in the command line. 
However  it still does not join.  I have applied the changes.  The AP keeps  rebooting with the same error message.  I just don't know why it will  not join the WLC.  Is there something else I'm missing?
I've enabled the following debugging:
debug mac addr <ap-mac-address>
    (in xx:xx:xx:xx:xx format)
    debug client <ap-mac-address>
    debug lwapp events enable    debug lwapp errors enable    debug pm pki enable
And the debug:
*Feb 10 16:50:15.890: 00:12:7f:25:58:16 DHCP received op BOOTREQUEST (1) (len 584, port 29, encap 0xec00)
*Feb 10 16:50:15.890: 00:12:7f:25:58:16 DHCP received a REQUEST on 'management' interface from AP -- bouncing to local DHCP server.
*Feb 10 16:50:15.890: 00:12:7f:25:58:16 DHCP sending to local dhcp server (0.0.0.0:68 -> 10.0.200.7:1067, len 301)
*Feb 10 16:50:15.890: 00:12:7f:25:58:16 DHCP received op BOOTREPLY (2) (len 308, port 29, encap 0xec00)
*Feb 10 16:50:15.890: 00:12:7f:25:58:16 DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->srcPort 67, op: 'BOOTREPLY')
*Feb 10 16:50:15.891: 00:12:7f:25:58:16 DHCP received op BOOTREQUEST (1) (len 584, port 29, encap 0xec00)
*Feb 10 16:50:15.891: 00:12:7f:25:58:16 DHCP received a REQUEST on 'management' interface from AP -- bouncing to local DHCP server.
*Feb 10 16:50:15.891: 00:12:7f:25:58:16 DHCP sending to local dhcp server (0.0.0.0:68 -> 10.0.200.7:1067, len 319)
*Feb 10 16:50:15.892: 00:12:7f:25:58:16 DHCP received op BOOTREPLY (2) (len 308, port 29, encap 0xec00)
*Feb 10 16:50:15.892: 00:12:7f:25:58:16 DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->srcPort 67, op: 'BOOTREPLY')
*Feb 10 16:50:15.892: 00:12:7f:25:58:16 DHCP received op BOOTREPLY (2) (len 548, port 0, encap 0x0)
*Feb 10 16:50:15.893: 00:12:7f:25:58:16 DHCP received a REPLY from the local server -- forwarding to 'management' interface
*Feb 10 16:50:15.893: 00:12:7f:25:58:16 DHCP received op BOOTREPLY (2) (len 548, port 0, encap 0x0)
*Feb 10 16:50:15.893: 00:12:7f:25:58:16 DHCP received a REPLY from the local server -- forwarding to 'management' interface
*Feb 10 16:50:17.895: 00:12:7f:25:58:16 DHCP received op BOOTREPLY (2) (len 308, port 29, encap 0xec00)
*Feb 10 16:50:17.895: 00:12:7f:25:58:16 DHCP dropping packet (no mscb) found - (giaddr 10.0.200.1, pktInfo->srcPort 67, op: 'BOOTREPLY')
*Feb 10 16:50:21.571: 00:12:7f:25:58:16 Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '29'
*Feb 10 16:50:21.571: 00:12:7f:25:58:16 Join Priority Processing status = 0, Incoming Ap's Priority 0, MaxLrads = 50,joined Aps =32
*Feb 10 16:50:21.572: 00:12:7f:25:58:16 Successful transmission of LWAPP Discovery Response to AP 00:12:7f:25:58:16 on port 29
*Feb 10 16:51:24.636: sshpmLscTask: LSC Task received a message 4
The first part is the dhcp and it gets an IP address.  After that it doesn't give me any errors.  However on the AP it just gives the same error message:
*Mar  1 00:00:50.285: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.
Please help.
Thank you.

Answer 1

What is the hardware platform of this WLC and what version of code?  Is this a 2100 or 4400 series?
-Cisco 4400
Also, what discovery method are you using for this AP to find the WLC  management interface?  Option 43, DNS, IP-Helper/IP Port Forwarding? 
-The AP is on the same subnet as WLC
Is the AP L2 adjacent to the management or on another VLAN?  What VLAN is AP in and what VLAN is management/ap-manager in?
-Same VLAN
Here is the output
(Cisco Controller) >show ap join stats detailed 00:12:7f:25:58:16
Discovery phase statistics
- Discovery requests received.............................. 4
- Successful discovery responses sent...................... 4
- Unsuccessful discovery request processing................ 0
- Reason for last unsuccessful discovery attempt........... Not applicable
- Time at last successful discovery attempt................ Feb 10 17:16:23.844
- Time at last unsuccessful discovery attempt.............. Not applicable
Join phase statistics
- Join requests received................................... 0
- Successful join responses sent........................... 0
- Unsuccessful join request processing..................... 0
- Reason for last unsuccessful join attempt................ Not applicable
- Time at last successful join attempt..................... Not applicable
- Time at last unsuccessful join attempt................... Not applicable
Configuration phase statistics
- Configuration requests received.......................... 0
- Successful configuration responses sent.................. 0
- Unsuccessful configuration request processing............ 0
- Reason for last unsuccessful configuration attempt....... Not applicable
--More-- or (q)uit
- Time at last successful configuration attempt............ Not applicable
- Time at last unsuccessful configuration attempt.......... Not applicable
Last AP message decryption failure details
- Reason for last message decryption failure............... Not applicable
Last AP disconnect details
- Reason for last AP connection failure.................... Not applicable
Last join error summary
- Type of error that occurred last......................... None
- Reason for error that occurred last...................... Not applicable
- Time at which the last join error occurred............... Not applicable
                                                                           Ethernet Mac : 00:00:00:00:00:00  Ip Address : 10.0.200.120
It's weird there's no join errors ....
Thank you.