Goldfish Networks wordmark
IntermediatePublished 2026-06-30

CCNA Static Routing: Redundant Branch Triangle

Bundle lab

Build a 3-router triangle with two branch LANs and real Alpine clients. Deploy primary static routes via the hub and floating backup statics over a direct branch-to-branch link. Verify reachability, path selection, and failover by simulating a hub outage.

Track
Est. time
65 minutes
Difficulty
Intermediate
Topics

Learning objectives

  • Configure bidirectional static routes along a multi-hop primary path
  • Deploy floating static routes with a higher administrative distance for backup
  • Verify RIB/FIB path selection and host-to-host reachability from real endpoints
  • Force a failover and observe floating static installation on both branches
  • Troubleshoot next-hop reachability and static route resolution

Troubleshooting focus

  • ping 10.10.2.10 from CLIENT-A fails: run show ip interface brief on each router. A down hub port stops the primary statics installing; a down direct link stops backup convergence.
  • Traffic is not forwarded though the static is configured: check the next-hop. A static pointing at a local address or the wrong /30 peer will not forward — use the neighbour's IP.
  • ARP or routing behaves erratically: every /30 and /24 must be unique; overlaps cause these anomalies.
  • The direct link carries traffic while the hub is up: the floating AD is too low; it must exceed the primary's AD of 1 — use 5.
  • Only one branch fails over during the outage test: you shut one hub transit. Shut both hub-facing interfaces on RTR-HUB so both branches switch together.

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.

Study this topic

Free guides, a command cheat sheet, and graded practice for this lab's topic.

Learn Static & Default RoutingHow Does Routing Work? The Routing Table Explained

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.