BFD Optimization: Why Minimum Interval Settings Are False
Short answer
A Setting BFD send intervals to the minimum value indiscriminately causes excessive CPU load and session flapping, making it a false optimization strategy.
Question
Key Takeaways
The main trap is confusing 'faster detection' with 'optimal configuration'; minimizing intervals ignores hardware limits and stability requirements.
Identify the false statement about BFD optimization. Setting BFD intervals to the minimum is incorrect due to CPU overload and flapping risks, while QoS prioritization, WTR timers, and delay configs are valid optimizations.
Common mistake: Candidates often select A as true because 'faster is better' seems intuitive, failing to recognize that extreme values cause instability (flapping) and resource exhaustion.
Expert Analysis
The question asks to identify the false statement regarding BFD (Bidirectional Forwarding Detection) optimization. The correct answer is A, as setting BFD packet intervals to the absolute minimum is not a recommended general practice.
Option A claims that one should set the send interval to the minimum value to quickly learn about network status. This is false because excessively short intervals generate high CPU overhead and can lead to session flapping, especially under load or on unstable links. BFD parameters must be balanced against device capabilities and link stability; blindly minimizing them degrades performance rather than optimizing it.
Option B is true: configuring a high priority (via DSCP/CoS) for BFD packets ensures they are preferentially forwarded by QoS mechanisms, which is critical for timely detection during congestion.
Option C is true: if a BFD session flaps due to minor issues, it triggers frequent master/backup switchovers in redundant systems. Configuring a Wait-to-Restore (WTR) timer prevents this by adding a delay before reverting traffic back to the primary path after recovery.
Option D is true: BFD sessions often come up faster than routing protocols (like OSPF/BGP). If traffic switches immediately upon BFD Up, but routes are not yet installed, blackholing occurs. A delay timer compensates for this race condition, ensuring routes are ready before traffic resumes.
Exam Strategy
When evaluating BFD tuning questions, always check for trade-offs between detection speed and system stability. Avoid options that suggest extreme values (minimum/maximum) without considering CPU load or link conditions. Look for keywords like 'preferential forwarding', 'WTR', and 'delay' as indicators of correct, nuanced configurations.
Frequently Asked Questions
Why is setting BFD intervals to the minimum value bad?
What is the purpose of the WTR timer in BFD?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
HCIP Resolutor 👍 1 Answered AConfigurar los intervalos de BFD al valor mínimo no es una buena práctica indiscriminada. En redes reales, si la CPU del dispositivo o la capacidad del enlace están bajo alta carga, reducir excesivamente los intervalos causa falsos aleteos de sesión (session flapping). Debe equilibrarse la velocidad de detección con la capacidad del procesador. Explicación de la Opción B (VERDADERA): Por defecto, en los sistemas Huawei VRP, a los paquetes BFD se les asigna una alta prioridad DSCP/CoS (como CS6 o EF) para garantizar que los conmutadores/routers los reenvíen con preferencia frente al tráfico de datos ordinario. Por lo tanto, la opción A es la afirmación FALSA que responde a la pregunta
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All H12-821 Questions
Access 168 questions with complete answers and detailed explanations.
View Full H12-821 Practice Test →