During a high-availability failover test on an enterprise subnet, client workstations lose all outbound network connectivity whenever the primary active router is powered off. Network logs confirm that the secondary router successfully assumes the active role within the First Hop Redundancy Protocol (FHRP) group and advertises the virtual MAC address. However, workstations fail to route traffic to external networks until the primary router is brought back online. Which of the following is the primary cause of this connectivity loss?
- Workstations were configured with the physical interface IP address of the primary router as their default gateway instead of the FHRP Virtual IP (VIP).Answer
- BThe secondary switch was configured with the highest numerical priority value for the Spanning Tree Protocol (STP) root bridge, placing all uplink ports into a blocking state.
- CThe workstation IP addresses and the default gateway interface were assigned IP addresses on completely different IP subnets.
- DA native VLAN mismatch across the trunk link between the switches caused all untagged FHRP heartbeat packets to be dropped.
Answer
Workstations were configured with the physical interface IP address of the primary router as their default gateway instead of the FHRP Virtual IP (VIP).
For First Hop Redundancy Protocols (FHRP) like HSRP or VRRP to provide seamless gateway failover, all network endpoints must use the Virtual IP (VIP) as their configured default gateway. If clients are statically or dynamically assigned the physical interface IP of the active router, traffic will continue flowing exclusively to that physical device. When that hardware fails, client traffic drops despite the standby router taking over the FHRP group and virtual MAC address.
Step-by-Step Solution
Key Concept
First Hop Redundancy Protocol Virtual IP Configuration
Estimated Time:1m 30s