Mobility group membership

Unanswered Question
Jun 20th, 2007

I have 4 WLC's deployed :

1. AnchorWLC - WLC4402 anchor in a DMZ for guest access

2. WLCA1 - WLC4402 on SiteA

3. WLCB1 - WLC2006 on SiteB

4. WLCB2 - WLC2006 on SiteB

SiteA & SiteB are geographically separated.

On all WLC's there is the same mobility group 'group1' with the following group members:

1.on AnchorWLC: group1 members:WLCA1,WLCB1,WLCB2

2.on WLCA1: group1 members: anchorWLC

3.on WLCB1: group1 members: WLCB2,anchorWLC

4.on WLCB2: group1 members:WLCB1,anchorWLC

As SiteA and SiteB are geographically separated I have not included internal(non-anchor) WLC's that are on siteA in the mobility group created on WLC's on SiteB and vice versa . The only WLC that has all controllers added to his mobility group is the AnchorWLC as guest access is needed from both siteA and siteB.

Is this a valid config(anayway it is working...) or is it recommended to have 2 different mobility groups, one for each site(A & B) and create 2 seperate mobility groups on the anchorWLC ?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
smahbub Wed, 06/27/2007 - 05:40

I would recommend going for two separate mobility groups. Even though it is working since it is geographically separated, its always better to have different mobility groups.

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