pSeries 655 Firmware Update

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

Contents

• 1.0  Systems Affected
• 2.0  Firmware Description and Revision History
• 3.0  Cautions and Important Notes
• 4.0  How to Determine Currently Installed Firmware Level
• 5.0  Downloading and Unpacking the Firmware Update Package
• 5.1      Internet Package
• 5.2     Remote Installation of Firmware
• 6.0  Updating the Firmware
• 6.1      Full System Partition
• 6.2      Partitioned System
• 6.3      HMC Restore Functions
• 6.4      Verifying the Update
• 6.5      Archiving the Update Files

 1.0  Systems Affected

The firmware level contained in this update are:

3J080425

ATTENTION:  Due to significant fixes in 4th quarter 2003 and 1st quarter 2004 firmware releases to improve
                                system availability, f irmware level 3J040326 or higher is being made mandatory for all 7039 systems.

2.0  Firmware Description and Revision History

3.0  Cautions and Important Notes

Before Beginning the Update

Before installing this level of firmware, ensure the Hardware Management Console (HMC) code on all HMC systems is Release 3, Version 1.2 or later.  If a High Performance Switch (7045-SW4) is installed, the HMC code on all HMC systems must be Release 3, Version 2.6 or later.  If you will be updating hardware, you will need to refer to the specific MES document to identify the required level of HMC code.

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

Linux

Firmware Update Installation Is Not Concurrent

Never Power Off the System during the Firmware Update Process

AIX and Linux Instructions are CASE SENSITIVE

Replacement Parts May Require Updating

4.0  How to Determine Currently Installed Firmware Levels

• If using AIX, continue to paragraph 4.1.
• If using Service Processor Main Menu, skip to paragraph 4.2.
• If using Linux, skip to paragraph 4.3.

4.1  Using AIX to Read Currently Installed Firmware Levels

    Enter:
        lscfg  -vp |  grep -p Platform

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

     Platform Firmware:
          ROM Level.(alterable).......3J061030
          Version.....................RS6K
          System Info Specific.(YL)...U1.18-P1-H2/Y2
        Physical Location: U1.18-P1-H2/Y23

If the right-most six characters (date) of the current firmware level are earlier than 080425, you should consider installing the update.

If you find the firmware must be updated, proceed to Section 5.0.   If the firmware level is correct and no update is needed, installation is complete.

4.2  Using the Service Processor Main Menu

If the right-most six characters (date) of firmware level are earlier than 080425, you should consider installing the update.

If you find the firmware must be updated, proceed to Section 5.0.  If the firmware level is correct and no update is needed, installation is complete.
 

4.3 Using Linux to Read Currently Installed Firmware Levels

         Enter:
            /sbin/lscfg -vp | grep -A 1  Platform

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

     Platform Firmware:
          ROM Level.(alterable).......3J061030

If the right-most six characters (date) of the current firmware level are earlier than 080425, you should consider installing the update.

If you find the firmware must be updated, proceed to Section 5.0.  If the firmware level is correct and no update is needed, installation is complete.

5.0  Downloading and Unpacking the Firmware Update Package

5.1 Internet Package

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

Follow the instructions on this web page.

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

The download choices at that entry are:

• Desc                      (Instructions document)
• AIX                      (For downloading to an AIX system)
• DOS                     (For downloading to a Windows workstation)
• RPM                     (For downloading to the target server ONLY - AIX or Linux)

• By downloading files directly to the target server.
• By downloading files to an intermediate AIX system and then using ftp for transferring to the target server.
• By downloading files to a Windows workstation and then using diskettes for transferring to an intermediate AIX system.

• If using the AIX package for downloading, continue to paragraph 5.1.1.
• If using the DOS package for downloading, skip to paragraph 5.1.2.
• If using the RPM package for downloading, skip to paragraph 5.1.3.

5.1.1 Downloading the AIX Package

  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 7039651F.BIN

   c) Unpack the file by executing the instructions below.

      Enter the commands:

        cd   /tmp/fwupdate
        chmod   +x   7039651F.BIN
        ./7039651F.BIN

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

      This file will be added to  /tmp/fwupdate.

          3J080425.img

