7 hands-on Dual Stack scenarios you build in your own Cisco Modeling Labs instance and grade against the answer key. Dual Stack configuration and troubleshooting practice for CCNA and CCNP.
Build an enterprise-clean dual-stack site end-to-end. IPv4 is complete and forwarding on day start; you will deploy IPv6 across the same topology. Enable IPv6 routing, assign prefixes, bring up OSPFv3 with explicit router-ids, keep the access LAN autoconfiguring via SLAAC with stateless DHCPv6 for DNS, and enforce an IPv6 ACL to allow one client flow to the server while denying another. Verify from the hosts and troubleshoot like a real operator.
Deploy a stateless DHCPv6 service on a remote router and relay client Information-Requests from a branch LAN across a routed core to that server. IPv4 is already fully functional; your job is to build the IPv6 DHCPv6 relay path and confirm clients receive DNS/domain options while keeping IPv6 addressing via SLAAC.
Build a compact dual-stack enterprise topology where IPv4 is already forwarding end-to-end using OSPFv2. Your task is to bring up IPv6 routing in parallel using OSPFv3 with explicit router-ids, proving that IPv6 control/data planes operate independently from IPv4. Verify both protocols resolve separately and that an IPv4 control-plane failure does not impact IPv6 forwarding.
Build a compact branch-to-edge topology that is dual-stack for IPv4 and intentionally incomplete for IPv6. IPv4 is fully working as a baseline. Your job: enable IPv6 forwarding on both routers, replace specific IPv6 routes at the branch with a single default (::/0) toward the edge, and add a specific IPv6 return route on the edge back to the branch LAN. Verify the branch host reaches the edge-side resources over IPv6 while the IPv4 plane remains stable.
Dual-stack enterprise lab with two routers, a shared access switch, and two hosts in separate VLANs. IPv4 is fully working via static routes in the starter. Your task is to add IPv6 static routes on both routers so the clients can communicate end-to-end over IPv6. Learn why a link-local next hop on a point-to-point link requires specifying the exit interface.
Bring IPv6 up alongside the already-working IPv4 baseline. You will enable IPv6 unicast routing on both routers, put a unique 2001:db8::/64 on each site LAN, put a /127 on the router-to-router transit, and address the dual-homed workstation on both of the LANs it is plugged into plus its IPv6 default route. Verify that IPv6 reaches both on-link gateways and, through the default route, the near router's transit address — while the far router's transit address stays unreachable over IPv6 and reachable over IPv4, because no IPv6 routing between the sites exists yet.
Configure and verify dual-stack IPv4 and IPv6 addressing on Cisco IOS router interfaces. R1-R2 share a /30 IPv4 and /64 IPv6 point-to-point transit, while R1 provides a dual-stack user LAN gateway. No routing protocols or router static routes are permitted; verify only directly connected reachability.
