Holddown Timers in Distance Vector Routing Protocols

Learn how RIP holddown timers use temporary route suppression after failures to reduce routing loops, route flapping, and stale route acceptance.

A holddown timer is a distance vector routing stability mechanism. It starts after a router declares a destination unreachable and temporarily restricts how the router accepts new information about that destination.

The purpose is to prevent a router from immediately trusting a reachable-route advertisement that may be stale or incorrect. This delay can reduce routing loops and route flapping after a link or network failure.

Prerequisites and Distance Vector Context

This lesson assumes familiarity with IPv4 addressing, routing tables, static and dynamic routing, RIP hop-count metrics, neighbor advertisements, and basic routing-loop behavior.

In a distance vector routing protocol, each router learns destinations from neighboring routers. It advertises reachability and a metric, then periodically exchanges routing information with its neighbors. A router generally does not have a complete map of the network; it relies on what neighbors report.

That reliance can create problems after a failure. One router may know that a destination is down while another still has an older route. Delayed, inconsistent, or stale advertisements can make a failed destination appear reachable. Routers may then forward packets toward one another in a routing loop, or repeatedly alternate between reachable and unreachable states, known as route flapping.

RIP, the Routing Information Protocol, is the primary example in this lesson. RIP uses hop count as its metric. Timer behavior can differ among routing protocols and between platform implementations, so a RIP value should not automatically be applied to every distance vector protocol.

What a Holddown Timer Does

When a router receives an advertisement indicating that a destination is unreachable, it marks the route as unreachable and starts a holddown interval. During that interval, reachable advertisements for the same destination are generally not accepted immediately from other neighbors.

The router is effectively saying: “This destination was just reported as failed, so I will not quickly replace that information with a potentially stale claim.” Once the timer expires, the router can again consider eligible route advertisements and install a valid replacement path.

Implementations may treat an update from the neighbor that originally advertised the route differently. That neighbor is the direct source of the route information and is in the best position to report whether its previously advertised path has recovered or changed. In common RIP behavior, an appropriate update from that original advertising neighbor can be considered during holddown, while competing reachable information from another neighbor is commonly suppressed. Always verify the behavior for the specific platform and software version.

Holddown Timer Event Sequence

Event	Route Information Received	Router Action	Holddown State	Effect on Route Installation
Normal route learned from neighbor	Reachable destination with a usable metric	Installs or refreshes the route and records the advertising neighbor	Inactive	Route can be used for forwarding
Unreachable update received	RIP metric 16, representing infinity	Marks the destination unreachable and starts the holddown timer	Active	Failed route is not treated as a usable path
Reachable update received from another neighbor during holddown	Finite metric claiming reachability	Generally ignores or suppresses the competing information	Active	New route is normally not installed immediately
Update received from original advertising neighbor during holddown	An update from the neighbor that supplied the original route	May process the update according to the implementation and update type	Active	Relevant recovery information may be accepted; verify platform behavior
Holddown timer expiration	Subsequent eligible advertisements can be evaluated	Ends the temporary restriction	Inactive	A valid replacement route may be installed

RIP Timer Values and Metrics

A common Cisco IOS RIP timer set is 30 seconds for periodic updates, 180 seconds for invalid, 180 seconds for holddown, and 240 seconds for flush. These are typical reference values, not a universal rule for every implementation.

Periodic update timer: controls the regular interval at which RIP sends routing updates.
Invalid timer: identifies how long a route can remain unrefreshed before it is considered invalid.
Holddown timer: temporarily restricts acceptance of replacement information after an unreachable route is reported.
Flush timer: controls when a route is removed from the routing table or routing process after it becomes invalid.

These timers have different purposes. The holddown timer is not the same as the update, invalid, or flush timer. Their interactions influence how quickly RIP detects, propagates, suppresses, and removes failed routes.

RIP measures distance in hops. A directly reachable network has a low hop count, and each routed hop increases the metric. A RIP metric of 16 is the infinity metric: it means the destination is unreachable. A route with metric 16 is not a valid forwarding path.

Item	Typical RIP Value	Purpose	Relationship to Holddown
Periodic update timer	30 seconds	Sends regular routing information	Periodic updates may communicate the failure or recovery
Invalid timer	180 seconds	Declares a route invalid when it is not refreshed	Route invalidation can be associated with later holddown processing
Holddown timer	180 seconds	Temporarily restricts new route information after failure	Provides the post-failure stability interval
Flush timer	240 seconds	Removes an invalid route from the routing process	Controls removal, not temporary acceptance suppression
Unreachable metric	16	Represents infinity in RIP	Often triggers the failure state that starts holddown

Two-Router RIP Failure Walkthrough

Consider this topology:

R1 and R2 share a point-to-point transit link, such as 192.0.2.0/30.
R1 uses 192.0.2.1 on the transit link.
R2 uses 192.0.2.2 on the transit link. This directly connected address identifies R2 as the original advertising neighbor from R1's perspective.
R2 provides reachability to the remote network 10.0.0.0/24.

Before the failure, R2 advertises 10.0.0.0/24 to R1. R1 installs a RIP route such as “10.0.0.0/24 via 192.0.2.2” with a usable hop-count metric, commonly 1 from R1's perspective.

Now suppose the network behind R2 fails. R2 advertises 10.0.0.0/24 with metric 16. This is route poisoning: R2 communicates that the destination is unreachable rather than advertising a normal finite metric.

