HPE2-W09 · Question #126
Does this correctly describe how the Virtual Switching Extension (VSX) fabric reacts to various component failure scenarios? Solution: The keepalive goes down, ISL link remains up. Switch-1 and…
The correct answer is B. No. The keepalive goes down, ISL link remains up. Switch-1 and Switch-2 remains up. The Split- recovery mode is disabled. In this case the secondary switch shutdowns SVIs is not a correct description of how the Virtual Switching Extension (VSX) fabric reacts to various component…
Question
Does this correctly describe how the Virtual Switching Extension (VSX) fabric reacts to various component failure scenarios? Solution: The keepalive goes down, ISL link remains up. Switch-1 and Switch-2 remains up. The Split-recovery mode is disabled. In this case the secondary switch shutdowns Svls.
Options
- AYes
- BNo
How the community answered
(19 responses)- A21% (4)
- B79% (15)
Explanation
The keepalive goes down, ISL link remains up. Switch-1 and Switch-2 remains up. The Split- recovery mode is disabled. In this case the secondary switch shutdowns SVIs is not a correct description of how the Virtual Switching Extension (VSX) fabric reacts to various component failure scenarios. VSX is a feature that provides active-active forwarding and redundancy for ArubaOS-CX switches. The ISL is the inter-switch link that connects two VSX nodes and carries data traffic. The keepalive link is a separate link that carries control traffic between two VSX nodes. The split-recovery mode is a feature that prevents split-brain scenarios when both VSX nodes lose connectivity with each other but remain up. When the keepalive goes down, but the ISL link remains up, both VSX nodes continue to forward traffic normally and do not shut down their SVIs because they can still exchange synchronization messages over the ISL link.
Topics
Community Discussion
No community discussion yet for this question.