VXLAN EVPN lab 1 of 14

IP fabric underlay on vEOS spines and Cumulus leaves

Build the routed underlay that every VXLAN tunnel depends on: eBGP on numbered and unnumbered links, equal-cost paths and BFD, across vEOS and Cumulus.

Run this lab

It needs Standard: its 4 nodes are set to 4 vCPU and 8,192 MB in total. That fits the free demo too.

In your workspace: Shared, then VXLAN EVPN fabrics guided labs, then 01 - IP fabric underlay on vEOS spines and Cumulus leaves

Try it free for 30 minutesRun it on Standard from £5 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 60 minutes
Nodes need
4 vCPU, 8,192 MB
Smallest plan
Standard

The scenario

Calder Freight is replacing the stretched VLANs in its Leeds data hall with a routed leaf-spine fabric. Before any VXLAN tunnel can exist, every leaf's loopback has to reach every other leaf's loopback, over every available path. That's the underlay, and everything in the rest of this course sits on top of it.

You have two Arista vEOS spines and two NVIDIA Cumulus leaves, all with nothing configured. spine1 uses ordinary numbered /31 links. spine2 uses unnumbered links, so you can compare the two.

NodeASLoopbackRole
spine16500010.255.0.1vEOS spine, numbered links
spine26500010.255.0.2vEOS spine, unnumbered links
leaf16500110.255.0.11Cumulus leaf
leaf26500210.255.0.12Cumulus leaf
LinkSpine sideLeaf side
spine1 Ethernet1 – leaf1 swp110.1.1.0/3110.1.1.1/31
spine1 Ethernet2 – leaf2 swp110.1.2.0/3110.1.2.1/31
spine2 Ethernet1 – leaf1 swp2no IPv4 addressno IPv4 address
spine2 Ethernet2 – leaf2 swp2no IPv4 addressno IPv4 address

What you’ll practise

  • Configure vEOS and Cumulus NVUE for a routed leaf-spine fabric
  • Run eBGP over /31 links and over unnumbered links
  • Confirm equal-cost multipath between leaf loopbacks
  • Add BFD to BGP sessions

The tasks

  1. Start the lab
  2. Address the links and loopbacks
  3. Run eBGP on the numbered links
  4. Add spine2 with unnumbered BGP
  5. Confirm equal-cost paths
  6. Detect failures quickly with BFD

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 IP fabric underlay on vEOS spines and Cumulus leaves4 nodes, 4 links. Every link is listed as text below the diagram.spine1spine2leaf1leaf2Ethernet1swp1Ethernet2swp2Ethernet2swp1Ethernet1swp2
4 nodes, with the interface names each link uses.
Nodes in IP fabric underlay on vEOS spines and Cumulus leaves, 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
spine2Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
leaf1NVIDIA Cumulus VXcumulus-vx-5.9.11 vCPU, 2,048 MB
leaf2NVIDIA Cumulus VXcumulus-vx-5.9.11 vCPU, 2,048 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 01 - IP fabric underlay on vEOS spines and Cumulus leaves 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.