NEXT_HOP Reachability
Option 3 - Do “neighbor x.x.x.x next-hop-self” on the iBGP sessions from R1 and R2 to R3
Adds 0 routes to the IGP
Adds 0 routes to BGP
Promotes IGP/BGP stability by leaving customer links out of the picture
BGP will have an IGP route to BGP NEXT_HOPs. Route churn due to illegal recursive lookups is no longer an issue
NEXT_HOPs accessed via a single recursive lookup which makes troubleshooting easier
Note: “next-hop-self” to a route-reflector-client will not modify the NEXT_HOP of a reflected route. Routes advertised from an eBGP peer to a RRC will be modified