On 04/04/06, Claudio Jeker <[EMAIL PROTECTED]> wrote:

> On Mon, Apr 03, 2006 at 10:37:38PM +0100, tony sarendal wrote:
> > I'm playing a bit with bgpd while trying to get the kids to sleep, 50%
> to
> > go.
> > With Hennings next-hop self patch I made a minimal config and slapped
> > together
> > a network with a handful of routers with a config like below:
> >
> > AS 65000
> > network 172.16.0.1/32
> > network connected
> > network static
> >
> > group "ibgp" {
> >         remote-as 65000
> >         route-reflector
> >         set metric +100
> >         set nexthop self
> >         holdtime 10
> >         neighbor 172.16.1.2 {
> >                 local-address 172.16.1.1
> >         }
> >         neighbor 172.16.1.6 {
> >                 local-address 172.16.1.5
> >         }
> > }
> >
> > All routers are in the same AS with same config with exception of the
> > loopback /32 and the neighbors.
> > If I flap the links a bit I get fatal in RDE: attr_diff: equal
> attributes
> > encountered.
> >
> > Bug or expected behaviour ?
> >
> > It looks like the rde takes a dive when it receives an ibgp prefix it
> > already has from another ibgp peer,
> > nexthop, clusterlist should be different though, metric might be the
> same as
> > previous prefix.
> >
> > If I get the little guy to sleep before me I'll try to have a closer
> look.
> >
>
> Smells like a bug. The only thing I do not understand is why you use
> route-reflector. Form you descripton it seems like you are running a full
> mesh so route-reflector makes no sense.


I use a bgp setup where a router only peers with it's connected neighbors.
Route-reflecting or confeds needed to propagate the prefixes.



> Anyway I'll have a look at it today (if time permits)


Thanks Claudio.

/Tony

--
Tony Sarendal - [EMAIL PROTECTED]
IP/Unix
       -= The scorpion replied,
               "I couldn't help it, it's my nature" =-

Reply via email to