The clusters in the NSX-V environment are displayed on the Migrate Hosts page. The clusters are arranged into migration groups, each migration group contains one vSphere host cluster. There are several settings which control how the host migration is performed.

Screenshot of the host migration plan screen

  • Click Settings to change the global settings: Pause Between Groups and Migration Order Across Groups.
  • Select a single host group (cluster) and use the arrows to move it up or down in the migration sequence.
  • Select one or more host groups (clusters) and click Actions to change these host groups settings: Migration Order Within Groups, Migration State, and Migration Mode.

Pause Between Groups

When migrating multiple host groups, you can pause the migration between groups by enabling the Pause Between Groups setting. After a group is migrated, you must click Continue to migrate the next host group. This setting is disabled by default. You can enable it if you want to verify the status of the applications running on each cluster before proceeding to the next one.

Serial or Parallel Migration Order

You can specify whether migration happens in a serial or parallel order. There are two ordering settings:

  • Migration Order Across Groups is a global setting that applies to all host groups.

    • Serial: One host group (cluster) at a time is migrated.
    • Parallel: Up to five host groups at a time are migrated. After those five host groups are migrated, the next batch of up to five host groups are migrated.
      Important:

      If you are migrating from NSX-V 6.4.4, 6.4.5, or 6.4.6, and your environment uses vSphere Distributed Switch 7.0 or later, do not select parallel migration order across groups.

      If you are migrating from NSX-V 6.4.8 or later, and your environment uses vSphere Distributed Switch 7.0 or later, parallel migration order across groups is supported.

  • Migration Order Within Groups is a host group (cluster) specific setting, so can be configured separately on each host group.

    • Serial: One host within the host group (cluster) at a time is migrated.
    • Parallel: Up to five hosts within the host group are migrated at a time. After those hosts are migrated, the next batch of up to five hosts are migrated.
      Important: Do not select parallel migration order within groups for a cluster if you plan to use Maintenance migration mode for that cluster.

By default, both settings are set to Serial. Together, the settings determine how many hosts are migrated at a time.

Table 1. Effects of Migration Settings on Number of Hosts Attempting Migration Simultaneously
Migration Order Across Groups (Clusters) Migration Order Within Groups (Clusters) Maximum Number of Hosts Attempting Migration Simultaneously
Serial Serial 1

One host from one host group
Serial Parallel 5

Five hosts from one host group
Parallel Serial 5

One host from five host groups
Parallel Parallel 25

Five hosts from five host groups
Important:

If there is a failure to migrate a host, the migration process will pause after all in-progress host migrations have finished. If Parallel is selected for both migration across groups and migration within groups, there might be a long outage for the failed host before you can retry migration.

Sequence of Migration Groups

You can select a host group (cluster) and use the arrows to move it up or down in the list of groups.

If migration fails for a host, you can move its host group to the bottom of the list of groups. The migration of other host groups can proceed while you resolve the problem with the failed host.

Migration State

Host groups (clusters) can have one of two migration states:

  • Enabled

    Hosts groups with a migration state of Enabled are migrated to NSX-T when you click Start on the Migrate Hosts page.

  • Disabled

    You can temporarily exclude host groups from migration by setting the migration state for the groups to Disabled. Hosts in disabled groups are not migrated to NSX-T when you click Start on the Migrate Hosts page. However, you must enable and migrate all Disabled host groups before you can click Finish. Finish all host migration tasks and click Finish within the same maintenance window.

In the Resolve Configuration step, hosts that are ineligible for migration are identified. In the Migrate Hosts step, these hosts have the migration state Do not migrate. For example, hosts that do not have NSX-V installed are not eligible for migration.

Migration Mode

Migration Mode is a host group (cluster) specific setting, and can be configured separately on each host group. In the Migrate Hosts step, you select whether to use In-Place or Maintenance mode.

There are two types of Maintenance migration modes:
  • Automated
  • Manual
In the Resolve Configuration step of the migration process, you select which type of Maintenance migration mode to use. You select a Maintenance mode even if you plan to migrate hosts using In-Place mode. When you select Maintenance migration mode in the Migrate Hosts step, the value you specified in the Resolve Configuration step determines whether Automated Maintenance mode or Manual Maintenance mode is used. However, in the Migrate Hosts step, if you select In-Place mode, your selected choice of Maintenance mode in the Resolve Configuration step does not take effect.

In-Place migration mode is not supported if your NSX-V installation uses vSphere Distributed Switch 7.0 or later.

If your environment uses Distributed Firewall, select Automated Maintenance migration mode. If you select a different migration mode, the following limitations apply to environments with Distributed Firewall:

  • If you use Manual Maintenance migration mode, all VMs must be moved to NSX-T hosts, connected to NSX-T segments, and powered on before the last NSX-V host starts migrating. When you migrate your last NSX-V host, do not power off the VMs on the host. Move them to an NSX-T host using vMotion.
  • If you use Manual Maintenance migration mode, VMs have a gap in firewall protection for up to 5 minutes after they move to an NSX-T host.
  • If you use In-Place migration mode, and you have Distributed Firewall rules that are applied to a VM, those rules are not pushed to the host until the host and all its VMs are migrated. Until the rules are pushed to the host, the following applies:
    • If the NSX-T default rule is deny, the VM is not accessible.
    • If the NSX-T default rule is accept, the VM is not protected by the applied-to rules.
The migration process is different for each migration mode:

  • In-Place migration mode

    NSX-T is installed and NSX components are migrated while VMs are running on the hosts. Hosts are not put in maintenance mode during migration. Virtual machines experience a short network outage and network storage I/O outage during the migration.

  • Automated Maintenance migration mode

    A task of entering maintenance mode is automatically queued. VMs are moved to other hosts using vMotion. Depending on availability and capacity, VMs are migrated to NSX-V or NSX-T hosts. After the host is evacuated, the host enters maintenance mode, NSX-T is installed, and NSX components are migrated. VMs are migrated back to the newly configured NSX-T host. Note that VMs that are powered off will not be reconfigured. After migration, you need to manually configure these VMs before powering them on.

  • Manual Maintenance migration mode

    A task of entering maintenance mode is automatically queued. To allow the host to enter maintenance mode, do one of the following tasks:
    • Power off all VMs on the hosts.
    • Move the VMs to another host using vMotion or cold migration.

    Once the host is in maintenance mode, NSX-T is installed on the host and NSX components are migrated. After the host is migrated, for the powered-off VMs and the VMs that you moved, you will need to change their network connection from the NSX-V logical switch to an NSX-T segment.

In the NSX-V environment, if the ESXi host's vmk0 management interface is connected to a VSS (vSphere Standard Switch) portgroup that does not have an uplink, and the portgroup is bridged to a VDS portgroup, and the VDS version is 6.5, 6.6 or 6.7, you must migrate using the Maintenance mode. If you use the In-Place mode, the migration will fail.