When you use storage devices that are not shared across a cluster, but that the vSphere storage stack cannot detect as local, compliance failures might occur when you apply a host profile.
Before you begin
Extract a host profile from a reference host. See Create a Host Profile for instructions.
About this task
To resolve the compliance failures caused by using unshared storage devices, use the upgraded Pluggable Storage Architecture (PSA) and Native Multipathing Plug-In host profile policies.
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.
- For SAS devices that are not detected as local, select .
- For each device not shared across the cluster, disable Device is shared clusterwide.
The Is Shared Clusterwide value 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.
By default, this value is populated to reflect the Is Local setting for the device. For example, a device with Is Local set to True, this setting is disabled by default. This setting allows storage host profiles to ignore these devices during compliance checks.
You can find the Is Local setting for the device by running the command esxcli storage core device list in the ESXi Shell. For more information on this command and identifying disks or LUNs, see http://kb.vmware.com/kb/1014953.
- Do not disable Is Shared Clusterwide for SAN boot LUNs. In ESXi 6.0, SAN boot LUN devices are handled as expected. If Is Shared Clusterwide is disabled for these devices, then compliance errors caused by SAN boot LUN devices in previous releases do not occur, but the device configuration is not applied to the other hosts in the cluster. Select and verify that this LUN is correctly captured.
- Remediate the profile to the reference host for the changes in the sharing state to take effect on the reference host.
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 sharing for devices that you previously configured.