A museums and culture department saw CPU spikes when a flapping WAN link churned OSPF. Which tuning goal should they pursue with SPF and LSA throttle timers?
Select an answer to reveal the explanation.
Short Explanation
Think of SPF like a smoke alarm that was going off every time a door slammed. Throttle timers add a short calm-down period so one WAN blip doesn’t keep the CPU rebuilding the whole map. You’re trading a little reconvergence speed for a lot of stability.
Full Explanation
SPF and LSA throttling introduce initial delay, hold, and max-wait intervals that pace Dijkstra runs and LSA flooding during instability. That dampens CPU and control-plane load when a link flaps without abandoning OSPF. Static-only or Hello-everywhere approaches miss the control-plane pacing problem. Totally stubby areas reduce some LSA types but do not replace throttle timers for flap damping.