AP will only associate with ONE controller

Unanswered Question
Dec 28th, 2007
User Badges:

We have 4 WiSM controllers; one of which is defined as the the Master Controller.

After APs have joined the Master Controller, we have changed some of them to use another controller as their primary controller. Even though the WCS shows these APs as having a different primary controller, ALL our APs are still associated with the one controller.

This persists despite rebooting the APs, and we can now no longer add any new APs to our wireless LWAPP network.

How do we get the APs to actually associate with their defined primary controller?


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Rob Huffman Fri, 12/28/2007 - 13:33
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Lynne,

Can you please try disabling the "Master Controller Mode" and then rebooting the AP's.

There are some good tips in this doc;


Hope this helps!


dancampb Sat, 12/29/2007 - 09:00
User Badges:
  • Cisco Employee,

Make sure the controllers are in the same mobility group. When defining the primary/secondary controller the AP will only move if the controllers are in the same mobility group.

kfccolonel Fri, 01/04/2008 - 18:43
User Badges:

You can usually get stubborn LAP's to move by defining in DNS the standard CISCO LWAPP CONTROLLER dns entry and pointing it to the controller you want the LAP to move to. Then reboot the LAP.

Once it moves, it will usually follow the primary/secondary settings it has.

I then remove the DNS entry.

I have found that sometimes, LAP's just won't go to the primary controller defined in the setup unless I use that DNS entry.

lynne.meeks Mon, 01/07/2008 - 09:42
User Badges:

Well, that turned out to be part of the answer.

We ended up adding ALL the controllers in DNS so a query for the CISCO LWAPP CONTROLLER returns all 4 IPs.

We also had to configure the mobility group on each controller. Even though I had changed these from the WCS, and the WCS shows the mobility group information as it should be -- the change on the WCS didn't 'take'; I had to make the mobility group changes on each controller.

It is not terribly obvious to me when one can make changes on the WCS and when you need to make the changes on the controllers-- seems to me that if the WCS allows you the option to configure the controllers it should really do it!

Thanks all for your assistance.

cchandler63 Wed, 01/09/2008 - 15:52
User Badges:

I'm curious when you added multiple DNS entries have the AP's then landed on their local controller or the first IP address for this DNS entry.

lynne.meeks Thu, 01/10/2008 - 05:09
User Badges:

The APs will associate with whichever controller we have specified as their primary controller.

We are currently having some issues with being able to actually change the primary controller on some APs, however. We connect to the AP and change the primary controller, and then apply the change. This seems to work; there are no errors - but when we check back the change hasn't 'stuck', and they still list the original controller as their primary controller, not the one we changed it to.

This only happens to a few APs which were associated with one particular controller that seems to have some issues.

That issue aside, the APs are associating with the primary controller they are configured with.


cchandler63 Wed, 01/09/2008 - 15:53
User Badges:

This too has been the only effective way I've been able to get stubborn AP's back on their primary controller. I'm wondering if anyone has had better luck with the option 43?


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