×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Wireless - Mobility Anchor - Data Path / Control Path

Answered Question
Mar 14th, 2014
User Badges:

Hi,

Wireless - Mobility Anchor - Data Path / Control Path

We had to power down the 2 WLC , Primary - 5508 / Mobility Anchor - 2504

Now the Control path is up for the Guest Wireless , however Data path refuses to come up.

I tried removing and dding the mobility anchor. no go.

tried enabling / disabling the interface / SSID - no go.

has any one faced this kind of issue before. We not made any changes to the configs.

Thanks,

JA

Correct Answer by Scott Fella about 3 years 5 months ago

Maybe the config was not saved of something happened.... I would look at the mobility configuration again... make sure the mac address you use is the one that shows up on the first line when adding a mobility group.  This should match up with the WLC base mac address, but at times it doesn't.  

I would also monitor your FW to see if the FW is blocking udp 16666 and udp 16667 (mping/control path) or IP 97 (eping/data path)

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Ali Aqrabawi Sat, 03/15/2014 - 02:17
User Badges:
  • Cisco Employee,

how about Mping ?

 

also can you share show run-config , from both WLCs ?

Correct Answer
Scott Fella Sat, 03/15/2014 - 07:01
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

Maybe the config was not saved of something happened.... I would look at the mobility configuration again... make sure the mac address you use is the one that shows up on the first line when adding a mobility group.  This should match up with the WLC base mac address, but at times it doesn't.  

I would also monitor your FW to see if the FW is blocking udp 16666 and udp 16667 (mping/control path) or IP 97 (eping/data path)

Joseph Antony Sun, 03/16/2014 - 18:44
User Badges:

hi 

 

thanks for your replies.

the issue was with our firewalls on the inside interface. I disabled it for a moment and it was ok. and then re-enabled the firewall rules it was still ok. Maybe it was just a few packets required to be released to bring the data path up.

I will revisit the rules to check exactly what was blocking this particular traffic. 

 

many thanks once again,

 

regards,

JA

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode