Question 240
At fictional Juniper Publishing, a network engineer supporting hybrid offices is reviewing VRRP, BFD and redundancy design during a post-maintenance incident review (HCIP-H12-821-RELIABILITY-060). The observed network issue is: A VRRP group flaps repeatedly because upstream connectivity causes tracked priority to alternate around the peer threshold. Which routing, switching, or network principle best explains the appropriate solution?
Explanation
Correct Answer
The governing principle is: Unstable track state can cause repeated virtual-gateway ownership changes. In this scenario, the appropriate action is: Adjust appropriate tracking conditions, hysteresis or delay settings and repair unstable uplink state. Valid evidence would show: Gateway mastership remains stable through normal transients and changes on genuine failure.
Incorrect Answers
“BFD detection speed depends on compatible transmit and receive timers and multiplier behavior” responds to another technical or business failure: BFD keeps an OSPF neighbor Down even after link restoration because the negotiated intervals or detection multiplier are incompatible. That source case depends on: BFD detection speed depends on compatible transmit and receive timers and multiplier behavior. The present issue is: A VRRP group flaps repeatedly because upstream connectivity causes tracked priority to alternate around the peer threshold. The more direct action is “Unstable track state can cause repeated virtual-gateway ownership changes” because Unstable track state can cause repeated virtual-gateway ownership changes.
“Bidirectional Forwarding Detection provides fast failure detection independent of routing protocol timers” responds to another technical or business failure: A router forwards to a remote next hop even after its BGP peer's far-end forwarding path is lost, causing slow detection. That source case depends on: Bidirectional Forwarding Detection provides fast failure detection independent of routing protocol timers. The present issue is: A VRRP group flaps repeatedly because upstream connectivity causes tracked priority to alternate around the peer threshold. The more direct action is “Unstable track state can cause repeated virtual-gateway ownership changes” because Unstable track state can cause repeated virtual-gateway ownership changes.
“VRRP interface or route tracking can couple gateway priority to actual upstream health” responds to another technical or business failure: A VRRP standby router never becomes master after the preferred uplink fails because only the physical LAN interface remains Up. That source case depends on: VRRP interface or route tracking can couple gateway priority to actual upstream health. The present issue is: A VRRP group flaps repeatedly because upstream connectivity causes tracked priority to alternate around the peer threshold. The more direct action is “Unstable track state can cause repeated virtual-gateway ownership changes” because Unstable track state can cause repeated virtual-gateway ownership changes.