From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Tue Aug 12 2003 - 23:03:33 GMT-3
You should look into using dialer interfaces on the hub or moving the
dialer watch function to the spokes.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Toll Free: 877-334-8987
Direct: 775-745-6404 (Outside the US and Canada)
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Tuesday, August 12, 2003 6:38 PM
To: Group Study; Ram Shummoogum
Subject: Re: dialer-watch config
Thanks again Ram. I read that thread and it helped alot. But, it also
raised another question. According to Brian Dennis, "If there is at
least
one of the watched routes in the routing table not learned by the backup
interface
the dialer watch feature will not trigger a call."
In the example below with the partial mesh frame relay network: If I'm
watching the loopback addresses of the 3 spoke routers and I want dialer
watch on the hub router to call the spoke router if the pvc from that
spoke
router goes down or the spoke router's f/r interface goes down, I'll
still
have the loopbacks from other 2 spoke routers. It sounds like in this
situation, according to Brian Dennis, dialer watch won't call the spoke
router because "there is at least one of the watched routes in the
routing
table".
Does this mean that dialer watch can't be used for this scenario on the
hub?
And, if I want to configure dialer watch, it has to be configured on
each
spoke router?
Thanks, dt
----- Original Message -----
From: "Ram Shummoogum" <rshummoo@ca.ibm.com>
To: <ccie2be@nyc.rr.com>
Cc: <ccielab@groupstudy.com>
Sent: Tuesday, August 12, 2003 7:50 PM
Subject: Re: dialer-watch config
> Read this link and follow the explanations from Brian Dennis:
>
> http://www.groupstudy.com/archives/ccielab/200307/msg00115.html
>
>
> HTH
>
>
>
>
>
>
>
>
> "ccie2be" <ccie2be@nyc.rr.com>@groupstudy.com on 08/12/2003 07:12:35
PM
>
> Please respond to "ccie2be" <ccie2be@nyc.rr.com>
>
> Sent by: nobody@groupstudy.com
>
>
> To: "Group Study" <ccielab@groupstudy.com>, Ram
> Shummoogum/Quebec/IBM@IBMCA
> cc:
> Subject: Re: dialer-watch config
>
>
> Hi,
>
> Thanks for getting back to me. I found an example of what you were
saying
> at this link:
>
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/d
ial_
>
> c/dcdbakdw.htm
>
> In this example, there are 3 routes listed in the dialer watch-list,
> 3.x.x.x, 4.x.x.x, and 5.x.x.x but there's only 2 dialer map
statements -
1
> for the ip addr of the other side of the dialup link and 1 for 3.x.x.x
>
> But, this is what I don't really understand. Why the dialer map for
> 3.x.x.x
> and not either 4.x.x.x or 5.x.x.x ?
>
> Would it work just as well if nets 4.x.x.x or 5.x.x.x were used
instead or
> did it have to be 3.x.x.x ?
>
> Also, I have another topology I'm wondering about.
>
> Suppose you have Frame Relay hub and spoke topology where r1 is the
hub
and
> is using a multipoint interface to reach r2, r3 and r4. All the
routers
> have bri interfaces and I want to have r1 using dialer watch call any
of
> the
> 3 spokes if their f/r interface goes down. Assume each spoke router
has a
> loopback interface such as 2.x.x.x, 3.x.x.x, and 4.x.x.x and these are
> exchanged via the routing protocol.
>
> In other words, I want r1 to call r2 if 2.x.x.x is no longer in the
route
> table or call r3 if 3.x.x.x is no longer in the route table or call r4
if
> 4.x.x.x is no longer in the route table. In this case, do I need 3
dialer
> map statements - 1 pointing to each of the spoke routers? And, are
there
> any other things I need to do to make this work?
>
> Thank you so much. dt
> ----- Original Message -----
> From: "Ram Shummoogum" <rshummoo@ca.ibm.com>
> To: <ccie2be@nyc.rr.com>
> Cc: <ccielab@groupstudy.com>
> Sent: Tuesday, August 12, 2003 6:25 PM
> Subject: Re: dialer-watch config
>
>
> > There is no need to have all watched routes in the dialer map
statements.
> > However, the watched list must cover all the watch routes.
> > The line will be triggered only after all the routes disappeared
from
the
> > routing table.
> > I have teste this already.
> >
> > "ccie2be" <ccie2be@nyc.rr.com>@groupstudy.com on 08/12/2003 05:53:45
PM
> >
> > Please respond to "ccie2be" <ccie2be@nyc.rr.com>
> >
> > Sent by: nobody@groupstudy.com
> >
> >
> > To: "Group Study" <ccielab@groupstudy.com>
> > cc:
> > Subject: dialer-watch config
> >
> >
> > Hi all,
> >
> > In the following example, there's a dialer map for the watched
route.
> See
> > http://www.cisco.com/warp/public/129/bri-backup-map-watch.html
> >
> >
> > Does this mean that for every route being watched, one dialer map
> statement
> > is
> > required?
> >
> > If so, that seems redundant, doesn't it? You have to create a
dialer
> > watch-list where each route to be watched is listed. And, then you
have
> to
> > create a dialer map statement for each watched route. Why is that?
> >
> > Thanks, dt
> >
> >
> >
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:58 GMT-3