To stop this alert in vCenter.
Symptoms:
YYYY-MM-DD HH:MM:SS info hostd[2103698] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=kbg3cv53-1515870-auto-whnl-h5:70140663-a0-ae-dd1e user=vpxuser:VSPHERE.LOCAL\Administrator] Event 1862 : Sensor -1 type , Description Memory state assert for . Part Name/Number N/A N/A Manufacturer N/A
YYYY-MM-DD HH:MM:SS info hostd[2103698] [Originator@6876 sub=Cimsvc opID=kbg3cv53-1515870-auto-whnl-h5:70140663-a0-ae-dd1e user=vpxuser:VSPHERE.LOCAL\Administrator]Sent ipmi events 0,storage health events 1
Sensor -1 type <-- Sensor ID and sensor type.
Description Memory <-- Sensor name.
state assert <-- Health state of sensor: deassert(green) indicates good health, otherwise assert(red, yellow).
Part Name/Number N/A N/A Manufacturer N/A <-- Other information.
NOTE: Storage hardware health is not supported(except when an LSI provider is installed).
NOTE: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
The health events are getting triggered for storage sensors even if the health state for it has not changed since the last polling.
This is happening because these storage sensors do not have a sensorId.
This issue is resolved in VMware ESXi 6.7 Patch release ESXi670-202004002. To download go to the Broadcom Support Portal page.
Workaround: