Arista EOS lab 14 of 20
Troubleshooting an EVPN-VXLAN fabric
The two-leaf EVPN fabric from lab 9 was rebuilt from a template, and now nothing crosses it properly. Validate the underlay, the overlay sessions, the layer 2 service and the layer 3 service in order, and fix five planted faults: a missing VTEP prefix, missing extended communities, a spine rewriting next hops, a route-target typo and an L3 VNI mismatch.
Run this lab
It needs Standard: its 7 nodes are set to 7 vCPU and 9,728 MB in total.
In your workspace: Shared, then Arista EOS guided labs, then 14 - Troubleshooting an EVPN-VXLAN fabric
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 7 vCPU, 9,728 MB
- Smallest plan
- Standard
The scenario
Over the weekend Northwind rebuilt pod 1 from a configuration template: two spines, leaf1 (rack 1) and leaf2 (rack 2), tenant VRF TENANT-A with symmetric IRB, exactly the design of lab 9. Monday's tickets:
- "Web server h1 can't reach its cluster partner h3" (same subnet, VLAN 10, other rack);
- "Web tier can't reach the database h2 or the shared service 10.99.99.1".
There are five faults. Validate the fabric in stages (underlay → overlay sessions → layer 2 service → layer 3 service), fix each fault with the smallest change, and record the evidence.
| Host | Leaf / port | VLAN | Address | Gateway |
|---|---|---|---|---|
| h1 | leaf1 Et3 | 10 WEB | 10.10.10.11/24 | 10.10.10.1 |
| h3 | leaf2 Et4 | 10 WEB | 10.10.10.13/24 | 10.10.10.1 |
| h2 | leaf2 Et3 | 20 DB | 10.20.20.12/24 | 10.20.20.1 |
| service | leaf2 Loopback100 (TENANT-A) | – | 10.99.99.1/32 | – |
What you’ll practise
- Validate an EVPN fabric in stages: underlay, overlay sessions, L2 VNI, L3 VNI
- Prove VTEP reachability with routes and source-based pings
- Read EVPN route details: next hop, extended communities (route targets), VNIs
- Recognise the signature of a spine that rewrites the next hop
- Fix RT and VNI mismatches and explain why routed and bridged traffic failed differently
The tasks
- Reproduce the tickets
- Stage 1: the underlay
- Stage 2: overlay sessions and route attributes
- Stage 3: the layer 2 service (VNI 10010)
- Stage 4: the layer 3 service (VNI 50001)
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 - leaf2
Ethernet4to h3eth0
| 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 |
| h3 | 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
14 - Troubleshooting an EVPN-VXLAN fabricand 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.