Home » vSphere » vSphere 5 on HP DL380 G7 with hardware warning status

vSphere 5 on HP DL380 G7 with hardware warning status

After installing the latest HP Offline bundle my server returned a hardware warning status, so the investigation started. Before upgrading the HP drivers there was no error so i had to be something in the driverpack from HP.

In my setup the affected server is a HP DL380 G7 with a P410i Arraycontroller.
The affected offline bundle is: hp-esxi5.0uX-bundle-1.4-16.zip

Solution: Remove the selected component and install an older version

First download the working offline bundle: hp-esxi5.0uX-bundle-1.3.5-3.zip
Upload the zip file to the datastore on the server.

Now we have to remove affected SMX package, so you have to SSH into you vSphere server and type the following command:

esxcli software vib remove -n hp-smx-provider

After completing the command you will see:

Removal Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed:
   VIBs Removed: Hewlett-Packard_bootbank_hp-smx-provider_500.03.02.00.23-434156
   VIBs Skipped:

Now you’re ready to install the older bundle.
From the SSH commandline go to the datastore (for example: cd /vmfs/volumes/datastore1), this will give you the full path to the uploaded zip file.
Execute the following command:

esxcli software vib install -d /vmfs/volumes/<datastoreid>/hp-esxi5.0uX-bundle-1.3.5-3.zip

After completing the command you will see:

Installation Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed: Hewlett-Packard_bootbank_hp-ams_500.9.2.0-11.434156, Hewlett-Packard_bootbank_hp-smx-provider_500.03.01.10.2-434156
   VIBs Removed: Hewlett-Packard_bootbank_hp-ams_500.9.3.0-13.434156
   VIBs Skipped: Hewlett-Packard_bootbank_char-hpcru_5.0.3.09-1OEM.500.0.0.434156, Hewlett-Packard_bootbank_char-hpilo_500.9.0.0.9-1OEM.500.0.0.434156

Now restart you server for the changes to be effective.
It will take some time, but in the end you will see all green hardware status again.

 

Check Also

Error: The parent virtual disk has been modified since the child was created

I was restoring a Virtual Machine with Veeam Backup and Recovery, which seemed to be …

Leave a Reply

Your email address will not be published. Required fields are marked *