How to migrate NSX-T to a new vCenter

Products

• VMware NSX
• VMware vCenter Server

Issue/Introduction

• A new vCenter is being deployed to replace the current vCenter.
• This may be for an upgrade or to separate working environments.
• The current NSX deployment needs to move as-is to the new vCenter.

Environment

• VMware vCenter Server
• VMware NSX

Cause

When migrating NSX Manager nodes and Edge nodes to a new vCenter, a simple vMotion or re-registration of NSX components can cause issues.

Nodes can still use the same configuration, but they need to be redeployed in the new vCenter in such a way that the current configuration isn't lost.

Resolution

Migrate NSX Manager nodes

To migrate NSX Manager nodes, there are two potential ways depending on how the manager was deployed.  When originally deploying NSX, one manager is usually deployed via OVA, then the additional managers are deployed from the UI.  In many cases, the original manager may be deleted and then deployed again from the cluster now that it contains the additional managers.

For migration of NSX managers, please see KB 395943 - How to move an NSX Manager appliance from one vCenter to another. 

 

Migrate NSX Edge nodes

Edge nodes must be redeployed into the new environment.  This is due to vCenter specific information in the deployment configuration. 

To migrate NSX Edge nodes, please refer to KB 417052 - How to move an NSX Edge appliance from one vCenter to another.

If you have already moved your NSX Edge nodes and are receiving an Alarm, please see NSX Edge Placement Mismatch Alarm.