[j-nsp] BGP Policy - then accept == Route Reflector?

[Keegan Holley]

On Fri, Nov 12, 2010 at 5:07 AM, Sebastian Wiesinger <
juniper-nsp at ml.karotte.org> wrote:

> * Richard A Steenbergen <ras at e-gerbil.net> [2010-11-11 18:12]:
> > > But there is a gotcha there: Cisco WILL NOT send iBGP routes learned
> > > from other iBGP peers when I configure such a policy. An MX960 on the
> > > other hand WILL happly start to act like a route reflector and pass on
> > > all the other iBGP routes that match the AS-Path.
> >
> > No router will send IBGP learned routes to another IBGP peer unless
> > configured to be a route-reflector.
>
> Hello,
>
> the MX960 with 9.6R2.11 did that. I was quite surprised as I was
> expecting the behaviour you describe.
>

Did this happen on a production router?  iBGP peers don't update routes to
show that they have seen them already so this would have resulted in an
instant routing loop.  Assuming nothing is redistributed into the IGP the
effects would have been noticeable. Can you provide more information has to
the topology and the kinds of routes you are talking about?


> > Use "from route-type external" in your policy to match only the EBGP
> > learned routes.
>
> Thanks I'll use that.
>
> Kind Regards,
>
> Sebastian
>
> --
> New GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A  9D82 58A2 D94A 93A0
> B9CE)
> Old GPG Key-ID: 0x76B79F20 (0x1B6034F476B79F20)
> 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE
> SCYTHE.
>            -- Terry Pratchett, The Fifth Elephant
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
>