A network administrator configures a redundant gateway topology using a First Hop Redundancy Protocol (FHRP) to provide high availability for a corporate subnet. During a scheduled failover test, the primary router is powered off. Although logs confirm that the standby router successfully transitioned to the active role, all client workstations immediately lose outbound internet connectivity. Troubleshooting reveals that workstation traffic continues to be routed toward the MAC and IP addresses of the powered-off primary router interface. Which of the following configuration errors is the most likely cause of this issue?
- The DHCP scope is distributing the physical interface IP address of the primary router as the default gateway rather than the virtual IP address of the FHRP group.Answer
- BThe standby router interface was assigned a higher numerical Spanning Tree Protocol bridge priority value, causing the switch port to remain in a blocking state.
- CThe client workstations and the virtual default gateway address were assigned to different IP subnets during the DHCP lease initialization.
- DA native VLAN mismatch on the switch trunk port prevented Virtual Router Redundancy Protocol hello packets from reaching the standby router.
Answer
The DHCP scope is distributing the physical interface IP address of the primary router as the default gateway rather than the virtual IP address of the FHRP group.
The correct answer identifies that First Hop Redundancy Protocols (such as HSRP, VRRP, or CARP) rely on end hosts pointing to a shared Virtual IP (VIP) as their default gateway. If the DHCP scope is mistakenly configured to distribute the physical interface IP of the primary router, workstations will bypass the virtual gateway abstraction. Consequently, when the primary router shuts down, client traffic continues targeting the physical IP of the offline router, resulting in total loss of external connectivity despite the standby router successfully assuming the active state.
Step-by-Step Solution
Key Concept
FHRP Virtual Gateway IP Configuration
Estimated Time:1m 30s