CloudLabBox
Try the free demo

HCIP-Datacom Core lab 7 of 14

MPLS and LDP

Turn a routed core into an MPLS core: LSR IDs, LDP sessions, label tables, penultimate hop popping, LSP ping and trace, LSP triggers, explicit null and a remote LDP session.

Run this lab

It needs Standard: its 6 nodes are set to 6 vCPU and 10,240 MB in total.

In your workspace: Shared, then HCIP-Datacom Core H12-821 guided labs, then 07 - MPLS and LDP

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 6 vCPU and 10,240 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 75 minutes
Nodes need
6 vCPU, 10,240 MB
Smallest plan
Standard

The scenario

Northwind's carrier arm wants to offer VPNs across its core, and VPNs need label switching. Today R1 to R4 are plain routers running OSPF. You'll turn on MPLS and LDP across the four, then learn to read the label tables, because when a VPN breaks at 3 a.m. those tables are what you'll be looking at.

RouterLoopBack0 (LSR ID)GE0/0/0GE0/0/1
R11.1.1.110.0.12.1/24192.168.1.1/24 (PC1 .10)
R22.2.2.210.0.12.2/2410.0.23.2/24
R33.3.3.310.0.23.3/2410.0.34.3/24
R44.4.4.410.0.34.4/24192.168.4.1/24 (PC2 .10)

What you’ll practise

  • Enable MPLS and LDP globally and per interface
  • Read LDP sessions, peers and the label table
  • Follow one LSP hop by hop, including penultimate hop popping
  • Test an LSP with ping lsp and tracert lsp
  • Widen LSP creation with lsp-trigger and change PHP with explicit null
  • Build a remote LDP session

The tasks

  • Task 0: Load the starting configuration
  • Concept: labels and LDP
  • Task 1: Turn on MPLS and LDP
  • Concept: reading the label table
  • Task 2: Follow one LSP
  • Concept: LSP triggers
  • Task 3: Build LSPs for LAN routes too
  • Concept: explicit null
  • Task 4: Advertise explicit null from R4
  • Concept: remote LDP
  • Task 5: Build a remote LDP session between R1 and R4

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 LDP6 nodes, 5 links. Every link is listed as text below the diagram.R1R2R3R4PC1PC2GE0/0/1eth0GE0/0/1eth0GE0/0/0GE0/0/0GE0/0/1GE0/0/0GE0/0/1GE0/0/0
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 GE0/0/0 to R2 GE0/0/0
  • R2 GE0/0/1 to R3 GE0/0/0
  • R3 GE0/0/1 to R4 GE0/0/0
  • R1 GE0/0/1 to PC1 eth0
  • R4 GE0/0/1 to PC2 eth0
Nodes in MPLS and LDP, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
R2Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
R3Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
R4Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC2VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 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 HCIP-Datacom Core H12-821 guided labs.

  3. Open 07 - MPLS and LDP 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 HCIP-Datacom Core labs

All HCIP-Datacom Core labs

Related labs in other courses

CloudLabBox is independent of Huawei. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.