IntermediatePublished 2026-06-25
CCNA IPv6 Static & Default Routing End-to-End Practice
Bundle lab
Hands-on IPv6 static and default routing across a 3-router, 2-LAN topology with end-user hosts. You will enable IPv6 unicast routing, apply IPv6 addressing, configure hub-and-spoke static and default routes, and validate bidirectional host reachability. The guide provides scenario context, step-by-step tasks with the why behind each action, and targeted troubleshooting.
Learning objectives
- Enable IPv6 unicast routing on IOS routers
- Apply IPv6 addressing to LAN and point-to-point transit links
- Configure IPv6 static routes using next-hop global unicast addresses
- Set IPv6 default routes (::/0) from branches to the hub
- Validate static-route installation and end-to-end IPv6 reachability from hosts
- Troubleshoot missing return routes, wrong next-hops, and default-route preference
Troubleshooting focus
- CLIENT-A cannot reach CLIENT-B (or the reverse) while the branch default route looks fine: RTR-HQ is missing the return path. Add a /64 static route toward that branch's LAN via the correct branch next-hop.
- Traceroute6 stalls at the hub although
show ipv6 routelooks normal: a static route points at a black hole. Each next-hop must be the neighbour's address on the directly attached transit — not a local address or an interface-only route. - Branches have no::/0 and pings to the remote LAN fail immediately: confirm
ipv6 unicast-routingis enabled globally on the router first, then that the default route uses the hub's correct global unicast next-hop on the transit subnet. - No Layer-3 reachability at all despite correct routes: confirm both ends of each transit are up and share the exact same /64, and that cabling on Ethernet0/0 and Ethernet0/1 aligns with the documented plan.
Topology
Subscribe to preview this lab's topology.
See plansGrade your work
How this lab is graded
- Build it your way. Where a lab lets you choose a value — a VLAN name, an interface description — grading checks that you configured it, not which name you picked. Names that another line has to reference, like an ACL applied with
access-class, are stated in the guide and do have to match. - Addresses, modes and protocol keywords are exact. An IP address, a subnet mask,
switchport mode trunk, an encapsulation — these carry the meaning of the lab, so they are graded as written in the guide. - Grading reads your saved configuration. Export the lab from CML after you have configured it, and make sure anything you set is in the running-config — a change that only exists in a terminal session never reaches the grader.
- You can submit as many times as you like. Your best score stands, and each attempt tells you which checks passed so you can work the gaps.
- Scored something you believe is correct? Use Report an issue on this page — that is exactly how the grading fixes in the changelog got found.
Create a free account to submit your lab for grading.
Create a free accountFound a problem with this lab?
Please sign in to report a problem — tying it to your attempts lets us reproduce and fix it faster.