From: BRZYSKI, ADAM E (SWBT) (ab1723@xxxxxxx)
Date: Tue Sep 04 2001 - 18:22:18 GMT-3
What you area doing kind of works as you described below. However your
approach negates the purpose of a ip OSPF demand circuit. Note that the
demand circuit suppresses hellos and LSA as long as there are no topology
changes. Once a change happens the change is send over the demand circuit.
I am assuming that you are redistributing to a different routing protocol
somewhere within your topology. If this is true what you are really dealing
with is a routing loop. If you do show ip OSPF database you will probably
see the ISDN IP network in the type-5 LSA table. What is happening is that
you are redistributing to another routing protocol and that protocol is in
turn redistributing the information back to OSPF. This is what causes the
demand circuit to go up and down. Use a route map or a distribute list to
filter the other routing protocol from advertising the ISDN IP network back
to OSPF. Once you do that you'll notice that the ISDN will stay down. The
best way to verify your filtering is to make sure that the ISDN IP network
does not appear in the OPSF database under type-5 LSA's. Hope this helps!
Adam Brzyski
Design Engineer II
CCIE #8082, NNCDE
-----Original Message-----
From: John Elias [mailto:jelias_@hotmail.com]
Sent: Tuesday, September 04, 2001 3:35 PM
To: ccielab@groupstudy.com
Subject: ip ospf deamd-circuit
Guys,
I know this question was asked before, but I need a definit answer. The
ip ospf demand-circuit command when running it over bri interfaces, does not
work for me. It seems that I need to filter out ospf multicasts so that the
line does not come up again. The only problem is that when the serial goes
down, the bri interface does not come up. I have to ping the other side to
get the bri interface to come up. Can someone please post a config that
might work.
John
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:14 GMT-3