NSX-V Setup with one vCenter & 2 DC (Sites)

[RJ1312]

I want to setup NSX-V in one vCenter but with 2 DCs. I am deploying one NSX Manager(Primary), Controller cluster in Prod Site.

Do I have to go with Universal components (UTZ,ULS,UDLR,UDFW) which I guess will be used only in case of more than one vCenter or Global components ? Also these components will be on each site or stretched. Do we have any guide on how to setup this environment for POC ?

[Lalegre]

Hey @RJ1312,

You are having a misconception. For configuring a Universal schema you need at least two NSX Manager which means you need at least two vCenter as the connection between them is 1:1. 

Please take a look at the next documentation first: https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.cross-vcenter-insta...

[pradeepadapa_om]

Lalegre

is Correct, to have a Universal Transport Zone and communication 1:1 as you mentioned, you will need 2 vCenters and 2 NSX Managers and then make a Universal Transport Zone between them with an L3 Network between the 2 vCenters and NSX. Please mark his answer as the correct one.

Pradeep Adapa

[RJ1312]

So If I go with one vCenter with 2 Datacenters then I will have to go with one NSX Manager (1:1) with local transport zone ?

[pradeepadapa_om]

That is Correct. Even if you have 2 DC within the same vCenter, it will need to be in 1 transport zone. 

My question to you would be on why do you want to have 2 DC's within the same vCenter server? if you are looking for 2 DC's, I would suggest 2 vCenters. Typically we have only 1 DC per vCenter (DC is the Primary Object we create in a vCenter)

[Sreec]

You can certainly use single VC with 2DC setup . However for ease of workload mobility and failover scenarios we will need stretched storage so there is a dependency on underlying hardware with supported RTT. If you are implementing this for a production use case, you will have to consider availability and connectivity for all management components and that will be a good challenge to sort out . This is the key reason cross VC design is the best for A-A and A-P sites , less dependency on underlying network and storage as it is not mandatory to have stretched storage and management network.