HCIP-Datacom Core lab 1 of 14
OSPF in depth - LSAs and special areas
Read every OSPF LSA type on a running three-area network, then shrink the databases with a stub area, a totally stubby area and an NSSA, and watch each LSA disappear or change type.
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 01 - OSPF in depth - LSAs and special areas
- Level
- Intermediate
- Time
- About 70 minutes
- Nodes need
- 6 vCPU, 10,240 MB
- Smallest plan
- Standard
The scenario
Northwind has outgrown its flat OSPF network. The team has split it into three areas: the Bristol depot (area 1), the core (area 0) and the Leeds warehouse (area 2), which also has a partner link. Depot routers are small, so they shouldn't carry routes they will never choose. You start with all three as normal areas, read what OSPF is really storing, and then cut each database down to what that area needs.
| Router | LoopBack0 (router ID) | GE0/0/0 | GE0/0/1 | Area of each interface |
|---|---|---|---|---|
| R1 | 1.1.1.1 | 10.0.12.1/24 | 192.168.1.1/24 (PC1 .10) | All in area 1 |
| R2 (ABR) | 2.2.2.2 | 10.0.12.2/24 | 10.0.23.2/24 | GE0/0/0 area 1, the rest area 0 |
| R3 (ABR) | 3.3.3.3 | 10.0.23.3/24 | 10.0.34.3/24 | GE0/0/1 area 2, the rest area 0 |
| R4 (ASBR) | 4.4.4.4 | 10.0.34.4/24 | 192.168.4.1/24 (PC2 .10) | All in area 2, plus LoopBack9 203.0.113.1/24 (the partner network, imported) |
What you’ll practise
- Name the LSA types and say who creates each one and how far it floods
- Read display ospf lsdb and tie each row to a router or a route
- Configure stub and totally stubby areas and explain what each removes
- Configure an NSSA and follow a Type 7 LSA through translation to Type 5
- Prove reachability after each change with a real ping
The tasks
- Task 0: Load the starting configuration
- Concept: what each LSA is for
- Task 1: Read a normal multi-area database
- Concept: stub areas
- Task 2: Make area 1 a stub area
- Concept: totally stubby
- Task 3: Make area 1 totally stubby
- Concept: NSSA
- Task 4: Turn area 2 into an NSSA
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.
Every link, as text
- R1
GE0/0/0to R2GE0/0/0 - R2
GE0/0/1to R3GE0/0/0 - R3
GE0/0/1to R4GE0/0/0 - R1
GE0/0/1to PC1eth0 - R4
GE0/0/1to PC2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| R2 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| R3 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| R4 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
HCIP-Datacom Core H12-821 guided labs.Open
01 - OSPF in depth - LSAs and special areasand 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
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.