topic Re: No Join request going out in Wireless

No Join request going out

Tabian — Sun, 04 Jul 2021 03:34:14 GMT

Hi Guys,

Trying to get an lightweight AP to register with a controller, never seen this one before where the Discovery request is going out to the controller, the discovery response is coming back, but then nothing. At this point the AP should then send a JOIN request, but it just doesnt.

I am using L3 LWAPP, and have the AP statically configured. its a 1131, connecting to a 5.1.151.0 in a WISM. I have run a wireshark and can see the discovery going out, its response coming back, but then nothing (the debugs below also back this up). I have also jumped on the controller and can see the discovery responces are going out but it says no JOIN's are coming in. I'm aware this is an old version of controller but still..

I've tried many different IOS on the AP, including the one it came with in the box, other previously successful IOS and the IOS that 5.1.151.0 dishes out to its registered AP's, multiple AP hardware resets, controller reboots, tried different controllers. etc... What would cause this? Possibly something in the response? See info below:

LWAPP Static IP Configuration

IP Address 172.18.240.244

IP netmask 255.255.255.192

Default Gateway 172.18.240.193

Primary Controller 172.18.252.40

APc471.feb0.b470#

Aug 11 11:03:55.520: UDP: sent src=172.18.240.244(2887), dst=172.18.252.40(12223), length=69 – Discovery request going out

Aug 11 11:03:55.521: UDP: rcvd src=172.18.252.40(12223), dst=172.18.240.244(2887), length=67 – Discovery response coming back

APc471.feb0.b470#

Here it should then send a join request, but nothing, just repeats the process of sending the discovery request.

Doing a debug lwapp event/error just shows the standard:

APc471.feb0.b470#

Aug 11 11:05:55.521: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR \

Aug 11 11:05:55.521: LWAPP_CLIENT_EVENT: spamResolveStaticGateway - gateway found

APc471.feb0.b470#

Controller

(WiSM-slot9-1) >show ap join stats detailed c4:71:fe:b0:b4:70

Discovery phase statistics
- Discovery requests received.............................. 6 <---------- Usually a lot more but ive bounced the controller.
- Successful discovery responses sent...................... 6
- Unsuccessful discovery request processing................ 0
- Reason for last unsuccessful discovery attempt........... Not applicable
- Time at last successful discovery attempt................ Aug 11 10:45:08.263
- 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 decrytion 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

Thats it..

Re: No Join request going out

Tabian — Fri, 12 Aug 2011 06:07:09 GMT

And obviously its nothing from here:

Troubleshoot a Lightweight Access Point Not Joining a Wireless LAN Controller

http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml#p1

No Join request going out

Leo Laohoo — Fri, 12 Aug 2011 06:10:02 GMT

Stay away from the WLC/WiSM firmware 5.X. Upgrade to 7.0.116.0 and try again.

No Join request going out

Surendra BG — Fri, 12 Aug 2011 06:10:46 GMT

Join request and response is for the AP manager interface.. do we have the same on the WLC?? make sure the AP manager is non pingable IP in thenetwork!!

Run the debug "debug capwap errors enable" "debug capwap events enable" on the WLC and pster it here and followed by get the console access to the AP and reboot it and paste the complete console legs till the AP reloads again.

Lemme know if this helps!!

Regards

Surendra

Re: No Join request going out

Tabian — Fri, 12 Aug 2011 06:16:31 GMT

Ofcourse the AP manager interface does not reply to ping.

I can see no point running the debug capwap errors enable, as I am using LWAPP, not CAPWAP.

Running the same debug for LWAPP shows the discovery request coming in, the response going out, and then nothing..

Re: No Join request going out

Surendra BG — Fri, 12 Aug 2011 06:18:38 GMT

are u able to ping the WLC managenment int ip addr freom the AP??

Regards

Surendra

Re: No Join request going out

Tabian — Fri, 12 Aug 2011 06:21:40 GMT

Yes, ofcourse..

and

You can see the discovery response coming back from it..

Aug 11 11:03:55.521: UDP: rcvd src=172.18.252.40(12223), dst=172.18.240.244(2887), length=67

– Discovery response coming back

Re: No Join request going out

Surendra BG — Fri, 12 Aug 2011 06:23:34 GMT

try this command

test lwapp controler ip

from the AP console.. and see if this helps

Regards

Surendra

Re: No Join request going out

dennischolmes — Fri, 12 Aug 2011 12:32:44 GMT

Your first mistake is using any version of 5x code. This was the most bug ridden version of code ever developed by Cisco and is why several developers made an abrupt exit from the Wireless Business Unit. Move to a production version of 6.0 or 7.0.116. If you don't want to move forward then I would suggest moving back to 4.2 code. Either way, there is absolutely NO WAY I would stay on 5.1. You are asking for more problems than you can imagine.