After migration has finished, some additional actions are required.

  • If you migrated from NSX-V 6.4.4, perform a reboot of all hosts that have migrated to NSX. The reboot must be done before you upgrade to a later version of NSX.

  • During migration, all transport nodes are added to a group called NSGroup with TransportNode for CPU Mem Threshold. This group ensures that the transport nodes have the correct CPU memory threshold settings in NSX. This group is required after migration has completed. If you need to remove a transport node from NSX after migration and you are running NSX 3.2.0, you must first remove the transport node from this group. If you are running NSX 3.2.1 or later, you do not need to remove the transport node from this group.

    To remove the transport node from the group, make sure you are in Manager mode and then select Inventory > Groups to remove the transport node from the NSGroup with TransportNode for CPU Mem Threshold group. For more information about Manager mode, see the topic "NSX Manager" in the NSX Administration Guide.

  • Verify that you have a valid backup and restore configuration. See "Backing Up and Restoring the NSX Manager" in the NSX Administration Guide.

Import Final Output Mapping File into vRealize Automation

Share the final output mapping file with the vRealize Automation administrator. The vRealize Automation administrator must import this output mapping file in step 4 of the vRealize Automation NSX-V to NSX migration plan.

The vRealize Automation administrator must complete the following steps in the migration plan:
  • Step 5: Migrate the NSX-V cloud account and its related objects to NSX.
  • Step 6: Test the migration results.
  • Step 7: Remove cloud accounts from maintenance mode and exit the migration plan.

For more information, see the vRealize documentation about migrating NSX-V to NSX.

Uninstall NSX-V After Migration

After the migration is verified and successful, uninstall your NSX-V environment. The process for uninstalling NSX-V after migration to NSX is different from the standard uninstall for NSX-V.

For more information, see Uninstalling NSX-V After Migration.

Finish Deploying the NSX Manager Cluster

You can run the migration coordinator tool with only one NSX Manager appliance deployed. Deploy two additional NSX Manager appliances before you use your NSX environment in production.

See the NSX Installation Guide for the following information:
  • NSX Manager Cluster Requirements
  • Deploy NSX Manager Nodes to Form a Cluster from UI
  • Configure a Virtual IP (VIP) Address for a Cluster