The Resolve Configuration page contains information about the features and configurations that are not supported for migration, and the issues that must be fixed in the NSX-v environment before you can migrate.

After reviewing the blocking issues and warnings, you might need to change configurations in your NSX-v environment before you can migrate to NSX-T. If you change the NSX-v environment, you must restart the migration to pick up the new configuration. Review all migration feedback before you provide input to avoid duplication of work.

Note: For some NSX-v 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.

Procedure

  1. From the Resolve Configuration page, review the reported issues in the Blocking category to identify blocking issues that require changes to your NSX-v environment.
    Figure 1. Blocking Issues on the Resolve Configuration Page
    Figure shows blocking issues on the Resolve Configuration page.
    Some examples of blocking issues are:
    • Incorrect DRS configuration of Maintenance mode migration.
    • vMotion vmknics not configured on host for Maintenance mode migration.
    • Unsupported VXLAN UDP port.
  2. Review the warnings and issues reported in each category.
    Figure 2. Warnings and Categories of Issues on the Resolve Configuration Page

    Warnings and Categories of Issues on the Resolve Configuration Page.
    1. Click Warnings and review the information there.
    2. Review the reported issues in all categories.

What to do next

If you find blocking issues, fix them in the NSX-v environment before you can proceed with the migration. See Make Changes to the NSX Data Center for vSphere Environment.

If you did not find any blocking issues or other configurations that require a change in the NSX-v environment, you can proceed with the migration. See Provide Input for Configuration Issues.