zNetLaB › Guided labs › Enterprise
IPv6 — two /64 segments across a routed link
Enterprise Intermediate 4 devices 5 checked tasks 100 points Plan lab
Address both LANs out of 2001:db8::/32, enable IPv6 unicast routing, and use a static route on each router so PC1 can reach PC2 over IPv6 alone. Watch Neighbor Discovery replace ARP in the trace. 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
Address both LANs out of 2001:db8::/32, enable IPv6 unicast routing, and use a static route on each router so PC1 can reach PC2 over IPv6 alone. Watch Neighbor Discovery replace ARP in the trace.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 5 goals show as passed (100 points).
Network status
Devices: 2 PCs, 2 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R1, R2 start 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
IPv6 unicast-routing is enabled on both routers (15 pts) Every router interface has a global address and a link-local (20 pts) R1 has a route to the far LAN 2001:db8:2::/64 (20 pts) R2 has a route back to 2001:db8:1::/64 (20 pts) PC1 can ping PC2 over IPv6 (25 pts)
The activity, in order
IPv6 unicast-routing is enabled on both routers Do what the title says on the device shown in the topology, then run the show command that proves it.Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Every router interface has a global address and a link-local Do what the title says on the device shown in the topology, then run the show command that proves it.Why: Each goal is a state the lab can check on the running device. Verify with: show running-config R1 has a route to the far LAN 2001:db8:2::/64 Do what the title says on the device shown in the topology, then run the show command that proves it.Why: Each goal is a state the lab can check on the running device. Verify with: show running-config R2 has a route back to 2001:db8:1::/64 Do what the title says on the device shown in the topology, then run the show command that proves it.Why: Each goal is a state the lab can check on the running device. Verify with: show running-config PC1 can ping PC2 over IPv6 From PC1, ping 2001:db8:2::10. If it fails, walk the path hop by hop: gateway, then each router’s routing table, then the way back.Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 2001:db8:2::10
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
Address both LANs out of 2001:db8::/32, enable IPv6 unicast routing, and use a static route on each router so PC1 can reach PC2 over IPv6 alone. Watch Neighbor Discovery replace ARP in the trace.
What you will be able to do
IPv6 unicast-routing is enabled on both routers
Every router interface has a global address and a link-local
R1 has a route to the far LAN 2001:db8:2::/64
R2 has a route back to 2001:db8:1::/64
The network
PC, ISR 4331 — 4 devices in all, already cabled.
Fa0 Gi0/0/0 Gi0/0/1 Gi0/0/1 Gi0/0/0 Fa0 PC1 R1 R2 PC2 Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
PC1 PC configure it
R1 ISR 4331 configure it
R2 ISR 4331 configure it
PC2 PC configure it
Cabling
PC1 Fa0 ↔ R1 Gi0/0/0
R1 Gi0/0/1 ↔ R2 Gi0/0/1
R2 Gi0/0/0 ↔ PC2 Fa0
What is configured at the start
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
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 IPv6 unicast-routing is enabled on both routers 15 Checked automatically against the device’s live state (ipv6Routing). and Checked automatically against the device’s live state (ipv6Routing).
2 Every router interface has a global address and a link-local 20 Checked automatically against the device’s live state (ipv6Ready). and Checked automatically against the device’s live state (ipv6Ready).
3 R1 has a route to the far LAN 2001:db8:2::/64 20 Checked automatically against the device’s live state (hasRoute6).
4 R2 has a route back to 2001:db8:1::/64 20 Checked automatically against the device’s live state (hasRoute6).
5 PC1 can ping PC2 over IPv6 25 On PC1: ping 2001:db8:2::10 must succeed.
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
interface g0/0/0
ipv6 address 2001:db8:1::1/64
no shutdown
exit
interface g0/0/1
ipv6 address 2001:db8:12::1/64
no shutdown
exit
ipv6 route 2001:db8:2::/64 2001:db8:12::2
R2 ipv6 unicast-routing
interface g0/0/0
ipv6 address 2001:db8:2::1/64
no shutdown
exit
interface g0/0/1
ipv6 address 2001:db8:12::2/64
no shutdown
exit
ipv6 route 2001:db8:1::/64 2001:db8:12::1
Where this is examined
This lab practises these topics in the zNetLaB certification courses:
Related labs
Where to start
The lessons are open to everyone, all guided labs are listed by track, and
plans explains what is free and what is not.
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.