08-02-2013 08:31 AM - edited 07-04-2021 12:34 AM
According to the N+1 deployment guide, when the primary controller comes back up/online, the APs on the secundary (HA SKU) controllers should fallback to the primary. During my tests, this did not work. I enabled "AP Fallback" on both primary and secundary (HA SKU) controllers, but the APs remain on the secundary (while the primary was back online). Only after a boot of the secundary, did the APs go back to the primary. Is this normal ?
How long can it take for an AP to fallback ? I waited 10 minutes.
NOTE: the HA SKU is going to server multiple controllers, so he is not configured with the IP or name of any primary controller. I guess it is the AP itself that needs to remember what his primary controller was....
regards,
Geert
08-03-2013 05:53 AM
Hi,
- make sure AP SSO is disabled.
- configure backup controller on the primary. WLC GUI>Wireless>Access points>Global Config
- configure high availablity tab on the AP's
- made sure that the names of the WLC on the AP high availablity tab are identical "case sensitive"
08-05-2013 12:28 AM
see below
- make sure AP SSO is disabled.
>> checked and true
- configure backup controller on the primary. WLC GUI>Wireless>Access points>Global Config
>> is done
- configure high availablity tab on the AP's
- made sure that the names of the WLC on the AP high availablity tab are identical "case sensitive"
>> ha, this is interesting. Are you saying that i need to configure this tab on each and every AP for AP fallback to work ??
>> I thought configuring the global redundancy Wireless -> Global Config would be enough (backup primary controller)
regards,
Geert
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide