VXLAN EVPN lab 6 of 14

Border leaf with type 5 routes and a default route

Connect a tenant VRF to a WAN router through a border leaf, exchange type 5 routes, inject a default route and keep host routes off the WAN.

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 06 - Border leaf with type 5 routes and a default route

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's tenant VRF, RED, works across the fabric, but nothing inside it can reach the outside world. leaf3 becomes the border leaf: it has no hosts, it just connects the fabric to the WAN router. You'll bring external routes into EVPN as type 5 routes, inject a default route, and keep host routes off the WAN.

NodeRoleDetails
spine1SpineAS 65000
leaf1Cumulus leafAS 65001, 10.255.0.11, VLAN 10 (10.10.10.0/24), h1 on swp3
leaf2Cumulus leafAS 65002, 10.255.0.12, VLAN 20 (10.20.20.0/24), h2 on swp3
leaf3vEOS border leafAS 65003, 10.255.0.13, VRF RED, L3 VNI 50001, Ethernet4 to the WAN
wan1IOSv WAN routerAS 65500, Gi0/0 10.99.0.1/30
AddressWhereWhy it matters
10.99.0.2/30leaf3 Ethernet4 in VRF REDThe WAN link
203.0.113.1wan1 Loopback0In BGP, so it arrives as a specific route
198.51.100.1wan1 Loopback1Not in BGP, so only a default route can reach it

What you’ll practise

  • Peer with a WAN router inside a tenant VRF
  • Read external routes as type 5 routes on a remote leaf
  • Inject a default route into the fabric
  • Filter host routes towards the WAN

The tasks

  1. Start the lab
  2. Peer with the WAN in the tenant VRF
  3. See the WAN route arrive as type 5
  4. Inject a default route
  5. Keep host routes off the WAN

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 Border leaf with type 5 routes and a default route7 nodes, 6 links. Every link is listed as text below the diagram.spine1leaf1leaf2leaf3wan1h1h2swp3eth0swp3eth0Ethernet4Gi0/0Ethernet2swp1Ethernet3Ethernet1Ethernet1swp1
7 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in Border leaf with type 5 routes and a default route, 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
wan1Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB
h1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
h2Alpine 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 06 - Border leaf with type 5 routes and a default route 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.