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?
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!
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.