RS/6000 S7x Series System and Service Processor Firmware Update

Applies to : IBM RS/6000 7013-S70, 7015-S70, 7017-S70
                                                  7013-S7A, 7015-S7A, 7017-S7A

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 7013 S70 and S7A, 7015 S70 and S7A, and 7017 S70 and S7A servers only.   Do not use on any other systems.

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

WARNING:  You willl need to be running a 32-bit kernel in order to update to this level of firmware.  Use the AIX command bootinfo -K to determine the current kernel type.  If you are currently running a 64-bit kernel,  you will have to reconfigure to a 32-bit kernel before updating the firmware.  If assistance in reconfiguring the kernel is required, contact your software support.

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.

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.

NOTE:  This firmware package CANNOT be used to update any S70 or S7A Series Servers that have System Firmware level earlier than 19990416, and Service Processor Firmware level earlier than 19990412 installed. See table 4.1 Update Decisions.


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.
  • 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.
20031006
  • Corrected missing audible prompt when entering or exiting SMS menu and missing speaker POST test indicator.
  • Corrected boot failure with 'Default Catch' message displayed on console after SMS 'Change SCSI ID' utility is accessed.
  • Parameter change to limit boot list entries set via AIX to 5.
  • Corrects system crash due to Program Interrupt updating system firmware from AIX in 64bit kernel mode.
  • Enhancements to prevent potential ping and NIM boot failures on SP and Cluster attached servers.
  • Resolves intermittent failure to power back on after shutdown -Fr command is issued.
  • Corrected boot failure with 'Default Catch' message displayed on console when booting from tape media containing large boot image.
20021007
  • Corrected error 20EE000B:  unable to find boot record after restore or NIM install on 36GB or larger disks.
  • Corrected auto configuration, ping and NIM failures on ethernet adapters attached to 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.
20020514
  • Added support for IBM Universal 4-Port 10/100 Ethernet Adapter FC4961. 
  • Corrected IBM 10/100 Mbps Ethernet PCI Adapter FC 2968 and IBM Universal 4-Port 10/100 Ethernet Adapter FC 4961 speed

  • settings within SMS. 
  • Corrected problem when issuing shutdown -Fr where system fails to power back up. 
  • Corrected problem that failed to detect an unplugged or bad redundant P/S on I/O drawers with 10 EIA units. 
  • Corrected problem when Gigabit Fibre Channel Adapter for PCI Bus FC 6227 or Gigabit Fibre Channel Adapter for 64-bit PCI Bus
  • FC 6228 was on the same PCI bridge chip as a GXT130 adapter. 
  • Corrected problem to allow backing up to SMS menu after Ping with Token ring. 
  • Corrected the VPD property for the 10/100/1000 Base-T Ethernet PCI Adapter FC 2975. 
  • Corrected problem when NIM install/boot is interrupted. 
  • Corrected  NIM boot failure when non-TFTP packets are received. 
  • Corrected EPOW handling to prevent system from hanging if power lost on redundant I/O drawer power supply(ies).
20010824
  • Added support for the 10/100/1000 Base-T Ethernet PCI Adapter FC 2975. 
  • Added support for IBM Universal 4-Port 10/100 Ethernet Adapter FC 4961. 
  • Corrected open firmware dir command problem related to Y2K fix. 
  • Corrected a problem with booting from mksysb on CDROM. 
  • Corrected a problem with service processor being reset intermittently. 
  • Corrected a VPD problem with missing clock card location code. 
  • Corrected a problem with VPD that allows correct processor numbering. 
  • Corrected a map addressing problem to report the correct I/O drawer. 
  • Corrected a VPD problem with location codes with AIX version 4.3.3 using lscfg -vp. 
  • Modified PCI bus algorithm to callout the correct failing adapter. 
  • Corrected a problem where SysKonnect SK-NET FDDI-LP SAS PCI FC 2741 cards don't filter out broadcast packets. 
  • Corrected a problem where system would hang while booting from Service Processor to SMS menu. 
19990917
  • Enhanced EPOW handling.
  • Increased firmware memory footprint to support more devices.
  • Corrected SMS menu screen problem.
  • Corrected system machine check error with diag SRN 9CC-102, 106, 10A,10E.
  • Miscellaneous minor enhancements and fixes.
