Arista EOS lab 8 of 20
VXLAN from static flood lists to EVPN
Stretch one VLAN across a routed leaf-spine twice: first with VXLAN head-end replication and a static flood list, then with MP-BGP EVPN, where VTEPs discover each other and learn MAC addresses through BGP instead of flooding.
Run this lab
It needs Standard: its 6 nodes are set to 6 vCPU and 9,216 MB in total.
In your workspace: Shared, then Arista EOS guided labs, then 08 - VXLAN from static flood lists to EVPN
- Level
- Advanced
- Time
- About 85 minutes
- Nodes need
- 6 vCPU, 9,216 MB
- Smallest plan
- Standard
The scenario
The application team runs a cluster whose two nodes must share one subnet (10.10.10.0/24), but one node is in rack 1 behind leaf1 and the other in rack 2 behind leaf2, and the fabric between them is routed (the eBGP underlay from lab 7 is already built). You will stretch VLAN 10 over the routed fabric with VXLAN: first the quick way, with a hand-written list of remote VTEPs, then the scalable way, with an EVPN control plane in BGP.
| Device | Loopback0 (BGP) | Loopback1 (VTEP) | AS | Host port |
|---|---|---|---|---|
| spine1 | 10.255.0.1 | – | 65000 | – |
| spine2 | 10.255.0.2 | – | 65000 | – |
| leaf1 | 10.255.0.11 | 10.255.1.11 | 65001 | Et3 → h1 (VLAN 10) |
| leaf2 | 10.255.0.12 | 10.255.1.12 | 65002 | Et3 → h2 (VLAN 10) |
| h1 / h2 | – | – | – | 10.10.10.11/24 · 10.10.10.12/24 |
Service: VLAN 10 APP ↔ VNI 10010, route target 10:10010.
What you’ll practise
- Create VTEP loopbacks and advertise them in the underlay
- Map a VLAN to a VNI on interface Vxlan1 and build a static head-end replication flood list
- Read the VXLAN address table and explain data-plane MAC learning
- Build eBGP EVPN overlay sessions between loopbacks, with next-hop-unchanged on the spines
- Configure a MAC-VRF (RD, route targets, redistribute learned) per VLAN
- Identify EVPN route types 2 (MAC-IP) and 3 (IMET) and the VTEP list they build
The tasks
- Check the underlay and add VTEP loopbacks
- VXLAN with a static flood list
- Why flood lists don't scale
- Build the EVPN overlay sessions
- Define the MAC-VRF for VLAN 10
- Watch MAC addresses travel in BGP
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 leaf1Ethernet1 - spine1
Ethernet2to leaf2Ethernet1 - spine2
Ethernet1to leaf1Ethernet2 - spine2
Ethernet2to leaf2Ethernet2 - leaf1
Ethernet3to h1eth0 - leaf2
Ethernet3to h2eth0
| 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 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| leaf2 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| h1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| h2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Arista EOS guided labs.Open
08 - VXLAN from static flood lists to EVPNand 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 Arista EOS labs
Related labs in other courses
CloudLabBox is independent of Arista Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.