Preparing Standalone Host Cluster Results in Failure

Preparing a standlone host cluster for NSX 3.2.2 results in failure.

Problem

In this scenario, there are two NSX deployments connected to same VMware vCenter in NSX 3.1.x. The VMware vCenter is registered with NSX-1 as compute manager and NSX-2 is using standalone cluster registered to the same VMware vCenter.

You upgrade NSX-1 to v3.2.2, then enable multi-NSX flag on the VMware vCenter. However, you do not upgrade the NSX-2 which remains on 3.1.x. Since NSX-1 is enabled with multi-NSX, the NSX Manager UI lists the standalone cluster of NSX-2 as an unprepared cluster.

If you try to prepare the standalone NSX-2 cluster from NSX-1, the standalone host goes into failure state.

Cause

NSX-2 hosts go into failure state because it is running NSX v3.1.x.

Solution

1. Log in to https://<vCenter-Server-IP>.
2. Migrate all VMs from that host to the other hosts using VMware vCenter.
3. Remove NSX from both managers using below API:
   DELETE https://<NSX Manager-IP>/api/v1/transport-nodes/<transportnode-id>?force=true&unprepare_host=false
4. Configure NSX on the desired NSX Manager.