19990416
  • Added fix to prevent a system hang which can occur as a result of the rollover to Year 2000.
  • Corrected hang problem that occurred after progress code E1DC.
  • Added support for Ultra-2 SCSI Adapter.
  • Added support to allow the server  to boot from a CDROM using bootlist.
  • Added  checking  to assure the update flash image is for  the S7x  Series products.
  • Miscellaneous minor enhancements.
19990121
  • Added GUI and TTY support for FDDI.
  • Corrected an intermittent hang occurring during NIM  installation at checkpoint E105. This is associated with the IBM 10/100Mbps Ethernet PCI adapter.
  •  Miscellaneous minor enhancements.
19981110
  • Updated FDDI microcode to level 12.07.
  • Miscellaneous minor fixes.
19980825
  • Added support for 1Gbps ethernet.
  • Added support for 10 EIA I/O drawer.
19980722
  • Added support for RS64-II 250MHz processor.
  • Enhanced data collection and reporting of error events.
19980429
  • Added support for FDDI as boot device.
  • Corrected L2 Cache size problem.
19980220
  • Diagnostic enhancements.
19971215
  • Miscellaneous minor fixes.
19971008
  • Original (GA) level.

 
Table 2.2: Service Processor Firmware Update Descriptions and History
20040716
  • Companion level to System Firmware level 20040716.
20031006
  • Companion level to System Firmware level 20031006.
20021004
  • Corrected potential cause for error 40A000000 during boot on systems with large quantities of DASD.
20010824
  • Enhanced array correction for processor machine check problems at runtime.
19990908
  • Corrected intermittent shutdown -Fr failure.
  • Miscellaneous minor enhancements and fixes.
19990412
  • Corrected problem that caused the system to hang during Year 2000 rollover. 
  • Added Service Processor Menu for boot mode setup.
  • Miscellaneous minor corrections. 
19990122
  • System modes have been changed to decrease the possibility of a checkstop.  The SRCs for these potential checkstops are: 
            word 11  B4604400 
            word 11  B4604401 
            word 11  B4604402 
            word 13  710xBBA2 (where x can be 0..9,A,B)
19981110
  • Protected system processor from accessing reserved address space
  • OP-Panel code enhancement
19980825
  • Added support for 10 EIA I/O drawer 
  • Added support to update SPCN in I/O drawer 
  • Added SvP menu controls for configuring processors 
  • Corrected instruction unit hang problem in RS64-II processor
19980729
  • Added support for RS64-II 250MHz processor.
  • Improved error handling and reporting.
19980429
  • Corrected a clocking condition that allowed a hang at ED00.
19980220
  • Added support for 64-bit memory cards.
  • Updated operator panel control for consistency.
19971106
  • Added support for IBM modems 7852-400 and 7857-017.
  • Corrected machine check presentation on op panel.
  • Improved speed for downloading SPCN program.
19971007
  • 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.

Potential Problem with Gigabit Ethernet Adapter

Firmware updates, Release S7XR9 and higher, potentially exposed the system to Machine Check errors with diagnostic SRN of  9CC-669 if any Gigabit Ethernet adapter (FC 2969) is installed in slots 11-14 in either the primary or secondary drawer of  a 701x-S7A.  To correct this problem, please remove the Gigabit Ethernet adapter (FC 2969) from its current slot, and move it to a slot as prescribed by the Adapter Placement Reference for AIX.

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 released levels of System and Service Processor firmware.   Table 3.2 lists previously released firmware information.
 
Table 3.1:  Combined Firmware,  File Sizes and Checksums
  Combined System and Service Processor Firmware Companion Levels Included
 Distribution Date  Filename   Size  Checksum Sys FW SvP FW
August 2004   S7RX14.img   4019238   14867             20040716            20040716
 November 2003   S7RX13.img   4019242   61070 20031006 20031006
 November 2002   S7XR12.img   4019246   63527 20021007 20021004
 June  2002   S7XR11.img   4019242   59743  20020514 20010824
 Oct  2001   S7XR10.img   4019242   40588  20010824 20010824
 Oct  1999   S7XR9.img   4018422   52105   19990917  19990908

 
