Configures the next hop address used in the outgoing updates to be the address of the BGP connection originating the update.
| remoteaddr | Specifies an IP address. |
| all | Specifies all neighbors. |
| ipv4-unicast | Specifies the IPv4 unicast address family. |
| ipv4-multicast | Specifies an IPv4 multicast address family. |
| ipv6-unicast | Specifies the IPv6 unicast address family. |
| ipv6-multicast | Specifies an IPv6 multicast address family. |
| vpnv4 | Specifies the VPNv4 address family for Layer 3 VPN support. This address family is applicable for PE to PE BGP neighbor sessions only. This keyword may prompt warning or error messages if executed for a regular BGP neighbor session, or for a PE to CE neighbor session. |
| next-hop-self | Specifies that the next hop address used in the updates be the address of the BGP connection originating it. |
| no-next-hop-self | Specifies that the next hop address used in the updates not be the address of the BGP connection originating it (lets BGP decide what would be the next hop). |
If no address family is specified, IPv4 unicast is the default.
This command applies to the current VR or VRF context. These settings apply to the peer group and all neighbors of the peer group.
Note
The BGP neighbor must be disabled before you can change the configuration with this command.
If you do not specify an address family, this command applies to the IPv4 unicast address family. To apply this command to an address family other than the IPv4 unicast address family, you must specify the address family.
Note
For an IPv6 peer, an IPv6 address family must be specified, because an IPv6 peer does not support IPv4 address families. If no address family is specified for an IPv6 peer, the default, the IPv4 unicast address family, applies and the command fails. Similarly an IPv4 peer only supports IPv4 address families and the command fails if an IPv6 address family is specified.
To configure this feature on Layer 3 VPNs, you must configure this feature in the context of the MPLS-enabled VR; this feature is not supported for BGP neighbors on the CE (VRF) side of the PE router.
The following command configures the next hop address used in the updates to be the address of the BGP connection originating it:
configure bgp neighbor 172.16.5.25 next-hop-self
This command was first available in ExtremeXOS 10.1.
This command required a specific license in ExtremeXOS 11.1.
Support for Layer 3 VPNs was added in ExtremeXOS 15.3.
This command is available on platforms that support the appropriate license. For complete information about software licensing, including how to obtain and upgrade your license and which licenses support the BGP feature, see the ExtremeXOS and Switch Engine 31.7 Feature License Requirements document.