Arista EOS lab 15 of 20
Capstone - a two-tenant EVPN-VXLAN fabric from a design
Turn a design document into a working fabric with nothing pre-built: eBGP underlay with ECMP and BFD, an EVPN overlay through route-server spines, tenant RED with VLAN-based services and tenant BLUE with a VLAN-aware bundle, symmetric IRB in both, and proof that the tenants are isolated.
Run this lab
It needs Standard: its 8 nodes are set to 8 vCPU and 10,240 MB in total.
In your workspace: Shared, then Arista EOS guided labs, then 15 - Capstone - a two-tenant EVPN-VXLAN fabric from a design
- Level
- Advanced
- Time
- About 120 minutes
- Nodes need
- 8 vCPU, 10,240 MB
- Smallest plan
- Standard
The scenario
Northwind has won a hosting contract with two customers who must never see each other's traffic. You have four factory-fresh switches (only hostnames and descriptions are set), four test hosts and the design below. Build the whole fabric, validate it in stages, and hand over evidence that each tenant works and that the tenants are isolated. This is the kind of multi-stage build the Data Center Engineering practical exam asks for: read the tables carefully, then work methodically.
Underlay
| Link | Spine side | Leaf side |
|---|---|---|
| spine1 Et1 – leaf1 Et1 | 10.1.1.0/31 | 10.1.1.1/31 |
| spine1 Et2 – leaf2 Et1 | 10.1.1.2/31 | 10.1.1.3/31 |
| spine2 Et1 – leaf1 Et2 | 10.1.2.0/31 | 10.1.2.1/31 |
| spine2 Et2 – leaf2 Et2 | 10.1.2.2/31 | 10.1.2.3/31 |
| Switch | AS | Loopback0 (router ID, overlay) | Loopback1 (VTEP) |
|---|---|---|---|
| spine1 / spine2 | 65000 | 10.255.0.1 / 10.255.0.2 | – |
| leaf1 | 65001 | 10.255.0.11 | 10.255.1.11 |
| leaf2 | 65002 | 10.255.0.12 | 10.255.1.12 |
Rules: fabric MTU 9214; spines accept leaves dynamically (AS 65001–65099); ECMP up to 4 paths; BFD on underlay sessions; only loopbacks are advertised in the underlay; overlay sessions between Loopback0 addresses, EVPN only, spines keep next hops unchanged.
Tenants (anycast gateway MAC 00:1c:73:00:00:99 on both leaves; gateways are .1)
| Tenant | VRF / L3 VNI / RT | VLAN | VNI | Subnet | Where | MAC-VRF |
|---|---|---|---|---|---|---|
| RED | RED / 50100 / 50100:50100 | 110 | 10110 | 10.110.0.0/24 | leaf1 (red1 .11 on Et3) | VLAN-based: RD <Lo0>:10110, RT 110:10110 |
| RED | 120 | 10120 | 10.120.0.0/24 | leaf2 (red2 .12 on Et3) | VLAN-based: RD <Lo0>:10120, RT 120:10120 | |
| BLUE | BLUE / 50200 / 50200:50200 | 210 | 10210 | 10.210.0.0/24 | both leaves (blue1 .11 on leaf1 Et4, blue2 .12 on leaf2 Et4) | VLAN-aware bundle BLUE: RD <Lo0>:2, RT 2:2 |
IP-VRF RDs: <Lo0>:50100 for RED, <Lo0>:50200 for BLUE.
| Host | Leaf / port | VLAN | Address | Gateway |
|---|---|---|---|---|
| red1 | leaf1 Et3 | 110 | 10.110.0.11/24 | 10.110.0.1 |
| blue1 | leaf1 Et4 | 210 | 10.210.0.11/24 | 10.210.0.1 |
| red2 | leaf2 Et3 | 120 | 10.120.0.12/24 | 10.120.0.1 |
| blue2 | leaf2 Et4 | 210 | 10.210.0.12/24 | 10.210.0.1 |
What you’ll practise
- Build a complete eBGP underlay from an addressing plan, with jumbo MTU, ECMP and BFD
- Build an EVPN overlay through route-server spines
- Deploy tenant RED with VLAN-based MAC-VRFs and tenant BLUE with a VLAN-aware bundle
- Route inside each tenant with symmetric IRB and anycast gateways
- Validate in stages and prove that the two tenants can't reach each other
The tasks
- Underlay
- Overlay
- Tenant RED (VLAN-based)
- Tenant BLUE (VLAN-aware bundle)
- Prove the handover
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 red1eth0 - leaf1
Ethernet4to blue1eth0 - leaf2
Ethernet3to red2eth0 - leaf2
Ethernet4to blue2eth0
| 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 |
| red1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| blue1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| red2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| blue2 | 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
15 - Capstone - a two-tenant EVPN-VXLAN fabric from a designand 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.