Table 3.2:  Companion Firmware Levels, File Sizes and Checksums
  System Firmware Service Processor Firmware
Distribution Date Filename Size Checksum Filename Size Checksum
Oct  1999 S7XR9SY.img 1573530 39492 S7XR9SP.img 2444892 14858
April 1999 S7XR8SY.IMG 1573530 51001 S7XR8SP.IMG 2444528 49186
Feb 1999 S7XR7SY.IMG 1573530 51069 S7XR7SP.IMG 2438572 45711
Nov 1998 S7XR6SY.IMG 1573530 54648 S7XR6SP.IMG 2438920 17312
Sept 1998 S7XR5SY.IMG 1573530 03673 S7XR5SP.IMG 2437872 48607
August 1998 S70R4SY.IMG 1573530 53851 S70R4SP.IMG 2421572 23011
May 1998 S70Rel3.img 3105363 50678 Combined with System FW
March 1998 012H7777.ruhxa 1573530 59833 SP980220.img 1531833 22963
January  1998 012H7777.ruhxa 1573530 28335 SP980105.img 1526433 54722
Original (GA) 012H7777.ruhxa 1573530 22001 SP971008.img  1520613 52645

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
  ROM Level.(alterable).......20031006 (A)  20021007 (B) <= System FW levels
  Version.....................RS6K
  System Info Specific.(YL)...u0.1-P1-X1

 SP_CARD_:
  Part Number.................PART_NUM
   EC Level....................EC_LEVEL
   FRU Number..................FRU_NUM_
   Manufacture ID..............IBM_
   Serial Number...............SERIAL_#
   System Info Specific.(YL)...u0.1-P1-X1

   ROM Level (alterable).......20031006 (A)  20021004 (B) <= SvP FW levels
The ROM Level lines list the level of the currently installed System and Service Processor firmware.  In these examples (illustrations only), the system was booted from type A, since it is listed first.  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 Users Guide.  For information on how to proceed, See Table 4.1.
 
Table 4.1:  Update Decisions
  If  Type A contains: and  Type B contains: Do this:
 1 System FW level 19990416 (or later)
                    and 
SvP FW level 19990412 (or later)
Any levels other than those contained in this package Proceed to Section 5.0 to update the firmware.
 2 Any levels other than those contained in this package System FW level 19990416  (or later)
           and
SvP FW level 19990412  (or later)
Promote contents of Type B to Type A  (see paragraph 6.4)
        then
Proceed to Section 5.0 to update the firmware.
 3 System FW level earlier than 19990416
          and
SvP FW level earlier than 19990412
System FW level earlier than 19990416 
                and
SvP FW level earlier than 19990412
Call your IBM Customer Engineer (CE).

If you find the firmware must be updated, proceed as specified above.  If no update is needed, installation is complete.


5.0  Downloading and Unpacking the Firmware Update Package

Instructions for downloading and unpacking the firmware update package follow.

Prerequisite:  System Firmware level 1990416 or later and Service Processor Firmware level 19990412 or later must be running on type A of the server in order to update firmware using this section.  Otherwise, the update will fail.

If the server meets the conditions for success stated above, continue to paragraph 5.1,  if not, you must return to  table 4.1 Update Decisions to determine  how to install the firmware update.

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 at once and assures the two firmware levels are companion levels.

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 that the filename is 7017S7XF.BIN

   c) Unpack the file by executing the instructions below.

      Enter the commands:

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

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

      These files will be added to  /tmp/fwupdate:

              S7XR14.img
              promote.img

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

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

5.1.1.1 The FTP Transfer Method

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

On the intermediate AIX system,

     Enter the commands:

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

        bin
        lcd  /tmp/fwupdate
        mkdir   /tmp/fwupdate
        cd   /tmp/fwupdate
        put  S7XR14.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 another diskette when the first is full):

          cd  /tmp/fwupdate
          ls  *.img |  backup  -i  -v  -f/dev/rfd0

