HCIP-Datacom Core lab 10 of 14
IPv6 routing with OSPFv3 IS-IS and BGP
Connect two IPv6 domains: OSPFv3 on one side, IS-IS on the other, BGP4+ between them. Hosts use SLAAC, and a prefix filter keeps a management network private.
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 10 - IPv6 routing with OSPFv3 IS-IS and BGP
- Level
- Advanced
- Time
- About 85 minutes
- Nodes need
- 6 vCPU, 10,240 MB
- Smallest plan
- Standard
The scenario
The Bristol and Glasgow networks are going IPv6-only for a pilot. Bristol's team likes OSPF, and Glasgow's likes IS-IS, and neither is changing. They'll stay separate domains and exchange routes over BGP4+ between R2 and R3. Glasgow's management network, 2001:DB8:44::/64, must not reach Bristol. All addresses are set: you add the routing.
| Router | AS | LoopBack0 | GE0/0/0 | GE0/0/1 | Domain |
|---|---|---|---|---|---|
| R1 | 65001 | 2001:DB8:FF::1 | 2001:DB8:12::1/64 | 2001:DB8:1::1/64 (PC1, SLAAC) | OSPFv3 |
| R2 | 65001 | 2001:DB8:FF::2 | 2001:DB8:12::2/64 | 2001:DB8:23::2/64 | OSPFv3, BGP4+ |
| R3 | 65002 | 2001:DB8:FF::3 | 2001:DB8:23::3/64 | 2001:DB8:34::3/64 | IS-IS, BGP4+ |
| R4 | 65002 | 2001:DB8:FF::4 | 2001:DB8:34::4/64 | 2001:DB8:4::1/64 (PC2, SLAAC) | IS-IS |
R4's LoopBack1, 2001:DB8:44::1/64, is the management network.
What you’ll practise
- Run OSPFv3 per interface and read its peers and routes
- Add an IPv6 topology to IS-IS
- Build a BGP4+ session and activate the IPv6 address family
- Import IPv6 routes between BGP4+ and each IGP
- Filter BGP4+ advertisements with an IPv6 prefix list
The tasks
- Task 0: Load the starting configuration
- Concept: OSPFv3 differences
- Task 1: Run OSPFv3 on R1 and R2
- Concept: SLAAC
- Task 2: Give the PCs addresses
- Concept: IS-IS for IPv6
- Task 3: Run IS-IS on R3 and R4
- Concept: BGP4+
- Task 4: Build BGP4+ between R2 and R3
- Task 5: Import BGP4+ into each IGP
- Task 6: Keep Glasgow's management network out
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
10 - IPv6 routing with OSPFv3 IS-IS and BGPand 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.