Multiple VCF instances with NSX-T Multisite configuration

[BassamZantout]

Hey guys,

I have a scenario where I have 2-sites and a VCF 4.x deployment per site where the aim is to use NSX-T 3.1 with Federation once its part of the VCF 4.x BOM in its next release. The network is L2 stretched but the storage/clusters are not, and cannot be stretched due to network latency.

• Due to some limitations in NSX-T 3.1 Federation, it seems that it will not be possible to implement NSX-T Federation and hence NSX-T multisite is the option moving forward.
• Since every VCF deployment mandates the installation of an NSX-T Manager instance, and since NSX-T Multisite is configured with a single NSX-T Manager instance across two sites, then does VCF allow for NSX-T Multisite configuration in such a scenario?

Had this been a VVD SDDC (ESXi + vSAN + NSX-T) deployment without VCF then it would have been possible, hence the reason for validating this with VCF.

Thanks

B

[shank89]

Hi,

Yes it is possible to run multisite in VCF 4.x, which deployment method are you thinking of configuring?

You will have at minimum an NSX-T manager cluster for the management domain and one for the first workload domain.  These are deployed as 3 node clusters.  Where have you seen that multisite requires a single node or did you mean a single NSX-T Manager cluster instance?  This link doesn't explicitly state this but it does refer to the manger cluster; https://docs.vmware.com/en/VMware-NSX-T-Data-Center/2.4/administration/GUID-5D7E3D43-6497-4273-99C1-....

What requirements are you trying to satisfy?

[BassamZantout]

Hey Shashank,

VCF 4.x with NSX-T 3.1 in federation is not possible. Given what i've described, the question is whether or not NSX-T 3.1 in Multisite is supported knowing that these are two VCF instances whereby an NSX-T manager has to be deployed per site.

In NSX-T multisite configuration there's a single NSX-T Manager that is taking care of two sites. Hence the question is, can I utilize a single NSX-T Manager instance in one of the VCF deployments for both sites and not utilize the NSX-T Manager instances in the other site. In case of DR i would restore configuration to the unused NSX-T manager instance in the other site.

B

[shank89]

hmmm, what about your edge nodes?

You would have to rebuild them or some how DR them across and then re-register them?  This would raise numerous concerns as well.  It doesn't seem like a very good idea.  In general I have seen multisite used quite a bit, however the it is structured as a multi-az management domain with local WLD's in either site.  

The WLD's can also be stretched, but I generally try to steer people away from stretching everything.

[scott28tt]

@BassamZantout 

Moderator: Please do not create multiple threads for the same topic/issue/question. Your duplicate has been archived.

[BassamZantout · Accepted solution]

After investigating this, it seems VCF with NSX-T multi site architecture is not possible. 

Reason is, every VCF instance needs to own its NSX-T manager instance hence it is not possible to have 2x VCF instances with a single NSX-T manager instance. NSX-T Federation is therefore the only option for deploying VCF in Active/Passive multi region setups.

In the event that NSX-T Federation is not an option, then revert back to VVD with NSX-T multi site.

[shank89]

If it is a requirement to have multiple VCF instances, then yes in this case multisite will not work.  A lot of clients in this situation tend to go with a stretched / multi-az management zone and/or stretched workload (which is generally less common that I have seen) with some cross region support.

My mistake I originally misread your question, but glad you came up with the answer!