15.6.1 Packet Tracer – Configure IPv4 and IPv6 Static and Default Routes – Instructions Answer

Edge_Router(config)#ip route 0.0.0.0 0.0.0.0 s0/0/0

Edge_Router(config)#ip route 0.0.0.0 0.0.0.0 s0/0/1 5

Edge_Router(config)#ipv6 route ::/0 2001:db8:a:1::1

Edge_Router(config)#ipv6 route ::/0 2001:db8:a:2::1 5

ISP1(config)#ip route 192.168.10.16 255.255.255.240 10.10.10.2

ISP1(config)#ip route 192.168.11.32 255.255.255.224 10.10.10.2

ISP1(config)#ip route 192.168.10.16 255.255.255.240 g0/0 5

ISP1(config)#ip route 192.168.11.32 255.255.255.224 g0/0 5

ISP1(config)#ipv6 route 2001:db8:1:10::/64 2001:db8:a:1::2

ISP1(config)#ipv6 route 2001:db8:1:11::/64 2001:db8:a:1::2

ISP1(config)#ipv6 route 2001:db8:1:10::/64 2001:db8:f:f::2 5

ISP1(config)#ipv6 route 2001:db8:1:11::/64 2001:db8:f:f::2 5

Edge_Router(config)#ip route 198.0.0.10 255.255.255.255 serial0/0/0

Edge_Router(config)#ip route 198.0.0.10 255.255.255.255 serial0/0/1 5

Edge_Router(config)#ipv6 route 2001:db8:f:f::10/128 2001:db8:a:1::1

Edge_Router(config)#ipv6 route 2001:db8:f:f::10/128 2001:db8:a:2::1 5

! ==============================================================
!--- 15.6.1 Packet Tracer - Configure IPv4 and IPv6 Static and Default Routes
!--- ANSWER SCRIPT FOR ROUTER EDGE_ROUTER
!--- Usage: from the console on Edge_Router, enter privileged EXEC mode with "enable", then paste this whole file. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- CRITICAL FIX: Part 1 explicitly asks for "directly connected" static default routes (exit-interface only), but the source Answer Scripts used next-hop IP addresses instead (the style that actually belongs to Part 2's IPv6 routes). Since both S0/0/0 (to ISP1) and S0/0/1 (to ISP2) are true point-to-point serial links, "directly connected" syntax is valid here and is what's actually being asked for - fixed below.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 1: IPv4 static and floating static DEFAULT routes ("directly connected" - exit interface only)
! --------------------------------------------------------------

!--- Primary default route via ISP1's serial link.
ip route 0.0.0.0 0.0.0.0 Serial0/0/0

!--- Floating default route via ISP2's serial link - AD 5 keeps it out of the routing table unless the primary (AD 1, the default for static routes) is unavailable.
ip route 0.0.0.0 0.0.0.0 Serial0/0/1 5

! --------------------------------------------------------------
!--- Part 2: IPv6 static and floating static DEFAULT routes ("next hop" - global unicast next-hop address)
! --------------------------------------------------------------

ipv6 route ::/0 2001:db8:a:1::1
ipv6 route ::/0 2001:db8:a:2::1 5

! --------------------------------------------------------------
!--- Part 5: Host routes to the customer server
! --------------------------------------------------------------

!--- IPv4 host routes ("directly connected") - /32 mask (255.255.255.255) matches exactly one address.
ip route 198.0.0.10 255.255.255.255 Serial0/0/0
ip route 198.0.0.10 255.255.255.255 Serial0/0/1 5

!--- IPv6 host route ("next hop") through ISP1 - /128 matches exactly one address.
ipv6 route 2001:db8:f:f::10/128 2001:db8:a:1::1

!--- IPv6 floating host route through ISP2. The Instructions' wording for this one ("directly connected... through the ISP2 router") is self-contradictory - "directly connected" style never references a next-hop router at all - so this follows the "next hop" pattern used consistently everywhere else for IPv6 in this lab, and matches "through the ISP2 router" literally.
ipv6 route 2001:db8:f:f::10/128 2001:db8:a:2::1 5

end

! --------------------------------------------------------------
!--- Operational habit (not explicitly required by this lab): save to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config

! ==============================================================
!--- Verification:
!---   Edge_Router# show ip route static   -> default routes via S0/0/0 (AD 1) and S0/0/1 (AD 5, absent unless S0/0/0 is down)
!---   Edge_Router# show ipv6 route static -> same pattern via the IPv6 next-hop addresses
!---   From PC-A or PC-B, ping the Customer Server (198.0.0.10 / 2001:db8:f:f::10) -> success
!---   Shut down S0/0/0 -> traffic fails over to the floating routes via S0/0/1; ping to the server still succeeds
! ==============================================================

! ==============================================================
!--- 15.6.1 Packet Tracer - Configure IPv4 and IPv6 Static and Default Routes
!--- ANSWER SCRIPT FOR ROUTER ISP1
!--- Usage: from the console on ISP1, enter privileged EXEC mode with "enable", then paste this whole file. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- The source Answer Scripts for ISP1 already matched the Instructions correctly - no fixes needed here. Note: the floating routes below use G0/0 (a shared Ethernet segment with ISP2 and the Customer Server) as a "directly connected" exit interface, per the Instructions' explicit wording - this only works because it's the sole path toward ISP2 in this topology; it's not general best practice on a multi-access link (see the lab's own disclaimer that this activity prioritizes route-type practice over ideal network design).
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Part 3, Step 1: IPv4 static routes to LAN 1 and LAN 2 ("next hop" through Edge_Router)
! --------------------------------------------------------------

