Question 590
At fictional Beacon Healthcare, a network engineer supporting hospital network services is reviewing VRRP, BFD and redundancy design during a new network integration (HCIP-H12-821-RELIABILITY-148). The observed network issue is: BFD keeps an OSPF neighbor Down even after link restoration because the negotiated intervals or detection multiplier are incompatible. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Review BFD session negotiation parameters and protocol association at both ends. The specific reported fault is: BFD keeps an OSPF neighbor Down even after link restoration because the negotiated intervals or detection multiplier are incompatible. Confirmation should show: The BFD session reaches Up and OSPF resumes the intended stable adjacency. The supporting technical principle is: BFD detection speed depends on compatible transmit and receive timers and multiplier behavior.
Incorrect Answers
“Configure supported VRRP uplink tracking and suitable priority decrement” 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: BFD keeps an OSPF neighbor Down even after link restoration because the negotiated intervals or detection multiplier are incompatible. The more direct action is “Review BFD session negotiation parameters and protocol association at both ends” because BFD detection speed depends on compatible transmit and receive timers and multiplier behavior.
“Adjust appropriate tracking conditions, hysteresis or delay settings and repair unstable uplink state” responds to another technical or business failure: A VRRP group flaps repeatedly because upstream connectivity causes tracked priority to alternate around the peer threshold. That source case depends on: Unstable track state can cause repeated virtual-gateway ownership changes. The present issue is: BFD keeps an OSPF neighbor Down even after link restoration because the negotiated intervals or detection multiplier are incompatible. The more direct action is “Review BFD session negotiation parameters and protocol association at both ends” because BFD detection speed depends on compatible transmit and receive timers and multiplier behavior.
“Repair the underlying link and choose supported detection timers or BFD that match availability requirements” responds to another technical or business failure: An operator increases routing protocol Dead timers to stabilize a flaky link but overlooks the resulting slow failover. That source case depends on: Reliability design balances false failures against convergence latency. The present issue is: BFD keeps an OSPF neighbor Down even after link restoration because the negotiated intervals or detection multiplier are incompatible. The more direct action is “Review BFD session negotiation parameters and protocol association at both ends” because BFD detection speed depends on compatible transmit and receive timers and multiplier behavior.