Configures whether the community path attribute associated with a BGP NLRI should be included in the route updates sent to the BGP neighbor.
|remoteaddr||Specifies an IP address of a BGP neighbor.|
|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.|
|send-community||Specifies to include the community path attribute.|
|dont-send-community||Specifies not to include the community path attribute.|
|both||Send both standard and extended community attributes to this BGP neighbor, or neighbors in peer group|
|extended||Send only extended communities to this BGP neighbor or neighbors in peer group|
|standard||Send only standard communities to this BGP neighbor or neighbors in peer group|
If no address family is specified, IPv4 unicast is the default. If no optional keyword (both, standard or extended) is specified, standard is assumed.
The command is additive; that is, if the command is executed twice with the standard or extended option, both the extended and standard communities are sent to the BGP neighbor.
This command applies to the current VR or VRF context.
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.
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 includes the community path attribute associated with a BGP NLRI in the route updates sent to all BGP neighbors:
configure bgp neighbor all send-community
This command was first available in ExtremeXOS 10.1.
This command required a specific license in ExtremeXOS 11.1.
Options to control the advertisement of extended community attributes were added in ExtremeXOS12.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 Switch Engine 32.3 Feature License Requirements document.