--- title: EVPN Centralized Routing with Arista EOS « ipSpace.net blog description: Explores how Arista EOS behaves in an EVPN centralized routing design where a spine switch acts as the default gateway for layer-2 leaf switches. By default,... canonical: https://daily.dev/posts/evpn-centralized-routing-with-arista-eos-ipspace-net-blog-nbxol1pfx twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: EVPN Centralized Routing with Arista EOS « ipSpace.net blog | daily.dev og:description: Explores how Arista EOS behaves in an EVPN centralized routing design where a spine switch acts as the default gateway for layer-2 leaf switches. By default,... og:url: https://daily.dev/posts/evpn-centralized-routing-with-arista-eos-ipspace-net-blog-nbxol1pfx og:image: https://api.daily.dev/og/posts/NBxOl1pFx.png og:image:alt: EVPN Centralized Routing with Arista EOS « 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 Centralized Routing with Arista EOS « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 6 min read · 0 upvotes · 0 comments ## Summary Explores how Arista EOS behaves in an EVPN centralized routing design where a spine switch acts as the default gateway for layer-2 leaf switches. By default, the spine does not advertise MAC+IP routes for hosts learned over VXLAN, forcing leaf switches to flood all routed traffic. The fix is to use the `redistribute router-mac system` or `redistribute router-mac system ip` command on the spine's MAC-VRF instances, causing it to advertise its gateway MAC (and optionally IP) via EVPN type-2 routes, eliminating unnecessary flooding. ARP snooping on leaf switches is an alternative approach. Lab topology is available in the netlab-examples GitHub repository. ## 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 stop leaf switches from flooding routed traffic in an Arista EOS EVPN centralized routing design? Add `redistribute router-mac system` (MAC only) or `redistribute router-mac system ip` (MAC+IP type-2 route) to each MAC-VRF instance on the centralized spine router. Without this, the spine does not advertise its gateway MAC address via EVPN, so leaf switches have no control-plane entry for the default gateway and must flood all routed traffic destined for it. _Engineers tuning EVPN fabric behavior track commands like these on daily.dev before they hit production._ ### Why does the Arista EOS centralized EVPN router not advertise MAC+IP routes for hosts learned over VXLAN? Arista EOS only advertises MAC+IP EVPN type-2 routes for hosts learned locally (data-plane on a directly attached interface). Hosts whose ARP entries are learned over a VXLAN interface are not re-advertised by the centralized router by default, meaning other routers in the fabric must perform their own ARP resolution independently. _Networking engineers navigating EVPN edge cases like this one find relevant deep-dives 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/evpn-centralized-routing-with-arista-eos-ipspace-net-blog-nbxol1pfx) ```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 Centralized Routing with Arista EOS « ipSpace.net blog","url":"https://daily.dev/posts/evpn-centralized-routing-with-arista-eos-ipspace-net-blog-nbxol1pfx","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/evpn-centralized-routing-with-arista-eos-ipspace-net-blog-nbxol1pfx"},"datePublished":"2026-08-11T08:54:03.963Z","dateModified":"2026-10-14T02:28:50.863Z","description":"Explores how Arista EOS behaves in an EVPN centralized routing design where a spine switch acts as the default gateway for layer-2 leaf switches. By default,...","image":"https://media.daily.dev/image/upload/s--foaA6JGU--/f_auto/v1722860399/public/Placeholder%2004","thumbnailUrl":"https://media.daily.dev/image/upload/s--foaA6JGU--/f_auto/v1722860399/public/Placeholder%2004","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-centralized-routing-with-arista-eos-ipspace-net-blog-nbxol1pfx","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"bgp,evpn","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 Centralized Routing with Arista EOS « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/evpn-centralized-routing-with-arista-eos-ipspace-net-blog-nbxol1pfx#faq","mainEntity":[{"@type":"Question","name":"How do I stop leaf switches from flooding routed traffic in an Arista EOS EVPN centralized routing design?","acceptedAnswer":{"@type":"Answer","text":"Add `redistribute router-mac system` (MAC only) or `redistribute router-mac system ip` (MAC+IP type-2 route) to each MAC-VRF instance on the centralized spine router. Without this, the spine does not advertise its gateway MAC address via EVPN, so leaf switches have no control-plane entry for the default gateway and must flood all routed traffic destined for it. Engineers tuning EVPN fabric behavior track commands like these on daily.dev before they hit production."}},{"@type":"Question","name":"Why does the Arista EOS centralized EVPN router not advertise MAC+IP routes for hosts learned over VXLAN?","acceptedAnswer":{"@type":"Answer","text":"Arista EOS only advertises MAC+IP EVPN type-2 routes for hosts learned locally (data-plane on a directly attached interface). Hosts whose ARP entries are learned over a VXLAN interface are not re-advertised by the centralized router by default, meaning other routers in the fabric must perform their own ARP resolution independently. Networking engineers navigating EVPN edge cases like this one find relevant deep-dives on daily.dev."}}]} ```