pSeries 630 Firmware Update

Applies to:  pSeries 630 Model 6C4 (7028-6C4) and Model 6E4 (7028-6E4)

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 630 Model 6C4 (7028-6C4) and Model 6E4 (7028-6E4) Servers only.  Do not use on any other systems.

The firmware level contained in this update is:

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


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
3R080425 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.
3R070425 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.
3R061030 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • A problem 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.
3R060917 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.
3R060626 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.
3R060109 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.
3R051101 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • 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.
  • Firmware was updated to fix intermittent failures of the AIX command "shutdown -t" to power on. 
3R050715 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • Fixes a problem that causes the system to crash when AIX tries a reset on a slot which is already in the reset state. 
  • 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.
  • 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 an I/O adapter.
  • Resolves a problem that prevented the hard reset of a partition from working every time.
  • 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.
3R050405 IMPACT:   Serviceability     SEVERITY:   Special Attention
  • Improved isolation for Remote I/O (RIO) loop failures.
  • Corrects systemTime of Day gains observed after reboot.
3R041029 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).
3R041021 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.
3R040602 IMPACT:   Usability     SEVERITY:  Attention
  • Added dynamic link recovery for Remote I/O loops in single I/O drawer per loop environments.
  • Corrects problem encountered after firmware update via diskettes with error A1FD0001 (entering recovery mode) displayed on the operator panel.
  • Prevents information checkpoints E900 and E901 from being displayed on operater panel during runtime for extended periods.
  • Increased HMC surveillance timeout value to prevent false lost of communication errors.
  • Corrects a condition where on a Primary I/O book with RIO-2 ports (PCI-X) a bit may be erroneously set causing 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).
  • 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 3R040602 (or later) before the image can be restored.
3R040323
  • Added support for AIX 5.3.
  • Added support for new or replacemnt CPU cards manufactured after March 2004.
  • Improved isolation for Remote I/O (RIO) loop failures.
  • Corrects SCAN_ERROR_CHRP error log entries with SRC B0061406 on initial boot after AC power is removed.  Only affects systems with firmware level 3R031021 installed. 
3R031021
  • Corrects cause for system crashes due to a false RIO bus timeout condition.  Only affects systems with level 3R030718 installed.
3R030718 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.
  • Corrects time loss on LPAR systems.
  • Enhanced error detection for RIO link failures.
  • Corrects system attention light blinking after a PCI hot plug operation is completed.
  • Corrects memory DIMM mis-isolation problem on systems equipped with 1.0 and 1.20 GHz Processors.
  • Corrects firmware flash update failure due to recoverable diskette errors when update is performed via Service Processor menus.
  • Corrects drawer ID reassignment for existing drawers when new drawers with duplicate IDs are added.
3R030529
  • Reliability enhancements for adapter recovery during an EEH event.
3R030528 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 RIO-2 Remote I/O Hardware.
  • Resolved incorrect PCI adapter AIX location codes when adapters are added or reassigned via a DLPAR operation. 
  • Corrects time loss problem on LPAR systems.
  • Corrects exposure to potential system crash on LPAR systems when one partition is shutdown and rebooted. 
  • Resolved incorrect identify and power LED behavior during PCI adapter hot plug operations.
  • Corrects configuration problems with IBM 3581 Ultrium Tape Autoloader. 
  • Corrects problems with tape devices not seen in some SMS menu screens. 
  • Corrects slow menu output behavior when SMS is accessed via a graphics display.
  • Added Linux compatibility option to Service Processor Boot Mode menu.
RR030324
  • Enabled configuration support for second 1-way processor card.
RR030219
  • Corrects processor frequency output value displayed with lsattr command.
