The KB explains how to migrate NSX Controllers with/without shared storage and what to check before & after migration.
Source and Destination clusters have shared storage:
- Verify on the Installation > Management page all three controllers are in a Connected state.
- Verify the Controller cluster health status per pre-migration checklist.
- vMotion the first Controller to the new cluster.
- Verify Ping connectivity between the three Controllers.
- Verify on the Installation > Management page that the migrated Controller is now in a Connected state.
- On the Installation > Management page click on the controller node and verify Cluster/Datastore/Host reflect the new location of the Controller.
- Verify the Cluster Status on each Controllers using the Post-migration checklist.
- Repeat the Migrations Steps for the remaining Controllers.
Note: The Controller vMotion will result in a brief disconnect and reconnect to the majority, this can be observed by running “show control-cluster history” following vmotion. The Controller master node will change following the migration.
The KB explains that you can vMotion the NSX controllers without redeploying it.
After the migration, you might also want to enable VM auto startup/shutdown as explained in the Deploy NSX Controller Cluster doc
If the controller node VMs are later migrated to other hosts, the new hosts might not have automatic VM startup/shutdown enabled. For this reason, VMware recommends that you check all hosts in the cluster to make sure that automatic VM startup/shutdown is enabled. See http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc%2FGUID-5FE08AC7-4486-438E-AF88-80D6…Bayu Wibowo | vExpert NSX, VCIX6-DCV/NV, Cisco Champion, AWS-SAA1 person found this helpful
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://nz.linkedin.com/in/bayupw | twitter @bayupw