A customer has a pair of Cisco 5520 WLCs set up in an SSO cluster to manage all APs. Guest traffic is anchored to a Cisco 3504 WLC located in a DMZ. Which action is needed to ensure that the EoIP tunn

Question

Options

• AUse the mobility MAC when the mobility peer is configured
• BUse the same mobility domain on all WLCs
• CEnable default gateway reachability check
• DConfigure back-to-back connectivity on the RP ports

• A
  79% (27)
• B
  6% (2)
• C
  3% (1)
• D
  12% (4)

Explanation

SSO Cluster EoIP Tunnel Failover Explanation

In an SSO (Stateful Switchover) cluster, the two Cisco 5520 WLCs share a single mobility MAC address (as opposed to their individual chassis MACs). When configuring the mobility peer relationship with the anchor WLC (3504 in the DMZ), you must use this mobility MAC rather than the physical MAC of either controller - this ensures the EoIP tunnel stays UP during failover because the anchor WLC still sees the same peer identity regardless of which 5520 takes the active role.

Why the distractors are wrong:

• B (Same mobility domain): While all WLCs should share the same mobility domain for guest anchoring to work, this alone doesn't address the tunnel surviving an SSO failover event.
• C (Default gateway reachability check): This feature monitors upstream connectivity but doesn't directly maintain the EoIP tunnel identity across an SSO switchover.
• D (Back-to-back RP ports): The Redundancy Port (RP) connection is required for SSO operation itself, but configuring it doesn't resolve the mobility peer identity issue with the anchor WLC.

Memory Tip: Think "SSO = One Face" - the SSO cluster presents a single mobility MAC to the outside world, so always configure mobility peers using that shared identity, not the individual controller MACs.

No community discussion yet for this question.