CloudLabBox
Try the free demo

VXLAN EVPN lab 3 of 14

Symmetric IRB with an anycast gateway and an L3 VNI

Make the fabric route: a tenant VRF with an L3 VNI, the same anycast gateway on every leaf, and type 5 routes between Cumulus and vEOS.

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 03 - Symmetric IRB with an anycast gateway and an L3 VNI

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 80 minutes
Nodes need
7 vCPU, 9,728 MB
Smallest plan
Standard

The scenario

The tracking servers in VLAN 10 now share a subnet across the racks. Calder Freight's new billing server (h3) is in its own subnet, VLAN 20, and it sits only on leaf3. Today, the tracking servers can't reach it: the fabric only bridges.

You'll add routing to the fabric itself. Every leaf becomes the default gateway for its hosts, using the same gateway address, and routed traffic crosses the fabric in one tenant-wide VNI.

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 / VNIAddressGateway
h1leaf1 swp310 / 1001010.10.10.11/2410.10.10.1
h2leaf2 swp310 / 1001010.10.10.12/2410.10.10.1
h3leaf3 Ethernet320 (local only)10.20.20.13/2410.20.20.1
Tenant itemValue
VRF / L3 VNIRED / 50001
IP-VRF route target65000:50001 on every leaf
IP-VRF route distinguisher<loopback>:50001
Anycast gateway MAC00:1c:73:00:00:01

What you’ll practise

  • Map a tenant VRF to an L3 VNI on Cumulus and vEOS
  • Build an anycast gateway with VRR and with ip address virtual
  • Read type 5 routes and the router MAC
  • Route between subnets where a leaf does not host the destination VLAN

The tasks

  1. Start the lab
  2. Create the tenant VRF and its L3 VNI
  3. Build the anycast gateways
  4. Route across the fabric

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 Symmetric IRB with an anycast gateway and an L3 VNI7 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 Symmetric IRB with an anycast gateway and an L3 VNI, 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 03 - Symmetric IRB with an anycast gateway and an L3 VNI 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.