pSeries 690 and 670 Version 3 Firmware Update

Applies to:  pSeries 690 Model 681 (7040-681), pSeries 670 Model 671 (7040-671)

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 firmware (FW) for pSeries 690 Model 681 (7040-681) and pSeries 670 Model 671 (7040-671) Servers only.  Do not use on any other systems.

The Version 3 firmware level contained in this update is:

Before installing this level of firmware, see Section 3.0 Cautions and Important Notes.

ATTENTION:  Due to significant fixes in 4th quarter 2003 and 1st quarter 2004 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.


2.0 Firmware Description

Firmware Versions

To maintain support for multiple versions of firmware, the name of the firmware has been changed to reflect it's version number.  The new name replaces the letter R with the version number (example 3Hyymmdd instead of RHyymmdd).  The firmware updates for each version will be distinguished by the having the leading number reflect the version.

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 3H080425

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:  Firmware File Information and Update Description
  Filename Size Checksum
May 2008 3H080425.img 6412002 32867
 3H080425 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • A problem was fixed that caused the time-of-day clock to gain one second every time the system or partition was rebooted.

For information about previous firmware levels,  see Section 7.0 Appendix:  Firmware History.


3.0 Cautions and Important Notes

The System, Service Processor (SvP), System Power Control Network (SPCN) and Power Subsystem firmware are combined into a single file.

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 Beginning the Update

These instructions CAN ONLY be used to update any pSeries 690 or pSeries 670 Servers that currently have Version 3 level firmware installed. See Table 4.1 Update Decisions for more details.

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 the backup of Profile Data is complete (if running LPAR).

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.

Linux

To update firmware from a Linux partition, you must first download and install the following service tools on your server: Platform Enablement Library, Service Aids, and Hardware Inventory. To obtain these service tools, go to  https://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/home.html and follow the instructions on this web site for downloading and installing the service tools.

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.

Never Power Off the System During the Firmware Update Process

The update will fail, and the process must be repeated.

AIX  and Linux Instructions are CASE SENSITIVE

In the instructions that follow are specific AIX, Linux and DOS commands. AIX and Linux 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.


4.0 How to Determine Currently Installed Firmware Level

The firmware level can be checked in AIX, in the Service Processor Main Menu, or in Linux.

4.1 Using AIX to Read Currently Installed Firmware Levels

Use the following AIX command for checking the firmware level.

         Enter:
            lscfg -vp | grep -p  Platform

       This command will produce a system configuration report similar to the following.

     Platform Firmware:
          ROM Level.(alterable).......3H061030
          Version.....................RS6K
          System Info Specific.(YL)...U1.18-P1-H2/Y2

        Physical Location: U1.18-P1-H2/Y2
The ROM Level line lists the level of the currently installed firmware. In the above example, the current firmware level  is 3H061030.

For information on how to proceed, See Table 4.1 Update Decisions.

4.2 Using the Service Processor Main Menu

The second line of the title, Version: 3H061030 shows the currently installed firmware level.

For information on how to proceed, See Table 4.1 Update Decisions.

4.3 Using Linux to Read Currently Installed Firmware Levels

Use the following Linux command for checking the firmware level.

         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).......3H061030
The ROM Level line lists the level of the currently installed firmware. In the above example, the current firmware level is 3H061030.

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 3H070425  (Version 3) 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.


5.0 Downloading and Unpacking the Firmware Update Package

Instructions for downloading and unpacking the firmware update package follow.

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.

5.1 Internet Package

The firmware, in AIX, DOS and RPM packages, along with impact and severity information, is located at the web site:

     download.html

Follow the instructions on this web page. You must read and agree to the license agreement to obtain the firmware packages.

In the drop-down box, choose the entry for your specific machine type and model.

 The download choices at that entry are:

You will want a copy of the instructions document and one of the download choices. You may transfer files to the target server in one of several ways. 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.

  a) Provide a directory on an AIX system to receive the AIX package 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.]

 This file will be added to  /tmp/fwupdate:

      3H080425.img
 

If the above procedure was used to transfer files directly to the target server,  proceed to Section 6.0, Updating the Firmware.

Otherwise, on the intermediate AIX system, choose one of the following methods for transferring files to the target server.

5.1.1.1 The FTP Transfer Method

