After you have reviewed the migration information and are ready to proceed with the migration, you can provide input for the reported configuration issues. The input you provide determines how the NSX-T environment is configured.
Multiple people can provide the input over multiple sessions. You can return to a submitted input and modify it. Depending on your configuration, you might run through the
Resolve Issues process multiple times, update your
NSX for vSphere environment as needed, and restart the migration.
Important: If you have changed the
NSX for vSphere environment for any reason since you last imported the configuration, you must restart the migration. For example, if you have connected a new VM to a logical switch, made a firewall rule change, or installed
NSX for vSphere on new hosts. See
Make Changes to the NSX for vSphere Environment for information on restarting the migration.
For some examples of configuration issues and the required input, including Edge node setup, see Example Configuration Issues.
Note: For some
NSX for vSphere features, there might be automatic configurations such as certificates present. If these configurations are for features that are not supported for the specific topology, these automatic configurations are flagged as issues that need to be skipped from migration. For example, in topologies that don't support L4-L7 services on Edge Services Gateways, the certificates present for VPN and DNS will raise issues to skip these configurations from migration.
Prerequisites
-
Verify that you have reviewed all issues and migration messages and are ready to continue with the migration.
-
Verify that you have addressed all blocking issues and other issues requiring a change to the NSX for vSphere.