HP HP Certifications HPE2-W09 Questions & Answers

• Question 71:

  Can you attach this type of ArubaOS-CX interface to a VRF?

  Solution: A loopback interface

  A. Yes

  B. No

  Correct Answer: B

  A loopback interface can be attached to a VRF on an ArubaOS-CX switch. A loopback interface is a virtual interface that has an IP address assigned to it and is always up. A loopback interface can be attached to a VRF by using the vrf attach command under its configuration mode1.

• Question 72:

  Is this a use case for disabling split-recovery mode on ArubaOS-CX switches in a Virtual Switching Extension (VSX) fabric?

  Solution: You are not concerned about split brain Issues in your environment, so you want the secondary member to keep its links up if the ISL falls.

  A. Yes

  B. No

  Correct Answer: A

  You are not concerned about split brain issues in your environment, so you want the secondary member to keep its links up if the ISL fails is a use case for disabling split-recovery mode on ArubaOS-CX switches in a Virtual Switching Extension (VSX) fabric. 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 split-recovery mode is a feature that prevents split-brain scenarios when both VSX nodes lose connectivity with each other but remain up. When split-recovery mode is disabled, if the ISL fails but both VSX nodes remain up,

• Question 73:

  Is this part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection Switching (ERPS) ring?

  Solution: 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 (M- LAGs).

  A. Yes

  B. No

  Correct Answer: B

  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 ArubaOS-CX 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.

• Question 74:

  Is this a rule for configuring schedule profiles on an ArubaOS-CX switch? Solution: With the exception of a single strict priority queue, all queues must use the same scheduling algorithm.

  A. Yes

  B. No

  Correct Answer: A

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

• Question 75:

  Does this correctly describe how the Virtual Switching Extension (VSX) fabric reacts to various component failure scenarios?

  Solution: 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 Svls.

  A. Yes

  B. No

  Correct Answer: B

  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.

• Question 76:

  Is this how you should position switches in the ArubaOS-CX portfolio for data center networks?

  Solution: Deploy Aruba 83xx switches as core switches for very large three-tier data center networks.

  A. Yes

  B. No

  Correct Answer: A

  Deploying Aruba 83xx 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. The Aruba 83xx switches are designed for data center spine or core roles, and they provide high performance, scalability, and resiliency. They can support very large three-tier data center networks with up to 512 leaf switches using VSX2.

• Question 77:

  Is this a use case for disabling split-recovery mode on ArubaOS-CX switches in a Virtual Switching Extension (VSX) fabric?

  Solution: In situations in which the primary switch fails and then reboots, you want to make the primary switch wait a period before it takes over as the primary switch.

  A. Yes

  B. No

  Correct Answer: B

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

• Question 78:

  Two ArubaOS-CX switches ate part of a Virtual Switching Extension (V5X) fabric. Is this a guideline for configuring the switches' link-up delay settings?

  Solution: Set the link-up delay timer based on the number of MAC forwarding, ARP, and routing table entries.

  A. Yes

  B. No

  Correct Answer: A

  Set the link-up delay timer based on the number of MAC forwarding, ARP, and routing table entries is a guideline for configuring the switches' link-up delay settings for Virtual Switching Extension (VSX) fabric. The link-up delay timer defines how long a VSX node waits before advertising link state changes to its peer node. This allows the node to synchronize its MAC forwarding, ARP, and routing tables with its peer node before sending or receiving traffic on the newly activated link1.

• Question 79:

  Is this part of a valid strategy for load sharing traffic across the links in an Ethernet Ring Protection Switching (ERPS) solution? Solution: Create two ERPS instances for the ring and assign different VLANs and different ring protection links (RPL) to each instance.

  A. Yes

  B. No

  Correct Answer: A

  Creating two ERPS instances for the ring and assigning different VLANs and different RPLs to each instance 1s part of a valid strategy for load sharing traffic across the links in an ERPS solution1. ERPS is a protocol that provides protection and recovery for Ethernet traffic in a ring topology1. It uses a RPL to block one of the links in the ring and prevent loops1. By creating two ERPS instances with different RPLs, you can use both links in the ring for different VLANs and achieve load sharing1.

• Question 80:

  Does this correctly describe how the Virtual Switching Extension (VSX) fabric reacts to various component failure scenarios?

  Solution: The ISL and keepalive goes down, and after a few seconds, the keepalive link restores. Switch-l and Switch-2 remains up. The Split-recovery mode is enabled. In this case the secondary switch shutdowns SVls when keepalive is restored.

  A. Yes

  B. No

  Correct Answer: A

  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.