From: Logan, Harold (loganh@mccfl.edu)
Date: Mon Jan 06 2003 - 11:03:22 GMT-3
Add to that an 'ip ospf cost' command, using a cost that's appropriate to the topology, ie higher than the primary links. In some cases, particularly with dialer profiles and multilink PPP, I've seen ospf treat the isdn circuit coming down as a change in cost, and when there's a change in cost, ospf sends out an update. If this is happening, you'll see it if you do some ospf debugging and use the isdn disconnect command. If LSA's go out immediately after you down the isdn circuit, your link could be flapping because ospf wants to inform everyone that the ISDN link is down, including the router on the other end of the demand circuit. Assigning a cost to the link should fix it.
> -----Original Message-----
> From: kym blair [mailto:kymblair@hotmail.com]
> Sent: Monday, January 06, 2003 6:13 AM
> To: fansh@publicf.bta.net.cn; ccielab@groupstudy.com
> Subject: Re: how to make ospf demand-circuit calm?
>
>
> Fan,
>
> Several suggestions:
>
> (1) add "no peer neighbor-route" to the bri or dialer
> interface on both
> routers
>
> (2) add "no cdp enable" to both
>
> (3) make "dialer idle-timeout 40" high enough (e.g. 40
> seconds) so ospf has
> time to converge before the line shuts down.
>
> (4) if you are doing redistribution on one of the routers,
> don't let the
> other routing protocol tell ospf about a "better" path to the
> isdn link.
>
> HTH, Kym
>
>
>
>
>
>
> >From: "Fan Shan" <fansh@publicf.bta.net.cn>
> >Reply-To: "Fan Shan" <fansh@publicf.bta.net.cn>
> >To: "Ccielab@Groupstudy.Com" <ccielab@groupstudy.com>
> >Subject: how to make ospf demand-circuit calm?
> >Date: Mon, 6 Jan 2003 18:40:24 +0800
> >
> >My ISDN on ospf demand-circuit is always up by multicast to
> 224.0.0.5, can
> >anyone tell me the correct config to calm it down?
> >.
> _________________________________________________________________
> MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*
> http://join.msn.com/?page=features/virus
> .
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:43 GMT-3