A virtual router is a method to prevent a single point of failure at the default gateway. To implement virtual router redundancy, several physical routers are configured to work jointly as a single logical router to the hosts on the LAN. The routers share an IP address and a MAC address and act as a single virtual router.
The IP address of the virtual router is used as the default gateway for the local network on a particular IP segment. When a host on the local network sends data toward a destination beyond the local subnet using the default gateway, it resolves the MAC address of that gateway via ARP. The ARP reply returns the virtual router’s MAC address, and traffic sent to that MAC address is then physically processed by whichever router is currently the active forwarder within the group.
The redundancy protocol recognises two or more routers as jointly responsible for processing frames sent to the virtual router’s shared IP and MAC address. Host devices send traffic to the virtual router’s address, but which physical router actually processes and forwards that traffic is entirely transparent to the hosts. The redundancy protocol decides which router takes the active role, and when that role must transfer to a standby router. The switch from one forwarding router to another happens without any awareness or reconfiguration on the part of end devices, allowing the network to recover dynamically from a router failure. This overall function is known as First Hop Redundancy.
What Is FHRP?
When the active router fails, a First Hop Redundancy Protocol (FHRP) promotes a standby router to the active role. The standby router detects the failure when it stops receiving Hello messages from the active router within the expected timing window. The standby then assumes both the IP and MAC addresses of the virtual router, and host devices experience no disruption in service, since from their perspective the default gateway’s address never changed.
FHRP is not a single protocol but a category of protocols solving this same problem in different ways. The main FHRPs covered in this guide are HSRP, VRRP, GLBP, and the legacy IRDP.
History and Evolution of FHRPs
First Hop Redundancy Protocols originated in the 1990s to address the limitations of relying on a single static default gateway. Cisco developed HSRP as a proprietary solution providing gateway redundancy without requiring any change to host configuration. The IETF later standardised VRRP (RFC 2338, 1998) as an open alternative supporting multi-vendor environments. GLBP, another Cisco innovation, added active load-balancing across multiple gateways on top of the redundancy that HSRP and VRRP already provided.
VRRPv3 was standardised in RFC 5798 (2010), adding native IPv6 support alongside IPv4. In April 2024, RFC 9568 obsoleted RFC 5798, clarifying the VRRP checksum calculation specification, notably confirming that the IPv4 checksum does not include a pseudo-header, removing ambiguity that existed in the earlier RFC’s wording.
Host Standby Router Protocol (HSRP)
HSRP is a Cisco-proprietary FHRP designed to allow transparent failover of a first-hop IPv4 gateway. It allows configuring two or more routers as a group, with exactly one router active at a time and the rest in standby. This provides first-hop routing redundancy for IPv4 hosts configured with a single default gateway address.
All routers in an HSRP group share a single virtual MAC address and virtual IP address, which together act as the default gateway for the local network. The active router forwards traffic and sends Hello packets to the standby router or routers. If a standby router fails to receive Hello packets for a defined period, it assumes the active role and takes over forwarding.
How HSRP Works in Detail
HSRP uses a priority-based election: the router with the highest priority becomes active. Priorities range from 0 to 255, with a default of 100 (the same style of priority-based election used in OSPF’s Designated Router selection, though the two protocols solve different problems). Preemption, if enabled, allows a higher-priority router that later comes back online to reclaim the active role from a lower-priority router that took over during its absence. Hello messages are sent every 3 seconds by default, with a hold time of 10 seconds; if no Hello arrives within the hold time, failover occurs.
In production deployments, HSRP is frequently combined with interface or object tracking, monitoring an upstream link’s status and automatically adjusting a router’s priority if that link goes down, preventing traffic from being blackholed toward a router that has lost its own upstream connectivity even though its LAN-facing interface is still up.
Example Topology
Consider two physical routers providing gateway redundancy for internet access to a local subnet. The active router has IP address 192.168.10.200, the standby router has 192.168.10.100, and they share a virtual router IP of 192.168.10.1 on the 192.168.10.0/24 subnet. This virtual IP is configured as the default gateway on every host on that subnet.
Traffic from hosts is directed to the virtual IP, currently handled by the active router. If the active router fails, the standby assumes the virtual IP and MAC address, maintaining connectivity with zero host-side reconfiguration. This is a typical, well-suited scenario for small-to-medium enterprise networks requiring resilient internet gateway access.
Advantages and Disadvantages of HSRP
Advantages: seamless failover, straightforward configuration on Cisco equipment, support for multiple HSRP groups to achieve manual load sharing across VLANs.
Disadvantages: Cisco-proprietary, limiting multi-vendor interoperability; no built-in load balancing within a single group (unlike GLBP).
HSRP for IPv6
HSRP for IPv6 is the same underlying Cisco-proprietary protocol, adapted for IPv6 environments. An HSRP IPv6 group uses a virtual MAC address derived from the HSRP group number, paired with a virtual IPv6 link-local address. Periodic Router Advertisement (RA) messages are sent to this virtual link-local address while the group is active; when the group becomes inactive, a final RA is sent before RAs stop entirely.
Virtual Router Redundancy Protocol (VRRP)
VRRP is an open-standard, non-proprietary election protocol providing router redundancy on a LAN. It allows several routers on a shared link to present a single virtual IPv4 (or, in VRRPv3, IPv6) address, removing the single point of failure inherent in a static default-gateway configuration.
In a VRRP configuration, one router is elected the virtual router master, and the remaining routers act as backups, ready to take over if the master fails. A virtual router is a collection of physical routers whose interfaces must belong to the same IP subnet, and each virtual router is assigned a virtual router ID (VRID); the same VRID can be reused with a different address mapping on separate LANs without conflict.
VRRPv2 Operational Details
VRRPv2 uses a master/backup model with priorities from 1 to 255. A router configured with the actual IP address of the virtual router (the “address owner”) automatically receives priority 255. Advertisements are sent every 1 second by default, with a master-down interval calculated as three times the advertisement interval plus a skew time. The virtual MAC address format is 0000.5E00.01{XX}, where XX is the VRID in hexadecimal.
VRRPv3
VRRPv3 extends VRRP to support both IPv4 and IPv6 in a single unified specification, compliant with RFC 5798 (now updated by RFC 9568). It provides faster switchover to a backup router than could be achieved relying on standard IPv6 neighbor discovery mechanisms alone, transitioning to master status in seconds with minimal overhead and no dependency on host-side behavior. VRRPv3 works across multi-vendor environments and scales better than VRRPv2, particularly in IPv6 or dual-stack deployments.
Advantages: open standard, multi-vendor support, sub-second failover achievable with tuned timers.
Disadvantages: no native load balancing across the group; convergence can be slower than HSRP’s defaults without deliberate timer tuning.
Gateway Load Balancing Protocol (GLBP)
GLBP is a Cisco-proprietary FHRP that protects data traffic from a failed router or circuit, like HSRP and VRRP, but adds genuine load sharing across the redundant router group rather than leaving standby routers entirely idle until a failure occurs.
GLBP Load Balancing Mechanisms
GLBP elects an Active Virtual Gateway (AVG), which assigns distinct virtual MAC addresses to up to four Active Virtual Forwarders (AVFs) within the group. Available load balancing methods include round-robin, host-dependent, and weighted distribution. This allows multiple routers in the group to simultaneously forward traffic rather than sitting idle in standby, improving overall bandwidth utilisation across the redundant links compared to HSRP or VRRP’s strictly active/standby model. GLBP can also be paired with BFD (Bidirectional Forwarding Detection) for accelerated failure detection, a general BFD capability applicable across multiple Cisco protocols, not unique to GLBP.
GLBP for IPv6
GLBP for IPv6 provides the same load-balancing redundancy function as GLBP for IPv4 hosts, but in IPv6 environments. Multiple first-hop routers on a local area network join to offer a single virtual first-hop IPv6 router while sharing the packet forwarding load across the group.
ICMP Router Discovery Protocol (IRDP)
Defined in RFC 1256, IRDP is a legacy FHRP allowing IPv4 hosts to locate routers providing connectivity to non-local IP networks. It uses ICMP router advertisement and router solicitation messages, allowing a host to discover operational routers on its local subnet. IRDP is largely deprecated in favour of HSRP, VRRP, and GLBP in modern networks, though it may still appear in some legacy systems, valued historically for its simplicity in small networks.
Comparison of FHRPs
| Protocol | Proprietary | Load Balancing | IPv6 Support | Typical Convergence | Best Use Case |
|---|---|---|---|---|---|
| HSRP | Cisco | No | Yes | Sub-second with tuning | Cisco-only enterprise networks |
| VRRP | Open standard | No | Yes (v3) | Sub-second | Multi-vendor environments |
| GLBP | Cisco | Yes | Yes | Sub-second | Active load-shared redundancy |
| IRDP | Open (legacy) | No | No | Variable | Legacy small networks |
GLBP stands out specifically for active bandwidth utilisation across the whole group, since HSRP and VRRP leave standby routers idle until a failure occurs.
Configuration Example
The following matches the example topology described above: an HSRP group on GigabitEthernet0/0, connecting both routers to the 192.168.10.0/24 subnet, with the active router given a higher priority and preemption enabled so it reliably reclaims the active role after recovering from any outage.
Active Router (192.168.10.200):
interface GigabitEthernet0/0
ip address 192.168.10.200 255.255.255.0
standby 1 ip 192.168.10.1
standby 1 priority 110
standby 1 preemptStandby Router (192.168.10.100):
interface GigabitEthernet0/0
ip address 192.168.10.100 255.255.255.0
standby 1 ip 192.168.10.1
standby 1 priority 100Verify the configuration on both routers:
Router# show standby
Router# show standby briefHosts on the subnet point to 192.168.10.1 as their default gateway, with failover to the standby router occurring transparently if the active router fails. Once a router is confirmed as the HSRP active forwarder, it uses its own normal forwarding path, typically CEF, to actually process and forward the traffic; see our guide to Cisco router forwarding mechanisms for how that forwarding decision itself works once HSRP has determined which router is responsible.
Real-World Use Cases
FHRPs are foundational in data centres, campus networks, and branch offices wherever a single default gateway would otherwise represent an unacceptable single point of failure. A common example is a branch office or campus distribution layer where two routers or Layer 3 switches provide redundant gateway service for a subnet of end-user devices, with HSRP or VRRP ensuring that a single router or switch failure does not disconnect the entire subnet from the rest of the network.
CCNA Exam Pointers
- FHRP = First Hop Redundancy Protocol, a category including HSRP, VRRP, GLBP, and legacy IRDP
- HSRP: Cisco-proprietary, priority 0–255 (default 100), Hello 3s/Hold 10s, virtual MAC
0000.0C07.ACxx - VRRP: open standard, priority 1–255 (255 = address owner), advertisement 1s, virtual MAC
0000.5E00.01{XX} - GLBP: Cisco-proprietary, the only one of the three with active load balancing (up to 4 AVFs per AVG)
- Preemption allows a recovered higher-priority router to reclaim the active role
standby [group] ip [address],standby [group] priority [value],standby [group] preempt— core HSRP configuration commandsshow standby/show standby brief— HSRP verification commands- RFC history: VRRPv2 = RFC 3768; VRRPv3 = RFC 5798 (2010), now obsoleted by RFC 9568 (April 2024)
Conclusion
First Hop Redundancy Protocols solve a fundamental single-point-of-failure problem: a default gateway is only useful if it’s actually reachable, and a single physical router is a fragile foundation for that role in any network where uptime matters. HSRP, VRRP, and GLBP each solve this with the same core mechanism, a shared virtual IP and MAC address, election of an active forwarder, and Hello-based failure detection, while differing in vendor openness and, in GLBP’s case, adding genuine load-sharing across the redundant group rather than leaving standby capacity idle. Understanding each protocol’s specific defaults, priority ranges, and configuration syntax is directly testable CCNA knowledge and a foundational real-world skill for designing resilient network edges.
Frequently Asked Questions
What is FHRP and why is router redundancy important?
FHRP (First Hop Redundancy Protocol) is a category of protocols, including HSRP, VRRP, and GLBP, that prevent a single router failure from isolating an entire subnet of hosts from the rest of the network. Multiple physical routers share a virtual IP and MAC address configured as the subnet’s default gateway; hosts are never aware of which physical router is currently forwarding their traffic, so a router failure triggers an automatic, typically sub-second failover to a standby router with zero host-side reconfiguration required. This makes FHRP foundational to any network design where default gateway availability genuinely matters.
What challenges arise when implementing router redundancy?
The most common implementation challenges are misconfigured or inconsistent priorities across the group, which can cause an unintended router to become active, and security exposure from unauthenticated Hello/advertisement messages, which can be spoofed by an attacker to disrupt the election process. Both HSRP and VRRP support authentication (plain text or MD5, depending on version and platform) specifically to mitigate this second risk, and it should be configured in any production deployment rather than left at its insecure default.
What is the difference between HSRP and VRRP?
HSRP is Cisco-proprietary and works only between Cisco devices, using priority values from 0–255 with a default of 100, Hello messages every 3 seconds, and a virtual MAC address in the 0000.0C07.ACxx range. VRRP is an open IETF standard supporting multi-vendor environments, using priority values from 1–255, advertisements every 1 second by default, and a virtual MAC in the 0000.5E00.01{XX} range. Functionally the two protocols solve the same problem in a very similar way; the choice between them typically comes down to whether the environment is Cisco-exclusive (favoring HSRP’s tighter Cisco ecosystem integration) or multi-vendor (requiring VRRP’s open standard).
How does GLBP improve on HSRP and VRRP?
GLBP adds active load balancing on top of the same basic redundancy HSRP and VRRP provide. Rather than leaving all but one router idle in standby, GLBP’s Active Virtual Gateway assigns distinct virtual MAC addresses to up to four Active Virtual Forwarders within the group, allowing multiple routers to simultaneously forward live traffic using round-robin, host-dependent, or weighted distribution methods. This means the redundant capacity that HSRP or VRRP would leave completely unused until a failure occurs is actively contributing to normal traffic handling under GLBP.
What changed with RFC 9568 for VRRP?
RFC 9568, published in April 2024, obsoletes RFC 5798 (which had defined VRRPv3 since 2010). The most notable technical change is a clarification of the VRRP checksum calculation: the updated specification confirms explicitly that the IPv4 checksum calculation does not include a pseudo-header, resolving ambiguous wording in the earlier RFC that had led to some inconsistent implementations. This is a specification clarification rather than a functional redesign of VRRP’s core election and failover behaviour.
