Are you referring to configuring WLCs for redundancy. This is possible with mobility groups. A set of controllers can be configured as a mobility group to allow seamless client roaming within a group of controllers. By creating a mobility group, you can enable multiple controllers in a network to dynamically share information and forward data traffic when inter-controller or inter-subnet roaming occurs. Controllers can share the context and state of client devices and controller loading information. With this information, the network can support inter-controller wireless LAN roaming and controller redundancy. For more information on this read http://www.cisco.com/en/US/products/ps6305/products_configuration_guide_chapter09186a00806b7277.html#wp1098647
I have followed the example in your post and configured two WLCs to be in the same Mobility Group. I configured half of the access points to use the first WLC as primary and the second WLC as secondary. Then the other have be configured the opposite way. If one WLC is rebooted, all Access Points register with the one WLC. When the rebooted WLC back up, I expected that those Access Points that have primary pointing to the rebooted WLC automatically switch back to it.
This does not happen in our test. The Cisco documentation stated that it should happen if two WLC in the same Mobility group.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...