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:
ATTENTION: Due to significant fixes in the last few firmware
releases to improve system
availability, firmware level 3H040326 or higher is being made mandatory
for all
7040 671/681 systems that currently have any previously released Version
3
firmware level installed.
The versions of released firmware follow:
Version 1 - RH011206 through RH020312
Version 2 - RH020413 through RH021024 and 2H030325
through 2H040323
Version 3 - RH021025 through RH030307 and 3H030524
through 3H050607
Version 2 and Version 3 are currently supported. A mandatory update
from Version 1 to Version 2 was implemented in April 2002.
For information about previous firmware levels, see Section
7.0 Appendix: Firmware History.
ATTENTION:
If your p670/p690 is at firmware level 3H031024 or an earlier Version
3 level (except 3H031021), you MUST update the firmware using the
Service Processor Menu method. If the AIX or Linux method is chosen,
there is a potential of a crash occurring during SPCN and power subsystem
code update that runs in the background after the firmware has been update
and the system has rebooted to AIX or Linux.
If the current firmware level is 3H031118 or later, you may update the firmware using either the Service Processor Menu method or the AIX or Linux command line method.
Before installing this level of firmware, ensure the Hardware Management Console (HMC) code on all HMC systems is Release 3, Version 1.2 or later. If a High Performance Switch (7045-SW4) is installed, the HMC code on all HMC systems must be Release 3, Version 2.6 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 code.
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).
Attempting to update firmware on a system with defective hardware FRUs will result in an incomplete firmware update. The system hardware should be checked prior to updating the firmware by reviewing Service Focal Point for Serviceable Event Details reported to the HMC, running AIX error log analysis via Concurrent Diagnostics, and reviewing hardware LED status. Address any errors and/or defects identified before proceeding with the firmware update.
Enter:
lscfg -vp | grep -p Platform
This command will produce a system configuration report similar to the following.
Platform Firmware: ROM Level.(alterable).......3H050215 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 3H050215.
For information on how to proceed, See Table 4.1 Update Decisions.
For information on how to proceed, See Table 4.1 Update Decisions.
Enter:
/sbin/lscfg -vp | grep -A 1 Platform
This command will produce a system configuration report similar to the following.
Platform Firmware: ROM Level.(alterable).......3H050215The ROM Level line lists the level of the currently installed firmware. In the above example, the current firmware level is 3H050215.
For information on how to proceed, See Table
4.1 Update Decisions.
| Table 4.1 Update Decisions | |
| If current firmware level is: | Do this: |
| 3H040326 through 3H050405 | Proceed to Section 5.0 to continue with the firmware update. |
| RH021025 through RH030307, or 3H030524 through 3H040301 (Version 3) | Proceed to Section 5.0 to continue with the firmware update, or call your IBM System Service Representative (SSR) and request ECA 601. |
| RH020413 through RH021024 or 2H030325 through 2H040323 (Version 2) | Call your IBM System Service Representative (SSR) and request ECJ11966. |
| RH011206 through RH020312 (Version 1) | Call your IBM System Service Representative (SSR) and request ECJ11432. |
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.
download.html
Follow the instructions on this web page. You must read and agree to the license agreement to obtain the firmware packages.
Scroll down to the entry for 7040-681 and 7040-671 Version 3.
The download choices at that entry are:
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 format file 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:
3H050607.img
ReadMe.TXT
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 3H050607.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 (3H050607) for 7040-681 and 7040-671"
"Volume 2: Version 3 Firmware (3H050607) for 7040-681 and 7040-671"
"Volume 3: Version 3 Firmware (3H050607) for 7040-681 and 7040-671"
"Volume 4: Version 3 Firmware (3H050607) for 7040-681 and 7040-671"
"Volume 5: Version 3 Firmware (3H050607) for 7040-681 and 7040-671"
Proceed to Section 6.0, Updating the Firmware.
a) Prepare a directory for receiving the DOS format file.
This directory can be in any partition
with 12MB available space.
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 format file 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
readme.txt
Note: The diskettes produced below will be in AIX backup
format and 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
40681_B1
Label this diskette,
"Volume 1: Version 3 Firmware (3H050607) 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 (3H050607) 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 (3H050607) 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 (3H050607) 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 (3H050607) for 7040-681 and 7040-671"
Proceed to Section 6.0 Updating the Firmware.
a) Provide a directory on the target server to receive the RPM format file.
Enter:
mkdir /tmp/fwupdate
Note: If the
directory /tmp/fwupdate already exists,
make sure it is empty before proceeding.
b) Transfer the RPM format file to the /tmp/fwupdate directory
(using "Save as ...").
You'll see that the filename is
3H050607.rpm
c) Unpack the file by executing the instructions below.
Enter the commands:
rpm -ihv --ignoreos 3H050607.rpm
The 3H050607.img file will be added to /tmp/fwupdate.
The file size and checksum will be verified.
Proceed to Section 6.0 Updating the Firmware.
Look for 7040-681 and 7040-671 Version 3.
You will want to read the update description and the latest installation instructions.
When you launch the firmware update selection in CORE, follow the instructions on the screen to access the instructions and make diskettes.
Note:
The diskettes produced by CORE for this update are in AIX backup format.
These diskettes, once made on the MoST platform, cannot be read using
normal PC platform tools or command line operations.
After reading the instructions and making the diskettes from CORE, proceed to Section 6.0 Updating the Firmware.
Enter:
mkdir /tmp/fwupdate
Note: If the
directory /tmp/fwupdate already exists,
make sure it is empty before proceeding.
cd /tmp/microcode/RPM
mv 3H050607.rpm /tmp/fwupdate
cd /tmp/fwupdate
rpm -ihv --ignoreos 3H050607.rpm
The 3H050607.img file will be added to /tmp/fwupdate:
The file size and checksum will be verified.
If you are installing manually:
Enter:
mkdir /tmp/fwupdate
Note: If
the directory /tmp/fwupdate already exists,
make sure it is empty before proceeding.
Copy the 3H050607.img file to the /tmp/fwupate directory.
Proceed to Section 6.0 Updating the Firmware.
If you are updating using the Service Processor Menus, or need diskettes for recovery mode, you will need to make diskettes, on a system running AIX, as follows:
Five 2MB (HD) new or freshly formatted diskettes are required.
With a diskette loaded in the drive,
Enter the AIX commands (this process will request additional diskettes as each is filled):
cd /tmp/fwupdate
ls 3H050607.img | backup -i -v -f/dev/rfd0
This will produce AIX backup diskettes. Label these diskettes, respectively,
"Volume 1: Version 3 Firmware (3H050607) for 7040-681 and 7040-671"
"Volume 2: Version 3 Firmware (3H050607) for 7040-681 and 7040-671"
"Volume 3: Version 3 Firmware (3H050607) for 7040-681 and 7040-671"
"Volume 4: Version 3 Firmware (3H050607) for 7040-681 and 7040-671"
"Volume 5: Version 3 Firmware (3H050607) for 7040-681 and 7040-671"
Proceed to Section 6.0 Updating the Firmware.
ATTENTION:
If your p670/p690 is at firmware level 3H031024 or an earlier Version
3 level (except 3H031021), you MUST update the firmware using
the Service Processor Menu method. If the AIX or Linux method is
chosen, there is a potential of a crash occurring during SPCN and power
subsystem code update that runs in the background after the firmware has
been update and the system has rebooted to AIX or Linux.
If the current firmware level is 3H031118 or later, you may update the firmware using either the Service Processor Menu method, the AIX command line method or the Linux command line method.
***
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 'sum'
command, as follows.
At the command line, enter:
sum 3H050607.img
The output will look like this ------> 61399 6258 3H050607.img
The checksum is --------------> 61399
Updating firmware must be initiated either directly from the Service Processor Menus, from the AIX command line or the Linux command line.
Service Processor Menus allow updating from AIX backup diskettes only.
You must have privileged user authority on the target server to update its firmware.
a. Shutdown the server from the HMC virtual terminal window or ASCII terminal window.
b. When the operator panel on the server 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 the screen.
Continue to paragraph 6.1.1.
b. Choose 7 for Reprogram Flash EPROM Menu. <Enter>
c. Type y to continue. <Enter>
d. Follow on-screen update steps as they are presented.
e. 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.
f. Begin watching the operator panel.
g. 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 the screen.
The second line of
the title, Version: 3H050607, should match the firmware level you just
installed.
Continue to paragraph 6.1.2.
b. Choose 9 for Power Control Network Utilities Menu. <Enter>
c. Choose 8 for Start Power Subsystem Code Update. <Enter>
This will update the SPCN (if necessary) and the Power Subsystem code.
You will see messages saying: Please wait......,SPCN_rc=21
The RC=21 means Present State Prohibits. This means the system is
collecting and
comparing the code level on the power FRU to the code level within the
firmware image.
Once completed and an update is needed, the power FRU will be updated to
the latest level.
This is NOT an error condition.
This step may take up to four hours to complete depending on the firmware
level and the
system configuration. For a typical configuration, this will take
approximately one hour.
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 |
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). The estimated time below includes a double
retry of code download to each FRU.
| 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 |
When the Power Subsystem code update has completed,
d. Choose 6 for Display Power Subsystem FRU Code Levels. <Enter>
The current code versions are:
| FRU | Code Version |
| BPC-RH | 000026a4 |
| BPR-F | 00000015 |
| BPR_MP | 0000001a |
| DCA-RHP | 0000002e |
| MDA-X | 00000007 |
| DCA-BC | 0000002c |
| MDA-BC | 00000005 |
| DCD-BCS | 00000034 |
| MDA-BR | 00000004 |
Power on the system.
If the OP Panel on the server displays OK and the Managed System state on the HMC is either RECOVERY or INCOMPLETE, continue to paragraph 6.1.3.
If the OP Panel on the server displays OK and the Managed System state on the HMC is READY, the update process is complete.
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.
The update process is complete.
Don't forget to retrieve and file any firmware update diskette that may still be in the system's diskette drive.
You must have root authority on the target server to update its firmware.
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 onto 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 (3H050607) 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 (3H050607) 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 (3H050607) 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 (3H050607) 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 (3H050607) for 7040-681 and 7040-671"
The file is now located in the /tmp/fwupdate subdirectory. Don't forget to retrieve and file any firmware update diskette that may still be in the server's diskette drive. Continue to paragraph 6.2.2.
With the file located in the /tmp/fwupdate subdirectory,
Enter the commands:
cd /usr/lpp/diagnostics/bin
./update_flash
-f /tmp/fwupdate/3H050607.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 one when the operator panel shows either blank (if you are running in Full System Partition mode) or LPAR ( if you are running in Partition Standby mode).
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.2.3.
If the OP Panel on the server displays OK and the Managed System state on the HMC is READY, boot the system to AIX, then skip to paragraph 6.2.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. Boot the system to AIX, then continue to paragraph 6.2.4.
This command will produce a system configuration report containing sections similar to the following.
Platform Firmware: ROM Level.(alterable).......3H050607 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, 3H050607.
Continue to paragraph 6.2.5.
Once the update has completed, the
AIX error log will post a Firmware Event.
For the SPCN completion, the reference
code will be B1284633, with a word 13 value of A70Exxxx.
The Power Subsystem initiation reference
code will be 1011875B and the completion reference code will be 1011875C.
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.
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). The estimated time below includes a double
retry of code download to each FRU.
The update process is complete.
You must have root authority on the target server
to update its firmware.
ATTENTION: This method is not recommended for partitioned
systems, unless the device resources
- One partition running Linux must have service authority.
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.
Enter the commands:
cd /tmp/fwupdate
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 and open a new
terminal window when the Operator Panel shows LPAR.
If the Managed System state on the HMC is either
RECOVERY or INCOMPLETE, skip to paragraph
6.3.2 HMC Restore Functions to complete the procedure.
If 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.3.3.
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 Managed System
state changes to READY. The update of the firmware is complete.
You will want to verify this update as shown in paragraph
6.3.3.
This command will produce a system configuration
report similar to the following.
Continue to paragraph
6.3.4.
Once the update has completed, the
error log will post a Firmware Event.
For the SPCN completion, the reference
code will be B1284633, with a word 13 value of A70Exxxx.
The Power Subsystem initiation reference
code will be 1011875B and the completion reference code will be 1011875C.
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.
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). The estimated time below includes a double
retry of code download to each FRU.
The update process is complete.
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.
End of Installation Instructions
Table 7.2
lists the distribution date and file information of previously released
firmware.
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
I/O
Drawer MDA (2 per drawer)
3
minutes
x
Minutes
Total
Time Required
Minutes
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
6.3 Using the Linux
Command-Line Method
Before installing this level of firmware, see Section
3.0 Cautions and Important Notes.
are allocated properly. This requires:
- 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.
6.3.1
Updating With Files Already Loaded on the Target Server
With the files located in the /tmp/fwupdate subdirectory,
/usr/sbin/update_flash
-f 3H050607.img
6.3.2 HMC
Restore Functions
To complete the update process,
6.3.3 Verifying the Update
Enter:
/sbin/lscfg -vp | grep -A 1 Platform
Platform Firmware:
ROM Level.(alterable).......3H050607
The ROM Level line should match the level of the you just installed, namely,
3H050607.
6.3.4
SPCN and Power Subsystem Update
To update the SPCN and Power Subsystem code, the
server MUST have Linux running. The update will take place
in the background. This may take up to four hours depending on your configuration.
Do NOT power down the system until you have verified (using the
completion reference codes below) that the SPCN and Power Subsystem code
updates have been completed.
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
I/O
Drawer MDA (2 per drawer)
3
minutes
x
Minutes
Total
Time Required
Minutes
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
6.4 Archiving the Update Files
In the event it becomes necessary to restore the server to a certain firmware
level, it is suggested you identify and archive the materials for each
update you install.
7.0 Appendix: Firmware History
Table 7.1
lists the description of previously released firmware.