HCX Network Profile creation fails with the "Unable to create Network Profile"
search cancel

HCX Network Profile creation fails with the "Unable to create Network Profile"

book

Article ID: 400898

calendar_today

Updated On:

Products

VMware HCX

Issue/Introduction

  • UI Error: The following message is displayed in the HCX Manager UI under Infrastructure > Interconnect > Network Profiles > Create Network Profile"Unable to create Network Profile"


  • The following error message is seen in the log file /common/logs/admin/app.log:
    <timestamp> UTC [https-jsse-nio-8443-exec-1, Ent: HybridityAdmin, , TxId: TxId: ########-####-####-####-##########] INFO  c.v.h.n.v.NetworkValidationHandler- Validating with vCenterInstanceUuid : ########-####-####-####-##########
    <timestamp> UTC [https-jsse-nio-8443-exec-1, Ent: HybridityAdmin, , TxId: TxId: ########-####-####-####-##########] ERROR o.a.c.c.C.[.[.[.[dispatcherServlet]- Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is java.lang.RuntimeException: NSX-T config was not found for VC uuid ########-####-####-####-##########] with root cause
    java.lang.RuntimeException: NSX-T config was not found for VC uuid ########-####-####-####-##########
    <timestamp> UTC [NSXService_SvcThread-428, Ent: HybridityAdmin, , TxId: ########-####-####-####-############] ERROR c.v.v.h.s.n.NsxTInventorySyncJob- Failed to update NsxT Inventory org.codehaus.jettison.json.JSONException: JSONObject["vcuuid"] not found.
  • The HCX Manager has NSX configured either Connector or a Cloud.

Cause

The issue is caused by a registration mismatch between the vCenter Server and the NSX Manager. This occurs in two primary scenarios:

  1. UUID Mismatch: The vCenter Server registered in the HCX Appliance Manager does not match the vCenter Server added as a "Compute Manager" within the NSX Manager.
  2. Unsupported Manager: The HCX Manager is incorrectly configured with an NSX Global Manager instead of a Local Manager.

Resolution

Ensure that HCX Manager is properly connected to a vCenter that is also connected to the NSX Manager.

  1. Checking vCenter in HCX (Port 9443)
    This interface (HCX Appliance Management) shows which vCenter is directly registered to the HCX Manager.
    1. Open a web browser and navigate to https://[HCX-Manager-IP-or-FQDN]:9443.
    2. Log in using the admin credentials.
    3. Navigate to the Configuration tab and select vCenter from the side menu.
    4. Note the following details:
      • vCenter Server: The FQDN or IP address of the registered vCenter.
      • Status: Ensure the status icon is green (Healthy).
  2. Checking vCenter in NSX Manager
    NSX must recognize the same vCenter as a "Compute Manager" for the integration to function
    1. Log in to the NSX Manager UI (port 443).
    2. Navigate to System > Fabric > Compute Managers
    3. Locate the entry that corresponds to your environment.
    4. Note the following details:
      • Name/FQDN: The address listed under the Compute Manager column.
      • Registration Status: Must show as Registered.
      • Connection Status: Must show as Up.
    5. Click on the Compute Manager name to view its ID/UUID.
  3. How to Compare and Verify
    A mismatch in these settings is the primary cause of the "Unable to create network profile" error.
    • Endpoint Match: The FQDN/IP address registered in HCX (Step 1) must be the exact same vCenter added as the Compute Manager in NSX (Step 2).
    • UUID Consistency: If you are using the same vCenter but getting errors, ensure that NSX is not pointing to an old or stale registration of that vCenter (e.g., following a vCenter reinstall or certificate replacement). The vcuuid seen in HCX logs must match the UUID of the active Compute Manager in NSX.
    • Local vs. Global: Ensure that the NSX Manager registered in HCX (9443 > Configuration > NSX) is a Local Manager. HCX does not support registration with an NSX Global Manager.

 

 

Additional Information