When you use storage devices, that are not shared across a cluster, but the vSphere storage stack cannot detect them as local (for example, some SAS devices), applying a host profile might result with compliance failures.
About this task
To resolve the compliance failures caused by using local storage devices, use the upgraded Pluggable Storage Architecture (PSA) and Native Multipathing Plug-In (NMP) host profile policies.
Note:
ESXi diagnostic data that you obtain by running the vm-support command contains host profiles information which includes storage host profiles, PSA, NMP, and Virtual Volumes data. No sensitive information, such as passwords, is collected.
Procedure
- For SAS devices that are not detected as local, navigate to Edit Host Profile and select .
- For each device not shared across the cluster, disable Device is shared clusterwide.
Note:
By default, the Device is shared clusterwide setting is disabled for devices detected as local and enabled for non-local devices. This setting allows storage host profiles to ignore local devices during compliance checks.
The Device is Shared Clusterwide setting for PSA devices helps you determine which devices in the cluster should be configured by a host profile. Correctly setting this value for devices in the cluster eliminates compliance errors due to non-shared devices.
To find out whether the device is detected as local or not, you can check the Is Local setting for the device by running the command esxcli storage core device setconfig -d naa.xxxx --shared-clusterwide=false in the ESXi shell. For more information on this command and identifying disks or LUNs, see KB 1014953.
- For SAN boot LUN devices shared across the cluster, but logically local to the host, disable the Device is shared clusterwide on the reference host. You must set the value to False before extracting the host profile from the reference host. By using the command esxcli storage core device setconfig -d naa.xxxx --shared-clusterwide=false you can disable the Device is shared clusterwide value, where naa.xxxx is the unique device identifier generated in naa format.
When applying the host profile to the target host, the boot device settings for the remote boot LUN device are copied from the reference host into the target host.
- Select and verify that the boot LUN ID is correctly captured.
- Remediate the host profile to the reference host for the changes to take effect.
If you must re-extract the profile (for example, if you attach more shared SAN boot LUNs to your cluster), you do not need to reconfigure Device is Shared Clusterwide setting for devices that you previously configured.