The following figure shows an example where multiple VxRail clusters are part of a customer-supplied vCenter environment. Each cluster is separate but managed centrally. Being managed from the same vCenter environment allows VMs to be easily migrated between vSAN environments for optimal workload balance and simplifies VxRail upgrades and expansion.
Figure 1. Customer-supplied vCenter environment with multiple VxRail clusters
Note: The customer-supplied vCenter Server deployment can be a physical server or a virtual server running on a vCenter Server appliance.
A customer-supplied vCenter Server solution is required when:
- VxRail 4.x is being added to an existing VMware platform, and a single management instance is desired.
- Multiple VxRail clusters are deployed using VxRail version 4.x, and a single management interface is desired.
- vCenter Server cannot be deployed on the 2-node cluster.
In versions earlier than VxRail 4.5.200, customer-supplied vCenter Server solution is required when:
- Stretched clusters are part of the solution.
- vSAN encryption is desired. When enabling Data at Rest Encryption (DARE) in a vSAN cluster, the Key Management Server (KMS) must be external to the vSAN cluster.
- VxRail Manager does not upgrade the customer-supplied vCenter Server. Before upgrading your VxRail software, see the release notes to verify the minimum required vCenter Server release number. You might have to upgrade the customer-supplied vCenter Server before the VxRail upgrade. See KB 000157682.
- RPQ is required if the customer-supplied vCenter Server is hosted on a VxRail cluster running versions earlier than 4.7.
The VxRail cluster shutdown function requires that you power off all VMs manually.
We highly recommend the vCenter be backed up to a remote site in case a vSAN failure occurs.
- You are responsible for the customer-supplied vCenter Server license.
- Log Insight is not activated when using a customer-supplied vCenter Server.
- Only one public IP address for the vCenter HA network is supported.