Author : Ben Corson
URL : http:////docs.vmware.com/en/VMware-Cloud-Foundation/4.0/vcf-40-introducing/GUID-6C75E7C7-AC9A-41A4-A...
Topic Name : Standard Architecture Model
Publication Name : Introducing VMware Cloud Foundation
Product/Version : VMware Cloud Foundation/4.0
Is it mandatory to have a dedicated NSX manager in each VI workload domain or can the Management domain NSX manager be shared with other VI workload domains?
The management domain requires a dedicated NSX Manager cluster.
The first VI workload domain that you create requires a new NSX Manager cluster (cannot share the management domain NSX Manager cluster).
Subsequent VI workload domains, can deploy a new NSX Manager cluster or share an NSX Manager cluster created for an existing VI workload domain.
See VMware Configuration Maximums for information about the maximum number of workload domains that can be managed by a single NSX Manager instance.
Do not share an NSX Manager cluster between workload domains catering to different use cases that would require different NSX-T Edge cluster specifications and configurations. For example: In order to share an NSX Manager cluster, the workload domains must use the same update manager. The workload domains must both use vSphere Lifecycle Manager (vLCM) or they must both use vSphere Update Manager (VUM).
Even though it is mentioned that there shall be separate NSX managers for Management and workload domain. There are many places where it doesn't indicate to use the same logic. The attached is from VMworld presentation where it talks about shared management and edge for medium size DC. Hence the question is that if it is mandatory to use dedicated NSX manager as well as edge node for Management domain and VI Workload domain or can it be shared as given below if the requirements are met for LCM, VUM etc. Also will it be correct to assume that with VCF the only possibility is to have dedicated NSX Managers for management domain and VI workload domain?
If this slide your showing is from VMworld then it is probably from VCF 3.9.x the NSX Architecture has changed when we released VCF 4.0. The current documentation reference above is correct.