HCX - Error "VIM NSX mapping not found" while loading Network Profile Wizard

Products

• VMware HCX

Issue/Introduction

This document is created as a reference for the HCX Network Profile wizard not displaying any content and how to recover that.


HCX Network Profile (NP) wizard will not load and below error notification could be seen in the UI and HCX Web-engine logs:

UI: <Error loading Network Proifles [object Object]>



Web.log:

2021-06-13 14:32:15.425 UTC [https-jsse-nio-127.0.0.1-8443-exec-7, 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 com.vmware.hybridity.networking.exception.InternalServerException: VIM NSX mapping not found.] with root cause
com.vmware.hybridity.networking.exception.InternalServerException: VIM NSX mapping not found.

Location of Web Engine log:

• HCX Manager : /common/log/admin/web.log

Environment

VMware HCX

Cause

HCX Network Profile (NP) wizard displays network backing from Distributed Switch (DVS), Standard Switch (VSS) & NSX backed logical switch (N-VDS or C-VDS).

IMPORTANT: NSX-T can be registered with multiple vCenters and fetches PGs from all vCenters part of its compute manager. Hence, it displays all PGs/backing in the HCX Network Profile wizard while selecting NSX backed logical switch (N-VDS or C-VDS).

If HCX manager is registered with vCenter (e.g: VC1) and user creates Network Profile using NSX-T backed segments corresponding to a different vCenter (e.g: VC2), HCX manager won't be able to locate & validate that segment with VC1, as a result the Network Profile UI becomes inaccessible post creation.

Resolution

For all greenfield deployments, the recommendation is to use correct vCenter backed segments/PGs for NSX logical switch during creation of network profile in the HCX NP wizard.

Workaround:
For an existing/brownfield deployment where VC backing is incorrectly set, please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.

Additional Information

Impact/Risks:

• The existing deployment will continue to be operational using different VC backed segment.
• Network Profile UI remain inaccessible as a result, no modifications or update in the IP resources are possible.
• If N-VDS has been migrated to C-VDS on NSX-T at src/dst, then Redeploy/Update workflow won't be serviced.
• Network Extension & Migration services will remain operational.