7017-S8x System and Service Processor Firmware Update

Applies to : RS/6000  7017-S80, 7017-S85, and pSeries 680

This document describes the installation of Licensed Machine Code, which is sometimes referred to generically as microcode or firmware.


Contents


1.0 Systems Affected

This update provides new System and Service Processor (SvP) firmware (FW) for RS/6000 7017-S80 and 7017-S85 Servers and pSeries 680 only.  Do not use on any other systems.

The firmware levels contained in this update (Release S8xU9) are:

NOTE: The System and Service Processor Firmware are combined into a single file.  This allows both the System Firmware and Service Processor Firmware to be updated together and assures they are companion levels.

The typical time to install this firmware is two hours.  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 System firmware.
Table 2.2 lists the levels and descriptions for Service Processor firmware.
 
Table 2.1: System Firmware Update Descriptions and History
20040716
  • Added support for AIX 5.3.
  • Corrected problem with auto negotiation at 10/100 speeds for 10/100/1000 Base-T Ethernet PCI Adapter (FC 2975).
  • GUI SMS menus replaced with text based menus.
  • Added remote IPL support in GUI SMS settings menu for 10/100 Mbps Ethernet PCI Adapter II (FC 4962).
  • Added support to provide response to APR requests for Hot Standby Router Protocol (HSRP) or other network processes that generate ARP requests during NIM operations.
  • Resolved incomplete location code provided by diagnostis for I/O hub (RIO) faults.
20030731
  • Enhancements to SMS network adapter menus to resolve various configuration issues and ping test failures.
  • 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.
  • Resolves intermittent failure to power back on after shutdown -Fr command is issued.
  • For 7017-S85 only:  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).
  • Enhancements to prevent potential ping and NIM boot failures on SP and Cluster attached servers.
20030117
  • Corrected boot failure with checkpoint E1F6 displayed after bootlist is set via AIX and more than 5 devices are specified.
  • Corrected missing audible prompt when entering or exiting SMS menu and missing speaker POST test indicator.
  • Improved FRU isolation for error B46664588 during system boot.
  • Corrected 'Default Catch' message displayed on console after SMS 'Change SCSI ID' utility screen is accessed.
  • Parameter change to limit bootlist entries set via AIX to 5.
20020920
  • Added support for 4.7GB SCSI-2 DVD-RAM Drive, FC 2623.
  • Added support for IBM Gigabit Ethernet_SX and TX PCI-X Adapters  FC 5700 and 5701.
  • Corrected auto configuration,  ping and NIM failures on ethernet adapters attached to a switch or router with Spanning Tree Algorithm enabled.
  • Corrected boot failure with SMS Open Firmware prompt displayed when bootlist is set via AIX and more than 5 devices are specified.
  • Corrected missing devices in SMS bootlist when bootlist set via AIX.
  • Corrected error 20EE000B:  unable to find boot record after restore or NIM install on 36GB or larger disks.
  • Changed behavior to prevent AIX error log entries when processors are manually deconfigured.
20020411
  • Corrected EPOW handling to prevent system from hanging if power lost on redundant I/O drawer power supply(ies). 
  • Corrected problem with NIM install using IBM Universal 4-Port 10/100 Ethernet Adapter (FC  4961; Type  A-E). 
  • Corrected data rate and media type parameters in SMS not always remaining set on ethernet adapters. 
  • Corrected need to set gateway IP address to 0.0.0.0 in SMS if client and server on the same subnet. 
  • Corrected failure of machine to successfully reboot if "shutdown -Fr" or "reboot" issued from AIX within a few minutes of midnight GMT. 
20020118
  • Added functional support for 10/100 Mbps Ethernet PCI Adapter II (FC  4962; Type  A-F). 
  • Corrected problem causing erroneous reporting of SRN 651/901. 
  • Corrected handling of MN field in VPD information for memory cards. 
  • Corrected handling of non-tftp packets occurring during NIM install. 
  • Corrected "Default Catch" failure if NIM install manually interrupted. 
  • Corrected handling of "ping" to use gateway IP address if no server IP address specified. 
20010920
  • Added functional support for IBM Gigabit Fibre Channel Adapter for PCI Bus (FC  6227; Type  4-S). 
  • Added functional support for IBM Gigabit Fibre Channel Adapter for 64-bit PCI Bus (FC  6228, Type  4-W). 
  • Added functional support for SAN boot. 
  • Corrected device tree properties for handling 64-bit PCI Base Address Registers. 
  • Removed check for PCI Vendor ID and PCI device ID resulting in erroneously reporting Firmware/POST Error Codes 26020001 and/or 26020002. 
