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 (7040-6E4) Servers only.  Do not use on any other systems.

The firmware level contained in this update is:

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.

To obtain the firmware that meets the requirements of the Common Criteria on secure delivery,  follow the link in the Contents section of download.html.

Use your web browser to check that the security information (server certificate) is valid.  To do this, click on the lock icon on the bottom bar of the web browser window.

To configure the certified firmware,  you must follow the instructions in the "Evaluation Assurance Level 4+" chapter of the Hardware Management Console for pSeries Installation and Service Guide.

NOTE:  See Section 3.0 Cautions and Important Notes for information on the new firmware level
                 name.

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

                 AIX support and the APAR listed above can be obtained at the following web site:

                 http://techsupport.services.ibm.com/server/support?view=pSeries
 

 NOTE:   This server can only be attached to an HMC that is running Release 3, Version 1.2 or higher.


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
3R031021 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.
  • 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

NOTE:   This server can only be attached to an HMC that is running  Release 3, Version 1.2 or higher.

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.

New Firmware Name

The name of the firmware has been changed. The new name replaces the first letter R with the number 3 (example 3Ryymmdd instead of RRyymmdd).

Service Processor Menus 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 Service Processor 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 pSeries 630 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 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
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

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.

Native Linux Systems

To update firmware on a native Linux system, you must use the Service Processor Menus method.  This method requires diskettes.  See Section 5.0.

How to Determine the Firmware Release Date

Level identifiers for the firmware use the 8-digit Gregorian date code method in terms of year, month, and day (such as 20031021 for 3R031021 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.

The firmware level can be checked in AIX 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).......RR030529
          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 RR030529.

If the right-most six characters (date) of the current firmware level are earlier than 031021,  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: RR030529 shows the currently installed firmware level.

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

Note:  To update firmware on a native Linux system, you must use the Service Processor Menus method.  This method requires diskettes.  Choose the correct download format for your environment.
 

5.1 Internet Package

The firmware, in AIX, RPM and DOS packages, is located at the web site

   https://www14.software.ibm.com/webapp/set2/firmware/gjsn?mode=10&page=isoiec.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.

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

      3R031021.img

If you used the above procedure 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 3R031021.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 (3R031021) for pSeries 630 (7028-6C4) and (7028-6E4)"

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

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

     "Volume 4:  Firmware (3R031021) 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:

       3R031021.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 3R031021.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 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
            286C4_B1

      Label this diskette,

           "Volume 1: Firmware (3R031021) 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 (3R031021) for 7028-6C4"

  c) With a third diskette loaded in the drive,

         Enter:
             286C4_B3

     Label this diskette,

           "Volume 3: Firmware (3R031021) 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 (3R031021) 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.

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

  c) Unpack the file by executing the instructions below.

     Enter the commands:

        rpm -ihv --ignoreos 3R031021.rpm

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

The file size and checksum will be verified and any operating system prerequisites will be checked for.  If any prerequisites are missing, refer to Section 3.0.

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


6.0 Updating the Firmware

NOTE:   For updating the firmware for a Common Criteria configured system,  you must use the Service Processor Menus method (Section 6.1.1).  For further information seethe "Evaluation Assurance Level 4+" chapter of the Hardware Management Console for pSeries Installation and Service Guide.

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.

NOTE:   This server can only be attached to an HMC that is running  Release 3, Version 1.2 or higher.

NOTE:  To update firmware on a native Linux system, you must use the Service Processor Menus method.

NOTE:  Updating the firmware may result in the HMC going into 'Recovery' state.   Before updating the firmware,  make sure an HMC Recovery CD is available,  the backup of Profile Data is complete (if running LPAR), and the backup of Critical Console Data to DVD is complete.  Make sure the 'write protect' tab is not set to write protect (there is no failure message if the write protect is enabled,  however no data is backed up).

***
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 3R031021.img

         The output will look like this -----> 30735  4907    3R031021.img
         The checksum is -----> 30735

6.1 Full System Partition

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

6.1.1  Using the Service Processor Menus Method

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 ASCII terminal window.

    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.

          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: 3R031021, 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.

The firmware update is complete.

6.1.2 Using the Service Aids Method

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

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.

Note: Review "Update System or Service Processor Flash" in the Service Aids
section of the eserver pSeries 630 User's Guide for more information about using this utility.

6.1.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: Firmware (3R031021) 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 (3R031021) 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 (3R031021) 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 (3R031021) 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 the Diagnostics Service Aids

  a) Invoke the Service Aids from on-line 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/3R031021.img

  d) If using an ASCII terminal press 'F7' key to 'Commit' the update.
       If using an HMC terminal  press 'ESC' + '7' keys to 'Commit' the update.

   e) Choose Yes to continue.

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.

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.1.3 Using the AIX Command-Line Method

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

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.

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

6.1.3.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 (3R031021) 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 (3R031021) 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 (3R031021) 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 (3R031021) for pSeries 630 (7028-6C4) and (7028-6E4)"

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

6.1.3.2 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/3R031021.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.2  Partitioned System

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

6.2.1  Using the Service Processor Menus Method

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

          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: 3R031021, 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.  Power on the system and then continue to paragraph 6.3 HMC Restore Functions to complete the procedure.
 

6.2.2 Using the Update System or Service Processor Flash Diagnostic Service Aids Method

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.

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.

Note:  Review "Update System or Service Processor Flash" in the Service Aids section
            of the eserver pSeries 690 User's Guide for more information about using this utility.

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

6.2.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: Firmware (3R031021) 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 (3R031021) 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 (3R031021) 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 (3R031021) 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 the Diagnostics Service Aids

  a) Invoke the Service Aids from on-line 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/3R031021.img

  d) If using an ASCII terminal press 'F7' key to 'Commit' the update.
       If using an HMC terminal  press 'ESC' + '7' keys to 'Commit' the update.

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

 Continue to paragraph 6.3 HMC Restore Functions to complete the procedure.

6.2.3 Using the AIX Command-Line Method

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.

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.

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

6.2.3.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 (3R031021) 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 (3R031021) 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 (3R031021) 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 (3R031021) for 7028-6C4 and 7028-6E4"

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

6.2.3.2 Updating With Files Already Loaded in the Target Server

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

       Enter the commands:

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

Continue to paragraph 6.3 HMC Restore Functions to complete the procedure.

6.3 HMC Restore Functions

The OP Panel on the server displays OK and the Managed System state on the HMC  shows  RECOVERY state.

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

6.4.2 Using the Service Processor Main Menu

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

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