• If the above procedure was used to transfer files directly to the target server, proceed to Section 6.0, Updating the Firmware.
• If the AIX package was transferred to an intermediate AIX system, continue to paragraph 5.1.1.1.

5.1.1.1 The FTP Transfer Method

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  3J080425.img
        quit

Proceed to Section 6.0, Updating the Firmware.

5.1.2 Downloading the DOS Package

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

   c) Unpack the file by executing the instructions below.

       Enter the commands:

         cd  [path]\fwupdate
         7039651F

These files will be added to the fwupdate subdirectory:

      3J080425.img
      39651_B1.exe
      39651_B2.exe
      39651_B3.exe
      39651_B4.exe
      39651_B5.exe

• To transfer files to the target server using ftp, continue to paragraph 5.1.2.1.
• To create diskettes for transferring files to the intermediate AIX system, skip to paragraph 5.1.2.2.

5.1.2.1 The FTP Transfer Method

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  3J080425.img
        quit

Proceed to Section 6.0, Updating the Firmware.

5.1.2.2 Diskettes for Intermediate AIX System

   Note: The diskettes produced below will be in AIX backup format and cannot
              be read using normal PC platform tools or command line operations.

  a) With a diskette loaded in the drive,

         Enter the commands:

            cd [path]\fwupdate
            386M2_B1

      Label this diskette,

           "Volume 1: Firmware (3J080425) for 7039-651"

  b) With a second diskette loaded in the drive,

         Enter:
             386M2_B2

     Label this diskette,

           "Volume 2: Firmware (3J080425) for 7039-651"

  c) With a third diskette loaded in the drive,

         Enter:
             386M2_B3

     Label this diskette,

           "Volume 3: Firmware (3J080425) for 7039-651"

 d) With a fourth diskette loaded in the drive,

         Enter:
             386M2_B4

     Label this diskette,

           "Volume 4: Firmware (3J080425) for 7039-651"

e) With a fifth diskette loaded in the drive,

         Enter:
             386M2_B5

     Label this diskette,

           "Volume 5: Firmware (3J080425) for 7039-651"

  f)  On the intermediate AIX system,

          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: Firmware (3J080425) for 7039-651"

When prompted for volume 2,

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

    "Volume 2: Firmware (3J080425) for 7039-651"

When prompted for volume 3,

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

    "Volume 3: Firmware (3J080425) for 7039-651"

When prompted for volume 4,

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

    "Volume 4: Firmware (3J080425) for 7039-651"

When prompted for volume 5,

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

    "Volume 5: Firmware (3J080425) for 7039-651"

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

    g)  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  3J080425.img
             quit

 Proceed to Section 6.0, Updating the Firmware.

5.1.3 Downloading the RPM Package to the Target Server

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

  c) Unpack the file by executing the instructions below.

     Enter the commands:

        rpm -ihv --ignoreos 3J080425.rpm

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

The file size and checksum will be verified.

Proceed to Section 6.0 Updating the Firmware.
 

5.2 Remote Installation of Firmware

6.0  Updating the Firmware

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

***
WARNING:

Do not power off the target 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 can be used to verify files have not been corrupted or altered during transmission.

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

           The output will look like this ------->  37083  6331   3J080425.img
           The checksum is --------------->  37083

6.1 Full System Partition

6.1.1  Using the AIX Command-Line Method

You must have root authority on the target server to update its firmware.  Because the update process will cause an automatic reboot, be sure the system is not running any user applications.

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

  Enter the commands:

        cd  /usr/lpp/diagnostics/bin
        ./update_flash  -f  /tmp/fwupdate/3J080425.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 target server.  Since the update occurs during this shutdown/reboot sequence, it is important to protect the server from interruptions.

NOTE:  On the HMC terminal you will need to close the existing terminal window and open a new terminal window when the State shows INITIALIZING.