This method presumes you have ftp access 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 3H080425.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 server are inconvenient.

 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 (3H080425) for 7040-681 and 7040-671"

     "Volume 2:  Version 3 Firmware (3H080425) for 7040-681 and 7040-671"

     "Volume 3:  Version 3 Firmware (3H080425) for  040-681 and 7040-671"

     "Volume 4:  Version 3 Firmware (3H080425) for 7040-681 and 7040-671"

     "Volume 5:  Version 3 Firmware (3H080425) for 7040-681 and 7040-671"

Proceed to Section 6.0, Updating the Firmware.

5.1.2 Downloading the DOS Package

Use this file to download to a Windows workstation.

  a) Prepare a directory for receiving the DOS package.
      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 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

5.1.2.1 Diskettes for Firmware Updates

Five 2MB (HD) new or freshly formatted DOS diskettes are required.

 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 (3H080425) 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 (3H080425) 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 (3H080425) 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 (3H080425) 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 (3H080425) for 7040-681 and 7040-671"

Proceed to Section 6.0 Updating the Firmware.

5.1.3 Downloading the RPM Package to the Target Server

Use this method to download to the target server only.

 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 3H080425.rpm

  c) Unpack the file by executing the instructions below.

     Enter the commands:

        rpm -ihv --ignoreos 3H080425.rpm

The 3H080425.img file will be added to  /tmp/fwupdate.

The file size and checksum will be verified.

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 file, 3H080425.img  to the /tmp/fwupdate directory on the remote system.  Proceed to Section 6.0 Updating the Firmware.


6.0 Updating the Firmware

The System, Service Processor (SvP), System Power Control Network (SPCN) and Power Subsystem firmware are combined into a single file.

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 target 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 3H080425.img

         The output will look like this ------>   32867  6262  3H080425.img

         The checksum is -------------->   32867

Updating firmware must be initiated either directly from the Service Processor Menus, from the AIX command line or the Linux command line.

6.1  Using the Service Processor Menus Method

Before installing this level of firmware, see Section 3.0 Cautions and Important Notes.

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.

6.1.1  System and Service Processor Firmware Update

    a. Choose 1 for Service Processor Setup Menu.  <Enter>

    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: 3H080425, should match the firmware level you just
          installed.

Continue to paragraph 6.1.2.

6.1.2 SPCN and Power Subsystem Update

     a.  Choose 3 for System Information Menu.  <Enter>

     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 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.

6.1.3 HMC Restore Functions

    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.

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.

6.2 Using the AIX Command-Line Method

Before installing this level of firmware, see Section 3.0 Cautions and Important Notes.

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.

6.2.1 File on Diskettes

On the target server,

        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 (3H080425) 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 (3H080425) 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 (3H080425) 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 (3H080425) 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 (3H080425) 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.

6.2.2 Updating With Files Already Loaded on the Target Server

Before installing this level of firmware,  see Section 3.0 Cautions and Important Notes.

With the file located in the /tmp/fwupdate subdirectory,

       Enter the commands:

           cd /usr/lpp/diagnostics/bin
          ./update_flash -f /tmp/fwupdate/3H080425.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.

6.2.3 HMC Restore Functions

If the OP Panel on the server displays OK and the Managed System state on the HMC is either RECOVERY or INCOMPLETE,

    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.

6.2.4 Verifying the Update

        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).......3H080425
        Version.....................RS6K
        System Info Specific.(YL)...U1.18-P1-H2/Y2
      Physical Location: U1.18-P1-H2/Y2
The ROM Level line should match the level you just installed, namely, 3H080425.

Continue to paragraph 6.2.5.

6.2.5  SPCN and Power Subsystem Update

To update the SPCN and Power Subsystem code, the server MUST have AIX 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.

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 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

The update process is complete.

6.3 Using the Linux Command-Line Method

Before installing this level of firmware, see Section 3.0 Cautions and Important Notes.

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.

6.3.1 Updating With Files Already Loaded on the Target Server

With the files located in the /tmp/fwupdate subdirectory,

     Enter the commands:

         cd /tmp/fwupdate
        /usr/sbin/update_flash -f  3H080425.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 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.

6.3.2 HMC Restore Functions

To complete the update process,

    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.

6.3.3 Verifying the Update

         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).......3H080425
The ROM Level line should match the level of the you just installed, namely, 3H080425.

Continue to paragraph 6.3.4.

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.

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 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

The update process is complete.

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.

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


 7.0 Appendix:  Firmware History

