HPE 380 Gen 9 FAN Status in vSphere 6.7

[preglerjr]

Fresh install of vSphere 6.7 on new GEN 9 HPE DL 380 servers and the fans in the server show up as failed.  I have seen other posts about this but those posts dead ended with no real resolutions to the problem.  Others stated it is a software issue on VMWare's side?  I am about to open up a support incident with them but don't want to waste money if they just tell me 'yeah we know about it'...

Any suggestions??

[RvdNieuwendijk]

Did you use the HPE ESXi Image for HPE ProLiant? If not, try that image. You can get more information about the HPE ESXi Image for HPE ProLiant on Using HPE Custom ESXi Images to Install ESXi on HPE ProLiant Servers | HPE.

[a_p_ · Accepted solution]

Don't waste your money. See https://kb.vmware.com/s/article/53134

André

[RvdNieuwendijk]

You can download the HPE ESXi Image for HPE ProLiant for free. It contains the HPE device drivers for ESXi. If you have installed the VMware ESXi image, you can also install the HPE ESXi Offline Bundles.

[preglerjr]

Yes used the custom ISO on VMWare's site for HPE.  Does not work.

[preglerjr]

I know this doesn't affect production but untrained eyes check these sensors and creates false positives and it need to be resolved.  Others have stated it is due to the absent fans for the second CPU.

[a_p_]

I totally agree with you, it's pretty ugly to see such warnings/errors.

IMO it's something that HPE - maybe together with VMware - should look at, so that a warning/error is only displayed in case one of thoses fans is missing in a two processor configuration.

If you have a support agreement with HPE, it may be an option to open a support case with them.

André

[preglerjr]

I wanted to give an update on this.  I contact HP and worked through their support team on the hardware to ensure no hardware issues were present.  I updated to the latest version of firmware on the DL380 Gen 9 and still no fix.

I then opened up a support case with VMWare and they just got back with me on it.  They stated it is a very well known issue and they will have a fix release in 6.7 update 1 (coming October of 2018) that will resolve this.

I will keep you posted on the progress but it appears this will be the fix.

Thanks.