From: Troy Rader (troy@xxxxxxxxxx)
Date: Thu Feb 07 2002 - 16:38:06 GMT-3
Thanks for quick responses. The link below had the answer. This sure
resolved a great deal of "mysterious" ospf demand circuit issues for me.
If anyone knows of any gotchas with ospf demand circuits with
authentication, please chime in. I have enabled authentication and it
appears to be okay, but as is always the case, certain small variations
that I may not have now, may show up later when I try this again, causing
me heartache and grief.
Thanks.
On Thu, 7 Feb 2002, DAN DORTON wrote:
> FYI:
>
> This should prove to be a very usefull link.
>
> http://www.cisco.com/warp/public/104/dcprob.html
>
> It helped me quite a bit.
>
> Kudos to chuck church for that one!
>
> >>> Troy Rader <troy@onenet.net> 02/07/02 11:23AM >>>
> 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:15 GMT-3