7025-F80, 7025-6F0 and 7025-6F1 Firmware Update

Applies to :  RS/6000 7025-F80,  pSeries 620 Models 6F0 and 6F1

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 firmware (FW) for RS/6000 7025-F80 and  pSeries 620 Model 6F0 (7025-6F0) and Model 6F1 (7025-6F1) Servers only.  Do not use on any other systems.

The firmware level contained in this update is:

The typical time to install this firmware is one hour. The firmware does not become active when  installed and requires a system reboot to become active. This 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 the firmware.
 
Table 2.1:  Firmware Update Descriptions and History
CL060505
  • A problem was fixed that was causing the time-of-day clock in the service processor to adjust for daylight savings time, even though daylight savings time was disabled.
  • A problem was fixed that caused the system to hang during boot if more than five boot devices had been put into the boot list by the operating system.
  • The address request protocol (ARP) function was enhanced to support broadcast ARPs in the TC/IP layer.
CL050203
  • Added support for network boot when target server provides preferred gateway information in bootp reply.
  • Enabled Enhanced Error Handling recovery (EEH)  for IBM Universal 4-Port 10/100 Ethernet Adapter (FC4961).
CL040712
  • Added support for AIX 5.3.
CL040119
  • Resolves intermittent diskette drive initialization failure during system boot (symptom: Diskette drive is inoperable).
  • Resolves duplicate/incorrect Vital Product Data displayed for system backplane on systems equipped with 1-way processor cards.
  • Resolves truncated Vital Product Data displayed for CPU card.
CL030829
  • Added support for IBM 2-Port 10/100/1000 Base-TX Ethernet PCI-X Adapter (FC 5706) and IBM 2-Port Gigabit Ethernet-SX PCI-X Adapter (FC 5707).
  • 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 SMS network adapter menus to resolve various configuration issues and ping test failures.
  • Corrected 'Default Catch' message displayed on console after SMS 'Change SCSI ID' utility screen is accessed.
CL021213
  • Corrected truncation of FRU location code in SMS error log.
  • Corrected error 20EE000B: unable to find boot record after restore or NIM install on 36GB or larger disks.
  • Corrected problem with bypassing initial SMS menu when accessed via GUI interface.
  • Enhancements to prevent potential ping and NIM boot failures on SP and Cluster attached servers.
CL020916
  • Added base support for PCI-X type adapters. 
  • Added support for IBM Gigabit Ethernet SX and TX PCI-X adapters, Feature Codes 5700 & 5701.
  • Added support for IBM PCI-X Dual Channel Ultra320 SCSI adapter, Feature Code 5702. 
CL020807
  • Corrected problem with failing Ping tests across gateways.
  • Added Universal Data Format support for CDROM and DVD drives.
  • Corrected error 20EE000B: unable to find boot record on some disk drive types when attached to PCI Dual Channel Ultra3 SCSI adapter Feature Code 6203, Type 4-Y. 
  • Improved FRU isolation for PCI Bus Machine Check errors.
CL020617
  • Corrected Operator Panel thermal sensor read failures not being reported.
  • Corrected one known cause for B0061406 error during boot.
CL020422
  • Corrected slot limitation for POWER GXT135P Graphics Accelerator, Type 1-X, Feature Code 2848. 
  • Corrected SMS password not being accepted if greater than 7 characters.
  • Corrected NIM boot problem when  non-TFTP packets are received.
  • Resolved incorrect/missing system Vital Product Data location codes.
  • Corrected potential boot hang at error 91FF after clearing NVRAM.
CL020407
  • Added support for IBM Universal 4-Port 10/100 Ethernet Adapter, Type A-E, Feature Code 4961.
  • Added support for 750MHz processors.
  • Corrected problem with 36hr time/date change after some reboots.
  • Corrected Memory DIMM pairs on 1 way CPU cards not displayed properly in Service Processor menus.
  • Corrected hot plug behavior on  POWER GXT135P Graphics Accelerator, Type 1-X, Feature Code 2848.
  • Corrected missing devices in SMS bootlist when bootlist set via AIX.
  • Corrected problem with failing Ping tests across gateways.
  • Added Universal Data Format support for CDROM and DVD drives.
  • Improved Fault Isolation for PCI bus address/data parity error. 
CL011206
  • Resolved incorrect behavior of SMS multiboot menu.
