In the VI Configuration wizard, you specify the storage, name, compute, and NSX platform details for the VI workload domain. Based on the selected storage, you provide vSAN parameters or NFS share details. You then select the hosts and licenses for the workload domain and start the creation workflow.

The workflow automatically:
  • Deploys an extra vCenter Server Appliance for the new workload domain within the management domain.

    By using a separate vCenter Server instance per workload domain, software updates can be applied without impacting other workload domains. It also allows for each workload domain to have additional isolation as needed.

  • Connects the specified ESXi servers to this vCenter Server instance and groups them into a cluster. Each host is configured with the port groups applicable for the workload domain.
  • Configures networking on each host.
  • Configures vSAN or NFS storage on the ESXi hosts.
  • Deploys an NSX Manager in the management domain and three NSX controllers on the ESXi datastore for each NSX for vSphere workload domain . The workflow also configures an anti-affinity rule between the controller VMs to prevent them from being on the same host for High Availability.
  • Deploys a cluster of three NSX-T Managers in the management domain for the first NSX-T VI workload domain. The workflow also configures an anti-affinity rule between the NSX Manager VMs to prevent them from being on the same host for High Availability. All subsequent NSX-T workload domains share this NSX-T Manager cluster.

    For an NSX-T workload domain, NSX Edges are needed to enable overlay VI networks and public networks for the north-south traffic. NSX Edges are not deployed automatically for an NSX-T VI workload domain. You can deploy them manually after the VI workload domain is created. Subsequent NSX-T VI workload domains share the NSX-T Edges deployed for the first workload domain.

  • NSX Managers deployed as part of a VI workload domain are configured to periodically get backed up to an SFTP server. By default, these backups are written to an SFTP server built into SDDC Manager, but you can register an external SFTP server for better protection against failures. See "Configure an External SFTP Server for File-Based Backups" in the VMware Cloud Foundation Operations and Administration Guide. SDDC Manager uses either the built-in or external SFTP server with all currently deployed NSX Managers and when deploying additional NSX Managers.
  • Licenses and integrates the deployed components with the appropriate pieces in the VMware Cloud Foundation software stack.
Note: Currently, the NSX-V to NSX-T migration is not supported in the VMware Cloud Foundation environments.