This morning a little birdie pointed me to an HP Reference Architecture document that is hot off the press: HP BladeSystem Reference Architecture: HP Virtual Connect Flex-10 and VMware vSphere 4.0 which appears to be the vSphere 4.0 update to the previous reference architecture HP produced for VI3. If you’re running or architecting vSphere deployments with HP blade systems (as a number of my clients are), you should check out this doc.
ESX 3.5 Update 4 Fixes ProcHot Status Issue
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.
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.
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.