HCIA-Datacom lab 3 of 22
Static and default routes with floating backups
Route between an HQ LAN and a branch LAN through a core router with static routes, send everything else to a default route, then add a floating static route over a backup link and prove it takes over when the primary link fails.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 7,168 MB in total. That fits the free demo too.
In your workspace: Shared, then HCIA-Datacom H12-811 guided labs, then 03 - Static and default routes with floating backups
- Level
- Beginner
- Time
- About 55 minutes
- Nodes need
- 4 vCPU, 7,168 MB
- Smallest plan
- Lite
The scenario
Northwind's HQ router R1 reaches the branch router R3 through the core router R2. A cheaper backup link joins R1 and R3 directly. The ISP hands over at R2, whose LoopBack1 (203.0.113.0/24) stands in for the internet, and R3's LoopBack1 (192.168.30.0/24) is the branch LAN. There is no dynamic routing yet: you'll build the whole design with static routes, then make the backup link take over automatically if the primary path fails.
| Link or LAN | Network | Addresses |
|---|---|---|
| HQ LAN | 192.168.10.0/24 | R1 GE0/0/1 .1, PC1 .10 |
| R1–R2 (primary) | 10.0.12.0/24 | R1 .1, R2 .2 |
| R2–R3 (primary) | 10.0.23.0/24 | R2 .2, R3 .3 |
| R1–R3 (backup) | 10.0.13.0/24 | R1 GE0/0/2 .1, R3 GE0/0/2 .3 |
| Loopbacks | 10.0.1.1, 10.0.2.2, 10.0.3.3 /32 | R1, R2, R3 |
What you’ll practise
- Read a VRP routing table: destination, protocol, preference, cost, flags and next hop
- Configure static routes with a next hop, and a default route
- Build a floating static route with preference and test failover
- Configure equal-cost static routes for load sharing
- Explain why every path needs a return route
The tasks
- Task 0: Load the starting configuration
- Task 1: What can each router reach?
- Task 2: Static routes over the primary path
- Concept: default routes
- Task 3: Default routes to the internet
- Concept: floating static routes
- Task 4: A floating backup over the R1–R3 link
- Task 5: Fail the primary link
- Task 6: Equal-cost load sharing
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/1 - R1
GE0/0/2to R3GE0/0/2 - R1
GE0/0/1to PC1eth0
| 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 |
| PC1 | 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
HCIA-Datacom H12-811 guided labs.Open
03 - Static and default routes with floating backupsand 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
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.