configure bgp peer-group send-community

configure bgp peer-group peer-group-name {address-family [ipv4-unicast | ipv4-multicast |ipv6-unicast | ipv6-multicast |vpnv4]} [send-community | dont-send-community] {both | extended | standard}


Configures whether communities should be sent to neighbors as part of route updates.

Syntax Description

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.
send-community Specifies that communities are sent to neighbors as part of route updates.
dont-send-community Specifies that communities are not sent to neighbors as part of route updates.
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.

Usage Guidelines

These settings apply to the peer group and all neighbors of the peer group.

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.



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.

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.

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 communities to be sent to neighbors as part of route updates:

configure bgp peer-group outer 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.

Platform Availability

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.