JNCIP-ENT lab 17 of 19
EVPN VXLAN and ESI multihoming
Stretch a VLAN across a routed fabric with EVPN-VXLAN, read route types 1 to 4 as they appear, dual-home a switch with an all-active ESI LAG, and fail a link.
Run this lab
It needs Professional: its 6 nodes are set to 15 vCPU and 18,176 MB in total.
In your workspace: Shared, then JNCIP-ENT JN0-650 guided labs, then 17 - EVPN VXLAN and ESI multihoming
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 15 vCPU, 18,176 MB
- Smallest plan
- Professional
The scenario
Northmere's data centre has grown past one spanning tree. You'll stretch a VLAN across a routed fabric with EVPN-VXLAN: the routed underlay stays simple, VXLAN carries Ethernet frames over it, and BGP EVPN tells each switch where every MAC address is. You'll read each EVPN route type as it appears, and then dual-home a server switch with no MLAG or spanning tree between the two leaves.
| Device | Interface | Address |
|---|---|---|
| LEAF1 | lo0, ge-0/0/0, ge-0/0/1 | 10.255.0.1/32, 10.1.12.1/30, 10.1.13.1/30 |
| LEAF2 | lo0, ge-0/0/0, ge-0/0/1 | 10.255.0.2/32, 10.1.12.2/30, 10.1.23.1/30 |
| LEAF3 | lo0, ge-0/0/0, ge-0/0/1 | 10.255.0.3/32, 10.1.13.2/30, 10.1.23.2/30 |
| LEAF1, LEAF2 | ge-0/0/4 | To CE1, a Cisco switch with Po1 on two links, which is ready |
| LEAF3 | ge-0/0/2 | To H2, access V100 |
| H1 | eth0 | 10.100.0.11/24, behind CE1 in VLAN 100 |
| H2 | eth0 | 10.100.0.12/24 |
OSPF already runs in the underlay. All three switches are in AS 64600. These images print requires 'bgp' license and requires 'vxlan' license warnings, and they don't stop anything here.
What you’ll practise
- Configure an iBGP EVPN overlay
- Map a VLAN to a VNI
- Explain EVPN route types 1, 2, 3 and 4
- Configure all-active multihoming
- Read a designated forwarder election and mass withdrawal
The tasks
- Map a VLAN to a VNI
- Bring up the EVPN overlay and read type 3
- Dual-home CE1 with an ESI LAG
- Read type 2 and the data path
- Fail a leaf link
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
- LEAF1
ge-0/0/0to LEAF2ge-0/0/0 - LEAF1
ge-0/0/1to LEAF3ge-0/0/0 - LEAF2
ge-0/0/1to LEAF3ge-0/0/1 - LEAF1
ge-0/0/4to CE1Gi0/0 - LEAF2
ge-0/0/4to CE1Gi0/1 - CE1
Gi0/2to H1eth0 - LEAF3
ge-0/0/2to H2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| LEAF1 | Juniper vJunos-switch | vjunosswitch-23.4R2-S2.1 | 4 vCPU, 5,120 MB |
| LEAF2 | Juniper vJunos-switch | vjunosswitch-23.4R2-S2.1 | 4 vCPU, 5,120 MB |
| LEAF3 | Juniper vJunos-switch | vjunosswitch-23.4R2-S2.1 | 4 vCPU, 5,120 MB |
| CE1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 768 MB |
| H1 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| H2 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIP-ENT JN0-650 guided labs.Open
17 - EVPN VXLAN and ESI multihomingand 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 JNCIP-ENT labs
Related labs in other courses
CloudLabBox is independent of Cisco and Juniper Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.