HP HPE2-W09 Practice Test - Questions Answers, Page 11

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 splitrecovery 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 does not affect how the primary switch waits a period before it takes over as the primary switch after a failure and reboot. The primary switch always takes over as the primary switch immediately when it comes back online, regardless of the split-recovery mode setting. To make the primary switch wait a period before it takes over as the primary switch, you need to configure a preemption delay on both VSX members1. Therefore, this is not a use case for disabling split-recovery mode on ArubaOS-CX switches in a VSX fabric.

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

Split-recovery mode is a feature of ArubaOS-CX that prevents traffic loss when the ISL goes out-ofsync and keepalive subsequently fails12. This can happen if the ISL is restored after a failure but the VSX nodes are not synchronized. Split-recovery mode enables the secondary switch to restore its VSX LAGs after 10 keepalive packets are missed, approximately 10 seconds after keepalive goes down2. This avoids a split brain situation where both switches act as primary and forward traffic independently, causing loops and duplicate packets1. Therefore, disabling split-recovery mode is not a use case for preventing split brain situations, and the correct answer is yes. For more information on split-recovery mode and VSX, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet3 and the Virtual Switching Extension (VSX) Guide for your switch model2.

Deploying Aruba CX 8400 switches as core switches for very large three-tier data center networks is how you should position switches in the ArubaOS-CX portfolio for data center networks. ArubaOS-CX is an operating system that provides advanced features and automation capabilities for data center networks1. It runs on various switch models that are designed for different roles and scenarios in the data center1. Aruba CX 8400 switches are modular switches that offer high performance, scalability, and reliability for the core layer of very large three-tier data center networks1. The statement is true because it correctly describes how to position Aruba CX 8400 switches in the ArubaOS-CX portfolio for data center networks.

Enhanced Transmission Selection (ETS) is a network scheduling algorithm that allows the switch to assign different priority and bandwidth values to different traffic classes1. This can be useful for transmitting traffic to servers that have different requirements for latency, jitter, or throughput. For example, ETS can prioritize voice or video traffic over data traffic, or allocate more bandwidth to backup or replication traffic. ETS is configured using the Data Center Bridging Exchange (DCBx) protocol, which advertises the configuration to peer devices2. Therefore, implementing ETS on an ArubaOS-CX switch is a valid use case for enabling the switch to assign the correct priority and bandwidth to traffic that it transmits to servers.

VXLAN is a tunneling protocol that encapsulates layer 2 traffic over an IP network using VXLAN Network Identifiers (VNIs) to identify different layer 2 segments. VXLAN Tunnel Endpoints (VTEPs) are devices that perform the encapsulation and decapsulation of VXLAN packets. VTEPs can use different methods to handle broadcast, unknown unicast, and multicast (BUM) traffic within a VNI. One of these methods is headend replication, which means that the VTEP that receives a BUM packet replicates it and sends it as a unicast to each remote VTEP in the same VNI1. This method does not require multicast routing in the underlay network, but it can increase the load on the ingress VTEP. Therefore, this correctly describes how the VTEPs handle VXLAN traffic forwarding without EVPN.

A schedule profile is a feature of ArubaOS-CX that determines the order and service of queues for transmission123. A schedule profile must be configured on every interface at all times23. The switch supports three scheduling algorithms: Guaranteed Minimum Bandwidth (GMB), Strict, and Strict EQS23. Strict scheduling gives absolute priority to a queue over other queues, regardless of the bandwidth allocation23. If the profile mixes strict priority scheduling with another scheduling algorithm, the strict priority queue must be the highest numbered queue23. Therefore, this is a rule for configuring schedule profiles on an ArubaOS-CX switch, and the correct answer is yes. For more information on schedule profiles and QoS, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet1 and the QoS Guide for your switch model23.

VXLAN is a feature of ArubaOS-CX that provides layer 2 connectivity between networks across an IP network1. VXLAN uses a 24-bit identifier called VXLAN Network Identifier (VNI) to segment the layer 2 domain1. VXLAN also uses a tunnel endpoint (VTEP) to encapsulate and decapsulate VXLAN packets1. A VXLAN interface is a logical interface that represents a VNI and is associated with a source IP address and a VRF1. To set up VXLAN without EVPN, you need to create VXLAN interfaces on each switch and configure static VTEP peers1. Based on the exhibit, Switch-1 needs to create two VXLAN interfaces, one with ID 5010 and one with ID 5020, to match the VNIs of the servers connected to it. Both VXLAN interfaces should use 192.168.1.1 as the source IP address, which is the loopback interface of Switch-1. Therefore, this is part of the process for setting up VXLAN to meet the requirements, and the correct answer is yes. For more information on VXLAN and EVPN, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet2 and the EVPN VXLAN Guide for your switch model1.

VXLAN is a feature of ArubaOS-CX that provides layer 2 connectivity between networks across an IP network1. VXLAN uses a 24-bit identifier called VXLAN Network Identifier (VNI) to segment the layer 2 domain1. VXLAN also uses a tunnel endpoint (VTEP) to encapsulate and decapsulate VXLAN packets1. A VXLAN interface is a logical interface that represents a VNI and is associated with a source IP address and a VRF1. To set up VXLAN without EVPN, you need to create VXLAN interfaces on each switch and configure static VTEP peers1. Based on the exhibit, Switch-1 needs to create two VXLAN interfaces, one with ID 5010 and one with ID 5020, to match the VNIs of the servers connected to it. However, you cannot add multiple VNIs to the same VXLAN interface1. Each VNI must have its own VXLAN interface with a unique source IP address and VRF1. Therefore, this is not part of the process for setting up VXLAN to meet the requirements, and the correct answer is no. For more information on VXLAN and EVPN, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet2 and the EVPN VXLAN Guide for your switch model1.