From: steven.j.nelson@xxxxxx
Date: Sun May 12 2002 - 12:40:18 GMT-3
just deny ospf
access-list 101 deny ospf any any
access-list 101 permit ip any any
Steve
-----Original Message-----
From: Curtis Phillips [mailto:cphillips@suscom.net]
Sent: 11 May 2002 22:25
To: ying chang; Nelson,SJ,Steven,IVNH25 C; ccielab
Subject: Re: Justification for use of Dialer-watch in OSPF
Ying, Steve,
How about the non-dialer-watch side of the connection?
Curtis
----- Original Message -----
From: "ying chang" <ying_c@hotmail.com>
To: <cphillips@suscom.net>; <steven.j.nelson@bt.com>;
<ccielab@groupstudy.com>
Sent: Saturday, May 11, 2002 4:21 PM
Subject: Re: Justification for use of Dialer-watch in OSPF
> Curtis,
>
> I have to agree with Steve. When I did dialer-watch a week or two ago, I
> could take dialer-group out and the dialer-watch would work without any
> problems. What triggers dialer-watch to dial is a watched missing route,
it
> has nothing to do with the interesting traffic specified in the
> dialer-group. After the line come up, it will check if the primary line
come
> backup every idle-timeout seconds, the line would stay up as long as the
> route is missing.
>
> Chang
>
>
> >From: "Curtis Phillips" <cphillips@suscom.net>
> >Reply-To: "Curtis Phillips" <cphillips@suscom.net>
> >To: <steven.j.nelson@bt.com>, <ccielab@groupstudy.com>
> >Subject: Re: Justification for use of Dialer-watch in OSPF
> >Date: Sat, 11 May 2002 15:41:39 -0400
> >
> >Steve,
> >
> >I think you will find that demand-circuit is still required if
dialer-watch
> >is used with OSPF.
> >Set it up and you will see that the OSPF will keep the ISDN up.
> >
> >Curtis
> >----- Original Message -----
> >From: <steven.j.nelson@bt.com>
> >To: <cphillips@suscom.net>; <ccielab@groupstudy.com>
> >Sent: Saturday, May 11, 2002 11:53 AM
> >Subject: RE: Justification for use of Dialer-watch in OSPF
> >
> >
> > > Curtis
> > >
> > > Think you may have answered your own question here except for one
small
> > > point.
> > >
> > > Dialer Watch and OSPF Demand circuit are not and were never meant to
> >work
> >in
> > > conjunction with each other, they are two separate technologies that
> >allow
> > > demand (Dialer, X.25, atm and frame svc etc etc) circuits to keep
quiet
> > > unless a specific condition is met.
> > >
> > > In the case of ospf demand circuit the trigger is a change in topology
> >etc
> > > etc
> > >
> > > In the case of Dialer Watch when a watched route dissapears from the
> >routing
> > > table
> > >
> > > Don't confuse the two and use them as they are meant separately...
> > >
> > > HTH, ant more questions mail me off line...
> > >
> > > All the best
> > >
> > > Steve
> > >
> > > -----Original Message-----
> > > From: Curtis Phillips [mailto:cphillips@suscom.net]
> > > Sent: 11 May 2002 16:29
> > > To: ccielab
> > > Subject: Justification for use of Dialer-watch in OSPF
> > >
> > >
> > > Hello All,
> > >
> > > I was thinking about the use of Dialer-watch with OSPF over ISDN. I
know
> > > that
> > > demand-circuits are used in conjunction with dialer-watch in the same
> >manner
> > > as protocol packets are filtered by dialer-lists fro EIGRP or IGRP.
> > >
> > > Demand interfaces allow the dialer to bypass keep-alives and to dial
> >only
> > > when there is a change (addition or deletion) of LSA in the OSPF
> >database.
> > >
> > > It seems to me that demand circuits would adequately cover the
> >suppression
> > > of
> > > dial related to anything other than a change in database LSAs. So, I
> >wonder
> > > what the perceived benefit is of using dialer-watch with OSPF. Unless
it
> >is
> > > to
> > > track routes that are not in the OSPF process.
> > >
> > > Any thoughts?
> > >
> > > Thanks,
> > >
> > > Curtis
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:55 GMT-3