After you migrate all other kernel interfaces, proceed to migrate the management kernel interface. When you migrate the management kernel interface, you move vmnic0 and vmk0 from a VSS or VDS to an N-VDS.

Then you can migrate the physical uplink vmnic0 and vmk0 to the N-VDS together in one step. Modify the transport node configuration so that the vmnic0 is now configured as one of its uplinks.


If you want to migrate the uplink vmnic0 and kernel interface vmk0 separately, first migrate vmk0 and then migrate vmnic0. If you first migrate vmnic0, then vmk0 remains on the VSS or VDS without any backing uplinks and you lose connectivity to the host.


  • Verify connectivity to the already migrated vmknics. See Migrate VM Kernel Interfaces to N-VDS.

  • If vmk0 and vmk1 use different VLANs, trunk VLAN must be configured on the physical switch connected to PNICs vmnic0 and vmnic1 to support both VLANs.

  • Verify that an external device can reach interfaces vmk1 on storage VLAN-backed logical switch and vmk2 on the vMotion VLAN-backed logical switch.


  1. (Optional) Create a second management kernel interface on VSS or VDS and migrate this newly created interface to N-VDS.
  2. (Optional) From an external device , verify connectivity to the test management interface.
  3. If vmk0 (management interface) uses a different VLAN than vmk1 (storage interface), create a VLAN-backed logical switch in the VLAN transport zone with a VLAN ID that matches the VLAN ID used by vmk0 on the VSS or VDS.
  4. Retrieve the vSphere ESXi transport node configuration.

    GET /api/v1/transport-nodes/<transportnode-id>

    Where <transportnode-id> is the UUID of the transport node.

  5. In the host_switch_spec:host_switches element of the configuration, add the vmnic0 to the pnics table and assign it to a dedicated uplink, uplink-2.

    While migrating the VM kernel interfaces, we assigned vmnic1 to uplink-1. It is necessary to assign vmnic0, the management interface to a dedicated uplink for the migration to be successful and the host to be reachable after migration.

    "pnics": [      {
                        "device_name": "vmnic0",
                        "uplink_name": "uplink-2"
                        "device_name": "vmnic1",
                        "uplink_name": "uplink-1"
  6. Migrate the management kernel interface, vmk0 to N-VDS using the updated configuration.

    PUT api/v1/transport-nodes/< transportnode-id>if_id=<vmk>&esx_mgmt_if_migration_dest=<network>

    Where, <transportnode-id> is the UUID of the transport node. The <vmk> is the name of the VMkernel management interface vmk0. The <network> is the UUID of the target logical switch.

  7. Verify that the migration has finished successfully.

    GET /api/v1/transport-nodes/<transportnode-id>/state

    Wait until the migration state appears as SUCCESS. In vCenter Server, you can verify whether the kernel adapters are configured to display the new logical switch name.

What to do next

You can choose to revert the migration of the kernel interfaces and management interface from N-VDS to a VSS or VDS switch.