WLC Controllers

Unanswered Question
Apr 1st, 2009
User Badges:

I have 2 controller environment. When I set the primary and secondary controller on a ap through the GUI, the ap doesn't move to the primary. I've set the mobility groups a couple of times.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Leo Laohoo Wed, 04/01/2009 - 22:54
User Badges:
  • Super Gold, 25000 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 LAN, Wireless

Depends on the firmware. Firmwares <5.0 (3.x & 4.x) have a bug where this option simply won't work. You'll have to set this option using CLI with the following command:

config ap primary-base controller_name ap_name controller_management_ip_address

runningboy01 Wed, 04/08/2009 - 11:19
User Badges:

Also, once you assign the primary and secondary controllers, you need to reboot the AP in order for it to join the appropriate controller.

jeff.kish Wed, 04/08/2009 - 12:35
User Badges:
  • Silver, 250 points or more

Or you can use the AP Fallback mode, found under the Controller tab in the web GUI. This causes APs to disconnect as soon as their primary controller is found to be up.

This is convenient because it fixes your AP distribution in case a controller gets reset, but it has the potential of causing issues if a controller is flopping (though I've never seen this).

runningboy01 Thu, 04/09/2009 - 07:18
User Badges:


From what I've seen with AP Fallback enabled is this:

If one controller crashes or reboots, the APs from that controller will go to the other controller that is set as their Secondary. However, once the crashed controller comes back the APs will not disconnect from the secondary and jump back to the Primary. I've found the only way to do this is to reset the APs. From what I have seen, AP Fallback mode is nice, but it doesn't seem to make the APs go back to their Primary controller.


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