Configures the next hop address used in the updates to be the address of the BGP (Border Gateway Protocol) connection originating the update.
| peer-group-name | Specifies a peer group. |
| 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. |
| 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 (Let the BGP protocol decide 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.
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
If the specified peer group contains IPv6 peers, it is an IPv6 peer group and you must specify an IPv6 address-family. When the specified peer group is an IPv6 peer group, this command fails if no address family is specified or if an IPv4 address-family is specified. This command also fails if an IPv6 address family is specified for an IPv4 peer-group.
To configure this feature on Layer 3 VPNs, you must configure this feature in the context of the MPLS (Multiprotocol Label Switching)-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 peer-group outer next-hop-self
This command was first available in ExtremeXOS 10.1.
This command required a specific license in ExtremeXOS 11.1.
Support for IPv6 was added in ExtremeXOS 12.6 BGP.
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 22.6 Feature License Requirements document.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB