There is a bug in the latest HP ESXi 5.0 bundle update 1.6 (released Jan/Feb 2013) which reports a hardware status warning with your HP Smart Array P410 controller.
Once you install the latest VIB’s you will see this warning on the hardware status tab;
To fix this;
- Remove the VIB’s for HP ESXi 5.0 Complete Bundle Update 1.6
- Deploy the previous stable version HP ESXi 5.0 Complete Bundle Update 1.5
Since I am more comfortable using Powershell than the console I used a combination of a SSH session and Powershell to resolve this.
Walkthrough;
From the console I first confirmed the Vendor (Hewlett-Packard) and Install Date (2013-03-21) so that I could use these in my Powershell filter. The highlighted rows are the relevant ones.
~ # esxcli software vib list | grep hp Name Version Vendor Acceptance Level Install Date -------------------- ---------------------------------- --------------- ---------------- ------------ char-hpcru 5.0.3.09-1OEM.500.0.0.434156 Hewlett-Packard PartnerSupported 2012-11-13 char-hpilo 500.9.0.0.9-1OEM.500.0.0.434156 Hewlett-Packard PartnerSupported 2012-04-11 hp-ams 500.9.3.0-13.434156 Hewlett-Packard PartnerSupported 2013-03-21 hp-smx-provider 500.03.02.00.23-434156 Hewlett-Packard VMwareAccepted 2013-03-21 hpacucli 9.40-12.0 Hewlett-Packard PartnerSupported 2013-03-21 hpbootcfg 01-01.02 Hewlett-Packard PartnerSupported 2013-03-21 hponcfg 04-00.10 Hewlett-Packard PartnerSupported 2013-03-21 ata-pata-hpt3x2n 0.3.4-3vmw.500.0.0.469512 VMware VMwareCertified 2012-03-26 scsi-hpsa 5.0.0-17vmw.500.0.0.469512 VMware VMwareCertified 2012-03-26 hpnmi 2.0.11-434156 hp PartnerSupported 2012-04-11
Now I created a Powershell script using the above Vendor and Install Date. This is a dry run to test the script againist a specific host without making any changes.
Dry Run;
Remember to change the highlighted rows to reflect your own environment.
## Connect to a specific ESXi 5.0 host $VMHost = "MyServer.MyDomain.fqdn" Connect-VIServer $VMHost -User 'username' -Password 'password' ## Expose the ESXCLI functionality $esxcli = Get-EsxCli -vmhost $VMHost ## Show VIB's installed on a specific date for a specific Vendor $esxcli.software.vib.list() ` | where {$_.InstallDate -eq "2013-03-21" -and $_.Vendor -match "Hewlett-Packard"} ` | Format-Table -AutoSize ## Get VIB Names : HP VIB's installed on a specific date $VIBS = $esxcli.software.vib.list() ` | where {$_.InstallDate -eq "2013-03-21" -and $_.Vendor -match "Hewlett-Packard"} ` | Select Name ## DRYRUN : Remove HP VIB's installed on a specific date Foreach ($VIB in $VIBS) { $esxcli.software.vib.remove($true, $false, $false, $false, $VIB.Name) }
Results;
This confirms that the correct VIB’s are filtered in the query;
This confirms the dry run removal of VIB’s;
Remove VIB’s;
Now you can commit the changes by changing the dryrun option from $false to $null;
## Connect to a specific ESXi 5.0 host $VMHost = "MyServer.MyDomain.fqdn" Connect-VIServer $VMHost -User 'username' -Password 'password' ## Expose the ESXCLI functionality $esxcli = Get-EsxCli -vmhost $VMHost ## Get VIB Names : HP VIB's installed on a specific date $VIBS = $esxcli.software.vib.list() ` | where {$_.InstallDate -eq "2013-03-21" -and $_.Vendor -match "Hewlett-Packard"} ` | Select Name ## LIVE : Remove HP VIB's installed on a specific date Foreach ($VIB in $VIBS) { $esxcli.software.vib.remove($null, $false, $false, $false, $VIB.Name) }
Refer to the vSphere documentation for ESXCLI options, and Robert van den Nieuwendijk blog for the ESXCLI syntax;
#$esxcli.software.vib.remove(boolean dryrun, boolean force, boolean maintenancemode, boolean noliveinstall, string[] vibname)
Results;
The message informs you that the update (removing the VIB’s) was successful, and you can now reboot the host.
When the host comes back up, you can check the Hardware Status tab and will notice two things;
-
The warning message has gone
- There are hardware sensors missing (for example storage)
Now all you need to do is deploy the previous stable version. I used VUM to deploy HP ESXi 5.0 Complete Bundle Update 1.5, but you could just as easily do this from the console using ESXCLI.
As you can see in the impact column, this requires a reboot, after which the Harware Status tab reports correctly with no warnings;
Now repeat this on all affected hosts – job done!
212,426 total views, 128 views today
Howzit
I have stumbled across your article – thanks for the detail on this. I have one question. I get quite a few hits on the vib list as seen below. Do I only remove the VIBS you have mentioned in the article or do I have to remove all the HP VIBS – i.e. ilo etc
Thanks
Arthur
AcceptanceLevel CreationDate ID InstallDate Name Status Vendor Version
————— ———— — ———– —- —— —— ——-
PartnerSupported 2012-08-30 Hewlett-Packard_bootbank_char-hpcru_5.0.3.09-1OEM.500.0.0.434156 2013-03-20 char-hpcru Hewlett-Packard 5.0.3.09-1OEM.500.0.0.434156
PartnerSupported 2011-10-07 Hewlett-Packard_bootbank_char-hpilo_500.9.0.0.9-1OEM.500.0.0.434156 2013-03-20 char-hpilo Hewlett-Packard 500.9.0.0.9-1OEM.500.0.0.434156
PartnerSupported 2012-11-30 Hewlett-Packard_bootbank_hp-ams_500.9.3.0-13.434156 2013-03-20 hp-ams Hewlett-Packard 500.9.3.0-13.434156
PartnerSupported 2013-01-04 Hewlett-Packard_bootbank_hp-build_5.34.23-434156 2013-03-20 hp-build Hewlett-Packard 5.34.23-434156
VMwareAccepted 2012-12-03 Hewlett-Packard_bootbank_hp-smx-provider_500.03.02.00.23-434156 2013-03-20 hp-smx-provider Hewlett-Packard 500.03.02.00.23-434156
PartnerSupported 2012-12-13 Hewlett-Packard_bootbank_hpacucli_9.40-12.0 2013-03-20 hpacucli Hewlett-Packard 9.40-12.0
PartnerSupported 2012-04-05 Hewlett-Packard_bootbank_hpbootcfg_01-01.02 2013-03-20 hpbootcfg Hewlett-Packard 01-01.02
PartnerSupported 2011-11-13 Hewlett-Packard_bootbank_hponcfg_04-00.10 2013-03-20 hponcfg Hewlett-Packard 04-00.10
VMwareCertified 2012-08-24 Hewlett-Packard_bootbank_scsi-hpsa_5.0.0-40OEM.500.0.0.472560 2013-03-20 scsi-hpsa Hewlett-Packard 5.0.0-40OEM.500.0.0.472560
PartnerSupported 2012-11-30 Hewlett-Packard_bootbank_scsi-hpvsa_5.0.0-50OEM.500.0.0.472560 2013-03-20 scsi-hpvsa Hewlett-Packard 5.0.0-50OEM.500.0.0.472560
VMwareAccepted 2011-10-07 Hewlett-Packard_bootbank_vmware-esx-hp_vaaip_p2000_2.1.0-2 2013-03-20 vmware-esx-hp_vaaip_p2000 Hewlett-Packard 2.1.0-2
Howzit Arthur,
You only need to remove the VIB’s listed in the article, the others can stay on the host. You could probably get away with only removing “hp-ams” and “hp-smx-provider”, but I would remove all VIB’s associated with this package so that you have a clean set of VIB’s with a specific package version.
Looking at your list provided, remove these;
AcceptanceLevel CreationDate ID InstallDate Name Status Vendor Version
————— ———— — ———– —- —— —— ——-
PartnerSupported 2012-11-30 Hewlett-Packard_bootbank_hp-ams_500.9.3.0-13.434156 2013-03-20 hp-ams Hewlett-Packard 500.9.3.0-13.434156
VMwareAccepted 2012-12-03 Hewlett-Packard_bootbank_hp-smx-provider_500.03.02.00.23-434156 2013-03-20 hp-smx-provider Hewlett-Packard 500.03.02.00.23-434156
PartnerSupported 2012-12-13 Hewlett-Packard_bootbank_hpacucli_9.40-12.0 2013-03-20 hpacucli Hewlett-Packard 9.40-12.0
PartnerSupported 2012-04-05 Hewlett-Packard_bootbank_hpbootcfg_01-01.02 2013-03-20 hpbootcfg Hewlett-Packard 01-01.02
PartnerSupported 2011-11-13 Hewlett-Packard_bootbank_hponcfg_04-00.10 2013-03-20 hponcfg Hewlett-Packard 04-00.10
Leave these as they are;
AcceptanceLevel CreationDate ID InstallDate Name Status Vendor Version
————— ———— — ———– —- —— —— ——-
PartnerSupported 2012-08-30 Hewlett-Packard_bootbank_char-hpcru_5.0.3.09-1OEM.500.0.0.434156 2013-03-20 char-hpcru Hewlett-Packard 5.0.3.09-1OEM.500.0.0.434156
PartnerSupported 2011-10-07 Hewlett-Packard_bootbank_char-hpilo_500.9.0.0.9-1OEM.500.0.0.434156 2013-03-20 char-hpilo Hewlett-Packard 500.9.0.0.9-1OEM.500.0.0.434156
PartnerSupported 2013-01-04 Hewlett-Packard_bootbank_hp-build_5.34.23-434156 2013-03-20 hp-build Hewlett-Packard 5.34.23-434156
VMwareCertified 2012-08-24 Hewlett-Packard_bootbank_scsi-hpsa_5.0.0-40OEM.500.0.0.472560 2013-03-20 scsi-hpsa Hewlett-Packard 5.0.0-40OEM.500.0.0.472560
PartnerSupported 2012-11-30 Hewlett-Packard_bootbank_scsi-hpvsa_5.0.0-50OEM.500.0.0.472560 2013-03-20 scsi-hpvsa Hewlett-Packard 5.0.0-50OEM.500.0.0.472560
VMwareAccepted 2011-10-07 Hewlett-Packard_bootbank_vmware-esx-hp_vaaip_p2000_2.1.0-2 2013-03-20 vmware-esx-hp_vaaip_p2000 Hewlett-Packard 2.1.0-2
Cheers bru,
Jon
Thanks a million.
You have been a great help!
Arthur
The latest HP Offline Bundle fixes the issues with the hardware status warning
http://vibsdepot.hp.com/hpq/apr2013/
Hi Rotem,
Thanks for the update, I will test this today.
Cheers – Jon
Fix confirmed;
https://jonmunday.net/2013/04/16/fix-hp-esxi-5-x-management-bundles/
It’s actually a nice and helpful piece of info. I am happy that you just shared this useful info with us. Please stay us up to date like this. Thanks for sharing.
Hi,
Do you also get vCenter client login an event every minute?
User root logged in
User root logged out
This has happen to me after installing HP Agentless Management Service Offline Bundle for VMware ESXi 5.x version 9.3.5
How can I stop this?