It collects information about the switch hardware is something that NetEdit 2.0 does after it discovers a switch. NetEdit 2.0 is a tool that provides configuration management and validation for ArubaOS-CX and ArubaOS-Switch devices. NetEdit 2.0 can discover switches using various methods such as IP range scan, LLDP scan, CSV import, etc.  After NetEdit 2.0 discovers a switch, it collects information about the switch hardware such as model number, serial number, MAC address, firmware version, etc 1 .

The wait to restore timer (WTR) Is set in units of minutes; you can set it to prevent frequent topology changes due to a link going up and down is a guideline for configuring timers for Ethernet Ring Protection Switching (ERPS) on an ArubaOS-CX switch.  The WTR timer is set in units of minutes, and it defines how long a node must wait before restoring traffic on a previously failed link that has recovered 1 .

The ISL and keepalive goes down, and after a few seconds, the keepalive link restores. Switch-1 and Switch-2 remains up. The Split-recovery mode is enabled. In this case the secondary switch shutdowns SVIs when keepalive is restored is 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 ISL and keepalive goes down, both VSX nodes continue to forward traffic independently.  When the keepalive link restores, the secondary switch detects that it has lost synchronization with the primary switch and shuts down its SVIs to prevent traffic loops 1 .

ERPS is a feature of ArubaOS-CX that prevents loops at layer 2 on ring networks 1 .  ERPS uses a protocol called Ring Auto Protection Switching (RAPS) to detect link failures and perform fast traffic switchover 1 .  ERPS supports multiple rings and multiple instances per ring 1 .  Each instance has a control VLAN and one or more protected VLANs 1 .  The control VLAN carries the RAPS PDUs and must be unique per ring 1 .  The protected VLANs are the user traffic VLANs that are protected by ERPS and must be unique per instance 1 . Based on the exhibit, the design for the control and protected VLANs on the VSX fabric 1 switches is not valid.  The control VLAN 51 is used for both instances 1 and 2 on ring 1, which violates the rule that the control VLAN must be unique per ring 1 .  The protected VLANs 51-100 and 101-150 are also overlapping with the control VLAN 51, which violates the rule that the protected VLANs must be unique per instance 1 . Therefore, this is not a valid design for the control and protected VLANs on the VSX fabric 1 switches, and the correct answer is no.  For more information on ERPS and VLANs, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet 2  and the ERPS Guide for your switch model 1 .

With the exception of a single strict priority queue, all queues must use the same scheduling algorithm is a rule for configuring schedule profiles on an ArubaOS-CX switch. A schedule profile defines how traffic is scheduled across different queues on an interface. Each queue can have one of three scheduling algorithms: strict priority (SP), weighted round robin (WRR), or weighted fair queuing (WFQ).  However, only one queue can have SP, and all other queues must have either WRR or WFQ 1 .

Virtual Switching Extension (VSX) is a high-availability technology that allows two ArubaOS-CX switches to operate as a single logical device. VSX Inter-Switch Link (ISL) is a link between the two VSX switches that is used for both data plane and control plane traffic.  It is not recommended to reserve the ISL for control plane traffic only, as this would limit the benefits of VSX and create suboptimal traffic forwarding 1 . Therefore, this is not a valid guideline for establishing a VSX ISL between two ArubaOS-CX switches.

Priority Flow Control (PFC) is a feature of ArubaOS-CX that eliminates packet loss due to congestion on a network link 1 .  PFC uses IEEE 802.1Qbb standard to pause traffic on a per-priority basis 1 .  PFC can be configured to operate in symmetric or asymmetric mode 1 .  Symmetric mode applies PFC to both the receiving and sending of pause frames 1 .  Asymmetric mode applies PFC to either the receiving or sending of pause frames 1 .  To configure PFC on an interface, you need to enable flow control with a priority value and configure a DCBX application priority on the interface 1 .  A DCBX application priority maps a traffic class to a priority group and enables the switch to negotiate PFC parameters with the peer device 1 . Therefore, this is a requirement for implementing PFC on an ArubaOS-CX switch interface, and the correct answer is yes.  For more information on PFC and DCBX, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet 2  and the QoS Guide for your switch model 1 .

The exhibit shows a network topology where Switch-1 and Switch-2 are part of a Virtual Switching Extension (VSX) fabric, and the router runs OSPF on LAG 100, which is a Layer 3 LAG. The question asks how to control how core-to-access traffic is forwarded, which means how the router chooses between the two links to Switch-1 and Switch-2. To force the router to use both links, ensuring that active gateway is enabled on LAG 100 on both Switch-1 and Switch-2 is not the correct solution. Active gateway is a feature that allows both VSX members to act as the default gateway for downstream devices, using a common virtual MAC address.  Active gateway does not affect how upstream devices, such as the router, forward traffic to the VSX members 1 . To force the router to use both links, the correct solution is to configure equal-cost multi-path (ECMP) in OSPF on the router. ECMP is a feature that allows a router to load balance traffic across multiple paths with the same cost.  ECMP can be configured using the maximum-paths command and specifying how many equal-cost paths the router should use 2 . Therefore, this does not correctly explain how to control how core-to-access traffic is forwarded.

VSX features a dual control plane while VSF features a single control plane.  VSX and VSF are both high availability solutions that provide redundancy and load balancing across a pair of switches 1 .  However, VSX features a dual control plane, which means that each switch has its own independent configuration and state information 1 .  VSF features a single control plane, which means that one switch acts as the commander and synchronizes the configuration and state information to the other switch 1 . The statement is true because it correctly describes the difference between VSX and VSF control planes.

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 .