HCIP-Datacom Core lab 14 of 14
Capstone - a carrier core for a two-site customer
Build it all from bare addresses: IS-IS and LDP in the core, a VPNv4 route reflector, one site on OSPF and one on BGP, route filtering, a VRRP gateway pair that follows BFD, and a real failover test.
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 14 - Capstone - a carrier core for a two-site customer
- Level
- Advanced
- Time
- About 150 minutes
- Nodes need
- 8 vCPU, 14,336 MB
- Smallest plan
- Standard
The scenario
You're the lead engineer on Northwind Carrier's first big customer. The racks are cabled and addressed, and nothing else is done. The customer has two sites. Bristol's router speaks OSPF only. Cardiff has two routers for resilience, speaks BGP, and has been promised that its LAN gateway survives a fault inside the carrier. You've got a list of requirements and no step-by-step. Plan it, build it from the bottom up, and test it.
| Device | Addresses |
|---|---|
| PE1 | LoopBack0 1.1.1.1, GE0/0/0 10.0.12.1/24, GE0/0/1 172.16.1.1/24 (VPN, to CE1) |
| P | LoopBack0 2.2.2.2, GE0/0/0 10.0.12.2/24, GE0/0/1 10.0.23.2/24 |
| PE2 | LoopBack0 3.3.3.3, GE0/0/0 10.0.23.3/24, GE0/0/1 172.16.2.1/24 (VPN, to CE2), GE0/0/2 172.16.3.1/24 (VPN, to CE3) |
| CE1 | LoopBack0 11.11.11.11, GE0/0/0 172.16.1.2/24, GE0/0/1 192.168.1.1/24 (PC1 .10), LoopBack9 10.99.0.1/24 (test network) |
| CE2 | LoopBack0 22.22.22.22, GE0/0/0 172.16.2.2/24, GE0/0/1 192.168.2.2/24 |
| CE3 | LoopBack0 33.33.33.33, GE0/0/0 172.16.3.2/24, GE0/0/1 192.168.2.3/24 |
| PC2 | 192.168.2.10, gateway 192.168.2.254 |
The customer-facing interfaces on the PEs are left empty, because binding to a VPN instance clears addresses. Add them from this table.
This lab doesn't cover multicast or IPv6: they have labs of their own, and a customer VPN carrying them is a bigger job than this.
What you’ll practise
- Plan and build a working carrier core with a route reflector
- Connect one site with OSPF and one with eBGP, in the same VPN
- Control routes with route policies at the PE and the CE
- Keep a gateway pair honest with VRRP and BFD
- Prove the design with a failure, and with traffic
The tasks
- Task 0: Load the starting configuration
- Concept: plan first
- Task 1: Requirement 1: core routing
- Task 2: Requirement 2: label switching
- Task 3: Requirement 3: VPNv4 with a route reflector
- Task 4: Requirement 4: the customer VPN
- Concept: OSPF as a PE to CE protocol
- Task 5: Requirement 5: Bristol on OSPF
- Task 6: Requirement 6: Cardiff on BGP
- Task 7: Requirement 7: the Cardiff gateway
- Task 8: Requirement 8: test the promise
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
- PE1
GE0/0/0to PGE0/0/0 - P
GE0/0/1to PE2GE0/0/0 - PE1
GE0/0/1to CE1GE0/0/0 - PE2
GE0/0/1to CE2GE0/0/0 - PE2
GE0/0/2to CE3GE0/0/0 - CE1
GE0/0/1to PC1eth0 - CE2
GE0/0/1to CARDIFF (network) - CE3
GE0/0/1to CARDIFF (network) - PC2
eth0to CARDIFF (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| PE1 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| P | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| PE2 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| CE1 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| CE2 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| CE3 | 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
14 - Capstone - a carrier core for a two-site customerand 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.