From: DAN DORTON (DHSTS68@xxxxxxxxxxxxxxx)
Date: Thu Feb 07 2002 - 15:02:32 GMT-3
In my experience both sides should keep the neighbor relationship up.
You notice on a demand circuit that it suppresses the hellos.
You should also notice that when you do a show ip ospf neighbors that
the neighbors across the BRI show no dead time, so the neighbor
relationship should never time out.
You should only need to put the demand circuit on one side (At least
this is in Cisco documentation.).
You should not need to take ospf traffic out of the dialer list as
interesting traffic, because the hellos should be surpressed in a
properly configured demand circuit.
The demand circuit will bounce when LSA changes happen in your network,
or /32 routes are present.
When using the ip ospf network poin-to-multipoint command this will
install /32 routes in your routing table. This can effect your demand
circuit. Use the no peer neighbor route command under your bri interface
to take care of this.
Other than that your problems could be caused by a redistribution
problem in another part of your network. If you are redistrbuting into
your ospf process somewhere in your network & the routes are bouncing
then LSA changes will happen frequently & cause your demand circuit to
bounce.
perform a debug ip ospf monitor at the router with your demand circuit
& it should show you which LSA changes are causing your demand circuit
to bounce. Then track them down & fix the issues.
Good luck demand circuits are a pain!
>>> Troy Rader <troy@onenet.net> 02/07/02 11:34AM >>>
I have a couple of questions.
1. With regard to an OSPF demand circuit, should the router on both
sides of
that circuit, retain the neighbor relationship, even after the isdn
line
goes back down? What I'm seeing is 1 side keeping the neighbor, but
the
other side only having that neighbor relationship when the isdn line is
up.
I have 'ip ospf demand' on the bri interfaces on both sides. Which
brings
up another point. I also MUST modify the dialer list to deny ospf or
the
isdn is brought up by OSPF. Under what conditions does everyone see
'ip
ospf demand' NOT work, and then requiring the dialer-list to do what
'ospf
demand' should do, but also having then other bad side affects, like
link
state changes not bringing up the circuit? Is this a config issue, IOS
bug,
etc?
2. I haven't gotten past #1, but wanted to go ahead and ask if anyone
can
elaborate on any known issues. Once I have this ospf demand circuit
working like I think it should, I want to authenticate it. Any issues
with
doing this that anyone can explain?
Thanks in advance.
Troy
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:14 GMT-3