Bah...can't be the hold time timer because that wouldn't start unless the
route was time out (invalid timer expired).....I need sleep. If anybody has
any legitimate ideas let me know it's driving me a bit crazy
On Wed, Jul 13, 2011 at 8:23 PM, Joe Astorino <joeastorino1982_at_gmail.com>wrote:
> OK so I think I figured it out. Simple -- RIP hold timer. If a RIP router
> sees a route with a HIGHER metric hop-count than the one it currently has,
> the hold timer has to expire first to prevent what I'm trying to do from
> happening : ) So ...not nearly as dramatic as I had thought and has NOTHING
> to do with frame-relay and DLCIs, just a general function of RIP
>
> I'm pretty sure it is just a hold timer thing.
>
> This is what happens when I don't get enough sleep or as Scott would say
> "not nearly enough caffeine". Still, thanks for reading and I welcome any
> comments
>
>
>
> --
> Regards,
>
> Joe Astorino
> CCIE #24347
> Blog: http://astorinonetworks.com
>
> "He not busy being born is busy dying" - Dylan
>
>
-- Regards, Joe Astorino CCIE #24347 Blog: http://astorinonetworks.com "He not busy being born is busy dying" - Dylan Blogs and organic groups at http://www.ccie.netReceived on Wed Jul 13 2011 - 20:35:02 ART
This archive was generated by hypermail 2.2.0 : Mon Aug 01 2011 - 06:30:05 ART