Table 7.1  lists the description of previously released firmware.

Table 7.2  lists the distribution date and file information of previously released firmware.
 
Table 7.1:  Firmware Update Description History
Version 3
3H080425 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • A problem was fixed that caused a failure with error code 20EE000B when upgrading to later AIX versions with large boot images.

  • A problem was fixed that caused Linux to fail to boot if there were more that 256 characters in the boot string.
3H061030 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • Aproblem was fixed that caused the ring indicate power-on function (in the service processor menus) to power on the system even though it was set to "disabled".
  • A problem was fixed that caused the system to hang at E52A when rebooted after SRC B1274634 ("SPCN loop fault") was reported.
3H060917 IMPACT:   Serviceability     SEVERITY:   Special Attention
 
  • A problem was fixed that was causing the calls to system firmware to set the  time-of-day clock to take too long and prevent interrupts on single processor systems.  This can cause adapter errors due to overruns which may result in hangs or retries depending on the adapters and system activity.
3H060626 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • A problem was fixed that was causing enhanced error handling (EEH) error codes to be erroneously generated when certain adapter card configurations were heavily stressed by the application code.
  • A problem was fixed that was causing the system to crash when error data was retrieved.
  • A problem was fixed that was causing "ghost" adapters to appear in the configuration on 7040-61D I/O drawers after a hot plug operation.
  • In a system with high performance switches, a problem was fixed that caused the switch adapter to crash after a reset under certain circumstances.
3H060109 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • Fixed a problem that was causing the AIX logical location codes of the Ethernet ports to be incorrect when several types of multi-port Ethernet adapter cards were replaced using the PCI hot-plug function.
3H051122 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • A problem was fixed that was preventing enlarged I/O capacity from functioning in the high-speed version of the 7040-61D I/O drawer.
  • A problem was fixed that was causing the service mode bootlist to be overwritten by the normal mode bootlist.
  • The firmware was changed so that the time-out for firmware console selection is 60 seconds no matter how many devices are attached to the system or partition.
  • Changes were made in the yellow button reset firmware path (in the service processor code) so that only licensed and configured processors are reset, instead of all processors, in full system partition mode. This enables the system to perform a dump when it has a mix of licensed and unlicensed processors.
  • Firmware was updated to fix intermittent failures of the AIX command "shutdown -t" to power on. 

  • Various enhancement to the microcode on the High-Performance Switch adapter
3H050715 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • Added support for address request protocol (ARP).
  • A problem was fixed that was causing the firmware to report an error on an I/O slot when no I/O adapter card was present.
  • A problem was fixed that was causing the PCI bus to report an error when a PCI adapter with a bridge on it was hot-plugged.
  • An invalid error code callout for clock errors was fixed.
  • Various fixes and updates to the high performance switch interface code.
3H050607 IMPACT:   Serviceability     SEVERITY:   Programming Error
  • Fixes a problem that causes the system to crash when AIX tries a reset on a slot which is already in the reset state. 
3H050405 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • Improved isolation for Remote I/O (RIO) loop failures.
  • Corrects system Time of Day gains observed after reboot.
  • Ensures that the SPCN and Power code informational error codes do not cause system interrupts.
3H050215  IMPACT:  Function     SEVERITY:  Special Attention
  • Change made to collect hypervisor dump as part of snap command.
  • Change made to mask interrupts for a specific slot if a problem is encountered with and I/O adapter.
  • Resolves an MCM logic condition such that an unwarranted checkstop is prevented.
  • Resolves a problem that prevented the hard reset of a partition from working every time.
  • Corrects a problem that caused incorrect tracking of CUoD activation time.
  • Corrects a problem that resulted in ON/OFF CUoD processors suddenly being deactivated.
  • Resolves the problem that caused informational firmware events (B1008FF0) to be posted after an ON/OFF event.
  • Resolves an issue with the firmware reset handler in order to prevent an LPAR hang condition.
  • Includes additional High Performance Switch enhancements.
3H041029 IMPACT:  Function     SEVERITY:  Special Attention
  • Added support for network boot when target server provides preferred gateway information in bootp reply.
  • Added support for PCI adapters that require additional memory I/O space (Future OEM vendor requirement).
  • Corrects network boot problems with IBM Gigabit Ethernet adapters (FC 2969).
  • Resolves issue where On/Off CUoD reclaims more processors than it should if system is allowed to go out of compliance.
  • Resolves issue where On/Off CUoD posts change event messages when ON/OFF resources are no longer in use.
  • Corrects a condition where all logical partitions  would terminate due to an incorrect bit being set for a correctable machine check interrupt, resulting in a system level hypervisor dump.
