Host Profiles playing up in vSphere 5

[NuggetGTR]

Hi all,

Ive recently upgraded about 200 hosts to ESXi 5 from ESX 4.1 and 2 vcenters 5 also.

Ive noticed a problem with host profiles when it comes to storage, and wanted to see if anyone else has come across it.

Basically its only happening on the HP BL620 G7 but the older HP BL680 G5's are unaffected.

When creating a profile from an existing host, That host it is created off obviously is compliant, but all the rest come back with saying that the local disk naa that was in the host it was created from is missing.. this only happens on the G7's might have something to do with a newer controller in the hosts?

Ok thats ok i edited the profile and removed that naa from the check but then the hosts are coming back with

Host state doesnt match specification: device (naa of local storage for that host) needs to be reset

Host state doesnt match specification: device (naa of local storage for that host) Path Selection Policy needs to be set to default for claiming SATP

Looking at the profile the default for VMW_SATP_LOCAL is fixed which is what the disk is set at.

Any one seen this? I have removed something from the check but seams to make things worse, I dont mind at the moment because I know the hosts are compliant I would like a big green tick instead of a big red cross

Cheers

[Troy_Clavell · Accepted solution]

this is a known issue.  Below is the fix

http://kb.vmware.com/kb/2002488

[Dracolith]

Troy Clavell wrote:

this is a known issue.  Below is the fix

http://kb.vmware.com/kb/2002488

The fix would appear to have the downside of excluding  PSA and Multipathing configuration

from the host profile   _Even_   for storage devices that actually are shared storage devices.

Those sections of the host profile also get re-enabled whenever you "Update Profile from Reference Host"

So yeah,  this issue is a nuisance.   It would be nice if there was a /real/  fix for it.

[ChrisGurley]

Agreed. One of my main objectives in using host profiles is to see shared devices not using the right PSP. It's already showed me several. If I turn this off, I'll lose out on a key purpose... *sad*

[DSeaman]

I'm running into the same problem with 5.0 Update 2 unfortunately. 

[Dadabo]

Still exists in 5.1

[jdptechnc]

This is still an issue with vCenter 5.1.0B and ESXi 5.1 Patch 1.  I can't believe a proper fix has not been implemented for this yet.

I was able to work around it by only disabling these sections under Storage Configuration/Pluggable Storage Architecture Configuration

- PSA Device Setting

- PSA Device Configuration

I didn't have to disable the settings for NMP.

I also ran into the same kind of thing with my BladeCenter servers when I had the remote media tray attached to a server.  The devices for the virutal CD Rom and USB were treated the same way and generated compliance errors.

[Josephvirtual]

I had same similar kind of issues while configuring vSphere 5.1 on Cisco UCS blades but fix for the following errors is not updated in VMware KB article.

Refer this blogpost for the fix with screenshots.  Host Profiles Compliance error in vSphere 5 |Virtualcloudz

Specification State absent from host: device naa.xxx Parameters needs to be set to Is Perennially Reserved = "false"

Host State doesn't match specification: device naa.xxx parameters need to be reset.