Learn how HSRP keeps a default gateway available by coordinating active and standby devices, detecting failures, transferring shared addresses, controlling preemption, and distributing forwarding work across groups.
What you will be able to do
- Describe how HSRP assigns active and standby roles within a router group.
- Explain how hello messages and priority support failure detection and takeover.
- Distinguish shared group addresses from a device’s real IP address during failover.
- Describe how preemption, BFD, and multiple HSRP groups affect failover behavior.
01
Why first-hop redundancy matters
A first-hop redundancy design keeps a router group ready to carry traffic when one device stops functioning. HSRP does this by presenting a shared group identity while preparing more than one device to provide packet-transfer functions.
The main value is continuity at the first routing step. One device forwards traffic for the group, while another remains prepared to take over if the forwarding device fails.
02
The active and standby roles
HSRP organizes participating devices into a router group with two central roles: active and standby. The active device performs the group’s forwarding work, and the standby device waits in a prepared state.
These roles are not permanent labels for the hardware. They describe each device’s current responsibility inside a particular HSRP group.
03
How hello messages coordinate devices
HSRP devices exchange multicast UDP hello messages. These messages let members monitor one another and support the selection of active and standby roles.
The standby device can learn the active device’s real IP address from those hello messages. This separates the active device’s own address from the addresses used by the HSRP group.
04
What happens during a failure
If the active device stops sending hellos for a configured period, HSRP treats the missing messages as evidence of failure. The standby devices then compare their priorities to determine which one should take responsibility.
The standby with the highest priority becomes active. During takeover, the replacement assumes the group’s MAC and IP addresses, allowing the group identity to move with the forwarding role.
05
Priority and preemption are different controls
Priority helps HSRP choose among standby devices when the active device fails. It identifies which standby should take over, rather than relying on a standby’s real IP address.
Preemption lets a higher-priority device become active after another device currently holds that role. With equal priority, a standby having a higher IP address does not preempt the active device.
A preempting device can also wait for a configured duration before changing to active. This delay controls when the role transition occurs.
06
One interface can participate in several groups
A physical interface needs only one HSRP group to elect its active and standby devices. The election is therefore associated with a group on the interface, not with a separate election for every possible role.
A device forwarding traffic for one group may be standby or listening for another group. This allows the same pair of devices to divide responsibilities instead of assigning all forwarding work to one device.
07
A simple role-sharing example
Imagine two devices and two HSRP groups. Device A can be active for group 1 and standby for group 2, while Device B is active for group 2 and standby for group 1.
This arrangement distributes the active roles across the devices. Each device still has a prepared partner role, so either group can have a standby ready to assume forwarding if its active device fails.
08
BFD can accelerate notification
Hello messages provide HSRP with a way to detect that the active and standby devices are no longer communicating. BFD can provide a faster notification path for that connectivity failure.
When BFD informs HSRP immediately, HSRP can prompt the standby to take over. BFD changes the speed of notification; the resulting takeover still uses the HSRP group’s failover behavior.
10
Recap for Practice and Prove
HSRP assigns active and standby roles inside a router group. The active device forwards traffic, while the standby remains prepared to take over.
A first-hop redundancy design keeps a router group ready to carry traffic when one device stops functioning. HSRP does this by presenting a shared group identity while preparing more than one device to provide packet-transfer functions.
HSRP devices exchange multicast UDP hello messages. These messages let members monitor one another and support the selection of active and standby roles.
If the active device stops sending hellos for a configured period, HSRP treats the missing messages as evidence of failure. The standby devices then compare their priorities to determine which one should take responsibility.