R1 receives the metric-16 advertisement from R2.
R1 marks 10.0.0.0/24 unreachable and starts its holddown timer.
During holddown, R1 generally does not accept a reachable advertisement for 10.0.0.0/24 from an unrelated neighbor. This protects R1 from stale information that could recreate a loop.
An update from the original advertising neighbor, R2 at 192.0.2.2, is the relevant exception. Depending on the implementation and update, R1 may process that information during holddown because R2 owns the failed advertisement source.
When holddown expires, R1 can again evaluate eligible reachable advertisements and install a valid replacement route.

The neighbor is identified by the directly connected interface address from which the route was learned, not by an unrelated address elsewhere in the topology. In this example, that address is R2's 192.0.2.2 address on the R1-R2 link.

Holddown and Other Loop-Prevention Mechanisms

Distance vector protocols use several complementary techniques. None of these mechanisms is identical to holddown, and holddown is not a universal solution for every routing loop.

Mechanism	What It Does	When It Applies	How It Relates to Holddown
Route poisoning	Advertises a failed route with an unreachable metric	When a route fails or is withdrawn	Communicates the failure; holddown governs later acceptance behavior
Split horizon	Does not advertise a learned route back through the interface from which it was learned	During normal route advertisement	Prevents some loops before they form; it does not provide a timed post-failure restriction
Poison reverse	Advertises a learned route back toward its source with an unreachable metric	During advertisements toward the source neighbor	Strengthens split-horizon signaling; it is not a holddown timer
Triggered updates	Sends an update soon after a topology change instead of waiting for the periodic interval	Immediately after a route change	Speeds failure propagation, while holddown may delay acceptance of competing recovery information
Maximum RIP hop count	Limits the distance a RIP route can have; metric 16 means unreachable	Whenever RIP evaluates hop count	Bounds count-to-infinity behavior; it does not decide when reachable updates are accepted
Holddown timer	Temporarily restricts new information about a failed destination	After an unreachable route is reported	Provides time-based stability after the failure notification

Stability Versus Convergence

Convergence is the process by which routers update their information and reach a consistent view of network paths. Holddown can improve convergence stability by reducing incorrect route changes, but it can also make convergence slower.

If a valid alternate path becomes available shortly after the original path fails, holddown may postpone its installation. That delay is useful when the alternate advertisement could be stale and might create a loop. However, in a network with a genuinely healthy replacement path, a long holddown can extend the outage.

Timer interactions matter during troubleshooting. The update, invalid, holddown, and flush timers affect different parts of failure processing. A route may remain unavailable because it is in holddown, because no valid advertisement has arrived, because the original neighbor has not reported recovery, or because the timers were changed from their defaults.

Cisco IOS RIP Lab

The following example uses R1 and R2 with a transit network of 192.0.2.0/30 and a remote LAN of 10.0.0.0/24 behind R2. Replace interface names with those used by your lab platform.

R1 configuration

interface GigabitEthernet0/0
 ip address 192.0.2.1 255.255.255.252
 no shutdown
!
router rip
 version 2
 no auto-summary
 network 192.0.2.0

R2 configuration

interface GigabitEthernet0/0
 ip address 192.0.2.2 255.255.255.252
 no shutdown
!
interface GigabitEthernet0/1
 ip address 10.0.0.1 255.255.255.0
 no shutdown
!
router rip
 version 2
 no auto-summary
 network 192.0.2.0
 network 10.0.0.0

After the RIP relationship forms, verify that R1 learns 10.0.0.0/24 through 192.0.2.2. To simulate failure, enter shutdown on R2's interface connected to the 10.0.0.0/24 network. Use no shutdown to restore the interface.

Verification commands

show ip route
show ip route rip
show ip protocols
show ip rip database
debug ip rip

Use debug ip rip only in a lab or controlled environment because debugging can generate substantial output and consume device resources. Look for the poisoned metric 16 advertisement, the source neighbor, and subsequent route changes.

Optional advanced demonstration: Cisco IOS can display or change RIP timers with the timers basic update invalid holddown flush command, for example timers basic 30 180 180 240. Changing timers affects convergence behavior and should not be performed casually in production. Timer values must be coordinated and tested.

Troubleshooting Holddown Behavior

A RIP route remains unreachable

Check whether the route is currently in holddown.
Determine whether a replacement advertisement is being suppressed during the holddown interval.
Confirm that the original advertising neighbor has sent an appropriate valid update.
Review RIP process and timer information with show ip protocols.
Inspect the routing table with show ip route and the RIP database with show ip rip database where supported.
Confirm interface state and reachability to the advertising neighbor.

A metric-16 route is mistaken for a valid path

Remember that RIP's maximum usable hop count is 15.
Metric 16 is infinity and means unreachable.
Check whether the metric-16 update is route poisoning following a topology failure.
Correlate the update with the affected interface and remote network state.

Convergence is unexpectedly slow

Holddown may be delaying acceptance of alternate information.
The router may be waiting for periodic updates if a triggered update was not sent or observed.
Timer values may have been changed from the defaults.
A flapping route or interface may be repeatedly changing state.
Review timer settings, interface transitions, route metrics, split horizon, and route-poisoning behavior.

Key Exam Notes

A holddown timer starts after a route is declared unreachable.
Its purpose is to suppress potentially stale reachable information and reduce loops or flapping.
RIP commonly uses a 180-second holddown value.
RIP metric 16 means infinity, or unreachable; it is not a usable 16-hop route.
Route poisoning is the failure advertisement. Holddown is the receiving router's temporary acceptance rule.
Split horizon, poison reverse, triggered updates, maximum hop count, and holddown address different parts of the loop-prevention problem.
Holddown improves stability at the cost of potentially slower recovery.
Exact timer behavior can vary by routing protocol, operating system, software release, and implementation.

For a concise reference to this subject, see Holddown Timer Explained.