Error logs on WLC

[hassan_si]

What is the meanining of the error message below....

Dec 27 01:53:12.404

Could someone please let us know if this is normal... I am getting the above message frequently on the Controllers.

ethoip.c:369 ETHOIP-3-PKT_RECV_ERROR: ethoipSocketTask: ethoipRecvPkt returned error

[Surendra BG]

"ethoipSocketTask: ethoipRecvPkt returned error" is the generic message related to Mobility and this is followed by various similar mobilities messages as well.. are we able to see any??

lemme know if this answered your question..

Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

[hassan_si]

This is the msg I am getting below... This error is related to mobility. Please let us know.

Dec 27 04:50:02.552 ethoip.c:369 ETHOIP-3-PKT_RECV_ERROR: ethoipSocketTask: ethoipRecvPkt returned error

2010-12-27 04:39:44 Local0.Error 172.30.64.132 DCAWLAN6: Dec 27 04:50:02.552 ethoip.c:369 ETHOIP-3-PKT_RECV_ERROR: ethoipSocketTask: ethoipRecvPkt returned error

2010-12-27 04:39:51 Local0.Error 172.30.64.132 DCAWLAN6: Dec 27 04:50:10.405 ethoip.c:369 ETHOIP-3-PKT_RECV_ERROR: ethoipSocketTask: ethoipRecvPkt returned error

2010-12-27 04:39:51 Local0.Error 172.30.64.132 DCAWLAN6: Dec 27 04:50:10.405 ethoip.c:369 ETHOIP-3-PKT_RECV_ERROR: ethoipSocketTask: ethoipRecvPkt returned error

2010-12-27 04:39:54 Local0.Error 172.30.64.132 DCAWLAN6: Dec 27 04:50:12.552 mm_listen.c:5696 MM-3-INVALID_PKT_RECVD: Received an invalid packet from 172.30.77.12. Source member:0.0.0.0. source member unknown.

2010-12-27 04:39:54 Local0.Error 172.30.64.132 DCAWLAN6: Dec 27 04:50:12.552 ethoip.c:369 ETHOIP-3-PKT_RECV_ERROR: ethoipSocketTask: ethoipRecvPkt returned error

2010-12-27 04:39:54 Local0.Error 172.30.64.132 DCAWLAN6: Dec 27 04:50:12.553 ethoip.c:369 ETHOIP-3-PKT_RECV_ERROR: ethoipSocketTask: ethoipRecvPkt returned error

2010-12-27 04:39:56 Local0.Error 172.30.64.132 DCAWLAN6: Dec 27 04:50:14.562 mm_listen.c:5696 MM-3-INVALID_PKT_RECVD: Received an invalid packet from 172.30.77.10. Source member:0.0.0.0. source member unknown.

2010-12-27 04:39:56 Local0.Error 172.30.64.132 DCAWLAN6: Dec 27 04:50:15.405 mm_listen.c:5696 MM-3-INVALID_PKT_RECVD: Received an invalid packet from 172.30.77.10. Source member:0.0.0.0. source member unknown.

2010-12-27 04:39:57 Local0.Error 172.30.64.132 DCAWLAN6: Dec 27 04:50:15.837 mm_listen.c:5696 MM-3-INVALID_PKT_RECVD: Received an invalid packet from 172.30.77.10. Source member:0.0.0.0. source member unknown.

2010-12-27 04:39:58 Local0.Error 172.30.64.132 DCAWLAN6: Dec 27 04:50:16.805 mm_listen.c:5696 MM-3-INVALID_PKT_RECVD: Received an invalid packet from 172.30.77.10. Source member:0.0.0.0. source member unknown.

Thanks,

Hassan

[Surendra BG · Accepted solution]

Hi,

From the below 2 outputs..

MM-3-INVALID_PKT_RECVD: Received an invalid packet from 172.30.77.10. Source member:0.0.0.0. source 
member unknown.

MM-3-INVALID_PKT_RECVD: Received an invalid packet from 172.30.77.12. Source member:0.0.0.0. source 
member unknown.

This message is almost always due to incorrect mobility group configuration. My guess is that 172.30.77.10 
and 172.30.77.12 are other  controllers in your environment. If these controllers should NOT be in a mobility 
group with the controller in question, remove the associated mobility group entries in these other controllers.
Otherwise, verify that  all controllers are added with the correct mac addresses to prevent  receiving "member 
unknown" errors.

here is the link to configure the mobility..

http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mobil.html#wp1093741

lemme know if this answered your question..

Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

[hassan_si]

Thanks for your support..

Regards,

Hassan

[Surendra BG]

Hi,

Its my pleasure!! Thanks for posting on CSC.. looking forward to see some more posts!!

Regards

Surendra

[Grayson Wells]

For future reference, I have also seen this error when the Mobility Domain name was different than the Mobility Group name. From my understanding, they don't have to be the same, but when I mirrored the two names, I stopped getting this error message.