From: Brian Hescock (bhescock@xxxxxxxxx)
Date: Mon Feb 05 2001 - 00:34:13 GMT-3
Mark,
I believe Kevin was referring to ospf in general, not with demand
circuit. I would agree though that with demand circuit it should keep
the circuit down since you have the route in routing table with DNA
set and dialer-watch would never cause isdn to dial (given this particular
situation). Good point though.
B.
On Sun, 4 Feb 2001, Mark Stover wrote:
> Not sure if you've got a weird version of IOS or a misconfiguration, but you
should be able to get dialer watch and OSPF demand-circuits working at the same
time. You may get a connection when the watched route first goes down, but the
n it should drop again unless there is some other interesting traffic.
>
> Mark
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Kevin Baumgartner
> > Sent: Sunday, February 04, 2001 9:30 PM
> > To: bhescock@cisco.com
> > Cc: ccielab@groupstudy.com
> > Subject: Re: watch-group observation
> >
> >
> > Sort of the same thing that I found when doing OSPF with dialer
> > watch-group. After the dialer idle timeout expired the ISDN line
> > would drop and then get redialed by dialer watch.
> >
> > I guess the idle-timeout could be set higher, but the dialer watch
> > feature doesn't seem to trigger a drop of the isdn line even if the
> > watch route comes back. So could incure a high isdn line cost until
> > it finally times out.
> >
> > Kevin
> >
> > >
> > > This looks like normal behavior but, in my opinion, is broken:
> > >
> > > - dialer watch-group configured for network 30.1.1.0, which
> > is learned via
> > > ethernet 0
> > > - shut down ethernet 0 interface, lose route for 30.1.1.0
> > and isdn comes
> > > up due to no route for 30.1.1.0
> > > - eigrp forms neighbors over isdn and we get route for 30.1.1.0
> > > - isdn drops after 120 seconds, the default idle-timeout
> > > - isdn redials immediately since it has no route for 30.1.1.0
> > >
> > > Personally, I think IOS should be smart enough to know it
> > only knows the
> > > route through isdn so it should keep the line up if it
> > doesn't know of a
> > > route for 30.1.1.0 via some other interface. It's a waste
> > of money to
> > > increase the idle-timeout so this doesn't happen as often
> > because then
> > > isdn will always stay up longer.
> > >
> > > Anyone know of a way around this problem other than increasing the
> > > idle-timeout? Looks like I may need to file a sys-wish bug
> > to get IOS
> > > changed so it doesn't drop the isdn link if the route is
> > only known via
> > > isdn. Perhaps it's just me but I think is silly that we
> > drop the link,
> > > only to bring it up again.
> > >
> > > Brian
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:36 GMT-3