MikroTik MTCINE lab 6 of 12
MPLS and LDP with PHP and MPLS traceroute
Turn Fernvale's four-router OSPF core into an MPLS network with LDP. Read label bindings and the forwarding table, follow a packet through push, swap and pop, see penultimate-hop popping and switch it to explicit null, read labels in traceroute, and bind a label by hand.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 1,024 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCINE RouterOS v7 guided labs, then 06 - MPLS and LDP with PHP and MPLS traceroute
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 4 vCPU, 1,024 MB
- Smallest plan
- Lite
The scenario
Fernvale is about to sell layer 2 and layer 3 VPNs, and both need an MPLS core. The four core routers already run OSPF. In this lab you switch them to MPLS with LDP and learn to read what MPLS does, before labs 7 to 12 build services on top of it. PE1 and PE2 are the provider edge routers where customers will connect; P1 and P2 are provider (core) routers.
| Router | Role | Loopback (LSR ID) | Links |
|---|---|---|---|
| PE1 | edge | 10.255.255.1 | ether1 10.0.12.1/30 · lan 192.168.1.1/24 |
| P1 | core | 10.255.255.2 | ether1 10.0.12.2/30 · ether2 10.0.23.1/30 |
| P2 | core | 10.255.255.3 | ether1 10.0.23.2/30 · ether2 10.0.34.1/30 |
| PE2 | edge | 10.255.255.4 | ether1 10.0.34.2/30 · lan 192.168.4.1/24 |
What you’ll practise
- Explain labels, FECs, LSRs and LERs, and the push, swap and pop operations
- Enable LDP with loopback LSR IDs and transport addresses, and read neighbours, mappings and the forwarding table
- Explain penultimate-hop popping, implicit null and explicit null
- Read MPLS labels in traceroute and explain how TTL propagation changes what traceroute shows
- Create a static label mapping and see LDP advertise it
The tasks
- A plain IP path first
- Bring up LDP
- Read the label tables
- Penultimate-hop popping
- Traceroute through MPLS
- Explicit null
- A label by hand
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
- PE1
ether1to P1ether1 - P1
ether2to P2ether1 - P2
ether2to PE2ether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| PE1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| P1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| P2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| PE2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
MikroTik MTCINE RouterOS v7 guided labs.Open
06 - MPLS and LDP with PHP and MPLS tracerouteand 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 MikroTik MTCINE labs
Related labs in other courses
CloudLabBox is independent of MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.