pSeries 650 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   Downloading from the Microcode Update Files and Discovery Tool CD
• 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 is:

•   3K050715

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.

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

Native Linux Systems

Firmware Update Installation Is Not Concurrent

Recovery Mode

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 Level

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

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

If the right-most six characters (date) of the current firmware level are earlier than 050715, 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  Downloading from the Microcode Update Files and Discovery Tool CD

      Enter:
        mkdir /tmp/fwupdate

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

      cd /tmp/microcode/RPM
      mv 3K050715.rpm /tmp/fwupdate
      cd /tmp/fwupdate
      rpm -ihv --ignoreos 3K050715.rpm

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

The file size and checksum will be verified.

If you are installing manually:

      Enter:
        mkdir /tmp/fwupdate

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

Copy the 3K050715.img file to the /tmp/fwupate directory.

If you are updating using the Service Processor Menus, or need diskettes for recover mode, you will need to make diskettes on a system running AIX as follows:

Four 2MB (HD) new diskettes are required.

With a diskette loaded in the drive,

  Enter the AIX 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 (3K050715) for  7038-6M2"

     "Volume 2:  Firmware (3K050715) for  7038-6M2"

     "Volume 3:  Firmware (3K050715) for  7038-6M2"

     "Volume 4:  Firmware (3K050715) for  7038-6M2"

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 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 3K050715.img

         The output will look like this ------>  61224  4981   3K050715.img
         The checksum is -------------->  61224

It is recommended that the update, on both a full system partition and a partitioned system, be performed using the Service Processor Menus.  Updating the firmware using the Service Processor Menus avoids the resource allocation issues that can arise if the server is a partitioned system.

• If updating the firmware infull system partition mode, continue to paragraph 6.1.
• If updating the firmware in partitioned system mode, skip to paragraph 6.2.

6.1 Full System Partition

6.1.1  Using the Service Processor Menus Method (Recommended)

Service Processor Menus allow updating from AIX backup diskettes only.

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

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

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

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

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

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

    e. Type y to continue.  <Enter>

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

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

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

    h. Begin watching the operator panel.

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

          The Service Processor Menu appears on your screen.

         The second line of the title, Version: 3K050715, 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.

If you are using an ASCII terminal, the update of the firmware is complete.

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.

6.1.2 Using the AIX Command-Line Method

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

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

• If the file is loaded in the target server, skip to paragraph 6.1.2.2.
• If the file is on diskettes, continue to paragraph 6.1.2.1.

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 (3K050715) for 7038-6M2"

    When prompted for volume 2,

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

          "Volume 2: Firmware (3K050715) for 7038-6M2"

     When prompted for volume 3,

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

          "Volume 3: Firmware (3K050715) for 7038-6M2"

     When prompted for volume 4,

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

          "Volume 4: Firmware (3K050715) for 7038-6M2"

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

6.1.2.2 Updating With Files Already Loaded in the Target Server

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

     Enter the commands:

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

If you are using an ASCII terminal, the update of the firmware is complete.  You will want to verify this update as shown in paragraph 6.4.

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.3 Using the Linux Command-Line Method

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

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

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

     Enter the commands:

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

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

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

If you are using an ASCII terminal, the update of the firmware is complete.  You will want to verify this update as shown in paragraph 6.4.

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 Service Processor Menus Method (Recommended)

Service Processor Menus allow updating from diskettes only.

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

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

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

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

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

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

    e. Type y to continue. <Enter>

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

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

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

    h. Begin watching the operator panel.

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

          The Service Processor Menu appears on your screen.

         The second line of the title, Version: 3K050715, 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.

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.

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

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

• If the file is loaded in the target server, skip to paragraph 6.2.2.2.
• If the file is on diskettes, continue to paragraph 6.2.2.1.

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 (3K050715) for 7038-6M2"

    When prompted for volume 2,

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

          "Volume 2: Firmware (3K050715) for 7038-6M2"

     When prompted for volume 3,

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

          "Volume 3: Firmware (3K050715) for 7038-6M2"

     When prompted for volume 4,

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

          "Volume 4: Firmware (3K050715) for 7038-6M2"

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

6.2.2.2 Updating With Files Already Loaded in the Target Server

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

       Enter the commands:

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

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

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

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

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

If the 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

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

 ATTENTION:  This method is not recommended for partitioned systems, unless the device resources
                                are allocated properly.  This requires:

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

If the required devices are not in the partition with service authority, the customer or system administrator must reassign the appropriate resources to it. This requires rebooting the partition with service authority. To avoid the resource allocation issues, it is recommended that the service processor menus be used to update the firmware.

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

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

     Enter the commands:

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

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

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

If the 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 Managed System state changes to READY.  The update of the firmware is complete.

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 SUSE 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).......3K050715
        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).......3K050715

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