FIX : HP ESXi 5.x Management Bundles

HP have just released updated VIB’s to address the bug in the Feb2013 release of the ESXi management bundles.

Download both ZIP files and import them into your VUM repository for deployment;

Remediate using VUM;

VUM-HP-VIB-April-2013

A quick check before deploying the updates confirms your current versions;


~ # 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.2.0-11.434156                 Hewlett-Packard  PartnerSupported  2013-03-25
hp-smx-provider       500.03.01.10.2-434156               Hewlett-Packard  VMwareAccepted    2013-03-25
hpacucli              9.20-9.0                            Hewlett-Packard  PartnerSupported  2013-03-25
hpbootcfg             01-01.02                            Hewlett-Packard  PartnerSupported  2013-03-25
hponcfg               04-00.10                            Hewlett-Packard  PartnerSupported  2013-03-25
hpnmi                 2.0.11-434156                       hp               PartnerSupported  2012-04-11

After remediation;

You can see that two packages have been updated;


~ # 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.5-02.434156                 Hewlett-Packard  PartnerSupported  2013-04-16
hp-smx-provider       500.03.02.10.4-434156               Hewlett-Packard  VMwareAccepted    2013-04-16
hpacucli              9.20-9.0                            Hewlett-Packard  PartnerSupported  2013-03-25
hpbootcfg             01-01.02                            Hewlett-Packard  PartnerSupported  2013-03-25
hponcfg               04-00.10                            Hewlett-Packard  PartnerSupported  2013-03-25
hpnmi                 2.0.11-434156                       hp               PartnerSupported  2012-04-11

Now looking at the hardware status tab, you can see that the this update correctly addresses the bug – no hardware warning for the array controller.

Hardware-Status

56,545 total views, 21 views today

BUG : HP ESXi 5.0 Complete Bundle Update 1.6

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;

HP Smart Array P410 Controller warning

To fix this;

  1. Remove the VIB’s for HP ESXi 5.0 Complete Bundle Update 1.6
  2. 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;

HP-VIB-bundle-1-6

This confirms the dry run removal of VIB’s;

Dryrun-VIB-Remove

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)

ESXCLI-options

Results;

The message informs you that the update (removing the VIB’s) was successful, and you can now reboot the host.

Live-VIB-Remove

When the host comes back up, you can check the Hardware Status tab and will notice two things;

  1. The warning message has gone
  2. There are hardware sensors missing (for example storage)

Hardware-Status-VIB-remove

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.

HP-VIB-bundle-1-5-remediate

As you can see in the impact column, this requires a reboot, after which the  Harware Status tab reports correctly with no warnings;

Hardware-Status-VIB-resolved

Now repeat this on all affected hosts – job done!

181,328 total views, 8 views today