vSAN Health Service – vSAN HCL Health – Controller Driver

Products

• VMware vSAN

Issue/Introduction

This article explains the vSAN HCL Health – Controller Driver Health check in the vSAN Health Service in vSAN 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 8.0.x

Resolution

Q: What does the vSAN HCL Health – Controller Driver check do?

This health check displays whether or not the storage I/O controller driver is supported for controller installed on the host running ESXi, and whether it is supported with that release of ESXi.

Assuming that the Controller on vSAN HCL and Controller Release Support health checks have passed, this check will further verify that the driver version in use is on the list of supported drivers.

This is important as drivers play a critical role in the stability and integrity of vSAN. Vendors often update their drivers to address critical bugs. In such cases, VMware may revoke the certification status of an old driver and only support the new version of the driver. Hence it is possible this check to turn from a healthy green (OK) state to showing warnings after refreshing the VCG database. In such cases, VMware recommends to upgrade the driver to the recommended version.

Note: There is also the possibility of a vendor updating a driver, and making it downloadable from their website. If VMware has not certified the driver for vSAN (either because the certification has not happened yet, or because it actually failed the certification) VMware does not recommend upgrading to this driver unless it appears on the VCG.

Before upgrading a driver, VMware recommends a refresh of the VCG database, checking the details section and checking for the supported drivers. If the new driver is supported, you can proceed with the upgrade with confidence.

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

Note: If the Controller on vSAN HCL or Controller Release Support check failed, then this check will also fail. If the driver is not listed in the VCG for this device and ESXi release, the vSAN environment may be at risk. If the driver is listed in the VCG for this device and ESXi release but still reports warning, it may indicate the driver is not certified with the current firmware.

For more information about this issue, refer to the following article: vSAN Health check warning for controller driver version containing string patterns with "-1OEM" or “VMW”.

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

If this test fails, VMware recommends to search the VCG and identify a desired driver and firmware pair and update the driver or firmware accordingly. It is possible the hardware (or it's firmware) or the release of the driver were recently added to the VCG.

For detailed instructions on how to query the make, model and version of your storage I/O controller, see the VMware vSAN Diagnostics and Troubleshooting Reference Manual (See Attached). If you still have difficultly determining storage I/O controller information, contact VMware Support to assess the situation fully. Do not simply rely on the automated health checks. VMware Support will also assist with any mitigation steps. For more information, see Filing Support Requests in Customer Connect and via Cloud Services Portal.

Q: My driver is certified as per vSAN VCG website, why the health check reports error?

Note: vSAN needs both controller driver and firmware to be a certified pair in order to be vSAN compliant.
If the driver is not currently certified with the current controller firmware, an error will be reported and you should either update the controller driver or update the controller firmware to ensure them to be a certified pair.

Additional Information

For more information on collecting VMware vSAN logs, see Collecting vSAN support logs and uploading to VMware.

For more information about compatibility between ESXi versions and vSAN on-disk format versions, see Understanding vSAN on-disk format versions and compatibility.

vSAN Health Service - Cluster Health - Advanced vSAN configuration in sync
vSAN Health Service - Network Health - Hosts disconnected from vCenter Server
vSAN Health Service - Network Health - Unexpected vSAN cluster members
vSAN Health Service - Network Health - vSAN Cluster Partition
vSAN Health Service - Network Health – Hosts with vSAN disabled
vSAN Health Service - Network Health - All hosts have a vSAN vmknic configured
vSAN Health Service - Network Health - Hosts small ping test (connectivity check) and Hosts large ping test (MTU check)
vSAN Health Service - Network Health - Hosts with connectivity issues
vSAN Health Service - Data Health – vSAN Object Health
vSAN Health Service - Physical Disk Health - Overall Disk Health
vSAN Health Service - Limits Health – Current Cluster Situation
vSAN Health Service - Limits Health – After one additional host failure
vSAN Health Service - Physical Disk Health - Disk Capacity
vSAN Health Service – Physical Disk Health – Component Metadata Health
vSAN Health Service - Physical Disk Health – Congestion
vSAN Health Service - Physical Disk Health – Memory pools
vSAN Health Service - vSAN HCL Health - Controller Release Support
vSAN Health Service - vSAN HCL Health – vSAN HCL DB up-to-date
vSAN Health Service - vSAN HCL Health – SCSI Controller on vSAN HCL
vSAN Health Service - Cluster Health – vSAN daemon liveness check