firmware update examplep640

pSeries 640 System and Service Processor Firmware Update

Applies to :  pSeries 640 Model B80 (7026-B80)

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  pSeries 640 Model B80 (7026-B80) Servers only.  Do not use on any other systems.

The firmware levels contained in this update are:

• System FW:  NAN04194
• SvP FW:  sc040624

 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 0.9 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:  System Firmware Update Descriptions and History
NAN04194	Added support for AIX 5.3. Added support for PCI-X Dual Channel Ultra 320 SCSI RAID Adapter (FC 5703). 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.
NAN03276	Corrected boot failure from CD-ROM after SMS Multiboot menus are accessed.  This only affects systems equipped with SSA disks.
NAN03156	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. Corrected boot failure with 'Default Catch' message displayed on console when booting from tape media containing large boot image. Enhancements to SMS network adapter menus to resolve various configuration issues and ping test failures. Enhancements to prevent potential ping and NIM boot failures on SP and Cluster attached servers.
NAN03029	Corrected boot failure with checkpoint E1F6 displayed after bootlist is set via AIX and more than 5 devices are specified. Corrected missing devices in SMS bootlist when bootlist set via AIX. Parameter change to limit bootlist entries set via AIX to 5.
NAN02254	Corrected ping failure with auto speed selected for integrated adapter and IBM 10/100 Ethernet PCI Adapter (FC 2968, Type 9-P). Corrected problem booting from DVD RAM Drive. (FC 2623 and 2627). Corrected auto configuration,  ping and NIM failures on ethernet adapters attached to a switch or router with Spanning Tree Algorithm enabled. Corrected problem causing intermittent configuration errors with 64bit/66Mhz PCI ATM 155 Adapter (FC 4953 Type A-C and FC 4957 Type A-D). Correction for boot failure when boot image is located beyond the first 4GB of storage on a disk drive. Made power supply VPD information visible.
NAN02066	Added support for new device id/vendor id for IBM Universal 4-Port 10/100 Ethernet Adapter (FC4961, Type A-E). Correction for handling xoff character transmitted to ASCII terminal during boot. Failure symptom:  terminal would stop displaying data during boot. Removed gateway IP address limitation for ping when client and server are on same subnet - gateway address no longer has to be specified as 0.0.0.0. Correction to allow return to SMS Utilities menu after a ping on any token ring adapter.
NAN02035	Added support for IBM 10/100 Mbps Ethernet PCI Adapter II (FC 4962, Type A-F).  Corrects interruption of NIM boot (via TFTP packet transfer) that was caused by non-TFTP packet transfers.  Failure symptoms vary: may hang at E1F7 or 611, trouble booting in maintenance mode.  Changed SMS "ping" routine: If "Server IP Address" is set to "0.0.0.0", only ping "Gateway IP Address". If "Server IP Address" is not set to "0.0.0.0", ping "Server IP Address".
NAN01271	Added support for IBM Gigabit Fibre Channel Adapter for PCI Bus. Added support for IBM Gigabit Fibre Channel Adapter for 64-bit PCI Bus. Added support for SAN boot. Corrected sysplanar0 error that resulted in checkstop 4B2758C4.
NAN01252	Added support for 450MHz processor (FC 4366).
NAN01184	Added support for the IBM PCI Dual Channel Ultra-3 SCSI Adapter (FC 6203, Type 4-Y).  Added support for the IBM 10/100/1000 Base-T Ethernet PCI Adapter (UTP) (FC 2975, Type A-A)  Added support for the IBM Cryptographic Accelerator Adapter (FC 4960, Type 6-J).  Corrected incorrect physical location codes in firmware.
NAN00252	Original (GA) level.

 

Table 2.2: Service Processor Firmware Update Descriptions and History
sc040624	Corrected problem with system time changes during Daylight Savings Time transitions in locales where DST is not observed.
sc031003	Corrected intermittent failure to generate AIX dump and/or display of error 40110001 when Op Panel reset button is depressed.
sc020308	Correction for false occurrence of CPU error codes 4B2xxx51 and 4B2xxx52.
sc020115	Correction to allow Unattended Start Mode to work when A/C power is switched to D/C power (switching to UPS power).
sc010928	Companion level to System firmware level NAN01271.
sc010831	Added support for 450MHz processor (FC 4366).
sc010702	Corrected FRU callout detail for error code 4BA00000.
sc000908	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.

The System and Service Processor (SvP) firmware are combined into a single file. This allows all the firmware to be updated together and assures they are companion levels.

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.

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.

Avoid Potential Firmware Update Corruption

Some firmware corruptions are recoverable in the field, and repeating the update will usually correct the problem.  If the second update attempt fails, replace the EPROMs or I/O planar containing the corrupted firmware module.  Here are some tips to help avoid the need for such recoveries.

Never power OFF the server during the firmware update process!
The update will be incomplete and will fail.  Depending on where in the update process the power was lost, a recovery attempt will often succeed.  One recovery attempt is worthwhile.

