--- title: Multi-Pod EVPN Troubleshooting: Extended BGP Communities... description: In a multi-pod EVPN fabric spanning two autonomous systems, leaf switch LB in AS 65002 fails to recognize remote VTEPs despite valid BGP routes and correct... canonical: https://daily.dev/posts/multi-pod-evpn-troubleshooting-extended-bgp-communities-ipspace-net-blog-umugr4kur twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Multi-Pod EVPN Troubleshooting: Extended BGP Communities « ipSpace.net blog | daily.dev og:description: In a multi-pod EVPN fabric spanning two autonomous systems, leaf switch LB in AS 65002 fails to recognize remote VTEPs despite valid BGP routes and correct... og:url: https://daily.dev/posts/multi-pod-evpn-troubleshooting-extended-bgp-communities-ipspace-net-blog-umugr4kur og:image: https://api.daily.dev/og/posts/UmUGr4KuR.png og:image:alt: Multi-Pod EVPN Troubleshooting: Extended BGP Communities « ipSpace.net blog 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. # Multi-Pod EVPN Troubleshooting: Extended BGP Communities « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 4 min read · 0 upvotes · 0 comments ## Summary In a multi-pod EVPN fabric spanning two autonomous systems, leaf switch LB in AS 65002 fails to recognize remote VTEPs despite valid BGP routes and correct next hops. The root cause is that extended BGP communities (Route-Target and TunnelEncap) are stripped when EVPN routes cross EBGP boundaries. By default, most EVPN implementations assume a single-AS IBGP design. Fixing the issue requires explicitly enabling extended BGP community propagation on the EBGP EVPN address family on Arista EOS. Once enabled on the border router (CA), LB receives routes with the expected extended communities, recognizes LA as a remote VTEP, and cross-site host connectivity is restored. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why are extended BGP communities missing on EVPN routes received over EBGP sessions? Extended BGP communities are not propagated by default over EBGP sessions. Most EVPN implementations are designed for single-AS IBGP environments where extended communities flow freely. When EVPN routes cross an EBGP boundary, the Route-Target and TunnelEncap communities are stripped unless extended community propagation is explicitly enabled on the EBGP EVPN address family — on Arista EOS this requires a specific nerd-knob configuration on the border router. _Engineers running multi-pod EVPN across AS boundaries track fixes like this on daily.dev before they hit production._ ### Why does my Arista EOS leaf not show any remote VTEPs even though EVPN IMET routes are present and valid? If EVPN type-3 IMET routes are present and show valid/best status but no remote VTEPs appear in 'show vxlan vtep', the likely cause is missing extended BGP communities on the received routes. Without the Route-Target and TunnelEncap extended communities, the EVPN control plane cannot install the VTEP. On Arista EOS in a multi-AS setup, extended community propagation must be explicitly enabled on the EBGP EVPN address family. _Arista EOS EVPN edge cases like this surface regularly for teams building multi-pod fabrics — daily.dev keeps that knowledge close._ ## Similar posts on daily.dev - [EVPN with SR-MPLS Core « ipSpace.net blog](https://daily.dev/posts/evpn-with-sr-mpls-core-ipspace-net-blog-taobtibzc) · ipSpace.net Blog · 0 upvotes · 0 comments --- Tags: [#bgp](https://daily.dev/tags/bgp), [#evpn](https://daily.dev/tags/evpn) [View this post on daily.dev](https://daily.dev/posts/multi-pod-evpn-troubleshooting-extended-bgp-communities-ipspace-net-blog-umugr4kur) ```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":"Multi-Pod EVPN Troubleshooting: Extended BGP Communities « ipSpace.net blog","url":"https://daily.dev/posts/multi-pod-evpn-troubleshooting-extended-bgp-communities-ipspace-net-blog-umugr4kur","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/multi-pod-evpn-troubleshooting-extended-bgp-communities-ipspace-net-blog-umugr4kur"},"datePublished":"2026-08-11T08:54:45.858Z","dateModified":"2026-10-14T02:25:02.547Z","description":"In a multi-pod EVPN fabric spanning two autonomous systems, leaf switch LB in AS 65002 fails to recognize remote VTEPs despite valid BGP routes and correct...","image":"https://media.daily.dev/image/upload/s--OHB84bZF--/f_auto/v1722860399/public/Placeholder%2010","thumbnailUrl":"https://media.daily.dev/image/upload/s--OHB84bZF--/f_auto/v1722860399/public/Placeholder%2010","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/multi-pod-evpn-troubleshooting-extended-bgp-communities-ipspace-net-blog-umugr4kur","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp,evpn","timeRequired":"PT4M"} {"@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":"Multi-Pod EVPN Troubleshooting: Extended BGP Communities « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/multi-pod-evpn-troubleshooting-extended-bgp-communities-ipspace-net-blog-umugr4kur#faq","mainEntity":[{"@type":"Question","name":"Why are extended BGP communities missing on EVPN routes received over EBGP sessions?","acceptedAnswer":{"@type":"Answer","text":"Extended BGP communities are not propagated by default over EBGP sessions. Most EVPN implementations are designed for single-AS IBGP environments where extended communities flow freely. When EVPN routes cross an EBGP boundary, the Route-Target and TunnelEncap communities are stripped unless extended community propagation is explicitly enabled on the EBGP EVPN address family — on Arista EOS this requires a specific nerd-knob configuration on the border router. Engineers running multi-pod EVPN across AS boundaries track fixes like this on daily.dev before they hit production."}},{"@type":"Question","name":"Why does my Arista EOS leaf not show any remote VTEPs even though EVPN IMET routes are present and valid?","acceptedAnswer":{"@type":"Answer","text":"If EVPN type-3 IMET routes are present and show valid/best status but no remote VTEPs appear in 'show vxlan vtep', the likely cause is missing extended BGP communities on the received routes. Without the Route-Target and TunnelEncap extended communities, the EVPN control plane cannot install the VTEP. On Arista EOS in a multi-AS setup, extended community propagation must be explicitly enabled on the EBGP EVPN address family. Arista EOS EVPN edge cases like this surface regularly for teams building multi-pod fabrics — daily.dev keeps that knowledge close."}}]} ```