From: Gregory W. Posey Jr. (gposey@xxxxxxxx)
Date: Mon Nov 26 2001 - 13:05:47 GMT-3
Having OSPF denied in the dialer-list only stops OSPF from causing the link
to come up. Once the link comes up, any and all traffic will pass over the
link (OSPF, IPX, RIP, etc.) unless there is an access list applied to the
actual interface on one side of the link or the other.
Thank you,
Greg Posey Jr.
CCIE #7981
CCNP - Security Specialist
Cisco Voice Access Specialist
M.S. EE
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
kenairs
Sent: Monday, November 26, 2001 10:29 AM
To: Rivron Francois; Jobson, Eddie; ccielab@groupstudy.com
Subject: Re: Dialer watch question
Hi Francois,
Refering to the cisco link, i have some question.
The dialer-list states that "access-list 101 deny ospf any any ".
I know that this prevents ospf hellos from bringing up the isdn link.
But with this access-list, how can the ospf routes propagates to the other
router once the backup (isdn) link is used ?
Am i missing some thing ?
tks
----- Original Message -----
From: Rivron Francois <Francois.Rivron@ei-rsi.fr>
To: Jobson, Eddie <EJobson@thrupoint.net>; <ccielab@groupstudy.com>
Sent: Monday, November 26, 2001 8:42 PM
Subject: RE: Dialer watch question
> Eddie,
>
> Look at
> http://www.cisco.com/warp/public/129/bri-backup-map-watch.html
>
> There is a good explanation of dialer watch.
>
> About the loopback problem :
>
> r1---serial---r2
> | |
> +----BRI-----+
>
> r1
> interface lo0
> ip adresse 10.10.10.1 255.255.255.0
>
> r2
> int bri0
> dialer watch-group 1
>
> dialer watch-list 1 ip 10.10.10.1 255.255.255.255
>
> because
>
> r2#show ip route
> 10.0.0.0/32 is subnetted, 1 subnets
> O 10.10.10.1 [110/65] via ..... Serial0
>
>
> Whatever the subnet of network is on the int loopback, you have to set /32
> in the dialer watch if you monitor this network.
>
>
> Francois.
>
>
>
> > -----Message d'origine-----
> > De: Jobson, Eddie [SMTP:EJobson@thrupoint.net]
> > Date: lundi 26 novembre 2001 11:53
> > @: 'Rivron Francois '; Jobson, Eddie; ''ccielab@groupstudy.com' '
> > Objet: 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.
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:22 GMT-3