CL011004
  • Added support for IBM Gigabit Fibre Channel Adapter for PCI Bus, Type 4-S, Feature Code 6227.
  • Added support for IBM Gigabit Fibre Channel Adapter for 64-bit PCI Bus, Type 4-W, Feature Code 6228.
  • Removed check for PCI vendor and device id to comply with PCI device specification. Will correct some causes for error codes 26020001 and 26020002.
  • Corrected hotplug behavior on IBM Universal 4-Port 10/100 Ethernet Adapter, Type A-E, Feature Code 4961.
  • Corrected problem with 600 & 668 Mhz processor Vital Product Data  incorrectly displayed as RS64-III.
  • Corrected missing lun id from Fibre Channel device in SMS Multiboot menu.

  • Corrected false "No Operating systems installed" message SMS Multiboot > Select Software menu. 
CL010808
  • Added NIM Pull speed and mode support for IBM 10/100 Ethernet PCI Adapter II, Type A-F, Feature Code 4962.
  • Allow NIM Push on all supported Network Adapters.
  • Corrected failure to report cooling/fan faults.
CL010507
  • Added support for Model 7025-6F0.
  • Corrected 1GB DIMM support on 1-way processor card.
  • Corrected support for the IBM Fiber 1000 Base SX Ethernet PCI Adapter, Type 9-U, Feature Code 2969.
  • Corrected intermittent boot time hang with the IBM 2-Port Multiprotocol PCI Adapter, Type 9-V, Feature Code 2962.
  • Improved fault isolation for PCI bus address/data parity error.
CL010321
  • Added support for Model 7025-6F1.
  • Added 1GB DIMM support. 
  • Added support for IBM PCI Dual Channel Ultra-3 SCSI Adapter, Type 4-Y, Feature Code 6203. 
  • Added support for hardware multithreading. 
  • Disabled monitoring of serial port 3 by Service Processor.
  • Corrected SMS SCSI utility menus to display all supported SCSI adapters.
  • Corrected hotplug behavior on IBM Dual Channel Ultra2 SCSI Adapter, Type 4-R, Feature Code 6205.
  • Corrected problem with Memory DIMM Vital Product Data incorrectly displayed or missing.
  • Corrected NIM boot problem with IBM 10/100/1000 Base -T Ethernet Adapter, Type A-A, Feature Code 2975.
  • Corrected problem with processor speed displayed incorrectly with lsattr command.
CL001108
  • Corrected problem with booting to SMS open firmware prompt when Multiboot Startup is enabled. 
  • Corrected power supply hotplug problem.
CL000628
  • Added support for the IBM 10/100/1000 Base-T Ethernet PCI Adapter, Type A-A, Feature Code 2975.
  • Added reporting of System Power Control Network open cable loop cable condition.
  • Added serial port snoop function to allow remote system reset 
  • Improved fault data capture. 
CL000516
  • Original (GA) level.


3.0 Cautions and Important Notes

ATTENTION:  The firmware levels contained in this package MUST be installed before installing AIX 5.3.

The System, Service Processor (SvP) and System Power Control Network (SPCN) firmware are combined into a single file. This allows all the firmware to be updated together and assures they are compatible.

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.

Service Processor Menu Update Method

This method of updating the firmware requires the update file to be on diskettes.   Details for creating these diskettes are contained in the download instructions.

Note:  If the update file will be downloaded directly to the target server,  diskettes will have to be made in order to update the firmware from the SP Menus.

Recovery Mode

If the service processor detects that its programming has been corrupted when it is powering up to  standby mode, it will enter recovery mode.   In recovery mode, it will ask for the firmware update diskettes by putting eight-digit codes on the operator panel.  For more details, see the RS/6000 Enterprise Server 7025 Model F80, eServer pSeries 620 Models 6F0 and 6F1 Service Guide.

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.

Replacement Parts May Require Updating

When a system planar is replaced, the firmware must be checked to ensure it is at the latest level. Table 3.1 lists the released levels.
 
Table 3.1: Firmware Levels, File Sizes and Checksums
   Firmware
Distribution Date Filename Size Checksum
June 2006 CL060505.img 3293246 52328
April 2005 CL050203.img 3293246 62266
August 2004 CL040712.img 3291758 43618
March 2004 CL040119.img 3248898 36206
September 2003 CL030829.img 3247826 52716
February 2003 CL021213.img 3246646 27681
November 2002 CL020916.img 3248494 11111
August 2002 CL020807.img 3248110 55401
June 2002 CL020617.img 3244686 32809
May 2002 CL020422.img 3243714 32709
April 2002 CL020407.img 3241238 41764
December 2001 CL011206.img 3232790 56006
November 2001 CL011004.img 3232790 36254
September 2001 CL010808.img 3234578 52213
May 2001 CL010507.img 3226826 51114
April  2001 CL010321.img 3220790 33465
November 2000 CL001108.img 2634727 52744
July 2000 CL000628.img 2600251 09426
June 2000 CL000516.img 2584111 38085

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

