From: Bill Dicks (wdicks@xxxxxxxxxxxxxxxxxx)
Date: Thu Aug 10 2000 - 12:54:17 GMT-3
Keith is right, I've had the exact same experience several months back when
doing ISDN and redistribution to OSPF on the same router (using ON demand
circuit). Whenever you do redistribution in the lab, ALWAYS use a
distribute list that only SPECIFICALLY permits the routes you want to get
redistributed. That way you won't get into tricky situations like
this...also, it's worth the time to specifically permit each route and use a
deny any at the end rather than deny certain routes from coming back in and
use a permit at the end. You just have more control that way.
Bill Dicks
CCIE # 6081
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Keith Kruepke
Sent: Thursday, August 10, 2000 8:32 AM
To: Bill Dellamar; ccielab@groupstudy.com
Subject: Re: ospf on demand-circuit
Bill,
It is definitely the redistribution between RIP and OSPF. When the ISDN
line hangs up, RIP stops generating it as a route. Then OSPF redistribution
notices that there is a change in the redistributed protocol, so it
generates an LSA to that effect. It brings up the line to send the LSA via
OSPF. Then RIP notices the line is back up, so it starts advertising and
redistributing that route again.
I think the best solution to this problem is to put a distribute list in
OSPF that blocks the redistribution of that one network. For example, if
your ISDN is 192.168.30.0/24, then create an access list that blocks that
network and permits all others. Then use that access list in a distribute
list under OSPF.
I hope this helps,
Keith
----- Original Message -----
From: "Bill Dellamar" <wdellamar@yahoo.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, August 10, 2000 7:36 AM
Subject: Re: ospf on demand-circuit
deb dialer shows that it is ospf that is bringing up
the link. "224.0.0.5".
I will post the config's tonight.
Thanks,
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:23 GMT-3