From: Snow, Tim (timothy.snow@eds.com)
Date: Tue Dec 30 2003 - 05:52:27 GMT-3
Without handing the answer away and not allowing you to learn anything, I
will have to tell you this and let you do the work.  Dialer watch does not
have any provisions to tell it how long after a route disappears before
it'll call.  You'll have to figure it out.
 
Of course there is a version of code that has provisions for this but you
may want to look that up on your own too.
 
Tim
#12042
-----Original Message-----
From: Pun, Alec CL [mailto:Alec.CL.Pun@pccw.com] 
Sent: Tuesday, December 30, 2003 3:44 AM
To: Snow, Tim; Sumit.kumar@comcast.net; Danny.Andaluz@triaton-na.com;
ccielab@groupstudy.com
Subject: RE: dialer-watch question
Agreed, any example for dialer-watch + backup interface ? thanks 
alec 
-----Original Message----- 
From: Snow, Tim [mailto:timothy.snow@eds.com <mailto:timothy.snow@eds.com> ]
Sent: Tuesday, December 30, 2003 4:37 PM 
To: Pun, Alec CL; Sumit.kumar@comcast.net; Danny.Andaluz@triaton-na.com; 
ccielab@groupstudy.com 
Subject: RE: dialer-watch question 
Dialer-watch watches and route that's in the RT and will trigger a call once
the primary path goes down. Regardless of protocol 
DC causes a dial based on a OSPF topology change.  This is OSPF dependant 
and is for any route or any change in the table (not just any time SPF is 
run) 
So basically it comes down to what protocols (if any) you are running on 
your ISDN.  If you happen to be running OSPF on your ISDN circuit than it 
really doesn't benefit you much because if the route your watching is 
learned via OSPF then OSPF would have triggered the call anyways based on a 
topo change.  If that route is NOT part of OSPF directly and is learned via 
another protocol but being injected into OSPF then the ISDN would have 
dialed anyways because of another topo change.  The only scenario that they 
wouldn't conflict is if you were watching a route via another protocol and 
NOT redistributing into OSPF, but in that case putting OSPF DC on the ISDN 
would do nothing for you anyways. 
So, I think the answer is no.  Backup int and dialer-watch or other 
technologies can work well together though, you just have to analyze how 
your using them 
Tim 
#12042 
-----Original Message----- 
From: Pun, Alec CL [mailto:Alec.CL.Pun@pccw.com
<mailto:Alec.CL.Pun@pccw.com> ] 
Sent: Tuesday, December 30, 2003 3:24 AM 
To: Sumit.kumar@comcast.net; Danny.Andaluz@triaton-na.com; 
ccielab@groupstudy.com 
Subject: RE: dialer-watch question 
is it reasonable to configure dialer-watch and demand circuit if the 
question asked to bring up the ISDN for any topology change as well as to 
watch for some subnet ? 
rgds, 
alec 
-----Original Message----- 
From: Sumit.kumar@comcast.net [mailto:Sumit.kumar@comcast.net
<mailto:Sumit.kumar@comcast.net> ] 
Sent: Tuesday, December 30, 2003 1:15 PM 
To: Pun, Alec CL; Danny.Andaluz@triaton-na.com; ccielab@groupstudy.com 
Subject: Re: dialer-watch question 
Alec, 
Dialer-watch is optimal in Hub and Spoke topology where Spoke router watches
the remote Hub site route and triggers a call in case that route disappears 
from routing table (for any reason). Dialer-watch works optimally with 
routing protocols like OSPF and BGP and one-way configuration is enough 
unless you want to have additional redundancy(Imagine a central site with 
100+ branch sites). To make it work both way you will have to configure 
100+ DW 
to watch route(s) at each site of the opposite sides. 
Danny, 
I agree with you that dialer  watch doesn't need interesting traffic to 
bring up the isdn or down but the Routing protocols multicast updates do 
trigger ISDN calls so it is a good practice to deny the routing protocols as
interesting traffic. 
good luck 
Sumit 
----- Original Message ----- 
From: "Pun, Alec CL" <Alec.CL.Pun@pccw.com> 
To: <Danny.Andaluz@triaton-na.com>; <ccielab@groupstudy.com> 
Sent: Monday, December 29, 2003 9:52 PM 
Subject: RE: dialer-watch question 
> I agree with you that dialer-group should take away or deny OSPF since 
> it will always bring up the line. 
> 
> But if we configure dialer watch on both ends, once the watched route 
> disappear, both side will make call at the same time !! Isn't that is 
> not suggested by Cisco ? 
> 
> rgds, 
> alec 
> 
> -----Original Message----- 
> From: Danny.Andaluz@triaton-na.com 
> [mailto:Danny.Andaluz@triaton-na.com <mailto:Danny.Andaluz@triaton-na.com>
] 
> Sent: Tuesday, December 30, 2003 3:43 AM 
> To: Pun, Alec CL; ccielab@groupstudy.com 
> Subject: RE: dialer-watch question 
> 
> 
> 
> I didn't see the part about both routers dialing.  Configure dialer 
> watch 
on 
> both then. 
> 
> IP won't trigger the call if you're running Dialer-watch, so again, it 
> shouldn't matter.  EIGRP and OSPF use MC addresses to communicate back 
> and forth (224.0.0.10 and 224.0.0.5 respectively).  This is included 
> in IP. 
> 
> I would include a "dialer-group <list number>" with a "dialer-list 
> <list 
> number> protocol ip permit".  I was just pointing out how it does not 
> number> use 
> this dialer-list traffic to initiate a call. 
> 
> Danny 
> 
> -----Original Message----- 
> From: Pun, Alec CL [ mailto:Alec.CL.Pun@pccw.com
<mailto:Alec.CL.Pun@pccw.com>  
> <mailto:Alec.CL.Pun@pccw.com <mailto:Alec.CL.Pun@pccw.com> > ] 
> Sent: Monday, December 29, 2003 1:22 PM 
> To: Andaluz, Danilo, Triaton/NA; ccielab@groupstudy.com 
> Subject: RE: dialer-watch question 
> 
> 
> Danny, 
> 
> Some questions 
> 1) What if both routers can initiate ISDN calls ? 
> 2) Understand that dialer-watch itself is an interesting traffic.  But 
> if 
we 
> don't deny OSPF hello, won't it always kick up the line ? I just want 
> to know if it is a MUST to either remove the dialer-group or deny 
> OSPF/EIGRP hello when using dialer-watch together. 
> 
> 
> rgds, 
> alec 
> 
> -----Original Message----- 
> From: Danny.Andaluz@triaton-na.com [ 
> mailto:Danny.Andaluz@triaton-na.com <mailto:Danny.Andaluz@triaton-na.com>
> <mailto:Danny.Andaluz@triaton-na.com <mailto:Danny.Andaluz@triaton-na.com>
> ] 
> Sent: Tuesday, December 30, 2003 2:15 AM 
> To: Pun, Alec CL; ccielab@groupstudy.com 
> Subject: RE: dialer-watch question 
> 
> 
> 
> I would say configure Dialer-Watch only on the calling router.  Only 
> the calling router needs to have this configured. 
> 
> As far as the OSPF hello's, it shouldn't matter.  Dialer-Watch is 
> watching for the loss of a route.  That is the "interesting" traffic, 
> not IP 
traffic. 
> I have tested dialer-watch with no dialer-group configured on the BRI 
> or Dialer interface.  It works fine.  Try it. 
> 
> HTH, 
> Danny 
> 
> -----Original Message----- 
> From: Pun, Alec CL [ mailto:Alec.CL.Pun@pccw.com
<mailto:Alec.CL.Pun@pccw.com>  
> <mailto:Alec.CL.Pun@pccw.com <mailto:Alec.CL.Pun@pccw.com> >  <
mailto:Alec.CL.Pun@pccw.com <mailto:Alec.CL.Pun@pccw.com>  
> <mailto:Alec.CL.Pun@pccw.com <mailto:Alec.CL.Pun@pccw.com> > > ] 
> Sent: Monday, December 29, 2003 11:41 AM 
> To: ccielab@groupstudy.com 
> Subject: dialer-watch question 
> 
> 
> Hi group, 
> 
> R1 ---- ISDN ------ R2 
>  |                         | 
>  |----------FR-----------| 
> 
> Both R1 and R2 can make ISDN calls and the topology is running OSPF.  
> My question is if dialer-watch is used to watch the remote loopback, 
> is it necessary 
> 
> 1) to configure dialer-watch on both routers ? 
> 2) deny ospf hello in the dialer-list for BOTH routers ? 
> 
> rgds, 
> alec 
> 
> ______________________________________________________________________ 
> _ 
> Please help support GroupStudy by purchasing your study materials from: 
> http://shop.groupstudy.com <http://shop.groupstudy.com>
<http://shop.groupstudy.com <http://shop.groupstudy.com> >  < 
> http://shop.groupstudy.com <http://shop.groupstudy.com>
<http://shop.groupstudy.com <http://shop.groupstudy.com> > > 
> 
> Subscription information may be found at: 
> http://www.groupstudy.com/list/CCIELab.html
<http://www.groupstudy.com/list/CCIELab.html>  
> <http://www.groupstudy.com/list/CCIELab.html
<http://www.groupstudy.com/list/CCIELab.html> > 
> < http://www.groupstudy.com/list/CCIELab.html
<http://www.groupstudy.com/list/CCIELab.html>  
> <http://www.groupstudy.com/list/CCIELab.html
<http://www.groupstudy.com/list/CCIELab.html> > > 
> 
> ______________________________________________________________________ 
> _ 
> Please help support GroupStudy by purchasing your study materials from: 
> http://shop.groupstudy.com <http://shop.groupstudy.com>
<http://shop.groupstudy.com <http://shop.groupstudy.com> > 
> 
> Subscription information may be found at: 
> http://www.groupstudy.com/list/CCIELab.html
<http://www.groupstudy.com/list/CCIELab.html>  
> <http://www.groupstudy.com/list/CCIELab.html
<http://www.groupstudy.com/list/CCIELab.html> > 
> 
> ______________________________________________________________________ 
> _ 
> Please help support GroupStudy by purchasing your study materials from: 
> http://shop.groupstudy.com <http://shop.groupstudy.com>  
> 
> Subscription information may be found at: 
> http://www.groupstudy.com/list/CCIELab.html
<http://www.groupstudy.com/list/CCIELab.html>  
This archive was generated by hypermail 2.1.4 : Sat Jan 03 2004 - 08:25:46 GMT-3