From: Guy Farber (gfarber@xxxxxxxxx)
Date: Mon Jun 04 2001 - 10:29:10 GMT-3
No I'm talking about a situation where ospf is running on the bri line, but
the rip or igrp is running on the bri interface too since you can't define a
network mask for them.
For example:
BRI 0/0 172.16.1.1 /24
E 0/0 172.16.2.1 /24
router ospf 1
net 172.16.1.1 0.0.0.0 area 0
router rip
net 172.16.0.0
You don't want rip to run on the bri but it gets it anyway...
Doing a route-map on the redistribution into ospf is the only way I see to
solve this.
-----Original Message-----
From: Tomasz Bartel [mailto:tbartel@rubikon.pl]
Sent: Mon, June 04, 2001 2:19 PM
To: Guy Farber; Hugo Steiner; Brian; ccielab@groupstudy.com
Subject: RE: OSPF Demand Circuit & Point to Point
What about snapshot-routing under rip and igrp? Should help.
Tomek
At 14:34 01-06-04 +0200, Guy Farber wrote:
>Even better, if you are redistributing rip or igrp on the dialing router
and
>rip or igrp runs on the bri interface (passive interface won't help you) -
>it will redistribute a new route into ospf which will bring up the ospf
>demand-circuit.
>
>The result is pretty amusing - whenever the line goes down it gets back up
>because it sends a new type 5 lsa about the change in the state of the bri
>link...
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
>Hugo Steiner
>Sent: Mon, June 04, 2001 8:45 AM
>To: Brian; ccielab@groupstudy.com
>Subject: Re: OSPF Demand Circuit & Point to Point
>
>
>Brian,
>
>packets to 224.0.0.5 will still bring the link up when they are sent,
>
>an OSPF Demand circuit surpresses LSA's that have already been sent, you
>will probably find that the traffic getting through is a new or updated
>LSA that hasn't been sent before.
>
>One cause of this might be that you are using Dialer profiles, which
>insert a host route into the routing table when the link comes up or
>goes down, these then get redistributed into OSPF, and sent over the
>serial link, they arrive at the other end of the link and the router
>goes, oh, new LSA, better bring the dialer up to send it.
>
>It's a vicious cycle.
>
>Filter and summarise so as these host routes don't get into OSPF. But
>the summary for the whole network is avalible.
>
>R
>Hugo
>--
>Hugo Steiner P: +61 2 4969 0176 The light at the end of the
>HunterLink Pty Limited F: +61 2 4969 0133 tunnel could be a dragon
>
>----- Original Message -----
>From: "Brian" <signal@shreve.net>
>To: <ccielab@groupstudy.com>
>Sent: Monday, June 04, 2001 4:05 PM
>Subject: OSPF Demand Circuit & Point to Point
>
>
> > I am working on a scenerio where a BRI line
> > is backing up a serial connection. The BRI
> > is set as an "ip ospf demand", yet I find
> > that packets to 224.0.0.5 are bringing the
> > link up still. If I set the network type
> > on the BRI lines to "ip ospf network non-broadcast"
> > then all is well, but if I leave it as the default
> > for a BRI, which is point-to-point, it will
> > keep getting brought up by traffic to 224.0.0.5.
> >
> > Does anyone have any insight to share? I have
> > seen plenty of demand circuit examples where it
> > just uses network type of point-to-point.
> >
> > Brian
> >
> >
> > -----------------------------------------------
> > Brian Feeny e:signal@shreve.net
> > CCNP+Voice/ATM/Security p:318.222.2638x109
> > CCDP f:318.221.6612
> > Network Administrator
> > ShreveNet Inc. (ASN 11881)
> > **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
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:17 GMT-3