Firmware Update via HPSIM

[Annette Jones_2]

ALL,

Want to deploy a firmware update, how is this achieved. I can see all my SSD's and associated components in the VCRM, but not the Firmware updates I have download and placed in the repository. Is this achievable?

ta

[Rob Buxton]

The firmware should show up in the VCA Display if it has been downloaded.
The initial check is to check the catalogue in the VCRM it should be there.
If not, check in the Repository directory there should be the .exe and a .mnf for the file. If not then rescan the Catalogue.
There is an issue where the latest System BIOS for various G3 Servers flags with a green tick in the VCA even if an older version is installed.
You can deploy System, Array and Lights Out ROM from the VCA.
There's also a nifty utility for updating the firmware on the newer NICs.

[Annette Jones_2]

Rob,

These updates I'm talking about do not show in the VCRM, specifically SP28809/SP28813/SP28846. These unpack themselves to create a floppy disk install.

Honestly thought that even firmware updates could be deployed from the CMS.

If you could advise diferently it will be much appreciated.

A

[Claas Kruhoefer]

Hello,

when the images creating Floppies they are cold update BIOS firmwares.

To use the VCRM to upgrade Firmwares, you need the online ROMs from the HP homepage and copy them in the repository folder.

It is not possible to upgrade harddisk firmwares with VRCM.

Hope this helps you

[Annette Jones_2]

The above mentioned updates are online HP updates for ROM on specific servers.

I still thought that this would be deployable through HPSIM. But although I have placed these executables in the Repository, they are not seen for deployment.

Anyone got any ideas or an absolute answer?

A

[David Claypool · Accepted solution]

Okay, sorry to ask about the obvious, but firmware updates are published in a couple of different formats. There is the traditional 'ROMPaq' format that uses a boot from floppy. The other is termed 'Online firmware update' and has both Windows and Linux executables. The Windows executable is delivered in the component pack format and is identified with filename conventions like cpXXXXXX.exe.

[Annette Jones_2]

No it wasn't that obvious, cause I had downloaded the wrong type.

Thanks very much.........simple

[Annette Jones_2]

Another stupid question:
Once I have a BIOS ROM Critical update downloaded, how do I deploy just the update?

I have used HPSIM to deploy SSD's, but not just an update.

When I choose a server to update, on the configured VCRM page, there is no drill down list for the BIOS although its visiable on the CMS VCRM webpage!!!

If this update has to go out as part of an SSD push is it inteligent enough to choose the correct processor version?

Ta

[Annette Jones_2]

Found it:

Even though I bounced the CMS after the repository changes it didn't seem to pick up the BIOS update.

On the Install Software & Firmwate, step 2 install items, I used the last update link and this completed a better refresh than a bounce. Now I can see the BIOS updates as a separate component to install.

[Annette Jones_2]

use the last update to refresh the respository on step 2.