cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
10773
Views
0
Helpful
12
Replies

Restarting CAPWAP after 1 minute

MJU-NETDESIGN
Level 1
Level 1

Hi there

 

I have a Office connected to a Main office via a site2site running a Asa in both ends.

There are a Access point 2802, that are losing the connection to the WLC every 1 minute.

 

[*06/06/2018 02:36:44.1579] Warning, unencrypted data keepalive failed
[*06/06/2018 02:36:44.1579] Failed to receive data keepalive
[*06/06/2018 02:36:44.1580]
[*06/06/2018 02:36:44.1580] Lost connection to the controller, going to restart CAPWAP...
[*06/06/2018 02:36:44.1580]
[*06/06/2018 02:36:44.1580] Restarting CAPWAP State Machine.

 

Can it be a bug or a config issue ?

 

 

Mvh Mickey

1 Accepted Solution

Accepted Solutions

The solution was:

No _ in the AP group name.

View solution in original post

12 Replies 12

Leo Laohoo
Hall of Fame
Hall of Fame
What firmware is the WLC running on?

Its a WLC 3504 running version 8.5.120.0 and the accesspoint is a 2802.

 

 

Mvh Mickey

Console into the AP and leave it alone for about 15 minutes. Make sure the output from the console is logged.
Attach the logs into the thread.

The solution was:

No _ in the AP group name.

I have the same problem, did you use the command "no ap group name"?

What was the solution?

Did you mean that we should not use "_" in the AP Group Name?

From this old thread, yes it states the fix was not to use an underscore “_”.

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

Hi Scott,

 

thanks for answering, we are currently migrating our WIFI network to SD-WAN (which basically means IPSEC Tunneling), I have some AP's continuously sending me this:

 

*Aug 19 16:27:36.000: %CAPWAP-3-DATA_KEEPALIVE_ERR: Failed to receive data keep-alive *Aug 19 16:27:36.000: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.0.0.1:5246

 

 

I check this post but the AP Group name configuration is not the case so I read the following article about CAPWAP Path MTU Discovery, so I am wondering if the additional encapsulation caused by SD-WAN devices in addition to CAPWAP could be the cause because from the AP showing those disconnections negotiated a MTU of 576 with the WLC instead of the maximum required one. 

 

(Cisco Controller) >show ap config general APTESTING

Cisco AP Identifier.............................. 520
Cisco AP Name.................................... APTESTING
CAPWAP Path MTU.................................. 576
Cisco AP Group Name.............................. TESTINGACCESSPOINT
Primary Cisco Switch Name........................ WLC

 

https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/211405-Configure-CAPWAP-Path-MTU-Discovery.html

 

Oh... you should start your own thread then since your issue is totally different.
-Scott
*** Please rate helpful posts ***

patoberli
VIP Alumni
VIP Alumni
Could be a UDP timeout, have you opened the required CAPWAP control/data ports?
https://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/113344-cuwn-ppm.html#anc8
Otherwise do what Leo suggested.

Hi,

This happens in my environment as well but I don't have a solution yet. It only happens on a group of WAPs and not all of them. The AP group name i have is "default-group" any suggestions?

 

Thanks

MJohar2
Level 1
Level 1

Hi,

I had the same problem too but weirdly enough, the issue somehow resolved after I changed the cable from the AP to the switch. Hopefully this will help.

Thanks.

Review Cisco Networking for a $25 gift card