Moving APs to controller in different Mobility Group

Unanswered Question
Jul 10th, 2008
User Badges:
  • Silver, 250 points or more


Project roll out question here. We have an existing environment with 4400 series controller and 1130 LAPs.

To provide Internet access for guests we have a guest wifi that hands of traffic in one of our datacenters.

Since usage is rapidly growing we are adding a set of controllers in a second datacenter, using a second mobility group (so far this sense I hope).

Now, I need to move the existing LAPs in one region to the new installed controllers in the new mobility group. I tried one by just changing the primary contrller but it keeps registering to one of the controllers in the first mobility group.

Anyone can shine a light on how to approach this. I need to move appr. 40 LAPs and 2 controller to the new mobility group (meaning changing them and leaving others in).

Thanks in advance,


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Richard Atkin Thu, 07/10/2008 - 07:25
User Badges:
  • Silver, 250 points or more

Easiest way is probably to put all controllers in the same mobility group, and get the APs on the controllers you want, assign primary, secondary controllers (etc) then change the Mobility Group of two of the Controllers, breaking the link and creating your two domains. The APs will stay on whatever controller they're on.

l.mourits Sun, 07/13/2008 - 23:25
User Badges:
  • Silver, 250 points or more

Thanks, that is what I thought should be the best way. It makes me wonder though. Does the LAP save the mobility group info locally then?

Scott Fella Mon, 07/14/2008 - 03:32
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

Yes. The LAP's will know of the other WLC via the mobility group information and does store that locally. Here is from a Cisco doc:

When the AP boots or resets, it only knows the controller management IP addresses from DNS ([email protected] (20 max), DHCP option 43 (20 max), OTAP,, and the previously joined controller. The controllers in the mobility group of the previously joined controller are not retained across reboots.


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