latoga labs

Alliances & Partnership Advising

  • About
  • Contact
  • View latoga’s profile on Twitter
  • View greglato’s profile on LinkedIn

© 2006–2025 · Log in

ESX 3.5 Update 4 Fixes ProcHot Status Issue

April 9, 2009 Leave a Comment

Yesterday one of my customers who runs HP Servers alerted me to a recent VMware KnowledgeBase article.  He was nice enough to annotate the article with some screens shots from his environment.   I received his permission to post this as today’s VMware Admin Guest Blogger.
So, if you’re running HP Servers and been annoyed by the error warning from the Intel ProcHot Sensor, ESX 3.5 Update 4 erases this annoyance.

—

Issue
On HP systems with the Intel PROCHOT sensor, a warning is issued, and yet the PROCHOT label is “Normal.” Furthermore, the HealthState setting of the sensor is “10”. This situation occurs because of an HP firmware issue where the digital discreet sensor asserts conflicting states. Below is a screen shot showing this in vCenter.

esx35u3-prochot-ss

Solution
This issue is resolved in ESX Server 3.5 Update 4 in that these conflicting states are now appropriately managed. Therefore, the sensor’s label and Healthstate setting would now be displayed as “Unknown,” which is proper given the information received from the firmware.

esx35u4-prochot-ss

Filed Under: Virtualization, VMware Tagged With: ESX3.5, HP Servers, ProcHot, Update 4, VMware

About latoga labs

With over 25 years of partnering leadership and direct GTM experience, Greg A. Lato provides consulting services to companies in all stages of their partnering journey to Ecosystem Led Growth.