RR030205
  • Added support for 1.45 GHz Processor cards.
  • Corrects system hang during boot with bad date/time stamp in AIX banner and 'default catch' message displayed on the console.
  • Provides potential performance enhancement for SP Switch2 PCI Attachment Adapters, Feature Code 8397.
  • Changed initialization routines for high performance PCI adapters to allow best use of available bandwidth.
  • Corrects false L3 Cache error and deconfiguration during system initialization.
  • Corrects failure to recognize PCI adapters equipped with PCI-X to PCI-X bridge chips during system boot.
  • Corrects potential cause for system hang with error B1114699 during firmware flash update.
  • Resolves incorrect I/O drawer FRU location codes posted by diagnostics.
  • Prevents logging of false error condition B1xx8FF0 in Service Processor and AIX error logs during firmware flash update.
  • Contains potential minor performance enhancement for PCI adapters internal to the system unit.
  • Corrects problem with tape devices not appearing in the SMS 'Select Boot Options' menu.
  • Corrects behavior where the system will automatically boot from tape device when SMS 'List All Devices' option is chosen.
  • Corrects truncation of FRU location codes in SMS error log.
  • Corrects potential cause for system hang during boot at checkpoint EAA1 and/or error code 26020010.
  • Corrects configuration problem during hot-plug operation for IBM Long-Wave Serial HIPPI PCI Adapter, Feature Code 2733.
  • Corrects ping and NIM boot failures with error 20A80001 on IBM 10/100MBps Ethernet PCI Adapter II, Type A-F, Feature Code 4962.
  • Corrects potential cause for system hang during boot at checkpoint 91FF.
RR021114
  • Added support for IBM 7311 Rack-Mounted High-Density Expansion Drawer Model D20.
  • Added support for Dynamic Logical Partitioning (DLPAR).
  • Added support for the performance correction on a variety of High Performance PCI adapters.
  • Corrected potential cause for system hang with errors 4B2E26FB, 4B2E26FD or 40640EAF during firmware flash update.
RR021024
  • Corrects potential L3 cache data recovery error. 
RR020927
  • Corrected system name not being updated in SP menu after set via HMC.
  • Enhanced error isolation for error 40670EA1.
  • Corrected system hang condition during dynamic CPU deallocation (CPUgard)
  • Corrected potential EEH data error.
RR020822
  • Correction for Green/Amber slot ID/Power lights not being turned on when using the PCI Hot Plugging Management function.
  • Correction for the System Bus Frequency field showing 0 (zero) instead of 333000000 in a output display of lsattr -El sys0 command.
  • Correction for Extended I/O Error Handling Option not properly resetting the PCI slot after a PCI Bus Error.
  • Eliminated the extraneous messages appearing when exiting SMS menu.
  • Corrected the SMS menu(s) condition under which pressing 1 multiple times (in order to get to SMS) would result in arriving at the next menu screen.
  • Correction for page 1 of SMS being truncated upon pressing an invalid key on that page.
  • Corrected the SMS console select option which resulted in the system booting instead of returning to SMS. 
  • Eliminated the double digit code appearing next to E1EB firmware progress code both in SMP and LPAR mode.
  • Corrected the changes in AIX location codes under PCI Hot Plugging remove/add option. This error would occur on all PCI Adapters containing bridges. 
  • Corrected the next page navigation footer in the SMS menus that was being displayed when there was no second page.
  • Corrected the condition under which generating "aliases" for integrated and slot devices may cause excessive boot time (especially on systems containing a large number of LAN and SCSI adapters). 
  • Corrected condition under which the system could not find a device to boot from, which results in the 20EE 000B error code.
  • Corrected a firmware condition that may result in the system hanging. 
  • Corrected the problem that caused AIX to record firmware informational errors as PERM type in the AIX error log.
  • Corrected the incorrect FRU callouts. 
  • Corrected the Service Processor firmware so that extraneous error log entries (error codes 4006 00B7, 4006 00B4, or B101 4669) after a temporary AC power outage are no longer logged. These error codes also appeared on the Operator Panel preceded by SPCN 1011 00AC error code.
RR020723
  • Original (GA) level.


3.0 Cautions and Important Notes

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.

Before Beginning the Update

Go to http://www14.software.ibm.com/webapp/set2/firmware/gjsn?mode=10&page=compare.html to determine if the tools can assist you with this update.

