zNetLaB › Guided labs › Enterprise
HSRP 33 — group 33, priority 137
Enterprise Advanced 4 devices 5 checked tasks 100 points Plan lab
Jodhpur's users use one gateway, 10.52.0.254, shared by two routers. Make R1 active (priority 137) with preempt, R2 standby, authenticate group 33 with an MD5 key, and check the PC still reaches the virtual address. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
Jodhpur's users use one gateway, 10.52.0.254, shared by two routers. Make R1 active (priority 137) with preempt, R2 standby, authenticate group 33 with an MD5 key, and check the PC still reaches the virtual address.
Your role: a network engineer on the enterprise team. Level: Advanced Done when: all 5 goals show as passed (100 points).
Network status
Devices: 2 routers, 1 switch, 1 PC, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R1 starts with addresses (G0/0 10.52.0.1/24). R2 starts with addresses (G0/0 10.52.0.2/24). PC is a host with 10.52.0.50/24, gateway 10.52.0.254. SW starts with an empty configuration. Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure. Goals
R1 is the active router (30 pts) R2 is standing by (20 pts) R1 preempts (15 pts) Group 33 is authenticated on both routers (20 pts) The PC reaches the virtual gateway (15 pts) The activity, in order
R1 is the active router Why: Hosts point at the virtual IP, so when the active router dies the standby answers and nobody reconfigures anything. Verify with: show standby brief R2 is standing by Why: The standby is the one that takes over; it must be configured identically except for priority. Verify with: show standby brief R1 preempts Why: This is the task that checks your configuration directly: the line must really be there, not just look right. Verify with: show running-config Group 33 is authenticated on both routers Why: This is the task that checks your configuration directly: the line must really be there, not just look right. Verify with: show running-config The PC reaches the virtual gateway Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 10.52.0.254 Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Common mistake: Different group numbers on the two routers Common mistake: Forgetting preempt — the recovered router does not take the role back Common mistake: Pointing hosts at a real router address instead of the virtual one Why this matters
If a single gateway router fails, every host on the LAN loses the internet. HSRP gives two routers one virtual IP; the one with the higher priority answers, and the other takes over silently if it disappears.
What you will be able to do
Configure HSRP with a virtual IP, priority and preempt
Authenticate the group
Read show standby
The network
ISR 2911, Catalyst 2960-24TT, PC — 4 devices in all, already cabled.
Fa0/1 Fa0 Fa0/2 Gi0/0 10.52.0.1/24 Fa0/3 Gi0/0 10.52.0.2/24 R1 R2 SW PC 10.52.0.50/24 · gw 10.52.0.254 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R1 ISR 2911 configure it R2 ISR 2911 configure it SW Catalyst 2960-24TT configure it PC PC 10.52.0.50 / 255.255.255.0 gw 10.52.0.254
Cabling
SW Fa0/1 ↔ PC Fa0 SW Fa0/2 ↔ R1 Gi0/0 SW Fa0/3 ↔ R2 Gi0/0
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
R1 interface g0/0
ip address 10.52.0.1 255.255.255.0
no shutdown
exit R2 interface g0/0
ip address 10.52.0.2 255.255.255.0
no shutdown
exit Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 R1 is the active router 30 On R1: show standby brief — the router is Active. 2 R2 is standing by 20 On R2: show standby brief — the router is Standby. 3 R1 preempts 15 On R1: show running-config contains the line(s) matching standby 33 preempt. 4 Group 33 is authenticated on both routers 20 On R1: show running-config contains the line(s) matching standby 33 authentication. and On R2: show running-config contains the line(s) matching standby 33 authentication. 5 The PC reaches the virtual gateway 15 On PC: ping 10.52.0.254 must succeed.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Common mistakes
Different group numbers on the two routers
Forgetting preempt — the recovered router does not take the role back
Pointing hosts at a real router address instead of the virtual one
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
R1 interface g0/0
standby 33 ip 10.52.0.254
standby 33 priority 137
standby 33 preempt
standby 33 authentication md5 key-string Hs32K3y
exit R2 interface g0/0
standby 33 ip 10.52.0.254
standby 33 priority 100
standby 33 authentication md5 key-string Hs32K3y
exit Where this is examined
CCNA 3.0 FHRP concepts; CCNP ENCOR HSRP/VRRP.
This lab practises these topics in the zNetLaB certification courses:
Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.