There are numerous reasons to use vSphere host profiles, namely to ensure all your ESXi hosts within a cluster are configured identically.
Storage of course is an important part of this, as we need to ensure all hosts can see the same datastores, the same pathing policy configured etc.
If not we want an alert to tell us this so we can correct - even perhaps automagically with host profiles!
However local SAS drives within the ESXi server can be detected as remote storage devices, which as you can imagine can cause an issue with this compliance checking.
If this is the case the local SAS drive "naa.xxxxx ID" needs to be presented to each ESXi server to tick the compliance box, but thats not possible as it's a local disk.
In such case you wll come across the following errors in your host profile checks. Attempting to remediate will not resolve the problem.
To my knowledge there is no way of getting the local SAS to disk not show as remote storage so all you can do is disable this part of the check in the host profile.
1. In vSphere client under Home --> Host Profiles select Enable/Disable Profile configuration.
2. As in the image below, go to Storage Configuration
3. Native Multi-pathing (NMP) --> PSP and SATP confiugration for NMP policies, untick "PSP configuration for"
4. Pluggable Storage Architecture (PSA) configuration --> PSP and SATP confiugration for NMP policies, untick "PSA device configuration"
5. Click Ok and Rescan your cluster for compliance
6. Your cluster should now be complaint remove the 4 device naa device compliance issues.
Share this blog post on social media:Tweet
All advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.