A regional bank maintains OMP peering between WAN Edges and two SD-WAN Controllers during a planned controller upgrade, needs forwarding to continue briefly if OMP drops, and wants predictable reconvergence. Which OMP graceful-restart and timer behavior best supports this OMP requirement?
Select an answer to reveal the explanation.
Short Explanation
Graceful restart buys you quiet continuity during that upgrade window. OMP peering is like a brief pause in conversation where neighbors remember your last words. It relies on adjacency timers to detect loss and then refresh state cleanly.
Full Explanation
OMP graceful restart configured on the WAN Edge and supported by the SD-WAN Controller, formerly vSmart, lets a restarting peer signal its neighbors to retain OMP routes in the RIB during a brief restart window while hello, hold, and restart timers govern detection and expiry to avoid churn. The correct behavior enables graceful restart so forwarding uses retained state only for the timer interval, then reconverges normally, which meets continuity plus predictability. Disabling graceful restart with zero timers fails by concept because aggressive expiry improves detection speed but causes immediate route withdrawal and traffic loss. Tuning only BFD fails by concept because BFD measures data-plane path liveness, not OMP control adjacency and RIB retention. Permanent retention fails by concept because graceful restart is time-bound by design, and indefinite staleness risks blackholing after topology changes. Exam caveat: do not confuse OMP timers with BFD or OMP best-path selection. Practical check: confirm graceful-restart support on peers and review OMP peer timers and restart state in SD-WAN Manager.