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
Change values at bottom:
config.vpxd.event.burstFilter.rateEvents = 3 [save]
config.vpxd.event.burstFilter.rateSeconds = 90 [save]
![Screenshot from the Resolve ESXi Sensor -1 Hardware Health Alarms walkthrough at step 2, showing Name must start with ‘config.’ For example: config log; the adjacent article text explains that change values at bottom: config.vpxd.event.burstFilter.rateEvents = 3 [save]; config.vpxd.event.burstFilter.rateSeconds = 90.](https://i0.wp.com/digitalthoughtdisruption.com/wp-content/uploads/2020/04/2.png?resize=849%2C136&ssl=1)
![Screenshot from the Resolve ESXi Sensor -1 Hardware Health Alarms walkthrough at step 3, showing Name must start with ‘config.’ For example: config.log; the adjacent article text explains that change values at bottom: config.vpxd.event.burstFilter.rateEvents = 3 [save]; config.vpxd.event.burstFilter.rateSeconds = 90.](https://i0.wp.com/digitalthoughtdisruption.com/wp-content/uploads/2020/04/3.png?resize=822%2C105&ssl=1)
Confirm changes applied
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.