01-13-2012 10:24 AM - edited 07-03-2021 09:22 PM
I have 2 3502I WAP's in my London office that i'm trying to register to our Amsterdam 4402 WLC. They were able to successfully pull DHCP from a local switch, including option 43, and did register with my controller yesterday. As per the normal process, the controller pushed an updated image to each, and the WAP's reboot. After the reboot, they are stuck in an endless loop of trying to call the ap-manager interface, not the Management interface, so are failing to register.
As of now, i'm at a loss as to how to correct this. Is there a compatibility issue with the image that was pushed? Is there a way to push a different image, with the correct IP?
Please see the attachment for the repeating logs on the CLI of one of the WAP's.
Any ideas/help would be greatly appreciated.
Jeff Bull
Solved! Go to Solution.
01-13-2012 03:57 PM
Controller is now running 7.0.116.0, and the 3502I's have received the new code, but are right back to where I started;
Hmmmm ... so it can "join" intially. Wierd.
Can you console into the WAP and enter the command "clear capwap private" and reboot again?
Another thing, you have a 4402. So how many WAPs can you 4402 support (25?) and how many are currently joined to this unit?
01-13-2012 11:38 AM
You are in 7.0.98.0 or higher code on the wlc?
Thanks,
Scott Fella
Sent from my iPhone
01-13-2012 11:40 AM
Running 7.0.98.0 right now. Odd part is, when the 3502I's connect, the controller sends them 7.0.112.74 instead of 7.0.98.0. I'm thinking 7.0.112.74 is not compatible with the 3502's.
01-13-2012 11:43 AM
That is weird. Do you have any other WLC's in the network. I you have a redundant wlc in the 7.0.98.0, change the option to point to that wlc. I'm also guessing you have other AP's on theses WLC's with no issues.
Thanks,
Scott Fella
Sent from my iPhone
01-13-2012 11:44 AM
Can you console into the ap and post the output.
Thanks,
Scott Fella
Sent from my iPhone
01-13-2012 12:13 PM
This same sequence is now repeating over & over...
*Jan 13 18:42:24.887: %CAPWAP-3-ERRORLOG: Selected MWAR 'AMSWLC01'(index 0).
*Jan 13 18:42:24.887: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jan 13 18:42:24.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.170.29.9 peer_port: 5246
*Jan 13 18:42:24.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Jan 13 18:42:24.566: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.170.29.9 peer_port: 5246
*Jan 13 18:42:24.566: %CAPWAP-5-SENDJOIN: sending Join Request to 10.170.29.9
*Jan 13 18:42:24.566: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Jan 13 18:42:25.862: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Jan 13 18:42:25.884: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.170.29.9
*Jan 13 18:42:25.884: %DTLS-5-PEER_DISCONNECT: Peer 10.170.29.9 has closed connection.
*Jan 13 18:42:25.884: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.170.29.9:5246
*Jan 13 18:42:25.931: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Jan 13 18:42:25.931: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Jan 13 18:42:25.991: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jan 13 18:42:25.991: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jan 13 18:42:26.003: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jan 13 18:42:26.006: status of voice_diag_test from WLC is false
01-13-2012 12:17 PM
You have other AP's on that wlc correct?
Sent from Cisco Technical Support iPhone App
01-13-2012 12:20 PM
Please check if the country code of AP and the country code of the WLC are in sync
Thanks
NikhiL
01-13-2012 12:23 PM
Scott,
Yes. I have 10 other access points, in Amsterdam (mix of 1142 & 1252's) currently registered.
Nikhil,
I verified that the NL country code is checked, but not GB (United Kingdom). When I try to add GB, I get a message that I need to disable 802.11a & b networks before I can make that change.
01-13-2012 12:29 PM
Ah... didn't think about AP's in a different country from the WLC:)
Thanks,
Scott Fella
Sent from my iPhone
01-13-2012 12:33 PM
Looks like both Netherlands and Great Britain support the same E domain, not sure though
If not in production you can disable both the 802.11a and b networks and enable GB along with NL in the country code for testing
Thanks
NikhiL
01-13-2012 12:46 PM
yes. The -E domain supports both GB and NL. When the ap joins it will pick the first regulatory domain that it matches. You would then need to set the more specific domain on the AP so that you are not in violation of any local regs. <-- for when multiple regulatory domains are allowed
So the ap would/should join as it would match the NL, reg domain.
The WLC shouldn't have 7.0.114 code on it, unless you had maybe had an engineering special loaded to the WLC.
So why it gave that code is a mystery. Right now.
Is it possible for you to upgrade to 7.0.220.0? That would force the ap to pull th new code and hopefully join
Sent from Cisco Technical Support iPad App
01-13-2012 01:37 PM
Thanks everyone. I'm actively copying a newer version of code to the controller (7.0.116.0, since I know it works at another office), and will load it shortly.
01-13-2012 03:51 PM
Controller is now running 7.0.116.0, and the 3502I's have received the new code, but are right back to where I started; In an endless cycle of trying to communicate with the ap-manager interface, but never getting connected.
I did add GB to the country code list (NL was already selected), but the behaviour didn't change.
Any thoughts? Completely at a loss now.
01-13-2012 03:55 PM
How do you have the ap manager setup. The management and ap-manager in the same subnet?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide