Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)   View by Article ID

Applying a host profile causes compliance failure in VMware ESXi 5.x / 6.0.x (2002488)


  • When attempting to complete the host profile application, or after applying the profile, you see these compliance failures:
Specification state absent from host: device 'datastore' state needs to be set to 'on'
Host state doesn't match specification: device 'datastore' needs to be reset
Specification state absent from host: device 'datastore' Path Selection Policy needs to be set to 'VMW_PSP_FIXED'
Host state doesn't match specification: device 'datastore' Path Selection Policy needs to be set to default for claiming SATP
  • This issue occurs when a host profile that is saved from a reference host records a SCSI-3 device as potentially a shared device. However, if the SCSI-3 is a local device, then after the host profile is applied to a host, a compliance check can fail. For example, this issue can occur if Host1 has a SAS device with GUID1 and Host2 has a different SAS device with GUID2. Examples of local-only SCSI-3 devices include certain local RAID controllers and SAS disks.

    Although the system hardware is comparable, you see a compliance error because similar devices with different device IDs are uniquely named in the form naa.UID, instead of the generic form mpx.pathname. The resulting profile compliance check detects that some devices are removed, while others are added without appearing in the stored profile.


The compliance error can be ignored if the issue is only a device ID mismatch. To avoid generating a compliance error, you can also disable the PSA and NMP profiles under Storage Configuration in the host profile as long as the storage configuration uses the default PSA or NMP profile settings.

To disable the PSA and NMP profiles in the vSphere Client:
  1. Log in to the vCenter Server using the vSphere Client.
  2. Under the Home view, click Host Profiles under Management.
  3. Recreate a new host profile to be applied. For more information, see Create a Host Profile in the vSphere Web Client section of the VMware vSphere 5.5 Host Profiles guide.
  4. In the Host Profiles view, right-click the host profile and select the second option, Enable/Disable Profile Configuration.
  5. Expand Storage Configuration.
  6. Expand Pluggable Storage Architecture (PSA) configuration.
  7. Deselect the PSA Device Configuration profile.
  8. Expand Native Mulitpathing (NMP).
  9. Expand PSP and SATP Configuration for NMP Devices.
  10. Deselect PSP configuration for and SATP configuration for (if present).
  11. Click OK.
  12. In Profile compliance, click Check compliance.
Note: If the issue persists after trying the steps in this article, file a Support Request with VMware Support and note this Knowledge Base article ID (2002488) in the problem description. For more information, see Filing a Support Request in My VMware (2006985).

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

For translated versions of this article, see:

Update History

10/10/2012 - Added note to contact VMware Support if issue persists

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 130 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 130 Ratings