DL585 G5 HP Vsphere CIM providers – ESXi bundle

Vsphere is a perfect choice for consolidating servers and to better utilize the hardware. We currently use HP DL585 G5 AMD powered workhorses powered by Vsphere 4.0 ESXi and Virtual Center reports hardware alert (under the tab Hardware Status):

1 Warning: System Board 8 ProcHot out of 111 sensors.

In vSphere 3.5 we easily solved the problem by installing HP ESXi CIM providers for Vmware 3.5. I went to the HP site and found HP ESXi providers for vSphere 4 (file name: hp-esxi4.0uX-bundle-1.1.zip). I downloaded and used vihostupdate.pl to update the server. Remember that you need to put it in Maintenance mode and then a reboot will be required – make sure you do migrate all virtual servers to a different vmware host.

I installed Vmware vSphere CLI on the Windows workstation – it does come with ActivePerl installation that’s automatically installed as well.

I scanned the remote Vmware vSphere server to make sure the bundle has not been installed before.

C:Program FilesVMwareVMware vSphere CLIbin>vihostupdate.pl –server vsphere1.ourcompany.com –scan –bundle ./hp-esxi4.0uX-bundle-1.1.zip

I got the following reply:

The bulletins which apply to but are not yet installed on this ESX host are listed.

———Bulletin ID———   —————-Summary—————–
hpq-esxi4.0uX-bundle-1.1        HP ESXi Bundle 1.1

I did install (“patch” the Vmware host) downloaded HP ESXi Bundle:

C:Program FilesVMwareVMware vSphere CLIbin>vihostupdate.pl –server vsphere1.ourcompany.com –install –bundle ../bundles/hp-esxi4.0uX-bundle-1.1.zip –bulletin hpq-esxi4.0uX-bundle-1.1

After entering username and password it took a while, perhaps one or two minutes. The update was successful:

The update completed successfully, but the system needs to be rebooted for the changes to be effective.

I did rescan the box once again with vihostupdate.pl utility:

C:Program FilesVMwareVMware vSphere CLIbin>vihostupdate.pl –server vsphere1.ourcompany.com –scan –bundle ../bundles/hp-esxi4.0uX-bundle-1.1.zip

I got the following response:

The bulletins which apply to but are not yet installed on this ESX host are listed.

———Bulletin ID———   —————-Summary—————–

Update was fully successful! Now let’s reboot the box and see if hardware sensors are fixed…. Ooops, guess what? The Hardware Status tab still shows the same error – the only thing I noticed is that sensors amount changed from 111 to 125. Unfortunately, the warning still persists.

Server type: HP DL585 G5, 4 CPU QUAD core monster powered by AMD 8347 HE. 4x vSphere 4.0 Enterprise licenses. BIOS A07 8.60.


Comments

  1. Olu says:

    Got same error but different staus report

    System Board 8 ProcHot “Status Current state limit exceeded”

    Vmware suggest the following fix

    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013850

    After applying the fix, still no joy, anyone with any idea?

  2. Hello

    You say that the problems was in esxi 3.5 but you downloaded the sim for 4.0 does the sim for esxi 4.0 works in esxi 3.5?

    Regards Kenneth Dalbjerg

Leave a Reply