NSX Overlay segments or Transport Zones are not visible during HCX Service Mesh creation
search cancel

NSX Overlay segments or Transport Zones are not visible during HCX Service Mesh creation

book

Article ID: 440424

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

While configuring an HCX Service Mesh or Compute Profile, you observe the following:

  • In the 'Select Network Containers' step for the destination site, only vSphere Distributed Switches (vDS) are available in the list.
  • Expected NSX Overlay Transport Zones or Segments are missing from the selection screen.
  • If you proceed with vDS selection, the Service Mesh fails later with a resource allocation error (e.g., VMware Distributed Virtual Switch is not supported for remote sites having NSX-T).

Environment

VMware HCX 

Cause

This visibility issue occurs when the HCX Manager is unable to sync the inventory from the registered NSX Manager. When HCX cannot communicate with NSX via the management API, it cannot discover the available Overlay Transport Zones or segments, leaving only the vCenter-discovered vDS resources visible in the UI.

Resolution

To restore resource visibility, you must re-establish the management connection between HCX and NSX:

  1. Verify Endpoint Status:

    • Log into the HCX Cloud Manager (Destination site).
    • Navigate to Administration > NSX Server.
    • Check if the status is Connected. If it shows 'Error' or 'Disconnected,' connectivity must be restored.
  2. Troubleshoot Management Connectivity:

    • Ensure that the NSX Manager is reachable from the HCX Manager on TCP port 443.
    • Verify that the service account credentials used for the NSX registration in HCX are still valid and have not been locked out.
  3. Refresh Inventory:

    • Once the status returns to Connected, wait 2–5 minutes for the background inventory sync to complete.
    • In the HCX UI, go to Infrastructure > Interconnect > Compute Profile and edit the profile.
    • The NSX Overlay Transport Zones should now be visible in the 'Network Containers' selection screen.

Additional Information

Service mesh fails to create when source and destination sites are configured to use distributed portgroups