[129548] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: eBGP Multihop

daemon@ATHENA.MIT.EDU (Truman Boyes)
Fri Sep 10 01:07:10 2010

From: Truman Boyes <truman@suspicious.org>
In-Reply-To: <4C7F6E9A.6070203@apolix.co.za>
Date: Fri, 10 Sep 2010 13:06:51 +0800
To: Graham Beneke <graham@apolix.co.za>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On 2 Sep 2010, at 5:30 PM, Graham Beneke wrote:

> I have been asked to investigate moving an entire network to multi-hop =
on all the eBGP sessions. Basically all upstreams, downstreams and peers =
will eBGP with a route reflector located in the core. This RR will be =
some kind of quagga or similar box. The dev guys want to be able to poke =
at the BGP feeds directly and do *magic* that standard router aren't =
capable of.
>=20
> My gut feel is that this is a bad idea. Besides anything else it makes =
sane link state detection very challenging - especially where we have =
multiple sessions with a peer.
>=20
> Is their any BCP or operational experience that agrees or disagrees =
with my gut. ;-)
>=20
> --=20
> Graham Beneke

Even in lab environments I would say that eBGP multihop is a bad idea. =
Production networks that try to make money should not embark on such a =
mission. Trust your gut :)

If some box wants to take a feed of routes, it should just iBGP peer =
with your RRs.=20

Truman


home help back first fref pref prev next nref lref last post