pSeries 610 and IntelliStation Power 265 System and Service Processor Firmware
Update
Applies to : IBM pSeries 610 Models 6E1 (7028-6E1) and 6C1 (7028-6C1)
and IBM IntelliStation Power 265 (9112-265)
This document describes the installation of Licensed Machine Code, which
is sometimes referred to generically as microcode or firmware.
Contents
1.0 Systems Affected
This update provides new System and Service Processor (SvP) firmware (FW)
for pSeries 610 Models 6E1 (7028-6E1) and 6C1 (7028-6C1) and IntelliStation
Power 265 (9112-265) systems
only. Do
not use
on any other systems.
The firmware levels contained in this update are:
-
Sys FW: CLT05208
-
SvP FW: ct050428
The typical time to install this firmware is 0.8 hours. The firmware does
not become active when installed and requires a system reboot to
become active. The reboot time will vary depending on the system
and the amount of features installed. This estimate is for an average
system.
2.0 Firmware
Description and Revision History
Table 2.1 lists
the levels and descriptions for System firmware.
Table 2.2 lists
the levels and descriptions for Service Processor firmware.
Table
2.1: System Firmware Update Descriptions and History |
CLT05208 |
-
Added support for ARP (address request protocol).
-
On the IBM10/100 Mbps Ethernet PCI adapter (FC 2698), the default network
settings were changed to auto,auto.
|
CLT05118 |
-
Added support for FAT-16 filesystem.
-
Added support for changes made to redundant power supply design in
service processor.
|
CLT04194 |
-
Added support for AIX 5.3.
-
Corrected problem with auto negotiation at 10/100 speeds for 10/100/1000
Base-T Ethernet PCI Adapter (FC 2975).
-
GUI SMS menus replaced with text based menus.
-
Added remote IPL support in GUI SMS settings menu for 10/100 Mbps Ethernet
PCI Adapter II (FC 4962).
-
Added support to provide response to APR requests for Hot Standby Router
Protocol (HSRP) or other network processes that generate ARP requests during
NIM operations.
|
CLT03210 |
-
Companion level to Service Processor Firmware levels ct030818 and ct031013.
|
CLT03156 |
-
Resolves incorrect Power Supply Vital Product Data (VPD) displayed after
power supply is replaced.
-
Enhancements to SMS network adapter menus to resolve various configuration
issues and ping test failures.
-
Resolves potential cause for error 4B2711C4 during boot on systems equipped
with 333MHz processors.
-
Corrected boot failure with 'Default Catch' message displayed on console
when booting from tape media containing large boot image.
-
Resolves ethernet adapter link errors reported in AIX error log during
boot on systems equipped with IBM 4-Port 10/100 Ethernet Adapter (FC 4951),
IBM Universal 4-Port 10/100 Ethernet Adapter (FC 4961) or integrated adapters
based on these adapter types.
-
Enhancements to prevent potential ping and NIM boot failures on SP and
Cluster attached servers.
|
CLT03027 |
-
Corrected boot failure with checkpoint E1F6 displayed after bootlist is
set via AIX and more than 5 devices are specified.
-
Corrected missing devices in SMS bootlist when bootlist set via AIX.
-
Parameter change to limit bootlist entries set via AIX to 5.
-
Resolves incorrect power supply location codes and serial number Vital
Product Data.
|
CLT02219 |
-
Correction for NIM boot failure, through Ethernet, when spanning tree algorithm
is enabled on the port of the attached Ethernet switch.
-
Correction for boot failure when boot image (typically written to /dev/hd5)
is located beyond the first 4GB of storage, on a disk drive.
-
Correction for possible NIM boot, or SMS ping, failures across Ethernet.
CRC errors may be observed on the port of the attached Ethernet switch.
|
CLT02121 |
-
Corrected ping failure with "auto" speed selected for integrated adapter
and IBM 10/100 Ethernet PCI Adapter Feature Code 2968, Type 9-P.
|
CLT02066 |
-
Added support for new device id/vendor id for IBM Universal 4-Port 10/100
Ethernet Adapter (Feature Code 4961, Type A-E).
-
Correction for handling xoff character transmitted to ASCII terminal during
boot. Failure symptom: terminal would stop displaying data during
boot.
|
CLT02043 |
-
Corrected incorrect callout on memory DIMM failure.
-
Correction to allow return to SMS Utilities menu after a ping on any token
ring adapter.
-
Removed gateway IP address limitation for ping when client and server are
on same subnet - gateway address no longer has to be specified as 0.0.0.0.
-
Correction to SMS boot menu Next/Previous button.
-
Correction for SMS ping failures when system is not connected to a network,
or when "Media Type"(10 Base T, 100 Base TX, or Auto) is set incorrectly
(doesn't match setting at ethernet switch or hub).
|
CLT02011 |
-
Changed SMS "ping" routine: If "Server IP Address" is set to "0.0.0.0",
only ping "Gateway IP Address". If "Server IP Address" is not set
to "0.0.0.0", ping "Server IP Address".
|
CLT01334 |
-
Added support for IBM 10/100 Mbps Ethernet PCI Adapter II (Feature Code
4962, Type A-F).
-
Added support for HACMP heart beat on serial port 3.
-
Corrects interruption of NIM boot (via TFTP packet transfer) that was caused
by non-TFTP packet transfers. Failure symptoms vary: may hang at
E1F7 or 611, trouble booting in maintenance mode.
|
CLT01309 |
-
Companion level to Service Processor level ct011102.
|
CLT01277 |
-
Enhancements to SMS menus.
|
CLT01263 |
|
Table
2.2: Service Processor Firmware Update Descriptions and History |
ct050428 |
-
Mask current share fault for redundant power supply.
|
ct040528 |
-
Corrected problem with system time changes during Daylight Savings Time
transitions in locales where DST is not observed.
|
ct031013 |
-
Corrected intermittent failure to generate AIX dump and/or display of error
40110001 when Op Panel reset button is depressed.
|
ct030818 |
-
Corrects potential cause for errors 4B271151, 2B271122 or 4B20000A encountered
on new or replacement 333MHz CPU FRUs.
|
ct030605 |
-
Companion level to System Firmware level CLT030156.
|
ct030127 |
-
Resolves incorrect power supply location codes and serial number Vital
Product Data.
|
ct020822 |
-
Correction for misnaming of power supply's #1, and #3, in AIX. Power supply
in position #1 would be called power supply #3. Power supply in position
#3 would be called power supply #1.
-
Correction for possible failure to reboot when using the "shutdown -t"
command.
|
ct020607 |
-
Corrected false fan errors (LEDs on blowers, Indicator Panel/Light Path
LEDs for blowers, and System Fault LED will all come on).
|
ct020501 |
-
Companion level to System Firmware level CLT02121.
|
ct020307 |
-
Companion level to System Firmware level CLT02066
|
ct020211 |
-
Added support for CPU deconfiguration.
-
Added support for IntelliStation Power 265 (9112-265).
|
ct020110 |
-
Removed display of word "rebooting" on op-panel after an AC power
loss.
|
ct011130 |
-
Added support for HACMP heart beat on serial port 3.
-
Enhancements to power supply error reporting.
|
ct011102 |
-
Correction to isolate a checkstop failure (4B2xxx01, 4B2xxx02) to the correct
CPU.
|
ct011004 |
-
Corrected CPU id for checkstop failure isolation.
|
ct010920 |
|
3.0 Cautions and Important
Notes
ATTENTION: The firmware levels contained in this package MUST
be installed before installing AIX 5.3.
The System and Service Processor (SvP) firmware are combined into a
single file. This allows all the firmware to be updated together and assures
they are companion levels.
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.
Firmware Update Installation Is Not Concurrent
Installation of the firmware will cause an unconditional reboot of the
system. Therefore, all user operations should be gracefully terminated
before firmware updates are to be applied.
Avoid Potential Firmware Update Corruption
Some firmware corruptions are recoverable in the field, and repeating the
update will usually correct the problem. If the second update attempt
fails, replace the card containing the corrupted firmware module.
Here are some tips to help avoid the need for such recoveries.
Never power OFF the system during the firmware update process!
The update will be incomplete and will fail. Depending
on where in the update process the power was lost, a recovery attempt will
often succeed. One recovery attempt is worthwhile.
Replacement Parts May Require Updating
When a system planar is replaced, the system and service processor firmware
must be checked to ensure they are at the latest companion
levels. If they are not, update to the latest companion levels using
the instructions in this document.
Table
3.1 lists the released levels.
Table
3.1: Combined Firmware Levels, File Sizes and Checksums |
|
Combined System and SvP
Firmware |
Companion Levels Included |
Distribution Date |
Filename |
Size |
Checksum |
System FW |
SvP FW |
September 2005 |
cc05208.img |
1621114 |
32049 |
CLT05208 |
ct050428 |
May 2005 |
cc05118.img |
1621114 |
51552 |
CLT05118 |
ct050428 |
August 2004 |
cc04194.img |
1620934 |
13788 |
CLT04194 |
ct040528 |
December 2003 |
cc03286.img |
1620918 |
58188 |
CLT03210 |
ct031013 |
August 2003 |
cc03210.img |
1620870 |
29851 |
CLT03210 |
ct030818 |
June 2003 |
cc03156.img |
1620858 |
38585 |
CLT03156 |
ct030605 |
April 2003 |
cc03027.img |
1620778 |
60690 |
CLT03027 |
ct030127 |
August 2002 |
cc02219.img |
1620606 |
58653 |
CLT02219 |
ct020822 |
June 2002 |
cc02158.img |
1616190 |
25018 |
CLT02121 |
ct020607 |
May 2002 |
cc02121.img |
1619802 |
37210 |
CLT02121 |
ct020501 |
April 2002 |
cc02066.img |
1617654 |
28303 |
CLT02066 |
ct020307 |
February 2002 |
cc02043.img |
1617238 |
07036 |
CLT02043 |
ct020211 |
January 2002 |
cc02011.img |
1613690 |
39107 |
CLT02011 |
ct020110 |
December 2001 |
cc01334.img |
1613902 |
37081 |
CLT01334 |
ct011130 |
November 2001 |
cc01309.img |
1612434 |
63842 |
CLT01309 |
ct011102 |
October 2001 |
cc01277.img |
1612326 |
61554 |
CLT01277 |
ct011004 |
Original (GA) |
cc01263.img |
1611710 |
27774 |
CLT01263 |
ct010920 |
AIX Instructions are CASE SENSITIVE
In the instructions that follow are specific AIX and DOS commands.
AIX commands are CASE (lower and upper) SENSITIVE, and must
be entered exactly as shown, including the filenames. DOS commands
are not case sensitive, and may be entered without regard to the cases
shown.
How to Determine the Firmware Release Date
Level identifiers for the SvP FW use the 8-digit Gregorian date code method
in terms of year, month, and day (such as 050428 for ct050428 level).
The System FW uses the 5-digit Julian date code method in terms of day
number in a year (such as 05208 for CLT05208 level -- the 208th day of
2005 or July 27, 2005).
4.0
How to Determine Currently Installed Firmware Levels
DO NOT rely on the part number or firmware level marking/label on the EPROM/FLASH
module because the content of the module may have been updated to a different
level. To be safe, always check the firmware level electronically.
Two methods for reading the firmware levels are described below.
-
If the operating system is running, use the AIX command-line method.
Continue to paragraph
4.1.
-
If the operating system is not running, use the SMS Utilities method.
Skip to paragraph
4.2.
4.1 Using
AIX to Read Currently Installed Firmware Levels
To check the firmware levels,
Enter:
lscfg -vp |
grep alterable
This command will produce a system configuration report similar
to the following.
ROM Level.(alterable).......ct040528 <== Service Processor FW level
ROM Level.(alterable).......CLT04194 <== System FW Level
The ROM Level lines list the levels of the currently installed firmware.
In the above example, the current System firmware level is CLT04194, and
the current Service Processor firmware level is ct040528.
If the right-most five characters (date) of the current System FW level
are earlier than 05208 you should consider installing the update.
If the right-most six characters (date) of the current Service Processor
FW level are earlier than 050428, you should consider installing the update.
If you find the firmware levels are not correct companions, or that
they must be updated, proceed to Section
5.0. If the firmware levels are correct companions and
no update is needed, installation is complete.
4.2 Using
SMS Utilities to Read Currently Installed Firmware Levels
The System Management Services (SMS) Utilities may be accessed in two ways.
Instructions for these two methods are slightly different, so be sure to
choose the correct instructions for your environment.
4.2.1 If
Using an ASCII Terminal
Power on or shutdown and restart the system. At checkpoint E1F1 on
the operator panel, watch the terminal for the time to press the
"1" key. An indicator appears on the terminal as each system component
is self-tested. When the word "keyboard" appears, quickly press the
"1" key. The SMS menu will be displayed after startup testing has completed.
The current System and Service Processor firmware levels can be found
under the "View System Configuration Components" selection
on the SMS main menu. The System firmware level is shown under "System
Information" on the line "Firmware Level", and the Service Processor
firmware level is shown under "Service Processor Information" on
the line "ROS Level."
When you have read the current firmware levels, exit SMS as directed
on the menu screens.
If the right-most five characters (date) of the current System FW level
are earlier than 05208 you should consider installing the update.
If the right-most six characters (date) of the current Service Processor
FW level are earlier than 050428, you should consider installing
the update.
If you find the firmware levels are not correct companions, or that
they must be updated, proceed to Section
5.0. If the firmware levels are correct companions and
no update is needed, installation is complete.
4.2.2 If
Using a Graphics Console
Power on or shutdown and restart the system. At checkpoint E1F1 on
the operator panel, watch the console for the time to press the "F1" key.
An indicator appears on the console as each system component is self-tested.
When the keyboard icon appears, quickly press the "F1" key. The SMS
menu will appear when all the component tests have completed.
The current System and Service Processor firmware levels can be found
under the "Config" selection on the SMS main menu. The System
firmware level is shown under "System Information" on the line "Firmware
Level", and the Service Processor firmware level is shown under "Service
Processor Information" on the line "ROS Level."
When you have read the current FW levels, exit SMS as directed
on the menu screens.
If the right-most five characters (date) of the current System FW level
are earlier than 05208 you should consider installing the update.
If the right-most six characters (date) of the current Service Processor
FW level are earlier than 050428, you should consider installing
the update.
If you find the firmware levels are not correct companions, or that
they must be updated, proceed to Section
5.0. If the firmware levels are correct companions and
no update is needed, installation is complete.
5.0
Downloading and Unpacking the Firmware Update Package
Instructions for downloading and unpacking the firmware update package
follow.
5.1 Internet Package
The System and Service Processor Firmware, in AIX and DOS packages, is
located at the web site
http://www14.software.ibm.com/webapp/set2/firmware/gjsn
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:
-
Desc (Instructions document)
-
AIX (For downloading to an AIX
system or workstation)
-
DOS (For downloading to a Windows workstation)
You will want a copy of the instructions document and one of the download
choices. You may transfer files to the target system in one of several
ways.
-
By downloading files directly to the target system.
-
By downloading files to an intermediate AIX system and then using either
ftp or diskettes for transferring to the target system.
-
By downloading files to a Windows workstation from which you will use diskettes
for transferring to the target system.
Detailed download/unpacking instructions follow for each of the downloading
preferences.
5.1.1 Downloading the AIX
Package
Use this method to download to an AIX system.
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 package.
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 the filename is 70286E1F.BIN
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x
70286E1F.BIN
./70286E1F.BIN
[Don't overlook the periods (.) in
the above command.]
This file will be added to /tmp/fwupdate.
cc05208.img
If the above procedure was used to transfer files directly to the target
system, proceed to Section 6.0, Updating
the Firmware.
Otherwise, on the intermediate AIX system, choose one of the following
methods for transferring to the target system.
-
To transfer files to the target system via the ftp method, continue to
paragraph
5.1.1.1.
-
To transfer files to the target system via the diskettes method, skip to
paragraph
5.1.1.2.
5.1.1.1 The FTP Transfer
Method
This method presumes you have ftp access to the target system.
On the intermediate AIX system,
Enter the commands:
ftp {name
of target system}
{Login with a
valid userid and password}
bin
lcd /tmp/fwupdate
mkdir /tmp/fwupdate
cd /tmp/fwupdate
put cc05208.img
quit
Proceed to Section 6.0, Updating
the Firmware.
5.1.1.2 The Diskette
Transfer Method
This method can be used for cases in which electronic connections between
the intermediate AIX system and the target system are inconvenient.
Two 2MB (HD) new or freshly formatted diskettes are required.
With the first diskette loaded in the drive,
Enter the commands (this process will request
additional diskettes as each is filled):
cd /tmp/fwupdate
ls cc05208.img
| backup -i -v -f/dev/rfd0
This will produce AIX backup diskettes. Label these diskettes,
respectively,
"Volume 1: AIX Backup: Combined System (CLT05208)
and SvP (ct050428) FW
for 7028-6E1, 7028-6C1, and 9112-265"
"Volume 2: AIX Backup: Combined System (CLT05208)
and SvP (ct050428) FW
for 7028-6E1, 7028-6C1 and 9112-265"
Proceed to Section 6.0, Updating
the Firmware.
5.1.2 Downloading the DOS
Package
Use this method to download to a Windows workstation.
a) Prepare a directory for receiving the DOS package.
This directory can be in any partition
with 6MB 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 70286E1F.EXE
c) Unpack the file by executing the instructions below.
Enter the commands:
cd [path]\fwupdate
70286E1F
These files will be added to the fwupdate subdirectory:
286E1_B1.exe
286E1_B2.exe
5.1.2.1 Diskette
for AIX Command-Line Update Method
Two 2MB (HD) new or freshly formatted DOS diskettes are required.
a) With the first diskette loaded in the drive,
Enter the commands:
cd [path]\fwupdate
286E1_B1
Label this diskette,
"Volume 1: AIX Backup:
Combined System (CLT05208) and SvP (ct050428) FW
for 7028-6E1, 7028-6C1 and 9112-265"
b) With the second diskette loaded in the drive,
Enter:
286E1_B2
Label this diskette,
"Volume 2: AIX Backup:
Combined System (CLT05208) and SvP (ct050428) FW
for 7028-6E1, 7028-6C1 and 9112-265"
Note:
Any diskette labeled: 'AIX Backup: . . . .' is in a format that can be
used
directly with a computer running AIX as it's operating system. This
diskette cannot be read using PC tools or command line operations.
Proceed to Section 6.0, Updating
the Firmware.
5.2 Remote Installation
of Firmware
To install firmware on a remote system, login to the remote
system as root. Copy (in binary format) the firmware file, cc05208.img,
to the /tmp/fwupdate directory on the remote system. Section
6.0 Updating the Firmware.
6.0 Updating the Firmware
The System and Service Processor (SvP) firmware are combined into a single
file. This allows all the firmware to be updated together and assures they
are companion levels.
***
WARNING:
Do not power off the target system at any time before
the update process completes.
***
Note: Checksums can be used to verify files have not been
corrupted or altered during transmission.
At the AIX command
line, enter:
sum cc05208.img
This command
will produce the following output:
32049 1584 cc05208.img
The checksum
is ---> 32049
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.
6.1 Using the
AIX Command-Line Method
You must have root authority on the target system to update its firmware.
Because the update process will cause an automatic AIX reboot, be sure
the system is not running any user applications.
This method allows updating either from files already loaded into the
target system or from diskettes.
6.1.1 Updating
with Files Already Loaded in the Target System
With the files located in the /tmp/fwupdate subdirectory,
Enter the commands:
cd /usr/lpp/diagnostics/bin
./update_flash
-f /tmp/fwupdate/cc05208.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 system will apply the
new firmware, reboot and return to the AIX prompt. This may take
up to ten minutes, depending on the configuration of the target system.
While the update is in progress, you will see "Rebooting . . ."
on the display for as long as three minutes.
The firmware update is complete. You will want to verify the update
as described in paragraph 6.2.
6.1.2 Updating from
AIX Backup Diskettes
On the target system,
Enter the commands:
mkdir /tmp/fwupdate
Note: If the directory /tmp/fwupdate
already exists,
make sure it is empty before proceeding.
cd /tmp/fwupdate
restore
You will be prompted to mount volume 1 on /dev/rfd0
In the drive of the target system, put the AIX backup diskette labeled,
"Volume 1: AIX Backup: Combined System (CLT05208) and SvP
(ct050428) FW
for 7028-6E1, 7028-6C1 and 9112-265"
When prompted for volume 2,
In the drive of the target system, put the AIX backup diskette labeled,
"Volume 2: AIX Backup: Combined System (CLT05208) and SvP
(ct050428) FW
for 7028-6E1, 7028-6C1 and 9112-265"
The file is now located in the /tmp/fwupdate subdirectory.
Enter the commands:
cd /usr/lpp/diagnostics/bin
./update_flash
-f /tmp/fwupdate/cc05208.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 system will apply the
new firmware, reboot and return to the AIX prompt. This may take
up to ten minutes, depending on the configuration of the target system.
While the update is in progress, you will see "Rebooting . . ."
on the display for as long as three minutes.
The firmware update is complete. You will want to verify this update
as shown in paragraph 6.2.
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.
6.2 Verifying the Updates
To verify the firmware update was successful, use the following AIX
command after the automatic reboot.
To check the firmware levels
Enter:
lscfg -vp |
grep alterable
This command will produce a system configuration report similar
to
the following.
ROM Level.(alterable).......ct050428 <== SvP FW level
ROM Level.(alterable).......CLT05208 <== System FW level
The ROM Level lines list the level of the newly installed System and Service
Processor firmware. For System FW, the level should now be CLT05208.
For Service Processor FW, the level should now be ct050428.
6.3 Archiving the Update
Files
In the event it becomes necessary to restore the system to a certain firmware
level, it is suggested you identify and archive the materials for each
update you install.
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