Chassis Management Module fails firmware update - IBM Flex System



Source

RETAIN tip: H207095

Symptom

A firmware update fails on an IBM Flex System Chassis Management Module (CMM) running firmware earlier than 2PET10K with one of the following errors:

  Timeout occurred while retrieving firmware file/firmware update fails

The Standby CMM posts the following in the Primary CMM Event log:

  Standby CMM is offline.

The CMM shows less than 250 megabytes (MB) Total Space, fails the firmware update, and displays the error:

  Timeout occurred while retrieving firmware file

The CMM's total space can be seen from the following path:

  CMM Web GUI -->Mgt Module Management --> File Management

Affected configurations

The system may be any of the following IBM servers:

  • Flex System Enterprise Chassis, type 7893, any model
  • Flex System Enterprise Chassis, type 8721, any model
  • Flex System Enterprise Chassis, type 8724, any model

The system is configured with one or more of the following IBM Options:

  • Flex System Chassis Management Module (CMM), Option part number 68Y7029, replacement part number (CRU) 68Y7032

This tip is not software specific.

Solution

This issue only affects CMMs running firmware prior to Build ID: 2PET10K. Although it is safe to run this utility, the utility provided below will not install on CMMs running firmware Build ID: 2PET10Q or later because it is not needed.

If the CMM is running firmware prior to Build ID: 2PET10K, follow the procedure below:

Update the CMM with the emergency fix utility and then flash the CMM firmware to the desired level.

Note: The utility should be run individually on each CMM. If a secondary CMM is installed, it will have to become primary and the utility should be run on that CMM in order for it to take effect.

  1. Download the following file: ftp://ftp.software.ibm.com/systems/support/system_x/cogent_27364_mefs_emergency.uxp
  2. Upload the file downloaded in step 1 to a remote location.
  3. Close all web sessions to the CMM.
  4. Log in to the CMM Command Line Interface (CLI) with an account that has Supervisor authority.
  5. Use the update command to run the file from step 1.
    For example:
      update -u https://<host ipv4 address>[/<path>]/cogent_27364_mefs_emergency.uxp -T MM[<CMM unit number>]

    where x = the MM bay of the primary CMM (1 or 2)


    Note: Depending on the CMM security setting, the user can choose from many protocols to complete the update. For more information, enter 'update -help' for the syntax and supported protocols.
  6. Restart the CMM:
      reset -T MM[<CMM unit number>]

    where x = the MM bay of the primary CMM (1 or 2)
  7. Update the CMM firmware to the desired firmware level using the normal procedure.

Additional Information

This issue is caused by a mis-configured memory partition in the Chassis Management Module (CMM).

It is recommended to run the fix utility before updating CMM firmware for the first time.

If there are two (2) CMMs present in the chassis, run the utility on each before updating CMM firmware.

It is possible that partition 2 (containing the main CMM firmware '.uxp' file) is full. The CMM has a built-in partition cleaner that runs every few minutes. It may experience firmware failures if the user executes multiple firmware updates back to back right after the utility is run.

Allow 30 minutes to an hour before attempting to flash another firmware version.

For additional information on using the update command, refer to the CMM CLI Guide that comes with the CMM firmware update package.


Applicable countries and regions

 


Document id:  MIGR-5091977
Last modified:  2014-02-10
Copyright © 2014 IBM Corporation