Setting up a repository for Patch / Firmware install.

[Juan Carlos Olaya]

Are there instructions as to how to set up a repository for Firmware upgrades etc?
I am trying to install on a lab server in order to deploy to all other servers, but confused as to where to start. fairle new to this.

Thank you,

[Steven E. Protter]

Shalom,

Firmware generally is not delivered via rpm. Therefore a traditional rpm repo is not going to help (probably not).

The steps to take are:

1) Look at the hardware specific instructions. Some use ftp, some use tftp, some use a .bin file.

2) Based on the instructions, set up a share directory that meets the needs.

SEP

[Brendan Murphy_5]

For more long term use (& funding permitted), I suggest you examine the possibility of using HP SIM & RDP. These two apps used in conjunction provide a powerful monitoring & management capability. You can use these for patch, firmware & OS deployment ... for both windows & Linux on all proliant & integrity platforms. I believe solaris has recently been included too.

[Gerardo Arceri]

We perform firmware upgrades from a central NFS server which contains the Firmware CD ISO image.
we then copy it to /var/tmp and run the FW Upgrade, basically
#!/bin/bash
FWISO=FW900.2010_0403.93.iso

mkdir /mnt/firmware
cp /mount/nfs/$FWISO /var/tmp
mount -o loop,ro -t iso9660 /var/tmp//$FWISO /mnt/firmware
cd /mnt/firmware
./hpsum /romonly /silent

Check logs on /var/hp/log/localhost for errors.
Firmware can take anywhere between 2 and 15 minutes depending on how old the current FW is.
BTW, if you are running a 64Bit OS, you need to install the following dependencies:
libXrender.i386
libXrandr.i386
freetype.i386
fontconfig.i386
libXfixes.i386
libXcursor.i386

From the redhat distribution media or use yum to install them.
This method has been used to upgrade most of our large installed base of Blade/Proliant Servers without a hitch.