CCNP ENARSI lab 21 of 35
MPLS LDP and Layer 3 VPN explorer
Build a three-router MPLS provider core with LDP, then deliver a Layer 3 VPN to two customers with overlapping addresses using VRFs, route distinguishers, route targets and MP-BGP, and watch the two-label stack in a traceroute.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 2,560 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 21 - MPLS LDP and Layer 3 VPN explorer
- Level
- Advanced
- Time
- About 80 minutes
- Nodes need
- 5 vCPU, 2,560 MB
- Smallest plan
- Lite
The scenario
You work for Peregrine Networks, a regional provider (AS 65000) with a three-router core: PE1, P and PE2. OSPF already runs in the core. Two customers want a private WAN between their two sites:
- Customer A has real routers at both sites: CE1 (AS 65011, LAN 192.168.1.0/24) and CE2 (AS 65012, LAN 192.168.2.0/24), which peer with your PEs using eBGP and are already configured.
- Customer B uses the same addresses (192.168.1.0/24 at site 1, 192.168.2.0/24 at site 2). In this lab, Customer B's sites are simulated by loopbacks on PE1 and PE2.
You'll turn on MPLS in the core, create one VRF per customer on each PE, and connect the PEs with MP-BGP so each customer's routes reach its other site and nobody else's.
| Device | Interface | Address | Notes |
|---|---|---|---|
| PE1 | Lo0 / Gi0/1 | 10.255.0.1/32 / 10.0.12.1/24 | core |
| P | Lo0 / Gi0/0 / Gi0/1 | 10.255.0.2/32 / 10.0.12.2/24 / 10.0.23.2/24 | core |
| PE2 | Lo0 / Gi0/1 | 10.255.0.3/32 / 10.0.23.3/24 | core |
| PE1 | Gi0/0 (VRF CUST-A) | 10.1.1.1/30 | to CE1 10.1.1.2 |
| PE2 | Gi0/0 (VRF CUST-A) | 10.2.2.1/30 | to CE2 10.2.2.2 |
| PE1 / PE2 | Lo20 (VRF CUST-B) | 192.168.1.1/24 / 192.168.2.1/24 | Customer B sites |
VRF plan: CUST-A RD 65000:1, route target 65000:1; CUST-B RD 65000:2, route target 65000:2.
What you’ll practise
- Enable MPLS with LDP and read LDP neighbours, label bindings and the LFIB
- Explain label push, swap and pop, penultimate hop popping and the LSP
- Configure VRFs with route distinguishers and route targets on provider-edge routers
- Exchange customer routes between PEs with MP-BGP VPNv4 and extended communities
- Show that the P router carries labels but no customer routes
The tasks
- Turn on MPLS with LDP in the core
- Create the customer VRFs on the PEs
- Connect the PEs with MP-BGP VPNv4
- Bring the customers into BGP
- Follow a packet across the provider
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
- CE1
Gi0/0to PE1Gi0/0 - PE1
Gi0/1to PGi0/0 - P
Gi0/1to PE2Gi0/1 - PE2
Gi0/0to CE2Gi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| CE1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| PE1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| P | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| PE2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| CE2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 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
CCNP ENARSI 300-410 guided labs.Open
21 - MPLS LDP and Layer 3 VPN explorerand 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 CCNP ENARSI labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.