3H041021 IMPACT:  Function     SEVERITY:  Special Attention
  • Resolves issue of excessive length of time required to collect AIX dump for partitions with Service Authority assigned.
  • Corrects potential cause for system hang with error 40670EA1 on systems with Linux Operating System.
  • Corrects loss of one hour of resource time when activating On/Off CUoD resources.
  • Corrects potential cause for system crash,  during a concurrent CEC/DCA replacement, only on system with 1.9GHz MCMs.
  • Includes additional High Performance Switch enhancements.
3H040901 IMPACT:  Function     SEVERITY:  Special Attention
  • Corrects a condition where on a Primary/Secondary I/O book with RIO ports (PCI) a bit may be erroneously set causing a system crash due to a GX Data Timeout, while being reported to diags as SRN 651-900 and posting a firmware error code of 40670EA4 (bus test detected fault in service processor code).
  • Corrects the FRU callout/priorities for a 406E0001 (scr_clock_stop) errors.
  • Corrects a condition where after updating firmware it is found that the time reported on LPARs had drifted.

  • Includes additional High Performance Switch enhancements.
3H040602 IMPACT:  Performance     SEVERITY:  Attention
  • Performance enhancements for High Performance Switch.
  • Prevents informational checkpoints E900 and E901 from being displayed on the operator panel during runtime for extended periods.
  • Increased HMC surveillance timeout value to prevent false 'loss of communication' errors.
  • Eliminates false mp_fatal errors from being reported. 
  • Corrects the informational message reported when a power redundancy error is encountered during the code update.
  • Corrects the VPD FRU number formatting reported to AIX for L3 memory modules.
  • Corrects a condition where on a Primary/Secondary I/O book with RIO-2 ports (PCI-X) a bit may be erroneously set causing a system crash due to a GX Data Timeout, while being reported to diags as SRN 651-900 and posting a Firmware error code of 40670EA4 (Bus test detected fault in service processor code).
3H040528 IMPACT:  NA     SEVERITY:  NA
  • Added support for AIX 5.3.
  • Changes made for manufacturing enhancements.
3H040503 IMPACT:  Function  SEVERITY: Attention
  • Adds support for using previously released memory books with the higher speed MCMs.
  • Corrects a condition where the failure of a component in an I/O (7040-61D) drawer DCA-BC  posts a critical over current fault causing  the I/O drawer to power off and the associated partitions to crash with an SRN of A03-041 and a firmware error code of 20D10011.
  • Corrects a condition that caused a performance degradation when the RIO-G bus is configured in double barrel mode.

  • Corrects a condition that caused a High Performance Switch (7045-SW4) adapter to be uninitialized in some cases.  This  lead to erroneous mp_fatal errors and could crash of the system.
3H040326 IMPACT:  Function SEVERITY: Attention
  • Corrects a problem where 20D009xx errors were not being reported to the operating system during a reboot.
  • Corrects an initialization setting in the service processor firmware that caused an invalid FAST(43) bit errors from being reported.
  • Corrects false B1314633 (with a word 13 value of A716xxxx),  "Power Subsystem code update has been interrupted" errors from being reported.
  • Added support for High Performance Switch adapters in systems with 1.9 GHz MCMs.
  • Added support for 1.3 GHz MCMs in a p670 (7040-671).
  • Corrects a condition where a soft reset of a logical partition (LPAR) could cause all logical partitions to crash.
  • Added a FRU callout for SRN A03-150,  "I/O Expansion Bus Connection Failure".
  • Corrects a condition that results in the AIX location code being incorrect after resources have been re-assigned during a dynamic LPAR operation.
  • Added support for system boot from devices containing boot images larger than 12MB.  Must be used in conjunction with AIX 5.1 APAR IY57522 or AIX 5.2 APAR IY56839. To create a boot image larger than 12MB, you must first apply the appropriate APAR.  The firmware must be at 3H040326 (or later) before the image can be restored.
3H040301
  • Adjustments made to PLL bit for 1.5 GHz, 1.7 GHz and 1.9 GHz MCMs to improve reliability.
