--- title: EVPN Designs: Multi-Pod Fabrics « ipSpace.net blog description: A deep-dive into EVPN multi-pod fabric design where two EVPN fabrics are connected via an EBGP session to form a unified, larger EVPN fabric. The setup uses... canonical: https://daily.dev/posts/evpn-designs-multi-pod-fabrics-ipspace-net-blog-qqi3o03f0 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: EVPN Designs: Multi-Pod Fabrics « ipSpace.net blog | daily.dev og:description: A deep-dive into EVPN multi-pod fabric design where two EVPN fabrics are connected via an EBGP session to form a unified, larger EVPN fabric. The setup uses... og:url: https://daily.dev/posts/evpn-designs-multi-pod-fabrics-ipspace-net-blog-qqi3o03f0 og:image: https://api.daily.dev/og/posts/QQI3o03f0.png og:image:alt: EVPN Designs: Multi-Pod Fabrics « 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. # EVPN Designs: Multi-Pod Fabrics « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 6 min read · 0 upvotes · 0 comments ## Summary A deep-dive into EVPN multi-pod fabric design where two EVPN fabrics are connected via an EBGP session to form a unified, larger EVPN fabric. The setup uses OSPF and IBGP within each site, with EBGP between WAN edge routers exchanging both IPv4 and EVPN prefixes without changing next hops — allowing direct VXLAN traffic between leaf switches across sites. The post includes a netlab topology diff showing key configuration changes (switching from FRR to Arista EOS, enabling EVPN on EBGP sessions, propagating extended BGP communities), actual BGP EVPN table output from Arista EOS, and instructions for spinning up the lab using netlab with various device options including SR Linux and Aruba AOS-CX. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I connect two EVPN fabrics with EBGP to form a multi-pod fabric without changing EVPN next hops? Configure an EBGP session between WAN edge routers with both IPv4 and EVPN address families enabled, and do not change the next hop on EVPN prefixes. This allows leaf switches in each site to exchange VXLAN traffic directly using the originating leaf's loopback as the next hop. Extended BGP communities must also be propagated over the EBGP session so route targets are preserved across AS boundaries. _Network engineers building multi-pod EVPN fabrics track design patterns and gotchas like next-hop handling on daily.dev._ ### Why does an EVPN multi-pod EBGP design require extended BGP communities to be sent over EBGP sessions? EVPN route targets are encoded as extended BGP communities. By default, extended communities are not forwarded over EBGP sessions, so the receiving site cannot match route targets and import EVPN routes into the correct VRF or VLAN. Explicitly enabling extended community propagation on the EBGP session (bgp.community.ebgp: [standard, extended]) is required for the design to function. _Keeping up with EVPN design nuances like community propagation is easier when BGP content surfaces where you already read on daily.dev._ ### Why does the EVPN multi-pod netlab example use Arista EOS instead of FRR? FRR has an IBGP loopback bug that prevents the multi-pod design from working correctly. The netlab topology switches the default device from FRR to Arista EOS specifically to avoid this issue, as the design relies on IBGP sessions between loopback addresses within each site. _Developers and network engineers evaluating NOS options for EVPN labs find comparative notes like this 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) [View this post on daily.dev](https://daily.dev/posts/evpn-designs-multi-pod-fabrics-ipspace-net-blog-qqi3o03f0) ```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":"EVPN Designs: Multi-Pod Fabrics « ipSpace.net blog","url":"https://daily.dev/posts/evpn-designs-multi-pod-fabrics-ipspace-net-blog-qqi3o03f0","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/evpn-designs-multi-pod-fabrics-ipspace-net-blog-qqi3o03f0"},"datePublished":"2026-08-11T08:56:01.409Z","dateModified":"2026-08-11T09:28:08.191Z","description":"A deep-dive into EVPN multi-pod fabric design where two EVPN fabrics are connected via an EBGP session to form a unified, larger EVPN fabric. The setup uses...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1d9c13fca7e8dc7b93c7a70b465b3be9?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1d9c13fca7e8dc7b93c7a70b465b3be9?_a=AQAEuop","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/evpn-designs-multi-pod-fabrics-ipspace-net-blog-qqi3o03f0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp","timeRequired":"PT6M"} {"@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":"EVPN Designs: Multi-Pod Fabrics « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/evpn-designs-multi-pod-fabrics-ipspace-net-blog-qqi3o03f0#faq","mainEntity":[{"@type":"Question","name":"How do I connect two EVPN fabrics with EBGP to form a multi-pod fabric without changing EVPN next hops?","acceptedAnswer":{"@type":"Answer","text":"Configure an EBGP session between WAN edge routers with both IPv4 and EVPN address families enabled, and do not change the next hop on EVPN prefixes. This allows leaf switches in each site to exchange VXLAN traffic directly using the originating leaf's loopback as the next hop. Extended BGP communities must also be propagated over the EBGP session so route targets are preserved across AS boundaries. Network engineers building multi-pod EVPN fabrics track design patterns and gotchas like next-hop handling on daily.dev."}},{"@type":"Question","name":"Why does an EVPN multi-pod EBGP design require extended BGP communities to be sent over EBGP sessions?","acceptedAnswer":{"@type":"Answer","text":"EVPN route targets are encoded as extended BGP communities. By default, extended communities are not forwarded over EBGP sessions, so the receiving site cannot match route targets and import EVPN routes into the correct VRF or VLAN. Explicitly enabling extended community propagation on the EBGP session (bgp.community.ebgp: [standard, extended]) is required for the design to function. Keeping up with EVPN design nuances like community propagation is easier when BGP content surfaces where you already read on daily.dev."}},{"@type":"Question","name":"Why does the EVPN multi-pod netlab example use Arista EOS instead of FRR?","acceptedAnswer":{"@type":"Answer","text":"FRR has an IBGP loopback bug that prevents the multi-pod design from working correctly. The netlab topology switches the default device from FRR to Arista EOS specifically to avoid this issue, as the design relies on IBGP sessions between loopback addresses within each site. Developers and network engineers evaluating NOS options for EVPN labs find comparative notes like this on daily.dev."}}]} ```