Mapping of virtual routing and forwarding (VRF) instances using ethernet virtual private network (EVPN) instances

1. A method comprising:

executing, with a spine network device of a plurality of network devices of a leaf and spine network, a primary Ethernet Virtual Private Network (EVPN) instance (EVI) to provide an EVPN to a plurality of leaf network devices of the plurality of network devices of the leaf and spine network, each of the plurality of leaf network devices executing a secondary EVI of a plurality of secondary EVIs to provide a plurality of network virtualization overlays to tenants of the plurality of leaf network devices,

wherein the primary EVI is associated with a primary Virtual Routing and Forwarding (VRF) instance and a primary Virtual Network Identifier (VNI), and

wherein each secondary EVI of the plurality of secondary EVIs is associated with a respective secondary VRF instance of a plurality of secondary VRF instances and a respective secondary VNI of a plurality of secondary VNIs,

defining, by the spine network device, a pseudo-mesh group mapping at least one logical interface labeled with the primary VNI to at least one logical interface labeled with a secondary VNI of a secondary EVI of the plurality of secondary EVIs;

defining, by the spine network device, a mesh group mapping the at least one logical interface labeled with the secondary VNI to at least one physical interface of a leaf network device of the plurality of leaf network devices executing the secondary EVI;

defining, by the spine network device and based on the pseudo-mesh group and the mesh group, one or more mappings between routes within the primary VRF instance and routes within each secondary VRF instance of the plurality of secondary VRF instances; and

translating, by the spine network device and based on the one or more mappings, network traffic between the primary EVI and a secondary EVI of the plurality of secondary EVIs.

2. The method of claim 1 , wherein translating network traffic between the primary EVI and the secondary EVI of the plurality of secondary EVIs comprises:

receiving, by the spine network device, first Broadcast, Unknown unicast, and Multicast (BUM) traffic specifying the at least one logical interface labeled with the primary VNI;

translating, by the spine network device and based on the pseudo-mesh group, the first BUM traffic specifying the at least one logical interface labeled with the primary VNI into second BUM traffic specifying the at least one logical interface labeled with the secondary VNI;

translating, by the spine network device and based on the mesh group, the second BUM traffic specifying the at least one logical interface labeled with the secondary VNI into third BUM traffic specifying the at least one physical interface of the leaf network device of the plurality of leaf network devices executing the secondary EVI; and

forwarding, by the spine network device, the third BUM traffic to the at least one physical interface the leaf network device of the plurality of leaf network devices executing the secondary EVI.

3. The method of claim 1 , wherein translating the network traffic between the primary EVI and the secondary EVI of the plurality of secondary EVIs comprises:

receiving, by the spine network device and from a leaf network device of the plurality of leaf network devices executing the secondary EVI, first network traffic specifying the secondary VNI associated with the secondary EVI;

translating, by the spine network device and based on the one or more mappings, the first network traffic into second network traffic specifying the primary VNI associated with the primary EVI;

forwarding, by the spine network device and to another network device within the primary EVI, the second network traffic specifying the primary VNI.

4. The method of claim 1 , wherein translating the network traffic between the primary EVI and the secondary EVI of the plurality of secondary EVIs comprises:

receiving, by the spine network device and from another network device within the primary EVI, first network traffic specifying the primary VNI associated with the primary EVI;

translating, by the spine network device and based on the one or more mappings, the first network traffic into second network traffic specifying the secondary VNI associated with the secondary EVI; and

forwarding, by the spine network device and to a leaf network device of the plurality of leaf network devices executing the secondary EVI, the second network traffic specifying the secondary VNI.

5. The method of claim 1 ,

wherein the spine network device comprises a first spine network device, and

wherein translating the network traffic between the primary EVI and the secondary EVI of the plurality of secondary EVIs comprises:

receiving, by the first spine network device and from a first leaf network device of the plurality of leaf network devices executing the secondary EVI, first network traffic specifying the secondary VNI associated with the secondary EVI;

translating, by the first spine network device and based on the one or more mappings, the first network traffic into second network traffic specifying the primary VNI associated with the primary EVI; and

forwarding, by the first spine network device, via an Integrated Routing and Bridging (IRB) interface, and to a second spine network device, the second network traffic specifying the primary VNI, wherein the second spine network device is configured to:

translate the second network traffic into the first network traffic specifying the secondary VNI associated with the secondary EVI; and

forward the first network traffic to a second leaf network device of the plurality of leaf network devices executing the secondary EVI.

6. The method of claim 1 , wherein the plurality of secondary EVIs comprises a plurality of Virtual eXtensible Local Area Network (VXLAN) instances.

7. The method of claim 1 , wherein the plurality of secondary EVIs comprises a plurality of Virtual Local Area Network (VLAN) instances.

8. The method of claim 1 ,

wherein each secondary EVI of the plurality of secondary EVIs is provisioned to a different data center of a plurality of geographically-separate data centers, and

wherein the spine network device is configured to operate as a Data Center Interconnect (DCI) for the plurality of data centers.

9. The method of claim 1 , wherein the network traffic comprises an EVPN Type-1 route specifying an Ethernet autodiscovery route for the secondary EVI of the plurality of secondary EVIs.

10. The method of claim 1 , wherein the network traffic comprises an EVPN Type-2 route specifying a Media Access Control (MAC) with Internet Protocol (IP) advertisement route for the secondary EVI of the plurality of secondary EVIs.

