Interconnect datacenter based on NSX-T

[dansty19]

How can I connect 2 datacenters based on NSX-T through the T0 with evpn or l2vc, so that the traffic between virtual machines hosted in each datacenter in overlay segments uses this connection. Each overlay segment in each datacenter is connected to its respective T1 and they are different layer 3 networks. The idea is not to extend the layer-level overlay network from one datacenter to the other, but to communicate at the layer 3 level based on routing.

[Sreec]

I hope you have a DC gateway that supports EVPN on both the sites? You may please review the below links to know what works best for your use case.  https://blogs.vmware.com/networkvirtualization/2022/03/multi-tenancy-datacenter-with-nsx-evpn.html/ 

https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-D8186088-6C8F-4553-B859-... 

https://nsx.techzone.vmware.com/?share=video2590&title=demo-5-multi-tenancy-with-nsx-evpn . You can also have EVPN configuration limited to underlay and advertise NSX routes between the DC(Termination points will be DC gateway in this case)

[dansty19]

We have Cisco APIC based, but we want to build evpn between local and remote DC without the participation of the APIC, so that it only fulfills the function of interconnecting the datacenters at the layer 3 level as an underlay layer, that is, raising the local NSX-T T0 vxlan and remote NSX-T T0.

For example, what is reported in this blog https://nsx.ninja/index.php/Hub_and_Spoke_Layer_2_VPNs_between_multiple_NSX-T_enabled_sites, as a hub and spoke solution, but they do it with l2vpn, if this solution is used, what limitations does it have?, because we have the T0 set to active/active with bgp-ECMP.

[Sreec]

We have Cisco APIC based, but we want to build evpn between local and remote DC without the participation of the APIC, so that it only fulfills the function of interconnecting the datacenters at the layer 3 level as an underlay layer, that is, raising the local NSX-T T0 vxlan and remote NSX-T T0.

Yes, that should, keeping Fabric in L2 mode and doing EVPN between T0 in different DC(Ideally it is done with DC gateway) 

For example, what is reported in this blog https://nsx.ninja/index.php/Hub_and_Spoke_Layer_2_VPNs_between_multiple_NSX-T_enabled_sites, as a hub and spoke solution, but they do it with l2vpn, if this solution is used, what limitations does it have?, because we have the T0 set to active/active with bgp-ECMP.

Most of the limitations are updated in https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-86C8D6BB-F185-46DC-828C-...  and config max portal https://configmax.esp.vmware.com/guest?vmwareproduct=NSX-T%20Data%20Center&release=NSX-T%20Data%20Ce...