Setting next-hop-self on iBGP peerings

From: Martin Cooper (mjc@cooper.org.uk)
Date: Thu Nov 30 2000 - 16:47:18 EST


We are currently considering a move from carrying
all our internal prefixes in OSPF to using iBGP
to carry the edge prefixes, and just using OSPF
to carry the BGP next-hop.

The way I'm thinking of doing this is by redist'ing
connected and static routes into iBGP via a route-
map that sets community 'no-export' to make sure
we don't leak the more specific prefixes, but I
am looking for arguments for and against setting
next-hop-self on iBGP peerings - the most obvious
argument that I can see in favour is that of not
having to carry external next-hops around in the
IGP - but I am sure there must be a disadvantage
to not knowing what the external next-hop was,
although I am not sure what it might be.

Any assistance greatly appreciated,

M.



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:22 EDT