VXLAN EVPN lab 5 of 14
Multihoming with EVPN ESI-LAG and MLAG
Dual-home a server with an EVPN Ethernet segment on Cumulus and another with MLAG on vEOS, compare them from across the fabric, and fail a link on each.
Run this lab
It needs Standard: its 7 nodes are set to 7 vCPU and 11,264 MB in total.
In your workspace: Shared, then VXLAN EVPN fabrics guided labs, then 05 - Multihoming with EVPN ESI-LAG and MLAG
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 7 vCPU, 11,264 MB
- Smallest plan
- Standard
The scenario
Calder Freight's order-processing servers have two NICs each, and a server must survive losing a leaf. Rack A's Cumulus leaves will use EVPN multihoming. Rack B's Arista leaves will use MLAG, the older approach, because a supplier's design document insists on it. You'll build both, and compare them from the other side of the fabric.
| Item | Rack A | Rack B |
|---|---|---|
| Leaves | leaf1 (AS 65001, 10.255.0.11), leaf2 (AS 65002, 10.255.0.12): Cumulus | leaf3 (AS 65003, 10.255.0.13), leaf4 (AS 65004, 10.255.0.14): vEOS |
| Host | h1, 10.10.10.11/24, LACP bond on swp3 of each leaf | h2, 10.10.10.12/24, LACP bond on Ethernet4 of each leaf |
| Redundancy | ESI 03:44:38:39:be:ef:aa:00:00:01, local-id 1 | MLAG domain POD2, peer link Port-Channel10 (Ethernet5 and 6), MLAG 20 |
| VTEP | Each leaf keeps its own loopback | Shared Loopback1 10.255.1.34 |
| Peer link addresses | none needed | leaf3 10.255.255.1/30, leaf4 10.255.255.2/30 on Vlan4094 |
VLAN 10 is VNI 10010 with route target 65000:10010 everywhere.
What you’ll practise
- Build an all-active EVPN Ethernet segment with LACP
- Read the designated forwarder election and type 1 and type 4 routes
- Build an MLAG pair with a shared VTEP
- Compare aliasing with a shared VTEP
The tasks
- Start the lab
- Build the Ethernet segment on rack A
- Read the election and the split-horizon rules
- Build the MLAG pair on rack B
- Compare them from the far side
- Fail a link on each side
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 - spine1
Ethernet3to leaf3Ethernet1 - spine1
Ethernet4to leaf4Ethernet1 - leaf1
swp3to h1eth0 - leaf2
swp3to h1eth1 - leaf3
Ethernet4to h2eth0 - leaf4
Ethernet4to h2eth1 - leaf3
Ethernet5to leaf4Ethernet5 - leaf3
Ethernet6to leaf4Ethernet6
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| spine1 | 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 |
| leaf3 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| leaf4 | 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
VXLAN EVPN fabrics guided labs.Open
05 - Multihoming with EVPN ESI-LAG and MLAGand 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.