From: Mas Kato (tealp729@xxxxxxxx)
Date: Sat May 26 2001 - 16:07:48 GMT-3
<OSPF demand circuit must be loaded on every router in the area>
I believe what that really means is that OSPF demand-circuits must be
supported by every implementation of OSPF in the area (must understand
the DNA LSA flag).
Demand-circuits supposedly only need to be configured on one side of
each link, since it's supposed to be negotiated as the adjacency
forms--I've had good luck with this, but the archives seem to indicate
your mileage will vary. Check to make sure it's been negotiated with 'sh
ip ospf neigh.'
224.0.0.5 is actually the AllSPFRouters multicast group--making it
uninteresting as the lab requires would prevent OSPF traffic from
initiating calls and reseting the idle-timeout. Depending on the
sequence of events, some other interesting traffic might have to
initiate the call in order for the adjacency to initially form and
negotiate the demand-circuit. But after the adjacency forms and a
topology change occurs, if the link is down, some interesting traffic
better come along or the adjacency will ultimately be torn down.
Without the access-list, the demand circuit should quiet down after the
databases sync. If it doesn't, it's probably because a topology change
is occurring somewhere...
Mas
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Don Dettmore
Sent: Saturday, May 26, 2001 5:09 AM
To: CCIE Lab List; Luke M
Subject: Re: Question on Lab 17, ISDN Portion
I had the same problem some time ago.
One thing I remember - the CCO doc states the OSPF demand circuit must
be
loaded on every router in the area. IT's not clear what they mean by
that,
but if I remember correctly I believe that fixed the problem.
Don Dettmore
----- Original Message -----
From: "Luke M" <luke.mendoza@home.com>
To: "Ccie (E-mail)" <ccielab@groupstudy.com>
Sent: Saturday, May 26, 2001 12:06 AM
Subject: Question on Lab 17, ISDN Portion
> Hello Guys,
>
> ISDN won't stay down even if I put "IP OSPF DEMAND-CIRCUIT" on one end
of
> the link. I checked out the Bootcamp anwer and they have it so that
R5
and
> R6 have the command on both BRI interfaces.
>
> I was also confused with the dialer-list on R5 which shows to deny
> 224.0.0.5. Here is a portion of the config.
>
>
> access-list 100 deny ip any host 224.0.0.5
> access-list 100 permit ip any any
>
> dialer-list 1 protocol ip list 100
>
>
> Which would make sense since R5 is the one who keeps dialing up to R6.
I
> believe the multicast address 224.0.0.5 is for OSPF DRs? I thought
this
was
> not needed since I have the demand-circuit command.
>
>
> I would appreciate any help or suggestions...
>
> kinda tired as I have been studying for about 10 hours... I'm sure I
am
> missing something simple.
>
> Luke
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:54 GMT-3