Arista EOS practice labs
20 guided labs on Arista vEOS switches, from your first EOS command to a two-tenant EVPN-VXLAN leaf-spine fabric: VLANs, MSTP and LACP, MLAG, OSPF, eBGP with ECMP and BFD, VXLAN and EVPN, automation with eAPI, Python and Ansible, and day-2 operations, with two troubleshooting labs. Five WAN routing labs add IS-IS levels, LDP, SR-MPLS with TI-LFA and an SR-TE policy, BGP L3VPN and MPLS troubleshooting, with real labelled traffic you can capture.
- Guided labs
- 20
- Follows
- Arista Network Foundations (AN-FN-OP01), Data Center Engineering (AN-DC-EN01) and part of WAN Routing: MPLS Core (AN-RT-MP01)
- Runs every lab
- Standard
- Devices
- vEOS, Alpine Linux and EVE-NG GUI server
Who these labs are for
For engineers preparing for Arista’s Network Foundations or Data Center Engineering exams, engineers moving from Cisco or Juniper to EOS, and anyone who wants real MLAG, leaf-spine BGP and EVPN-VXLAN practice without building a lab server.
CloudVision isn’t hosted here, so the labs work on the switches themselves. The WAN labs cover part of AN-RT-MP01: RSVP-TE, pseudowires, BGP-LU, L3EVPN type 5 and EVPN E-LAN aren’t included. vEOS nodes take about 4 minutes to boot.
The 20 labs
Every lab in the folder, as the workspace lists them, with what each runs and the smallest plan that fits. Read on 2 November 2026.
Arista EOS course 20 labs
Shared folderArista EOS guided labs
From the EOS CLI to EVPN-VXLAN, two troubleshooting labs and a capstone fabric, then five labs on WAN routing and MPLS.
-
01EOS CLI and management access with safe change
Take two factory-fresh Arista leaf switches to a documented, secured baseline: learn the EOS command line, build an out-of-band management VRF with SSH, add role-based users, and make changes safely with configuration sessions and checkpoints.
2× vEOS
2 vCPU, 4,096 MBFits LiteRuns in the free demo
-
02VLANs and trunks with SVIs and LLDP
Segment Northwind's operations floor into VLANs, carry them over an 802.1Q trunk with a deliberate native VLAN, and route between them with switched virtual interfaces on the core switch.
3× Alpine Linux, 2× vEOS
5 vCPU, 5,632 MBFits LiteRuns in the free demo
-
03MSTP and LACP port-channels
Turn a looped triangle of switches into a loop-free, load-shared layer 2 network: bundle the inter-switch links with LACP, design an MSTP region with one root per instance, and protect the edge with portfast, BPDU guard and root guard.
3× vEOS, 1× Alpine Linux
4 vCPU, 6,656 MBFits LiteRuns in the free demo
-
04MLAG with VARP and VRRP gateways
Join two Arista leaves into an MLAG pair so an access switch can dual-home with one LACP port-channel, then give the hosts an active-active VARP gateway and compare it with an active-standby VRRP gateway.
3× vEOS, 2× Alpine Linux
5 vCPU, 7,168 MBFits LiteRuns in the free demo
-
05Static routing and multi-area OSPF in a leaf-spine
Address a small routed leaf-spine from an addressing plan, connect it first with static routes, then replace them with OSPF: a point-to-point backbone, a non-backbone area on one leaf with a summary at the ABR, passive host interfaces, a default route from the spine and a floating static backup.
3× vEOS, 2× Alpine Linux
5 vCPU, 7,168 MBFits LiteRuns in the free demo
-
06ACLs and management-plane hardening with IPv6 basics
Protect Northwind's infrastructure from the user VLAN with an extended ACL and per-entry counters, restrict SSH to the admin workstation with a standard ACL on the management plane, inspect the control-plane ACL, and add dual-stack IPv6 with static routes.
2× Alpine Linux, 2× vEOS
4 vCPU, 5,120 MBFits LiteRuns in the free demo
-
07eBGP leaf-spine underlay with ECMP and BFD
Build the routed underlay of a two-spine, two-leaf fabric the way Arista designs recommend: one private AS per leaf, a shared spine AS, peer groups, dynamic BGP peering on the spines, route-map-controlled advertisements, four-way ECMP, BFD and jumbo MTU.
4× vEOS, 2× Alpine Linux
6 vCPU, 9,216 MBFits Standard
-
08VXLAN 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.
4× vEOS, 2× Alpine Linux
6 vCPU, 9,216 MBFits Standard
-
09EVPN layer 3 with anycast gateways and symmetric IRB
Add routing to the EVPN fabric: a tenant VRF with an L3 VNI, distributed anycast gateways on every leaf, symmetric IRB between subnets that exist on different leaves, and an external prefix advertised as an EVPN type 5 route.
4× vEOS, 3× Alpine Linux
7 vCPU, 9,728 MBFits Standard
-
10VXLAN and EVPN with an MLAG leaf pair
Dual-home an access switch to an MLAG leaf pair that acts as one VTEP: shared VTEP loopback, iBGP underlay between the peers, EVPN to the spine, anycast gateways with the MLAG system MAC, and a failover test that keeps traffic flowing.
5× vEOS, 2× Alpine Linux
7 vCPU, 11,264 MBFits Standard
-
11Automating EOS with eAPI and Python and Ansible
Turn on Arista's eAPI in the management VRF, read structured JSON from the CLI and over HTTPS with curl, collect an inventory and push a VLAN with Python, then make the same kind of change idempotently with an Ansible playbook.
2× vEOS, 1× EVE-NG GUI server
3 vCPU, 6,144 MBFits LiteRuns in the free demo
-
12EOS day-2 operations with AEM and port mirroring
Run the day-2 toolkit a data-centre operations engineer uses on EOS: a quick health check, a SPAN session to a capture host, an event handler that reacts to an uplink going down, scheduled CLI snapshots, and a configuration session that rolls itself back unless confirmed.
3× Alpine Linux, 2× vEOS
5 vCPU, 5,632 MBFits LiteRuns in the free demo
-
13Troubleshooting a campus pod with MLAG and OSPF
A rack that was 'finished' on Friday doesn't work on Monday: users can't reach the application server and monitoring says the MLAG pair is degraded. Find and fix five planted faults across port-channels, MLAG, OSPF and an ACL, using a bottom-up method and EOS show commands.
4× vEOS, 2× Alpine Linux
6 vCPU, 9,216 MBFits Standard
-
14Troubleshooting 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.
4× vEOS, 3× Alpine Linux
7 vCPU, 9,728 MBFits Standard
-
15Capstone - 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.
4× Alpine Linux, 4× vEOS
8 vCPU, 10,240 MBFits Standard
-
16IS-IS levels and areas for a WAN core
Build the IS-IS underlay of an MPLS core: a Level-2 backbone, a Level-1 area with two attached routers, PE loopbacks leaked down into Level 1, a metric that sets the working path, and authenticated hellos and LSPs.
4× vEOS, 2× Alpine Linux
6 vCPU, 9,216 MBFits Standard
-
17MPLS and LDP with a BGP-free core
Switch on MPLS and LDP across an IS-IS core, read the label tables, run iBGP on the PEs only, and prove with LSP ping and a packet capture that P routers running no BGP forward customer traffic on labels alone.
4× vEOS, 2× Alpine Linux
6 vCPU, 9,216 MBFits Standard
-
18SR-MPLS with TI-LFA and an SR-TE policy
Move a running core from LDP to segment routing without touching BGP, protect it with TI-LFA, watch the repair label stack on the wire during a real link failure, then steer one service down a non-default path with an SR-TE policy and BGP colour.
4× vEOS, 2× Alpine Linux
6 vCPU, 9,216 MBFits Standard
-
19BGP L3VPN with overlapping customers
Run two customers with the same addresses over one SR-MPLS core: VRFs, route distinguishers, route targets, a VPNv4 session between PEs, eBGP to a customer router, then a shared-services VRF that both customers reach without reaching each other.
5× Alpine Linux, 4× vEOS
9 vCPU, 10,752 MBFits Standard
-
20Troubleshooting an MPLS core and L3VPN
A weekend change left the core broken. Work up the stack from IS-IS through MPLS and segment routing to BGP and the VRFs, find five planted faults, fix each with the smallest change, and prove the service end to end.
4× Alpine Linux, 4× vEOS
8 vCPU, 10,240 MBFits Standard
Devices and images
The exact Add Node images the labs use, and the vCPU and RAM their nodes are set to. Your plan counts what each running node is set to.
| Device | Image in Add Node | Set to | Labs | Nodes |
|---|---|---|---|---|
| Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB | 20 | 68 |
| Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB | 18 | 46 |
| EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 2,048 MB | 1 | 1 |
How to open the labs
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Arista EOS guided labs.Open a lab and start its nodes, then open Lab Tasks for the steps.
The labs are read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change a lab, rebuild it in your own folder.


