- VDS version compatibility with vCenter and ESXi
vCenter Server Version | vDS version | Host Version |
vCenter Server 8.0 | vDS 8.0/7.0/6.6 | ESXi 8.0 |
vCenter Server 7.0 | vDS 7.0/6.6/6.5 | ESXi 7.0 |
VDS 6.5 can be upgraded to either 6.6 or later
If your current VDS version is 6.5, then you might experience a brief downtime while upgrading your switches to a later version. If your current VDS version is 6.6 or later, then you might not experience any downtime while upgrading the switches to a later version.
VMware vCenter Server 7.x, 8.x
VMware ESXi 7.x, 8.x
Before you begin, please make sure to:
- Upgrade vCenter to a version that is compatible with the VDS
- Upgrade all hosts connected to the distributed switch to a supported version for VDS
The following steps can be taken as best practices and recommendations to reduce the impact on production:
1. VDS upgrade needs be done during a maintenance window.
2. Export the VDS configuration (reference: Exporting/importing/restoring Distributed Switch configs using vSphere Web Client)
3. Disable DRS on all the clusters that will undergo this upgrade to ensure there are no vMotions at the same time as the upgrade. It can be enabled once the upgrade finishes. This step is important.
- Do not perform VM operations (I.E. power on/off, vMotion, etc.) during the VDS upgrade; this could potentially lead to a failure in dvport allocation7. Post upgrade if the issues like "The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server." are seen, open the case with Broadcom Support.
For more information, refer the following KB article:- ESXi hosts out of sync on a VDS after migration/upgrade and ESXi hosts showing out of sync with VDS
Note: The worst-case scenario with a VDS upgrade is that we lose network connectivity to the VDS on a host.
If management vmknic is on the same VDS, this may force us to access the host through the console and/or perform a reboot. But we don't have any known issues that could lead to this.