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:
NOTE: If your firmware level is RR021024 or earlier, you must use the instructions in this document to update your firmware manually.
Before installing this level of firmware, AIX 5.1.0 should be updated to Maintenance Level 3 (APAR IY32749).
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.
Updating the firmware may result in the HMC going into 'Recovery' state. Before updating the firmware, make sure the backup of Profile Data is complete (if running LPAR).
Enter:
lscfg -vp | grep -p Platform
This command will produce a system configuration report similar to the following.
Platform Firmware: ROM Level.(alterable).......3R040602 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 3R040602.
If the right-most six characters (date) of the current firmware level are earlier than 050715, 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 050715, 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.
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).......3R040602The ROM Level line lists the level of the currently installed firmware. In the above example, the current firmware level is 3R040602.
If the right-most six characters (date) of the current firmware level are earlier than 050715, 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.
Enter:
mkdir /tmp/fwupdate
Note: If the
directory /tmp/fwupdate already exists,
make sure it is empty before proceeding.
cd /tmp/microcode/RPM
mv 3R050715.rpm /tmp/fwupdate
cd /tmp/fwupdate
rpm -ihv --ignoreos 3R050715.rpm
The 3R050715.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 3R050715.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 recover mode, you will need to make diskettes on a system running AIX as follows:
Four 2MB (HD) new 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 *.img | backup -i -v -f/dev/rfd0
This will produce AIX backup diskettes. Label these diskettes, respectively,
"Volume 1: Firmware (3R050715) for pSeries 630 (7028-6C4) and (7028-6E4)"
"Volume 2: Firmware (3R050715) for pSeries 630 (7028-6C4) and (7028-6E4)"
"Volume 3: Firmware (3R050715) for pSeries 630 (7028-6C4) and (7028-6E4)"
"Volume 4: Firmware (3R050715) for pSeries 630 (7028-6C4) and (7028-6E4)"
Proceed to Section 6.0 Updating the Firmware.
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.
***
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
3R050715.img
The output will look
like this -----> 07826 4977 3R050715.img
The checksum is ------------->
07826
Service Processor Menus allow updating from AIX backup diskettes only.
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,
If using
an ASCII terminal - Press Enter
If using
an HMC terminal - close the current terminal window and open a new terminal
window.
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 the screen.
The second line of
the title, Version: 3R050715, 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.
NOTE: If you are running Native Linux,
- choose 2 System Power Control Menu
- choose 7 Boot Mode Menu
- Enable the Linux compatibility mode by choosing 1 (if currently disabled).
The firmware update is complete.
You must have root authority on the target server to update its 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: Firmware (3R050715) for pSeries 630 (7028-6C4) and (7028-6E4)"
When prompted for volume 2,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 2: Firmware (3R050715) for pSeries 630 (7028-6C4) and (7028-6E4)"
When prompted for volume 3,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 3: Firmware (3R050715) for pSeries 630 (7028-6C4) and (7028-6E4)"
When prompted for volume 4,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 4: Firmware (3R050715) for pSeries 630 (7028-6C4) and (7028-6E4)"
The file is now located in the /tmp/fwupdate subdirectory. Continue to paragraph 6.1.2.2.
With the files located in the /tmp/fwupdate subdirectory.
Enter the commands:
cd /usr/lpp/diagnostics/bin
./update_flash -f /tmp/fwupdate/3R050715.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.
ATTENTION: You may get error codes 4B2E26FB, 4B2E26FD or
40640EAF depending on the type of processor card(s) installed in the system.
You will be in the Service Processor Main Menu. To continue the firmware
update process:
1) Press the white button on the operator panel.
2) Within a minute, the operator panel will display 9022.
3) Press the white button again.
4) Within a minute, the operator panel will display OK.
5) The second line of the title on the Service Processor Menu
will match the firmware level you just
installed.
The update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.
You must have root authority on the target server to update its firmware.
This method allows updating from files already loaded onto the target server.
With the files located in the /tmp/fwupdate subdirectory,
Enter the commands:
cd /tmp/fwupdate
/usr/sbin/update_flash
-f 3R050715.img
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 first line on the Operator Panel shows Linux ppc64.
ATTENTION: You may get error codes 4B2E26FB, 4B2E26FD or
40640EAF depending on the type of processor card(s) installed in the system.
You will be in the Service Processor Main Menu. To continue the firmware
update process:
1) Press the white button on the operator panel.
2) Within a minute, the operator panel will display 9022.
3) Press the white button again.
4) Within a minute, the operator panel will display OK.
5) The second line of the title on the Service Processor Menu
will match the firmware level you just
installed.
The update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.
Service Processor Menus allow updating from diskettes only.
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,
If using
an ASCII terminal - Press Enter
If using
an HMC terminal - close the current terminal window and open a new terminal
window.
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 the screen.
The second line of
the title, Version: 3R050715, 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.
NOTE: If you are running Native Linux,
- choose 2 System Power Control Menu
- choose 7 Boot Mode Menu
- Enable the Linux compatibility mode by choosing 1 (if currently disabled).
Power on the system. If the HMC goes into Recovery state, skipto paragraph 6.3 HMC Restore Functions to complete the procedure. Otherwise, the firmware update 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
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: Firmware (3R050715) for 7028-6C4 and 7028-6E4"
When prompted for volume 2,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 2: Firmware (3R050715) for 7028-6C4 and 7028-6E4"
When prompted for volume 3,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 3: Firmware (3R050715) for 7028-6C4 and 7028-6E4"
When prompted for volume 4,
In the drive of the target server, put the AIX backup diskette labeled:
"Volume 4: Firmware (3R050715) for 7028-6C4 and 7028-6E4"
The file is now located in the /tmp/fwupdate subdirectory. Continue to paragraph 6.2.2.2.
With the file located in the /tmp/fwupdate subdirectory,
Enter the commands:
cd /usr/lpp/diagnostics/bin
./update_flash
-f /tmp/fwupdate/3R050715.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 and open a new terminal window 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 HMC goes into Recovery state, skip to paragraph 6.3 HMC Restore Functions to complete the procedure. Otherwise, the update of the firmware is complete. You will want to verify the update as shown in paragraph 6.4.
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 Linux 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 from files already loaded onto the target server.
With the files located in the /tmp/fwupdate subdirectory,
Enter the commands:
cd /tmp/fwupdate
/usr/sbin/update_flash
-f 3R050715.img
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 HMC goes into Recovery state, skip to paragraph 6.3 HMC Restore Functions to complete the procedure. Otherwise, the update of the firmware is complete. You will want to verify the 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).......3R050715 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, 3R050715.
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).......3R050715The ROM Level line should match the level of the you just installed, namely, 3R050715.
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