[112737] in North American Network Operators' Group
Re: BGP nexthop-self vs. EIGRP redistribution
daemon@ATHENA.MIT.EDU (Mark Tinka)
Mon Mar 16 12:29:18 2009
From: Mark Tinka <mtinka@globaltransit.net>
To: nanog@nanog.org
Date: Tue, 17 Mar 2009 00:28:42 +0800
In-Reply-To: <058c1d303220336a06f94c4e8b837847@mindfury.net>
Cc: phil@mindfury.net
Reply-To: mtinka@globaltransit.net
Errors-To: nanog-bounces@nanog.org
--nextPart1338851.CqluEJqkhc
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Tuesday 17 March 2009 12:20:08 am phil@mindfury.net=20
wrote:
> My question is, which is the correct method of
> implementing this? Should we be redistributing static
> and connected routes on our borders into IGP, and not
> using next-hop-self? Or should we not redistribute and
> use next-hop-self?
I always recommend setting the NEXT_HOP attribute to 'self'=20
for all iBGP sessions at the (peering) edge, and using your=20
IGP to provide reachability to all Loopback addresses in the=20
network. This scales quite well.
And while IGP/BGP redistribution may be possible, we tend to=20
avoid it as much as possible.
Cheers,
Mark.
--nextPart1338851.CqluEJqkhc
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iQIcBAABAgAGBQJJvn4/AAoJEGcZuYTeKm+GL3YP/iwVI4WjmTkFOxi6w1ka644d
ahJ5L4+2+8ln78uR4k1iP/mMbR18m+B9mtGo4fpk24zdx55iOjgDsOf+SvvfG5XT
aFTHB3KUj8XEzVb0/tHO/LOn/dMiZYlSRE9Iq6QlsoLK+rLx/AzO1yZ7ADZKycdp
0Fyx4i8G7yqI46dK9oidHgf5YXlVSpLpHtCyJ8zKpGIaXSl5nAROrr6jfzTMTabD
GIajfZL3OkHnae/hSgWptOExksTHmXf7pq7cSmxt1z++6Pmw+RnNmcdv4DtlNPev
x+OwPZovE1z05d6WWuWN1aU5eRjb+VirjFcFFGsHh8t7z4i/V1Sl6McA9gc0TV9Q
kQ1TTAQcolgpv8Kd40esLTIeRzw2iYRfe4/r3sH2MWXrlYOMzfanbEK1Fvh/rfHz
Vd2SoVjjv6/sT6+ryKMBVZU/rXEqLCvaTIo6KfY3AL3DyRr5IRV15upsoRL4o17N
XSiFw16Qu3R+oH2mu224701WqFKZ8Sozv/xpxuThPEeZ19BJAeTliyedPYR4/dRm
I+vr8LMb1gwMs3Bzps2Tys9ibLJQcdszSrgb7VDtzDy6ZwsgPyMFeLee3L9ykDUt
SJOhXJWd7cU2AoedWfQWDju0BvqT7ldIAcWn3ZYH4/3F6sa8k1AvJi0DJblwWKHr
nsXFTQ7gPT1GjE7HYhVe
=vftO
-----END PGP SIGNATURE-----
--nextPart1338851.CqluEJqkhc--
