LWAPP Discovery Ok, Not sending request to join

Dave Dougher · ‎02-26-2015

Trying to get an AP to join the WLC, but I'm getting stuck. The WLC debug can see the AP doing it's discovery request, the WLC sends a response, and then nothing.

Fri Feb 27 00:20:21 2015: 00:25:83:e8:46:80 Received LWAPP DISCOVERY REQUEST from AP 00:25:83:e8:46:80 to ff:ff:ff:ff:ff:ff on port '1'
Fri Feb 27 00:20:21 2015: 00:25:83:e8:46:80 Successful transmission of LWAPP Discovery Response to AP 00:25:83:e8:46:80 on port 1
Fri Feb 27 00:20:49 2015: 00:25:83:e8:46:80 Received LWAPP DISCOVERY REQUEST from AP 00:25:83:e8:46:80 to ff:ff:ff:ff:ff:ff on port '1'
Fri Feb 27 00:20:49 2015: 00:25:83:e8:46:80 Successful transmission of LWAPP Discovery Response to AP 00:25:83:e8:46:80 on port 1
Fri Feb 27 00:21:17 2015: 00:25:83:e8:46:80 Received LWAPP DISCOVERY REQUEST from AP 00:25:83:e8:46:80 to ff:ff:ff:ff:ff:ff on port '1'
Fri Feb 27 00:21:17 2015: 00:25:83:e8:46:80 Successful transmission of LWAPP Discovery Response to AP 00:25:83:e8:46:80 on port 1
Fri Feb 27 00:21:45 2015: 00:25:83:e8:46:80 Received LWAPP DISCOVERY REQUEST from AP 00:25:83:e8:46:80 to ff:ff:ff:ff:ff:ff on port '1'
Fri Feb 27 00:21:45 2015: 00:25:83:e8:46:80 Successful transmission of LWAPP Discovery Response to AP 00:25:83:e8:46:80 on port 1

This is all I get. I'm troubleshooting this AP/WLC remotely so I don't have hands on access. Anything you guys can suggest? I've been scratching my head at this for awhile. I cannot Telnet/SSH into the AP due to security settings.

I'm also noticing that the AP does not have a listing in the ARP cache of the router, however that could be normal if it is unjoined? I'm not too sure.

Leo Laohoo · ‎02-26-2015

Time and date of the AP is correct. Therefore there's only a few culprits left:

1. Your AP is running MESH IOS;

2. Your AP has the wrong Regulatory Domain

Post the output the the command:

1. AP: sh version;

2. AP: sh ip int brief;

3. WLC: sh sysinfo

Dave Dougher · ‎02-26-2015

I can get the sysinfo from the WLC, but again I cannot log into the AP as security settings have disabled remote access.

(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 4.2.207.0
RTOS Version..................................... 4.2.207.0
Bootloader Version............................... 4.2.207.0
Build Type....................................... DATA + WPS

System Name...................................... wlc1463a
System Location.................................. Store Location
System Contact................................... Network Group
System ObjectID.................................. 1.3.6.1.4.1.9.1.818
IP Address....................................... 10.24.94.236
System Up Time................................... 0 days 9 hrs 8 mins 15 secs

Configured Country............................... US - United States

State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Disabled
Number of WLANs.................................. 7
3rd Party Access Point Support................... Disabled
Number of Active Clients......................... 3
--More-- or (q)uit

Burned-in MAC Address............................ 00:1E:BE:CC:03:C0

knadsady · ‎02-26-2015

DId you doublecheck the controller name you configured for the Primary or secondary controller for the AP?

Not sure about your older version 4.2, but newer versions require the primary controller name configured for the AP to match exactly the name configured for the controller, including upper/lower case characters. If they don't match, I have seen a problem similar to yours where the AP does not like the response from the controller.

johnd2310 · ‎02-26-2015

Was this access point associated to the controller and is now failing or is this a new access point?

What is the model of the access point

**Please rate posts you find helpful**

Abhishek Abhishek · ‎03-09-2015

Please refer to the link-

http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/99948-lap-notjoin-wlc-tshoot.html

mohanak · ‎03-10-2015

Issue the debug lwapp events enable command at the controller CLI.

Look for the LWAPP discovery > discovery response > join request > join response sequence. If you do not see the LWAPP discovery request, it means the AP cannot or does not find the controller.

Check for IP connectivity between the AP network and the controller. If the controller and the AP reside in the same subnet, ensure that they are properly interconnected. If they reside in different subnets, ensure that a router is used in between them and routing is properly enabled between the two subnets.

Verify that the discovery mechanism is correctly configured.

If the Domain Name System (DNS) option is used for discovering the WLC, ensure that the DNS server is correctly configured to map CISCO-LWAPP-CONTROLLER.local-domain with the WLC IP address. Hence, if the AP can resolve the name, it issues an LWAPP join message to the resolved IP address.

If option 43 is used as the discovery option, ensure that it is properly configured on the DHCP server.

Refer to Register the LAP with the WLC for more information on the discovery process and sequence.

Refer to DHCP OPTION 43 for Lightweight Cisco Aironet Access Points Configuration Example for more information on how to configure DHCP option 43.

http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/69339-lwapp-upg-tool.html#cause1