Maintain private cloud configuration health

This page describes how Cloud Administrators can use Google Cloud VMware Engine to regularly monitor their configuration to ensure it remains ready for future upgrades. To help you maintain private cloud stability, Google Cloud VMware Engine performs regular health checks for configuration drift, logs details in Cloud Logging, and notifies you of any critical issues in email summaries. This approach helps you identify and resolve configuration drift in your private cloud.

Caution: When Google Cloud VMware Engine detects configuration drift, remediate it immediately. Failure to act can result in repetitive notifications and might leave your environment in an unsupported state.

Configuration health checks

VMware Engine performs the following checks to ensure your environment remains in a supported and efficient state.

NSX-T Tier-0 gateway name

To enable automated lifecycle management and updates, ensure the management NSX-T Tier-0 gateway is named exactly Provider-LR. You can verify the gateway name in NSX-T Manager by navigating to Networking > Tier-0 Gateways.

Impact

If you rename this gateway to a name other than Provider-LR, you might experience failed upgrades or delays in scheduled maintenance.

Gateway name remediation

1. Access NSX-T Manager.
2. Navigate to Networking > Tier-0 Gateways.
3. Identify the provider gateway and click Edit.
4. Change the name of the gateway to Provider-LR and save the changes.

NSX-T Edge high-availability mode

To maintain predictable throughput and support stateful services, ensure your NSX-T Tier-0 gateway uses the Active-Standby configuration.

Impact

If you use other modes (such as Active-Active), you may encounter traffic disruptions during failovers or inconsistent performance if a node fails.

High-availability mode remediation

1. Access NSX-T Manager.
2. Navigate to Networking > Tier-0 Gateways.
3. Locate the identified gateway and click Edit.
4. Set the High Availability Mode to Active-Standby and save.

vSAN storage policy

To protect your data from physical host failures, ensure your virtual machines (VMs) use a storage policy with Failures to Tolerate (FTT) set to at least 1. An FTT of 0 means you have no data redundancy.

Impact

If a physical host fails and your FTT is 0, you will experience permanent data loss or corruption. Maintenance operations also take longer without a redundant storage policy.

vSAN storage policy remediation

1. Access vSphere Client.
2. Locate the affected VM and select Edit Settings.
3. Identify the specific disks (for example, Hard disk 1).
4. Change the VM storage policy to a resilient policy such as FTT 1 or higher.

Extension and interoperability checks

The following checks and recommended actions ensure your extensions and paired on-premises environments are compatible with upcoming VMware Engine updates.

Service check	Benefit	Action
Zerto version	Enables system-wide upgrades and prevents disaster recovery failures.	In vCenter, go to Administration > Solutions > Client Plug-ins to upgrade the Zerto plugin.
HCX local version	Maintains compatibility with infrastructure updates and migration features.	Install latest updates in HCX Cloud Manager UI > System Updates.
HCX remote version	Prevents Network Extension failures during site-pairing upgrades.	Upgrade on-premises HCX Connector by using its management UI.
Remote vCenter version	Ensures API compatibility and inventory discovery during migrations.	Upgrade on-premises vCenter to meet the minimum required version.