NSX Manager Nodes Deployed to Incorrect Management Portgroup During VCF Import

Products

• VMware Cloud Foundation
• VCF Operations

Issue/Introduction

During a VMware Cloud Foundation (VCF) import of an existing vCenter Server, the automation incorrectly deploys NSX Manager nodes onto the ESXi management portgroup instead of the target VM management portgroup.
This causes the NSX Manager distribution to fail during bring-up.

Additionally, subsequent upgrade pre-checks fail with an error indicating multiple vCenter Service Appliance VMs cannot share the same hostname.
Error example below:

Multiple vCenter Service Appliance VMs cannot share the same hostname 
Remove outdated vCenter Server Appliance (VCSA) virtual machines. First ensure they are no longer in use, then power them off and finally remove them from the vSphere inventory.

 

 

Environment

VMware Cloud Foundation 9.1.0
vCenter Server 9.1.0
VMware NSX 9.1.0

Cause

The VCF import discovery workflow incorrectly relies on the hostname without checking the virtual machine power state, falsely identifying a stale, powered-off vCenter VM as the active target.

Resolution

1. Ensure the outdated, powered-off vCenter Server virtual machine is no longer in use.
2. Remove the stale vCenter Server virtual machine from the vSphere inventory to eliminate the hostname conflict.
3. Move the active vCenter Server virtual machine back into the VCF Management Cluster.
4. Re-run the environment pre-checks and proceed with the update or upgrade workflows.