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 7.0.x
VMware vSAN 6.0.x
VMware vSAN 6.2.x
VMware vSAN 6.7.x
VMware vSAN 6.1.x
VMware vSAN 8.0.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 your vCenter Server has Internet access, click the "Get Latest Version Online" button. (Do not support vCenter Server without DNS, will hit the error message "Unable to get the latest HCL database version online". Please try the method for vCenter Server doesn't have Internet access).
  • If your vCenter Server doesn’t have Internet access, then you can get the latest HCL DB from http://partnerweb.vmware.com/service/vsan/all.json, save this as a .json file locally then use the "Update From File" button to upload it to vCenter Server.

 


Additional Information

For more information on collecting VMware vSAN logs, see How to collect vSAN support logs and upload to VMware by Broadcom (327035).
 
vSAN Health Service - Cluster Health - vSAN daemon liveness check (318410)
vSAN Health Service - Network Health - Hosts disconnected from vCenter Server (326848)
vSAN Health Service - Network Health - Unexpected vSAN cluster members (315548)
vSAN Health Service - Network Health - vSAN Cluster Partition (318839)
vSAN Health Service - Network Health - Hosts with vSAN disabled (331449)
vSAN Health Service - Network Health - All hosts have a vSAN vmknic configured (326928)
vSAN Health Service - Network Health - vSAN Cluster Partition (318839)
vSAN Health Service - Network Health - Hosts small ping test (connectivity check) and Hosts large ping test (MTU check) (326823)
vSAN Health Service - Network Health - Hosts with connectivity issues (326428)
vSAN Health Service - Data Health – vSAN Object Health (326929)
vSAN Health Service - Physical Disk Health – Component Metadata Health (327060)
vSAN Health Service - Physical Disk Health - Operation Health (326969)
vSAN Health Service - Physical Disk Health - Disk Capacity (326890)
Powered by Wolken Software