When using N-VDS as the host switch, NSX-T is represented as an opaque network in vCenter Server. N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from NSX-T Data Center. You can migrate your host switch to vSphere Distributed Switch (VDS) 7.0 for optimal pNIC usage, and manage the networking for NSX-T hosts from vCenter Server. When running NSX-T on a VDS switch, a segment is represented as an NSX Distributed Virtual Port Groups. Any changes to the segments on the NSX-T network are synchronized in vCenter Server. Note that in NSX-T Data Center 3.1, N-VDS to vSphere Distributed Switch migration is not supported for an N-VDS-based Collapsed Cluster environment. It is supported in NSX-T Data Center 3.1.1 without named teaming.
The parallel remediation feature requires vCenter Server 7.0 Update 2 or later. This feature is not supported for NSX-T Data Center 3.1 and should not be enabled for clusters under migration.
- X = Major
- Y = Minor
- Z = Maintenance
- U = Update
- P = Patch
Starting with 3.2.1, a precheck run will not fail in case of incompatible configurations between transport nodes within the same NSX-T Data Center. For incompatible configurations of UplinkProfile, LLDPProfile, and NIOCProfile, precheck will generate configuration issues. You can check the incompatible configurations and determine whether you want to apply topology or align configurations between transport nodes and run precheck again.
Precheck will also create VDSs for each combination of different configuration. Recommended topologies will include all combinations of different configuration of transport nodes within the same NSX-T Data Center (or the same cluster in case of VCF). A specific VDS will be generated for transport nodes with equivalent UplinkProfile, LLDPProfile, and NIOCProfile.
Prerequisites
The following requirements must be met to migrate to a VDS 7.0 host switch:
- vCenter Server 7.0 or later
- ESXi 7.0 or later
- NSX-T is no longer represented as an opaque network after migration. You may need to update your scripts to manage the migrated representation of the NSX-T hosts.