--- title: EVPN Designs: Multi-Pod with IP-Only WAN Routers «... description: This post details how to implement a multi-pod EVPN design using IP-only WAN edge routers, effectively applying Inter-AS Option C with EVPN/VXLAN. Instead of... canonical: https://daily.dev/posts/evpn-designs-multi-pod-with-ip-only-wan-routers-ipspace-net-blog-wfbyeodrx twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: EVPN Designs: Multi-Pod with IP-Only WAN Routers « ipSpace.net blog | daily.dev og:description: This post details how to implement a multi-pod EVPN design using IP-only WAN edge routers, effectively applying Inter-AS Option C with EVPN/VXLAN. Instead of... og:url: https://daily.dev/posts/evpn-designs-multi-pod-with-ip-only-wan-routers-ipspace-net-blog-wfbyeodrx og:image: https://api.daily.dev/og/posts/wFByeODrX.png og:image:alt: EVPN Designs: Multi-Pod with IP-Only WAN Routers « 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 with IP-Only WAN Routers « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 6 min read · 0 upvotes · 0 comments ## Summary This post details how to implement a multi-pod EVPN design using IP-only WAN edge routers, effectively applying Inter-AS Option C with EVPN/VXLAN. Instead of requiring WAN edge routers to support EVPN, a multihop EBGP session is established between spine route reflectors to carry EVPN routes, while the WAN edge routers handle only IPv4 underlay forwarding. The post includes a working lab topology using Arista EOS containers via netlab, with configuration snippets and verified BGP EVPN route output showing correct next-hop preservation across sites. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How can I connect two EVPN fabrics without requiring WAN edge routers to support EVPN? Use Inter-AS Option C: establish a multihop EBGP session between the spine route reflectors of each fabric to carry EVPN routes, while the WAN edge routers exchange only IPv4 underlay routes via a standard EBGP session. This removes the EVPN requirement from WAN edge devices entirely, allowing simpler IP-only routers at the boundary. _Engineers designing multi-pod EVPN fabrics track design patterns like this on daily.dev._ ### In a multi-pod EVPN design with Inter-AS Option C, do EVPN next hops change when routes cross between fabrics? No, next hops are preserved. In this design, the VTEP address of the originating leaf (e.g., LA at 10.0.0.1) remains the next hop as seen on the remote leaf (LB), and the route reflector (CB) is the advertising peer — not the WAN edge router. This is the expected behavior for multi-pod deployments. _Keeping next-hop behavior correct across fabric boundaries is a common pain point — developers and network engineers working through it share findings 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-with-ip-only-wan-routers-ipspace-net-blog-wfbyeodrx) ```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 with IP-Only WAN Routers « ipSpace.net blog","url":"https://daily.dev/posts/evpn-designs-multi-pod-with-ip-only-wan-routers-ipspace-net-blog-wfbyeodrx","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/evpn-designs-multi-pod-with-ip-only-wan-routers-ipspace-net-blog-wfbyeodrx"},"datePublished":"2026-08-11T08:56:01.563Z","dateModified":"2026-08-11T09:10:17.301Z","description":"This post details how to implement a multi-pod EVPN design using IP-only WAN edge routers, effectively applying Inter-AS Option C with EVPN/VXLAN. Instead of...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/14c9352e3c80977de6ccfc33412d637a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/14c9352e3c80977de6ccfc33412d637a?_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-with-ip-only-wan-routers-ipspace-net-blog-wfbyeodrx","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 with IP-Only WAN Routers « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/evpn-designs-multi-pod-with-ip-only-wan-routers-ipspace-net-blog-wfbyeodrx#faq","mainEntity":[{"@type":"Question","name":"How can I connect two EVPN fabrics without requiring WAN edge routers to support EVPN?","acceptedAnswer":{"@type":"Answer","text":"Use Inter-AS Option C: establish a multihop EBGP session between the spine route reflectors of each fabric to carry EVPN routes, while the WAN edge routers exchange only IPv4 underlay routes via a standard EBGP session. This removes the EVPN requirement from WAN edge devices entirely, allowing simpler IP-only routers at the boundary. Engineers designing multi-pod EVPN fabrics track design patterns like this on daily.dev."}},{"@type":"Question","name":"In a multi-pod EVPN design with Inter-AS Option C, do EVPN next hops change when routes cross between fabrics?","acceptedAnswer":{"@type":"Answer","text":"No, next hops are preserved. In this design, the VTEP address of the originating leaf (e.g., LA at 10.0.0.1) remains the next hop as seen on the remote leaf (LB), and the route reflector (CB) is the advertising peer — not the WAN edge router. This is the expected behavior for multi-pod deployments. Keeping next-hop behavior correct across fabric boundaries is a common pain point — developers and network engineers working through it share findings on daily.dev."}}]} ```