From: Yasser Abdullah (yasser@alharbitelecom.com)
Date: Fri May 28 2004 - 14:17:27 GMT-3
Ok, just tested RIP with dialer-watch.
The dialer-watch was not initiated until the route was off the routing
table. When the route was inaccessible, dialer-watch still considered the
primary route to be up and so didn't start.
So basically, without modifying the timers, my router took more than 240 sec
to fire the dialer-watch.
Brgds,
Yasser
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Friday, May 28, 2004 7:07 PM
To: Group Study; Yasser Abdullah
Subject: Re: ISDN Dialer-Watch Question - kick-in delay
Hey Yasser,
Thanks, buddy. You confirmed my feelings about everything except RIP.
With rip, the route remains in the route table until the garbage (or flush)
timer expires. But, before that happens, the route is marked unreachable.
So, here's the question. Does Dialer Watch consider whether a route in the
route table is unreachable?
I don't know, but if it doesn't, Dialer Watch can wait a long time before
kicking in. What do ya think?
Tim
----- Original Message -----
From: "Yasser Abdullah" <yasser@alharbitelecom.com>
To: "'ccie2be'" <ccie2be@nyc.rr.com>; <ccielab@groupstudy.com>
Sent: Friday, May 28, 2004 11:37 AM
Subject: RE: ISDN Dialer-Watch Question - kick-in delay
> Yes, normally you don't need to change the delay timer in the watch-list,
> but it's good to know it anyway :)
>
> For the routing protocols: OSPF, ISIS & EIGRP you will need to change the
> hello timer. The dead (OSPF) and multiplier (ISIS) are automatically
> adjusted when you configure the hello interval. EIGRP, changing the hello
> will not automatically change the hold-time so you need to change both
> manually.
>
> For RIP, change the timers as you said.
>
> Brgds,
>
> Yasser
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> ccie2be
> Sent: Friday, May 28, 2004 6:05 PM
> To: Yasser Abdullah; ccielab@groupstudy.com
> Subject: Re: ISDN Dialer-Watch Question - kick-in delay
>
> Thanks, Yasser. But, I think if the objective is to speed up convergence,
> you don't have to worry about the dialer watch-list delay command because,
> by default, there is no delay. You only need to know which timers for
each
> protocol to adjust.
>
> Off-hand, these are the timers I'd change to speed convergence for each
> protocol.
>
> RIP - timers garbage parameter ( just a guess, I don't know if dialer
looks
> for when route is unreachable or actually not in route table)
>
> OSPF - Hello timer or Dead Interval
>
> ISIS - Hello or hello multiple??
>
> Eigrp - Hello timer?
>
> What's my score? 100%, 75%, 50 %, or 25% or 0%?
>
> Thanks
>
>
> ----- Original Message -----
> From: "Yasser Abdullah" <yasser@alharbitelecom.com>
> To: "'ccie2be'" <ccie2be@nyc.rr.com>; <ccielab@groupstudy.com>
> Sent: Friday, May 28, 2004 10:32 AM
> Subject: RE: ISDN Dialer-Watch Question - kick-in delay
>
>
> > There are two timers actually:
> >
> > 1- You might first need to modify the routing protocol timers to detect
> the
> > loss of the neighbor within an x amount of seconds. For example, if you
> have
> > OSPF running on NBMA network (type non-broadcast), then you will need to
> > adjust the hello timer.
> >
> > 2- You need to adjust the dialer-watch connect timer. This is done via
the
> > command" dialer watch-list x delay connect xyz". In this case, your
> > dialer-watch will activate the second link after xyz seconds from
> detecting
> > the loss of the route.
> >
> > Brgds,
> >
> > Yasser
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> > ccie2be
> > Sent: Friday, May 28, 2004 5:16 PM
> > To: Richard Dumoulin; vdadlaney@comcast.net; ccielab@groupstudy.com
> > Subject: Re: ISDN Dialer-Watch Question - kick-in delay
> >
> > Hey Guys,
> >
> > What determines how long it takes before Dialer Watch kicks in and
> triggers
> > a call?
> >
> > I suspect it depends on waht routing protocol is running and how long it
> > takes the routing protocol to remove the watched routes from the routing
> > table. Is this true?
> >
> > And, if so, is this info easily found on the Doc CD, so that I don't
have
> to
> > memorize this info for each routing protocol before the lab?
> >
> > Thanks in advance
> >
> >
> > ----- Original Message -----
> > From: "Richard Dumoulin" <richard.dumoulin@vanco.es>
> > To: <vdadlaney@comcast.net>; <ccielab@groupstudy.com>
> > Sent: Friday, May 28, 2004 9:27 AM
> > Subject: RE: ISDN Dialer-Watch Question
> >
> >
> > > Yes, with a dialer string instead. But I thought it was well known,
> > >
> > > --Richard
> > >
> > > -----Original Message-----
> > > From: vdadlaney@comcast.net [mailto:vdadlaney@comcast.net]
> > > Sent: viernes, 28 de mayo de 2004 15:11
> > > To: ccielab@groupstudy.com
> > > Subject: ISDN Dialer-Watch Question
> > >
> > >
> > > Hi, has anyone seen a scenario where dialer watch is used for isdn
> backup
> > > but there is no dialer map for the watched network. I always thought
> this
> > > was a requirement but I have seen this working perfectly without the
> > command
> > > in a production network. The route being watched is a default route of
> > > 0.0.0.0 which is being provided by the primary router which has the
> > primary
> > > link. Appreciate your thoughts on this. Thanks
> > >
> > >
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:19 GMT-3