CloudLabBox
Try the free demo

MikroTik MTCRE lab 12 of 14

MPLS, LDP and VPLS (MTCINE preview)

Go one step beyond MTCRE: label-switch Fernvale's OSPF core with MPLS and LDP, read label bindings and the forwarding table, then build a VPLS pseudowire that joins two customer sites at layer 2 across the core.

Run this lab

It needs Lite: its 5 nodes are set to 5 vCPU and 1,280 MB in total. That fits the free demo too.

In your workspace: Shared, then MikroTik MTCRE RouterOS v7 guided labs, then 12 - MPLS LDP and VPLS - MTCINE preview

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 60 minutes
Nodes need
5 vCPU, 1,280 MB
Smallest plan
Lite

The scenario

Harper Ltd (from lab 6) now wants its two sites joined on one layer-2 network, but Fernvale's new core is routed, not switched. The answer used by most ISPs is MPLS with VPLS: the core forwards labelled packets, and a pseudowire between the two provider edge routers (PE1, PE2) carries Harper's Ethernet frames. The core already runs OSPF between the loopbacks. Harper's routers CE1 and CE2 are on the same subnet, 10.50.0.0/24, and can't see each other yet.

RouterRoleLoopback / LSR IDCore links
PE1Provider edge, site A10.255.255.1ether1 10.0.12.1/30
PCore label switch10.255.255.210.0.12.2/30, 10.0.23.1/30
PE2Provider edge, site B10.255.255.3ether1 10.0.23.2/30

What you’ll practise

  • Explain labels, LSRs, label edge routers, LDP and penultimate-hop popping
  • Enable LDP with loopback LSR IDs and transport addresses
  • Read LDP neighbours, label bindings and the MPLS forwarding table
  • Build an LDP-signalled VPLS interface and bridge it to a customer port
  • Prove layer-2 connectivity between two sites over the pseudowire

The tasks

  1. Check the core
  2. Switch the core to labels with LDP
  3. Build the pseudowire with VPLS
  4. Look at what crossed the core

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 LDP and VPLS - MTCINE preview5 nodes, 4 links. Every link is listed as text below the diagram.CE1PE1PPE2CE2ether1ether2ether1ether1ether2ether1ether2ether1
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • CE1 ether1 to PE1 ether2
  • PE1 ether1 to P ether1
  • P ether2 to PE2 ether1
  • PE2 ether2 to CE2 ether1
Nodes in MPLS, LDP and VPLS (MTCINE preview), with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
CE1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PE1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PE2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
CE2MikroTik 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 MTCRE RouterOS v7 guided labs.

  3. Open 12 - MPLS LDP and VPLS - MTCINE preview 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 MTCRE labs

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