Q: 2
During a wireless design all APs are mapped to designated controllers in case of a failure. The
controllers are located in the same data center but in different racks. An AP failed over to a controller
that was not defined on its High Availability tab. The customer does not want the AP to move back to
its defined Cisco WLCs until they manually intervene. What needs to be addressed in the design?
Options
Discussion
Option B. Was it specifically asked for the AP not to revert automatically, or would auto-fallback be preferred if the original controller becomes available? That would change if A or B is correct here, since fallback setting is key.
Probably B
Yeah, you need B for manual AP return. Fallback enabled (A) would move them back automatically.
B , disabling AP fallback is what keeps the AP on the backup controller until someone manually moves it back.
B, not A
B tbh, fallback enabled (A) would force APs back to their WLC, which isn't what the customer wants.
B. that's what I've seen on similar practice. Official guide spells out the fallback settings for manual intervention situations.
Nah, I think B is correct. A is a trap since fallback enabled would auto-return the AP.
C , since changing the secondary HA unit sounds like it could control failover behavior.
I don’t think it’s A in this scenario. Since the customer wants to avoid automatic switchover, B is the way to go. Setting AP fallback to disabled keeps the AP on the new WLC until someone moves it manually. Pretty sure that’s how Cisco handles this, but always worth double-checking controller settings.
Be respectful. No spam.
