AIR-CAP3602I-E-K9 are not connecting remotely (Flexconnect ) to 5508 controller

vinodjad1234 · ‎08-06-2013

Hi Experts,

I have remote site where AP's are connected and controller is located at centralised location

AP version : AIR-CAP3602I-E-K9

WLC 5508 - software version 7.0.220.0

AP's are getting ip address sucessfully however not getting registered with controller .

i have configured directly connected ports as trunk to allow SSID vlan subnets made native vlan as AP management subnet vlan .

i could see cdp neighbors for all AP's but did not see any logs even in controller for this AP's

Could you please suggest me to troubleshoot this issue ?

or is it compatibility issue with controller firmware ?

Scott Fella · ‎08-06-2013

Add a DNS entry for cisco-capwap-controller pointing to the WLC management IP address. Unless you stages the APs, they don't know how to find the WLC.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

vinodjad1234 · ‎08-06-2013

Hi,

I have already configured DHCP option 43 pointing to the WLC management ip address however still not able to find the controller .

Debug output has got discovery request and response packets however i do not see any join request from any AP. i have attached the debug output for the same .

even the output of join summary shows that AP's status as " Not joined "

what could be the reason that AP's are not able to send join request to controller ?

Message was edited by: vinod jadhav

vinodjad1234 · ‎08-06-2013

Hi Experts,

I am really clueless for such issue.

Can anybody look into this and suggest me ?

Scott Fella · ‎08-07-2013

Console into the ap and reboot the ap and post the output.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

vinodjad1234 · ‎08-07-2013

Hi Scott,

Thanks for your reply .

AP's is in remote location however i would get this output shortly and share it .

meantime i collected the < debug capwap event enable > output from controller for one of the AP.

below is the output :

23:12.6 4c:00:82:xx:xx:xx Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 350, joined Aps 170

23:12.6 4c:00:82:xx:xx:xx Discovery Response sent to 10.x.6.4:30637

23:22.6 4c:00:82:xx:xx:xx Discovery Request from 10.x.6.4:30637

23:22.6 4c:00:82:xx:xx:xx Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 350, joined Aps 170

23:22.6 4c:00:82:xx:xx:xx Discovery Response sent to 10.x.6.4:30637

23:32.6 4c:00:82:xx:xx:xx Discovery Request from 10.x.6.4:30637

23:32.6 4c:00:82:xx:xx:xx Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 350, joined Aps 170

23:32.6 4c:00:82:xx:xx:xx Discovery Response sent to 10.x.6.4:30637

23:42.6 4c:00:82:xx:xx:xx Discovery Request from 10.x.6.4:30637

23:42.6 4c:00:82:xx:xx:xx Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 350, joined Aps 170

23:42.6 4c:00:82:xx:xx:xx Discovery Response sent to 10.x.6.4:30637

23:52.6 4c:00:82:xx:xx:xx Discovery Request from 10.x.6.4:30637

23:52.6 4c:00:82:xx:xx:xx Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 350, joined Aps 170

23:52.6 4c:00:82:xx:xx:xx Discovery Response sent to 10.x.6.4:30637

In above output , i do not see any join request coming from AP.

Rasika Nayanajith · ‎08-07-2013

You have to get console output to see what's going on...

In the mean time can you check what is the IP get by AP via DHCP & test the reachability to that from your WLC. I hope you have convert AP into flexconnect mode with VLAN mapping before sending it to remote branch. If not try connect it in local mode (configuring switch port as access vlan)

In case Option 43 or DNS is not working you can try manually configure the controller IP on AP CLI once you get into AP console.

Try these two command & see

# debug capwap console cli

# capwap ap primary-base

HTH

Rasika

vinodjad1234 · ‎08-07-2013

Thanks for sharing information . i will collect this info and share it for sure ....

Moreover i am able to ping the ip address of AP from WLC. so there is no issue for reachability .

attached screenshot is the additional info from wlc which shows the join status :

Thanks ...

Syed Moazzam Ali · ‎08-07-2013

1- upgrade WLC 5508 - software version to 7.2 or 7.3.

2- can WLC ping AP and AP ping WLC.

