Ensure the System Firmware is at a level that supports the POWER®5+TM processors which
is SF240_201 or higher. For more details, please see the hardware prerequisite
page at IBM Prerequisite at http://www-912.ibm.com/e_dir/eserverprereq.nsf/UpgradeCategories/Hardware?opendocument.
Ensure
that when replacing the service processor on a model
561 or
570 that the replacement FRU does
not contain down level firmware.
Tip: The firmware level installed
on the service processor appears in the upper right corner of the main ASMI
menu panel.
SRC B181F12C or B181F40 is displayed when the firmware
level installed on a replacement service processor is at a release prior to
01SF240.
Remember: - If your model 561 or 570 is HMC managed, update the
system to the minimum required or later level firmware.
- If the system is non-HMC managed, you must order a service processor
containing the same level of firmware as the service processor being replaced.
During a service processor replacement on a nonmanaged systems,
order service processor FRU 10N8348 code A.
During a service processor
replacement on a managed system, if the firmware is not at a supported level,
the state of the managed system goes into a "recovery" state, indicating a
mismatch between the partition profile data that is stored on the HMC and
the newly installed service processor. You will need to clear the "recovery"
state prior to upgrading the firmware to a supported level. To clear the recovery
state and then upgrade the firmware to a supported level, do the following:
- Rename the copy of the profile data that exists on the HMC. (This prevents
the recovery state from being re-encountered.)
- For systems connected by statically assigned IP addresses, obtain the
IP addresses for the managed system. To view the IP addresses, do the following:
- Working from the HMC console, with a cursor blinking on your desktop,
click the right mouse button.
- Select rshterm (terminals).
Note: When entering (typing in) any
of the commands listed in the following steps, you do so from the command
line that is visible on your HMC display. After you have completed typing
in the command entry, you press the Enter key to activate the command.
- Enter the lssysconn -r all command.
Note: For systems equipped
with redundant service processors, record both addresses.
- Using the HMC, logically remove the Ethernet connection for the managed
system by clicking your right mouse button on the managed system object, and
then selecting the Reset or Remove Connection option.
Note: Do not physically
remove the Ethernet connectors from the system.
- Obtain the pesh password from your support center.
- Obtain the existing HMC root password.
- Login to the HMC as user hscpe, then create a hscpe user ID.
- Enter the pesh command, for example, pesh XXXXXXX.
Note: The
XXXXXXX equals the HMC serial number.
- When prompted, enter in the pesh password.
- Enter the su command to become root.
- When prompted, enter the HMC's root-user's password.
- Use the following cd command to change your directory to the profiles
directory cd /var/hsc/profiles.
- Enter the ls command. A directory entry for each of the attached
managed systems is displayed by serial number.
- Use the cd command to change to the directory of the managed system
you are working.
- Enter the ls command. A file named "backupFile" displays.
- Use the following cp command to copy the displayed
backupFile to a new file name cp backupFile mybackup.
- Use the following rm command to remove the backupFile rm
backupFile.
- For systems connected by static IP addresses, manually add the managed
system to the HMC using the GUI Add Managed System option, or enter
the following mksysconn command mksysconn --ip 9.3.23.1 -r
sys.
- For systems connected by DHCP assigned addresses allow the HMC to reconnect.
- After the managed system has been added to the HMC, the system reappears
on the HMC in a "Failed Authentication" state. Authenticate the managed system
using the HMC access password by clicking your right mouse button on the managed
system object.
- Upgrade the firmware to the required level.
- Power on the system to partition standby.
- Restore the partition profile data using the renamed backup
file created in step 15.
Note: Do not use
the new file named "backupFile". You must use the renamed backup file.
- After the partition profile data restore is complete, the partitions can
now be activated. When the first partition is activated, a panel might appear
stating that the managed system is currently in the manufacturing default
configuration (MDC). Select the Exit MDC using partition profile activation option.
- Select OK. This ends the procedure.