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

A broadcast arrives in VLAN 10 on Switch-1. Switch 1 forwards the frame on all interfaces assigned to VLAN 10, except the incoming interface. It encapsulates the broadcast with VXLAN and sends it to 192.168.1.3, but not 192.168.1.2 is not a correct explanation of how the switch handles the traffic. Switch-1, Switch-2, and Switch-3 are ArubaOS-CX switches that use VXLAN and EVPN to provide Layer 2 extension over Layer 3 networks. VXLAN is a feature that uses UDP encapsulation to tunnel Layer 2 frames over Layer 3 networks using VNIs. EVPN is a feature that uses BGP to advertise multicast information for VXLAN networks using IMET routes. Switch-1 receives a broadcast in VLAN 10, which belongs to VNI 5010. Switch-1 forwards the frame on all interfaces assigned to VLAN 10, except the incoming interface, as per normal Layer 2 switching behavior. However, Switch-1 does not encapsulate the broadcast with VXLAN and send it only to 192.168.1.3, which is Switch-2's loopback interface, but rather replicates the broadcast, encapsulates each broadcast with VXLAN, and sends the VXLAN traffic to both 192.168.1.2 and 192.168.1.3, which are Switch-3's and Switch-2's loopback interfaces respectively.

Combine multiple links between two data centers into link aggregations (but not multi-chassis ones) is part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection Switching (ERPS) ring. ERPS is a feature that provides loop prevention and fast convergence for Layer 2 networks that use ring topologies. ERPS can support link aggregation groups (LAGs) between two nodes in a ring as long as they are not multi-chassis LAGs (MC-LAGs). MC-LAGs are not supported by ERPS because they can create loops in the ring topology.

Implement Virtual Switching Extension (VSX) on pairs of ERPS switches at the same site. Then combine multiple links between two data centers into VSX LAGs (MC-LAGs) is not part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection Switching (ERPS) ring. ERPS is a feature that provides loop prevention and fast convergence for Layer 2 networks that use ring topologies. VSX is a feature that provides active-active forwarding and redundancy for ArubaOSCX switches. VSX LAGs or MC-LAGs are LAGs that span across two VSX nodes and provide load balancing and resiliency. However, VSX LAGs or MC-LAGs are not supported by ERPS because they can create loops in the ring topology. A better way to load share traffic across the links in an ERPS ring would be to use link aggregation groups (LAGs) between two nodes in a ring as long as they are not multi-chassis LAGs (MC-LAGs)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 loops1.

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

On Switch-1, set 192.168.1.3 as a peer IP address in the VNI 5020 context is part of the process for setting up VXLAN to meet the requirements of enabling servers to be part of the same VXLANs and VNIs as shown in the exhibit. Switch-1, Switch-2, and Switch-3 are ArubaOS-CX switches that use VXLAN to provide Layer 2 extension over Layer 3 networks without EVPN. VXLAN is a feature that uses UDP encapsulation to tunnel Layer 2 frames over Layer 3 networks using VNIs. To set up VXLAN without EVPN on Switch-1, you need to do the following steps:

Configure loopback interfaces with IP addresses on each switch

Configure VLAN interfaces with IP addresses on each switch

Configure VXLAN interfaces with VNIs on each switch

Configure peer IP addresses for each VNI on each switch

Configure static routes or dynamic routing protocols to enable reachability between loopback interfaces On Switch-1, setting 192.168.1.3 as a peer IP address in the VNI 5020 context means that Switch-1 can send and receive VXLAN traffic for VNI 5020 to and from Switch-2, which has the loopback interface with IP address 192.168.1.3.

To help the switch to look inside tunneled traffic and apply different quality of service (QoS) settings to different types of traffic is not a use case for implementing Enhanced Transmission Selection (ETS) on an ArubaOS-CX switch. ETS is a feature that provides bandwidth allocation and priority assignment for different traffic classes based on IEEE 802.1Qaz standard. ETS does not help the switch to look inside tunneled traffic, but rather relies on the priority values in the outer header of the tunneled traffic to apply QoS settings. A better way to help the switch to look inside tunneled traffic and apply different QoS settings to different types of traffic would be to use deep packet inspection (DPI) or application visibility and control (AVC) features.

To ensure a minimum bandwidth guarantee between two endpoints traffic with various 802.1p values is a use case for implementing Enhanced Transmission Selection (ETS) on an ArubaOS-CX switch. ETS is a feature that provides bandwidth allocation and priority assignment for different traffic classes based on IEEE 802.1Qaz standard. ETS can help to ensure a minimum bandwidth guarantee between two endpoints by assigning different priority groups and bandwidth percentages to different traffic classes based on their 802.1p values1.

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