3H040214
  • Added support for 1.9 GHz MCMs.
  • Added support for the 633 MHz memory card feature.
  • Provides RAS enhancements.
  • Corrects LPAR hang condition during concurrent CEC DCA replacements on systems with 1.5 GHz and 1.7 GHz MCMs. 
3H040130
  • Corrects location code designation for the Service Processor battery FRU.
  • Adds the primary I/O book to the FRU list for certain incidents of the A01-011 SRN.
3H031218
  • Corrects a potential checkstop condition while concurrently replacing a CEC DCA on a system  with a 101C5A16 error.
3H031118
  • Corrects power code problem that causes I/O planars to power down when flashing firmware from Version 2 to Version 3.
  • Corrects power subsystem errors after a power line disturbance indicated by 10118711, 10118731, and possibly B00E hangs.
  • Addresses miscellaneous pSeries High Performance Switch tuning issues.
  • Corrects diagnostic FRU callout for SRN A01-011; now includes the applicable I/O book.
  • Corrects erroneous capacity on demand (CoD) error messages being posted hourly on non-COD systems.
  • Corrects FRU callout for I/O bridge/internal device error; now includes the applicable I/O book.
  • Corrects a condition where the soft reset of a partition may cause a system crash.
3H031024
  • Added support for pSeries High Performance Switch (7045-SW4) including the applicable adapters FC 6432 and FC 6434.
  • Eliminates an erroneous memory error from being logged on the first boot after system firmware has been installed.
  • Corrects AIX location code mismatch when PCI-X I/O backplane (FC 6571) is being installed.
  • Modified timing to ensure SPCN code updates in conjunction with system and service processor firmware.
  • Changes made to limit the occurrences of NOT_VALID_VPD type errors. Also added details to error description to better understand root cause of the error.
  • Corrects diagnostic FRU call for SRN A08-340 to include L3 module.
  • Corrects a problem where after activating On/Off Capacity on Demand (CoD), the op panel would be blank when it should indicate LPAR.
3H031021 NOTE:  This level of firmware is certified compliant to the Common Criteria (CC), an international standard (ISO/IEC 15408) for evaluation of information technology product security.
  • Modified timing to ensure SPCN code updates in conjunction with system and service processor firmware.
  • Attention light will no longer activate for informational error messages.
  • Fix for CUoD code to only run on CUoD systems.
  • Modification to handle different keyfields for NAS Gateway.
3H031007
  • Manufacturing only.
3H030916 NOTE:  This release contains a significant number of improvements and changes which are too numerous to document individually.  Only those items of common interest or high impact are documented.  Customers are strongly encouraged to install this release.
  • Added support for On/Off Capacity on Demand (CoD).
  • Corrects time synchronization problem on CUoD processors added via DLPAR operation.
  • Added support for new BPR. 
  • Corrects erroneous error code 25B00004 from being reported for a repeat gard error.
  • System will now indicate processor was manually deallocated when cpu_deallocate command is issued.
  • Added error detection when a BIST error occurs on I/O EADS chip.
  • Updated the Service Processor Main Menu to include the 'Start SPCN Flash Update' function.
  • Corrects MCM FRU callout for data parity error on the bus.
  • Corrects an erroneous SRN 9CC-100 when the operating system discovers and repairs a deskew event.
  • Corrects AIX location code discrepancies for integrated SCSI devices when using DLPAR.
  • Corrects the SPCN auto download requirements for systems implementing the X-frame.
3H030905
  • Corrects memory controller timing to prevent a false fail during manufacturing mode IPLs.
3H030811
  • Required when MCM P/N Number 44P4719 is installed in system.
  • Corrects erroneous error code 101C7F06 seen during start of IPL.
  • Corrects system from being stuck in calibration (error code 101100CA) during start of IPL.
  • Corrects SCR clock start failure during L3 initialization for 1.5GHz and 1.7GHz MCMs.
  • Corrects erroneous error codes 10118710/10118711 during IPL after a firmware update.
  • Corrects erroneous error code 101C5Ax6 during Power Subsystem code download.
  • Corrects one potential cause of boot failures (with error code 450E25E7 or 4B2E25E9) on systems equipped with 1.7 GHz MCMs.
3H030703
  • Corrects an erroneous error being reported to AIX during a slow boot on systems with two or three MCMs installed.
3H030617
  • Required when primary MCM0 (C1, north) has a CCIN 526B (see lscfg) and CUoD MCMs are installed.
