Two cisco 5520 wireless LAN controllers are managing all access points throughout the network. The WLCs are in different locations to provide geographical redundancy a mobility group has been configured on both WLCs and has a UP status on both controllers. The Aps in location A are statically configured to use controller A as the primary and controller B as the secondary. If the WLC in location A goes offline. The Aps successfully join the WLC in location, but they do not fail over to their primary configured controller. Which configuration task fixes the issue?
Seen this in some practice labs, enabling AP fallback globally on the WLC (so C) is necessary for APs to automatically return to their primary controller after a failover. Just setting priorities or using DHCP options won’t trigger the fallback. If you’re prepping, official Cisco guides and lab practice really help clarify these controller behaviors. Pretty sure about C but let me know if someone has had different results.
I don't think D really solves the fallback issue here. Setting AP failover priority changes how APs pick a controller during a failover, but it doesn't make them return to their primary when it comes back up. That feature is controlled by enabling AP fallback globally (C). Seen similar question in practice materials, so I'm pretty sure that's what Cisco wants. Anyone get different results on real gear?
