From: ccie2be (ccie2be@nyc.rr.com)
Date: Fri May 28 2004 - 12:04:53 GMT-3
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
> >
> > _______________________________________________________________________
> > Please help support GroupStudy by purchasing your study materials from:
> > http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> > _______________________________________________________________________
> > Please help support GroupStudy by purchasing your study materials from:
> > http://shop.groupstudy.com
> >
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:18 GMT-3