I should read more carefully on a Monday morning. My earlier reply "disappeared" because it was under a different heading. Your earlier experiment proved that route poisoning was working as it should.
I'm off to eat raw coffee beans.... s vermill wrote: > > My earlier reply must have went into the bit bucket. Here goes > again... > > The hold down timer doesn't prevent the triggered update from > poisoning the bad route. It prevents the router that just > received the poison update from accepting any new updates that > would indicate the route is back up. I think the exception is > if an update comes in with a better metric than the originally > poisoned route. > > Try shutting and no shutting the interface. The route should > dissappear immediately but not show back up for hold down > time. This is a stability feature. > > Pierre-Alex GUANEL wrote: > > > > Cisco does not seem to support poison reverse for RIP and RIP > > version 2. > > > > Do you know network vendors who do? > > > > Pierre-Alex > > > > > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=33446&t=33402 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
