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
- 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.
| Node | AS | Loopback | Role |
|---|---|---|---|
| spine1 | 65000 | 10.255.0.1 | vEOS spine, numbered links |
| spine2 | 65000 | 10.255.0.2 | vEOS spine, unnumbered links |
| leaf1 | 65001 | 10.255.0.11 | Cumulus leaf |
| leaf2 | 65002 | 10.255.0.12 | Cumulus leaf |
| Link | Spine side | Leaf side |
|---|---|---|
| spine1 Ethernet1 – leaf1 swp1 | 10.1.1.0/31 | 10.1.1.1/31 |
| spine1 Ethernet2 – leaf2 swp1 | 10.1.2.0/31 | 10.1.2.1/31 |
| spine2 Ethernet1 – leaf1 swp2 | no IPv4 address | no IPv4 address |
| spine2 Ethernet2 – leaf2 swp2 | no IPv4 address | no 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
- Start the lab
- Address the links and loopbacks
- Run eBGP on the numbered links
- Add spine2 with unnumbered BGP
- Confirm equal-cost paths
- 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.
Every link, as text
- spine1
Ethernet1to leaf1swp1 - spine1
Ethernet2to leaf2swp1 - spine2
Ethernet1to leaf1swp2 - spine2
Ethernet2to leaf2swp2
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| spine1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| spine2 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| leaf1 | NVIDIA Cumulus VX | cumulus-vx-5.9.1 | 1 vCPU, 2,048 MB |
| leaf2 | NVIDIA Cumulus VX | cumulus-vx-5.9.1 | 1 vCPU, 2,048 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
VXLAN EVPN fabrics guided labs.Open
01 - IP fabric underlay on vEOS spines and Cumulus leavesand 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
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.