Re: OSPF On-demand Circuit

From: kongck (kongck@xxxxxxxxx)
Date: Wed Jun 14 2000 - 22:48:12 GMT-3


   
I think u should not disable ospf traffic,use bigger cost on interface
BRI.plz give me a answer is u have done it.

----- Original Message -----
From: "David H. Brown" <DHBrown@PipeLine.com>
To: "'Randall Scheffer'" <rscheffe@allstar.com>; <ccielab@groupstudy.com>
Sent: Wednesday, June 14, 2000 11:26 PM
Subject: RE: OSPF On-demand Circuit

> Randall,
>
> I setup my dialer access-list:
> - access-list 103 deny ospf any host 224.0.0.5 log
> - access-list 103 permit ip any any
> which will make the local OSPF LSA traffic NOT bring up the line, but does
> not prevent the router from receiving the updates once the BRI line is up.
> The problem I am seeing now is that without a static route, the BRI does
not
> consider any traffic interesting (when Serial goes down) because it does
not
> know to route it through the BRI -- the OSPF table has not been built yet.
> Now, if I manually bring it up once and let it stay on, the DNA routes
> remain and it works perfectly. But, if power goes down and back up on
that
> router then it will NOT dial the BRI line because the DNA routes are gone.
> Is there a better solution than floating static?
>
> David
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Randall Scheffer
> Sent: Wednesday, June 14, 2000 9:43 AM
> To: 'David H. Brown'; ccielab@groupstudy.com
> Subject: RE: OSPF On-demand Circuit
>
>
> If you deny OSPF traffic, then you deny OSPF routes too. Just let ospf
> demand circuit do its work. Everything else remains the same.
>
> Randall
>
> -----Original Message-----
> From: David H. Brown [mailto:DHBrown@PipeLine.com]
> Sent: Monday, June 12, 2000 10:53 PM
> To: kmiho@lycos.ne.jp; ccielab@groupstudy.com
> Subject: RE: OSPF On-demand Circuit
>
>
> Kmiho,
>
> If your access-list is setup correctly to deny OSPF traffic, it should not
> come up until it is needed. I just restarted my 'backup' router to see if
> it would bring up the ISDN line, and it did not when it started. It
should
> not come up until the Serial line fails and interesting traffic tries to
> route.
>
> Hmmm, this is interesting: there are no DNA routes in the OSPF database
> after restarting (I suppose I could achieve the same result by 'clear ip
> route *'), and now the router does not know to route through the ISDN as a
> backup once the Serial line goes down. It works if I force it open once
by
> pinging the other side of the ISDN circuit because it gets the routes
then,
> but that's not a good practice in real life. What did I miss here?
Statics
> aren't allowed, how else can I fill that OSPF table?? Seems like having
it
> come up once when it starts would be a great idea! BTW, I am running
> 11.2(22a) and 11.2(12).
>
> David
> (RTP lab 6/15)
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> kmiho@lycos.ne.jp
> Sent: Sunday, June 11, 2000 6:28 AM
> To: ccielab@groupstudy.com
> Subject: OSPF On-demand Circuit
>
>
> Is it true that when you use the "ip ospf demand-circuit" command,
> the link will be brought up once even though the network topology is
> stable(or else the other side of the bri0 will not make it to OSPF
> database?). I do not have the isdn simulator to verify that but I do
> notice the following message appear even though the ethernet link
> between R1 and R2 is not broken.
>
> ********
> bri0: ip (s=R1's bri0, d=224.0.0.5), interesting(ip PERMIT)
> bri0: sending broadcast to ip (R2's bri0)
> ********
>
> Can somebody clarify this? Thanks in advance.
>
>
>
> --- R1(bri0)------------- isdn ------------(bri0)R2----
> (e0) (e0)



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:42 GMT-3