This command enables multi protocol BGP (Border Gateway Protocol) (MBGP) and route-refresh capabilities for one or all BGP neighbors.
| all | Specifies that the configuration applies to all neighbors in the specified address family. If no address family is specified or if an IPv4 address is specified, the configuration applies to all IPv4 neighbors. If an IPv6 address family is specified, the configuration applies to all IPv6 neighbors. |
| remoteaddr | Specifies the IPv4 or IPv6 address of a BGP neighbor. The switch uses the IP address format to determine if the address is an IPv4 or IPv6 address. |
| 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 VPN ipv4 unicast address family for a BGP neighbor. This is a required configuration for PE to PE BGP neighbor session. You must configure it before you enable a neighbor. |
| route-refresh | Specifies ROUTE-REFRESH message capabilities. |
| ipv4-vxlan | Specifies IPv4 VXLAN capability. |
The following capabilities are enabled by default for IPv4 peers: IPv4 unicast, IPv4 multicast, and route refresh.
The following capabilities are enabled by default for IPv6 peers: route refresh.
Note
For IPv4 peers, the IPv4 unicast and IPv4 multicast capabilities are enabled by default to support legacy peers that do not support MBGP. All other capabilities (except route-refresh) are disabled by default.When you change the capability configuration, you must enable the BGP neighbor before the configuration becomes active. If the BGP neighbor was enabled before the change, you must disable and enable the BGP neighbor. After the capabilities have been enabled, the BGP neighbor announces its capabilities to neighbors in an OPEN message.
When one or more address families are enabled, routes from the specified address families are updated, accepted, and installed. If more than one address family capability is enabled,or if the VPNv4 address family is enabled,the MBGP extension is automatically enabled. To disable MBGP, you must disable all enabled address families.
To support Layer 3 VPNs, you must enable the VPNv4 address family for all MBGP peers that will distribute VPNv4 routes across the service provider backbone. The VPNv4 address family must be enabled on the MPLS (Multiprotocol Label Switching)-enabled VR; it is not supported for BGP neighbors on the CE (VRF) side of the PE router.
Use the vpnv4 keyword for all PE to PE BGP neighbor sessions. This instructs BGP to negotiate the vpnv4 address family in an open message with other PE routers. If this command is executed when a BGP neighbor session is established, it will take effect only after BGP session is reset. We recommend that you execute this command when a BGP neighbor is operationally down. Do not issue this command for a neighbor that is part of a VRF (PE – CE), or a warning message will be displayed.
Note
To inter-operate with Cisco routers for BGP graceful restart, you must enable the IPv4 unicast address capability.This command applies to the current VR or VRF context.
Note
For an IPv6 peer, an IPv6 address family must be specified. From 21.1 ExtremeXOS allows IPV4 peering sessions to carry IPV6 routes and IPV6 peering sessions to carry IPV4 routes for the Unicast and Multicast sub-address families.Note
You must enable a VPN IPv4 unicast address family for a BGP neighbor for a PE to PE BGP neighbor session before you enable the neighbor.The following command enables the route-refresh feature for all neighbors:
enable bgp neighbor all capability route-refresh
The following command enables the VPNv4 address family for a BGP neighbor:
virtual router corp1_vrf enable bgp neighbor 192.168.96.235 capability vpnv4
The following command enables VXLAN capability for the BGP neighbor at 192.168.68.1:
enable bgp neighbor 192.168.68.1 capability ipv4-vxlan
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.
Suport for IPv4 VXLAN was added in ExtremeXOS 22.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.7 Feature License Requirements document.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB