Goldfish Networks wordmark
IntermediatePublished 2026-07-02

Static Route Next-Hop Types: Recursive, Direct & Fully-Specified

Archive lab

Hands-on static routing lab in a small branch–WAN–branch triangle. You will configure recursive, directly-attached, and fully-specified static routes to enable end-to-end reachability between two hosts across three routers. You will learn how next-hop resolution works, how it appears in show ip route, and how to troubleshoot when static routes don’t resolve or forward as expected.

Track
Est. time
60 minutes
Difficulty
Intermediate
Topics

Learning objectives

  • Configure recursive, directly-attached, and fully-specified static routes on Cisco routers.
  • Explain and verify recursive next-hop resolution using show ip route and route details.
  • Troubleshoot static route failures due to unreachable or misconfigured next-hop targets.
  • Validate bidirectional host-to-host connectivity across a multi-router path.

Troubleshooting focus

  • Identify route resolution failures in the routing table and CEF.
  • Use ARP and interface status to diagnose directly-attached static routes on Ethernet links.
  • Confirm return-path static routes exist to support bidirectional pings.

Topology

Subscribe to preview this lab's topology.

See plans

Related labs

More hands-on Cisco Modeling Labs practice on the same track and topics.

Grade 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 account
Found a problem with this lab?

Please sign in to report a problem — tying it to your attempts lets us reproduce and fix it faster.