This document describes the installation of Licensed Machine Code, which
is sometimes referred to generically as microcode or firmware.
The firmware level contained in this update is:
To obtain the firmware that meets the requirements of the Common Criteria on secure delivery, follow the link in the Contents section of download.html.
Use your web browser to check that the security information (server certificate) is valid. To do this, click on the lock icon on the bottom bar of the web browser window.
To configure the certified firmware, you must follow the instructions in the "Evaluation Assurance Level 4+" chapter of the Hardware Management Console for pSeries Installation and Service Guide.
NOTE: See Section 2.0 Firmware Description and Revision History for information on the new firmware level name.
NOTE: This server can only be attached to an HMC
that is running Release 3, Version 1.2 or higher.
All previously released firmware levels for the pSeries 650 (7038-6M2) are Version 3.
Table 2.1
lists the levels and descriptions for the firmware.
The System, Service Processor (SvP) and System Power Control Network (SPCN) firmware are combined into a single file. This allows all the firmware to be updated together and assures they are compatible.
Don't be alarmed at the length of this document! For any given download/unpacking/update environment, the process is short. This document describes processes for several environments. One should be suitable for your needs, and these instructions guide you through just the environment you choose.
Note: If the update file will be downloaded directly to the target server, diskettes will have to be made in order to update the firmware from the Service Processor Menus.
The firmware level can be check in AIX or in the Service Processor Main Menu.
Enter:
lscfg -vp | grep -p Platform
This command will produce a system configuration report similar to the following.
Platform Firmware: ROM Level.(alterable).......3K030916 Version.....................RS6K System Info Specific.(YL)...U1.18-P1-H2/Y2 Physical Location: U1.18-P1-H2/Y2The ROM Level line lists the level of the currently installed firmware. In the above example, the current firmware level is 3K030916.
If the right-most six characters (date) of firmware level is earlier than 031021, you should consider installing the update.
If you find the firmware must be updated, proceed to Section 5.0. If the firmware level is correct and no update is needed, installation is complete.
If the right-most six characters (date) of firmware level is earlier than 031021, you should consider installing the update.
If you find the firmware must be updated, proceed to Section 5.0. If the firmware level is correct and no update is needed, installation is complete.
Note: To update firmware on a native Linux system, you must use the Service Processor Menus method. This method requires diskettes. Choose the correct download format for your environment.
https://www14.software.ibm.com/webapp/set2/firmware/gjsn?mode=10&page=isoiec.html
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.
The download choices at that entry are:
Note: In the instructions that follow are specific AIX commands.
AIX commands
are CASE (lower and upper) SENSITIVE, and must
be entered
exactly as shown, including the filenames.
a) Provide a directory on an AIX system to receive the AIX format file.
Enter:
mkdir /tmp/fwupdate
Note: If the
directory /tmp/fwupdate already exists,
make sure it is empty before proceeding.
b) Transfer the AIX package to the /tmp/fwupdate directory (using
"Save as ...").
You'll see that the filename is
70386M2F.BIN
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x 70386M2F.BIN
./70386M2F.BIN
[Don't overlook the periods (.) in the above command.]
This file will be added to /tmp/fwupdate:
3K031021.img
If the above procedure was used to transfer files directly to the target server, proceed to Section 6.0, Updating the Firmware.
Otherwise, on the intermediate AIX system, choose one of the following methods for transferring files to the target server.
On the intermediate AIX system,
Enter the commands:
ftp {name of target server}
{Login with a valid userid and password}
bin
lcd /tmp/fwupdate
mkdir /tmp/fwupdate
cd /tmp/fwupdate
put 3K031021.img
quit
Proceed to Section 6.0 Updating the Firmware.
Four 2MB (HD) new diskettes are required.
With a diskette loaded in the drive,
Enter the commands (this process will request additional diskettes as each is filled):
cd /tmp/fwupdate
ls *.img | backup -i -v -f/dev/rfd0
This will produce AIX backup diskettes. Label these diskettes, respectively,
"Volume 1: Firmware (3K031021) for 7038-6M2"
"Volume 2: Firmware (3K031021) for 7038-6M2"
"Volume 3: Firmware (3K031021) for 7038-6M2"
"Volume 4: Firmware (3K031021) for 7038-6M2"
Proceed to Section 6.0 Updating the Firmware.
a) Prepare a directory for receiving the DOS package.
This directory can be in any partition
with 12MB available space.
Executing in such a partition, called
[path] in these instructions
(ex. c:\download),
Enter:
md [path]\fwupdate
Note: If the directory [path]\fwupdate
already exists,
make sure it is empty before proceeding.
b) Transfer the DOS package to the [path]\fwupdate directory
(using "Save as ...").
You'll see the filename is 70386M2F.EXE
c) Unpack the file by executing the instructions below.
Enter the commands:
cd [path]\fwupdate
70386M2F
These files will be added to the fwupdate subdirectory:
386M2_B1.EXE
386M2_B2.EXE
386M2_B3.EXE
386M2_B4.EXE
Note: The diskettes produced below will be in a format
that can be used
directly with a computer running AIX as it's operating system. These
diskettes, once made on a PC platform, cannot be read using normal PC
platform tools or command line operations.
a) With a diskette loaded in the drive,
Enter the commands:
cd
[path]\fwupdate
386M2_B1
Label this diskette,
"Volume 1: Firmware (3K031021) for 7038-6M2"
b) With a second diskette loaded in the drive,
Enter:
386M2_B2
Label this diskette,
"Volume 2: Firmware (3K031021) for 7038-6M2"
c) With a third diskette loaded in the drive,
Enter:
386M2_B3
Label this diskette,
"Volume 3: Firmware (3K031021) for 7038-6M2"
d) With a fourth diskette loaded in the drive,
Enter:
386M2_B4
Label this diskette,
"Volume 4: Firmware (3K031021) for 7038-6M2"
Proceed to Section 6.0 Updating the Firmware.
Note: In the instructions that follow are specific AIX commands.
AIX commands
are CASE (lower and upper) SENSITIVE, and must
be entered
exactly as shown, including the filenames.
a) Provide a directory on the target server to receive the RPM package.
Enter:
mkdir /tmp/fwupdate
Note: If the
directory /tmp/fwupdate already exists,
make sure it is empty before proceeding.
b) Transfer the RPM package to the /tmp/fwupdate directory (using
"Save as ...").
You'll see that the filename is
3K031021.rpm
c) Unpack the file by executing the instructions below.
Enter the commands:
rpm -ihv --ignoreos 3K031021.rpm
The 3K031021.img file will be added to /tmp/fwupdate:
The file size and checksum will be verified.
Proceed to Section 6.0, Updating the Firmware.
NOTE: This server can only be attached to an HMC that is running Release 3, Version 1.2 or higher.
NOTE: To update firmware on a native Linux system, you must use the Service Processor Menus method.
The System, Service Processor (SvP) and System Power Control Network (SPCN) firmware are combined into a single file. This allows all the firmware to be updated together and assures they are compatible.
Once the System and Service Processor firmware had been updated, the server will reboot. The System Power Control Network (SPCN) update will continue to run in the background.
NOTE: Updating the firmware may result in the HMC going into 'Recovery' state. Before updating the firmware, make sure an HMC Recovery CD is available, the backup of Profile Data is complete (if running LPAR), and the backup of Critical Console Data to DVD is complete. Make sure the 'write protect' tab is not set to write protect (there is no failure message if the write protect is enabled, however no data is backed up).
***
WARNING:
Do not power off the server at any time before
the update process completes. Be sure the system is NOT running any
user applications when you begin the update process.
***
Note: Checksums should be used to verify files have not been corrupted or altered during transmission.
At the AIX command
line, enter.
sum 3K031021.img
The output will look
like this ------> 23042 4911 3K031021.img
The checksum is -------------->
23042
It is recommended that the update, on both a full system partition and a partitioned system, be performed using the Service Processor Menus. Updating the firmware using the Service Processor Menus avoids the resource allocation issues that can arise if the server is a partitioned system.
You must have privileged user authority on the target server to update its firmware.
Note: All firmware (System, Service Processor and SPCN) will be updated when using this method.
a. Shutdown the server from the HMC virtual terminal window or ASCII terminal window.
b. When the operator panel on the server says OK,
press Enter, to bring up the Service Processor
Menu.
c. Choose 1 for Service Processor Setup Menu. <Enter>
d. Choose 7 for Reprogram Flash EPROM Menu. <Enter>
e. Type y to continue. <Enter>
f. Follow on-screen update steps as they are presented.
g. The 'Rebooting Service Processor ' message appears on the screen.
h. Begin watching the operator panel.
i. When the panel says 'OK',
If using an ASCII
terminal - Press Enter.
If using an HMC terminal
- close the current terminal window and open a new terminal window.
The Service Processor Menu appears on your screen.
The second line of
the title, Version: 3K031021, should match the firmware level you just
installed.
Don't forget to retrieve and file any firmware update diskette that may still be in the system's diskette drive. A good time to do this is after the reboot has completed.
The firmware update is complete.
Note: In the instructions that follow are specific AIX commands.
AIX commands
are CASE (lower and upper) SENSITIVE, and must
be entered
exactly as shown, including the filenames.
Note: Review "Update System or Service Processor Flash" in the
Service Aids
section of the eserver pSeries 650 User's
Guide for more information about using this utility.
mkdir /tmp/fwupdate
Note: If the directory /tmp/fwupdate
already exists,
make sure it is empty before proceeding.
cd /tmp/fwupdate
Enter :
restore
You will be prompted to mount volume 1 on /dev/rfd0
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 1: Firmware (3K031021) for 7038-6M2"
When prompted for volume 2,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 2: Firmware (3K031021) for 7038-6M2"
When prompted for volume 3,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 3: Firmware (3K031021) for 7038-6M2"
When prompted for volume 4,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 4: Firmware (3K031021) for 7038-6M2"
The file is now located in the /tmp/fwupdate subdirectory. Continue to paragraph 6.1.2.2.
b) Choose Update System or Service Processor Flash.
c) Select 'File System' as the source of the flash update image file.
The fully qualified path name of the update file is /tmp/fwupdate/3K031021.img
d) If using an ASCII terminal press 'F7' key to 'Commit' the
update.
If using an HMC terminal
press 'ESC' + '7' keys to 'Commit' the update.
e) Choose Yes to continue.
The server automatically performs the update and reboots. The checkpoints 99FF and 99FD alternately appear while the update is in progress. This may take up to thirty minutes, depending on the configuration of the target server. Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.
NOTE: If using an HMC terminal you will need to close the existing terminal window and open a new terminal window when the operator panel goes blank.
Don't forget to retrieve and file any firmware update diskette that may still be in the server's diskette drive. A good time to do this is after the reboot has completed.
The update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.
Note: In the instructions that follow are specific AIX commands.
AIX commands
are CASE (lower and upper) SENSITIVE, and must
be entered
exactly as shown, including the filenames.
AIX allows updating either from files already loaded into the target server or from diskettes.
Enter the commands:
mkdir /tmp/fwupdate
Note: If the directory /tmp/fwupdate
already exists,
make sure it is empty before proceeding.
cd /tmp/fwupdate
Enter :
restore
You will be prompted to mount volume 1 on /dev/rfd0
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 1: Firmware (3K031021) for 7038-6M2"
When prompted for volume 2,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 2: Firmware (3K031021) for 7038-6M2"
When prompted for volume 3,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 3: Firmware (3K031021) for 7038-6M2"
When prompted for volume 4,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 4: Firmware (3K031021) for 7038-6M2"
The file is now located in the /tmp/fwupdate subdirectory. Continue to paragraph 6.1.3.2.
Enter the commands:
cd /usr/lpp/diagnostics/bin
./update_flash -f /tmp/fwupdate/3K031021.img
[Don't overlook the periods (.) in the above command.]
You will be asked for confirmation to proceed with the firmware update and the required reboot. If you confirm, the server automatically performs the update and reboots. The checkpoints 99FF and 99FD alternately appear while the update is in progress. This may take up to thirty minutes, depending on the configuration of the server. Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.
NOTE: If using an HMC terminal you will need to close the existing terminal window and open a new terminal window when the Operator Panel goes blank.
The update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.
You must have privileged user authority on the target server to update its firmware.
Note: All firmware (System, Service Processor and SPCN) will be updated when using this method.
a. Shutdown the server from the HMC virtual terminal window or the ASCII terminal .
b. When the operator panel on the server says OK,
press Enter, to bring up the Service Processor
Menu.
c. Choose 1 for Service Processor Setup Menu. <Enter>
d. Choose 7 for Reprogram Flash EPROM Menu. <Enter>
e. Type y to continue. <Enter>
f. Follow on-screen update steps as they are presented.
g. The 'Rebooting Service Processor ' message appears on the screen.
The target server
will reboot. This may take up to thirty minutes, depending on the
configuration
of the target
server. Since the update occurs during this shutdown/reboot sequence,
it is
important
to protect the server from interruptions.
h. Begin watching the operator panel.
i. When the panel says 'OK',
If using an ASCII
terminal - Press Enter.
If using an HMC terminal
- close the current terminal window and open a new terminal window.
The Service Processor Menu appears on your screen.
The second line of
the title, Version: 3K031021, should match the firmware level you just
installed.
Don't forget to retrieve and file any firmware update diskette that may still be in the system's diskette drive. A good time to do this is after the reboot has completed.
If the OP Panel on the server displays OK and the Managed System state on the HMC is either RECOVERY or INCOMPLETE, skip to paragraph 6.3 HMC Restore Functions to complete the procedure.
If the OP Panel on the server displays OK and
the Managed System state on the HMC is READY, the update
of the firmware is complete. You will want to verify this update as shown
in paragraph 6.4.
ATTENTION: This method is not recommended for partitioned
systems, unless the device resources
are allocated properly. This requires:
- One partition running AIX must have service authority.
- All other partitions except the one with service authority must be shut
down.
- The partition with service authority must own the device from which the
firmware
update image will be read.
- It is also recommended that the partition with service authority have
a hard disk.
If the required devices are not in the partition with service authority, the customer or system administrator must reassign the appropriate resources to it. This requires rebooting the partition with service authority. To avoid the resource allocation issues, it is recommended that the service processor menus be used to update the firmware.
Note: In the instructions that follow are specific AIX
commands.
AIX commands are CASE (lower and upper) SENSITIVE, and must
be entered exactly as shown, including the filenames.
Note: Review "Update System or Service Processor Flash"
in the Service Aids section
of the eserver pSeries
650 User's Guide for more information about using this utility.
Service Aids allows updating from files already loaded into the target server or from diskettes.
mkdir /tmp/fwupdate
Note: If the directory /tmp/fwupdate
already exists,
make sure it is empty before proceeding.
cd /tmp/fwupdate
Enter :
restore
You will be prompted to mount volume 1 on /dev/rfd0
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 1: Firmware (3K031021) for 7038-6M2"
When prompted for volume 2,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 2: Firmware (3K031021) for 7038-6M2"
When prompted for volume 3,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 3: Firmware (3K031021) for 7038-6M2"
When prompted for volume 4,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 4: Firmware (3K031021) for 7038-6M2"
The file is now located in the /tmp/fwupdate subdirectory. Continue to paragraph 6.2.2.2.
b) Choose Update System or Service Processor Flash.
c) Select 'File System' as the source of the flash update image file.
The fully qualified path name of the update file is /tmp/fwupdate/3K031021.img
d) If using an ASCII terminal press 'F7' key to 'Commit' the
update.
If using an HMC terminal
press 'ESC' + '7' keys to 'Commit' the update.
The server automatically performs the update and reboots. The checkpoints 99FF and 99FD alternately appear while the update is in progress. This may take up to thirty minutes, depending on the configuration of the target server. Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.
NOTE: If using an HMC terminal you will need to close the existing terminal window and open a new terminal window and open a new terminal window when the Operator Panel goes blank.
Don't forget to retrieve and file any firmware update diskette that may still be in the server's diskette drive. A good time to do this is after the reboot has completed.
If the OP Panel on the server displays OK and the Managed System state on the HMC is either RECOVERY or INCOMPLETE, skip to paragraph 6.3 HMC Restore Functions to complete the procedure.
If the OP Panel on the server displays OK and the Managed System state on the HMC is READY, the update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.
ATTENTION: This method is not recommended for partitioned
systems, unless the device resources
are allocated properly. This requires:
- One partition running AIX must have service authority.
- All other partitions except the one with service authority must be shut
down.
- The partition with service authority must own the device from which the
firmware
update image will be read.
- It is also recommended that the partition with service authority have
a hard disk.
If the required devices are not in the partition with service authority, the customer or system administrator must reassign the appropriate resources to it. This requires rebooting the partition with service authority. To avoid the resource allocation issues, it is recommended that the service processor menus be used to update the firmware.
AIX allows updating either from files already loaded into the target server or from diskettes.
Enter the commands:
mkdir /tmp/fwupdate
Note: If the directory /tmp/fwupdate
already exists,
make sure it is empty before proceeding.
cd /tmp/fwupdate
Enter :
restore
You will be prompted to mount volume 1 on /dev/rfd0
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 1: Firmware (3K031021) for 7038-6M2"
When prompted for volume 2,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 2: Firmware (3K031021) for 7038-6M2"
When prompted for volume 3,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 3: Firmware (3K031021) for 7038-6M2"
When prompted for volume 4,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 4: Firmware (3K031021) for 7038-6M2"
The file is now located in the /tmp/fwupdate subdirectory. Continue to paragraph 6.2.3.2.
Enter the commands:
cd /usr/lpp/diagnostics/bin
./update_flash
-f /tmp/fwupdate/3K031021.img
[Don't overlook the periods (.) in the above command.]
You will be asked for confirmation to proceed with the firmware update and the required reboot. If you confirm, the server automatically performs the update and reboots. The checkpoints 99FF and 99FD alternately appear while the update is in progress.This may take up to thirty minutes, depending on the configuration of the server. Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.
Don't forget to retrieve and file any firmware update diskette that may still be in the server's diskette drive. A good time to do this is after the reboot has completed.
If the OP Panel on the server displays OK and the Managed System state on the HMC is either RECOVERY or INCOMPLETE, skip to paragraph 6.3 HMC Restore Functions to complete the procedure.
If the OP Panel on the server displays OK and the Managed System state on the HMC is READY, the update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.
a. Click on the managed system name.
b. Select the "Recover Partition Data" task.
c. Select "Restore profile data from HMC backup" option.
This can take up to 10 minutes.
When the restore is finished, the state changes to READY and the system Status and operator panel will say LPAR.
You will want to verify this update as shown in paragraph 6.4.
Enter:
lscfg -vp | grep -p Platform
This command will produce a system configuration report containing sections similar to the following.
Platform Firmware: ROM Level.(alterable).......3K031021 Version.....................RS6K System Info Specific.(YL)...U1.18-P1-H2/Y2 Physical Location: U1.18-P1-H2/Y2The ROM Level line should match the level you just installed, namely, 3K031021.
If the download process produced diskettes, label and store them in a safe place.
If the download process produced files, archive and identify the files for convenient retrieval.