zNetLaB › Guided labs › Enterprise
IPv6 hosts — SLAAC, stateless and stateful DHCPv6
Enterprise Intermediate 3 devices 4 checked tasks 100 points Plan lab
Two LANs, two ways for a host to get an IPv6 address. LAN A builds its own from the router advertisement and asks DHCPv6 only for DNS; LAN B is told by the M flag to take a managed address from a DHCPv6 pool instead. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
Two LANs, two ways for a host to get an IPv6 address. LAN A builds its own from the router advertisement and asks DHCPv6 only for DNS; LAN B is told by the M flag to take a managed address from a DHCPv6 pool instead.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 4 goals show as passed (100 points).
Network status
Devices: 1 router, 2 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R1 starts with an empty configuration. Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure. Goals
R1 routes IPv6 (15 pts) PC-A configures itself by SLAAC (30 pts) PC-A learns its DNS server by stateless DHCPv6 (25 pts) PC-B takes a managed address by stateful DHCPv6 (30 pts) The activity, in order
R1 routes IPv6 Why: Each goal is a state the lab can check on the running device. Verify with: show running-config PC-A configures itself by SLAAC Why: Each goal is a state the lab can check on the running device. Verify with: show running-config PC-A learns its DNS server by stateless DHCPv6 Why: Each goal is a state the lab can check on the running device. Verify with: show running-config PC-B takes a managed address by stateful DHCPv6 Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Why this matters
Two LANs, two ways for a host to get an IPv6 address. LAN A builds its own from the router advertisement and asks DHCPv6 only for DNS; LAN B is told by the M flag to take a managed address from a DHCPv6 pool instead.
What you will be able to do
R1 routes IPv6
PC-A configures itself by SLAAC
PC-A learns its DNS server by stateless DHCPv6
PC-B takes a managed address by stateful DHCPv6
The network
ISR 2911, PC — 3 devices in all, already cabled.
Gi0/0 Fa0 Gi0/1 Fa0 R1 PC-A PC-B Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R1 ISR 2911 configure it PC-A PC configure it PC-B PC configure it
Cabling
R1 Gi0/0 ↔ PC-A Fa0 R1 Gi0/1 ↔ PC-B Fa0
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
R1 interface g0/0
no shutdown
exit
interface g0/1
no shutdown
exit Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 R1 routes IPv6 15 Checked automatically against the device’s live state (ipv6Routing). 2 PC-A configures itself by SLAAC 30 Checked automatically against the device’s live state (host6). 3 PC-A learns its DNS server by stateless DHCPv6 25 Checked automatically against the device’s live state (host6Dns). 4 PC-B takes a managed address by stateful DHCPv6 30 Checked automatically against the device’s live state (host6).
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
R1 ipv6 unicast-routing
ipv6 dhcp pool LAN-A
dns-server 2001:db8::53
domain-name lab.local
exit
ipv6 dhcp pool LAN-B
address prefix 2001:db8:b::/64
dns-server 2001:db8::53
exit
interface g0/0
ipv6 address 2001:db8:a::1/64
ipv6 nd other-config-flag
ipv6 dhcp server LAN-A
exit
interface g0/1
ipv6 address 2001:db8:b::1/64
ipv6 nd managed-config-flag
ipv6 nd prefix 2001:db8:b::/64 2592000 604800 no-autoconfig
ipv6 dhcp server LAN-B
exit PC-A ipconfig /renew6 PC-B ipconfig /renew6 Where this is examined
This lab practises these topics in the zNetLaB certification courses:
Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.