Multiple WLC devices, Inter-subnet roaming, and Mobility Groups

Unanswered Question
May 17th, 2007
User Badges:

We have a scenario in which we have multiple controllers in separate buildings (separate VLANs and two different mobility groups) with 200+ APs spread throughout the enterprise. Because of an old controller DNS entry and OTAP, it is probably safe to assume that every LWAPP AP has built a list that includes every controller in the enterprise -- including controllers in another VLAN.

Here is the problem: Recently, a controller at the primary building crashed and some AP's moved to a controller in the secondary building (different VLAN). When that happened, users began roaming between APs in mobility groups. Because of this, inter-subnet roaming did not occur, client IP addresses changed, and loss of connectivity ensued.

My question: Should we create one large mobility group between the two buildings (multiple VLANs) OR should we reset every AP back to default (to wipe the known controllers list), ensure that AP's in each building only know about controllers in that same building, and keep the two separate mobility groups.

I am seeking advice since having one large mobility group would mean possible tunneling back over our gigabit connection between the primary and secondary buildings.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
beth-martin Thu, 05/24/2007 - 05:19
User Badges:
  • Bronze, 100 points or more

If you need to retain the ip address have single mobility group configured throughout.

ankbhasi Thu, 05/24/2007 - 05:59
User Badges:
  • Cisco Employee,

Hi Friend,

I will say the best use of wireless network is mobility and if you do not have mobility configured then even if you wipe the known controller lists and one controller goes down still your clients will loose connectivity.

But if you have mobility configured and have a large mobility group configured you can achieve roaming incase any disaster happens and you will retain same ip throughout. I understand that you are concerned with tunneling and mobility exchang emessages but all these exchange over gig link should not have much affect.



*Pls rate all helpfull post


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