20010417
  • Added fast boot routine to achieve fairly significant reduction (~single-digit minutes saved) in BOOT time. 
  • Added functional support for IBM PCI Dual Channel Ultra3 SCSI Adapter (FC  6203; Type  4-Y). 
  • Corrected hang at Firmware Checkpoint E1DC when processors numbered 0, 1, 2, 3, 4 and 5 are all deconfigured at the same time. 
  • Added functional support for IBM 10/100/1000 Base-T Ethernet PCI Adapter (FC  2975; Type  A-A). 
20001003
  • Added functional support for Gigabit Ethernet - SX Adapter (FC  2969; Type  9-U). 
  • Added functional support for RS64 IV, 600MHz processors (CCIN#: 246F; Type 1; and CCIN#: 246E; Type 2). 
  • Corrected IBM Universal 4-Port 10/100 Ethernet Adapter (FC  4961, Type  A-E) parameters not always being setup properly. 
  • Corrected problem of certain types of SCSI adapters not being recognized under the "SCSI Utilities -> Change SCSI ID" menu in SMS. 
  • Corrected verification routines to ensure default variables properly initialized and assigned in NVRAM. 
20000524
  • Corrected ping failure when server is not visible to local network.
  • Miscellaneous minor fixes.
20000316
  • No functional changes, enhancements, or corrections. 
19991206
  • Enhanced error reporting for invalid address error.
  • Added support for IBM 4-Port 10/100 PCI Ethernet Adapter.
  • Corrected unknown program interrupt error due to cpuguard.
19990909
  • Corrected intermittent processor deallocation - with  POST error code 2B200031.
  • Corrected intermittent machine check due to parity error.
  • Enhanced error reporting for RIO failover.
  • Miscellaneous minor fixes.
19990824
  • Original (GA) level.

 
Table 2.2: Service Processor Firmware Update Descriptions and History
20040628
  • No functional changes, enhancements, or corrections.
20030731
  • No functional changes, enhancements, or corrections.
20030120
  • No functional changes, enhancements, or corrections. 
20020920 (S80)
or
20020921 (S85)
  • No functional changes, enhancements, or corrections. 
20020411
  • No functional changes, enhancements, or corrections. 
20020118
  • No functional changes, enhancements, or corrections. 
20010913
  • No functional changes, enhancements, or corrections. 
20010417
  • Added manufacturing enhancement to recognize vendor (Sony) SRAM ID for VPD fields. 
  • Corrected retries when "shutdown -Fr" issued to machine attached as node to an SP2 through a RAN causing faulty system hang at SRC  D1068000.
20001016
  • Corrected faulty reporting of Service Processor Error Code 40A00000 during boot. 
  • Added functional support for RS64 IV, 600MHz processors (CCIN 246F; Type 1; and CCIN 246E; Type 2). 
  • Added functional support for 8192MB memory card (CCIN 4A8C). 
20000524
  • Corrected OS Surveillance failure during AIX dump.
  • Corrected processor deallocation for post error.
  • Miscellaneous minor fixes.
20000316
  • Enhanced processor built-in self test.
  • Corrected problem during IPL boot resulting in a B46x240x error on the op panel display.
20000120
  • Added support for I/O Hub adapter version 2.1
  • Corrected faulty attention error 7FFFDD02.
19990910
  • Corrected intermittent shutdown -Fr failure.
  • Miscellaneous minor enhancements and fixes.
19990831
  • 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.

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.

Combined Update Process

The System and Service Processor Firmware are combined into a single image file. This allows both the System Firmware and Service Processor Firmware to be updated together and assures they are companion levels.

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 Service Processor card or system planar is replaced, the system and service processor firmware must be checked to ensure that they are at the latest companion levels. Table 3.1 lists the released levels of System and Service Processor firmware.
 
Table 3.1: Firmware Levels, File Sizes and Checksums
  Combined System and SvP Firmware Companion Levels Included
Distribution Date Filename Size Checksum System FW SvP FW
August 2004 S8xU9.img 3362400 37427 20040716 20040628
September 2003 S8xU8.img 3521360 54328 20030731 20030731
April 2003 S8xU7.img 3350136 36592 20030117 20030120
November 2002 S8xU6.img 3520376 02656 200020920 20020921/20020920
May 2002 S8xU5.img 3519188 17721 20020411 20020411
February 2002 S8xU4.img 3349232 47235 20020118 20020118
October 2001 S8xU3.img 3340572 46366 20010920 20010913
May 2001 S8xU2.img 3502344 63655 20010417 20010417
November 2000 S8xU1.img 3504316 25576 20001003 20001016
August 2000 S80V4.img 2783456 22910 20000524 20000524
April 2000 S80V3.img 2671942 16042 20000316 20000316
February 2000 S80V2.img 2671254 65055 19991206 20000120
October 1999 S80V1.img 2660286 50764 19990909 19999010
Original (GA) S80R11.img 2660818 25791 19990824 19990831

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 use the 8-digit Gregorian date code method in terms of year, month, and day (such as 20040716).


4.0 How to Determine Currently Installed Firmware Levels

DO NOT rely on the part number or firmware level marking/label on the EPROM/FLASH module because the content of the module may have been updated to a different level. To be safe, always check the firmware level electronically.

Use the following AIX command for checking the firmware levels.

   Enter:
      lscfg  -vp  |  grep  -p  alterable

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

 System Firmware VPD:
  ROM Level.(alterable).......20030731 (B)  20030731 (A) <= System FW levels
  Version.....................RS6K
  System Info Specific.(YL)...U0.1-P1-X1
 Physical Location: U0.1-P1-X1/Y1

 Service Processor Firmware VPD:
  ROM Level.(alterable).......20030731 (B) 20030731 (A)
  Version.....................RS6K
  System Info Specific.(YL)...U0.1-P1-X1/Y2
 Physical Location: U0.1-P1-X1/Y2
The ROM Level lines list the level (date) of the currently installed System and Service Processor firmware. In these examples (illustrations only), the system was booted from type B, since it is listed first. If the most recent level (A or B) is earlier than the update level(s) available for the server, you should install the update(s).

For more information about the uses of IPL Types A and B, see paragraphs 6.0 and 6.4, or refer to the Server's User's Guide.

If you find the firmware must be updated, proceed to Section 5.0. If the firmware levels are 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 System and Service Processor Firmware, in AIX and DOS packages, is located at the web site

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

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

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

      The download choices at that entry are:

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

      Enter:
        mkdir /tmp/fwupdate

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

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

  c) Unpack the file by executing the instructions below.

     Enter the commands:

        cd /tmp/fwupdate
        chmod +x 7017S8xF.BIN
        ./7017S8xF.BIN

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

    These files will be added to  /tmp/fwupdate:

         S8xU9.img
         promote.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, 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 S8xU9.img
       put promote.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: System and Service Processor FW (U9) and Promote
                         for S8x Servers and pSeries 680

     Volume 2: System and Service Processor FW (U9) and Promote
                         for S8x Servers and pSeries 680

     Volume 3: System and Service Processor FW (U9) and Promote
                         for S8x Servers and pSeries 680