Firmware level identifiers for the firmware use the 8-digit Gregorian date code method in terms of year, month, and day (such as 20060505 for CL060505 level).

4.0 How to Determine Currently Installed Firmware Level

DO NOT rely on the part number or firmware level marking/label on an 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.

Use the following AIX command for checking the firmware level.

   Enter:
      lscfg -vp | grep -F .CL

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

  ROM Level.(alterable).......CL040712
The ROM Level line lists the level of the currently installed firmware. In the above example, the current firmware level  is CL040712.

If the right-most six characters (date) of firmware level is earlier than 060505, 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.


5.0 Downloading and Unpacking the Firmware Update Package

Instructions for downloading and unpacking the firmware update package follow.

5.1 Internet Package

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

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.

Note: In the instructions that follow are specific AIX commands.
           AIX commands are CASE (lower and upper) SENSITIVE, and must
           be entered exactly as shown, including the filenames.

  a) Provide a directory on an AIX system to receive the AIX format file.

      Enter:
        mkdir /tmp/fwupdate

        Note:  If the directory /tmp/fwupdate already exists,
                    make sure it is empty before proceeding.

  b) Transfer the AIX package to the /tmp/fwupdate directory (using "Save as ...").
       You'll see that the filename is 7025F80F.BIN

  c) Unpack the file by executing the instructions below.

     Enter the commands:

        cd /tmp/fwupdate
        chmod +x 7025F80F.BIN
        ./7025F80F.BIN

     [Don't overlook the periods (.) in the above command.]

 This file will be added to  /tmp/fwupdate:

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

 On the intermediate AIX system, proceed as follows. Three 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:  FW (CL060505) for 7025-F80, 7025-6F0 and 7025-6F1"

     "Volume 2:  FW (CL060505) for 7025-F80, 7025-6F0 and 7025-6F1"

     "Volume 3:  FW (CL060505) for 7025-F80, 7025-6F0 and 7025-6F1"

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.
      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 7025F80F.EXE

  c) Unpack the file by executing the instructions below.

      Enter the commands:

        cd [path]\fwupdate
        7025F80F

These files will be added to the fwupdate subdirectory:

       25F80_B1.EXE
       25F80_B2.EXE
       25F80_B3.EXE

5.1.2.1 Diskettes for Firmware Updates

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

  Note: The diskettes produced below will be in a format that can be used
             directly with a computer running AIX as it's operating system. These
             diskettes, once made on a PC platform, cannot be read using normal PC
             platform tools or command line operations.

  a) With a diskette loaded in the drive,

         Enter the commands:

            cd [path]\fwupdate
            25F80_B1

      Label this diskette,

           "Volume 1: FW (CL060505) for 7025-F80, 7025-6F0 and 7025-6F1"

  b) With a second diskette loaded in the drive,

         Enter:
             25F80_B2

     Label this diskette,

           "Volume 2: FW (CL060505) for 7025-F80, 7025-6F0 and 7025-6F1"

  c) With a third diskette loaded in the drive,

         Enter:
             25F80_B3

     Label this diskette,

           "Volume 3: FW (CL060505) for 7025-F80, 7025-6F0 and 7025-6F1"

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, CL060505.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) and System Power Control Network (SPCN) firmware are combined into a single file. This allows all the firmware to be updated together and assures they are compatible.

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

Note: Checksums can be used to verify files have not been corrupted or altered during transmission.

            At the AIX command line, enter:

              sum  CL060505.img

This command will produce the following output:

                 52328  3217 CL060505.img

         The checksum is ----> 52328

You must have root authority on the target server to update its firmware.

As the firmware update takes place (during the automatic shutdown sequence), progress can be monitored from the operator panel. The checkpoints 99FF and 99FD alternately appear while the update is in progress.

At some points in the update process, these checkpoints may not change for ten to thirty minutes. If this occurs, be patient and allow time for the update process to complete.

Updating firmware must be initiated either directly from the AIX command line, from the Update Flash Diagnostic Service Aid, or from the Service Processor Menu.

 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

This method allows updating either from files already loaded into the target server or from diskettes.

6.1.1 Updating With Files Already Loaded in the Target Server

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

     Enter the commands:

        cd /usr/lpp/diagnostics/bin
        ./update_flash -f /tmp/fwupdate/CL060505.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 will apply the new firmware, reboot and return to the AIX prompt. This may take ten to thirty minutes (or more), depending on the configuration of the target server.

