A broadcast arrives in VLAN 10 on Switch-1. Switch 1 forwards the frame on all interfaces assigned to VLAN10, except the incoming interface. It encapsulates the broadcast with VXLAN and sends it to 192.168.1.2, but not 192.168.1.3 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.2, which is Switch-3’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 1 .

MAC/IP advertisement routes advertise the MAC addresses that can be reached through the VTEP is a correct description of routing information advertised by a VXLAN Tunnel Endpoint (VTEP) that uses EVPN. EVPN is a feature that provides control plane learning and signaling for VXLAN networks.  MAC/IP advertisement routes are one of the types of routes that EVPN uses to advertise MAC and IP addresses of hosts connected to VTEPs 2 .

Creating two configuration plans, one with the standard config and one with the device-specific settings, is not what you should do.  NetEdit is a tool that allows you to manage and monitor multiple switches from a single interface 1 .  It also provides a plan feature that lets you create containers to group devices and execute operations on them, such as deploying, committing, or rolling back device configuration or firmware 1 . However, you do not need to create two configuration plans for your scenario.  You can create one configuration plan with the standard config and use variables to define the device-specific settings 1 .  Variables are placeholders that can be replaced with different values for different devices 1 .  This way, you can deploy a standard config with device-specific settings using one configuration plan 1 .

Different switches have different limitations for the number of NAE scripts, monitors, and agents supported is a correct description of Network Analytics Engine (NAE) limitations on ArubaOS-CX switches. NAE is a feature that provides automation and analytics for managing ArubaOS-CX switches. NAE scripts are scripts that run on switches and collect data from various sources. NAE monitors are rules that define conditions and actions for NAE agents. NAE agents are instances of NAE scripts and monitors that run on switches.  Different switches have different limitations for the number of NAE scripts, monitors, and agents supported depending on their hardware resources 1 .

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 .

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.

The ArubaOS-CX time-series database helps to support network analytics and troubleshooting is a correct description of the ArubaOS-CX architecture. The time-series database (TSDB) is a component of the ArubaOS-CX software that stores information about the switch’s configuration, status, and performance over time.  The TSDB helps to support network analytics and troubleshooting by providing historical data and trend analysis for various metrics 1 .

You cannot leak multicast routes is a rule for the setup of multi-protocol BGP to implement dynamic VRF route leaking on an ArubaOS-CX switch.  Multi-protocol BGP only supports unicast routes for route leaking, and multicast routes are not leaked between VRFs 1 .

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 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 member 1 . 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 members 1 . Therefore, this is not a use case for disabling split-recovery mode on ArubaOS-CX switches in a VSX fabric.

A broadcast arrives in VLAN 10 on Switch-1. Switch 1 forwards the frame on all interfaces assigned to VLAN10, except the incoming interface. It replicates the broadcast, encapsulates each broadcast with VXLAN, and sends the VXLAN traffic to 192.168.1.2 and 192.168.1.3 is 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. Switch-1 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.