Hello Community,
we had a server which had only 8 of 10 fans installed what is still ok.
But since we upgraded the host from 5.5 to 6.5 the hardware status triggers an alert for those two missing fans.
Is there a possibility to disable the 2 fans trigger or the completely hardware status?
Thanks for a short response.
Greetings
KKvss
Hi,
hardware health reports sensor's health and in your case 2 fans are missing.
Even if its not alarming situation for you, it should be reported as warning.
There is a way to suppress or disable these warnings.
Not ideal, but helpful.
in VC
Configure -> Alarm Definitions -> Filter alarm by name -> Host hardware fan status -> Select it -> disable if already enabled
The column "Enabled' will show current value
Note: This is only available in HTML5 client
you may consider to temporarily disable the alarm until the issue is solved.
It looks like that I can´t disable those original alarms - I can only set the alarm to "green" but after a new hardware status refresh job the alarm triggers again.
Like I said it is not an issue - we have 1 CPU and it´s not a performance model so 8 of 10 fans are built in what is a normal configuration from HP.
Please, print the alarm.
Hi,
hardware health reports sensor's health and in your case 2 fans are missing.
Even if its not alarming situation for you, it should be reported as warning.
There is a way to suppress or disable these warnings.
Not ideal, but helpful.
in VC
Configure -> Alarm Definitions -> Filter alarm by name -> Host hardware fan status -> Select it -> disable if already enabled
The column "Enabled' will show current value
Note: This is only available in HTML5 client
Hi,
that´s what I need but in my case it´s on DC / Cluster and Host level grayed out also with administrator@vsphere.local.
Greetings
KKvss
You can not do it on host level.
These alarms are defined at the vCenter level and are applied to concerned child objects. Therefore, they need to be disabled at the vCenter level itself.
Cheers,
Supreet
Issue is fixed with:
ESXi 6.7 Express Patch 5 | ESXi670-201811001 | 2018-11-09 | 10764712 |
and
ESXi 6.5 Express Patch 11 | ESXi650-201811001 | 2018-11-09 | 10719125 |
That was a knowing issue from VMware with HP Gen8 and 6.5 missing fans created an alert also for HP Gen9/10 and 6.7 they fixed an alert for missing [Device] I/O Module.
Issue is back running VMware ESXi, 6.7.0, 16075168 on a HPE ProLiant DL360 Gen10 Ilo Firmware version 2.10 Oct 30 2019
Can confirm
2x dl360 gen10 both with the same error after upgrade to 16075168
iLo Version 2.15
0.29.1.3Fan Device 1 Fan 1 Alarm19216Fan
Same problem here.
9x ProLiant DL380 Gen10 with the same error after upgrade to VMware ESXi, 6.7.0, 16075168
iLo Version 2.15
Can-confirm the issue is back in release 16075168. We have 14 DL380 Gen10 servers with iLO 2.15. All have the issue since applying the update.
Same here after upgrading to release 16075168
Hardware HPE Proliant DL380 Gen10
Please Fix this!
I can also confirm this has regressed with the latest patch.
6x DL380 gen10 (3 with the same error after upgrade to 16075168 - we stopped when this occurred).
All firmware current. iLO at 2.15, but had the same issue at 2.14.
0.29.1.3Fan Device 1 Fan 1 Alarm19216Fan
I have an active case with Support that has gone to Engineering.
Did they hire some Microsoft devs here? It's not often I've had a bad patch from VMware.
in same boat as others , did you had any meaningful response/solution from support , is there point to open ticket ?
Same to me at all Gen10 Esxi, but haven't found a solution.
This may help: HP DL380 Gen10 - esxi 6.7.0 - Build 16075168 - Hardware State error - Fan Device 1 Fan 1
Thanks , this is definitely better workaround than disabling fan alert definition on vcenter level
They posted an article, KB78989, that tells you to disable the sensor on the Host. While that may make the alert in VC go away, if you look at the result of the ipmi command it also disables anything else under sensor #3 (in that case), which would be a LOM and CPU#2.
I'm pretty sure that most people would want to know about hardware alerts for hardware that is actually installed, so this isn't a viable solution if you care about valid hardware alerts.
They closed my case and pointed me to the KB. Engineering is involved, so it will likely get patched, but I find the workaround pretty dangerous.