IBM Flex System p24L Installation And Service Manual page 465

Recovering the system firmware
The system firmware is contained in separate temporary and permanent images in the flash memory of
the compute node. These images are referred to as TEMP and PERM, respectively. The compute node
normally starts from the TEMP image, and uses the PERM image as a backup. If the TEMP image
becomes damaged, such as from a power failure during a firmware update, you can recover the TEMP
image from the PERM image.
About this task
If your system hangs, start the PERM image. See "Starting the PERM image."
Starting the PERM image
You can force the compute node to start the permanent (PERM) image.
About this task
To force the compute node to start the PERM image, see http://publib.boulder.ibm.com/infocenter/
flexsys/information/topic/com.ibm.acc.psm.hosts.doc/dpsm_managing_hosts_power_firmware.html.
Starting the TEMP image
The system firmware is contained in separate temporary and permanent images in the flash memory of
the compute node. These images are referred to as TEMP and PERM, respectively. The compute node
normally starts from the TEMP image. Start the TEMP image before you update the firmware.
About this task
To start the TEMP image, see http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/
com.ibm.acc.psm.hosts.doc/dpsm_managing_hosts_power_firmware.html.
Recovering the TEMP image from the PERM image
To recover the TEMP image from the PERM image, you must perform the reject function. The reject
function copies the PERM image into the TEMP image.
About this task
To perform the reject function, complete the following steps:
Procedure
1. If you have not started the system from the PERM image, do so now. See "Starting the PERM image."
2. Issue the appropriate command for your operating system to reject the TEMP image:
v If you are using the Red Hat Enterprise Linux or SUSE Linux operating system, type the following
command:
update_flash -r
Chapter 8. Troubleshooting
453