An enterprise implements Virtual Router Redundancy Protocol (VRRP) across two core switches to provide high availability for client devices on a production VLAN. During a scheduled test, the primary switch is powered down, and network logs confirm that the standby switch successfully transitions to the master role. However, workstations on the VLAN immediately lose external network connectivity and fail to recover. Diagnostics show that VRRP advertisement packets and virtual MAC transitions operated correctly. Which of the following host misconfigurations is the most likely cause of this connectivity failure?
- Workstations were configured with the primary switch's physical interface IP address as their default gateway rather than the virtual IP address shared by the redundancy group.Answer
- BWorkstations were assigned a higher numerical Spanning Tree Protocol priority value than the secondary switch, preventing trunk negotiation.
- CWorkstations were configured with a default gateway residing on a separate subnet that requires an active DHCP relay agent to resolve.
- DWorkstations were isolated into a dedicated broadcast domain that restricts inter-VLAN communication to physical MAC addresses.
Answer
Workstations were configured with the primary switch's physical interface IP address as their default gateway rather than the virtual IP address shared by the redundancy group.
For First Hop Redundancy Protocols (such as VRRP or HSRP) to provide seamless failover, client workstations must use the Virtual IP (VIP) assigned to the router redundancy group as their default gateway. When the active router fails, the standby router takes ownership of the Virtual IP and virtual MAC address. If workstations are statically or dynamically configured with the physical interface IP of the primary router instead of the VIP, their traffic continues targeting the failed physical interface, breaking outbound connectivity despite a successful protocol failover.
Step-by-Step Solution
Key Concept
FHRP Virtual Gateway IP Configuration