NOTE:  If your firmware level is RR021024 or earlier,  you must use the instructions in this document to update your firmware manually.

Before installing this level of firmware, AIX 5.1.0 should be updated to Maintenance Level 3 (APAR IY32749).

 Before installing this level of firmware, ensure the Hardware Management Console (HMC) code on all HMC systems is Release 3, Version 1.2 or later.

Updating the firmware may result in the HMC going into 'Recovery' state.  Before updating the firmware, make sure the backup of Profile Data is complete (if running LPAR).

Native Linux Systems

To update firmware on a Linux system, 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.

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 pSeries 630 Service Guide.

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.

Replacement Parts May Require Updating

When a CEC backplane 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
May 2008 3R080425.img 5100471 41435
June 2007 3R070425.img 5100447 47728
December 2006 3R061030.img 5100415 62255
November 2006 3R060917.img 5100203 24343 
August 2006 3R060626.img 5100215 03845
February 2006 3R060109.img 509979 44215
December 2005 3R051101.img 5099903  41125 
August 2005 3R050715.img 5096151 07826
April 2005 3R050405.img 5096263 61220
November 2004 3R041029.img 5088499 18284
October 2004 3R041021.img 5077231 13872
June 2004 3R040602.img 5064099 39743
April 2004 3R040323.img 5048379 28013
December 2003 3R031021.img 5023923 30735
August 2003 3R030718.img  4952939 12129
June 2003 3R030529.img 4919371 27817
June 2003 (manufacturing only) 3R030528.img n/a n/a
April 2003 RR030324.img 4671019 20264
March 2003 RR030219.img 4670987 28812
February 2003 RR030205.img 4670883 32990
December 2002 RR021114.img 4651979 54970
October 2002 RR021024.img 4237035 24358
October 2002 RR020927.img 4236959 34516
September 2002 RR020822.img 4235343 13252
August 2002 RR020723.img 4256731 47308


4.0 How to Determine Currently Installed Firmware Level

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

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).......3R061030
          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 3R061030.

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

4.2 Using the Service Processor Main Menu

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

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

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

If the right-most six characters (date) of the current firmware level are earlier than 080425, 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, DOS and RPM packages, along with severity and impact information, is located at the web site

         http://www14.software.ibm.com/webapp/set2/firmware/gjsn

Follow the instructions on this web page.

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.

      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 70286C4F.BIN

  c) Unpack the file by executing the instructions below.

     Enter the commands:

        cd /tmp/fwupdate
        chmod +x 70286C4F.BIN
        ./70286C4F.BIN

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

 This file will be added to  /tmp/fwupdate:

      3R080425.img

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

Otherwise, from 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 3R080425.img
     quit

Proceed to Section 6.0, Updating the Firmware.

5.1.1.2 The Diskette Transfer Method

This method presumes a diskette drive is installed on the target server.

 Four 2MB (HD) new  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:  Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

     "Volume 2:  Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

     "Volume 3:  Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

     "Volume 4:  Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

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 70286C4F.EXE

  c) Unpack the file by executing the instructions below.

      Enter the commands:

        cd [path]\fwupdate
        70286C4F

These files will be added to the fwupdate subdirectory:

       3R080425.img
       286C4_B1.EXE
       286C4_B2.EXE
       286C4_B3.EXE
       286C4_B4.EXE

5.1.2.1 The FTP Transfer Method

This method presumes you have ftp access to the target server.

On the Windows workstation,

   Enter the commands:

      ftp {name of target server}
     {Login with a valid userid and password}

     bin
     lcd [path]\fwupdate
     mkdir /tmp/fwupdate
     cd /tmp/fwupdate
     put 3R080425.img
    quit

Proceed to Section 6.0, Updating the Firmware.

5.1.2.2 Diskettes for Firmware Updates

This method presumes a diskette drive is installed on the target server.