Questions about the Arista EOS labs
Are these Arista EOS labs free?
They’re included with every lab plan, with nothing extra to pay, rather than free. Plans start at £3 a day or £0.50 an hour. To try one first, the free demo gives you 30 minutes with 6 vCPU and 8 GB, enough to run 8 of these labs.
Which plan do I need for these labs?
Standard, with 12 vCPU and 16 GB, runs every lab here. Lite runs 8 of the 20. EVE-NG admits a node by the vCPU and RAM configured on it, so a lab needs the total its running nodes are set to. The biggest here, “VXLAN and EVPN with an MLAG leaf pair”, needs 7 vCPU and 11,264 MB. Each lab’s Lab Tasks pane names the plan it needs.
Can I change these labs?
You can start the nodes and configure the devices, but the labs are read-only: changes to the topology can’t be saved. To change one, rebuild it in your own folder.
Are these labs from Arista Networks?
No. CloudLabBox wrote them to follow the topics of Arista’s Network Foundations Associate (AN-FN-OP01) and Data Center Engineering Specialist (AN-DC-EN01) exams, and the hands-on routing and MPLS skills in part of WAN Routing: MPLS Core Specialist (AN-RT-MP01). They aren’t training material from Arista Networks, and CloudLabBox is independent of Arista Networks.
Try a lab before you choose
The free demo is a real workspace for 30 minutes, with 6 vCPU and 8 GB: enough to run 8 of these labs. No card and no email.
More practice labs
- CCNA practice labs online
- CompTIA Network+ practice labs
- CCNP ENCOR practice labs
- CCNP ENARSI practice labs
- CCNP Service Provider practice labs
- Cisco NX-OS data centre practice labs
- CCIE Enterprise Infrastructure practice labs
- Network automation practice labs
- Cisco ASA firewall practice labs
- Packet analysis labs with Wireshark and tcpdump
- FortiGate practice labs
- FortiGate SD-WAN practice labs
- Cisco Catalyst SD-WAN CLI practice labs
- Palo Alto firewall practice labs
- Check Point CCSA practice labs
- Check Point CCSE practice labs
- Multi-vendor firewall and VPN practice labs
- BGP practice labs across vendors
- Nokia SR OS NRS I practice labs
- MPLS and L3VPN practice labs
- VXLAN EVPN practice labs across vendors
- IPv6 practice labs across vendors
- Linux labs for network engineers
- Multi-vendor troubleshooting practice labs
- JNCIA-Junos practice labs
- JNCIS-ENT practice labs
- JNCIA-SEC and JNCIS-SEC practice labs
- JNCIS-SP JN0-364 practice labs
- JNCIP-ENT JN0-650 practice labs
- HPE Aruba Networking CX switching labs
- Huawei HCIA-Datacom practice labs
- HCIP-Datacom Core practice labs
- MikroTik MTCNA practice labs
- MikroTik MTCRE practice labs
- MikroTik MTCINE practice labs
- MikroTik MTCSE practice labs
- MikroTik MTCTCE practice labs
- MikroTik MTCIPv6E practice labs
- All practice labs
CloudLabBox is independent of Arista Networks. The labs follow exam topics and aren’t vendor training material; vendor names identify the exams and the images in the workspace.