CloudLabBox
Try the free demo

CCNA lab 41 of 46

Troubleshooting IPv4 and IPv6 addressing and static routes

Three sites, dual stack, static routes only, and seven faults: a wrong interface mask, a wrong gateway, a missing return route, a mistyped next hop, swapped administrative distances, IPv6 routing switched off and a mistyped IPv6 prefix. Find each with ping, traceroute and the routing tables.

Run this lab

It needs Lite: its 6 nodes are set to 6 vCPU and 6,144 MB in total. That fits the free demo too.

In your workspace: Shared, then CCNA 200-301 guided labs, then 41 - Troubleshooting IPv4 and IPv6 addressing and static routes

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 55 minutes
Nodes need
6 vCPU, 6,144 MB
Smallest plan
Lite

The scenario

Brookvale Surgery runs three sites over static routes, dual stack. A new engineer prepared tomorrow's backup circuit between R1 and R3 and also "cleaned up" some addressing. Now site 1 can't reach site 3, site 2's PC is cut off, and nothing works over IPv6 beyond the first router. There are seven faults. Use ping and traceroute to find where packets stop, then the tables to find why.

Design:

ItemDesign
Site LANsR1 Gi0/1 10.41.1.0/24, R2 Gi0/1 10.41.2.0/24, R3 Gi0/1 10.41.3.0/24; IPv6 2001:db8:41:1::/64, :2::/64, :3::/64; router = .1 / ::1
PCsPC1 10.41.1.10, PC3 10.41.2.10, PC2 10.41.3.10; gateway .1; IPv6 by SLAAC
LinksR1–R2 10.0.12.0/30 and 2001:db8:0:12::/64 (R1 .1/::1, R2 .2/::2); R2–R3 10.0.23.0/30 and 2001:db8:0:23::/64 (R2 .1/::2, R3 .2/::3)
RoutingR1 and R3: IPv4 and IPv6 default routes to R2. R2: routes to sites 1 and 3. R1 also reaches site 3 primarily via R2, with a floating static (AD 200) over the backup link for when it's in service
Backup linkR1 Gi0/2 10.0.13.1/30 – R3 Gi0/2 10.0.13.2/30, not in service yet (R3 Gi0/2 is shut down)

What you’ll practise

  • Troubleshoot IPv4 addressing: masks, gateways and overlapping subnets
  • Troubleshoot IPv6 addressing and prefixes, including SLAAC
  • Troubleshoot static, default and floating static routes in both IP versions
  • Use ping, traceroute and the routing table to locate where packets stop
  • Record each fault with symptom, evidence, cause and fix

The tasks

  1. Map what works
  2. Find the IPv4 faults on the path from site 1 to site 3
  3. Find the site 2 faults
  4. Find the IPv6 faults
  5. Fix all seven faults and prove it

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Troubleshooting IPv4 and IPv6 addressing and static routes6 nodes, 6 links. Every link is listed as text below the diagram.R1R2R3PC1PC3PC2Gi0/1eth0Gi0/1eth0Gi0/1eth0Gi0/0Gi0/0Gi0/2Gi0/0Gi0/2Gi0/2
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 Gi0/0 to R2 Gi0/0
  • R2 Gi0/2 to R3 Gi0/0
  • R1 Gi0/2 to R3 Gi0/2
  • R1 Gi0/1 to PC1 eth0
  • R2 Gi0/1 to PC3 eth0
  • R3 Gi0/1 to PC2 eth0
Nodes in Troubleshooting IPv4 and IPv6 addressing and static routes, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 1,024 MB
R2Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 1,024 MB
R3Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 1,024 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC3VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC2VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder CCNA 200-301 guided labs.

  3. Open 41 - Troubleshooting IPv4 and IPv6 addressing and static routes and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More CCNA labs

All CCNA labs

Related labs in other courses

CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.