Risks regarding vCenter Server and ESXi version mismatch
search cancel

Risks regarding vCenter Server and ESXi version mismatch

book

Article ID: 436818

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware vCenter Server

Issue/Introduction

This article provides information regarding the behavior and risks when the ESXi version is newer than the vCenter Server version. Use this as a reference when upgrading only ESXi to apply specific fixes.

Environment

VMware vSphere 8.0
VMware vSphere 7.0

Cause

vCenter Server is designed with the premise that its version is equal to or higher than the managed ESXi hosts. A configuration where the ESXi version is newer than the vCenter Server version differs from this premise.

Resolution

Systems will generally function as long as the versions are listed as compatible in the Product Interoperability Matrix. However, issues such as management operation failures, errors, or functional limitations may arise because this differs from the originally intended configuration.

Therefore, unless there is a specific reason such as applying a patch for a critical operational issue, it is recommended to maintain the vCenter Server at a version or build equal to or higher than the ESXi hosts.

If you choose to upgrade ESXi first, please be aware that such issues might occur.

In the unlikely event that you encounter any issues in a configuration where the ESXi version is newer, VMware Support may advise you to upgrade the vCenter Server to an equal or higher version. Depending on the situation, there may be no effective workaround other than upgrading.

Additional Information

Japanese version: vCenter Server と ESXi のバージョン不一致におけるリスクについて(436817) 

Related KB
vCenter Server version & ESXi Host version recommendations and considerations

Known issues reported in such environment include:

vSAN On disk format fails with error Detected disks of higher disk version on hosts(372553)

Running an image compliance check against a host or cluster in Lifecycle Manager results in an error stating, an unexpected error has occurred(376580)

vSAN health history not showing data(411092)

These are only a few reported examples. Since there is limited verification and historical data for this environment, other issues may occur.