Holddown

Revision as of 13:11, 31 January 2025 by imported>Hiearucix (Changed "they" to "it" to match the singular "router." Replaced "in fact reachable" with "actually reachable" for a slightly smoother phrasing. Changed "solve the case where" to "resolve situations where" for clearer expression. Reworded "can do nothing" to "are ineffective" for a more formal tone. Replaced "usually" with "typically" for a slightly more formal tone. Changed "until the network is stable" to "until the network stabilizes" for a smoother phrasing.)
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

Template:About

Holddown works by having each router start a timer when it first receive information about a network that is unreachable. Until the timer expires, the router will discard any subsequent route messages that indicate the route is actually reachable. It can resolve situations where multiple routers are connected indirectly. There are realistic scenarios where split horizon and split horizon with poisoned reverse are ineffective.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>

In other words, a holddown prevents a router from receiving route updates until the network appears to be stable—until either an interface stops changing state (flapping) or a better route is learned.

Holddowns are typically implemented with timers. If the router detects that a network is unreachable, the timer is started. The router will then wait a preset number of seconds until the network stabilizes. When the timer expires, the router will begin receiving its routing updates from other routers. For example, in RIP, the default holddown timer is set to 180 seconds.

ReferencesEdit

Template:Reflist