350-401 · Question #389
A company has an existing Cisco 5520 HA cluster using SSO. An engineer deploys a new single Cisco Catalyst 9800 WLC to test new features. The engineer successfully configures a mobility tunnel between
The correct answer is B. mobility MAC on the 9800 WLC. The issue of clients failing to roam after a 5520 WLC failover indicates the 9800 WLC does not recognize the secondary 5520 as a mobility peer, requiring its mobility MAC address to be configured on the 9800.
Question
Options
- Amobility MAC on the 5520 cluster
- Bmobility MAC on the 9800 WLC
- Cnew mobility on the 5520 cluster
- Dnew mobility on the 9800 WLC
How the community answered
(26 responses)- A19% (5)
- B69% (18)
- C4% (1)
- D8% (2)
Why each option
The issue of clients failing to roam after a 5520 WLC failover indicates the 9800 WLC does not recognize the secondary 5520 as a mobility peer, requiring its mobility MAC address to be configured on the 9800.
Configuring the mobility MAC on the 5520 cluster itself is not the corrective action from the perspective of the 9800 WLC needing to recognize the failover target.
When the primary 5520 WLC fails and the secondary takes over, the 9800 WLC must be configured with the mobility MAC address of the secondary 5520 WLC to correctly establish a mobility tunnel to the new active controller, enabling seamless roaming post-failover.
New mobility is the feature that allows communication, and the question states it was successfully configured, meaning the fundamental feature is in place but a specific configuration for HA is missing.
New mobility is configured on the 9800 WLC, but the specific problem after failover points to a missing peer entry for the secondary WLC's MAC, not a complete lack of new mobility on the 9800.
Concept tested: WLC mobility group HA configuration
Source: https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_wl_16_10_cg/m_new_mobility.html
Topics
Community Discussion
No community discussion yet for this question.