Four 2MB (HD) new 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
            286C4_B1

      Label this diskette,

           "Volume 1: Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

  b) With a second diskette loaded in the drive,

         Enter:
             286C4_B2

     Label this diskette,

           "Volume 2: Firmware (3R080425) for 7028-6C4"

  c) With a third diskette loaded in the drive,

         Enter:
             286C4_B3

     Label this diskette,

           "Volume 3: Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

  c) With a fourth diskette loaded in the drive,

         Enter:
             286C4_B4

     Label this diskette,

           "Volume 4: Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

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

  c) Unpack the file by executing the instructions below.

     Enter the commands:

        rpm -ihv --ignoreos 3R080425.rpm

The 3R080425.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, 3R080425.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.

Once the System and Service Processor firmware had been updated, the server will reboot. The System Power Control Network (SPCN) update will continue to run in the background.

***
WARNING:

Do not  power off the server at any time before the update process completes.  Be sure the system is NOT running any user applications when you begin the update process.
***

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

        At the AIX command line, enter:
           sum 3R080425.img

         The output will look like this ----->  41435  4981  3R080425.img
         The checksum is ------------->  41435

6.1 Full System Partition

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

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

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

    a. Shutdown the server from the HMC virtual terminal window or ASCII terminal window.

    b. When the operator panel on the server says OK,
           If using an ASCII terminal  - Press Enter
           If using an HMC terminal - close the current terminal window and open a new terminal window.

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

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

    e. Type y to continue.  <Enter>

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

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

          The target server will reboot.  This may take up to thirty minutes, depending on the configuration
          of the target server.  Since the update occurs during this shutdown/reboot sequence, it is
           important to protect the server from interruptions.

    h. Begin watching the operator panel.

    i.  When the panel says 'OK',
           If using an ASCII terminal  - Press Enter
           If using an HMC terminal - close the current terminal window and open a new terminal window.

          The Service Processor Menu appears on the screen.

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

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

NOTE:  If you are running Native Linux,
 - choose 2 System Power Control Menu
- choose 7 Boot Mode Menu
- Enable the Linux compatibility mode by choosing 1 (if currently disabled).

The firmware update is complete.

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

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

6.1.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: Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

    When prompted for volume 2,

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

          "Volume 2: Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

     When prompted for volume 3,

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

          "Volume 3: Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

     When prompted for volume 4,

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

          "Volume 4: Firmware (3R080425) for pSeries 630 (7028-6C4) and (7028-6E4)"

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

6.1.2.2 Updating With Files Already Loaded in the Target Server

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

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

     Enter the commands:

        cd /usr/lpp/diagnostics/bin
        ./update_flash -f /tmp/fwupdate/3R080425.img

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

You will be asked for confirmation to proceed with the firmware update and the required reboot.  If you confirm, the server automatically performs the update and reboots.   The checkpoints 99FF and 99FD alternately appear while the update is in progress. This may take up to thirty minutes, depending on the configuration of the server.  Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.

NOTE:  If using an HMC terminal you will need to close the existing terminal window and open a new terminal window when the Operator Panel goes blank.

ATTENTION:  You may get error codes 4B2E26FB, 4B2E26FD or 40640EAF depending on the type of processor card(s) installed in the system.  You will be in the Service Processor Main Menu.  To continue the firmware update process:
  1) Press the white button on the operator panel.
  2) Within a minute, the operator panel will display 9022.
  3) Press the white button again.
  4) Within a minute, the operator panel will display OK.
  5) The second line of the title on the Service Processor Menu will match the firmware level you just
        installed.

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

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

This method allows updating from files already loaded onto the target server.

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

     Enter the commands:

         cd /tmp/fwupdate
        /usr/sbin/update_flash -f  3R080425.img

The server automatically performs the update and reboots.  The checkpoints 99FF and 99FD alternately appear while the update is in progress. This may take up to thirty minutes, depending on the configuration of the server.  Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.

NOTE:  If using an HMC terminal you will need to close the existing terminal window and open a new terminal window when the first line on the Operator Panel shows Linux ppc64.

