HCIA-Datacom lab 16 of 22
IPv6 addressing with SLAAC and DHCPv6
Bring IPv6 up on two routers and two LANs. You read link-local and global addresses and the neighbour table, let a PC configure itself with SLAAC, hand out DNS with stateless DHCPv6 and whole addresses with stateful DHCPv6, and join the LANs with IPv6 static routes.
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 16 - IPv6 addressing with SLAAC and DHCPv6
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 4 vCPU, 7,168 MB
- Smallest plan
- Lite
The scenario
Northwind is starting its IPv6 roll-out with a pilot: HQ (R1) and a branch (R2). PC1 at HQ should configure itself automatically, and the branch's Client should get a fully managed address. The ISP gave Northwind 2001:DB8::/32 (the documentation prefix) and the team carved /64s from it:
| Segment | Prefix | Router address | Address assignment |
|---|---|---|---|
| LAN A (R1 GE0/0/1 – PC1) | 2001:DB8:10::/64 | 2001:DB8:10::1 | SLAAC, plus DNS by stateless DHCPv6 |
| Link (R1 GE0/0/0 – R2 GE0/0/0) | 2001:DB8:12::/64 | R1 ::1, R2 ::2 | static |
| LAN B (R2 GE0/0/1 – Client) | 2001:DB8:20::/64 | 2001:DB8:20::1 | stateful DHCPv6 |
| DNS server (for the options) | 2001:DB8::53 | – | – |
What you’ll practise
- Read IPv6 addresses: global unicast, link-local (FE80::/10), EUI-64 interface IDs, prefix lengths
- Enable IPv6 on VRP and configure global and link-local addresses
- Explain NDP (NS/NA/RS/RA) and read display ipv6 neighbors
- Configure SLAAC, stateless DHCPv6 (O flag) and stateful DHCPv6 (M flag)
- Configure IPv6 static routes
The tasks
- Task 0: Load the starting configuration
- Task 1: Turn IPv6 on and look at link-local addresses
- Task 2: Global addresses and neighbours
- Concept: how hosts get addresses
- Task 3: SLAAC for PC1
- Task 4: Stateless DHCPv6 for DNS
- Task 5: Stateful DHCPv6 for the branch
- Task 6: IPv6 static routes
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 - R1
GE0/0/1to PC1eth0 - R2
GE0/0/1to ClientGE0/0/1
| 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 |
| Client | 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
16 - IPv6 addressing with SLAAC and DHCPv6and 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.