IntermediatePublished 2026-06-25
CCNA Static Routing: Host vs Subnet (/32 vs /24)
Bundle lab
Deploy a compact two-site topology with a WAN core and two end hosts to practice IPv4 static host routes (/32) versus subnet routes (/24). You will configure a specific /32 host route to steer one destination host over the direct R1–R3 path while a broader /24 for the same remote LAN is sent via the R1–R2–R3 core. Validate with show commands and traceroute, then troubleshoot longest-prefix match and return-path issues.
Learning objectives
- Configure IPv4 static host routes (/32) and subnet routes (/24) on IOS (iol-xe).
- Demonstrate longest-prefix match where the /32 host route overrides the /24 for the same network.
- Verify forwarding decisions with show ip route and end-to-end traceroute from hosts.
- Troubleshoot overlapping static routes and return-path issues.
Troubleshooting focus
- A host cannot ping its local gateway: check the host IP, mask and default gateway, then
show ip interface briefon its edge router — the LAN interface must match the plan and read up/up. traceroute -nstalls at the first hop: a static route points at the wrong next-hop, or at the router itself. It must name the neighbor on the connected link, and that address must be reachable out that interface.- Ping fails even though the forward path looks right: the replies have no way back. Both edges and the core must hold a route to the source subnet or host.
traceroute -n 10.30.30.10from CLIENT-A01 leaves via 10.12.12.2 instead of 10.13.13.2: the /32 is on the wrong router or points to the wrong next-hop. It must resolve over the direct intersite link.- The /32 is in
show ip routebut test traffic ignores it: check the host address for a typo. It must be exactly 10.30.30.10 on RTR-A-EDGE1 and 10.10.10.10 on RTR-B-EDGE1.
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.