HCX Service Mesh Upgrade or Deployment Fails with OvfNetworkMappingNotSupported Error

Products

• VMware HCX
• VMware Cloud on AWS

Issue/Introduction

• An upgrade or redeployment workflow on HCX Service Mesh fleet appliances fails.
• The following error is found in the HCX App Engine logs (/common/log/admin/app.log):

  com.vmware.vim.binding.vim.fault.OvfNetworkMappingNotSupported:The provided network mapping between OVF networks and the system network is not supported by any host.. Cause: null.

Environment

• VMware HCX
• VMware Cloud on AWS

Cause

This error occurs due to an inconsistency between the HCX network mapping and the actual environment configuration. Common causes include:

• Renaming or migrating vCenter port groups or Distributed Switches (vDS) after the HCX Compute Profile was established.
• N-VDS to C-VDS migration at the NSX-T level, leading to network backing discrepancies (Opaque Network vs. DVPG).
• Stale database references in the HCX configuration.

Resolution

Follow these steps sequentially to resolve the issue.

1. Verify Environment Configuration: Ensure all clusters/ESXi hosts in the HCX Compute Profile have proper network backing association (DVPG) at the vCenter level for all segments (Uplink, Management, vSR, vMotion) specified in the HCX Network Profile.
2. Perform Service Mesh Resync: From the on-prem/connector side, trigger a "Resync" on the affected Service Mesh. This forces the HCX Manager to re-query the vCenter inventory and update the network MOID mappings.
3. Attempt Appliance Redeploy: Once Resync is successful, retry the appliance upgrade/redeploy.
4. Deploy New Service Mesh (If Above Fails): If Resync fails or does not resolve the issue, and database remediation is too high-risk, deploy a new service mesh and migrate the networks.