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

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

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.

RouterRoleLoopback (LSR ID)Links
PE1edge10.255.255.1ether1 10.0.12.1/30 · lan 192.168.1.1/24
P1core10.255.255.2ether1 10.0.12.2/30 · ether2 10.0.23.1/30
P2core10.255.255.3ether1 10.0.23.2/30 · ether2 10.0.34.1/30
PE2edge10.255.255.4ether1 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

  1. A plain IP path first
  2. Bring up LDP
  3. Read the label tables
  4. Penultimate-hop popping
  5. Traceroute through MPLS
  6. Explicit null
  7. 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.

Topology of MPLS and LDP with PHP and MPLS traceroute4 nodes, 3 links. Every link is listed as text below the diagram.PE1P1P2PE2ether1ether1ether2ether1ether2ether1
4 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in MPLS and LDP with PHP and MPLS traceroute, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
PE1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
P1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
P2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PE2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder MikroTik MTCINE RouterOS v7 guided labs.

  3. Open 06 - MPLS and LDP with PHP and MPLS traceroute and 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

All 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.