Unable to Import Local Manager to Global Manager Due to MultiTenancy Error

Products

• VMware NSX
• VMware Cloud Foundation

Issue/Introduction

During NSX Federation 9.1 Local Manager (LM) to Global Manager (GM) import operations, the import workflow fails.

Symptom / Error Message: Global Manager: Error - Unable to import due to these unsupported features MultiTenancy. Viewing the details of the error: Entity VPC_CONNECTIVITY_PROFILE at site <site-name> is not supported for configuration import on GM. Please delete entity VPC_CONNECTIVITY_PROFILE from the site <site-name> and try again.

In the NSX Local Manager UI at the affected site, the Default VPC Connectivity Profile is present, but the option to delete it is greyed out.

Environment

• VMware NSX 9.1 (NSX Federation)

• VMware Cloud Foundation 9.1

Cause

An active IP Block association tied to the Default VPC Connectivity Profile triggers a MultiTenancy feature validation check during the LM-to-GM import process, causing the Global Manager to reject the site import.

Resolution

 

• Log into the NSX Local Manager UI at the target site.

• Navigate to the Default VPC Connectivity Profile under VPCs > Profiles > VPC Connectivity Profile and edit its configuration.

• Remove the associated IP Block mapping in the Private - Transit Gateway IP Blocks column and save the changes.

• Retry the Local Manager import to the Global Manager.

• After the LM import completes successfully, re-edit the Default VPC Connectivity Profile, re-assign the IP Block association, and save the profile.

 

Additional Information

Related KBs:

• Import of Local Manager to Global Manager fails with "Unable to import due to these unsupported features: MultiTenancy" error.

• VPC IP Address Block Cannot Be Removed Because It Is Referenced by _DEFAULT-SNAT_TRANSLATED

Technical Document Reference:

• Importing Configurations from Local Manager