Replacement Parts May Require Updating

When EPROMs or I/O planars are replaced, the system and service processor firmware must be checked to ensure they are at the latest levels.

Table 3.1:  Combined 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	cb040194.img	1604074	40421	NAN04194	sc040624
December 2003	cb03276.img	1604058	44097	NAN03276	sc031003
August 2003	cb03156.img	1604014	62649	NAN03156	sc020308
April 2003	cb03029.img	1604014	43492	NAN03029	sc020308
November 2002	cb02254.img	1604014	10414	NAN02254	sc020308
March 2002	cb02066.img	1604014	57469	NAN02066	sc020308
March 2002	cb02035.img	1603986	38749	NAN02035	sc020115
October 2001	cb01271.img	1603690	37955	NAN01271	sc010928
September 2001	cb01252.img	1604614	61922	NAN01252	sc010831
July 2001	cb01184.img	1603410	11128	NAN01184	sc010702
Original (GA)	cb00252.img	1601422	17587	NAN00252	sc000908

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

Level identifiers for the Service Processor FW use the 8-digit Gregorian date code method in terms of year, month, and day (such as 040624 for sc040624 level).  The System FW uses the 5-digit Julian date code method in terms of day number in a year (such as 04194 for NAN04194 level -- the 194th day of 2004 or July 12, 2004).

---

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.

Two methods for reading the firmware levels are described below.

• If the operating system is running, use the AIX command-line method.  Continue to .
• If the operating system is not running, use the SMS Utilities method.  Skip to .

4.1  Using AIX to Read Currently Installed Firmware Levels

To check the firmware levels

    Enter:
        lscfg  -vp |  grep  alterable

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

   ROM Level.(alterable).......sc020308    <== Service Processor FW level
   ROM Level.(alterable).......NAN03029    <== System FW Level

The ROM Level lines list the levels of the currently installed firmware.  In the above example, the current System firmware level is NAN03029, and the current Service Processor firmware level is sc020308.

If the right-most five characters (date) of the current System FW level are earlier than 04194 you should consider installing the update.

If the right-most six characters (date) of the current Service Processor FW level are earlier than 040624, you should consider installing the update.

 If you find the firmware levels are not correct companions, or that they must be updated, proceed to .   If the firmware levels are correct companions and no update is needed, installation is complete.

4.2  Using SMS Utilities to Read Currently Installed Firmware Levels

The System Management Services (SMS) Utilities may be accessed in two ways.

• If using an ASCII terminal, continue to .
• If using a graphics console, skip to .

Instructions for these two methods are slightly different, so be sure to choose the correct instructions for your environment.

4.2.1  If Using an ASCII Terminal

Power on or shutdown and restart the server.  At checkpoint E1F1 on the operator panel,  watch the terminal for the time to press the "1" key.  An indicator appears on the terminal as each system component is self-tested.  When the word "keyboard" appears, quickly press the "1" key. The SMS menu will be displayed after startup testing has completed.

The current System and Service Processor firmware levels can be found under the "Display Configuration" selection on the SMS main menu.  The System firmware level is shown under "System Information" on the line "Firmware Level", and the Service Processor firmware level is shown under "Service Processor Information" on the line "ROM Level."

When you have read the current firmware levels, you may exit SMS as directed on the menu screens.

If the right-most five characters (date) of the current System FW level are earlier than 04194 you should consider installing the update.

If the right-most six characters (date) of the current Service Processor FW level are earlier than 040624, you should consider installing the update.

If you find the firmware levels are not correct companions, or that they must be updated, proceed to .   If the firmware levels are correct companions and no update is needed, installation is complete.

4.2.2  If Using a Graphics Console

Power on or shutdown and restart the server.  At checkpoint E1F1 on the operator panel, watch the console for the time to press the "F1" key.   An indicator appears on the console as each system component is self-tested. When the keyboard icon appears, quickly press the "F1" key.  The SMS menu will appear when all the component tests have completed.

The current System and Service Processor firmware levels can be found under the "Config" selection on the SMS main menu.  The System firmware level is shown under "System Information" on the line "Firmware Level", and the Service Processor firmware level is shown under "Service Processor Information" on the line "ROM Level."

When you have read the current FW levels, you may exit SMS as directed on the menu screens.

If the right-most five characters (date) of the current System FW level are earlier than 04194 you should consider installing the update.

If the right-most six characters (date) of the current Service Processor FW level are earlier than 040624, you should consider installing the update.

If you find the firmware levels are not correct companions, or that they must be updated, proceed to .   If the firmware levels are correct companions 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 formats, are located at the web site

       

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

In the table for System/Service Processor Combined Microcode, scroll down to the entry for 7026-B80.

The download choices at that entry are:

• Description        (Instructions document)
• AIX Format       (For downloading to an AIX system or workstation)
• DOS Format      (For downloading to a Windows workstation)

You will want a copy of the description (instructions document) and one of the format choices. You may transfer files to the target server in one of several ways.

• 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 system.