This will produce AIX backup diskettes.  Label these diskettes, respectively,

      "Volume 1: System (20040716) and SvP (20040716) FW (R14) and Promote for
                            S7x Series Servers"

      "Volume 2: System (20040716) and SvP (20040716) FW (R14) and Promote for
                             S7x Series Servers"

      "Volume 3: System (20040716) and SvP (20040716) FW (R14) and Promote for
                            S7x Series Servers"

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 7017S7XF.EXE

   c) Unpack the file by executing the instructions below.

       Enter the commands:

         cd  [path]\fwupdate
        7017S7XF

      These files will be added to the fwupdate subdirectory:

          S7XR14B1.EXE
          S7XR14B2.EXE
          S7XR14B3.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 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
          S7XR14B1

      Label this diskette,

        "Volume 1: System (20040716) and SvP (20040716) FW (R14) and Promote for
                              S7x Series Servers"

  b) With a second diskette loaded in the drive,

        Enter:
           S7XR14B2

      Label this diskette,

        "Volume 2: System (20040716) and SvP (20040716) FW (R14) and Promote for
                              S7x Series Servers"

   c) With a third diskette loaded in the drive,

        Enter:
            S7XR14B3

      Label this diskette,

       "Volume 3: System (20040716) and SvP (20040716) FW (R14) and Promote for
                             S7x Series Servers"

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

6.0  Updating the Firmware

Prerequisite:  System Firmware level 1990416 or later and Service Processor Firmware level 19990412 or later must be running on type A of you system in order to update firmware using this section.  Otherwise, the update will fail.

If you server meets the conditions for success stated above, continue,  if not, you must return to Table 4.1 Update Decisions to determine  how to install the firmware update.

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.

***
WARNING:

Do not power off the target server at any time before the update process completes.  Be sure the server 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 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 twenty five 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 server 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 in the S7x Series servers 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  S7XR14.img

           This command will produce the following output:

             14867  3926      S7XR14.img

           The checksum is ----->    14867

6.1.1 Updating With Files Already Loaded in the Target Server

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

      Enter the commands:

        cd  /usr/lpp/diagnostics/bin
        ./update_flash  -f  /tmp/fwupdate/S7XR14.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 twenty five  minutes, 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 the 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.3Promotion 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

  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: System (20040716) and SvP (20040716) FW (R14) and Promote
                               for S7x Series Servers"

When prompted for volume 2,

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

         "Volume 2: System (20040716) and SvP (20040716) FW (R14) and Promote
                                for S7x Series Servers"

When prompted for volume 3,

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

         "Volume 3: System (20040716) and SvP (20040716) FW (R14) and Promote
                               for S7x Series Servers"

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

      Enter the commands:

        cd  /usr/lpp/diagnostics/bin
        ./update_flash  -f  /tmp/fwupdate/S7XR14.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 twenty five minutes, 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.3Promotion 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.2 Using the Update Flash Diagnostic Service Aid Method

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

          Note:   Review "Update System or Service Processor Flash" in the Service Aids
                        section of the RS/6000 Enterprise Server S7x User's Guide for more
                        information about using this utility.

6.2.1 File on Diskettes

      Enter the commands:

           mkdir /tmp/fwupdate

     Note: If the directory [path]\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 (20040716) and SvP (20040716) FW (R14) and Promote
                               for S7x Series Servers"
 

When prompted for volume 2,

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

         "Volume 2: System (20040716) and SvP (20040716) FW (R14) and Promote
                               for S7x Series Servers"

When prompted for volume 3,

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

         "Volume 3: System (20040716) and SvP (20040716) FW (R14) and Promote
                               for S7x Series Servers"

The files are now located 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, diskette and filename information as shown  below.

        The update file is /tmp/fwupdate S7XR14.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.3Promotion 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 updates 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:
  ROM Level (alterable).......20040716 (B)  20020524 (A)<= System FW levels
  Version.....................RS6K
  System Info Specific.(YL)...u0.1-P1-X1
 SP_CARD_:
   Part Number.................PART_NUM
   EC Level....................EC_LEVEL
   FRU Number..................FRU_NUM_
   Manufacture ID..............IBM_
   Serial Number...............SERIAL_#
   System Info Specific.(YL)...u0.1-P1-X1

   ROM Level (alterable).......20040716 (B)  20010824 (A) <= SvP FW levels
The (B) ROM Levels  should match the levels you just installed, namely, 20040716 and 20040716 respectively.

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 Users 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 to IPL from Type B

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


End of Installation Instructions