3H030608
  • Corrects a hypervisor problem that results in an AIX crash with a PROGRAM_INT signature.
  • Added sensing to check DCA code version prior to logically powering on DCA.
3H030524 NOTE:  This release contains a significant number of improvements and changes which are too numerous to document individually.  Only those items of common interest or high impact are documented.  Customers are strongly encouraged to install this release.
  • Added support for 1.5 GHz and 1.7 GHz MCMs.
  • Reliability enhancements for adapter recovery during an EEH event.
  • Corrects configuration problems with IBM 3581 Ultrium Tape Autoloader. 
  • Resolved incorrect PCI adapter AIX location codes when adapters are added or reassigned via a DLPAR operation. 
  • Added details to error description for exceeding plug count errors.
  • Corrects graphical representation of MCM/L3 interposer plug count menu. 
  • Corrects problem in NVRAM which reported a 20EE000B when rebooting after updating system and service processor firmware.
  • Resolved incorrect identify and power LED behavior during PCI adapter hot plug operations.
  • Corrects diagnostics FRU priority callout.
  • Corrects location code in the error logs for U1.18-P1-H2 that had been showing as U1.18-P1-H2 /Y3.
  • Added an error signature for when the SPCN code does not load successfully when the system and service processor firmware is updated.
  • Corrects erroneous checkstop condition reported as 40670EA1.
  • Corrects time loss on LPAR systems.
  • Corrects 4-way affinity partitions (ALPAR) failure to boot. 
RH030307
  • Added additional time for correctable errors to be resolved before impacting system/LPAR operation.
  • Corrects potential cause for hang during boot at error 2B0x00EE  or B1xx4691 with 'default catch' message displayed on console of systems equipped with CUoD resources.
  • Corrects an intermittent problem where the SPCN portion of the system firmware is not loaded correctly.
  • Prevents AIX and HMC CPU status information from getting out of sync during a Dynamic Processor Sparing operation.
  • Corrects erroneous 'Note Supported' message when exiting from the Service Processor Interposer Plug Count menu.
  • Corrects system hang during boot with bad date/time stamp in AIX banner and 'default catch' message displayed on console.
  • Corrects false L3 Cache error and deconfiguration during system initialization.
  • Changed initialization routines for high performance PCI adapters to allow best use of available bandwidth.
  • Fixes failures during ping or NIM boot attempted via SMS when configured in an SP environment.
  • Provides potential performance enhancement for SP Switch2 PCI Attachment Adapters, Feature Code 8397.
  • Provides additional I/O resource information in HMC menus when in Full System  partition mode.
  • Corrects initialization routines for high performance PCI adapters to ensure best performance after a hot plug operation.
  • Corrects erroneous FRU location for error 20FC0020.
  • Corrects erroneous message regarding a required recover operation when attempting to add adapters to a partition.
  • Corrects time loss on machines running in LPAR mode.
  • Corrected a situation where the System Attention LED would not reactivate upon a system reboot.
RH021114
  • Added support for On Demand Resource Capacity Upgrade (CUoD).
  • Improved failure isolation for CEC-DCA failures.
  • Eliminates intermittent BIST fail in primary and secondary I/O books during IPL
RH021025
  • Improved error detection to prevent checkstops.
  • Corrects SRC B1024696 (CSP LIC error) from being logged erroneously.
  • Change made to the TOD internal reporting which will correct TOD messaging.
  • Prevents bootlist from being corrupted while upgrading firmware.
  • Corrects potential L3 cache data recovery error.
  • Added support for Dynamic modification of Logical Partition Resources (DLPAR).
  • Added support for LED for CEC and I/O FRU identification.
  • Added support for notification and logging of RIO error handling.
  • Added support for MCM interposer plug tracking.
  • Added support for boot time array repair.
  • Added support for redundant RIO link hotplug.
Version 2
2H040323 IMPACT:  Function     SEVERITY:  Attention
  • Additional enhancement to support 633MHz memory cards.
2H040202
  • Added support for the 633 MHz memory card feature.
2H030325
  • Corrects adapter status after logically removing an adapter via a PCI Hot Plug action.  Adapter is then available for reassignment to other LPARs.
  • Added support for the 600MHz memory card feature.
RH021024
  • Fix for apparent garding of processors without a real fault.
  • Fix for SRN 101C7F06 (related to Retain Tip H76544).
  • Corrects potential L3 cache data recovery error.