NOTE:  You may see a frame icon 'Unknown*Frame' that was created during the update.  If so, click on 'Unknown*Frame', then chose Refresh.  This will delete the icon.

If you are using an HMC, once you have powered on the system:

• If the Managed System state on the HMC is either RECOVERY or INCOMPLETE, skip to paragraph 6.3 HMC Restore Functions to complete the procedure.
• If the Managed System state on the HMC is READY, the update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.

6.1.2 Using the Service Aids Method

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

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

  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/3J080425.img

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

   e) Choose Yes to continue.

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:  On the HMC terminal you will need to close the existing terminal window and open a new terminal window when the State shows INITIALIZING.

NOTE:  You may see a frame icon 'Unknown*Frame' that was created during the update.  If so,  click on 'Unknown*Frame', then chose Refresh.  This will delete the icon.

If you are using an HMC,  once you have powered on the system:

• If the Managed System state on the HMC is either RECOVERY or INCOMPLETE, skip to paragraph 6.3 HMC Restore Functions to complete the procedure.
• If the Managed System state on the HMC is READY, the update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.

6.2  Partitioned System

6.2.1 Using the AIX Command-Line Method

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

 ATTENTION:  This method requires the device resources to be 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.

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

       Enter the commands:

           cd /usr/lpp/diagnostics/bin
          ./update_flash -f /tmp/fwupdate/3J080425.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:  On the HMC terminal you will need to close the existing terminal window and open a new terminal window when the Operator Panel Value shows LPAR.

NOTE:  You may see a frame icon 'Unknown*Frame' that was created during the update.  If so, click on 'Unknown*Frame', then chose Refresh.  This will delete the icon.

If the Managed System state on the HMC is either RECOVERY or INCOMPLETE, skip to paragraph 6.3 HMC Restore Functions to complete the procedure.

If the Managed System state on the HMC is READY, the update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.

6.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/3J080425.img

  d) f using an HMC terminal  press 'ESC' + '7' keys to 'Commit' the update.

  e) Choose Yes to continue.

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:  On the HMC terminal you will need to close the existing terminal window and open a new terminal window when the Operator Panel Value shows LPAR.

NOTE:  You may see a frame icon 'Unknown*Frame' that was created during the update.  If so, click on 'Unknown*Frame', then chose Refresh.  This will delete the icon.

If the Managed System state on the HMC is either RECOVERY or INCOMPLETE, skip to paragraph 6.3 HMC Restore Functions to complete the procedure.

If the Managed System state on the HMC is READY, the update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.

6.2.3 Using the Linux Command-Line Method

 ATTENTION:  This method requires the device resources to be allocated properly.  This requires:

                              - One partition running Linux must have service authority.
                              - All other partitions except the one with service authority must be shut down.
                              - The partition with service authority must own the device from which the firmware
                                   update image will be read.
                              - It is also recommended that the partition with service authority have a hard disk.

If the required devices are not in the partition with service authority, the customer or system administrator must reassign the appropriate resources to it. This requires rebooting the partition with service authority.

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

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

     Enter the commands:

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

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

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

If the Managed System state on the HMC  is either RECOVERY or INCOMPLETE,  skip to paragraph 6.3 HMC Restore Functions to complete the procedure.

If the Managed System state on the HMC is  READY, the update of the firmware is complete. You will want to verify this update as shown in paragraph 6.4.

6.3 HMC Restore Functions

    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

• If using AIX, continue to paragraph 6.4.1.
• If using Service Processor Main Menu, skip to paragraph 6.4.2.
• If using Linux, skip to paragraph 6.4.3.

6.4.1 Using AIX

         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).......3J080425
        Version.....................RS6K
        System Info Specific.(YL)...U1.18-P1-H2/Y2
      Physical Location: U1.18-P1-H2/Y2

6.4.2 Using the Service Processor Main Menu

6.4.3 Using Linux

         Enter:
            /sbin/lscfg -vp | grep -A 1  Platform

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

     Platform Firmware:
          ROM Level.(alterable).......3J080425

6.5  Archiving the Update Files

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