CloudLabBox
Try the free demo

HCIP-Datacom Core lab 13 of 14

Troubleshooting MPLS VPN VRRP and BFD

A customer VPN is down and the Cardiff gateways are confused. Six planted faults, from the IGP under LDP up to BFD and VRRP: follow the layers, prove each one with its own command, and fix the lot.

Run this lab

It needs Standard: its 8 nodes are set to 8 vCPU and 14,336 MB in total.

In your workspace: Shared, then HCIP-Datacom Core H12-821 guided labs, then 13 - Troubleshooting MPLS VPN VRRP and BFD

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 8 vCPU and 14,336 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 100 minutes
Nodes need
8 vCPU, 14,336 MB
Smallest plan
Standard

The scenario

Northwind's customer in Bristol and Cardiff has no connection through VPN A, and the Cardiff gateways are behaving strangely. Last week's maintenance touched nearly every box and the ticket says only "various changes". The design hasn't changed. You have six faults to find, and every one of them breaks a different layer.

The design:

  • IGP: every core interface and loopback on PE1, P and PE2 is in IS-IS, Level-2, wide metrics.
  • LDP: every core link runs mpls and mpls ldp.
  • MP-BGP: PE1 and PE2 peer on loopbacks in AS 100, and the VPNv4 family is enabled on both.
  • VPN A: RD 100:1 and route target 100:1, export and import, on both PEs.
  • PE to CE: eBGP in VPN A, to CE1 (AS 65001), and CE2 and CE3 (AS 65002).
  • Cardiff LAN: VRRP group 1, virtual IP 192.168.2.254. CE2 is Master, priority 120, and CE3 stays at the default.
  • BFD: a static session between CE2 and PE2 on their link. CE2 local 20, remote 21. PE2 the reverse. If it fails, CE2 drops 30 in priority.
DeviceAddresses
PE1LoopBack0 1.1.1.1, GE0/0/0 10.0.12.1/24, GE0/0/1 172.16.1.1/24 (to CE1)
PLoopBack0 2.2.2.2, GE0/0/0 10.0.12.2/24, GE0/0/1 10.0.23.2/24
PE2LoopBack0 3.3.3.3, GE0/0/0 10.0.23.3/24, GE0/0/1 172.16.2.1/24 (to CE2), GE0/0/2 172.16.3.1/24 (to CE3)
CE1GE0/0/0 172.16.1.2/24, GE0/0/1 192.168.1.1/24 (PC1 .10)
CE2GE0/0/0 172.16.2.2/24, GE0/0/1 192.168.2.2/24
CE3GE0/0/0 172.16.3.2/24, GE0/0/1 192.168.2.3/24
PC2192.168.2.10, gateway 192.168.2.254

What you’ll practise

  • Troubleshoot an L3VPN in layers: IGP, LDP, MP-BGP, VPN instance, PE to CE
  • Find a missing LSP and say why it matters
  • Tell a BGP session fault from a missing address family
  • Compare route targets on two PEs
  • Trace a wrong VRRP Master back to a BFD session

The tasks

  • Task 0: Load the starting configuration
  • Concept: layers of an L3VPN
  • Task 1: Fix the IGP
  • Task 2: Fix LDP
  • Task 3: Fix MP-BGP
  • Task 4: Fix the one-way routes
  • Concept: reading VRRP faults
  • Task 5: Fix the virtual gateway
  • Concept: static BFD faults
  • Task 6: Fix who is Master

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 VPN VRRP and BFD8 nodes and 1 network, 9 links. Every link is listed as text below the diagram.PE1PPE2CE1CE2CE3PC1PC2CARDIFFeth0GE0/0/1GE0/0/1GE0/0/1eth0GE0/0/0GE0/0/0GE0/0/1GE0/0/0GE0/0/1GE0/0/0GE0/0/1GE0/0/0GE0/0/2GE0/0/0
8 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • PE1 GE0/0/0 to P GE0/0/0
  • P GE0/0/1 to PE2 GE0/0/0
  • PE1 GE0/0/1 to CE1 GE0/0/0
  • PE2 GE0/0/1 to CE2 GE0/0/0
  • PE2 GE0/0/2 to CE3 GE0/0/0
  • CE1 GE0/0/1 to PC1 eth0
  • CE2 GE0/0/1 to CARDIFF (network)
  • CE3 GE0/0/1 to CARDIFF (network)
  • PC2 eth0 to CARDIFF (network)
Nodes in Troubleshooting MPLS VPN VRRP and BFD, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
PE1Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
PHuawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
PE2Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
CE1Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
CE2Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
CE3Huawei 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 13 - Troubleshooting MPLS VPN VRRP and BFD 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.