--- title: Multi-Pod EVPN Troubleshooting: Route Targets «... description: This post is the fourth in a multi-pod EVPN troubleshooting series. After fixing BGP next hop issues in a previous installment, the author investigates why PE... canonical: https://daily.dev/posts/multi-pod-evpn-troubleshooting-route-targets-ipspace-net-blog-8n7ndbuqg twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Multi-Pod EVPN Troubleshooting: Route Targets « ipSpace.net blog | daily.dev og:description: This post is the fourth in a multi-pod EVPN troubleshooting series. After fixing BGP next hop issues in a previous installment, the author investigates why PE... og:url: https://daily.dev/posts/multi-pod-evpn-troubleshooting-route-targets-ipspace-net-blog-8n7ndbuqg og:image: https://api.daily.dev/og/posts/8N7NdBuqg.png og:image:alt: Multi-Pod EVPN Troubleshooting: Route Targets « 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: Route Targets « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 5 min read · 0 upvotes · 0 comments ## Summary This post is the fourth in a multi-pod EVPN troubleshooting series. After fixing BGP next hop issues in a previous installment, the author investigates why PE devices still fail to recognize each other as remote VTEPs. The root cause is a route target mismatch: each pod's leaf switches use their local BGP AS number when auto-generating route targets (e.g., 65001:1000 vs 65002:1000), so import filters on each side reject the other pod's IMET routes. Two fixes are discussed — adding remote import route targets or standardizing all import/export route targets to a consistent cross-AS value (65000:1000). After applying the fix on LA, it correctly recognizes LB as a remote VTEP, but LB still doesn't see LA, indicating further work remains. The post also warns about automatic route target derivation from local AS numbers and vendor inconsistencies in multi-vendor EVPN deployments. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why are my EVPN IMET routes valid but the remote VTEP not showing up in my VXLAN VTEP table? A common cause is a route target mismatch between pods. Even if IMET routes are valid and have correct BGP next hops, a leaf switch only installs a remote VTEP when the route's extended community matches its import route target. If each pod auto-generates route targets from its local AS number (e.g., 65001:1000 vs 65002:1000), the import filter on the other side will silently reject the route. _Engineers debugging multi-pod EVPN VTEP discovery issues track patterns like this on daily.dev._ ### How should I fix route target mismatches between autonomous systems in a multi-pod EVPN fabric? Two approaches exist: add the remote pod's route target as an additional import target on each leaf (non-disruptive but doesn't scale with more pods), or standardize all import and export route targets to a single consistent value across all autonomous systems (e.g., 65000:1000). The second approach scales better when adding more pods but requires a coordinated configuration change. _Network engineers planning multi-pod EVPN expansions find relevant design discussions on daily.dev._ ## 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-route-targets-ipspace-net-blog-8n7ndbuqg) ```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: Route Targets « ipSpace.net blog","url":"https://daily.dev/posts/multi-pod-evpn-troubleshooting-route-targets-ipspace-net-blog-8n7ndbuqg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/multi-pod-evpn-troubleshooting-route-targets-ipspace-net-blog-8n7ndbuqg"},"datePublished":"2026-08-11T08:55:59.036Z","dateModified":"2026-10-14T02:26:07.871Z","description":"This post is the fourth in a multi-pod EVPN troubleshooting series. After fixing BGP next hop issues in a previous installment, the author investigates why PE...","image":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","thumbnailUrl":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","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-route-targets-ipspace-net-blog-8n7ndbuqg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp,evpn","timeRequired":"PT5M"} {"@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: Route Targets « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/multi-pod-evpn-troubleshooting-route-targets-ipspace-net-blog-8n7ndbuqg#faq","mainEntity":[{"@type":"Question","name":"Why are my EVPN IMET routes valid but the remote VTEP not showing up in my VXLAN VTEP table?","acceptedAnswer":{"@type":"Answer","text":"A common cause is a route target mismatch between pods. Even if IMET routes are valid and have correct BGP next hops, a leaf switch only installs a remote VTEP when the route's extended community matches its import route target. If each pod auto-generates route targets from its local AS number (e.g., 65001:1000 vs 65002:1000), the import filter on the other side will silently reject the route. Engineers debugging multi-pod EVPN VTEP discovery issues track patterns like this on daily.dev."}},{"@type":"Question","name":"How should I fix route target mismatches between autonomous systems in a multi-pod EVPN fabric?","acceptedAnswer":{"@type":"Answer","text":"Two approaches exist: add the remote pod's route target as an additional import target on each leaf (non-disruptive but doesn't scale with more pods), or standardize all import and export route targets to a single consistent value across all autonomous systems (e.g., 65000:1000). The second approach scales better when adding more pods but requires a coordinated configuration change. Network engineers planning multi-pod EVPN expansions find relevant design discussions on daily.dev."}}]} ```