Having successfully executed the above commands, the server automatically performs the update and reboots.  Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.  The checkpoints 99FF and 99FD alternately appear while the update is in progress.

The update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.

6.1.2 Updating from 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: FW (CL060505) for 7025-F80, 7025-6F0 and 7025-6F1"

    When prompted for volume 2,

     In the drive of the target server, put the AIX backup diskette labeled:

          "Volume 2: (CL060505) FW for 7025-F80, 7025-6F0 and 7025-6F1"

     When prompted for volume 3,

     In the drive of the target server, put the AIX backup diskette labeled:

          "Volume 3: (CL060505) FW for 7025-F80, 7025-6F0 and 7025-6F1"

The file is now located in the /tmp/fwupdate subdirectory.

       Enter the commands:

           cd /usr/lpp/diagnostics/bin
          ./update_flash -f /tmp/fwupdate/CL060505.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 will apply the new firmware, reboot and return to the AIX prompt. This may take ten to thirty minutes (or more), depending on the configuration of the target server.

Having successfully executed the above commands, the server automatically performs the update and reboots.  Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions. The checkpoints 99FF and 99FD alternately appear while the update is in progress.

Don't forget to retrieve and file any firmware update diskette that may still be in the server's diskette drive. A good time to do this is after the reboot has completed.

The update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.

6.2 Using the Update Flash Diagnostic Service Aid Method

This method allows updating from files already loaded into the target server or from diskettes.

Note: Review "Update System or Service Processor Flash" in the Service Aids
section of the RS/6000 Enterprise Server 7025 Model F80, eServer pSeries 620
Models 6F0 and 6F1, User's Guide for more information about using this utility.

6.2.1 File on 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: FW (CL060505) for 7025-F80, 7025-6F0 and 7025-6F1"

When prompted for volume 2,

In the drive of the target server, put the AIX backup diskette labeled:

    "Volume 2: FW (CL060505) for 7025-F80, 7025-6F0 and 7025-6F1"

When prompted for volume 3,

In the drive of the target server, put the AIX backup diskette labeled:

    "Volume 3: FW (CL060505) for 7025-F80, 7025-6F0 and 7025-6F1"
 

The file is now located in the /tmp/fwupdate subdirectory. Continue to paragraph 6.2.2.

6.2.2 Updating with the Diagnostics Service Aid

  a) Invoke the Service Aids from either on-line or standalone diagnostics.

  b) Choose Update System or Service Processor Flash.

  c) Select 'File System' as the source of the flash update image file.

      The fully qualified path name of the update file is /tmp/fwupdate /CL060505.img

  d) Press 'F7' key to 'Commit' the update.

The server automatically performs the update and reboots.  Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.   The checkpoints 99FF and 99FD alternately appear while the update is in progress.

Don't forget to retrieve and file any firmware update diskette that may still be in the server's diskette drive. A good time to do this is after the reboot has completed.

The update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.

6.3  Using the Service Processor Menu Method

This method allows updating from diskettes only.

Note:   All  firmware (System, Service Processor and SPCN) will be updated when using this method.

Note:  Access to the Service Processor Menus is not available on serial port (S4).

    a. Power on or shutdown and restart the system.

    b. When the operator panel on the server says OK,  press Enter, to bring up the Service Processor
         Menu.

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

    d. Choose 7 for Reprogram Flash EPROM Menu.  <Enter>

    e. Type y to continue.  <Enter>

    f. Follow on-screen update steps as they are presented.

    g.  The 'Rebooting Service Processor ' message appears on the screen.

    h. Begin watching the operator panel.

    i.   When the panel says 'OK',  Press Enter.

          The Service Processor Menu appears on the screen.

         The second line of the title, Version: CL060505, should match the firmware level you just
          installed.

    j.  To restart AIX,  choose 2 for System Power Control Menu.  <Enter>

    k.  Choose 4 for Power-On System.  <Enter>

   l.  Type y to confirm.  <Enter>

If you confirm, the server will reboot and return to the AIX prompt. This may take ten to thirty minutes (or more), 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.  The checkpoints 99FF and 99FD alternately appear while the update is in progress.

Don't forget to retrieve and file any firmware update diskette that may still be in the system's diskette drive.  A good time to do this is after the reboot has completed.

The firmware update is complete. You will want to verify this update as shown in paragraph 6.4.

6.4 Verifying the Update

To verify the update was successful,  use the following AIX command after the automatic reboot.

     Enter:
        lscfg -vp | grep  -F .CL

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

        ROM Level.(alterable).......CL060505
The ROM Level line should match the level you just installed, namely, CL060505.
 

6.5 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