# Using Multiple Transit VNIs per EVPN VRF

DevFeed: [Using Multiple Transit VNIs per EVPN VRF](<https://devfeed.tech/articles/using-multiple-transit-vnis-per-evpn-vrf-11055.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2024/08/multiple-transit-vni-evpn-vrf/>)

Published: 2024-08-22T06:48:00Z

Content type: tutorial

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [evpn](<https://devfeed.tech/topics/evpn.md>), [VXLAN](<https://devfeed.tech/topics/vxlan.md>), [BGP](<https://devfeed.tech/topics/bgp.md>), [networking](<https://devfeed.tech/topics/networking.md>)

Tags: [bgp](<https://devfeed.tech/tags/bgp.md>), [evpn](<https://devfeed.tech/tags/evpn.md>), [github](<https://devfeed.tech/tags/github.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [vxlan](<https://devfeed.tech/tags/vxlan.md>)

## AI overview

The article tests whether EVPN implementations can handle different transit VNI values within a shared VRF. In an Arista cEOS lab, three switches use unique per-switch VNIs, and the data plane creates one local VNI plus outgoing VNIs for remote peers. The article concludes that this capability can work but may consume a separate VLAN for each unique VNI and risk exhausting the 4096-VLAN limit on large deployments.

## Source excerpt

After reading the Layer-3-Only EVPN: Behind the Scenes blog post, one might come to an obvious conclusion: the per-VRF EVPN transit VNI must match across all PE devices forwarding traffic for that VRF. Interestingly, at least some EVPN implementations handle multiple VNIs per VRF without a hitch; I ran my tests in a lab where three switches used unique per-switch VNI for a common VRF. The rest of this blog post describes Arista cEOS behavior; please feel free to use the same netlab topology to run similar tests on other devices. Read more ...