RH020822
  • Fixes a potential data error situation.
  • Improves FRU call for clock card failures.
  • Changes L3 performance settings to Mode A as a default for p670 (7040-671) systems.
  • Improves isolation of memory problems during an uncorrectable memory error.
  • Fixes timing window issue which can only happen during reset/reload.
  • Changes recovery actions to deconfigure processor for L2 Directory Error.
  • Prevents error code 10118402 (VPD Error) from being logged during initialization.
  • Improves isolation of NVRAM Low Battery Warning.
  • Changes recovery action to Checkstop on uncorrectable error from memory.
  • Improves error detection for BPR failure with single phase power.
  • Corrects error codes 101A3C11 & 101B3C11 from being logged erroneously.
  • Corrects UEPO stuck button problem from being logged erroneously (related to Retain Tip H174927).
  • System will now boot with single RIO cable connected.
  • Improved Error Detection for open link on RIO Port.
  • Shows correct adapter status on HMC after hot plug operation.
  • Adds Mode A/B NVRAM variable values to Open Firmware device tree. 
  • Added support for Memory Books - part numbers: 53P4160, 53P4165, 53P4170, 53P4175, 53P4182, 53P4196, 53P4201, 53P4206, 53P4211, and 53P4218.
RH020724
  • For manufacturing only.
RH020606
  • Improvement for identifying correct processors for L3 directory correctable errors. 
  • Clarified EPOW entry descriptions in AIX diagnostics. 
  • Improved FRU isolation for fan faults.
  • New default Reboot Policy (reboot after a checkstop) - will only take affect if NVRAM is cleared.
  • Fix to deconfigure L3's if associated with memory that is deconfigured.
  • Updated CCIN/FRU Table for MCMs (p670) and Memory Cards (p670 and p690). 
  • Corrected AIX location codes of Media Drawer devices.
  • Fix for detecting critical BPR over temperature condition during boot time.
  • Improved procedure for replacing BPR - during a maintenance procedure, 350V shut off electronically vs. turning slide switch.
RH020513
  • Improvement to FRU isolation in I/O Drawer.
  • Fixed TOD code problem.
RH020425
  • Corrected false Internal Service Processor Processor FW errors.
  • Error code 101100CA (thermal calibration) was changed to informational error.
  • Improved detection of NVRAM low battery warning.
  • Improved Memory Configuation/Deconfiguration Menu to be on one page of vterm.
  • Fixes made to Token-Ring ping test within SMS menu.
  • Fixes made to have PCI adapter vpd not contain VK version keyword.
  • Fixes to show state change of a partition on HMC.
  • Improved initialization of TOD_base.
  • Delay of power/on/off of FC 6203 (Type 4-Y) adapter was altered.
  • Fixes for CEC DCA current balance problem (101C05x1, 101C06x1).
RH020413
  • Added support for Affinity LPAR (ALPAR).
  • Added support for 7040-671.
  • Added support for I/O drawers 7 and 8 for 7040-681 only.
  • Improved error message for L3 resource that has been deconfigured during boot.
  • Corrected FRU call for clock fault during Processor Configuration.
  • Improved error message for L3 undetermined error.
  • Prevent login from S1 port.
Version 1
RH020312
  • Corrected erroneous exit of SP menu when viewing VPD data.
  • Corrected VPD information for BPA.
  • Improved FRU call for L3 timeout. 
RH020307
  • Changed the L3 CE threshold.
  • Enhanced scan log dump to collect critical hardware information first.
  • Improved error recovery on L3 register timeout.
  • Enhanced L3 cache line delete code.
  • Improved error isolation after a UE in memory.
  • IBM Gigabit Fibre Channel Adapter for 64-bit PCI Bus now configures during boot in Partitioned System Mode.
  • Changed PCI hot plug code to enable EEH prior to performing slot reset.
  • Enhanced interrupt handling for IBM Short-wave Serial HIPPI PCI Adapter.
  • Changed memory mapping in Partitioned System Mode.
RH020208
  • System boots up to AIX when Restart/Reboot Policy is set correctly.
  • Improved isolation for MCM parity errors.
  • Enhanced error recover for CEs in L2/L3 directory.
  • Corrected problem with NIM install which resulted in error code 20EE000B.
  • Improved CPU deallocation after CPU error.
  • Corrected reboot problem in SMP mode.
  • Corrected problem that resulted in message 'Stack underflowed' during SMS Multiboot.
