Re: RIP Timers

From: <kebramccie_at_gmail.com>
Date: Sat, 20 Feb 2010 05:45:49 +0000

Hi sarad,

The holddown timer specifies the time duration updates regarding better paths are surpressed. A route enters a hold down state when an update packet is received that a route is unreachable. The routes hop count will be increased to 16 hence marked unreachable to other neighbors. However, rip running routers will continue to forward packets until an update is received with a better metric or until the hold down timer expires. When hold down expires, routes advertised by other sources are accepted and the route is no longer accessible.

Answering your question I think new routes are added after the hold down period. More experienced guys should please let me know if my reasoning is wrong as I have nt labbed this up.

HTH (that's if this helps.. :)

Kabir
------Original Message------
From: Sarad
Sender: nobody_at_groupstudy.com
To: groupstudy
ReplyTo: Sarad
Subject: RIP Timers
Sent: Feb 20, 2010 03:53

Hi All,

I have some concerns on RIP timers. Would like to clear it out, As per RIP
default timers, Update = 30, Invalid = 180, holddown=180, flush = 240
Let say a router got an update saying particular destination is down. Ok
then it will go to invalid after 180 seconds time between the Invalid (180)
to flush(240) router still route the packet to destination ie its still in
the routing table. It's only will be removed after flush timer expires.

My question is Ok if I get a new route with larger metric to the same
destination it will not be install to the routing table untill holddown
timer expires let say when hold down timer expires it will add the new route
to the Routing table but my question is as Holddown timer is less than the
flush timer how can a router can add a route with a higher distance before
flush timer expire. Or will hold down timer will trigger the flush timer.

Whats the best debug or show command to monitor this set up?

Thanks
Sara

Blogs and organic groups at http://www.ccie.net
Received on Sat Feb 20 2010 - 05:45:49 ART

This archive was generated by hypermail 2.2.0 : Mon Mar 01 2010 - 06:28:36 ART