IntermediatePublished 2026-07-02
HSRP Interface Tracking for Uplink Failover
Bundle lab
Lab 4 of 13 in First-Hop Redundancy (HSRP & VRRP) · ← Previous · Next →
CCNA exam domain: IP Connectivity
Implement HSRP with interface tracking so the virtual gateway fails over when the active router loses its upstream link. Two routers (R1, R2) share a user LAN via SW with a single virtual default gateway for the PC, and both uplink to a separate CORE switch. The learner adds HSRP group 1 with a virtual IP, priority/preempt on R1, and tracks R1's uplink to drive deterministic failover.
Learning objectives
- Configure HSRP group 1 with a shared virtual IP on two routers for a single LAN
- Make R1 the intended active via HSRP priority and preempt
- Track the upstream interface on R1 so an uplink failure reduces its HSRP priority and triggers failover
- Verify HSRP active/standby state and tracked decrement using show commands
- Validate endpoint default-gateway behavior using the virtual IP
Troubleshooting focus
- HSRP group or virtual IP mismatch preventing peering
- Virtual IP equals a real interface IP (invalid)
- Preempt missing on the intended primary prevents role reclamation
- Tracked interface reference wrong or down/up state misunderstood
- PC default gateway not set to the VIP, causing loss of external reachability
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.