Excessive Hardware health alarms being triggered for “Sensor -1 type” on ESXi hosts running vSphere 6.7 U3 (74607) Work Around & Solution

Posted by

Recently while working in my environment I uncovered a known issue and a KB article with a resolution and work around.  Here is a step by step of the applied work around.  I applied the immediate work around to avoid a vCenter crash, which is never a good thing.

Error:
Alarm ‘Host hardware sensor state’ on XXXXXX triggered by event 140601307 ‘Sensor -1 type , Description Intel Corporation C620  Series Chipset Family PCI Express Root Port #5 #28 state assert for . Part Name/Number N/A N/A Manufacturer N/A’

Alarm ‘Host hardware sensor state’ on XXXXXX triggered by event 1406691306 ‘Sensor -1 type . Description Intel Corporation C620  Series Chipset Family PCI Express Root Port #1 #28 state assert for . Part Name/Number N/A N/A Manufacturer N/A’

Alarm ‘Host hardware sensor state’ on XXXXX triggered by event 1406691305 ‘Sensor -1 type , Description Intel Corporation Sky  Lake-E DMI3 Registers #0 state assert for . Part Name/Number N/A N/A Manufacturer N/A’

These produced the following warning in my environment:
Event burst of ‘com.vmware.vc.StatelessAlarmTriggeredEvent’

Event burst of ‘vim.event.AlarmActionTriggeredEvent’

Associated VMWare KB article:
https://kb.vmware.com/s/article/74607?lang=en_US

Work around:
vCenter level > Configure > Advanced Settings > Edit Settings

Machine generated alternative text:
Summary 
Settings 
Monitor 
Configure 
permissions 
Datacenters 
Hosts & Clusters 
VMS 
Datastores 
Networks 
Linked vCenter Server Systems 
Summary 
Extensions 
Et*TTlNGs 
General 
Licensing 
Message of the Day 
Advanced Settings 
Authentication Proxy 
vCenter HA 
Advanced vCenter Server Settings 
alarms.version 
contig.alarms».'im version 
contig.alert log.enabled 
Value 
vim.version_version15 
true 
Default alarm upgrade version

Change values at bottom:
config.vpxd.event.burstFilter.rateEvents  = 3          [save]
config.vpxd.event.burstFilter.rateSeconds = 90         [save]

Machine generated alternative text:
Name • 
config_vpxd event burstFilterr 
Value : 
3 
I - 10 of 730 settings 
CANCEL 
73 
SAVE 
ADD 
Name must start with 'config.' For example: config_log
Machine generated alternative text:
Name • 
config_vpxd event burstFilterr 
Value : 
go 
CANCEL 
ADD 
Name must start with 'config.' For example: config_log 
SAVE

Confirm changes applied

Machine generated alternative text:
Advanced vCenter Server Settings 
Value 
contig.vpxd .event.burstFil 
contig.vpxd .event.burstFil 
x 
Summary 
730 items

Solution:
This issue is resolved in ESXi 6.7 Patch Release ESXi670-201911001, available at VMware Downloads.

Summary:
I am in the process of upgrading the hosts in this cluster per the KB.  I have noticed since applying the work around that the Warnings have ceased and the risk of my vCenter crashing has gone away.  I hope y’all found this article helpful.

Leave a Reply