Configure the vSphere ESXi hypervisor as an NSX-T transport node with two uplinks. Assign only the vmnic1 configuration to the transport node at that stage. The vmnic0 configuration remains attached to the VSS.
About this task
Migrate the vmknics from the VSS to the N-VDS, using NSX-T API calls to the NSX Manager. See NSX-T API Guide. For example, you can migrate the storage kernel interface vmk1 to N-VDS.
Verify that the physical network infrastructure provides the same LAN connectivity to vmnic1 and vmnic0.
Verify that the unused physical NIC, vmnic1, has Layer 2 connectivity with vmnic0.
All vmknics involved in migration must belong to the same network. If you migrate vmknics to an uplink connected to a different network, the host might become unreachable or non-functional.
- Create a VLAN transport zone with the host_switch_name of the N-VDS used by the OVERLAY transport zone.
- Create a VLAN-backed logical switch in the VLAN transport zone with a VLAN ID that matches the VLAN ID used by vmk1 on the VSS.
- Add the vSphere ESXi transport node into the VLAN transport zone.
- Retrieve the vSphere ESXi transport node configuration.
Where <transportnode-id> is the UUID of the transport node.
- Migrate the storage kernel interface, vmk1 to N-VDS.
PUT https://<NSXmgr>/api/v1/transport-nodes/<transportnode-id> ?if_id=<vmk>&esx_mgmt_if_migration_dest=<network>
Where the <transportnode-id> is the UUID of the transport node. The <vmk> is the name of the vmknic, vmk1. The <network> is the UUID of the target logical switch.
- Verify that the migration has finished successfully.
Wait until the migration state appears as SUCCESS. You can also verify the migration status of the vmknic in vCenter Server.
The VMkernel interface is migrated from VSS to N-VDS switch.
What to do next
You can migrate the remaining vmknics and the management kernel interface of the VSS to the N-VDS.