300-425 practice question 17 of 25

Based on a wireless network design, an engineer configured a primary and secondary controller for their APs. A power interruption caused the primary…

Full set: 286 questions

Domain WLAN High Availability

Based on a wireless network design, an engineer configured a primary and secondary controller for their APs. A power interruption caused the primary Cisco WLC to go down, and, as expected, all APs joined the secondary controller. When the primary controller came back up, all the APs remained joined to the secondary controller. Which approach must the engineer take for the APs to move back to the primary?
Answer options
A: Set AP Fail over Priority to 4 on each AP.
B: Set AP Fallback to Enabled on the secondary controller. Correct answer
C: Set AP Fallback to Enabled on the primary controller.
D: Set AP Fail over Priority to Critical globally.
Correct Answer:
B. Set AP Fallback to Enabled on the secondary controller.
Explanation

The AP Fallback feature controls whether an access point, after failing over to a secondary or tertiary controller, will attempt to return to its primary controller once it becomes available again. This feature is disabled by default. For the APs to move back to the primary controller, the AP Fallback feature must be enabled on the controller to which they are currently joined. In this scenario, the APs have failed over and are connected to the secondary controller. Therefore, the secondary controller must be configured to enable AP Fallback, which will then instruct the joined APs to revert to their primary controller when it is detected on the network.

Why Incorrect

A. Set AP Fail over Priority to 4 on each AP. AP Failover Priority is used to manage which APs are disconnected when a controller reaches its maximum AP capacity. It does not control the fallback behavior.
C. Set AP Fallback to Enabled on the primary controller. The fallback setting is effective on the controller the AP is currently joined to (the secondary). The primary controller has no influence over the APs until they rejoin it.
D. Set AP Fail over Priority to Critical globally. This setting, like option A, relates to controller AP capacity management during failover events, not the process of an AP returning to its primary controller after a failover. ---

References

1. Cisco Wireless LAN Controller Configuration Guide

Release 8.5

"Configuring High Availability" chapter

"Configuring AP Fallback" section.

"By default

the fallback feature is disabled. If you enable it

the access point falls back to the primary controller as soon as it comes back online... You can enable or disable the AP fallback feature globally for all access points joined to the controller..." This confirms the feature must be enabled on the controller the APs are currently joined to (the secondary).

2. Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide

Cisco IOS XE Bengaluru 17.6.x

"High Availability" chapter

"AP Failover" section.

"AP fallback is a feature where an AP that has failed over to a secondary or tertiary C9800 WLC will fall back to the primary C9800 WLC when it becomes available again. This feature is disabled by default. You can enable it globally on the C9800 WLC." This documentation for a newer platform confirms the same principle: the setting is applied to the controller managing the AP post-failover.

3. Cisco Wireless LAN Controller Configuration Guide

Release 8.5

"Configuring High Availability" chapter

"Configuring AP Failover Priority" section.

"You can configure the failover priority for access points. The failover priority is used when the number of access points associated to the controller exceeds the controller's AP capacity... The controller disassociates the access points with the lowest priority." This source clarifies that AP Failover Priority is for capacity management

making options A and D incorrect.

Scroll to Top