Import option greyed out with error in logs Site is not registered with this Global Manager NSX

Products

• VMware NSX

Issue/Introduction

When attempting to import a site into the NSX Global Manager, the operation fails and the import option appears grayed out. The system logs report the following error:

MP606117 - Site [Site_Name] is not registered with this Global Manager.

This issue occurs due to a name-binding mismatch between the Local Manager (Site Manager) and the Global Manager.

Environment

NSX 4.2.3 and earlier versions.

Cause

A name-binding discrepancy exists between the site name registered on the Global Manager (GM) and the site name already bound on the Local Manager's Site Manager (SM) component. This can occur when a site already has a name bound in SM from a prior onboarding to another component (for example, SSP) and is then onboarded to GM using a different name. In versions prior to 4.2.4, SM did not reject this mismatch, so the onboarding request was silently accepted instead of returning an error leaving GM's site record and SM's bound name out of sync. When GM later performs its onboarding version/feature check, it looks up the LM by the GM-side name; since that name doesn't match what's bound in SM, no LM is found and MP606117 is returned before the check can proceed.

Resolution

To resolve this mismatch, perform the following API calls on the Local Manager (LM):

1. Execute the unbind_name action: POST /api/v1/sites?action=unbind_name
2. Change the site name to match the Global Manager's Site ID: POST /api/v1/sites?action=change_name Body: {"site_id": "", "site_name": "<name>"}
3. Bind the name to confirm the update: POST /api/v1/sites?action=bind_name Body: {"site_name": "<name>"}
4. Proceed with the site re-onboarding process to the Global Manager.

Additional Information

If the issue persists, contact Broadcom Support for further assistance. For details on how to create or manage support cases, see Creating and Managing Broadcom Support Cases.