After you have resolved all configuration issues, you can migrate the configuration. When the configuration is migrated, configuration changes are made in the NSX environment to replicate the NSX-V configuration.

If needed, you can roll back the configuration that is migrated. Rolling back does the following:
  • Remove the migrated configuration from NSX.
  • Roll back all the resolved issues in the previous step.

See Roll Back a Migration for more information.

Prerequisites

Verify that you have completed the Resolve Configuration step.

Procedure

  1. From the Migrate Configuration page, click Start.
    The NSX-V configuration is migrated to NSX.
  2. Verify that all the migrated configurations are displayed in your NSX environment.

    You can verify the migrated configurations either in the NSX NSX Manager interface or by running the NSX APIs.

    Important:
    • During the Migrate Configuration step, Security Tags from NSX-V are not migrated to NSX. Therefore, the Security Tag-based migrated dynamic Groups and Groups with static memberships in NSX are empty after this step is finished. The reason is that in NSX-V, a Security Tag is an object, whereas in NSX, a tag is an attribute of a VM. The tags are applied to the workload VMs only after the workloads are migrated to NSX during the Migrate Hosts step.
    • When the configuration is migrated to NSX, the configuration changes are made in the NSX NSX Manager database, but it might take some time for the configuration to take effect. You must verify that all expected NSX-V configurations appear on the NSX Manager interface or API in NSX before you proceed to the Migrate Edges step. For example, firewall configuration, logical switches, transport zones.
    Caution: This caution note applies only when you are using an NSX for vShield Endpoint license in your virtualized environment. This license is included in all vSphere editions. It enables you to use NSX-V to offload only anti-virus processing (Guest Introspection service) on VMs to service appliances that are provided by VMware partners.

    In a Guest Introspection service migration, Security Groups with only dynamic VM membership criteria are supported. If tags-based dynamic Security Groups are used in your NSX-V environment, the Security Tags are not migrated to NSX. As no host migration is involved, the migrated dynamic Groups in NSX are empty. After the Migrate Configuration step is finished, you must manually create the equivalent tags in NSX, and attach them to the VMs that require an endpoint protection.

Results

After this procedure is completed, the fp-eth0, fp-eth1, and fp-eth2 interfaces on the Edge nodes are set to "administratively down". Do not reboot the Edge nodes. Otherwise the fp interfaces will come up and inadvertently advertise the NSX networks.