Proceed to Section 6.0, Updating the Firmware.

5.1.2 Downloading the DOS Package

Use this method to download to a Windows workstation.

  a) Prepare a directory for receiving the DOS package.
      This directory can be in any partition with 10MB 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 7017S8xF.EXE

  c) Unpack the file by executing the instructions below.

      Enter the commands:

        cd [path]\fwupdate
        7017S8xF

These files will be added to the fwupdate subdirectory:

      S8xU9_B1.EXE
      S8xU9_B2.EXE
      S8xU9_B3.EXE

5.1.2.1 Diskettes for the AIX Command-Line Update Method

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

      Label the diskette,

           "Volume 1: System and Service Processor FW (U9) and Promote
                                 for S8x Servers and pSeries 680"

  b) With a second diskette loaded in the drive,

         Enter:
             S8xU9_B2

     Label the diskette,

           "Volume 2: System and Service Processor FW (U9) and Promote
                                 for S8x Servers and pSeries 680"

  c) With a third diskette loaded in the drive,

        Enter:
           S8xU9_B3

     Label the diskette,

           "Volume 3: System and Service Processor FW (U9) and Promote
                                 for S8x Servers and pSeries 680"

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, S8xU9.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 and Service Processor Firmware are combined into a single file. This allows both the System Firmware and Service Processor Firmware to be updated together and assures they are companion levels.

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

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

If the server is currently running from IPL Type B,  you should consider promoting that level before continuing. Use the instructions in paragraph 6.4, Promoting the Update, for reference.

Updating the firmware requires rebooting the server. The update is applied during the shutdown sequence following the firmware transfer.

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

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

The new firmware is placed in IPL Type B, for use while your acceptance tests are under way. When you are satisfied with the performance of the new level, "promote" it to  IPL Type A. There is no time limit on when promotion must occur. Thorough testing of any changes to the system is recommended before committing to them.

If you applied the update while running in IPL Type A, you will need to boot from IPL Type B in order to test the new level of firmware.

Updating firmware on the Server must be initiated either directly from the AIX command line or from the Update Flash Diagnostic Service Aid.

    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. Note: Checksums can be used to verify files have not been corrupted or altered during transmission.

      At the AIX command line, enter:

              sum S8xU9.img

    This command will produce the following output:

          37427  3284    S8xU9.img

    The checksum is -----> 37427

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/S8xU9.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 fifteen 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, reboots, and places the update in IPL Type B.  Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.

