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;
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.
44,632 total views, 26 views today