ATTENTION:  You may get error codes 4B2E26FB, 4B2E26FD or 40640EAF depending on the type of processor card(s) installed in the system.  You will be in the Service Processor Main Menu.  To continue the firmware update process:
  1) Press the white button on the operator panel.
  2) Within a minute,  the operator panel will display 9022.
  3) Press the white button again.
  4) Within a minute,  the operator panel will display OK.
  5) The second line of the title on the Service Processor Menu will match the firmware level you just
       installed.

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

6.2  Partitioned System

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

6.2.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 diskettes only.

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

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

    a. Shutdown the server from the HMC virtual terminal window or  the ASCII terminal.

    b. When the operator panel on the server says OK,
           If using an ASCII terminal  - Press Enter
           If using an HMC terminal - close the current terminal window and open a new terminal window.

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

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

    e. Type y to continue. <Enter>

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

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

          The target server will reboot.  This may take up to thirty minutes, depending on the configuration
          of the target server.  Since the update occurs during this shutdown/reboot sequence, it is
           important to protect the server from interruptions.

    h. Begin watching the operator panel.

    i.  When the panel says 'OK',
           If using an ASCII terminal  - Press Enter
           If using an HMC terminal - close the current terminal window and open a new terminal window.

          The Service Processor Menu appears on the screen.

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

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

NOTE:  If you are running Native Linux,
 - choose 2 System Power Control Menu
- choose 7 Boot Mode Menu
- Enable the Linux compatibility mode by choosing 1 (if currently disabled).

 Power on the system.  If the HMC goes into Recovery state, skipto paragraph 6.3 HMC Restore Functions to complete the procedure.  Otherwise, the firmware update is complete.

6.2.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 into the target server or from diskettes.

6.2.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: Firmware (3R080425) for 7028-6C4 and 7028-6E4"

    When prompted for volume 2,

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

          "Volume 2: Firmware (3R080425) for 7028-6C4 and 7028-6E4"

     When prompted for volume 3,

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

          "Volume 3: Firmware (3R080425) for 7028-6C4 and 7028-6E4"

     When prompted for volume 4,

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

          "Volume 4: Firmware (3R080425) for 7028-6C4 and 7028-6E4"

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

6.2.2.2 Updating With Files Already Loaded in 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/3R080425.img

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

You will be asked for confirmation to proceed with the firmware update and the required reboot.  If you confirm, the server automatically performs the update and reboots.   The checkpoints 99FF and 99FD alternately appear while the update is in progress. This may take up to thirty minutes, depending on the configuration of the server.  Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.

NOTE:  If using an HMC terminal you will need to close the existing terminal window and open a new terminal window and open a new terminal window when the Operator Panel shows LPAR.

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

 If the HMC goes into Recovery state, skip to paragraph 6.3 HMC Restore Functions to complete the procedure.  Otherwise, the update of the firmware is complete. You will want to verify the update as shown in paragraph 6.4.

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

This method allows updating from files already loaded onto the target server.

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

     Enter the commands:

         cd /tmp/fwupdate
        /usr/sbin/update_flash -f  3R080425.img

The server automatically performs the update and reboots.  The checkpoints 99FF and 99FD alternately appear while the update is in progress. This may take up to thirty minutes, depending on the configuration of the server.  Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.

NOTE:  If using an HMC terminal you will need to close the existing terminal window and open a new terminal window and open a new terminal window when the Operator Panel shows LPAR.

 If the HMC goes into Recovery state, skip to paragraph 6.3 HMC Restore Functions to complete the procedure.  Otherwise, the update of the firmware is complete. You will want to verify the update as shown in paragraph 6.4.

6.3 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 state changes to READY and the system Status and operator panel will say LPAR.

You will want to verify this update as shown in paragraph 6.4.

6.4 Verifying the Update

To verify the update was successful, the firmware level can be check in AIX, Linux or in the Service Processor Main Menu.

6.4.1 Using AIX

Use the following AIX command for checking the firmware level.

         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).......3R080425
        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, 3R080425.

6.4.2 Using the Service Processor Main Menu

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

6.4.3 Using Linux

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

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