CloudLabBox
Try the free demo

VXLAN EVPN lab 7 of 14

Multi-tenancy with VRFs and controlled route leaking

Build a second tenant, prove it is isolated, then open a shared-services path across vendors by leaking routes with route targets and filters.

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 07 - Multi-tenancy with VRFs and controlled route leaking

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 now hosts systems for a sister company, so the fabric has two customers who must never see each other. RED is Calder's tenant and BLUE is the sister company's. Both need the shared DNS and licensing server, h3, in a third VRF called SHARED.

You'll build BLUE, prove that the tenants are isolated, then open only the paths you want by leaking routes with route targets.

TenantVRF / L3 VNIRoute targetLeaf and VLANHost
CalderRED / 5000165000:50001leaf1 (Cumulus), VLAN 10h1 10.10.10.11/24
Sister companyBLUE / 5000265000:50002leaf2 (Cumulus), VLAN 30h2 10.30.30.12/24
Shared servicesSHARED / 5000365000:50003leaf3 (vEOS), VLAN 40h3 10.40.40.13/24

leaf3 also has Loopback41, 10.41.41.1/32, in VRF SHARED. It's the management address of the shared services, and no tenant may learn it.

Leaves: leaf1 AS 65001 10.255.0.11, leaf2 AS 65002 10.255.0.12, leaf3 AS 65003 10.255.0.13. Spine: spine1 AS 65000.

What you’ll practise

  • Build a tenant VRF with its own L3 VNI
  • Prove isolation between tenants
  • Leak routes between VRFs with route targets
  • Filter what a VRF exports

The tasks

  1. Start the lab
  2. Build tenant BLUE
  3. Prove the isolation
  4. Leak shared services into the tenants
  5. Control what leaks

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 Multi-tenancy with VRFs and controlled route leaking7 nodes, 6 links. Every link is listed as text below the diagram.spine1leaf1leaf2leaf3h1h2h3swp3eth0swp3eth0Ethernet3eth0Ethernet2swp1Ethernet1swp1Ethernet3Ethernet1
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 Multi-tenancy with VRFs and controlled route leaking, 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 07 - Multi-tenancy with VRFs and controlled route leaking 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.