Mobility anchor issues

Unanswered Question
Mar 30th, 2010

Hi all.

I've got 2 WiSMs running as my internal controllers and a 5508 as the anchor. the docs I've seen say to have the anchor and the internal controllers in separate mobility groups but the only time i could get them to show 'Up' under control path in the Mobility Group section was when i placed them in the same mobility group. while in separate groups with the control path showing as down i could ping between internal and anchor controllers.

apreciate your help.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
sayrmatics Wed, 03/31/2010 - 04:47

i've got software version running on both the WiSMs and the 5508.

Andrew Betz Wed, 04/07/2010 - 18:42

Hi Seyi,

The WLCs will allow for you to maintain your Anchor WLCs within a seperate mobility domain.  Since mobility is operational between your two WLCs when within the same group, it is possible that there may be a slight misconfiguration.  Please take a look at the example below, and see if this helps:

Foreign WLC:

Default Mobility Domain: corp_internal

Mobility Members:

11:22:33:44:55:66 corp_internal

66:55:44:33:22:11 dmz

Anchor WLC:

Default Mobility Domain: dmz

Mobility Members:

66:55:44:33:22:11 dmz

11:22:33:44:55:66 corp_internal

Once you make these changes, try sending an eping and mping between WLCs.




This Discussion

Related Content



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