HP HP Certifications HPE2-W09 Questions & Answers

• Question 1:

  Can you attach this type of ArubaOS-CX interface to a VRF? Solution: a GRE tunnel interface

  A. Yes

  B. No

  Correct Answer: A

  A GRE tunnel interface is a virtual interface that can encapsulate different network layer protocols inside point-to-point or point-to-multipoint links over an IP network1 . It can be assigned an IP address and attached to a VRF. A VRF allows multiple instances of a routing table to co-exist within the same router2. By attaching a GRE tunnel interface to a VRF, you can isolate the traffic of that tunnel from other tunnels and routing domains2.

• Question 2:

  Is this a use case for disabling split-recovery mode on ArubaOS-CX switches in a Virtual Switching Extension (VSX) fabric? Solution: You want to prevent any possibility of a split brain situation from occurring if the keepalive link fails some time after the ISL.

  A. Yes

  B. No

  Correct Answer: A

  Split-recovery mode is a feature of ArubaOS-CX that prevents traffic loss when the ISL goes out-of-sync 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.

• Question 3:

  Refer to the exhibit.

  

  You are adding a VLAN 30, subnet 10.0.30.0/24 to the network shown in the exhibit. (This network is simplified to just the relevant switches for this item.) This subnet belongs in VRF A, and you have added a Layer 3 VLAN 30 interface

  attached to this VRF on Switch-1. You want to make the services in this VLAN available to devices in 10.1.20.0/24 in VRF B.

  Is this part of a valid setup for meeting these requirements?

  Solution: Add VRF B as the secondary VRF on VLAN interface 30.

  A. Yes

  B. No

  Correct Answer: B

  The solution is incorrect because adding VRF B as the secondary VRF on VLAN interface 30 is not part of a valid setup for meeting these requirements. Adding VRF B as the secondary VRF on VLAN interface 30 would allow devices in VLAN 30 to communicate with devices in VRF B, but not vice versa. Therefore, adding VRF B as the secondary VRF on VLAN interface 30 is not sufficient for meeting these requirements. https://www.arubanetworks.com/support-services/ training-services/data-center-network- specialist/

• Question 4:

  Does this correctly describe how Network Analytics Engine (NAE) agents work?

  Solution: Agents collect data every minute and send the data to a centralized SNMP server in SNMP traps.

  A. Yes

  B. No

  Correct Answer: B

  Agents do not collect data every minute and send the data to a centralized SNMP server in SNMP traps. NAE is a feature that provides network operators with distributed analytics for faster troubleshooting and resolution of network-impacting issues1 . Agents are scripts that run on ArubaOS-CX switches and collect data from various sources, such as CLI commands, REST APIs, or syslog messages1. Agents can also define conditions and actions based on the collected data1. Agents do not send the data to a centralized SNMP server, but store it locally on the switch1. Agents can also send alerts to external systems, such as email servers or syslog servers, but not in SNMP traps1. The statement is false because it incorrectly describes how NAE agents work.

• Question 5:

  Your customer is using Nutanix AHV and they need a network orchestration tool to simplify network provisioning. Is this operation supported when Aruba Fabric Composer (AFC) is integrated with Nutanix?

  Solution: Automated configuration of Layer 3 MP-BGP protocol on leaf switches

  A. Yes

  B. No

  Correct Answer: B

  Automated configuration of Layer 3 MP-BGP protocol on leaf switches is not an operation supported when Aruba Fabric Composer (AFC) is integrated with Nutanix. AFC is a tool that provides automation and orchestration for managing data center networks composed of ArubaOS-CX switches. AFC can integrate with various data center software such as VMware vSphere, Nutanix AHV, Microsoft Hyper-V, etc. AFC can discover, monitor, and configure Nutanix AHV clusters and hosts using REST APIs. However, AFC does not support the configuration of Layer 3 MP-BGP protocol on leaf switches, which is required for EVPN VXLAN networks. AFC only supports the configuration of Layer 2 VXLAN networks without EVPN1.

• Question 6:

  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: The link-up delay timer is only required when split-recovery is disabled.

  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. VSX link-up delay is a feature that delays bringing downstream VSX links up, following a VSX device reboot or an ISL flap. This prevents traffic blackholing or loops due to transient conditions. The link-up delay timer is not only required when split-recovery is disabled. Split-recovery is another feature that prevents traffic blackholing or loops when the ISL link fails and then recovers. Split-recovery works by disabling the secondary VSX member's downstream links until it synchronizes with the primary member. However, split-recovery does not cover all scenarios where traffic blackholing or loops can occur, such as when both VSX members reboot simultaneously or when the ISL flaps rapidly. Therefore, it is recommended to configure the link-up delay timer even when split-recovery is enabled1. Therefore, this is not a valid guideline for configuring the switches' link-up delay settings.

• Question 7:

  Is this correct positioning of AtubaOS-CX switches in the data center?

  Solution: A data center will use a leaf-spine topology and requires 64 leaf switches. Aruba CX 8325 switches can be a good choice for both the leaf and spine switches.

  A. Yes

  B. No

  Correct Answer: A

  ArubaOS-CX switches are designed for enterprise campus, aggregation, and data center networking use cases1. ArubaOS-CX switches support a leaf-spine topology, which is a two-layer network architecture that provides high performance, scalability, and reliability for data center networks2. Aruba CX 8325 switches are compact 1U switches that offer high density and high speed connectivity for both leaf and spine switches3. Aruba CX 8325 switches can support up to 32 ports of 100GbE or 48 ports of 25GbE and 8 ports of 100GbE3. For a data center that requires 64 leaf switches, Aruba CX 8325 switches can be a good choice for both the leaf and spine switches, as they can provide enough bandwidth and port density for the network traffic3. Therefore, this is a correct positioning of ArubaOS-CX switches in the data center, and the correct answer is yes. For more information on ArubaOS-CX switches and data center solutions, refer to the Aruba Data Center Network Specialist (ADCNS) certification datasheet and the Aruba CX Switch Series datasheets3 .

• Question 8:

  You enter this command on an ArubaOS-CX switch:

  Switch# show erps status ring 1

  Is this what the specified status means?

  Solution: The status is Protection, which means that the ring is up and fully connected with the RPL port blocked.

  A. Yes

  B. No

  Correct Answer: A

  The status is Protection, which means that the ring is up and fully connected with the RPL port blocked is what the specified status means for Ethernet Ring Protection Switching (ERPS) on an ArubaOS-CX switch. Protection is one of the possible statuses for an ERPS ring instance, and it indicates that the ring is operating normally with one port blocked to prevent loops. The RPL port is the port that connects to the RPL node, which is responsible for blocking and unblocking traffic on the ring2

• Question 9:

  You plan to use multi-protocol BGP to implement dynamic VRF route leaking on an ArubaOS-CX switch.

  Is this a rule for the setup?

  Solution: You can only leak routes between up to three VRFs.

  A. Yes

  B. No

  Correct Answer: B

  You can only leak routes between up to three VRFs is not a rule for the setup of multi-protocol BGP to implement dynamic VRF route leaking on an ArubaOS-CX switch. There is no limit on the number of VRFs that can participate in route leaking using multi- protocol BGP. You can configure multiple import and export route targets for each VRF and leak routes between any VRFs that have matching route targets1.

• Question 10:

  Refer to the exhibits.

  

  

  Is this how the switch-1 handles the traffic?

  Solution: 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 VXIAN and sends it to 192.168.1.3, out not

  192.168.1.2.

  A. Yes

  B. No

  Correct Answer: B

  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.