Recovering The System Firmware; Starting The Perm Image; Starting The Temp Image - IBM Flex System p260 Installation And Service Manual

3. To restore the new fcsx device to the correct vfchost, enter the vfcmap command as follows:
vfcmap -vadapter vfchost0 -fcp fcs0
4. To check the vfchost mapping, enter the lsmap command as follows:
lsmap -vadapter vfchost2 -npiv
The output might look like the following example:
Name Physloc
--------------- ---------------------------------------- ------- ---------- ------
vfchost2 U7895.42X.9999999-V1-C33
Status NOT_LOGGED_IN
FC name fcs0
Ports logged in 0
Flags 4<NOT_LOGGED>
VFC client name
In this example, the new serial number is represented as newSN99.

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.
494
Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide
ClntID ClntName
4
FC loc code:U78AF.001.newSN99-P1-C35-L1-T1
VFC client DRC
ClntOS