From: Christian Sica (csica@liweb.net)
Date: Fri Oct 28 2005 - 13:40:07 GMT-3
Yes it does. This is what Cisco says:
"After the backup link is up, the primary link is checked again at the
expiration of each idle timeout. If the primary link remains down, the idle
timer is reset. Since the router should periodically check whether the
primary link has been reestablished, configure a small value for the dialer
idle-timeout. When the primary link is reestablished, the routing protocol
will update the routing table and all traffic should once again pass on the
primary link. Since traffic will no longer pass across the backup link, the
idle timeout will expire and router will deactivate the backup link."
So once the primary route is back up and in the routing table, the idle
timeout will cause the ISDN line to go down. Since there is a valid route
in your routing table, dialer watch will not trigger another call until the
route drops out again.
HTH,
Christian
_____
From: Venkataramanaiah.R [mailto:vramanaiah@gmail.com]
Sent: Friday, October 28, 2005 11:59 AM
To: Christian Sica
Subject: Re: Dialer Watch - and Interesting Traffic
Agree with you, but does that ever bring down the isdn link whenever the
primary comes back...?
Would you mind checking that...
thanks
-Venkat
On 10/28/05, Christian Sica <csica@liweb.net> wrote:
Venkat,
Configuring the "dialer-group" command is not required for dialer watch to
operate. The "dialer-group" command can be used in conjunction with the
dialer watch feature if you want to bring up the isdn line for other
reasons. However, dialer watch has its own dialing mechanism. When the
route it's watching drops out of the routing table, it searches for another
viable route, and if it finds none, it then uses the dialer map you
configured for the watched route to trigger the call. Note the debug dialer
output below that shows the reason for the call:
*Mar 1 10:29:40.189: BRI0/0: wait for isdn carrier timeout, call id=0x8003
*Mar 1 10:29: 40.189: DDR: Dialer Watch: watch-group = 1
*Mar 1 10:29:40.189: DDR: network 150.1.4.0/255.255.255.0 UP,
*Mar 1 10:29:40.189: DDR: primary DOWN
*Mar 1 10:29: 43.189: BR0/0 DDR: Attempting to dial 5937826
Check here for more information:
http://www.cisco.com/warp/public/129/bri-backup-map-watch.html#dialerwatchop
eration
HTH,
Christian
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com
<mailto:nobody@groupstudy.com> ] On Behalf Of
Venkataramanaiah.R
Sent: Friday, October 28, 2005 5:22 AM
To: Pierre-Alex GUANEL
Cc: The Great Ryan; george.cosmo@gmail.com; ccielab@groupstudy.com
Subject: Re: Dialer Watch - and Interesting Traffic
That means dialer-group must be configured but with all traffic made
uninteresting. This is to permit dialer watch check the status of primary
link at regular interval, which is the idle-timeout.
Correct me if i am wrong...
-Venkat
On 10/28/05, Pierre-Alex GUANEL <paguanel@gmail.com> wrote:
>
> Correct!
>
> "With dialer watch, the router monitors the existence of a specified route
> and if that route is not present, it initiates dialing of the backup link.
> Unlike the other backup methods (such as backup interface or floating
> static
> routes) dialer watch does not require interesting traffic to trigger the
> dial. "
>
> For best practices:
>
> "Configure on caller router routing protocols as uninteresting in the
> interesting traffic definition to prevent periodic hellos from resetting
> the
> idle timeout. Since the router uses the interesting traffic definition
> ONLY
> to check whether the primary link is active, consider making all IP
> traffic
> uninteresting using the command dialer-list number protocol ip deny. With
> this interesting traffic definition, the idle timeout is never reset, and
> the router checks the status of the primary link at the specified
> interval.
> "
>
> http://www.cisco.com/warp/public/123/backup-main.html
>
> Cheers,
>
> Pierre
>
>
> ----- Original Message -----
> From: "The Great Ryan" <pv.ryan@gmail.com>
> To: "George Cosmo" < <mailto:george.cosmo@gmail.com>
george.cosmo@gmail.com>
> Cc: "Cisco certification" <ccielab@groupstudy.com>
> Sent: Friday, October 28, 2005 7:06 AM
> Subject: Re: Dialer Watch - and Interesting Traffic
>
>
> > Without interesting interface, I think you don't need to configure
> > "dialer-group" on bri interface
> >
> > If you choose to use dialer watch-group, you should define watch-list
> > & dialer map ip <ip-being-monitored> to kick the BRI up.
> >
> >
> > Regards,
> > Ryan
> >
> > 2005/10/28, George Cosmo < <mailto:george.cosmo@gmail.com>
george.cosmo@gmail.com>:
> >> Case:
> >> *There is no routing protocol on ISDN, I am using dialer watch to
> >> provide
> >> backup. ISDN should only come up in case of network failure. *
> >> **
> >> - Do I need interesting traffic, as if I have a default route and I
> ping
> >> any
> >> address that is not in my routing table ISDN will come up.
> >> - Even there is a dialer watch applied ISDN will come up in case there
> is
> >> a
> >> interesting traffic.
> >> what is a good practice ? no interesting traffic define with dialer
> >> watch?
> >> thanks !
> >>
> >> _______________________________________________________________________
> >> 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
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:55 GMT-3