CloudLabBox
Try the free demo

VXLAN EVPN lab 2 of 14

EVPN control plane with route types 2 and 3

Stretch one VLAN across a routed fabric with EVPN on Cumulus and vEOS leaves, then read the type 3 and type 2 routes that replace flood-and-learn.

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 02 - EVPN control plane with route types 2 and 3

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
Intermediate
Time
About 70 minutes
Nodes need
7 vCPU, 9,728 MB
Smallest plan
Standard

The scenario

Calder Freight's Leeds data hall now has the routed underlay from lab 1. The warehouse-tracking servers still expect to sit in one subnet, even though they're spread across three racks. You'll stretch VLAN 10 across the routed fabric, with EVPN carrying the MAC addresses instead of flood-and-learn.

Two of the leaves run Cumulus Linux and one runs Arista EOS, so you'll read the same routes through two sets of commands.

ItemValue
Spinespine1, AS 65000, Loopback0 10.255.0.1
Leavesleaf1 AS 65001, 10.255.0.11 (Cumulus) · leaf2 AS 65002, 10.255.0.12 (Cumulus) · leaf3 AS 65003, 10.255.0.13 (vEOS)
Fabric linksspine1–leafN 10.1.N.0/31 (spine .0, leaf .1)
Host portsleaf1 swp3, leaf2 swp3, leaf3 Ethernet3
HostLeaf and portVLAN / VNIAddress
h1leaf1 swp310 / 1001010.10.10.11/24
h2leaf2 swp310 / 1001010.10.10.12/24
h3leaf3 Ethernet310 / 1001010.10.10.13/24

Route distinguisher: <loopback>:<VNI>. Route target: 65000:<VNI> on every leaf.

What you’ll practise

  • Add the EVPN address family to an existing eBGP underlay
  • Map a VLAN to a VNI on Cumulus and on vEOS, with explicit RD and RT
  • Read type 3 routes and the ingress-replication flood list
  • Read type 2 routes and the remote MAC table

The tasks

  1. Start the lab
  2. Add the EVPN address family
  3. Map VLAN 10 to VNI 10010
  4. Read route type 3 and the flood list
  5. Pass traffic and read route type 2

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 EVPN control plane with route types 2 and 37 nodes, 6 links. Every link is listed as text below the diagram.spine1leaf1leaf2leaf3h1h2h3Ethernet2swp1swp3eth0swp3eth0Ethernet3eth0Ethernet1swp1Ethernet3Ethernet1
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
  • leaf2 swp3 to h2 eth0
  • leaf3 Ethernet3 to h3 eth0
Nodes in EVPN control plane with route types 2 and 3, 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
h2Alpine 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 02 - EVPN control plane with route types 2 and 3 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.