VXLAN EVPN lab 10 of 14
Junos EVPN-VXLAN with edge-routed bridging
Add a Juniper vJunos-switch leaf to a Cumulus and Arista fabric: a loopback overlay session, a stretched VLAN and type 5 routing across three vendors.
Run this lab
It needs Standard: its 7 nodes are set to 10 vCPU and 12,800 MB in total.
In your workspace: Shared, then VXLAN EVPN fabrics guided labs, then 10 - Junos EVPN-VXLAN with edge-routed bridging
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 10 vCPU, 12,800 MB
- Smallest plan
- Standard
The scenario
Calder Freight has bought a rack of Juniper switches, so a third vendor joins the fabric. You'll add leaf4, running Junos, to a working Cumulus and Arista fabric, using edge-routed bridging (ERB): each leaf is the gateway for its own hosts, which is what you've been building all along under the name symmetric IRB.
Junos differs from the others in one way that matters: it wants its EVPN session on the loopback.
| Node | AS | Loopback | Role |
|---|---|---|---|
| spine1 (vEOS) | 65000 | 10.255.0.1 | Spine |
| leaf1 (Cumulus) | 65001 | 10.255.0.11 | VLAN 10, h1 10.10.10.11 |
| leaf3 (vEOS) | 65003 | 10.255.0.13 | VLAN 20, h3 10.20.20.13 |
| leaf4 (vJunos-switch) | 65004 | 10.255.0.14 | VLAN 10, h4 10.10.10.14 on ge-0/0/1 |
| Item | Value |
|---|---|
| VLAN 10 | VNI 10010, RT 65000:10010, gateway 10.10.10.1/24 |
| VLAN 20 | Local to leaf3, gateway 10.20.20.1/24 |
| VRF RED | L3 VNI 50001, RT 65000:50001 |
| Anycast gateway MAC | 00:1c:73:00:00:01 |
| leaf4 fabric link | ge-0/0/0, 10.1.4.1/31 |
What you’ll practise
- Explain why Junos runs EVPN on a loopback session
- Configure VXLAN with switch-options and protocols evpn
- Build an ERB gateway with IRB and a routing instance
- Forward traffic across three vendors
The tasks
- Start the lab
- Move EVPN to a loopback session
- Add the layer 2 service
- Add routing
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
Ethernet3to leaf3Ethernet1 - spine1
Ethernet4to leaf4ge-0/0/0 - leaf1
swp3to h1eth0 - leaf3
Ethernet3to h3eth0 - leaf4
ge-0/0/1to h4eth0
| 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 |
| leaf3 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| leaf4 | Juniper vJunos-switch | vjunosswitch-23.4R2-S2.1 | 4 vCPU, 5,120 MB |
| h1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| h3 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| h4 | 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
10 - Junos EVPN-VXLAN with edge-routed bridgingand 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.