CloudLabBox
Try the free demo

VXLAN EVPN lab 4 of 14

Arista and Cumulus interoperability

Find out why automatic route targets break a mixed fabric, fix it two ways, then read a Cumulus Ethernet segment from the Arista side.

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 VXLAN EVPN fabrics guided labs, then 04 - Arista and Cumulus interoperability

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 7 vCPU and 9,728 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 75 minutes
Nodes need
7 vCPU, 9,728 MB
Smallest plan
Standard

The scenario

Calder Freight bought one more rack, and the supplier delivered Arista leaves. In labs 2 and 3 the route targets were written out by hand on every leaf, so the mix of vendors didn't matter. The new rack's installer left the Cumulus leaves on automatic route targets, and h3 on the Arista leaf can't reach anything.

You'll work out what each vendor derives automatically and why they don't match, fix it two ways, then dual-home a new server (h4) and see how an Ethernet segment looks from the other vendor's side.

Itemleaf1 (Cumulus)leaf2 (Cumulus)leaf3 (vEOS)
AS / loopback65001 / 10.255.0.1165002 / 10.255.0.1265003 / 10.255.0.13
VLAN 10 mapped toVNI 10010VNI 10010VNI 10010
RD and RT todayautomaticautomaticrd auto, RT 65000:10010
HostPortAddress
h1leaf1 swp310.10.10.11/24
h3leaf3 Ethernet310.10.10.13/24
h4LACP bond to leaf1 swp4 and leaf2 swp410.10.10.14/24

What you’ll practise

  • Compare automatic RDs and RTs on Cumulus and EOS
  • Explain why an eBGP fabric needs explicit route targets across vendors
  • Build an EVPN Ethernet segment with a type 3 ESI
  • Read type 1 and type 4 routes and aliasing from another vendor

The tasks

  1. Start the lab
  2. Read what each vendor derived
  3. Find the symptom
  4. The quick fix
  5. The better fix
  6. Dual-home h4 and read the ESI

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.

Topology of Arista and Cumulus interoperability7 nodes, 7 links. Every link is listed as text below the diagram.spine1leaf1leaf2leaf3h1h4h3Ethernet2swp1Ethernet3eth0swp3eth0swp4eth1swp4eth0Ethernet1swp1Ethernet3Ethernet1
7 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • spine1 Ethernet1 to leaf1 swp1
  • spine1 Ethernet2 to leaf2 swp1
  • spine1 Ethernet3 to leaf3 Ethernet1
  • leaf1 swp3 to h1 eth0
  • leaf1 swp4 to h4 eth0
  • leaf2 swp4 to h4 eth1
  • leaf3 Ethernet3 to h3 eth0
Nodes in Arista and Cumulus interoperability, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
spine1Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
leaf1NVIDIA Cumulus VXcumulus-vx-5.9.11 vCPU, 2,048 MB
leaf2NVIDIA Cumulus VXcumulus-vx-5.9.11 vCPU, 2,048 MB
leaf3Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
h1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
h4Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
h3Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder VXLAN EVPN fabrics guided labs.

  3. Open 04 - Arista and Cumulus interoperability and 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

All 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.