From: NGUYEN Trung (trung@vnsystem.net)
Date: Sun Apr 03 2005 - 08:08:28 GMT-3
Hi,
And the isdn can't be disconnected when the primary link comes up, if the
metric of the backup is better than the primary.
If i configure with "dialer watch-disable 30", then i think the isdn will be
terminated in 30 secs after the idle-timeout exprired.
But in fact. i tested on lab and it did not work.
I didn't test with "dialer watch-list x delay disconnect" cmd but i believe
it would work.
A confirmation will be greatly appreciated.
Thanks
N.Trung
----- Original Message -----
From: "Brian Dennis" <bdennis@internetworkexpert.com>
To: "Sundar Palaniappan" <sundarp@gmail.com>; <ccielab@groupstudy.com>
Sent: Sunday, April 03, 2005 11:43 AM
Subject: RE: Dialer Watch idle timeout
> <Quote>
> When the ISDN call comes up because of watched route loss how does the
> dialer idle-timeout functions. Does it reset the link after 120
> seconds (default) and interface comes up again because the watched
> route is still missing.
> </Quote>
>
> When the idle-timeout starts to expire, dialer watch will "wake up" and
> check to see if the watched route is still missing from the routing
> table. If the watched route is still missing, the router will reset the
> idle-timeout. To effect how often dialer watch checks the routing
> table, use the "dialer idle-timeout" command. The default value is 120
> seconds of course. Lastly use the "debug dialer" command to verify the
> dialer watch operation.
>
> <Quote>
> Even if the router that made the call doesn't disconnect the call the
> far end router would disconnect the call after 120 seconds. The
> solution would be to set the idle timeout to 0. Here is the problem
> though, the far end router is also allowed to dial when there is some
> interesting traffic (eg. icmp) anytime this router dials it will never
> disconnect the call, which isn't allowed.
> </Quote>
>
> Just put the "dialer idle-timeout 120 either" command on the router with
> dialer watch configured so that it'll drop the link due to the lack of
> interesting traffic when the call is received from the remote router.
>
> HTH,
>
> Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
>
> bdennis@internetworkexpert.com
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987
> Direct: 775-745-6404 (Outside the US and Canada)
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Sundar Palaniappan
> Sent: Saturday, April 02, 2005 7:51 PM
> To: ccielab@groupstudy.com
> Subject: Dialer Watch idle timeout
>
> Guys,
>
> I have a couple of doubts regarding dialer watch. Hope I can clear up
> from the group.
>
> When the ISDN call comes up because of watched route loss how does the
> dialer idle-timeout functions. Does it reset the link after 120
> seconds (default) and interface comes up again because the watched
> route is still missing.
>
> Even if the router that made the call doesn't disconnect the call the
> far end router would disconnect the call after 120 seconds. The
> solution would be to set the idle timeout to 0. Here is the problem
> though, the far end router is also allowed to dial when there is some
> interesting traffic (eg. icmp) anytime this router dials it will never
> disconnect the call, which isn't allowed.
>
> TIA,
> Sundar Palaniappan
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue May 03 2005 - 07:54:52 GMT-3