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

This health check verifies the VMware Compatibility Guide (VCG) 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.

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 to keep the database updated as often as operationally possible. Since vSphere 6.7 Update 3 release, this check will also show warning if not all ESXi versions are included in HCL database even the file is not older than 90 days.

To resolve this issue, use one of the options:

  • To allow auto-update from the Internet:
    1. Enable Internet access for the vCenter.
    2. Go to Cluster > Monitor > vSAN > Skyline Health > Hardware Compatibility > vSAN HCL DB up-to-date.
  1. Click GET LATEST VERSION ON LINE.
  2. Click RETEST.
     
  • To manually update the HCL DB:
    1. Go to Cluster > Monitor > vSAN > Skyline Health > Hardware Compatibility > vSAN HCL DB up-to-date.
    2. Click UPDATE FROM FILE.
      1. On a workstation with Internet connectivity, browse to, https://partnerweb.vmware.com/service/vsan/all.json (Right click, Save as)
      2. Save the file as all.json. If you are unable to save the file, you must copy the entire content and create a new file with extension “*.json”.
    3. Select a valid HCL file with latest or newer timestamp.
    4. Click RETEST.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s