CloudLabBox
Try the free demo

VXLAN EVPN lab 9 of 14

NX-OS vPC with VXLAN

Pair two Nexus 9000v leaves with vPC, then make them one VTEP with a shared secondary address so a remote Arista leaf reaches the dual-homed server.

Run this lab

It needs Professional: its 6 nodes are set to 8 vCPU and 21,504 MB in total.

In your workspace: Shared, then VXLAN EVPN fabrics guided labs, then 09 - NX-OS vPC with VXLAN

Run it on Professional from £7.50 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 8 vCPU and 21,504 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 100 minutes
Nodes need
8 vCPU, 21,504 MB
Smallest plan
Professional

The scenario

Calder Freight's finance database has two NICs and must stay up if a switch fails. Rather than move to EVPN multihoming on day one, the Cisco design uses vPC: two Nexus switches that look like one to the server. You'll build the pair, then make it work as one VTEP so the remote rack can reach the server.

NodeASLoopbackRole
spine1 (vEOS)6500010.255.0.1Spine
leaf1 (NX-OS)6500110.255.0.11vPC peer, role priority 100
leaf2 (NX-OS)6500210.255.0.12vPC peer, role priority 200
leaf3 (vEOS)6500310.255.0.13Remote VTEP, h3 on Ethernet3
ItemValue
vPC domain1
Peer linkport-channel10 on Ethernet1/3 and 1/4
KeepaliveEthernet1/5 in VRF KEEPALIVE, 192.168.255.1/30 and .2/30
Host portEthernet1/2 in port-channel20, vpc 20, VLAN 10
Shared VTEP address10.255.1.12, a secondary address on loopback0 of both leaves
VLAN 10VNI 10010, RT 65000:10010

Hosts: h1 10.10.10.11/24 (LACP bond), h3 10.10.10.13/24. EVE's labels e1 to e5 are Ethernet1/1 to 1/5.

What you’ll practise

  • Build a vPC domain with a peer link and keepalive
  • Dual-home a server with LACP to a vPC
  • Share a VTEP address across a vPC pair
  • Check that traffic survives a link failure

The tasks

  1. Start the lab
  2. Build the vPC pair
  3. Make the pair one VTEP
  4. Test from the far side
  5. Fail one link

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of NX-OS vPC with VXLAN6 nodes, 9 links. Every link is listed as text below the diagram.spine1leaf1leaf2leaf3h1h3Ethernet2e1Ethernet3eth0e2eth0e2eth1e3e3e4e4e5e5Ethernet1e1Ethernet3Ethernet1
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • spine1 Ethernet1 to leaf1 e1
  • spine1 Ethernet2 to leaf2 e1
  • spine1 Ethernet3 to leaf3 Ethernet1
  • leaf1 e2 to h1 eth0
  • leaf2 e2 to h1 eth1
  • leaf1 e3 to leaf2 e3
  • leaf1 e4 to leaf2 e4
  • leaf1 e5 to leaf2 e5
  • leaf3 Ethernet3 to h3 eth0
Nodes in NX-OS vPC with VXLAN, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
spine1Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
leaf1Cisco Nexus 9000vnxosv9k-9300v-9.3.102 vCPU, 8,192 MB
leaf2Cisco Nexus 9000vnxosv9k-9300v-9.3.102 vCPU, 8,192 MB
leaf3Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
h1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
h3Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder VXLAN EVPN fabrics guided labs.

  3. Open 09 - NX-OS vPC with VXLAN and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More VXLAN EVPN labs

All VXLAN EVPN labs

Related labs in other courses

CloudLabBox is independent of Arista Networks, Cisco, HPE, Juniper Networks and NVIDIA. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.