From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Fri Oct 17 2003 - 17:24:01 GMT-3
Ken,
Assuming you are only dialing from one side set the idle timeout
on the side that is being called (the one not doing the watch) to 0. On
the side that is doing the watch, the idle timeout will determine both
how long the device will keep the link up when there is normal
interesting traffic, and how often the dialer-watch process will check
the routing table to see if the primary route is back.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 708-362-1418 (Outside the US and Canada)
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Jonathan V Hays
> Sent: Friday, October 17, 2003 1:34 PM
> To: Ken.Farrington@barclayscapital.com; ccielab@groupstudy.com
> Subject: RE: Dialer Watch
>
> Dialer-watch will bring up the line and nail it up, depending only on
> the watched route. It does not pay any attention to interesting
traffic
> as far as bringing up the line or keeping it up. Dialer-watch works
> independently of interesting traffic.
>
> So whether or not 224.0.0.10 brings up the link is a separate issue
from
> dialer-watch.
>
> Since dialer-watch is configured on one side only (I'll call it the
> local side), when the watched route is gone and the line is brought up
> by dialer-watch, the remote side will time out after 120 seconds
> (default idle-timeout is 120) and drop the line. Dialer-watch will
just
> bring it back up again every time this happens. To avoid this link
> flapping, just set dialer idle-timeout to 0 (which means never time
out)
> on the remote side of the link.
>
> HTH,
>
> Jonathan
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Ken.Farrington@barclayscapital.com
> Sent: Friday, October 17, 2003 2:04 PM
> To: ccielab@groupstudy.com
> Subject: Dialer Watch
>
>
> Hey gang,
>
> just a thought, if you use dialer-watch to watch a route and I use
> EIGRP
> over this, i dont want 224.0.0.10 to bring the cct up so i mark it as
> "uninteresting" (Bit like watching Manchester United play football).
>
> so,
>
> when the watched route goes down, the isdn kicks in, but now, i want
to
> keep the cct up whilst the dialer software reports the primary route
as
> down
> and not have an ISDN idle-timeout or it would be nice to allow eigrp
> hellos
> keep the cct up so that my routing table is stable on this router (but
> is
> already marked as Manu, opps, sorry, uninteresting).
>
> Can I do this, thing is, I dont want to set the dialer idle-timer to
0
> cause I still need an idle timeout incase someone pings the other side
> of
> the int.
>
> Basically, want dialer-watch to ensure that while it is reporting the
> watched route as down, there is no dialer idle timeout value.
>
> Is this achievable,
>
> I know that Manchester United will never play exciting football, but
> that's
> ok, I'm an Arsenal Fan :))
>
> Cheers :))
>
> Ken.
>
>
>
------------------------------------------------------------------------
> For more information about Barclays Capital, please
> visit our web site at http://www.barcap.com.
>
>
> Internet communications are not secure and therefore the Barclays
> Group does not accept legal responsibility for the contents of this
> message. Although the Barclays Group operates anti-virus programmes,
> it does not accept responsibility for any damage whatsoever that is
> caused by viruses being passed. Any views or opinions presented are
> solely those of the author and do not necessarily represent those of
the
>
> Barclays Group. Replies to this email may be monitored by the
Barclays
> Group for operational or business reasons.
>
>
------------------------------------------------------------------------
>
>
This archive was generated by hypermail 2.1.4 : Mon Nov 24 2003 - 07:53:04 GMT-3