topic Re: CAPWAP log messages in Wireless

CAPWAP log messages

Flavio Boniforti — Sun, 04 Jul 2021 04:31:27 GMT

Hello everybody.

While looking at one of my LAPs I got following log entries:

*Feb 7 06:24:43.648: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb 7 06:24:43.648: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.30.0.100

What could above messages mean?

I actually got troubles for clients trying to surf the web from that LAP: they do not get through (I'm investigating, I don't know yet if they at least get an IP address assigned or not)...

Could the above log entries have something to do with the troubles my clients are experiencing?

Thanks,

CAPWAP log messages

Scott Fella — Tue, 07 Feb 2012 12:49:22 GMT

Could be... you need to paste more of the log. Does the ap show up as joined on the wlc or do you see it bouncing... take a look at the join time when you click on the ap in the GUI.

Re: CAPWAP log messages

Flavio Boniforti — Tue, 07 Feb 2012 12:56:28 GMT

Hy Scott...

The AP is joined AFAICS:

UP Time 11 d, 00 h 48 m 31 s

Controller Associated Time 0 d, 13 h 34 m 38 s

Controller Association Latency 0 d, 00 h 00 m 27

Here a bit more log output from the LAP itself:

*Feb 7 06:24:43.648: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb 7 06:24:43.648: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.30.0.100

*Feb 7 06:59:03.203: %CAPWAP-5-CHANGED: CAPWAP changed state to DOWN

*Feb 7 06:59:03.367: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Feb 7 06:59:04.373: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Feb 7 06:59:04.543: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Feb 7 06:59:04.789: %CAPWAP-5-CHANGED: CAPWAP changed state to UP

*Feb 7 06:59:04.955: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Feb 7 06:59:05.113: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 7 06:59:05.135: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Feb 7 06:59:05.144: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Feb 7 06:59:05.160: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 7 06:59:06.135: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Feb 7 07:17:09.319: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb 7 07:17:09.319: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.30.0.100

*Feb 7 07:26:03.890: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb 7 07:26:03.890: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.30.0.100

*Feb 7 07:32:01.689: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb 7 07:32:01.692: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.30.0.100

*Feb 7 07:40:58.774: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb 7 07:40:58.774: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.30.0.100

*Feb 7 07:46:58.131: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb 7 07:46:58.131: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.30.0.100

*Feb 7 07:52:55.484: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb 7 07:52:55.484: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.30.0.100

*Feb 7 08:01:52.202: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb 7 08:01:52.202: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.30.0.100

*Feb 7 08:52:36.977: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Feb 7 08:52:36.977: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.30.0.100

*Feb 7 09:27:18.152: %CAPWAP-5-CHANGED: CAPWAP changed state to DOWN

*Feb 7 09:27:19.244: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Feb 7 09:27:19.392: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Feb 7 09:27:19.750: %CAPWAP-5-CHANGED: CAPWAP changed state to UP

*Feb 7 09:27:19.923: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Feb 7 09:27:19.939: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Feb 7 09:27:20.392: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Feb 7 09:27:21.109: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Feb 7 09:27:21.128: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 7 09:27:22.128: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Feb 7 10:08:27.912: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to down

*Feb 7 10:08:27.921: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Feb 7 10:08:27.937: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 7 10:08:27.943: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

*Feb 7 10:08:27.953: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Feb 7 10:08:27.978: %LWAPP-3-CLIENTEVENTLOG: SSID Guest added to the slot[0]

*Feb 7 10:08:27.994: %LWAPP-3-CLIENTEVENTLOG: SSID Guest added to the slot[1]

*Feb 7 10:08:28.148: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Feb 7 10:08:28.154: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to down

*Feb 7 10:08:28.164: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Feb 7 10:08:28.179: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 7 10:08:28.186: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

*Feb 7 10:08:28.195: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Feb 7 10:08:28.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Feb 7 10:09:23.912: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to down

*Feb 7 10:09:23.922: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Feb 7 10:09:23.937: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 7 10:09:23.944: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

*Feb 7 10:09:23.953: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Feb 7 10:09:23.969: %LWAPP-3-CLIENTEVENTLOG: SSID Guest added to the slot[0]

*Feb 7 10:09:23.985: %LWAPP-3-CLIENTEVENTLOG: SSID Guest added to the slot[1]

