Syslog.log file of the Dell host reports the log spew: IpmiIfcRhFruInv: Reading FRU header for 0xc FAILED cc=0xc3
search cancel

Syslog.log file of the Dell host reports the log spew: IpmiIfcRhFruInv: Reading FRU header for 0xc FAILED cc=0xc3

book

Article ID: 339926

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • In the /var/log/syslog.log of the Dell hosts, you see entries similar to this in every 60 minutes:
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfruInfoAreaLength: Reading FRU for 0x11 at 0x7f8 FAILED cc=0xc9</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfcFruChassis: Reading FRU Chassis Info Area length for 0x11 FAILED</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfruInfoAreaLength: Reading FRU for 0x11 at 0x7f8 FAILED cc=0xc9</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfcFruBoard: Reading FRU Board Info Area length for 0x11 FAILED</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfruInfoAreaLength: Reading FRU for 0x11 at 0x7f8 FAILED cc=0xc9</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfcFruProduct: Reading FRU product Info Area length for 0x11 FAILED</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfcFruMultiLength: Reading FRU Multi Record Header for 0x11 at offset 0x7f8 FAILED cc=0xc9</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfcFruMulti: FRU Multirecord len is equal to zero, not valid.</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfcRhFruInv: Reading FRU header for 0xa FAILED cc=0xc3</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfcRhFruInv: Reading FRU header for 0xf FAILED cc=0xc3</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfcRhFruInv: Reading FRU header for 0xe FAILED cc=0xc3</time>
<YYYY-MM-DD>T<time> sfcb-vmware_raw[2522806] IpmiIfcRhFruInv: Reading FRU header for 0xc FAILED cc=0xc3</time>

  • Messages in syslog server causes excessive log spew.
  • No errors are observed in the hardware status tab on the vSphere Client or vSphere Webclient.


Environment

VMware vSphere ESXi 6.0
VMware vSphere ESXi 5.1
VMware vSphere ESXi 5.5

Cause

This issue occurs when the fru components fail to return data or there is no data available for the request.

Resolution

This is a known issue affecting ESXi 5.1.x, 5.5.x and 6.0.

Currently, there is no resolution.

To workaround this issue, set CIMLogLevel log level to 1 which results in suppressing these messages that does not impact any functions or indicate any problems on the host.

To set CIMLogLevel log level to 1:

  1. Log in as root to the ESXi console through SSH or iDRAC.
  2. Run this command to stop the sfcbd service:

    /etc/init.d/sfcbd-watchdog stop

  3. Set the CIMLogLevel to 1 using the command:

    esxcfg-advcfg -s 1 /UserVars/CIMLogLevel

  4. Run this command to start the sfcbd service:

    /etc/init.d/sfcbd-watchdog start


Additional Information

Dell 主机的 syslog.log 文件显示多条错误消息:IpmiIfcRhFruInv:Reading FRU header for 0xc FAILED cc=0xc3
Dell ホストの Syslog.log ファイルに次のエラー メッセージのエントリがいくつも表示される:IpmiIfcRhFruInv:Reading FRU header for 0xc FAILED cc=0xc3