RH020121
  • Improved isolation for L3 error.
  • Changed command to BOOT Normal for Partition Timed Power On.
  • Improved error description in diag report for memory error.
  • Corrected invalid error code (B0061406) being logged after slow boot.
  • Service Processor now logs error code 101C6914 in the error log.
  • Reference to HSC change to HMC in the Service Processor Menus.
  • Improved isolation for CPU Cache.
  • Corrected problem with NIM install in Partitioned System mode, resulting in error 20A0005.
  • CPU now deconfigures correctly in Partitioned System Mode.
  • VPD now displays the correct clock frequency for CPU.
RH020115
  • Gathers additional error information after checkstop.
  • Fix for floating point instruction sequence potential error.
RH011222
  • Corrected DRAM clock delay.
RH011214
  • Scan dump option in Service Processor changed to always hw_dump.
  • Corrected problem that causes a system crash resulting in error 406DEA0.
  • Processor error now lists correct AIX resource name in ERRPT.
  • Added callout for L3 UE.
  • Corrected problem resulting in error 406E0EA0.
  • Corrected FRU isolation error for SRN A03-081.
  • Corrected problem that caused IBM PCI Dual Channel Ultra3 SCSI Adapter not to configure during boot.
  • Changed Ambient OT Warning/Critical from >30/36 to  >36/50.
RH011206
  • Original (GA) level.

 

  Table 7.2:  Firmware Levels, File Sizes and Checksums
   Firmware
Distribution Date Filename Size Checksum
Version  3
June 2007 3H070425.img 6411978 01041
December 2006 3H061030.img 6411946 20647 
November 2006 3H060917.img 6411734 52087
August 2006 3H060626.img 6411746 10154 
February 2006 3H060109.img 6411330 16614
December 2005 3H051122.img 6411450 39773
August 2005 3H050715.img 6407918 15143
June 2005 3H050607.img 6408006 61399
April 2005 3H050405.img 6408014 39936
February 2005 3H0504215.img 6405130 02287
November 2004 3H041029.img 6376236 21164
October 2004 3H041021.img 6364968 55799
September 2004 3H040901.img 6366076 15041 
June 2004 3H040602.img 6348656 26970 
June 2004 3H040528.img 6336788 53559
May 2004 3H040503.img 6336796 03418
April 2004  3H040326.img 6334464 23582
March 2004 3H040301.img 6331840 15023
March 2004 3H040214.img 6331936 65239
February 2004 3H040130.img 6330204 51116
January 2004 3H031218.img 6316744 46339
December 2003
3H031118.img
6285000
33543
October 2003 3H031024.img 6280468 56093
This level of firmware is certified compliant
to the Common Criteria (CC), international
standard (ISO/IEC 15408).
3H031021.img 6272448 17750
October 2003 (manufacturing only) 3H031007.img N/A N/A
September 2003 3H030916.img 6271776 65474
September 2003 (manufacturing only) 3H030905.img N/A N/A
August 2003 3H030811.img 6163228 62886
July 2003 3H030703.img 6147012 15302
June 2003 (manufacturing only) 3H030617.img N/A N/A
June 2003 3H030608.img 6146744 09872
May 2003 (manufacturing only) 3H030524.img N/A N/A
April 2003 RH030307.img 5780008  58374
November 2002 RH021114.img 5690572 28302
October 2002 RH021025.img 5686848 59636
Version  2
May 2004 2H040323.img 4483398 57070
March 2004 2H040202.img 4483430 14084
May 2003 2H030325.img 4483274 22549
October 2002 RH021024.img 4483246 47585
September 2002 RH020822.img 4483106 28471
September 2002 (manufacturing only) RH020724.img NA NA
August 2002 RH020606.img 4470286 37854
August 2002 RH020513.img 4440186 37483
May 2002 (manufacturing only) RH020425.img NA NA
April 2002 RH020413.img 4438902 62152
Version 1
April 2002 RH020312.img 4370810 42635
March 2002 RH020307.img 4370610 16762
February 2002 RH020208.img 4370262 07950
January 2002 RH020121.img 4367754 22440
January 2002 RH020115.img 4365050 33568
December 2001 RH011222.img 4362538 05451
December 2001 RH011214.img 4362538 61184
December 2001 RH011206.img 4361370 23299