CloudLabBox
Try the free demo

JNCIS-SP lab 15 of 16

Troubleshooting MPLS and Layer 2

Seven faults between a customer VLAN and a far site: a blocked port, a missing VLAN, a misplaced gateway, then LSPs that fail for four different reasons.

Run this lab

It needs Standard: its 6 nodes are set to 11 vCPU and 15,104 MB in total.

In your workspace: Shared, then JNCIS-SP JN0-364 guided labs, then 15 - Troubleshooting MPLS and Layer 2

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 11 vCPU and 15,104 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 90 minutes
Nodes need
11 vCPU, 15,104 MB
Smallest plan
Standard

The scenario

Malton (H1) has lost contact with York (H2). A customer VLAN reaches PE1 over a trunk from SW1, PE1 is the VLAN's gateway, and an RSVP LSP in each direction carries the traffic over P, which runs no BGP. Last night's "harmless" change left seven faults on PE1, P and PE2. SW1 and the hosts are correct, and so is IS-IS. Work outwards from H1, using the design sheet.

Design sheetValue
SW1 to PE1802.1Q trunk, VLANs 100 and 200, on ge-0/0/2. This is a switch link, not an edge port
VLAN 100Bridge domain V100, gateway irb.100, 192.168.1.1/24
H1192.168.1.10/24 in VLAN 100
CorePE1 10.255.0.1, P 10.255.0.2, PE2 10.255.0.3. IS-IS Level 2
LinksPE1 to P 10.0.12.0/30, P to PE2 10.0.23.0/30
MPLSAll core links carry MPLS and RSVP
LSP TO-PE2From PE1 to 10.255.0.3, strict through 10.0.12.2 then 10.0.23.2
LSP TO-PE1From PE2 to 10.255.0.1
BGPAS 64510, PE1 to PE2. Each advertises its LAN
H2192.168.2.10/24, gateway 192.168.2.1

What you’ll practise

  • Find and clear a BPDU block
  • Trace a VLAN from trunk to IRB
  • Read why an LSP is down, from CSPF to RSVP
  • Check both directions of an LSP

The tasks

  1. From H1 to its gateway
  2. The LSP from PE1
  3. The way back

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 Troubleshooting MPLS and Layer 26 nodes, 5 links. Every link is listed as text below the diagram.H1SW1PE1PPE2H2eth0Gi0/1ge-0/0/2eth0Gi0/0ge-0/0/2ge-0/0/1ge-0/0/0ge-0/0/0ge-0/0/0
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • H1 eth0 to SW1 Gi0/1
  • SW1 Gi0/0 to PE1 ge-0/0/2
  • PE1 ge-0/0/0 to P ge-0/0/0
  • P ge-0/0/1 to PE2 ge-0/0/0
  • PE2 ge-0/0/2 to H2 eth0
Nodes in Troubleshooting MPLS and Layer 2, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
H1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
SW1Cisco IOSvL2viosl2-adventerprisek9-m.ssa.high_iron_202009291 vCPU, 768 MB
PE1Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
PJuniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 3,584 MB
PE2Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 3,584 MB
H2VPCS 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 JNCIS-SP JN0-364 guided labs.

  3. Open 15 - Troubleshooting MPLS and Layer 2 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 JNCIS-SP labs

All JNCIS-SP labs

Related labs in other courses

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