300-425 practice question 6 of 25

A customer has this wireless design: • two Cisco Catalyst 9800 Series wireless controllers that are configured in a high-availability SSO cluster to…

Full set: 286 questions

Domain WLAN High Availability

A customer has this wireless design: • two Cisco Catalyst 9800 Series wireless controllers that are configured in a high-availability SSO cluster to manage the APs in a local office network • 100 APs in local mode that are registered to the high-availability cluster • one Catalyst 9800 Series wireless controller that is deployed as an anchor in a DMZ • a CAPWAP tunnel in UP state between the high-availability cluster and the anchor WLC The customer wants the anchored traffic to remain up if a single WLC in the high-availability cluster fails. How must this requirement be incorporated into the design?
Answer options
A: Configure the APs with the high-availability cluster as the primary base.
B: Deploy EMC APs as anchors and configure a high-availability cluster.
C: Create a separate EoIP tunnel for each WLC in the high-availability cluster.
D: Configure the mobility MAC address for the high-availability cluster. Correct answer
Correct Answer:
D. Configure the mobility MAC address for the high-availability cluster.
Explanation

In a Cisco Catalyst 9800 High Availability (HA) Stateful Switchover (SSO) pair, a shared virtual MAC address, known as the Mobility MAC address, is used for all mobility communications. This MAC address, along with a shared virtual IP address, presents the HA cluster as a single logical controller to external peers, such as the anchor WLC. When a failover occurs, the standby controller becomes active and assumes this same Mobility MAC address. From the anchor controller's perspective, it is still communicating with the same entity, which allows the CAPWAP mobility tunnel to remain stable and anchored traffic to continue flowing without interruption.

Why Incorrect

A. This is a standard configuration for APs to join an HA cluster, ensuring AP and client connectivity during a failover, but it does not specifically address the resilience of the mobility tunnel to the anchor WLC.
B. Embedded Wireless Controller (EWC) APs are not designed to function as dedicated mobility anchors in an enterprise deployment of this scale; this suggests an incorrect network architecture.
C. Catalyst 9800 controllers use CAPWAP for mobility data tunnels, not the legacy EoIP. Creating separate tunnels would violate the single-entity principle of SSO and would not provide seamless failover.

References

1. Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide, Cisco IOS XE Bengaluru 17.6.x, "High Availability" Chapter: In the "Information About High Availability SSO" section, it states, "The active and standby WLCs in an HA pair share the same IP address and MAC address. This allows the connected APs and clients to continue to operate without being aware of a switchover." This shared identity is what the anchor WLC communicates with, ensuring tunnel stability. The MAC address used for mobility is specifically the Mobility MAC.

2. High Availability (SSO) Deployment Guide for Cisco Catalyst 9800 Series Wireless Controllers, "SSO Functionality" section: This guide details the mechanism: "The active and standby WLCs in an HA pair share the same IP address and MAC address... The HA pair uses a dedicated redundancy port to synchronize information... This includes bulk synchronization of the configuration and periodic synchronization of the dynamic state of the system." The synchronized state includes mobility tunnel information, which relies on the consistent MAC address for identification.

3. Mobility Configuration Guide, Cisco Catalyst 9800 Series Wireless Controllers, Cisco IOS XE Cupertino 17.9.x, "Configuring a Mobility Group" section: When configuring mobility, the controller is identified by its IP and MAC. The command show wireless mobility summary on a C9800 controller displays the "Mobility MAC Address," which is the source MAC address used in mobility control packets. In an HA SSO pair, this MAC is virtual and shared to ensure failover transparency for mobility peers.

Scroll to Top