Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CAPWAP - AP won't join controller

I recently upgraded all our controllers to 5.2.178 code and now one of the access points in Russia will not connect to the controller in Leeds. The AP is giving the following output:

*Dec 14 16:04:17.968: %CAPWAP-5-CHANGED: CAPWAP changed state to UP

*Dec 14 16:04:17.970: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 14 16:04:17.977: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller BANANA

*Dec 14 16:04:18.024: %DTLS-3-BAD_RECORD: Erroneous record received from <output omitted>: : Duplicate (replayed) record

*Dec 14 16:04:18.033: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to down

*Dec 14 16:04:18.034: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Dec 14 16:04:18.063: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Dec 14 16:04:18.063: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 14 16:04:18.093: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 14 16:04:20.623: %DTLS-3-BAD_RECORD: Erroneous record received from <output omitted>: Duplicate (replayed) record

*Dec 14 16:04:23.487: %DTLS-3-BAD_RECORD: Erroneous record received from <output omitted>: : Duplicate (replayed) record

*Dec 14 16:04:26.353: %DTLS-3-BAD_RECORD: Erroneous record received from <output omitted>: : Duplicate (replayed) record

*Dec 14 16:04:29.220: %DTLS-3-BAD_RECORD: Erroneous record received from <output omitted>: : Duplicate (replayed) record

*Dec 14 16:04:32.084: %DTLS-3-BAD_RECORD: Erroneous record received from <output omitted>: : Duplicate (replayed) record

*Dec 14 16:04:34.951: %DTLS-5-ALERT: Received WARNING : Close notify alert from <output omitted>:

*Dec 14 16:04:34.951: %DTLS-5-PEER_DISCONNECT: Peer <output omitted>:  has closed connection.

*Dec 14 16:04:34.951: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to <output omitted>:

*Dec 14 16:04:35.001: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 14 16:04:35.002: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

6 REPLIES
Hall of Fame Super Gold

Re: CAPWAP - AP won't join controller

Avoid using the 5.X firmware if possible.

New Member

Re: CAPWAP - AP won't join controller

Hi

did u follow the upgrade path of the WLC? I dont think this will create a problem.

Thanks,

Elie

New Member

Re: CAPWAP - AP won't join controller

I face the same problem now, can you post the way you solved it out please.

Thanks

New Member

Re: CAPWAP - AP won't join controller

This issue ended up being a result of having the wrong country codes configured on the controller. I had to add GB and RU to my country list to get the AP's to join the controller. What is the model of the AP? Mine was this: AIR-LAP1242AG-E-K9 so I had to go into the following on the controller:

wireless>Country and select the appropriate regulatory domains

Make sure your regulatory domains include the letter 'E' (or whatever your access point model is)

Also, you have to disable the 'A' and 'G' radios globally to change the country domains.

New Member

Re: CAPWAP - AP won't join controller

My AP is AIR-LAP1142N-P-K9,  and controller is 5508.

I disabled radios as you said and checked Japan(P) in the Wireless/Country section...and it works!

Thanks a lot!

New Member

Re: CAPWAP - AP won't join controller

HI

My AP  is AIR-CAP3502I-E-K9 & WLC is 5508, even i had same error on AP console.

Many Thanks to  above post by vancamt76

Even i disabled radios & changed country code to SA , & then  it worked.

Thanks

Mazhar

3318
Views
10
Helpful
6
Replies
CreatePlease login to create content