This document describes the installation of Licensed Machine Code, which
is sometimes referred to generically as microcode or firmware.
The Version 3 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.
The installation of the Common Criteria firmware level 3H031021 on a p670 or p690 system that is currently at firmware level 3H031024 or later, will require 'backleveling' the system firmware. Please contact your IBM Service Representative for more information on how to successfully backlevel your system firmware.
Any system that has been backleveled to 3H031021 may find that certain functions are not longer enabled. The Common Criteria Certification was performed prior to the availability of these functions. For example, support for the pSeries High Performance Switch (7045-SW4) was released in the 3H031024 level of firmware, therefore releases prior to this will not support this Switch. Please refer to Section 2.0, Firmware Description and Revision History for more information.
ATTENTION: If your p670/p690 is at firmware level 3H030916, contact your SSR to have this level of firmware installed (reference ECA 598).
ATTENTION: These instructions CAN ONLY be used to
update any pSeries 690 or pSeries 670
Servers that currently have a Version 3 level firmware installed.
See Table 4.1 Update Decisions.
Note: Before installing this level of firmware, ensure the HMC code on all HMC systems to Release 3, Version 1.2 or later. If you will be updating hardware, you will need to refer to the specific MES document to identify the required level of HMC.
The versions of released firmware follow:
Version 1 - RH011206 through RH020312
Version 2 - RH020413 through RH021024 and 2H030325
Version 3 - RH021025 through RH030307 and 3H030524
through 3H031024
Version 2 and Version 3 are currently supported. A mandatory update from Version 1 to Version 2 was implemented in April 2002.
Table 2.1
lists the levels and descriptions for the firmware.
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: These instructions CAN ONLY be used to update any pSeries 690 or pSeries 670 Servers that currently have a Version 3 level firmware installed. See Table 4.1 Update Decisions.
IMPORTANT! If your system configuration has six 7040-61D
I/O Drawers and three IBFs (battery backup) OR seven or more 7040-61D I/O
Drawers, regardless of the number of IBFs, place a service call to IBM
and request that a Service Representative be sent to your location to update
your system(s) to this level of firmware.
The table below states the time needed to wait
for a complete SPCN/Power Subsystem code update to occur on a maximum-configured
CEC assembly (4 MCMs).
| 7040-61D Drawers | Minutes | Hours:Minutes |
| 1 | 118 | 1:58 |
| 2 | 134 | 2:14 |
| 3 | 150 | 2:30 |
| 4 | 166 | 2:46 |
| 5 | 182 | 3:02 |
| 6 | 198 | 3:18 |
| 7 | 214 | 3:34 |
| 8 | 230 | 3:50 |
OR
The table below can be used to calculate the minimum
time needed to wait for a complete SPCN/Power Subsystem code update to
occur on a specific configuration.
| System Configuration | Time | Quantity | Time Required |
| BPC | 10 minutes | x 2 | 20 Minutes |
| BPR (2-6) | 5 minutes | x | Minutes |
| SPCN | 10 minutes | x 1 | 10 Minutes |
| CEC DCA (2-6) | 5 minutes | x | Minutes |
| CEC MDA | 3 minutes | x 4 | 12 Minutes |
| I/O Drawer DCA (2 per drawer) | 5 minutes | x |
Minutes
|
| I/O Drawer MDA (2 per drawer) | 3 minutes | x | Minutes |
| Total Time Required | Minutes |
If no errors are reported to AIX or the HMC after the specified amount of time, then the update occurred successfully.
If errors are reported to AIX or the HMC after the specified amount of time, then contact your next level of support for assistance.
If you wish to see the SPCN level displayed correctly in AIX, the system should be rebooted after the time has elapsed. Do not Power Off the Frame via the UEPO.
To verify the SPCN level, follow the procedure in Section 6.4 Verifying the SPCN Update.
If there is a need to verify the Power Subsystem FRU Code Levels on the system, this can be done from the Service Processor Main Menu.
a) Choose 3 for System Information Menu.
b) Choose 9 for Power Control Network Utilities
c) Choose 6 for Display Power Subsystem FRU Code Levels.
The current code versions are:
| FRU | Code Version |
| BPC -RH | 00002594 |
| BPR-F | 00000015 |
| DCA-RHP | 0000002a |
| MDA-X | 00000007 |
| DCA-BC | 00000028 |
| MDA-BC | 00000005 |
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).......3H030811 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 3H030811.
For information on how to proceed, See Table 4.1 Update Decisions.
For information on how to proceed, See Table
4.1 Update Decisions.
| Table 4.1 Update Decisions | |
| If current firmware level is: | Do this: |
| RH021025 through RH030307 or 3H030524 through 3H030905 (Version 3) | Proceed to Section 5.0 to continue with the firmware update. |
| 3H031024 or later | Call your IBM Service Representative for more information. |
| 3H030916 | Call your IBM Customer Engineer (CE) and request ECA 598 |
| RH020413 through RH021024 or 2H030325 (Version 2) | Call your IBM Customer Engineer (CE) and request EC J11966 |
| RH011206 through RH020312 (Version 1) | Call your IBM Customer Engineer (CE) and request EC J11432 |
If you find the firmware must be updated, proceed as specified above. If no update is needed, installation is complete.
ATTENTION: If the current firmware level on the server is NOT Version 3, you MUST return to Table 4.1 Update Decisions to determine how to proceed.
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 table for System Microcode, scroll down to the entry for 7040-681 and 7040-671 Version 3.
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
7040681F.BIN
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x 7040681F.BIN
./7040681F.BIN
[Don't overlook the periods (.) in the above command.]
These files will be added to /tmp/fwupdate:
3H031021.img
errata.txt (this
contains information about potential problems that may be encountered)
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 3H031021.img
quit
Proceed to Section 6.0, Updating the Firmware.
Five 2MB (HD) new or freshly formatted 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: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
"Volume 2: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
"Volume 3: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
"Volume 4: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
"Volume 5: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
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 7040681F.EXE
c) Unpack the file by executing the instructions below.
Enter the commands:
cd [path]\fwupdate
7040681F
These files will be added to the fwupdate subdirectory:
40681_B1.EXE
40681_B2.EXE
40681_B3.EXE
40681_B4.EXE
40681_B5.EXE
errata.txt (this
contains information about potential problems that may be encountered)
a) With a diskette loaded in the drive,
Enter the commands:
cd
[path]\fwupdate
40681_B1
Label this diskette,
"Volume 1: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
b) With a second diskette loaded in the drive,
Enter:
40681_B2
Label this diskette,
"Volume 2: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
c) With a third diskette loaded in the drive,
Enter:
40681_B3
Label this diskette,
"Volume 3: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
d) With a fourth diskette loaded in the drive,
Enter:
40681_B4
Label this diskette,
"Volume 4: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
e) With a fifth diskette loaded in the drive,
Enter:
40681_B5
Label this diskette,
"Volume 5: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
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.
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
3H031021.rpm
c) Unpack the file by executing the instructions below.
Enter the commands:
rpm -ihv --ignoreos 3H031021.rpm
The 3H031021.img file will be added to /tmp/fwupdate.
The file size and checksum will be verified.
Proceed to Section 6.0 Updating the Firmware.
ATTENTION: These instructions CAN ONLY be used to update any pSeries 690 or pSeries 670 Servers that currently have a Version 3 level firmware installed. See Table 4.1 Update Decisions.
Note: Before installing this level of firmware, ensure the HMC code on all HMC systems to Release 3, Version 1.2 or later. If you will be updating hardware, you will need to refer to the specific MES document to identify the required level of HMC.
IMPORTANT! If your system configuration has six 7040-61D I/O Drawers and three IBFs (battery backup) OR seven or more 7040-61D I/O Drawers, regardless of the number of IBFs, place a service call to IBM and request that a Service Representative be sent to your location to update your system(s) to this level of 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.
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.
The checksum can be computed for any file by using the AIX 'sum'
command, as follows.
At the AIX command line, enter:
sum 3H031021.img
The output will look like this ------> 17750 6126 3H031021.img
The checksum is --------------> 17750
Updating firmware must be initiated either directly from the Service Processor Menus, from the Update Flash Diagnostic Service Aids, or from the AIX command line.
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 the Enter key, 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', press the Enter key.
The Service Processor Menu appears on the screen.
The second line of
the title, Version: 3H031021, 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 platform firmware update is complete. 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.
Note: Review "Update System or Service Processor Flash" in the
Service Aids
section of the eserver pSeries 690 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: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 2,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 2: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 3,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 3: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 4,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 4: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 5,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 5: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
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/3H031021.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.
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 press the close the existing terminal window and open a new one when the operator panel shows blank.
NOTE: Please refer to the SPCN/Power Subsystem Code update times in Section 3.0.
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 platform firmware is complete. 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: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 2,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 2: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 3,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 3: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 4,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 4: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 5,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 5: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
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/3H031021.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: Please refer to the SPCN/Power Subsystem Code update times in Section 3.0.
NOTE: If using an HMC terminal you will need to close the existing terminal window and open a new one when the operator panel shows blank.
The update of the platform firmware is complete. 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 the Enter key, 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', press the Enter key.
The Service Processor Menu appears on the screen.
The second line of
the title, Version: 3H031021, 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: Review "Update System or Service Processor Flash"
in the Service Aids section
of the eServer pSeries
690 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: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 2,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 2: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 3,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 3: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 4,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 4: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 5,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 5: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
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/3H031021.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.
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: Please refer to the SPCN/Power Subsystem Code update times in Section 3.0.
NOTE: If using an HMC terminal you will need to close the existing terminal window and open a new one when the operator panel shows LPAR.
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.
This method 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: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 2,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 2: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 3,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 3: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 4,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 4: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
When prompted for volume 5,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 5: Version 3 Firmware (3H031021) for 7040-681 and 7040-671"
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/3H031021.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: Please refer to the SPCN/Power Subsystem Code update times in Section 3.0.
NOTE: If using an HMC terminal you will need to close the existing terminal window and open a new one when the operator panel shows LPAR.
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.
Continue to paragraph 6.4 to verify the the update.
Note: You must wait the time specified by the table in Section 3.0, before verifying the SPCN firmware level.
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).......3H031021 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, 3H031021.
2) Use the following AIX command for checking the SPCN firmware level.
Enter:
lscfg -vp | grep -p SPCN
This command will produce a system configuration report containing sections similar to the following.
SPCN Firmware: ROM Level.(alterable).......0000RHE06203 Version.....................RS6K System Info Specific.(YL)...U1.18-P1-H2/Y3 Physical Location: U1.18-P1-H2/Y3The ROM Level line should match the level you just installed, namely, 0000RHE06203.
2) To check the SPCN firmware level,
a) Choose 3 for System Information Menu. <Enter>
b) Choose 1 for ReadVPD Images from Last Boot. <Enter>
c) Look for SPCN Firmware and type in the coresponding number. <Enter>
d) This command will produce configuration information containing sections similar to the following.
SPCN Firmware: RM .....................0000RHE06203 VK .....................RS6K YL .....................U1.18-P1-H2/Y3The RM line should match the level you just installed, namely, 0000RHE06203.
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.