When establishing eBGP peering between devices that are not directly connected, the TTL (Time To Live) value of the BGP packets must be increased to allow them to traverse multiple hops. This is achieved by configuring ebgp-multihop, which increases the TTL beyond the default value of 1.
next-hop-self changes the BGP next-hop attribute but is not required for multihop eBGP.
route-reflector is a BGP design feature unrelated to multihop.
address-family ipv4 external is not a standard command on Aruba CX switches.
Therefore, to successfully peer eBGP sessions across multiple hops, ebgp-multihop must be configured.
[References:, , ArubaOS-CX BGP Configuration Guide, , RFC 4271 (BGP-4), , HPE Aruba Networking Best Practices for BGP]
Submit