Error: "Comparable profile not found" for PSA, NMP, or SATP during Host Profile Compliance Check

Products

• VMware vCenter Server

Issue/Introduction

• When performing a Host Profile compliance check against a VMware ESXi host, the host reports a status of Not Compliant.
• The compliance check fails with errors related to the Pluggable Storage Architecture (PSA), Native Multipathing (NMP), or Storage Array Type Plug-in (SATP) policies for multiple Storage Device IDs (NAA IDs).

• Exact error messages observed:

  • Comparable profile not found: NmpDeviceConfigurationProfile

  • Comparable profile not found: PsaDeviceInquiryCacheProfile

  • Comparable profile not found: PsaDeviceSettingProfile

  • Comparable profile not found: SatpDeviceProfile

Environment

vSphere 7.x

vSphere 8.x

Cause

• Host Profiles enforce shared storage configurations across all hosts in a cluster, expecting storage devices to be strictly categorized as either "local" or "shared cluster-wide." The vSphere storage stack automatically detects which devices are local.

  However, this detection mechanism is not always reliable for the special case of local Serial Attached SCSI (SAS) devices. Local SAS devices are sometimes incorrectly detected as non-local (shared). Because these unshared devices have unique Device IDs (NAA IDs) on each host, applying a Host Profile generated from a reference host to another host results in compliance failures due to device ID mismatches.

Resolution

To prevent the compliance error from generating, disable the specific PSA and NMP profile checks under the Storage Configuration in the Host Profile.

Note: There is no downtime required for this task.

1. 1. Navigate to Policies and Profiles > Host Profiles in the vSphere Client.

   2. Right-click the affected Host Profile and select Edit Host Profile or Enable/Disable Profile Configuration (depending on the vSphere client version).

   3. Unfold Storage Configuration.

   4. Unfold Pluggable Storage Architecture (PSA) Configuration.

   5. De-select PSA Device Configuration.

   6. Unfold Native Multi-Pathing (NMP).

   7. Unfold PSP and SATP configuration for NMP devices.

   8. De-select PSP configuration for.

   9. Click OK or Save to apply the configuration.

   10. Re-run the compliance check on the affected hosts to verify the profile now shows as Compliant.

Additional Information

For further details regarding PSA and Native Multipathing Plug-In host profile policies, refer :

Host Profile Compliance Check fails with error "Comparable profile not found: SatpClaimrulesProfile - Parameter value eui.###### not found by esxcli."