%CAPWAPPING-3-PKT_RECV_ERROR: 1 wcm:

[rhub]

I've installed 3650 as MA; wlc 5508 is MC. APs are 3702.

Everything worked fine until yesterday. I've checked the log-entries and found the following error-msg, appearing every 30 secs:

%CAPWAPPING-3-PKT_RECV_ERROR: 1 wcm:  capwapPingSocketTask: capwappingRecvPkt returned error

Nobody is claiming about any problems using the WLAN.

Doing a "sh wireless mobility summary" eveything seems to be o.k

Mobility Agent Summary:

Mobility Role                                   : Mobility Agent
Mobility Protocol Port                      : 16666
Mobility Switch Peer Group Name  : XXX_SPG_1
Multicast IP Address                        : 0.0.0.0
DTLS Mode                                      : Enabled
Mobility Domain ID for 802.11r         : 0x41d
Mobility Keepalive Interval                : 10
Mobility Keepalive Count                  : 3
Mobility Control Message DSCP Value             : 48
Switch Peer Group Members Configured            : 1

Link Status is Control Link Status : Data Link Status

The status of Mobility Controller:

IP              Public IP            Link Status
------------------------------------------------
172.16.2.50     172.16.2.50          UP   : UP

Switch Peer Group members:

IP              Public IP            Data Link Status
-----------------------------------------------------
172.16.2.40     172.16.2.40          UP

Config looks o.k too

Any hint is appreciated very much

Best regards

Roman

[Salma Sulthana]

Hi Roman,

It seems to be a cosmetic Bug, of reporting excessive %CAPWAPPING-3-PKT_RECV_ERROR: 1 wcm:  capwapPingSocketTask: capwappingRecvPkt returned error logs.

However, these logs will also be generated if the MAs IP address is not configured correctly with the management interface VLAN, but configured with MC IP address.

Regards

Salma

[rhub]

Hi Salma,

wireless management interface is vlan2, 

ip address of the MA is:

interface vlan2

 ip address 172.16.2.40/24

MC has ipaddr of 172.16.2.50

So, first, from my point of view, the config is ok and second, clients are not facing any problems.

Regards

Roman

[Salma Sulthana]

Hi Roman,

Thanks for your response, please do make sure that you have not configured "Wireless mobility controller peer xxx" command when you have just one MA.

Since you only have one controller, you should only have "wireless mobility
controller" command configured on it and nothing else.
When you will add other controllers, you will be able to add a peer-group and add as
member all the MA (and not the MC itself).

This occurs if you configured yourself as mobility peer. This is normally not possible
unless you configure the mobility controller peer ip command and then change your wireless
management ip to be that ip. Removing oneself as mobility peer made the problem go away.

Regards

Salma

[rhub]

Hi Salma,

many thanks for your newest reply. I'm aware of the command you've mentioned and

NO... I did not configure it. Currently we have implemented a 2nd 3650 as MA with the same config (of course except ip addressing etc.) and interestingly enough, I don't see these error-msgs. We have a different (lower) code-level on this 3650, so it's most probably a cosmetical bug, as you mentioned in your 1st reply.

Best regards

Roman

[Salma Sulthana]

Hi Roman,

Thanks for the update, i am glad that you have configured it correctly.

Yes, there can be a possibility that this is a cosmetic Bug as I see that there are many such cosmetic issues. 

Regards

Salma