[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
BGP nexthop-self vs. EIGRP redistribution
- Subject: BGP nexthop-self vs. EIGRP redistribution
- From: mtinka at globaltransit.net (Mark Tinka)
- Date: Tue, 17 Mar 2009 00:28:42 +0800
- In-reply-to: <[email protected]>
- References: <[email protected]>
On Tuesday 17 March 2009 12:20:08 am phil at mindfury.net
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'
for all iBGP sessions at the (peering) edge, and using your
IGP to provide reachability to all Loopback addresses in the
network. This scales quite well.
And while IGP/BGP redistribution may be possible, we tend to
avoid it as much as possible.
Cheers,
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20090317/dd990bb1/attachment.bin>