Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
1,654 Views

Intel S5520HC: VmWare Esxi 5.1 and Bmc Fans Speed

#

Hardware / Software Configuration:

http://www.elledi.it/shop/product_info.php?products_id=52288469 S5520HCR Firmware : S5520HC_S5520SC_EFI_BIOS63_BMC61_FRU33_ME112

VMkernel localhost 5.1.0 # 1 SMP Release build-1065491 Mar 23 2013 10:12:46 x86_64 GNU/Linux

#

After Boot i see this warning in vmkernel.log and fans run fast about every 2/3 minutes

#

tail -f /var/log/vmkernel.log

2013-05-11T12:59:33.771Z cpu2:8688)<4>IPMI message handler: This message has repeated 78 times: BMC returned incorrect response expected netfn b cmd 43, got netfn 11 cmd 43

2013-05-11T12:59:33.856Z cpu2:8688)<4>IPMI message handler: This message has repeated 79 times: BMC returned incorrect response expected netfn b cmd 43, got netfn 11 cmd 43

2013-05-11T12:59:33.865Z cpu2:8688)<4>IPMI message handler: This message has repeated 80 times: BMC returned incorrect response expected netfn b cmd 43, got netfn 11 cmd 43

#

Message disappear stopping CIM agent

/etc/init.d/sfcbd-watchdog stop

The CIM agent is the process providing hardware health information.

Disabling this service will disable the hardware health status.

what is the cause of the problem?

0 Kudos
8 Replies
Highlighted
Employee
41 Views

Check the System Event Log (SEL) with the selview utility. Match up with the timestamps from the kernel log, to tell you what is ratcheting up the fan speed at those times.

Highlighted
Beginner
41 Views

No critical or related event are reported System Event Log:

05/10/2013-16:53:59 Processor /P1 Status (# 0x60) Informational event: P1 Status reports the processor's presence has been detected. BMC - LUN # 0 (Channel # 00h) 05/10/2013-16:53:59 Processor /P2 Status (# 0x61) Informational event: P2 Status reports the processor's presence has been detected. BMC - LUN # 0 (Channel # 00h) 05/10/2013-16:54:07 Power Supply /PS1 Status (# 0x50) Informational event: PS1 Status reports the power supply's presence has been detected. BMC - LUN # 0 (Channel # 00h) 05/10/2013-17:49:49 Power Unit /Pwr Unit Status (# 0x01) Informational event: Pwr Unit Status reports the power unit is powered off or being powered down. BMC - LUN # 0 (Channel # 00h) 05/10/2013-17:49:53 Power Unit /Pwr Unit Status (# 0x01) Informational event: Pwr Unit Status reports the power unit is powered off or being powered down. BMC - LUN # 0 (Channel # 00h) 05/10/2013-17:50:01 System Event /BIOS Evt Sensor (# 0x83 Informational event: BIOS Evt Sensor reports Timestamp Clock Sync. Event is first of two expected events from BIOS on every power on. BIOS (Channel # 00h) 05/10/2013-17:50:02 System Event /BIOS Evt Sensor (# 0x83 Informational event: BIOS Evt Sensor reports Timestamp Clock Sync. Event is second of two expected events from BIOS on every power on. BIOS (Channel # 00h) 05/10/2013-17:50:24 Drive Slot (Bay) /Pri Drv0 Pres (# 0x Informational event: The HSBP-A states that Pri Drv0 Pres reports the device has been inserted or is present. Primary HSC - LUN # 0 05/10/2013-17:50:26 Drive Slot (Bay) /Pri Drv1 Pres (# 0x Informational event: The HSBP-A states that Pri Drv1 Pres reports the device has been inserted or is present. Primary HSC - LUN # 0 05/10/2013-17:50:28 Drive Slot (Bay) /Pri Drv2 Pres (# 0x Informational event: The HSBP-A states that Pri Drv2 Pres reports the device has been inserted or is present. Primary HSC - LUN # 0 05/10/2013-17:50:30 Drive Slot (Bay) /Pri Drv3 Pres (# 0x Informational event: The HSBP-A states that Pri Drv3 Pres reports the device has been inserted or is present. Primary HSC - LUN # 0 05/10/2013-17:58:20 System Event /BIOS Evt Sensor (# 0x83 Informational event: BIOS Evt Sensor reports a system boot event has occurred. BIOS (Channel # 00h) 05/10/2013-18:27:45 Button /Button (# 0x09) Informational event: Button reports the power button has been pressed. BMC - LUN # 0 (Channel # 00h) 05/11/2013-12:56:06 System Event /BIOS Evt Sensor (# 0x83 Informational event: BIOS Evt Sensor reports a system boot event has occurred. BIOS (Channel # 00h) 05/14/2013-17:09:46 System Event /BIOS Evt Sensor (# 0x83 Informational event: BIOS Evt Sensor reports Timestamp Clock Sync. Event is first of two expected events from BIOS on every power on. BIOS (Channel # 00h) 05/14/2013-17:09:56 System Event /BIOS Evt Sensor (# 0x83 Informational event: BIOS Evt Sensor reports Timestamp Clock Sync. Event is second of two expected events from BIOS on every power on. BIOS (Channel # 00h)
0 Kudos
Highlighted
Beginner
41 Views

No events reported in SEL is related with this reported in /var/log/vmkernel.log:

2013-05-18T14:38:55.520Z cpu2:8688)<4>IPMI message handler: This message has repeated 29 times: BMC returned incorrect response expected netfn b cmd 23, got netfn 9 cmd 23

