VMware Cloud Community
KKvss
Enthusiast
Enthusiast
Jump to solution

vCenter 6.7 - disable specific hardware status warnings

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

Tags (2)
1 Solution

Accepted Solutions
kbiradar
Enthusiast
Enthusiast
Jump to solution

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

disablealarm.png

Note: This is only available in HTML5 client

View solution in original post

21 Replies
diegodco31
Leadership
Leadership
Jump to solution

you may consider to temporarily disable the alarm until the issue is solved.

Diego Oliveira
LinkedIn: http://www.linkedin.com/in/dcodiego
Reply
0 Kudos
KKvss
Enthusiast
Enthusiast
Jump to solution

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.

Reply
0 Kudos
diegodco31
Leadership
Leadership
Jump to solution

Please, print the alarm.

Diego Oliveira
LinkedIn: http://www.linkedin.com/in/dcodiego
Reply
0 Kudos
kbiradar
Enthusiast
Enthusiast
Jump to solution

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

disablealarm.png

Note: This is only available in HTML5 client

KKvss
Enthusiast
Enthusiast
Jump to solution

Hi,

that´s what I need but in my case it´s on DC / Cluster and Host level grayed out Smiley Sad also with administrator@vsphere.local.

pastedImage_1.png

Greetings

KKvss

Reply
0 Kudos
kbiradar
Enthusiast
Enthusiast
Jump to solution

You can not do it on host level.

Reply
0 Kudos
SupreetK
Commander
Commander
Jump to solution

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

Reply
0 Kudos
KKvss
Enthusiast
Enthusiast
Jump to solution

Issue is fixed with:

ESXi 6.7 Express Patch 5ESXi670-2018110012018-11-0910764712

and

ESXi 6.5 Express Patch 11ESXi650-2018110012018-11-0910719125

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.

Reply
0 Kudos
Marcel72
Contributor
Contributor
Jump to solution

Issue is back running VMware ESXi, 6.7.0, 16075168 on a HPE ProLiant DL360 Gen10 Ilo Firmware version 2.10 Oct 30 2019

SchneiderRobert
Contributor
Contributor
Jump to solution

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

HugsterOne
Contributor
Contributor
Jump to solution

Same problem here.

9x ProLiant DL380 Gen10 with the same error after upgrade to VMware ESXi, 6.7.0, 16075168

iLo Version 2.15

Nodnarb
Enthusiast
Enthusiast
Jump to solution

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.

2020-05-06_11-27-46.png

Reply
0 Kudos
OLVSystems
Contributor
Contributor
Jump to solution

Same here after upgrading to release 16075168

Hardware HPE Proliant DL380 Gen10

pastedImage_0.png

Please Fix this!

Reply
0 Kudos
pclement
Contributor
Contributor
Jump to solution

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.

Reply
0 Kudos
mariss35
Contributor
Contributor
Jump to solution

in same boat as others , did you had any meaningful response/solution from support , is there point to open ticket ?

Reply
0 Kudos
Aurhel
Contributor
Contributor
Jump to solution

Same to me at all Gen10 Esxi, but haven't found a solution.

Reply
0 Kudos
scott28tt
VMware Employee
VMware Employee
Jump to solution

This may help: HP DL380 Gen10 - esxi 6.7.0 - Build 16075168 - Hardware State error - Fan Device 1 Fan 1


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
mariss35
Contributor
Contributor
Jump to solution

Thanks , this is definitely better workaround than disabling fan alert definition on vcenter level

Reply
0 Kudos
pclement
Contributor
Contributor
Jump to solution

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.

Reply
0 Kudos