Examine the attached diagram -
Two AOS-CX switches are configured for VSX at the access layer, where servers attached to them. An SVI interface is configured for VLAN 10 and serves as the default gateway for VLAN 10. The ISL link between the switches fails, but the keepalive interface functions. Active gateway has been configured on the switches.
What is correct about access from the servers to the Core?
When the ISL (Inter-Switch Link) fails but the keepalive interface is still operational, the secondary switch disables all of its aggregate interfaces. This ensures that split-brain scenarios are avoided, where both switches could potentially forward traffic simultaneously, leading to inconsistencies. Consequently, Server 2 cannot access the core layer as its connection relies on the aggregate interfaces, which would be disabled on the secondary switch. Server 1 retains access to the core layer via the primary switch's uplink. Therefore, Server 2 is isolated from the core layer.
when only ISL is down and peer-keepalive is up the VSX secondary switch disable all his agregate interfaces, so server 2 is isolated. His ports is stil up but there is no connection to the core.
The answer is C. If the ISL link breaks, the multi-chassis LAGs links on the VXS pair will no longer work on the second member. Server 2 will therefore be isolated
D = no, as the link to the secondary peer is deactivated in the case of an MC-LAG, the two VSX peers should no longer see each other. C = why not? This is a normal link, which remains even if the two VSX peers are interrupted. A = Keepalive link only sends "hellos" back and forth between the VSX nodes to detect a split brain. Consequently, it must be B.
Must be C, When ISL is down and KA is up ALL VSX-MC are shutdown from the secondary switch.
I go for B. A: keepalive is only for hellos B: Server 1 traffic travelns via Primary to Core to Secondary to Server 2 C: When ISL fails, LAG interfaces are shut down; not the access ports, to which devices are connected to D: Uplink to Secondary is shut down because of ISL fail. So it is not correct. https://www.arubanetworks.com/techdocs/AOS-CX/10.10/HTML/vsx/Content/Chp_TS/fai-sce-spl-rec.htm
During ISL cut, if the VSX Secondary node has a port that is a member of a VSX LAG then the associated SVI of the VLAN transported by the said VSX LAG is turned OFF/SHUT on the VSX Secondary node, whether or not there is an orphan port carrying that given VLAN. Hence the SVI is down on the secondary, and server 2 is disconnected
Answer C. Ater an ISL failure, ports and SVI associated to a VSX LAG automatically turned off (shutdown), ports and SVIs not related to and VSX LAG still operating. In this case, server 2 and VLAN 10 are still operating, but since there are no external uplinks and routes, server 2 is isolated.
I vote C - the question states the SVI has Active-Gateway configured, therefore must be on the VSX pair, also, uplink to the core is a MC-LAG and will be shut down.
C https://www.arubanetworks.com/techdocs/AOS-CX/10.11/HTML/vsx/Content/Chp_TS/tra-los-whe-isl-out-of-syn-kee-dow-10.htm Traffic loss after the ISL has been out-of-sync and keepalive is down Symptom Traffic loss is seen after the ISL has been out-of-sync and keepalive is down. Cause If the ISL becomes out-of-sync and keepalive is established, the secondary VSX LAGs are brought down. If keepalive then fails and you have split recovery mode enabled (default setting), the secondary switch brings up its VSX LAGs.