NSX-T Multisite

[santunezlenovo]

Hello Guys

I have a question regarding NSX-T and mobility of VMs that are in two different places

I have two datacenters located in different zones and the vCenters are configured with VMWare ELM.

NSX-T is going to be integrated and the idea is that NSX-T is the owner of the VM traffic networks (they do not have physical nodes) and BGP will be enabled in both sites.

Each site has different network segments, vlans, but the VMs do see each other. Now, with the NSX-T integration, the customer wants each VM to maintain the same network segment if moved for any contingency and remain active-active sites.

My question is if you can help me understand what the requirements would be to be able to achieve what the client asks for, and if there is documentation about it, because I have found a lot of documentation, but they all have different ways of doing it, and they generally speak of active-passive.

Thanks

[grimsrue · Accepted solution]

I assume that each datacenter has its own NSX-T instance?

If so you can stretch your segments between the instances.

The Best Solution for this is NSX-T Federation. It will not only allow you to share the segments between DC-A and DC-B, but you can setup federation to allow the VM to route ingress/egress traffic out through DC-B instead of having to route all the way back to DC-A. It is a bit involved in the setup and configuration. I have not yet personally this up yet, but is on my task list. 

I have read somewhere that you should also be able to stretch the segments through a L2VPN. I have not done this. I have only use L2VPN to stretch a Physical "VLAN" into NSX-T.

Federation
https://rutgerblom.com/2020/06/30/configuring-nsx-t-3-0-stretched-networking/
https://vxplanet.com/2021/04/22/nsx-t-federation-part-2-stretched-a-s-tier-0-gateway-with-location-p...
vxplanet has a 7 part series on setting up federation all the way to site failures and network recovery