vSAN Health Service - vSAN HCL Health – SCSI Controller on vSAN HCL
search cancel

vSAN Health Service - vSAN HCL Health – SCSI Controller on vSAN HCL

book

Article ID: 319933

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

This article explains the vSAN HCL Health – SCSI Controller on vSAN HCL 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 8.0.x
VMware vSAN 7.0.x

Resolution

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

This check displays information regarding the local storage I/O controller on the ESXi hosts that are participating in the vSAN cluster.

The check verifies that this critical piece of the hardware is listed on the VCG. The lookup is performed based on the PCI ID information (Vendor ID, Device ID, SubVendor ID, SubDevice ID).

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

If this check fails, the first step is to update the VCG database. It is possible that the hardware (or its firmware) got recently added to the VCG. If the device is still not listed in the VCG (and the health check fails), the vSAN environment may be at risk.


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

For more information how to query the make, model and version of your storage I/O controller, see the Using Esxcli Commands with vSAN (esxcli vsan debug controller list). 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 How to file a Support Request in Customer Connect.

Additional Information

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

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 - Component Metadata 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 – Congestion
vSAN Health Service - Physical Disk Health – Memory pools
vSAN Health Service - vSAN HCL Health - Controller Release Support
vSAN Health Service – vSAN HCL Health – Controller Driver
vSAN Health Service - vSAN HCL Health – vSAN HCL DB up-to-date
vSAN Health Service - Cluster Health – CLOMD liveness check
vSAN Health Check Information
vSAN Health Service - Network Health - Active Multicast connectivity check