This document provides information about the installation of Licensed Machine
or Licensed Internal Code, which is sometimes referred to generically as
microcode or firmware.
The firmware level in this package is:
Go to the following URL to access the HMC code packages:
NOTE: You must be logged in as hscroot in order for the firmware installation to complete correctly.Firmware updates should be performed on an entire Managed Frame and all
Managed Systems
contained in that frame at one time. The following instructions
can be used to update
one Managed Frame and all Managed Systems that it contains. The
instructions can be
repeated as many times as needed until all Managed Frames have been
updated.
1) Power off all Managed Systems in the Managed Frame
2) Reinstall the current firmware level on all Managed Systems in the Managed Frame:
The following command can be used to determine the current firmware level:
lslic -t sys -m <managedsystem_1> -F activated_level
The following command will retrieve and reinstall the current
firmware level on
one Managed System:
updlic -o a -m <managedsystem_1> -t sys -l <current_fsp_level> -r <repos>
<current_fsp_level> is the level determined with the lslic command.
<repos> is the location of the firmware
such as "-r dvd", "-r ibmwebsite", etc.
Additional parameters might be required,
depending on the repository selection.
If the firmware has already been retrieved
to the HMC, the HMC hard drive (-r disk)
should be used as the repository.
After the firmware has been retrieved to the HMC, the HMC
hard drive (-r disk) should
be used as the repository to update the remaining Managed
Systems:
updlic -o a -m <managedsystem_2> -t
sys -l <current_fsp_level> -r disk
updlic -o a -m <managedsystem_3>
-t sys -l <current_fsp_level> -r disk
......
updlic -o a -m <managedsystem_N>
-t sys -l <current_fsp_level> -r disk
These commands can be run in the background in parallel to speed up the processing.
Wait for all updlic commands to complete before proceeding to step 3.
3) Install and activate new BPC firmware only (during this step the Managed
Systems will
transition from "Power Off" to "No Connection" and then
back to "Power Off"):
Select 1 Managed System as the target of the updlic command
and update BPC firmware.
The following command will retrieve firmware from the repository
and update the BPCs:
updlic -o a -m <managedsystem_1> -t power -l latest -r <repos> .....
<repos> is the location of the firmware
such as "-r dvd", "-r ibmwebsite", etc.
Additional parameters might be required,
depending on the repository selection.
If the firmware has already been retrieved
to the HMC, the HMC hard drive (-r disk)
should be used as the repository.
4) Wait for all Managed Systems to return to "Power Off" state.
5) Install and activate new firmware on all Managed Systems in the Managed Frame.
updlic -o a -m <managedsystem_1> -t sys -l latest -r <repos> .....
<repos> is the location of the firmware
such as "-r dvd", "-r ibmwebsite", etc.
Additional parameters might be required,
depending on the repository selection.
If the firmware has already been retrieved
to the HMC, the HMC hard drive (-r disk)
should be used as the repository.
After the firmware has been retrieved to the HMC, the HMC
hard drive (-r disk) should
be used as the repository to update the remaining Managed
Systems:
updlic -o a -m <managedsystem_2> -t
sys -l latest -r disk
updlic -o a -m <managedsystem_3>
-t sys -l latest -r disk
......
updlic -o a -m <managedsystem_N>
-t sys -l latest -r disk
These commands can be run in the background in parallel to speed up the process.
Wait for all updlic commands to complete before proceeding to step 6.
6) Power on the Managed SystemsNote: The file names and service pack levels used in the following
examples are for clarification only, and are not
necessarily levels that have been, or will be released.
Power Subsystem firmware file naming convention:
02EPXXX_YYY_ZZZ
An installation is disruptive if:
An installation is concurrent if:
Firmware Information and Update Description
Filename | Size | Checksum |
02EP330_104_078.rpm | 18,138,429 | 04648 |
EP330_104_078 04/26/2010 |
Impact: Availability
Severity: ATT
|
EP330_095_078 08/31/2009 |
Impact: Serviceability Severity: SPE
|
EP330_092_078 05/18/2009 |
Impact: Serviceability Severity: SPE
|
EP330_078_078
01/15/2009 |
Impact: Function Severity: Hiper
|
EP330_057_029
10/20/2008 |
Impact: Function
Severity: Hiper
|
EP330_054_029
09/22/2008 |
Impact: Function
Severity: Hiper
|
EP330_049_029
08/28/2008 |
Impact: Function
Severity: Hiper
|
EP330_029_029
06/10/2008 |
Impact: Function
Severity: Hiper
|
EP330_017_017
05/13/2008 |
Impact: New
Severity: New
|
http://www14.software.ibm.com/webapp/set2/firmware/gjsn
Follow the instructions on this web page. You must read and agree to the license agreement to obtain the firmware packages.
In the drop-down box, choose the entry for your specific machine type and model.
You may download the individual .rpm and .xml files for Power Subsystem firmware from this location to your server, an ftp server, or a CD-ROM (both files are required). Make sure the file names have the format 02EP3xx_yyy_zzz, with an extension of .rpm and .xml before copying them to your server, an ftp server or CD-ROM. If using a CD-ROM, copy the .rpm and .xml files to the CD-ROM using a local CD-ROM burner utility.
Another method is to download the .iso file and create a CD-ROM to use with your HMC.
Note: If your HMC is not internet-connected you will need to download
the new firmware level to a CD-ROM or ftp server.
Example: EPXXX_YYY_ZZZ
Where XXX = release level