Question 920
At Bayside Campus, a distribution migration places a downstream MC-LAG into different VSX LAG identifiers on each peer. Which implementation directly addresses this campus fault without replacing the wrong component?
Explanation
Correct Answer
For Bayside Campus, the decisive mechanism is VSX MC-LAG. MC-LAG provides one downstream LAG across two independently managed VSX peers. Configure a supported VSX multi-chassis LAG with consistent LACP identity and peer link state establishes the needed configuration in the case rather than merely measuring a symptom.
Incorrect Answers
This is relevant to AOS 10 gateway cluster, where an AOS 10 gateway cluster improves tunneled WLAN availability but still needs correct forwarding and policy In the Bayside Campus case, Changing that neighboring feature does not implement the missing function. The specific mechanism is mC-LAG provides one downstream LAG across two independently managed VSX peers
This is relevant to Loop protection, where loop detection complements STP by containing accidental edge loops In the Bayside Campus case, Changing that neighboring feature does not implement the missing function. The specific mechanism is mC-LAG provides one downstream LAG across two independently managed VSX peers
This is relevant to VRRP redundant gateway, where VRRP supplies virtual first-hop gateway failover between eligible routing peers In the Bayside Campus case, Changing that neighboring feature does not implement the missing function. The specific mechanism is mC-LAG provides one downstream LAG across two independently managed VSX peers