Does this correctly describe how the Virtual Switching Extension (VSX) fabric reacts to various component failure scenarios?
Solution: The ISL goes down, and after a few seconds, the keepalive link goes down too. Switch-
1 and Switch-2 remains up.
The Split-recovery mode is enabled. In this case the secondary switch first shutdowns and then enables SVis.
Is this a way that a data center technology can help meet requirements for multi-tenancy?
Solution: Virtual Extensible LAN (VXLAN) provides millions of IDs to scale for the needs of a multi-tenant environment
Is this a use case for disabling split-recovery mode on ArubaOS-CX switches in a Virtual Switching Extension (VSX) fabric?
Solution: You want to prevent any possibility of a split brain situation from occurring if the keepalive link fails some time after the ISL.
Is this how you should position switches in the ArubaOS-CX portfolio tor data center networks?
Solution: Deploy Aruba CX 8400 switches as core switches for very large three-tier data center networks.
Can you attach this type of ArubaOS-CX interface to a VRF?
Solution: A Layer 3 VLAN interface