Solved: ESX 3.5 U2 - Health status warning

jbusink · ‎07-30-2008

We just upgraded to 3.5U2 and VC2.5U2 and now we're getting server health warnings on all servers ("ProcHot for System Board 2 - Normal") for some reason. All machines are HP Proliant DL385G2 with the latest HP tools installed (v8.1). The HP tools don't show any hardware degradation and everything is running just fine, yet VC keeps complaining. Anyone else having the same issue?

rreynol · ‎08-25-2008

I finally opened a case with HP to get their side of the story. Here it is, basically the prochot reading should be for Intel only. AMD users can ignore the warnings:

"Please ignore this ProcHot warning for any host with AMD CPUs. The ProcHot flag is an Intel only health status flag.

This is an issue with the VMware Cim Server on the ESX.

We already have opened a VMWare support request, and they're still working on it.

As the health status system is being improved we hope to see this issue resolved in a future update/release."

View solution in original post

anttijf · ‎07-30-2008

Yes! I have same issue. Under "Other" there is warning about "ProcHot for System Board 3 - Normal". Server is HP Proliant BL685c G1. (Same error on all servers.) HP agents are 800a and they are showing that all is ok.

I believe that this information is pulled from CIM, is there any possibility to disable this sensor?

willwgm3 · ‎07-30-2008

Same issue here. I've installed on 6 585G2's so far and am getting the ProcHot warning as well, but for System Board 8. I'm gonna go poke around the BIOS and see if there are any clues in there.

-Will

willwgm3 · ‎07-30-2008

I've tried a few things to resolve this. I updated the firmware to the latest release and checked the BIOS for any options for this sensor. No luck yet. I'm guessing that it is a thermal sensor that VMware hasn't accounted for yet.

-Will

jbusink · ‎07-30-2008

No solution yet. Just a quick observation: So far everyone who has posted here seems to be running HP hardware with AMD CPUs.

I can also confirm that a firmware upgrade does not help as we installed the latest FW just before we upgraded to 3.5U2.

dconvery · ‎07-31-2008

From what I understand, the monitoring is all through CIM, not the HP SIM agents. Did anyone try to uninstall the HP agent? I haven't used U2 in an AMD server yet, so I can't "play".

Dave Convery, VCDX-DCV #20 ** http://www.tech-tap.com ** http://twitter.com/dconvery ** "Careful. We don't want to learn from this." -Bill Watterson, "Calvin and Hobbes"

mimo17 · ‎07-31-2008

Hello

Just that you see that you are not allone.

We have as well HP585 G5 Quad Core with HP FW 8.10 and Agents 8.10. As well the ProcHot warning for System Board 8.

I cannot find anything in the System Management Homepage.

HP - do you provide 8.10a soon?

Michael

alevinson · ‎08-02-2008

Having the same problem on BL465c's with latest firmware, HP and VMware 3i, 3.5.0, 103909 . The problem appeared after the VMware updates. Error is "ProcHot for System Board 2 - Normal" I do not think it is possible to remove the CIM agents, and probably not desired.

vjasonsum · ‎08-04-2008

Same issue after upgrading our bl465c blades to esx 3.5 update 2

The original release did not report this. I too cannot find anything wrong with the hardware.

wally · ‎08-05-2008

Same issue here with our DL385G2 servers, "prochot for system board 2 - normal", we also have DL385G1 servers but they don't have this issue.

All servers run firmware from the hp firmware cd 8.1

willwgm3 · ‎08-05-2008

I've got some new G5 AMD 465c blades and 585's that just arrived yesterday. Gonna put 3i on them today or tomorrow and see if they report the same error. I'll keep you all posted.

-Will

vjasonsum · ‎08-05-2008

After spending a few hours on this it appears to be a problem with the HP agent

If it is uninstalled I get a status of unknown

mansof · ‎08-05-2008

Same here with my 6 HP BL465c. AMD based blades.

Is the warning harmful, or it is just a false alarm?

It is buggy but as long as it is a false alarm I am OK?

Does anybody knows this.

-Francisco

vjasonsum · ‎08-05-2008

I have not had any trouble out side of being annoying. So far I only have 2 days of run time however compared with 250 days prior to the update.

rreynol · ‎08-06-2008

We get the same prochot warnings on our DL585 G5 hardware, with current BIOS (8.1). Will watch this thread to see if any fixes are found.

JarettK · ‎08-06-2008

Seeing this as well with 1 of my 3 DL385 w/ ESX 3.5 U2. No agents installed. It was a fresh install of 3.5 U2 this morning

My 2 DL385 G2 that don't see it were cold upgrades to 3.5U2 from 3.5U1 and interim patches.

meistermn · ‎08-07-2008

Same Problem with HP 585 G5.

Tried : http://www.yellow-bricks.com/2008/08/05/health-status-not-showing/

Does not help.

Anyone open an SR?

meistermn · ‎08-07-2008

Did an SR and VMware told following:

Health Status is a new feature in ESX 3.5 Update 2.

It reports information received from the IPMI interface of the server.

IPMI is a hardware architecture for reporting information about hardware components.

PROCHOT monitors the CPU temperature and checks if the maximum safe operating temperature has been reached.

If you are receiving alerts, it means that the hardware is reporting high values.

This may not indicate a CPU temperature problem but I recommend contacting your hardware vendor for additional information regarding IPMI and for processor temperature guidelines/information.

mansof · ‎08-07-2008

It looks for all of us that all our AMD CPUs are having temperature problem, unlike Intel CPUs..

It just looks to me that some thresholds have not been successfully set up and

VMWare is the one that has to contact AMD to change the thresholds for AMD chip temperature.

Is there any way to increase that threshold?

wally · ‎08-07-2008

That's not correct, we have 10 DL385G1 servers with the exact same dual core opterons that we have in our DL385G2 servers. We don't have this warning on our G1 boxes, only on our G2's.