2013-05-18T14:38:55.598Z cpu2:8688)<4>IPMI message handler: This message has repeated 30 times: BMC returned incorrect response expected netfn b cmd 23, got netfn 9 cmd 23

2013-05-18T14:38:56.203Z cpu2:8688)<4>IPMI message handler: This message has repeated 31 times: BMC returned incorrect response expected netfn b cmd 23, got netfn 9 cmd 23

2013-05-18T14:39:03.117Z cpu2:8688)<4>IPMI message handler: This message has repeated 32 times: BMC returned incorrect response expected netfn b cmd 11, got netfn 5 cmd 11

2013-05-18T14:39:04.217Z cpu0:8688)<4>IPMI message handler: This message has repeated 33 times: BMC returned incorrect response expected netfn b cmd 11, got netfn 5 cmd 11

0 Kudos
Highlighted
Beginner
41 Views

Vmware say:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=200193... VMware KB: The ESXi/ESX host logs report the message: IPMI message handler: BMC returned incorrect response

Resolution

If these messages are reported occasionally in the log files, you can safely ignore them. However, if the log file contains a log spew of this message, they may be symptomatic of an underlying issue. In this case, try one of the options:

  • Update the BMC firmware and system BIOS to the latest version. For more information, consult your hardware vendor.

     

     

  • Update the IPMI driver and SFCB CIM components on the ESX/ESXi host to the latest version. Search the knowledge base and the http://downloads.vmware.com/go/selfsupport-download Patch Download Center for IPMI and CIM patches.

     

     

  • If the hardware health status information is not required or used, disable the CIM agent on the host. For more information, see /message/search.do?cmd=displayKC&externalId=1025757 How to disable the CIM agent on the ESX/ESXi host (1025757).
0 Kudos
Highlighted
Beginner
41 Views

the problem occurs only with ESXi

everything works perfectly with Knoppix

Starting Esxi After a few minutes the problem appears....

The Chassis fans run at full speed for a few seconds every 2/3 minutes

0 Kudos
Highlighted
Employee
41 Views

Hmm, so however ESXi is querying the BMC through IPMI, the board doesn't recognize the query enough to even bother logging it in the SEL.

I'm guessing you already tried those three suggestions from VMware, and they didn't help at all?

0 Kudos
Highlighted
Beginner
41 Views

Yes i have already tried suggestions from VmWare.

0 Kudos
Highlighted
Beginner
41 Views

I noticed that the problem occurs after every reboot for about 2 hours.

After about two hours the problem disappears.

0 Kudos