Software Delivery Repository

Software Delivery Repository   |   Getting Started   |   FAQ  |  Repositories

Firmware Pack for ProLiant (Gen9 and earlier)

For Gen10 and later, please see the production Firmware Pack for ProLiant

The HPE Firmware Pack for ProLiant (FWPP) provides rpm-packaged firmware for various ProLiant system boards, host adapters, nics and other complex logic devices. Installing an rpm stages the firmware payload and flasher utility on your Linux filesystem. The flasher may then be run manually, or via a system configuration manager like HPE SUM. Once the rpm is installed (rpm -Uvh packagename.rpm), you'll find the firmware and flash utility in

    /usr/lib/x86_64-linux-gnu/hp-firmware-type-vendor-version/

Simply run "./setup" in this directory to flash the component on the target host.

You can access the FWPP repository with your web browser (or dnf/yum, or zypper) using the following https URL syntax:

    https://downloads.linux.hpe.com/SDR/repo/fwpp-gen9

Similarly for rsync:

    rsync -avH rsync.linux.hpe.com::FIRMWARE/repo/fwpp-gen9

For a technical overview and FAQ about the transition from scexe to rpm, please see this customer announcement.

  Browse Gen9

Browse Gen8

what's my gen?

Gen10 and later?




Subscribe your system to the fwpp repository


Red Hat Enterprise Linux

Cut-n-paste the following section (substituting ditribution, architecture and project version) into /etc/yum.repos.d/fwpp.repo on your RedHat system:

[fwpp]
name=Firmware Pack for ProLiant
baseurl=https://downloads.linux.hpe.com/SDR/repo/repo_generation/rhel/dist_ver/arch/project_ver/
enabled=1
gpgcheck=1
gpgkey=https://downloads.linux.hpe.com/SDR/hpPublicKey2048_key1.pub,https://downloads.linux.hpe.com/SDR/hpePublicKey2048_key1.pub,https://downloads.linux.hpe.com/SDR/hpePublicKey2048_key2.pub

Please replace repo_generation, dist_ver, arch, and project_ver with the values appropriate for your environment.


Where:

   repo_generation         fwpp-gen9, fwpp-gen8    (what's my gen?)
   dist_ver                6, 7, 8
   arch                    x86_64  
   project_ver (Gen9)      current, next, gen9.1, 2022.03.0, 2021.05.0, 2020.09.0, 2020.03.0, 2019.12.0, 2019.09.0
   project_ver (Gen8)      current, gen8.1_hotfix9, gen8.1_hotfix2, gen8.0_postprod, ...
        

      current is an accumuilation of all firmwrae from every Service Pack for ProLiant
      next is firmware scheduled to go into the next Service Pack for ProLiant



SUSE Linux Enterprise Server

Cut-n-paste the following section (substituting ditribution, architecture and project version) into /etc/zypp/repos.d/fwpp.repo on your SUSE system:

[fwpp]
name=Firmware Pack for ProLiant
baseurl=https://downloads.linux.hpe.com/repo/repo_generation/suse/dist_ver/arch/project_ver/
enabled=1
autorefresh=1
type=rpm-md
keeppackages=0
gpgcheck=1
gpgkey=https://downloads.linux.hpe.com/SDR/hpePublicKey2048_key1.pub,https://downloads.linux.hpe.com/SDR/hpePublicKey2048_key2.pub


Please replace repo_generation, dist_ver, arch, and project_ver with the values appropriate for your environment.


Where:

   repo_generation         fwpp-gen9, fwpp-gen8   (what's my gen?)
   dist_ver                11, 12, 15
   arch                    x86_64  
   project_ver (Gen9)      current, next, 2022.03.0, 2021.10.0, 2021.05.0, 2020.09.0, 2020.03.0, 2019.12.0
   project_ver (Gen8)      current, gen8.1_hotfix9, gen8.1_hotfix2, gen8.0_postprod, ... 
        

      current is an accumuilation of all firmwrae from every Service Pack for ProLiant
      next is firmware scheduled to go into the next Service Pack for ProLiant



Installing fwpp packages


List hp-firmware packages

# yum search firmware


Install a specific package

# yum install packagename


NOTE: this simply stages the flash utility and firmware payload on your filesystem at /usr/lib/x86_64-linux-gnu/hp-firmware-type-vendor-version/ . Run "./setup" in this directory to physically flash the firmware. HPE SUM firmware RPM commands may also be used to manage and flash the staged firmware onto the local system. HPE SUM GUI, CLI, InputFile and interactive CLI modes require the full RPM files instead of installed RPMs. See the HPE Smart Update Manager User Guide's chapter on Deploying Firmware RPMs at http://www.hpe.com/info/hpsum/documentation for more information.


Contact