Getting server firmware fixes through AIX or Linux when you are unable to start the operating system or server

Learn how to apply server firmware fixes through AIX® or Linux® when you are unable to start the operating system or server.

The server firmware is the part of the Licensed Internal Code that enables hardware, such as the service processor.
Note: Installing the server firmware fixes through the operating system is a disruptive (nonconcurrent) process.

Perform tasks 1 through 4.

Task 1. Determine the existing level of firmware

Use this procedure to determine the existing level of server firmware when you are unable to start the AIX or Linux operating system or server.
  1. Insert the eServer™ Standalone Diagnostics Version xxxxx CD into the CD drive on the server and boot the CD. If you need more information about how to boot the Standalone Diagnostics Version xxxxx CD, see Running the eServer stand-alone diagnostics from CD.
  2. Initialize the terminal type, if requested.
  3. On the function selection screen, select Tasks and Service Aids.
  4. On the task selection screen, scroll to the bottom of the list of options, and select Update and Manage Flash
    Note: When the lsmcode command is run on a 7037-A50 or 7047-185 system, the temporary or permanent side of the flash might report _UNKNOWN_ for the firmware level. This occurs because there is only one level of base motherboard controller firmware. The level is _UNKNOWN_ when it is not included with the system firmware.

    When you install new firmware, it is installed onto the temporary side by default. This new firmware level includes a new level of base motherboard controller code, and will cause _UNKNOWN_ to be reported for the permanent side. This is not a problem; it indicates that the firmware levels in the flash are not a combination that is included from the factory.

    To update the firmware so that _UNKNOWN_ is not reported, perform the following steps:
    1. Perform a commit operation using the appropriate operating system command.
    2. After the commit operation is complete, restart the system.
    3. When the system has restarted and the operating system is running, rerun the lsmcode command. Both the T and P should report a level (such as AT206_061) instead of _UNKNOWN_.
  5. Record the information for the current temporary system firmware image.

Task 2. Obtain the Microcode Update Files & Discovery Tool CD

You will need to obtain the Microcode Update Files & Discovery Tool CD. Contact service and support for details.
  1. From a computer or server with an Internet connection, go to the Fix Central Web site at http://www.ibm.com/eserver/support/fixes/.
  2. Select the appropriate family in the Product family list.
  3. Select Hardware microcode and firmware in the Product list.
  4. Click Continue.
  5. From the Microcode downloads Web site, choose from the following options:
    • If there are tabs at the top of the page, continue with step 6.
    • If there is a drop-down list at the top of the page, continue with step 7.
  6. Perform the following steps:
    1. Select CD image in the Microcode downloads tab at the top of the window. The Microcode update files & discovery tool CD image page is displayed.
    2. Select Microcode Update Files & Discovery Tool CD image. The License agreement is displayed.
    3. Click I have read and understood this license agreement and I agree to abide by its terms.
    4. Follow the on-screen prompts to download the image.
    5. Follow the instructions for your CD program to create the CD.
    6. After you have the CD, continue with Task 3. Apply the server firmware fix .
  7. Perform the following steps:
    1. Follow the on-screen prompts to download the image.
    2. Follow the instructions for your CD program to create the CD.
    3. After you have the CD, continue with Task 3. Apply the server firmware fix.

Task 3. Apply the server firmware fix

  1. Insert the Microcode Update Files & Discovery Tool CD into the media device, select Validate and Update System Firmware, and press Enter.
    Note: If you receive a message stating: This partition does not have the authority to perform the requested function, see Message regarding a server that was previously managed by an HMC.
  2. Select the appropriate device and press Enter.
  3. Press F4. A list of firmware fix image files is displayed.
  4. Select the image file that is similar to /microcode/SqnP5/01SF2xx_yyy_zzz.img.
  5. Press F7. The server firmware level that you selected will be installed on the temporary side.

Task 4. Verify that the fix installed correctly

Use this procedure to verify the fix installed correctly.
  1. Choose from the following options:
    • To use the AIX or Linux command line (the operating system must be running and the diagnostics must be available), continue with the next step.
    • To use the ASMI, view the level of server firmware displayed in the upper-right corner below the copyright statement on the ASMI Welcome pane; for example, SF220_006. If the level of server firmware displayed is not the level that you installed, see Failed verification that the fix installed successfully.
  2. Enter the following at a command line:
    lsmcode
    The existing levels of server firmware are displayed. For example, you might see output similar to the following:
    The current permanent system firmware image is SF220_005.
    The current temporary system firmware image is SF220_006.
    The system is currently booted from the temporary image.
    Note:
    1. The permanent level is also known as the backup level.
    2. The temporary level is also known as the installed level.
    3. The system was booted from the temporary side, so at this time the temporary level is also the activated level.
  3. If you are using a 7037-A50 or 7047-185 system, note the following:
    Note: When the lsmcode command is run on a 7037-A50 or 7047-185 system, the temporary or permanent side of the flash might report _UNKNOWN_ for the firmware level. This occurs because there is only one level of base motherboard controller firmware. The level is _UNKNOWN_ when it is not included with the system firmware.

    When you install new firmware, it is installed onto the temporary side by default. This new firmware level includes a new level of base motherboard controller code, and will cause _UNKNOWN_ to be reported for the permanent side. This is not a problem; it indicates that the firmware levels in the flash are not a combination that is included from the factory.

    To update the firmware so that _UNKNOWN_ is not reported, perform the following steps:
    1. Perform a commit operation using the appropriate operating system command.
    2. After the commit operation is complete, restart the system.
    3. When the system has restarted and the operating system is running, rerun the lsmcode command. Both the T and P should report a level (such as AT206_061) instead of _UNKNOWN_.
  4. Verify that the level of server firmware displayed is the level that you installed.
  5. If the level of server firmware displayed is not the level that you installed, see Failed verification that the fix installed successfully.

Send feedback | Rate this page