The update of the System and Service Processor firmware is complete. You will want to verify this update and then promote it after you have tested it to your satisfaction. Verifying is discussed in paragraph 6.3. Promotion is discussed 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
         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: System and Service Processor FW (U9) and Promote
                         for S8x Servers and pSeries 680"

When prompted for volume 2,

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

   "Volume 2: System and Service Processor FW (U9) and Promote
                         for S8x Servers and pSeries 680"

When prompted for volume 3,

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

   "Volume 3: System and Service Processor FW (U9) and Promote
                         for S8x Servers and pSeries 680"

The files are now in the /tmp/fwupdate subdirectory.

       Enter the commands:

           cd  /usr/lpp/diagnostics/bin
          ./update_flash  -f  /tmp/fwupdate/S8xU9.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 fifteen 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, reboots, and places the update in IPL Type B. Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.

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 System and Service Processor firmware is complete. You will want to verify this update and then promote it after you have tested it to your satisfaction. Verifying is discussed in paragraph 6.3. Promotion is discussed 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 S8x User's Guide, eServer pSeries 680
                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
        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: System and Service Processor FW (U9) and Promote
                          for S8x Servers and pSeries 680"

When prompted for volume 2,

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

    "Volume 2: System and Service Processor FW (U9) and Promote
                          for S8x Servers and pSeries 680"

When prompted for volume 3,

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

   "Volume 3: System and Service Processor FW (U9) and Promote
                         for S8x Servers and pSeries 680"

The files are now in the /tmp/fwupdate subdirectory.  Continue to paragraph 6.2.2.

6.2.2 Updating with the Diagnostic Service Aid Method

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

  b) Choose Update System or Service Processor Flash.

  c) Follow the on-screen update steps as they are presented.
      When you are asked for a filename, first list the files and then select the appropriate
      one for the update task.

  Use the directory and filename information as shown below.

  The update file is /tmp/fwupdate/S8xU9.img

The server automatically performs the update, reboots, and places the update in IPL Type B. Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.

The update of the System and Service Processor firmware is complete. You will want to verify this update and then promote it after you have tested it to your satisfaction. Verifying is discussed in paragraph 6.3. Promotion is discussed in paragraph 6.4.

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.

6.3 Verifying the Updates

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

     Enter:
        lscfg  -vp  |  grep  -p  alterable

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

      System Firmware VPD:
        ROM Level.(alterable).......20040716 (B) 20030731 (A)
        Version.....................RS6K
        System Info Specific.(YL)...U0.1-P1-X1/Y1
      Physical Location: U0.1-P1-X1/Y1

      Service Processor Firmware VPD:
        ROM Level.(alterable).......20040628 (B) 20030731 (A)
        Version.....................RS6K
        System Info Specific.(YL)...U0.1-P1-X1/Y2
      Physical Location: U0.1-P1-X1/Y2
The (B) ROM Levels  should match the levels you just installed, namely, 20040716 and 20040628.

6.4 Promoting the Updates

It is important for the promotion process to succeed. Therefore, it is recommended that you read and understand this section before you begin the promotion process.

The server maintains two copies of System and Service Processor firmware. These copies reside in locations referred to as IPL Type A and IPL Type B.

The server normally runs IPL Type A. New firmware updates are stored in IPL Type B until they are promoted. Once promotion takes place, the two IPL types are identical.

Operator panel function 01 may be used to determine which IPL type is in use at any given time. See the Server's User's Guide for more information about operator panel functions.

Between the time of a firmware update and the promotion procedure, the server may be instructed (using operator panel function 02) to use either IPL type for the purpose of firmware testing.

 When this update has been tested thoroughly,  and you are ready to promote the new firmware, the server MUST be using IPL Type B. Otherwise the promotion fails. The recovery procedure is:

  a) Turn off the server power

  b) Switch the server's operation to IPL Type B

  c) Turn on the server power

Be aware that the promotion process requires the server to shut down all of its processes to rewrite the IPL and reboot from it.

To promote the firmware refer to the instructions you used to install the update. Use the same instructions (i.e., either the AIX command-line method or the Update Flash Diagnostic Service Aid method) to execute the promotion.

This time, use the promote.img file rather than the filename you selected previously. It is located either:

As promotion occurs, during the processes shutdown sequence, checkpoint E082 appears during the promotion activity. This checkpoint can last several minutes, depending on the server's configuration.

When the promotion is processed, the server automatically begins using IPL Type A.

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 only files, archive and identify the files for convenient retrieval.


End of Installation Instructions