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.
Refer to the exhibit.
You need to set up an ArubaOS-CX switch to implement Virtual Extensible LAN (VXLAN) WITHOUT Ethernet VPN (EVPN). The exhibit Indicates which servers should be part of the same VXLANs and the desired VNls for the VXLANs. Assume that the network is already configured to permit each ArubaOS-CX switch to reach each other switch's loopback interface.
Is this part of the process for setting up VXLAN to meet the requirements?
Solution: On Switch-1, set 192.168.1.3 as a peer IP address in the VNI 5020 context.
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.
Refer to the exhibit.
You need to set up an ArubaOS-CX switch to implement Virtual Extensible LAN (VXLAN) WITHOUT Ethernet VPN (EVPN). The exhibit Indicates which servers should be part of the same VXLANs and the desired VNls for the VXLANs. Assume that the network is already configured to permit each ArubaOS-CX switch to reach each other switch's loopback interface.
Is this part of the process for setting up VXLAN to meet the requirements?
Solution: On Switch-1, set 192.168.1.3 as a peer IP address in the VNI 5020 context.
Refer to the exhibits.
Is this how the switch handles the traffic?
Solution: 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 VXIAN and sends it to 192.168.1.2. but not 192.168.1.3.
Submit Cancel