Hi all.
I was working on a lab with an ISDN link between two of my OSPF routers. The
link would come up if the Frame cloud went away. Normal stuff link would be
initiated as usual. However, since area 0 had authentication turned on
broadcasts from 224.0.0.5 kept the isdn link up all the time. If I
I waited for an expert to answer, but none did. But sometimes seeing that
I'm intrigued (and/or confused), smokes them out of their holes. ;-)
It doesn't make sense that turning on MD5 authentication with OSPF would
cause the demand-circuit to stay up. MD5 doesn't send the key over the
wire. I
You mentioned restricting demand circuit to stubby, totally stubby, and
NSSA areas and I had never really thought about that. A quick search on
CCO turned this up:
Implementation Considerations
Evaluate the following considerations before implementing this
feature:
Because LSAs that include
As far as I can tell from my reading, if you want to avoid periodic
30-minute refresh LSAs passing over the demand circuit, every router in the
network (not just the area!) needs to understand OSPF demand circuits, per
RFC 1793. They don't have to be configured to be demand circuits, but they
Wouldn't surprise me at all that this is a bug. What IOS are you using?
Have you checked out the bug navigator? I just had a quick pass through,
but seeing as instead of actually searching for my keywords, the tool
ignores them and provides 500-1500 additional bugs to be "helpful", I was
una
Thanks for all the replies. No clear answer yet. I do know for a fact due to
debugs that there is a periodic key exchange sequence. The debug would show
as OSPF: Send with youngest Key 1. The traffic would come across as
224.0.0.5. The only difference between the demand-circuit peers staying up
or
Are you using the simple password authentication or the MD5 authentication?
I realized that I assumed MD5 in my previous answer.
At 02:20 PM 2/1/02, Richard Newman wrote:
>Thanks for all the replies. No clear answer yet. I do know for a fact due to
>debugs that there is a periodic key exchange s
I'm not discounting a bug. I have submitted a question to the open forum on
cco, no responses yet. I know that my config is correct as the ospf
neighbors form soon after the isdn link is activated (ie. the keys do match
on both sides). The neighbors will stay up, however, the isdn link also
stays
8 matches
Mail list logo