Detailed download/unpacking instructions follow for each of the downloading preferences.

• If using an AIX system for downloading, continue to .
• If using a Windows workstation for downloading, skip to .

5.1.1 Downloading the AIX Format File

Use this method to download to an AIX system.

                    Note:  In the instructions that follow are specific AIX commands.
                                AIX commands are CASE (lower and upper) SENSITIVE, and must be
                                entered exactly as shown, including the filenames.

  a) Provide a directory on an AIX system to receive the AIX format file.

      Enter:
        mkdir  /tmp/fwupdate

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

   b) Transfer the AIX format file to the /tmp/fwupdate directory (using "Save as ...").
       You'll see the filename is 7026B80F.BIN

   c) Unpack the file by executing the instructions below.

      Enter the commands:

        cd   /tmp/fwupdate
        chmod   +x   7026B80F.BIN
        ./7026B80F.BIN

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

      These files will be added to  /tmp/fwupdate.

          cb04194.img
          ReadMe.TXT

• If the AIX format file was transferred directly to the target server, proceed to .
• If the AIX format file was transferred to an intermediate AIX system, continue to .

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  cb04194.img
        quit

Proceed to .
 

5.1.2 Downloading the DOS Format File

Use this method to download to a Windows workstation.

   a) Prepare a directory for receiving the DOS format file.
       This directory can be in any partition with 6MB 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 format file to the [path]\fwupdate directory (using "Save as ...").
       You'll see the filename is 7026B80F.EXE

   c) Unpack the file by executing the instructions below.
       You will need the password from the license agreement.

       Enter the commands:

         cd  [path]\fwupdate
         7026B80F

These files will be added to the fwupdate subdirectory:

      cb04194.img
      26B80_B1.EXE
      26B80_B2.EXE
      readme.txt

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

5.1.2.1 The FTP Transfer Method

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

On the Windows workstation,

     Enter the commands:

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

        bin
        lcd  [path]\fwupdate
        mkdir   /tmp/fwupdate
        cd   /tmp/fwupdate
        put  cb04194.img
        quit

Proceed to .

5.1.2.2 Diskettes for Intermediate AIX System

Two 2MB (HD) new or freshly formatted DOS diskettes are required.

a) With the first diskette loaded in the drive,

     Enter the commands:

          cd  [path]\fwupdate
         26B80_B1

      Label this diskette,

        "Volume 1:  AIX Backup: Combined System (NAN04194) and SvP (sc040624) FW
                             for IBM pSeries 640 (7026-B80)"

b) With the second diskette loaded in the drive,

     Enter the commands:

          cd  [path]\fwupdate
         26B80_B2

      Label this diskette,

        "Volume 2:  AIX Backup: Combined System (NAN04194) and SvP (sc040624) FW
                           for IBM pSeries 640 (7026-B80)"

            Note:  Any diskette labeled: 'AIX Backup: . . . .' is in a format that can be used
                            directly with a computer running AIX as its operating system.  This
                            diskette cannot be read using PC tools or command line operations.

  c)  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 intermediate AIX system, put the AIX backup diskette labeled,

              "Volume 1: AIX Backup: Combined  System (NAN04194) and SvP (sc040624) FW
                                                        for 7026-B80"

          When prompted for volume 2,

           In the drive of the intermediate system, put the AIX backup diskette labeled,

                  "Volume 2: AIX Backup: Combined  System (NAN04194) and SvP (sc040624) FW
                                                            for 7026-B80"

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

     d)  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  cb04194.img
             quit

Proceed to .

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, cb04194.img, to the /tmp/fwupdate directory on the remote system.  Proceed to .

---

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

Note:  Checksums can be used to verify files have not been corrupted or altered during transmission.

            At the AIX command line, enter:

            sum cb04194.img

           This command will produce the following output:

                     40421  1567  cb04194.img

           The checksum is ------>  40421
 

6.1  Using the AIX Command-Line Method

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.

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

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

  Enter the commands:

        cd  /usr/lpp/diagnostics/bin
        ./update_flash  -f  /tmp/fwupdate/cb04194.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 up to ten minutes, depending on the configuration of the target server.

While the update is in progress, you will see "Rebooting  . . ." on the display for as long as three minutes.

The firmware update is complete.  You will want to verify the update as described in

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

6.2  Verifying the Update

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

    Enter:
        lscfg  -vp |  grep  alterable

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

  ROM Level.(alterable).......sc040624    <== SvP FW level
  ROM Level.(alterable).......NAN04194    <== System FW level

The ROM Level lines list the level numbers of the newly installed System and Service Processor firmware.  For System FW, the level number should now be NAN04194.  For Service Processor FW, the level should now be sc040624.
 

6.3  Archiving the Update Files

In the event it becomes necessary to restore the server to a certain firmware level, it is suggested you identify and archive the materials for each update you install.

If the download process produced diskettes, label and store them in a safe place.

If the download process produced files, archive and identify the files for convenient retrieval.

---

End of Installation Instructions