If both can ping each other, then send the output of show flash: of the AP. might be this AP came with Mesh software and you have to add it in MAC filter list of WLC.

v.avagliano · ‎08-07-2013

Check the Compatibilitry Matrix, and as written update the WLC release

vinodjad1234 · ‎08-07-2013

Hi ,

I feel you are right ....

The compatibility is the issue because according to doc. first software version is

7.1.91.0 however we have controller with 7.0.220.0.

should i upgrade to 7.2.110.0 ?

both can ping each other ...

Scott Fella · ‎08-07-2013

He is right... Certain code only supports certain hardware. You can upgrade to any code that supports the AP. what code train you go with depends on the features you need. The WLC contains the image file and if you consoled into the AP you would if seen a log stating the code compatibility. The WLC doesn't have an image to push to that AP. Upgrade to a version that is compatible with all your AP models you have.

Here is the matrix just in case

http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

Rasika Nayanajith · ‎08-07-2013

Yes, you have to upgrade your WLC software.

If you checked your AP CLI output it should tell something similare to this.. Here is a 3600 AP trying to register to my WLC which is running 7.0.116.0.

%CAPWAP-3-ERRORLOG: Discovery response from MWAR 'WLC2'running version 7.0.116.0 is rejected.

%CAPWAP-3-ERRORLOG: Failed to decode discovery response.

%CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

%CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

%CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.20.22

%CAPWAP-3-ERRORLOG: Discovery response from MWAR 'WLC2'running version 7.0.116.0 is rejected.

vinodjad1234 · ‎08-07-2013

Thanks to all for sharing all the information !!!

I will upgrade the software firmware and revert with result.

This forum is really rocks ..............:)

vinodjad1234 · ‎08-16-2013

Hi Experts,

I have controller with 7.2.110.0 firmware now however no luck still..

AP's are not able to join the controller :

*spamApTask2: Aug 16 09:55:11.499: ec:e1:a9:6b:a5:90 Discovery Request from 10.51.6.4:30638

*spamApTask2: Aug 16 09:55:11.499: ec:e1:a9:6b:a5:90 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask2: Aug 16 09:55:11.499: ec:e1:a9:6b:a5:90 Discovery Response sent to 10.51.6.4:30638

*spamApTask2: Aug 16 09:55:22.272: ec:e1:a9:6b:a5:90 DTLS keys for Control Plane are plumbed successfully for AP 10.51.6.4. Index 178

*spamApTask2: Aug 16 09:55:22.272: ec:e1:a9:6b:a5:90 DTLS Session established server (10.1.0.19:5246), client (10.51.6.4:30638)

*spamApTask2: Aug 16 09:55:22.272: ec:e1:a9:6b:a5:90 Starting wait join timer for AP: 10.51.6.4:30638

*spamApTask2: Aug 16 09:55:22.409: ec:e1:a9:6b:a5:90 Join Request from 10.51.6.4:30638

*spamApTask2: Aug 16 09:55:22.409: ec:e1:a9:6b:a5:90 Deleting AP entry 10.51.6.4:30638 from temporary database.

*spamApTask2: Aug 16 09:55:22.410: ec:e1:a9:6b:a5:90 Join Version: = 117599744

*spamApTask2: Aug 16 09:55:22.410: ec:e1:a9:6b:a5:90 Join resp: CAPWAP Maximum Msg element len = 90

*spamApTask2: Aug 16 09:55:22.410: ec:e1:a9:6b:a5:90 Join Response sent to 10.51.6.4:30638

*spamApTask2: Aug 16 09:55:22.410: ec:e1:a9:6b:a5:90 CAPWAP State: Join

*spamApTask2: Aug 16 09:55:22.410: ec:e1:a9:6b:a5:90 capwap_ac_platform.c:1224 - Operation State 0 ===> 4

*apfReceiveTask: Aug 16 09:55:22.410: ec:e1:a9:6b:a5:90 Register LWAPP event for AP ec:e1:a9:6b:a5:90 slot 0

*apfReceiveTask: Aug 16 09:55:22.410: WARP IEs: (12)