vCenter version to ESXi version

Products

• VMware vCenter Server
• VMware vSAN
• VMware vSphere ESXi

Issue/Introduction

To clarify the versioning requirements between vCenter and ESXi

Impact/Risks:
In rare cases, ESXi hosts on a newer version than vCenter may not properly process the unicast agent updates. This can result in a vSAN network partition.

Symptoms:

• Discrepancies in reporting between ESXi and vCenter
• Slow updates from the Hosts to vCenter.

Environment

• VMware vSAN (All Versions)
• VMware vCenter Server (All Versions)
• VMware vSphere ESXi (All Versions)

Cause

Communication between ESXi and vCenter is critical for VMware environments and build compatibility is key to reliable functionality. Code updates resolve known issues and enhance communication between related products.

For more detailed information regarding best practices for upgrading the environment see the following Knowledge Base articles:

• Update sequence for vSphere 8.0 and its compatible VMware products
• Update sequence for vSphere 7.0 and its compatible VMware products

vSAN

The health check feature in vSAN relies heavily on vCenter & ESXi communication and requires that vCenter be on an equal to or newer version than the ESXi hosts for reliable communication.

VxRail

As VxRail is built upon vSAN, it carries similar requirements for vCenter.
See Correlating VxRail Release with VMware build numbers for details about released versions of VxRail.

Resolution

Verify that the vCenter version is equal to or greater than the ESXi version.

Refer to:

• Correlating build numbers and versions of VMware by Broadcom products for more details about released products.
• Build numbers and versions of VMware vCenter Server specifically for vCenter Server versions.
• Build numbers and versions of VMware ESXi/ESX for ESXi versions

NOTE: Verify that all the products are compatible with the version of vCenter when planning updates by using the Product Interoperability Matrix.

Additional Information