If you found this blog post because you are searchting for a solution for a FAN FAILURE on your ProLiant Gen10 HW after applying the latest ESXi 6.7 patches, then use this shortcut for the workaround: Fan health sensors report false alarms on HPE Gen10 Servers with ESXi 6.7
I had a really annoying problem at one of my customers. After deploying new VMware ESXi hosts (HPE ProLiant DL380 Gen10) along with an upgrade of the vCenter Server Appliance to 6.7 U2, the customer reported recurring host hardware sensor state alarm messages in the vCenter for all hosts.
After acknowledging the alarm, it recurred after a couple of minutes or hours. The hardware was finde, no errors or warnings were noticed in the ILO Management Log. But the vCenter reported periodically a Sensor -1 type error in the Events window. The /var/log/syslog.log contained messages like this:
2019-11-29T04:39:48Z sfcb-vmw_ipmi[4263212]: IpmiIfcSelGetInfo: IPMI_CMD_GET_SEL_INFO cc=0xc1 2019-11-29T04:39:49Z sfcb-vmw_ipmi[4263212]: IpmiIfcSelGetInfo: IPMI_CMD_GET_SEL_INFO cc=0xc1 2019-11-29T04:39:50Z sfcb-vmw_ipmi[4263212]: IpmiIfcSelGetInfo: IPMI_CMD_GET_SEL_INFO cc=0xc1 2019-11-29T04:39:51Z sfcb-vmw_ipmi[4263212]: IpmiIfcSelGetInfo: IPMI_CMD_GET_SEL_INFO cc=0xc1 2019-11-29T04:39:52Z sfcb-vmw_ipmi[4263212]: IpmiIfcSelGetInfo: IPMI_CMD_GET_SEL_INFO cc=0xc1
Sure, you can ignore this. But you shouldn’t ignore this, because these events can result in the vCenter database increasing in size. vCenter can crash once the SEAT partition size goes above the 95% threshold. So you better fix this!
Long story short: This bug is fixed with the latest November updates for ESXi 6.7 U3. A workaround is to disable the WBEM service. The WBEM service might be enabled after a reboot. In this case you have to disable the sfcbd-watchdog service.
But the best way to solve this is to install the latest patches (VMware ESXi 6.7, Patch Release ESXi670-201911001)
Feel free to follow him on Twitter and/ or leave a comment.
- Why you should change your KRBTGT password prior disabling RC4 - July 28, 2022
- Use app-only authentication with the Microsoft Graph PowerShell SDK - July 22, 2022
- Getting started with the Microsoft Graph PowerShell SDK - July 21, 2022
Isn’t there a command line option to modify the threshold of the sensor for the alert?
After latest patch fan failure warning is back.
All upgraded hosts have FAN1 Failure :)
Noooo.
Yes, can confirm with Fredrik, updated my hosts yesterday and all are throwing this warning again.
Thank you for this hint!
I’ve run into the same fan issue after updating yesterday. I’ve also flashed BIOS and iLO on all my HP hosts and cannot clear this error. Hoping someone out there finds a solution. I am going to open a ticket with VMware.
Do they have a solution now?
Same problem in VMware ESXi, 6.7.0, 16075168 on DL560 Gen10 with all FW updated.
But, no problem on ProLiant DL560 Gen9 with the same VMware ESXi version.
Thanks
Eros
Same Problem on DL360 Gen10, ESXi, 6.7.0, 16075168
Regards
Frank
Hi Frank, have you tried the Workaround from the KB article?
Hello everybody,
I solved this problem on HP DL380 GEN10. You cant download auto from VUM . Only possible download manually this link
https://www.vmware.com/resources/compatibility/detail.phpdeviceCategory=vsanio&productid=42830&vsanrncomp=true&vcl=true and then create baselane or ad existing baselane. then select host after remidate, this take about 10-15 minutes. and then see green. I hoped this scenario help to yours.