BGP basics: BGP communities propagation

I’ve got this question from Pete:

Which community will be sent if only "neighbor {ip-address} send-community" is configured?

Quick answer: only the standard BGP communities are propagated.

More details

The neighbor send-community enables the community propagation. Without this option, no BGP communities will be sent to the BGP neighbor, even if they are attached to entries in the local BGP table. After the neighbor send-community has been configured, the router will start propagating the communities attached to BGP entries in its BGP table to the neighbor.

BGP has two community attributes: the standard BGP communities (defined in RFC 1997) and extended BGP communities (defined in RFC 4360). You can control which communities are sent to a BGP neighbor with the (very obvious) standard, extended or both options of the neighbor send-community router configuration command. If you use neighbor send-community with no extra options, only the standard BGP communities are propagated to preserve backward compatibility.

This article is part of You've asked for it series.


  1. says under vpnv4 family, if configured send-community both, does the PE routers sent standard community as well?
  2. I tried to redistribute eigrp and bgp into each other. After redistribution both eigrp and bgp routers are getting routes of each other but bgp router cannot ping any ip from eigrp router at same time eigrp router can ping any ip from bgp router.

    Please find the attached configuration for the same. Could anyone tell me what is the problem?

    Router A

    router eigrp 1
    no auto-summary

    Router B

    router eigrp 1
    redistribute bgp 2 route-map check
    no auto-summary

    router bgp 2
    no synchronization
    bgp log-neighbor-changes
    bgp redistribute-internal
    network mask
    network mask
    redistribute eigrp 1
    neighbor remote-as 2
    neighbor update-source Loopback200
    no auto-summary

    route-map check permit 10
    match ip address prefix-list bgp-routes
    set metric 100000 10 255 1 1500

    ip prefix-list bgp-routes seq 5 permit
    ip prefix-list bgp-routes seq 6 permit
    ip prefix-list bgp-routes seq 7 permit

    Router C

    router bgp 2
    no synchronization
    bgp log-neighbor-changes
    network mask
    neighbor remote-as 2
    neighbor update-source Loopback1
    no auto-summary

    Network Next Hop Metric LocPrf Weight Path
    *>i116.214.28.0/24 0 100 0 i
    *> 0 32768 i
    *>i172.16.252.32/27 297246976 100 0 ?
    *>i200.200.200.0/30 0 100 0 i


    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 16/32/92 ms


    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to, timeout is 2 seconds:
    Success rate is 0 percent (0/5)
  3. This bothers me a lot.

    Say I decided to use communities and, god forbid, stumbled upon some cisco routers on my way in some transit AS, those routers must be configured to relay community attributes. Otherwise I'm busted.

    Doesn't look like following RFC logic at all, if you ask me.

  4. Communities were never intended to have global reach (and most of them have local significance anyway), so it's not necessarily a bad idea that they're filtered by default.

    BTW, the RFC logic is not violated. Communities are optional transitive attributes, which means you should pass them on IF YOU DON'T KNOW WHAT TO DO WITH THEM. If you do, you're free to do whatever you wish.
  5. Hello,

    I noticed I can insert more than one community value per line in a route-map:

    route-map stanga permit 10
    match ip address prefix-list six
    set community 100:70 100:1300

    The two values are reaching the other neighbor: from (
    Origin IGP, metric 0, localpref 130, valid, external, best
    Community: 100:70 100:1300

    But only one action is performed on the prefix, although route-map should modify both MED and LOCAL PREF:

    ip bgp-community new-format
    ip community-list 1 permit 100:1300
    ip community-list 2 permit 100:1250
    ip community-list 3 permit 100:80
    ip community-list 4 permit 100:70
    route-map Clienti permit 10
    match community 1
    set local-preference 130
    route-map Clienti permit 20
    match community 2
    set local-preference 125
    route-map Clienti permit 30
    match community 3
    set metric 80
    route-map Clienti permit 40
    match community 4
    set metric 70

    Can you tell me why MED is not modified?
  6. Route-map processing stops after the first match. You need "route-map continue" functionality.
  7. What are the equivalent commands in XR for Send-community both and send-community extended.

    Does these commands are required only for EBGP peers or they also require for iBGP peers.

    Please explain the above condition for both IOS and IOS XR
    1. On Cisco IOS (classic) you have to configure community propagation on both IBGP and EBGP peers (if that's what you want to do). I'm not an IOS XR person, so you'll have to ask that question somewhere else.
  8. Thanks for your properly response, I have found it, as you said for IOS we must configure for both IBGP and EBGP neighbors, Whereas In IOS XR, by default it propagates to IBGP neighbors and we must configure for EBGP neighbors.

    Thanks once again.
  9. Under IPv6, what is the effect of send-community attribute in BGP. if i not used send-community attribute but only activate attribute then effects.

    Please reply
Add comment