Before you configure any redundancy protocol, let's take a moment to feel the problem it solves.
For this lesson, forget the administrator role: you are a regular user, sitting at PC1 in a small office network.Check Your Gateway
Here is the network you work in every day.
Your LAN has a single exit toward the outside world, and that exit is R1.
Figure 1 – One router serves as your default gateway
Let's start by checking which gateway your PC actually uses.
Run the following command:PC1> ipconfig Ethernet adapter Ethernet: IPv4 Address. . . . . . . . . . . : 192.168.10.101 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.10.1As you can see, your default gateway is 192.168.10.1, which is the physical address of R1.
Every single packet you send outside your subnet 192.168.10.0/24 travels through that one address.Answer the question below
What is the IP address of PC1?
Test the Connectivity
Now let's confirm that this gateway does its job.
Send a ping to 8.8.8.8, a public address on the Internet:PC1> ping 8.8.8.8 Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time<1ms TTL=254 Reply from 8.8.8.8: bytes=32 time<1ms TTL=254 Reply from 8.8.8.8: bytes=32 time<1ms TTL=254 Reply from 8.8.8.8: bytes=32 time<1ms TTL=254 Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),You received four replies, which means your packets crossed R1, reached the Internet, and came back without any problem.

Figure 2 – Your traffic reaches the Internet through R1
Everything works as expected.
You browse, you stream, and you never have to think about R1: it quietly does its job in the background.Answer the question below
Which address is PC1's default gateway?
Now, imagine that one morning, R1 suddenly loses power.
Nobody warned you, and nothing changed on your PC.Let's see what your morning looks like from your seat.
The Ping Fails
You sit down at your desk, open your usual applications, and nothing loads anymore.

Figure 3 – The default gateway fails
To understand what is happening, run the exact same ping as yesterday:
PC1> ping 8.8.8.8 Pinging 8.8.8.8 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),Take a moment to realize what this output means.
Your IP address is still valid, your cable is fine, the switch is fine, and 8.8.8.8 is perfectly alive.
And yet, your PC keeps sending frames to a router that has vanished from the network.Answer the question below
What percentage of packets did you lose?
The Single Point of Failure
The explanation is simple.
Your PC can only hold one default gateway address, and right now that address points to a dead router.
It has no mechanism to discover a backup router on its own, even if one is sitting right next to R1.
Figure 4 – Single Point of Failure
This is why we say the default gateway is a single point of failure.
You could reconfigure your PC manually to use another router, but imagine doing that on hundreds of devices every time a gateway fails. This is clearly not a solution.Answer the question below
Which device was your single point of failure?
This is exactly the problem First Hop Redundancy Protocols (FHRP) were designed to solve.
You already studied them in depth during your CCNA journey, so let's simply refresh the essentials together.One Virtual Gateway
Here is the design that would have saved your morning.
Take a look at the topology below:
Figure 5 – Two routers, one virtual gateway
With an FHRP, R1 and R2 work together and present one virtual gateway to your whole LAN.
Your PC points at a virtual IP address that belongs to no physical machine.One router is active and forwards the traffic. The other one waits as a backup.
The two routers monitor each other with periodic Hello messages, so if the active one fails, the backup takes over automatically.
The best part: you change nothing on your PC.
Everything happens between the routers.Answer the question below
Do you need to change anything on your PC when the active router fails?
HSRP, VRRP, and GLBP
The family has three members, and you must be able to recognize each of them:
Protocol
Origin
Key Trait
HSRP
Cisco
One Active, one Standby. The most deployed FHRP.
VRRP
One Master, one or more Backups. Multi-vendor.
GLBP
Cisco
Several routers forward at once: load balancing per host.
Table 1 – The three FHRP protocols
In the next lessons, you will configure HSRP and VRRP yourself.
For GLBP, the exam only expects you to understand the concept: know what it does and what makes it different from the other two.Answer the question below
Which FHRP is an open standard?
After that bad morning, your network team deployed HSRP on R1 and R2.
A few weeks later, R1 loses power again.
But this time, thanks to HSRP, the backup router understands that R1 is dead:
Figure 6 – The backup router takes over the virtual gateway
R2 noticed that the Hellos from R1 stopped, waited a short moment, and claimed the role of active router.
All of this happened automatically, in a few seconds, without any human intervention.A New Gateway Address
Run the same ipconfig and compare the result:
PC1> ipconfig Ethernet adapter Ethernet: IPv4 Address. . . . . . . . . . . : 192.168.10.101 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.10.3Your gateway is no longer 192.168.10.1: during the deployment, the team also updated the DHCP scope.
The new address, 192.168.10.3, belongs to no physical router: it is the virtual IP of the HSRP group.
Answer the question below
Which address is your default gateway now?
Try to Reach the Internet
The failover happened just seconds ago.
Run your ping right away:PC1> ping 8.8.8.8 Pinging 8.8.8.8 with 32 bytes of data: Request timed out. Request timed out. Reply from 8.8.8.8: bytes=32 time=1ms TTL=254 Reply from 8.8.8.8: bytes=32 time<1ms TTL=254 Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),You lost two packets: that is the short time R2 needed to detect the silence of R1 and claim the virtual gateway.

Figure 7 – R2 carries your traffic, same virtual gateway
Then your traffic simply came back, and you touched nothing on your PC.
Answer the question below
How many packets did you lose during the failover?
Verify the Failover
Let's check which router is currently forwarding your packets.
We can trace the path to find out:PC1> tracert 8.8.8.8 Tracing route to 8.8.8.8 over a maximum of 30 hops: 1 0 ms 0 ms 0 ms 192.168.10.2 2 0 ms 0 ms 0 ms 8.8.8.8 Trace complete.The first hop is now 192.168.10.2, the physical IP address of R2.
From your point of view, the gateway address never changed.
Only the physical router behind it did.Answer the question below
Which physical router forwards your traffic after the failover?
You just lived through the same failure twice: once without any protection, and once with HSRP running in the background.
In the next lesson, you become the network administrator, and you configure HSRP yourself, step by step.