CloudLabBox
Try the free demo

HCIA-Datacom lab 21 of 22

Troubleshooting routing and services

HQ has lost the branch and the internet after a weekend change. Five faults hide across OSPF adjacencies, route advertisement, an ACL and NAT. You follow the packet hop by hop, prove each cause with display output, and restore the documented design.

Run this lab

It needs Standard: its 5 nodes are set to 5 vCPU and 9,216 MB in total.

In your workspace: Shared, then HCIA-Datacom H12-811 guided labs, then 21 - Troubleshooting routing and services

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 5 vCPU and 9,216 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 75 minutes
Nodes need
5 vCPU, 9,216 MB
Smallest plan
Standard

The scenario

Over the weekend, someone "hardened" Northwind's routers. On Monday morning PC1 at HQ (192.168.1.200) can't reach the branch server or the internet. Here is the documented design you must restore:

  1. OSPF: area 0 on every link and network of R1, R2 and R3. The R1–R2 link uses MD5 interface authentication, key ID 1, key Huawei@123.
  2. Advertising: R1 advertises the HQ LAN 192.168.1.0/24. R3 advertises the branch server 3.3.3.3, the Finance LAN 172.16.1.0/24, and a default route (it is the internet edge).
  3. Security policy (on R2): HQ may reach the branch server, but must not reach the Finance LAN.
  4. Internet: R3 translates every internal address (192.168.1.0/24 and 10.0.0.0/8) to its outside address (Easy IP) towards the ISP.

There are five faults. The ISP router and PC1 are configured correctly.

What you’ll practise

  • Troubleshoot OSPF adjacencies: authentication and area mismatches
  • Find missing routes caused by wrong network statements
  • Debug ACL logic that blocks more than intended
  • Find why NAT isn't translating a host, using the NAT ACL and session table
  • Work hop by hop and in both directions

The tasks

  1. Load the broken network
  2. The R1–R2 adjacency
  3. The R2–R3 adjacency
  4. The missing HQ LAN
  5. Still no branch server
  6. The internet
  7. Prove the design and write it up

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 routing and services5 nodes, 4 links. Every link is listed as text below the diagram.R1R2R3ISPPC1GE0/0/1eth0GE0/0/2GE0/0/0GE0/0/0GE0/0/0GE0/0/1GE0/0/1
5 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/1
  • R3 GE0/0/2 to ISP GE0/0/0
  • R1 GE0/0/1 to PC1 eth0
Nodes in Troubleshooting routing and services, 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
ISPHuawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
PC1VPCS 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 HCIA-Datacom H12-811 guided labs.

  3. Open 21 - Troubleshooting routing and services 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 HCIA-Datacom labs

All HCIA-Datacom 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.