Configure Bgp Community And Extended-Community Advertisements - Cisco NCS 5500 Series Configuration Manual

BGP Cost Community
• route-policy route-policy-name { in | out }
Step 8
commit
Step 9 show bgp ip-address
Example:
RP/0/RP0/CPU0:router# show bgp 172.168.40.24
Displays the cost community in the following format:
Cost: POI : cost-community-ID : cost-number

Configure BGP Community and Extended-Community Advertisements

Perform this task to specify that community/extended-community attributes should be sent to an eBGP
neighbor. These attributes are not sent to an eBGP neighbor by default. By contrast, they are always sent to
iBGP neighbors. This section provides examples on how to enable sending community attributes. The
send-community-ebgp keyword can be replaced by the send-extended-community-ebgp keyword to
enable sending extended-communities.
If the send-community-ebgp command is configured for a neighbor group or address family group, all
neighbors using the group inherit the configuration. Configuring the command specifically for a neighbor
overrides inherited values.
Note BGP community and extended-community filtering cannot be configured for iBGP neighbors. Communities
and extended-communities are always sent to iBGP neighbors under VPNv4, MDT, IPv4, and IPv6 address
families.
SUMMARY STEPS
1. configure
2. router bgp as-number
3. neighbor ip-address
4. remote-as as-number
5. address-family{ipv4 {labeled-unicast | unicast | mdt | | mvpn | rt-filter | tunnel} | ipv6
{labeled-unicast | mvpn | unicast}}
6. Use one of these commands:
7. commit
BGP Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.2.x
54
• send-community-ebgp
• send-extended-community-ebgp
Implementing BGP