*Feb 7 10:09:24.136: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Feb 7 10:09:24.145: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to down

*Feb 7 10:09:24.154: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Feb 7 10:09:24.170: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 7 10:09:24.176: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

*Feb 7 10:09:24.186: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Feb 7 10:09:24.202: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

Thanks again for your support!

Re: CAPWAP log messages

Scott Fella — Tue, 07 Feb 2012 14:23:35 GMT

Take a look at this post

https://supportforums.cisco.com/thread/343896

Sent from Cisco Technical Support iPhone App

Re: CAPWAP log messages

Flavio Boniforti — Tue, 07 Feb 2012 14:29:29 GMT

Hy Scott.

I'm running Firmware 7.0.116.0, so the issue from that post is for sure solved, what do you think?

CAPWAP log messages

Scott Fella — Tue, 07 Feb 2012 14:35:02 GMT

Are you having issues will only one ap or all of them?

Re: CAPWAP log messages

Flavio Boniforti — Tue, 07 Feb 2012 15:20:49 GMT

I saw those messages on two LAP (out of 7).

Those 2 are abroad, in a different country.

I thought there may be troubles caused from the messages I posted initially, but the firewall-guy didn't create the relevant policies to enable my wireless-clients to surf... Sorry for bothering... 😞

I rebooted both LAPs and since 1 hour I didn't get those messages anymore... this doesn't have to do with the firewall-policies now enabling wlan-clients to surf, thus I'll be reporting back if something will happen again...

Thanks so far!

Re: CAPWAP log messages

Scott Fella — Tue, 07 Feb 2012 15:53:59 GMT

At least you figured out the problem. Good job.

Thanks,

Scott Fella

Sent from my iPhone

CAPWAP log messages

Johan Lindstrand — Fri, 27 Sep 2013 07:51:25 GMT

I still get this capwap errors.

*Sep 27 07:48:39.830: %CAPWAP-3-ERRORLOG: Selected MWAR 'xxxxxx'(index 0).

*Sep 27 07:48:39.830: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Sep 27 07:48:30.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.xx.yy peer_port: 5246

*Sep 27 07:48:30.640: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.17.xx.yy peer_port: 5246

*Sep 27 07:48:30.641: %CAPWAP-5-SENDJOIN: sending Join Request to 172.17.16.27

*Sep 27 07:48:30.646: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.

*Sep 27 07:48:30.646: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.

*Sep 27 07:48:30.647: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Sep 27 07:48:30.647: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.17.xx.yy

I am running 7.5.102 version.

My clients complaining about losing connection to the AP

Regards

Johan

CAPWAP log messages

Rasika Nayanajith — Fri, 27 Sep 2013 21:39:28 GMT

What is the model number of those two AP ?

CAPWAP log messages

Jwaas9876 — Mon, 18 Nov 2013 15:47:00 GMT

Hi All,

We are having a similar issue. We have a 1142N LAP at a site connected via FlexConnect to a Flex7510 WLC at a datacenter. 7510 WLC is running 7.3.X code.

The following excerpt is from the LAP "show log":

*Nov 18 14:19:25.127: %CAPWAP-3-ERRORLOG: Received packet with invalid sequence number: got 150 expected 151.

*Nov 18 14:19:25.127: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Nov 18 14:19:25.127: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from X.X.X.X

*Nov 18 14:37:49.733: %CAPWAP-3-ERRORLOG: Received packet with invalid sequence number: got 222 expected 223.

*Nov 18 14:37:49.733: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Nov 18 14:37:49.733: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from X.X.X.X

*Nov 18 14:37:52.801: %CAPWAP-3-ERRORLOG: Received packet with invalid sequence number: got 223 expected 224.

*Nov 18 14:37:52.802: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Nov 18 14:37:52.802: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from X.X.X.X

Will be opening a case with TAC to troubleshoot further. May be more of a WAN related issue...

CAPWAP log messages

Leo Laohoo — Mon, 18 Nov 2013 21:39:55 GMT

Post the following output:

1. WLC: sh sysinfo;

2. WLC: sh time;

3. AP: sh version;

4. AP: sh ip interface brief; and

5. AP: sh inventory

CAPWAP log messages

Johan Lindstrand — Tue, 19 Nov 2013 07:01:23 GMT

Check your trunk connection.

My problem was a trunk that was not stable, losing connection to WLC for 1-2 sek during resynking