VMware Virtual Volumes (VVols) operation fails with the error: Sanity check failed for path vmhbaX:Y:Z. The path is to a vVol PE, but it goes out of adapter vmhbaX which is not PE capable. Path dropped

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• VMware Virtual Volumes (VVols) operation fails.
• Running the esxcli storage core adapter list command fails to list Second Level Lun ID (SLLID) for a specific Host Bus Adapter (HBA)
• In the /var/log/vmkernel.log file on the ESXi host, you see the error similar to:
  
  Sanity check failed for path vmhbaX:Y:Z. The path is to a VVol PE, but it goes out of adapter vmhbaX which is not PE capable. Path dropped.

Environment

VMware vSphere ESXi 6.7
VMware vSphere ESXi 7.0
VMware vCenter Server 6.0.x
VMware vSphere ESXi 8.0
VMware vSphere ESXi 6.0
VMware vSphere ESXi 6.5

Cause

This issue occurs because the path that the Protocol Endpoint (PE) LUN is using is not VVol capable.

A Protocol Endpoint (PE) must be exposed from a storage array prior to registering the Vendor Provider (VP) through the VMware vSphere APIs for Storage Awareness (VASA).

Virtual Volumes (VVols) operations requires specific driver support, and paths to a VVol PE LUN that are presented to a driver that is not VVol-capable cannot be used and are dropped.

Newly discovered LUNs can be independently recognized as PEs from their SCSI INQUIRY data, (SCSI VPD Page 0x86 Inquiry with LU_CONG bit set, indicating that this Logical Unit is part of a conglomerate, and that SPC3 or greater (ansi 0x5) support is advertised ). However, vSphere checks if the driver for the adapter through which the PE LUN was presented is VVol-capable before claiming the path for possible use.

If a newly discovered LUN is recognized as a PE LUN but the path is not VVol capable, the path is dropped instead.

Note: Third party customized images may contain a vSphere 6.0.x compatible drivers but it may not be VVol capable.

Resolution

To resolve this issue, upgrade the HBA driver to a VVol capable level. The HBA driver must support the feature for Second Level Lun ID (SLLID). To confirm HBA driver support for SLLID feature, please see VMware Hardware Compatibility list.

To manually check if the HBA is VVol capable, run this command esxcli storage core adapter list. Ensure the Second Level Lun ID is returned under the Capabilities output.

For example:

Additional Information

This warning appears every time a PE LUN is presented through an HBA when the driver is not VVol capable. However, the error does not interfere with normal, non-VVol operations.

Note: Periodic SAN path probes occur every 5 minutes. The error message appears in the /var/log/vmkernel.log file on the ESXi host every time the HBA is scanned.
VMware 仮想ボリューム (VVols) が動作ににすると次のエラーで失敗する：パス vmhbaX:Y:Z のサニティ チェックに失敗しました。このパスは VVol PE ヘのパスですが、PE 非対応のアダプタ vmhbaX からのパスです。パスはドロップされました。