Hi
For the MPLS L3VPN the answer is that the next hop attribute needs to be
an address from the default VRF and if the peering is happening in a VRF
context, there is no address from the default VRF you could use as next
hop other than self.
This can be rather inconvenient as there are advantages to have the real
next hop. For example fast rerouting works better when all defective
routes can be removed in one go because the next hop was removed by the
IGP instantly invalidating the affected routes.
Regards,
Baldur
Den 01/12/2017 kl. 16.06 skrev craig washington:
Hello everyone,
Question, what are the true benefits to using the next-hop self feature,
doesn't matter what vendor.
Most information I see is just to make sure you have reach-ability for external
routes via IBGP, but what if all your IBGP knows the eBGP links?
Is there a added benefit to using next hop self in this situation?
Any feedback is much appreciated, either for the question specifically or
whatever else you got 😊, L3VPN's or underlying technology that has to have that.
Thanks
