From: @ Home NetMail (@)
Date: Mon Nov 26 2001 - 14:41:08 GMT-3
RE: Dialer watch questionBelow is a working example, with #'s changed to
protect the innocent.
In this routers table there are 2 load balancing routes to redundant
routers over theWAN:
D 10.199.8.0/21
[90/20514560] via 10.199.1.41, 5d14h, Serial1/0:0.211
[90/20514560] via 10.199.1.43, 5w1d, Serial1/0:0.311
Both routes go away the ISDN will dial and use 2 B channels if needed.
HTH,
-Todd
interface BRI0/0
description Backup frame via dialer-watch
ip address 10.250.1.1 255.255.255.252
no ip directed-broadcast
encapsulation ppp
dialer idle-timeout 300
dialer watch-disable 15
dialer map ip 10.250.1.2 name theWAN broadcast 15555551234
dialer map ip 10.199.8.0 name theWAN broadcast 15555551234
dialer map ip 10.250.1.2 name theWAN broadcast 15555551235
dialer map ip 10.199.8.0 name theWAN broadcast 15555551235
dialer load-threshold 10 either
dialer watch-group 1
dialer-group 1
isdn switch-type basic-ni
isdn spid1 33333312340101 3331234
isdn spid2 33333312350101 3331235
no fair-queue
no cdp enable
ppp authentication chap
ppp multilink
!
!
access-list 100 deny eigrp any any
access-list 100 permit ip any any
dialer watch-list 1 ip 10.199.8.0 255.255.248.0
dialer-list 1 protocol ip list 100
----- Original Message -----
From: Jobson, Eddie
To: 'Todd Veillette '
Sent: Monday, November 26, 2001 7:57 AM
Subject: RE: Dialer watch question
So does that mean you need an extra dialer map as well as the normal one
pointing at the remote ISDN address? Sorry for so many question on this but I
don't have access to ISDN at the moment to test it.
Eddie.
-----Original Message-----
From: Todd Veillette
To: Jobson, Eddie
Sent: 26/11/01 08:05
Subject: Re: Dialer watch question
Hi Eddie,
The best way set the network is to actually get the route in the table
on
the
router. So whatever you want to watch, has to be exact per the table,
just
get it up and look at the route and mask; set it to your dialer
watch-list,
and dialer map (no mask is needed but it must be the same). You must
also
put a dialer map for the other end bri ip. If you want to use multilink
you
would have 4 map statements for 2 spids.
HTH,
-Todd
----- Original Message -----
From: "Jobson, Eddie" <EJobson@thrupoint.net>
To: "'Rivron Francois '" <Francois.Rivron@ei-rsi.fr>; "Jobson, Eddie"
<EJobson@thrupoint.net>; <ccielab@groupstudy.com>
Sent: Monday, November 26, 2001 5:53 AM
Subject: RE: Dialer watch question
> Thanks Francois.
>
> If the ip ospf network point-to-point was used the /32 loopback is
then
> advertised as a /24 or whatever, but would you still use the specific
> interface address? The one used in the dialer map is usually the
remote
ISDN
> and wouldn't be used as a dialer watch, it would usually be a local
LAN/WAN
> that the ISDN was monitoring and backing up.
>
> Eddie.
>
>
> -----Original Message-----
> From: Rivron Francois
> To: Jobson, Eddie; 'ccielab@groupstudy.com'
> Sent: 26/11/01 05:24
> Subject: RE: Dialer watch question
>
> Hello,
>
> The <network> statement in "dialer map " and "dialer watch-list"
command
>
> have to be the same.
>
> The <network > entry is the one looked up in the routing
> table...so
> if you monitor network 10.10.10.0 you have to use "dialer watch-list 1
> ip
> 10.10.10.1 255.255.255.0"
>
> Aware with the int loopback and OSPF,cause OSPF use a /32 mask
> to
> describe a stub network , so the specific address of the int loopback
> need
> to be used in "dialer watch-list".
>
> Francois.
>
>
> > -----Message d'origine-----
> > De: Jobson, Eddie [SMTP:EJobson@thrupoint.net]
> > Date: lundi 26 novembre 2001 11:03
> > @: 'ccielab@groupstudy.com'
> > Objet: Dialer watch question
> >
> > If dialer watch is used to monitor an interface does the specific
> > interface
> > IP address have to be used including the subnet mask for the network
> it
> > sits
> > on, or is it better to use the whole network range, or can either be
> used.
> >
> > dialer watch-list 1 ip 10.10.10.0 255.255.255.0
> > OR
> > dialer watch-list 1 ip 10.10.10.1 255.255.255.0
> >
> > Thanks,
> >
> > Eddie.Note: The information contained in this message may be
> privileged
> > and
> > confidential and protected from disclosure. If the reader of this
> message
> > is not the intended recipient, or an employee or agent responsible
for
> > delivering this message to the intended recipient, you are hereby
> notified
> > that any dissemination, distribution or copying of this
communication
> is
> > strictly prohibited. If you have received this communication in
> error,
> > please notify us immediately by replying to the message and deleting
> it
> > from
> > your computer. Thank you. ThruPoint, Inc.
> Note: The information contained in this message may be privileged and
> confidential and protected from disclosure. If the reader of this
message
> is not the intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby
notified
> that any dissemination, distribution or copying of this communication
is
> strictly prohibited. If you have received this communication in
error,
> please notify us immediately by replying to the message and deleting
it
from
> your computer. Thank you. ThruPoint, Inc.
Note: The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this message is
not the intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please notify
us immediately by replying to the message and deleting it from your computer.
Thank you. ThruPoint, Inc.
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:23 GMT-3