HCX Service Mesh fails with "Failed to check if custom fleet network profile feature is supported"

Products

• VMware HCX

Issue/Introduction

• VMware HCX. When updating or creating a Service Mesh, the process fails at the resource allocation phase.

• Symptoms:

  • Error: Retrieving Network Resources Requirements failed.Interconnect Service Workflow AllocateResourcesForInterconnectAppliance failed.

  • Error: Failed to check if custom fleet network profile feature is supported at both HSM endpoints for service mesh-UUID Cause: null

  • Retrieving Network Resources Requirements failed.Interconnect Service Workflow AllocateResourcesForInterconnectAppliance failed. Error: Failed to check if custom fleet network profile feature is supported at both HSM endpoints for service mesh servicemesh-################. Cause: null, Failed to check if custom fleet network profile feature is supported at both HSM endpoints for service mesh servicemesh-################. Cause: null

                 

• • Site Pairing is successful, but Interconnect appliances fail to deploy.

Environment

HCX 4.11.4

Cause

The WAN Optimization, Network Extension, V2T Migration services require an NSX overlay transport zone to function properly. But here a VDS-backed network was selected in the network containers at the HCX Cloud (destination) site causing the Service Mesh to fail

Resolution

 

1. Open the HCX UI and navigate to Interconnect > Service Mesh.

2. Select the affected Service Mesh and click Edit.

3. Navigate to the network selection screens.

4. On the Cloud/Destination side, ensure that only NSX Overlay Transport Zones or segments are selected.

5. Deselect any VDS backed networks.

6. Click Finish/Update to re-trigger the resource allocation workflow.

 

Additional Information

Refer to Broadcom KB 412764 regarding transport zone requirements for Service Mesh.