Aruba Data Center Network Specialist

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 member 1. 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 members 1. Therefore, this is a valid use case for disabling split-recovery mode on ArubaOS-CX switches in a VSX fabric.

NetEdit is a network management tool that allows you to configure, monitor, and troubleshoot ArubaOS-CX switches. You can use NetEdit to deploy a standard config to the switches, but you need to use a different feature than conformance validation tests. Conformance validation tests are used to check if the switches comply with a predefined set of rules or best practices, and to generate reports or alerts if any deviations are found 1. They are not used to deploy configurations. To deploy a standard config that includes device-specific settings, you should use templates. Templates are files that contain configuration commands with variables that can be replaced with device-specific values when applied to the switches 1. Therefore, this is not what you should do.

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 1.

Implementing Virtual Switching Extension (VSX) on pairs of ERPS switches at the same site is part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection Switching (ERPS) solution. VSX allows two switches to act as a single logical device and provide active-active forwarding across both switches. This way, traffic can be load balanced across all links in the ERPS ring without creating loops 1.

The exhibit shows a network topology where Switch-1 and Switch-2 are ArubaOS-CX switches that implement VXLAN without Ethernet VPN (EVPN). Switch-2 uses the same VNI-to-VLAN mappings as Switch-1. The question asks how the specified servers communicate, which means Server 1 and Server 4.
Server 1 and Server 4 are in different VLANs and different VNIs, which means they are in different layer 2 segments. To communicate with each other, they require routing services between the VXLANs. However, using Virtual Routing and Forwarding (VRF) to tunnel iSCSI traffic through the network spine on the same links that data traffic uses is not the correct way to provide routing services. VRF is a technology that creates multiple isolated Layer 3 domains on a physical network, each with its own routing table. VRF does not provide any benefits for iSCSI traffic, as it does not guarantee bandwidth, priority, or quality of service.
VRF also adds overhead and complexity to the network configuration 1. To provide routing services between the VXLANs, the correct way is to use VXLAN routing with EVPN or distributed anycast gateway (DAG). VXLAN routing with EVPN allows the switches to exchange MAC and IP information using BGP EVPN control plane, and to perform routing between different VNIs using a centralized or distributed model 2. DAG allows the switches to act as anycast gateways for their local hosts, and to route traffic between different VNIs using a symmetric or asymmetric model 3. Therefore, this does not correctly describe how the specified servers communicate.

VSX permits admins to select which features to synchronize between members while VSF requires manual configuration of identical features on each member of the VSF fabric is a way that Virtual Switching Extension (VSX) differs from Virtual Switching Framework (VSF). VSX is a feature that provides active-active forwarding and redundancy for ArubaOS-CX switches. VSF is a feature that provides active-standby forwarding and redundancy for legacy campus switches. VSX allows admins to select which features to synchronize between members using an opt-in model, while VSF requires manual configuration of identical features on each member using a commander-member model 1.

In the Enhanced Transmission Selection (ETS) Local advertisement section is not where you can see whether the connected converged network adapter (CNA) has accepted the application priorities advertised with DCBX on an ArubaOS-CX switch interface. The ETS Local advertisement section shows the priority groups and bandwidth allocation that the switch advertises to the CNA, but it does not show whether the CNA has accepted them or not. To see whether the CNA has accepted the application priorities advertised with DCBX, you need to look at the Application Priority Local advertisement section, which shows the application protocol identifier (APPID) and priority values that the switch advertises to the CNA, and compare them with the Application Priority Remote advertisement section, which shows the APPID and priority values that the CNA advertises to the switch 1.

Both ARP-Suppression and ND-Suppression are disabled by default is not a true statement about ARP and ND Suppression. ARP-Suppression is enabled by default on ArubaOS-CX switches, while ND-
Suppression is disabled by default 1. ARP-Suppression and ND-Suppression are features that reduce broadcast traffic on VXLAN networks by using a local ARP/ND cache on each switch instead of flooding ARP/ND requests to all VXLAN tunnel endpoints (VTEPs)1.

Ring 1, instance 1: control VLAN: 1000protected VLANs: 51-135 Ring 1,Instance2: control VLAN: 1001 protected VLANs: 136-220 Ring 2, Instance 1: control VLAN: 1000 protected VLANs: 181 -200 Ring 2,
Instance 2: control VLAN: 1003 protected VLANs: 201 -220 is not a valid design for the control and protected VLANs on the VSX fabric 1 switches for an Ethernet Ring Protection Switching (ERPS) solution.
The control VLANs must be unique for each ring instance and must not overlap with any protected VLANs.
In this design, the control VLAN 1000 is used for both ring 1 instance 1 and ring 2 instance 1, which can cause conflicts and errors. Also, the protected VLANs 181-220 are used for both ring instances on ring 2, which can cause loops and traffic duplication 2.

The IPv6 and IPv4 overlay networks can be encapsulated with VXLAN and transmitted through the underlay network is a true statement about EVPN and IPv6 for configuring an EVPN solution for a dual-stack IPv4 and IPv6 protocol in the overlay networks. VXLAN is a feature that provides Layer 2 extension over Layer 3 networks using UDP encapsulation. VXLAN can support both IPv4 and IPv6 overlay networks over an IPv4 or IPv6 underlay network 2.