HCIA-Datacom lab 17 of 22

Dual stack with OSPFv3

Add IPv6 to a working IPv4 OSPF network and route it with OSPFv3. You run the two protocols side by side, compare how OSPFv3 forms neighbours and builds routes over link-local addresses, read its new LSA types, and originate an IPv6 default route.

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 17 - Dual stack with OSPFv3

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Advanced
Time
About 55 minutes
Nodes need
4 vCPU, 7,168 MB
Smallest plan
Lite

The scenario

The IPv6 pilot (lab 16) went well, so Northwind is going dual-stack on the core. R1, R2 and R3 already route IPv4 with OSPF. You'll add IPv6 to every link, run OSPFv3 next to OSPFv2 so that both families are routed independently, and let R3, the internet edge, hand out an IPv6 default route.

Link or LANIPv4 (running)IPv6 (to add)
R1 – R210.0.12.0/242001:DB8:12::/64 (R1 ::1, R2 ::2)
R2 – R310.0.23.0/242001:DB8:23::/64 (R2 ::2, R3 ::3)
HQ LAN (R1 GE0/0/1, PC1)192.168.1.0/242001:DB8:1::/64 (R1 ::1, PC1 by SLAAC)
Loopbacks1.1.1.1 / 2.2.2.2 / 3.3.3.32001:DB8::1 / ::2 / ::3 (/128)
R3 LoopBack2 (the IPv6 internet, not in OSPFv3)–2001:DB8:FFFF::1/128

What you’ll practise

  • Configure dual-stack interfaces alongside an existing IPv4 OSPF network
  • Enable OSPFv3 with an explicit router ID and per-interface area commands
  • Explain why OSPFv3 neighbours and next hops use link-local addresses
  • Read display ospfv3 peer, display ospfv3 lsdb and the OSPFv3 routes
  • Originate an IPv6 default route with default-route-advertise

The tasks

  1. Load the starting configuration
  2. Go dual-stack
  3. Start OSPFv3
  4. Read OSPFv3
  5. An IPv6 default route from the edge
  6. Compare the tables

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 Dual stack with OSPFv34 nodes, 3 links. Every link is listed as text below the diagram.R1R2R3PC1GE0/0/1eth0GE0/0/0GE0/0/0GE0/0/1GE0/0/1
4 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in Dual stack with OSPFv3, 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
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 17 - Dual stack with OSPFv3 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.