When host IPMI system event log status alarm is triggered repeatedly in the Hardware Status tab in vCenter Server 4.x, 5.x or 6.x, clear the IPMI System Event log file located at /var/log/ipmi.
Symptoms:
VMware vSphere ESXi 6.0
VMware vSphere ESXi 6.5
VMware vSphere ESXi 6.7
This issue occurs when the IPMI System Event log file is full, which triggers the alarm that monitors the log file.
To determine why the log has filled up, investigate the hardware.
these additional symptoms are experienced:
In the /var/log/vmkernel.log
file, entries similar to the below are seen:
sfcb-vmware_raw[5153]: IpmiIfcSelReadAll: failed call to IpmiIfcSelReadEntry cc = 0xff
sfcb-vmware_raw[5153]: IpmiIfcSelReadAll: failed call to IpmiIfcSelReadEntry cc = 0xff
snmpd[19956]: Connection from UDP: [10.16.16.65]:61945
sfcb-vmware_raw[5153]: IpmiIfcSelReadAll: failed call to IpmiIfcSelReadEntry cc = 0xff
/usr/lib/vmware/bin/vmware-hostd[19577]: Accepted password for user root from 10.16.16.65
sfcb-vmware_raw[5153]: IpmiIfcSelReadAll: failed call to IpmiIfcSelReadEntry cc = 0xff
sfcb-vmware_raw[5153]: IpmiIfcSelReadAll: failed call to IpmiIfcSelReadEntry cc = 0xff
snmpd[19956]: Connection from UDP: [10.16.16.65]:61945
sfcb-vmware_raw[5153]: IpmiIfcSelReadAll: failed call to IpmiIfcSelReadEntry cc = 0xff
sfcb-vmware_raw[5153]: IpmiIfcSelReadAll: failed call to IpmiIfcSelReadEntry cc = 0xff
Note:If Warnings are being expirenced in the Hardware Status tab of an ESXi host fail to clear refer to: https://knowledge.broadcom.com/external/article?articleNumber=344267
Restarting the Management agents in ESXi
Location of vCenter Server log files
Timekeeping best practices for Windows, including NTP
vCenter Server 中出现 “主机 IPMI 系统事件日志状态 (Host IPMI system event log status)” 警报
Der Ereignisprotokoll-Statusalarm für das Host-IPMI-System wird in VMware vCenter Server 4.x und 5.x wiederholt ausgelöst
Der Ereignisprotokoll-Statusalarm für das Host-IPMI-System wird in VMware vCenter Server 4.x und 5.x wiederholt ausgelöst