vSAN Health Service - vSAN HCL Health – vSAN HCL DB up-to-date
search cancel

vSAN Health Service - vSAN HCL Health – vSAN HCL DB up-to-date

book

Article ID: 327011

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

This article explains the vSAN HCL Health – vSAN HCL DB up-to-date check in the vSAN Health Service and provides details on why it might report an error.

Adherence to the VMware Compatibility Guide (VCG)/Hardware Compatibility Guide (HCL) is critically important to the stability of vSAN environments. Experience has shown that failing to observe the VCG often leads to production outages over time. It is, therefore, very important to monitor the health checks in the HCL checker category. For more information, see the VMware Certified Compatibility Guides.

Environment

VMware vSAN 6.x
VMware vSAN 7.x
VMware vSAN 8.x
VMware vSAN 9.x

Resolution

Q: What does the vSAN HCL Health – vSAN HCL DB up-to-date check do?

This health check verifies the VMware Compatibility Guide database used for the HCL checks is up-to-date. These VCG checks are not done against the HCL on the VMware website, but rather against a copy stored on the vCenter Server.

The initial release of the health feature ships with a copy of the HCL database, which was current when released. This copy of the database will become outdated over time. This is especially true as new certifications with partners get added to the VCG.

Note: Hardware vendors regularly update their drivers and send them for VMware certification. Older drivers may even get removed from the VCG to reflect issues found. Therefore, it is critically important to keep the local copy up-to-date.

Q: What does it mean when it is in an error state?

This check uses thresholds of 90 or 180 days of age to show a warning or error, respectively. Those thresholds are on the high side, and VMware recommends keeping the database updated as often as operationally possible.

Note: As of version 6.7 U3 this warning will also trigger if one or more hosts are running a build of ESXi that is not on the HCL such as a pulled build or custom hot patch.

Q: How does one troubleshoot and fix the error state?

    • If the vCenter Server has Internet access, the "Get Latest Version Online" button should be used to pull the current HCL DB automatically. (Not supported for vCenter Servers without DNS setup, this would trigger the error message "Unable to get the latest HCL database version online". In this case the below method for vCenter Server without the Internet access should be followed).
    • If the vCenter Server does not have Internet access, the latest HCL DB can be sourced from  https://vvs.broadcom.com/service/vsan/all.json , this should be saved as a .json file locally, then uploaded to the VCenter server using the "Update From File" button.

Additional Information