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

5520 Mobility Group "Control and Data Path Down"

William Krueger
Level 1
Level 1

I have installed and configured these two new 5520s for my client. They are to be redundant AP fail-overs for some 5508s. We are seeing Mobility Group failures (Status: Control and Data Path Down).  I have asked that the following ports be verified open:

  • UDP 16666 for tunnel control traffic
  • IP protocol 97 for user data traffic
  • UDP 161 and 162 for SNMP

I have verified I can do a standard ping between controllers.

From the 5520 with IP X.X.X.X:
(Cisco Controller) >show mobility summary

Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... atl
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0x4134
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 2
Mobility Control Message DSCP Value.............. 0

Controllers configured in the Mobility Group
MAC Address IP Address Group Name Multicast IP Status
64:00:f1:f5:77:cf X.X.X.X atl 0.0.0.0 Control and Data Path Down
a0:e0:af:33:a6:31 Y.Y.Y.Y atl 0.0.0.0 Up

(Cisco Controller) >


From the 5508 with IP Y.Y.Y.Y:
(Cisco Controller) >show mobility summary

Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... HOU
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0x66d1
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 2
Mobility Control Message DSCP Value.............. 0

Controllers configured in the Mobility Group
MAC Address IP Address Group Name Multicast IP Status
64:00:f1:f5:77:c0 Y.Y.Y.Y HOU 0.0.0.0 Up
a0:e0:af:33:a6:39 X.X.X.X atl 0.0.0.0 Control and Data Path Down

(Cisco Controller) >

Debug Logs:


(Cisco Controller) >*mmMobility: Apr 05 10:44:28.973: Keepalive: Data Ping request not received from peer HOU-WLC01-IP. transmitter->dataPingReqWaitCounter = 4

*mmMobility: Apr 05 10:44:28.973: Keepalive:Mobility Member HOU-WLC01-IP detected DOWN status 3, cleaning up client entries

*ethoipSocketTask: Apr 05 10:44:38.278: Keepalive:INVALID(GroupMismatch):ETHOIP_OP_REQ:Received from HOU-WLC01-IP:version=02:SeqNo=15200:receiverStatusOnTransmitter=0
*mmMobility: Apr 05 10:44:39.313: Keepalive: Data Ping request not received from peer HOU-WLC01-IP. transmitter->dataPingReqWaitCounter = 1

*mmMobility: Apr 05 10:44:39.313: Keepalive:Mobility Member HOU-WLC01-IP detected DOWN status 3, cleaning up client entries

*ethoipSocketTask: Apr 05 10:44:48.279: Keepalive:INVALID(GroupMismatch):ETHOIP_OP_REQ:Received from HOU-WLC01-IP:version=02:SeqNo=15201:receiverStatusOnTransmitter=0
*mmMobility: Apr 05 10:44:49.613: Keepalive: Data Ping request not received from peer HOU-WLC01-IP. transmitter->dataPingReqWaitCounter = 2

*mmMobility: Apr 05 10:44:49.613: Keepalive: Mobility Control Ping request not received from the peer HOU-WLC01-IP.reties = 3

*mmMobility: Apr 05 10:44:49.613: Keepalive:Mobility Member HOU-WLC01-IP detected DOWN status 3, cleaning up client entries

*ethoipSocketTask: Apr 05 10:44:58.277: Keepalive:INVALID(GroupMismatch):ETHOIP_OP_REQ:Received from HOU-WLC01-IP:version=02:SeqNo=15202:receiverStatusOnTransmitter=0
*mmMobility: Apr 05 10:44:59.969: Keepalive: Data Ping request not received from peer HOU-WLC01-IP. transmitter->dataPingReqWaitCounter = 3

*mmMobility: Apr 05 10:44:59.969: Keepalive:Mobility Member HOU-WLC01-IP detected DOWN status 3, cleaning up client entries

*ethoipSocketTask: Apr 05 10:45:08.282: Keepalive:INVALID(GroupMismatch):ETHOIP_OP_REQ:Received from HOU-WLC01-IP:version=02:SeqNo=15203:receiverStatusOnTransmitter=0
*mmMobility: Apr 05 10:45:10.253: Keepalive: Data Ping request not received from peer HOU-WLC01-IP. transmitter->dataPingReqWaitCounter = 4

*mmMobility: Apr 05 10:45:10.253: Keepalive:Mobility Member HOU-WLC01-IP detected DOWN status 3, cleaning up client entries

1 Reply 1

Use "eping" & "mping" to verify data and control path between these WLCs

https://mrncciew.com/2013/03/24/mobility-ping-tests/

you should see success for both, otherwise you need to check anything in the middle blocking those ports.

HTH

Rasika

*** Pls rate all useful responses ***

Review Cisco Networking products for a $25 gift card