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
- 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.
| Node | Role | Details |
|---|---|---|
| spine1 | Spine | AS 65000 |
| leaf1 | Cumulus leaf | AS 65001, 10.255.0.11, VLAN 10 (10.10.10.0/24), h1 on swp3 |
| leaf2 | Cumulus leaf | AS 65002, 10.255.0.12, VLAN 20 (10.20.20.0/24), h2 on swp3 |
| leaf3 | vEOS border leaf | AS 65003, 10.255.0.13, VRF RED, L3 VNI 50001, Ethernet4 to the WAN |
| wan1 | IOSv WAN router | AS 65500, Gi0/0 10.99.0.1/30 |
| Address | Where | Why it matters |
|---|---|---|
| 10.99.0.2/30 | leaf3 Ethernet4 in VRF RED | The WAN link |
| 203.0.113.1 | wan1 Loopback0 | In BGP, so it arrives as a specific route |
| 198.51.100.1 | wan1 Loopback1 | Not 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
- Start the lab
- Peer with the WAN in the tenant VRF
- See the WAN route arrive as type 5
- Inject a default route
- 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.
Every link, as text
- spine1
Ethernet1to leaf1swp1 - spine1
Ethernet2to leaf2swp1 - spine1
Ethernet3to leaf3Ethernet1 - leaf1
swp3to h1eth0 - leaf2
swp3to h2eth0 - leaf3
Ethernet4to wan1Gi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| spine1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| leaf1 | NVIDIA Cumulus VX | cumulus-vx-5.9.1 | 1 vCPU, 2,048 MB |
| leaf2 | NVIDIA Cumulus VX | cumulus-vx-5.9.1 | 1 vCPU, 2,048 MB |
| leaf3 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| wan1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| h1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| h2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
VXLAN EVPN fabrics guided labs.Open
06 - Border leaf with type 5 routes and a default routeand 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
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.