cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
754
Views
0
Helpful
1
Replies

Wireless syslog errors

Hemakumar Ramasamy
Community Member

Hi,

In my syslog server we are seeing some wireless errors. Can you please tell me how to trouble shoot these errors.

Errors

1. WW_WIFI_CORE1_WISM-B: *ethoipSocketTask: ethoip.c:338 ethoipSocketTask: ethoipRecvPkt returned error

2. WW_WIFI_CORE1_WISM-B: *ethoipSocketTask: ethoip.c:131 Recv Ethernet over IP ping from 159.3.56.21, not from a mobility peer

3. WW_WIFI_CORE1_WISM-A: *spamReceiveTask: spam_apf.c:333 Unable to find AP 00:15:f9:5a:99:d0 entry in the database, could not process delete WLAN ALL MNs message


4. WW_WIFI_CORE1_WISM-A: *mmListen: mm_listen.c:7671 Received an invalid packet from 159.3.56.21. Source member:0.0.0.0. source member unknown.

1 Reply 1

Rasika Nayanajith
VIP Alumni
VIP Alumni
 WW_WIFI_CORE1_WISM-B: *ethoipSocketTask: ethoip.c:131 Recv Ethernet over IP ping from 159.3.56.21, not from a mobility peer

Seems like WISM-A & WISM-B in different mobility group and you have not configured mobility peering with each other.

"show mobility summary" output tells you the mobility status of your controllers.

HTH

Rasika

*** Pls rate all useful responses ***

Review Cisco Networking for a $25 gift card