--- title: BGP Community Propagation on Cisco IOS | daily.dev description: A regression was discovered in Cisco IOS/XE release 17.16.01a where the long-standing behavior of combining `neighbor send-community standard` and `neighbor... canonical: https://daily.dev/posts/bgp-community-propagation-on-cisco-ios-bwlixgn6n twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: BGP Community Propagation on Cisco IOS | daily.dev og:description: A regression was discovered in Cisco IOS/XE release 17.16.01a where the long-standing behavior of combining `neighbor send-community standard` and `neighbor... og:url: https://daily.dev/posts/bgp-community-propagation-on-cisco-ios-bwlixgn6n og:image: https://api.daily.dev/og/posts/bWliXgn6N.png og:image:alt: BGP Community Propagation on Cisco IOS og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # BGP Community Propagation on Cisco IOS **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 2 min read · 0 upvotes · 0 comments ## Summary A regression was discovered in Cisco IOS/XE release 17.16.01a where the long-standing behavior of combining `neighbor send-community standard` and `neighbor send-community extended` into `neighbor send-community both` was silently broken. Instead of merging the two commands, the second command now overrides the first, causing standard BGP community propagation to be lost when extended is configured last. This behavior worked correctly through at least IOS/XE 17.15.01. The workaround is to use `neighbor send-community both` directly. A Cisco engineer confirmed the regression on 17.18.01 hardware and is investigating the cause. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Does Cisco IOS/XE still merge 'neighbor send-community standard' and 'neighbor send-community extended' into 'neighbor send-community both'? No, this merging behavior broke in Cisco IOS/XE release 17.16.01a. Prior to that release (through at least 17.15.01), entering both commands sequentially would consolidate them into 'neighbor send-community both' in the running config. From 17.16.01a onward, the second command overrides the first, so only the last-entered community type is retained. The safe workaround is to configure 'neighbor x.x.x.x send-community both' directly. _Network engineers templating BGP configs across IOS/XE versions track regressions like this on daily.dev._ ### What is the workaround for the Cisco IOS/XE BGP send-community regression in 17.16? Use 'neighbor x.x.x.x send-community both' as a single command instead of entering standard and extended separately. The regression, confirmed on hardware through 17.18.01, causes the second send-community keyword to override the first rather than merging them. Entering 'both' directly bypasses the broken accumulation logic and correctly enables propagation of both standard and extended BGP communities. _Teams managing Cisco BGP deployments at scale find regression details like this on daily.dev._ ## Similar posts on daily.dev - [Exploring the BGP Neighbor CONNECT State « ipSpace.net blog](https://daily.dev/posts/exploring-the-bgp-neighbor-connect-state-ipspace-net-blog-q28k0i62x) · ipSpace.net Blog · 0 upvotes · 0 comments - [The Never-Ending IPv6 Loopback Prefix Saga « ipSpace.net blog](https://daily.dev/posts/the-never-ending-ipv6-loopback-prefix-saga-ipspace-net-blog-4nlhgh10l) · ipSpace.net Blog · 0 upvotes · 0 comments --- Tags: [#bgp](https://daily.dev/tags/bgp) [View this post on daily.dev](https://daily.dev/posts/bgp-community-propagation-on-cisco-ios-bwlixgn6n) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"BGP Community Propagation on Cisco IOS","url":"https://daily.dev/posts/bgp-community-propagation-on-cisco-ios-bwlixgn6n","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/bgp-community-propagation-on-cisco-ios-bwlixgn6n"},"datePublished":"2026-08-11T08:54:52.872Z","dateModified":"2026-08-24T06:57:04.170Z","description":"A regression was discovered in Cisco IOS/XE release 17.16.01a where the long-standing behavior of combining `neighbor send-community standard` and `neighbor...","image":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","thumbnailUrl":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","isAccessibleForFree":true,"articleSection":"ipSpace.net Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ipSpace.net Blog","logo":"https://media.daily.dev/image/upload/s--xS7E82MT--/f_auto,q_auto/v1786438303/logos/ipspace?_a=BAMAMicg0","url":"https://daily.dev/sources/ipspace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/bgp-community-propagation-on-cisco-ios-bwlixgn6n","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ipSpace.net Blog","item":"https://daily.dev/sources/ipspace"},{"@type":"ListItem","position":3,"name":"BGP Community Propagation on Cisco IOS"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/bgp-community-propagation-on-cisco-ios-bwlixgn6n#faq","mainEntity":[{"@type":"Question","name":"Does Cisco IOS/XE still merge 'neighbor send-community standard' and 'neighbor send-community extended' into 'neighbor send-community both'?","acceptedAnswer":{"@type":"Answer","text":"No, this merging behavior broke in Cisco IOS/XE release 17.16.01a. Prior to that release (through at least 17.15.01), entering both commands sequentially would consolidate them into 'neighbor send-community both' in the running config. From 17.16.01a onward, the second command overrides the first, so only the last-entered community type is retained. The safe workaround is to configure 'neighbor x.x.x.x send-community both' directly. Network engineers templating BGP configs across IOS/XE versions track regressions like this on daily.dev."}},{"@type":"Question","name":"What is the workaround for the Cisco IOS/XE BGP send-community regression in 17.16?","acceptedAnswer":{"@type":"Answer","text":"Use 'neighbor x.x.x.x send-community both' as a single command instead of entering standard and extended separately. The regression, confirmed on hardware through 17.18.01, causes the second send-community keyword to override the first rather than merging them. Entering 'both' directly bypasses the broken accumulation logic and correctly enables propagation of both standard and extended BGP communities. Teams managing Cisco BGP deployments at scale find regression details like this on daily.dev."}}]} ```