11. The method of claim 1 , wherein the network traffic comprises an EVPN Type-3 route specifying an inclusive multicast (IM) Ethernet tag route for the secondary EVI of the plurality of secondary EVIs.

12. The method of claim 1 , wherein the network traffic comprises an EVPN Type-5 route specifying an Internet Protocol (IP) prefix route for the secondary EVI of the plurality of secondary EVIs.

13. The method of claim 1 , wherein the network traffic comprises network traffic associated with a network service provided by the secondary EVI of the plurality of secondary EVIs.

14. A spine network device of a plurality of network devices of a leaf and spine network, the spine network device configured to:

execute a primary Ethernet Virtual Private Network (EVPN) instance (EVI) to provide an EVPN to a plurality of leaf network devices of the plurality of network devices of the leaf and spine network, each of the plurality of leaf network devices executing a secondary EVI of a plurality of secondary EVIs to provide a plurality of network virtualization overlays to tenants of the plurality of leaf network devices,

wherein the primary EVI is associated with a primary Virtual Routing and Forwarding (VRF) instance and a primary Virtual Network Identifier (VNI), and

wherein each secondary EVI of the plurality of secondary EVIs is associated with a respective secondary VRF instance of a plurality of secondary VRF instances and a respective secondary VNI of a plurality of secondary VNIs,

define a pseudo-mesh group mapping at least one logical interface labeled with the primary VNI to at least one logical interface labeled with a secondary VNI of a secondary EVI of the plurality of secondary EVIs;

define a mesh group mapping the at least one logical interface labeled with the secondary VNI to at least one physical interface of a leaf network device of the plurality of leaf network devices executing the secondary EVI;

define, based on the pseudo-mesh group and the mesh group, one or more mappings between routes within the primary VRF instance and routes within each secondary VRF instance of the plurality of secondary VRF instances; and

translate, based on the one or more mappings, network traffic between the primary EVI and a secondary EVI of the plurality of secondary EVIs.

15. The spine network device of claim 14 , wherein to translate network traffic between the primary EVI and the secondary EVI of the plurality of secondary EVIs, the spine network device is configured to:

receive first Broadcast, Unknown unicast, and Multicast (BUM) traffic specifying the at least one logical interface labeled with the primary VNI;

translate, based on the pseudo-mesh group, the first BUM traffic specifying the at least one logical interface labeled with the primary VNI into second BUM traffic specifying the at least one logical interface labeled with the secondary VNI;

translate, based on the mesh group, the second BUM traffic specifying the at least one logical interface labeled with the secondary VNI into third BUM traffic specifying the at least one physical interface of the leaf network device of the plurality of leaf network devices executing the secondary EVI; and

forward the third BUM traffic to the at least one physical interface the leaf network device of the plurality of leaf network devices executing the secondary EVI.

16. The spine network device of claim 13 , wherein to translate network traffic between the primary EVI and the secondary EVI of the plurality of secondary EVIs, the spine network device is configured to:

receive, from a leaf network device of the plurality of leaf network devices executing the secondary EVI, first network traffic specifying the secondary VNI associated with the secondary EV;

translate, based on the one or more mappings, the first network traffic into second network traffic specifying the primary VNI associated with the primary EVI;

forward, to another network device within the primary EVI, the second network traffic specifying the primary VNI.

17. The spine network device of claim 14 , wherein to translate network traffic between the primary EVI and the secondary EVI of the plurality of secondary EVIs, the spine network device is configured to:

receive, from another network device within the primary EVI, first network traffic specifying the primary VNI associated with the primary EVI;

translate, based on the one or more mappings, the first network traffic into second network traffic specifying the secondary VNI associated with the secondary EVI; and

forward, to a leaf network device of the plurality of leaf network devices executing the secondary EVI, the second network traffic specifying the secondary VNI.

18. A non-transitory, computer-readable medium comprising instructions that, when executed, are configured to cause processing circuitry of a spine network device of a plurality of network devices of a leaf and spine network to:

execute a primary Ethernet Virtual Private Network (EVPN) instance (EVI) to provide an EVPN to a plurality of leaf network devices of the plurality of network devices of the leaf and spine network, each of the plurality of leaf network devices executing a secondary EVI of a plurality of secondary EVIs to provide a plurality of network virtualization overlays to tenants of the plurality of leaf network devices,

wherein the primary EVI is associated with a primary Virtual Routing and Forwarding (VRF) instance and a primary Virtual Network Identifier (VNI), and

wherein each secondary EVI of the plurality of secondary EVIs is associated with a respective secondary VRF instance of a plurality of secondary VRF instances and a respective secondary VNI of a plurality of secondary VNIs,

define a pseudo-mesh group mapping at least one logical interface labeled with the primary VNI to at least one logical interface labeled with a secondary VNI of a secondary EVI of the plurality of secondary EVIs;

define a mesh group mapping the at least one logical interface labeled with the secondary VNI to at least one physical interface of a leaf network device of the plurality of leaf network devices executing the secondary EVI;

define, based on the pseudo-mesh group and the mesh group, one or more mappings between routes within the primary VRF instance and routes within each secondary VRF instance of the plurality of secondary VRF instances; and

translate, based on the one or more mappings, network traffic between the primary EVI and a secondary EVI of the plurality of secondary EVIs.