CCNP Service Provider lab 9 of 23

MPLS LDP: protection, security and label filtering

Run LDP on an IOS XR core and make it safe: verify the label path with LSP ping, add an MD5 key, filter label allocation, and use IGP sync and session protection against failures.

Run this lab

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

In your workspace: Shared, then CCNP Service Provider guided labs, then 09 - MPLS LDP - protection security and label filtering

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 4 vCPU and 10,240 MB together. Every lab plan includes every guided lab.

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

The scenario

Fellgate Carrier's core now has a working IGP. The next step is label switching, so that the core doesn't need any customer routes. R1 to R4 run IS-IS. The path R1, R2, R4 is the main one, and the links through R3 have a metric of 20, so they carry traffic only after a failure.

You'll bring up LDP, then make it safe to run: a link failure shouldn't drop labels for longer than it has to, nobody should be able to join LDP without a key, and the routers shouldn't waste labels on prefixes no VPN needs.

DeviceInterfaceAddressConnects to
R1Loopback010.255.0.1/32
R1Gi0/0/0/010.0.12.1/30R2 Gi0/0/0/0
R1Gi0/0/0/110.0.13.1/30R3 Gi0/0/0/0
R2Loopback010.255.0.2/32
R2Gi0/0/0/010.0.12.2/30R1 Gi0/0/0/0
R2Gi0/0/0/110.0.24.1/30R4 Gi0/0/0/0
R3Loopback010.255.0.3/32
R3Gi0/0/0/010.0.13.2/30R1 Gi0/0/0/1
R3Gi0/0/0/110.0.34.1/30R4 Gi0/0/0/1
R4Loopback010.255.0.4/32
R4Gi0/0/0/010.0.24.2/30R2 Gi0/0/0/1
R4Gi0/0/0/110.0.34.2/30R3 Gi0/0/0/1

What you’ll practise

  • Bring up LDP and read labels and bindings
  • Verify a label-switched path with traceroute mpls
  • Authenticate LDP sessions
  • Filter local label allocation
  • Use LDP-IGP synchronisation
  • Keep a session through a link failure with session protection

The tasks

  1. Bring up LDP
  2. Follow a label path
  3. Authenticate LDP
  4. Allocate labels only where they're needed
  5. LDP-IGP synchronisation
  6. Session protection

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 - protection security and label filtering4 nodes, 4 links. Every link is listed as text below the diagram.R1R2R3R4Gi0/0/0/0Gi0/0/0/0Gi0/0/0/1Gi0/0/0/0Gi0/0/0/1Gi0/0/0/0Gi0/0/0/1Gi0/0/0/1
4 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in MPLS LDP: protection, security and label filtering, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 MB
R2Cisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 MB
R3Cisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 MB
R4Cisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 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 CCNP Service Provider guided labs.

  3. Open 09 - MPLS LDP - protection security and label filtering 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 CCNP Service Provider labs

All CCNP Service Provider 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.