Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vSAN build recommendation engine may recommend an unsupported upgrade path (78295)

Last Updated: 8/27/2023Categories: InformationalTotal Views: 3671Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The vSAN build recommendation engine may recommend an update to an unsupported ESXi version under certain circumstances. Instead of supporting the highest supported build version for a server model as certified on the VMware hardware compatibility list, it will recommend a higher ESXi version that is not supported on the platform.

Cause

The vSAN build recommendation engine leverages the VMware Update Manager (VUM), the vSAN hardware compatibility list (HCL), and the vSAN release catalog to provide upgrade baselines for individual vSAN clusters. The vSAN HCL does not cover all hardware components in a server. The only components that are being taken into consideration for the compatibility check are:

- Storage Controllers

Other components, such as the NICs, CPUs, or server itself, are not being evaluated against the VMware VSAN HCL.

Impact / Risks

As controllers may be certified for multiple ESXi versions and being sold in multiple platforms, it can lead to hardware compositions where a subset of the components is certified but others aren't.

Example 1:
A cluster contains CPUs that are not supported for the latest version of ESXi, whereas the storage controller is fully supported for the latest version.

-> As the vSAN build recommendation engine will only check the compatibility of the storage controller, this will result in an upgrade baseline to the latest version. If this baseline is applied, it will result in an unsupported configuration and potentially a host that will not boot ESXi.

Example 2:
A host contains multiple storage controllers, of which not all are used for vSAN, and not all controllers are on the vSAN HCL.

-> The vSAN build recommendation engine will recommend the upgrade because the new state is no worse than the current state. For more information, please see
vSAN Build Recommendations for vSphere Update Manager

Resolution

For clusters that contain hardware that is not fully supported for the latest release of ESXi, the hardware has to be checked manually against the VMware HCL before proceeding with an upgrade.

If it has been determined that the cluster is not compatible with the latest version of ESXi and VMware vCenter 6.7U3 or higher is used, then it is possible to set the baseline preference to "Include patches and updates for current ESXi versions". That setting will result in the build recommendation engine only recommending patches and updates to the installed ESXi version but not any upgrades to a newer ESXi version.

Workaround

If the vCenter is not on version 6.7U3 or higher, then an update of the vCenter to 6.7U3 or higher can be performed to be able to set baseline preferences for the cluster.

If an update/upgrade of the vCenter is not possible, then the vSAN cluster has to be updated by creating a custom VMware Update Manager baseline or by patching the hosts manually.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
「AMQP ブローカ接続のテスト：失敗 - ACCESS_REFUSED - 認証メカニズム PLAIN を使用したログインが拒否されました。詳細については、ブローカのログ ファイルを参照してください。(Test AMQP Broker Connection: Failed - ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.)」 (76149)

KB
•
更改 SRM 站点清单映射后，无法更新现有保护组（受保护的虚拟机）上的清单映射 (78232)

KB
•
从 vSphere 控制台访问 vRealize Operations Manager 节点 (78377)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.7.x

VMware vSAN 6.5.x

Take Our Survey

Support Assistant