Is this a use case for disabling split-recovery mode on ArubaOS-CX switches in a Virtual Switching Extension (VSX) fabric? Solution: You want an admin to manually fail traffic over to the secondary member if the primary member fails.

Is this a use case for disabling split-recovery mode on ArubaOS-CX switches in a Virtual Switching Extension (VSX) fabric? Solution: You want an admin to manually fail traffic over to the secondary member if the primary member fails.
A . Yes
B. No

View Answer

Answer: A

Explanation:

Virtual Switching Extension (VSX) is a high-availability technology that allows two ArubaOS-CX switches to operate as a single logical device. Split-recovery mode is a feature that prevents traffic loss when the Inter-Switch Link (ISL) goes out-of-sync and keepalive subsequently fails. When split-recovery mode is enabled, the secondary VSX member disables its downstream links until it synchronizes with the primary member. When split-recovery mode is disabled, the secondary VSX member keeps its downstream links up even when it is out-of-sync with the primary member1. Disabling split-recovery mode is a use case for situations where you want an admin to manually fail traffic over to the secondary member if the primary member fails. This can be useful for planned maintenance or testing purposes, where you want to avoid automatic failover and failback of traffic. To manually fail traffic over to the secondary member, you need to shut down the ISL on both VSX members1. Therefore, this is a valid use case for disabling split-recovery mode on ArubaOS-CX switches in a VSX fabric.