--- title: Using Multiple Transit VNIs per EVPN VRF « ipSpace.net blog description: An investigation into whether EVPN implementations can handle multiple transit VNIs per VRF, rather than requiring a single matching VNI across all PE devices.... canonical: https://daily.dev/posts/using-multiple-transit-vnis-per-evpn-vrf-ipspace-net-blog-ywwvwx1eh twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Using Multiple Transit VNIs per EVPN VRF « ipSpace.net blog | daily.dev og:description: An investigation into whether EVPN implementations can handle multiple transit VNIs per VRF, rather than requiring a single matching VNI across all PE devices.... og:url: https://daily.dev/posts/using-multiple-transit-vnis-per-evpn-vrf-ipspace-net-blog-ywwvwx1eh og:image: https://api.daily.dev/og/posts/yWwvWx1EH.png og:image:alt: Using Multiple Transit VNIs per EVPN VRF « 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. # Using Multiple Transit VNIs per EVPN VRF « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 5 min read · 0 upvotes · 0 comments ## Summary An investigation into whether EVPN implementations can handle multiple transit VNIs per VRF, rather than requiring a single matching VNI across all PE devices. Using a netlab lab with three Arista cEOS switches each configured with a unique per-switch VNI for a shared VRF, the tests show that Arista cEOS handles this gracefully: each unique remote VNI gets its own dynamically allocated VLAN and VXLAN mapping. However, this approach consumes one VLAN per unique remote VNI, which can exhaust the 4096 VLAN limit in large deployments. The conclusion: technically possible, but not recommended in practice. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Can different PE devices use different transit VNIs for the same EVPN VRF, or must they all match? At least some EVPN implementations, including Arista cEOS, handle mismatched transit VNIs per VRF without issues. Each unique VNI advertised by a remote PE gets its own dynamically allocated VLAN on the receiving switch. The trade-off is VLAN consumption: one VLAN is created per unique remote VNI, which can exhaust the 4096 VLAN limit in large deployments. _Engineers designing large EVPN fabrics track scale limitations like this on daily.dev before they become production problems._ ### What happens to VLAN allocation on Arista cEOS when multiple transit VNIs are used in the same EVPN VRF? Arista cEOS dynamically allocates a separate internal VLAN for every unique VNI value advertised by peer PE devices. The local VNI is mapped to the VRF's routing table, while remote VNIs each get their own VLAN without a routing table association. In a three-switch lab with VNIs 200101, 200102, and 200103, switch s1 allocated VLANs 4092, 4093, and 4094 respectively. _Network engineers evaluating Arista EVPN behavior at scale find real lab findings like these 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/using-multiple-transit-vnis-per-evpn-vrf-ipspace-net-blog-ywwvwx1eh) ```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":"Using Multiple Transit VNIs per EVPN VRF « ipSpace.net blog","url":"https://daily.dev/posts/using-multiple-transit-vnis-per-evpn-vrf-ipspace-net-blog-ywwvwx1eh","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/using-multiple-transit-vnis-per-evpn-vrf-ipspace-net-blog-ywwvwx1eh"},"datePublished":"2026-08-11T08:51:53.795Z","dateModified":"2026-10-14T02:23:37.715Z","description":"An investigation into whether EVPN implementations can handle multiple transit VNIs per VRF, rather than requiring a single matching VNI across all PE devices....","image":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","thumbnailUrl":"https://media.daily.dev/image/upload/s--ZrL_HSsR--/f_auto/v1722860399/public/Placeholder%2006","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/using-multiple-transit-vnis-per-evpn-vrf-ipspace-net-blog-ywwvwx1eh","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":"Using Multiple Transit VNIs per EVPN VRF « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/using-multiple-transit-vnis-per-evpn-vrf-ipspace-net-blog-ywwvwx1eh#faq","mainEntity":[{"@type":"Question","name":"Can different PE devices use different transit VNIs for the same EVPN VRF, or must they all match?","acceptedAnswer":{"@type":"Answer","text":"At least some EVPN implementations, including Arista cEOS, handle mismatched transit VNIs per VRF without issues. Each unique VNI advertised by a remote PE gets its own dynamically allocated VLAN on the receiving switch. The trade-off is VLAN consumption: one VLAN is created per unique remote VNI, which can exhaust the 4096 VLAN limit in large deployments. Engineers designing large EVPN fabrics track scale limitations like this on daily.dev before they become production problems."}},{"@type":"Question","name":"What happens to VLAN allocation on Arista cEOS when multiple transit VNIs are used in the same EVPN VRF?","acceptedAnswer":{"@type":"Answer","text":"Arista cEOS dynamically allocates a separate internal VLAN for every unique VNI value advertised by peer PE devices. The local VNI is mapped to the VRF's routing table, while remote VNIs each get their own VLAN without a routing table association. In a three-switch lab with VNIs 200101, 200102, and 200103, switch s1 allocated VLANs 4092, 4093, and 4094 respectively. Network engineers evaluating Arista EVPN behavior at scale find real lab findings like these on daily.dev."}}]} ```