ip route 192.168.10.16 255.255.255.240 10.10.10.2
ip route 192.168.11.32 255.255.255.224 10.10.10.2

! --------------------------------------------------------------
!--- Part 3, Step 2: IPv4 floating static routes to LAN 1 and LAN 2 ("directly connected" through ISP2)
! --------------------------------------------------------------

ip route 192.168.10.16 255.255.255.240 GigabitEthernet0/0 5
ip route 192.168.11.32 255.255.255.224 GigabitEthernet0/0 5

! --------------------------------------------------------------
!--- Part 4, Step 1: IPv6 static routes to LAN 1 and LAN 2 ("next hop" through Edge_Router)
! --------------------------------------------------------------

ipv6 route 2001:db8:1:10::/64 2001:db8:a:1::2
ipv6 route 2001:db8:1:11::/64 2001:db8:a:1::2

! --------------------------------------------------------------
!--- Part 4, Step 2: IPv6 floating static routes to LAN 1 and LAN 2 ("next hop" through ISP2)
! --------------------------------------------------------------

ipv6 route 2001:db8:1:10::/64 2001:db8:f:f::2 5
ipv6 route 2001:db8:1:11::/64 2001:db8:f:f::2 5

end

! --------------------------------------------------------------
!--- Operational habit (not explicitly required by this lab): save to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config

! ==============================================================
!--- Verification:
!---   ISP1# show ip route static   -> LAN1/LAN2 routes via 10.10.10.2 (AD 1); the GigabitEthernet0/0 floating routes (AD 5) only appear if S0/0/0 goes down
!---   ISP1# show ipv6 route static -> same pattern via the IPv6 next-hop addresses
! ==============================================================

! ==============================================================
!--- 15.6.1 Packet Tracer - Configure IPv4 and IPv6 Static and Default Routes
!--- ANSWER SCRIPT FOR ROUTER ISP2 (NOT explicitly requested by the Instructions or the source Answer Scripts - see the discrepancy note in chat before applying)
!--- Usage: from the console on ISP2, enter privileged EXEC mode with "enable", then paste this whole file. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- Why this exists: the Instructions never mention configuring ISP2 at all, and neither does the source Answer Scripts section. But ISP1's OWN floating routes (Part 3.2 / 4.2) send LAN1/LAN2-bound traffic out its G0/0 interface toward ISP2 whenever ISP1's direct link to Edge_Router is down - and ISP2 has no way to actually deliver that traffic without its own route back to LAN1/LAN2. Without this, the lab's own stated success criterion ("if the primary route link is down, connectivity... should still exist") cannot actually be satisfied for return traffic from the Customer Server.
! ==============================================================

enable
configure terminal

! --------------------------------------------------------------
!--- Routes to LAN 1 and LAN 2, via Edge_Router's S0/0/1 link ("next hop", matching ISP1's own primary-route style for the same kind of link)
! --------------------------------------------------------------

ip route 192.168.10.16 255.255.255.240 10.10.10.6
ip route 192.168.11.32 255.255.255.224 10.10.10.6
ipv6 route 2001:db8:1:10::/64 2001:db8:a:2::2
ipv6 route 2001:db8:1:11::/64 2001:db8:a:2::2

end

! --------------------------------------------------------------
!--- Operational habit (not explicitly required by this lab): save to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config

! ==============================================================
!--- Verification:
!---   ISP2# show ip route static / show ipv6 route static -> LAN1/LAN2 routes present via 10.10.10.6 / 2001:db8:a:2::2
!---   With S0/0/0 (Edge_Router<->ISP1) shut down, ping the Customer Server from PC-A/PC-B -> still succeeds, including the return path via ISP1's G0/0 floating route -> ISP2 -> S0/0/1 -> Edge_Router
! ==============================================================