Updating Flex System Manager (FSM) from version 1.1.0 - IBM Flex

Resolving The Problem

Source

RETAIN tip: H206132

Symptom

When updating Flex System Manager (FSM) from version 1.1.0 of the software stack to any subsequent supported version, if a discovery task was not run on the FSM node firmware elements, the FSM Unified Extensible Firmware Interface (UEFI) and Integrated Management Module (IMM) levels are not updated. The update process indicates that it has completed successfully.

Inspect the FSM inventory after the update process completes by selecting the FSM from the graphical view of the FSM management interface, then select Actions, then select Inventory, then select View and Collect Inventory. The inventory detail is shown in the bottom half of the user interface. An example is shown in the following file:

If the line items for IMM2 and UEFI are at build number 28Q for IMM2 or build number 14A for UEFI, the update process failed to update the IMM and UEFI.

Affected configurations

The system may be any of the following IBM servers:

• Flex System Manager Node, type 7955, any model
• Flex System Manager Node, type 8731, any model
• Flex System Manager Node, type 8734, any model

This tip is not software specific.

This tip is not option specific.

The following system firmware level(s) are affected:

• FSM version 1.1.0
  

Solution

This problem was fixed in v1.1.0.1 of the FSM firmware.

Note: The workaround (documented below) is only required when a user is updating from FSM firmware v1.1.0.

Workaround

To avoid this issue, initiate the inventory process prior to running the update process. To run inventory, select the FSM from the graphical view of the chassis, select Actions, select Inventory, then select Collect Inventory. After this process completes, the update can be run.

If the above is not completed prior to running the update process, a force-update of the FSM firmware is required. The force-update process must be executed from the FSM Command Line Interface (CLI).

1. Log in to the FSM CLI via an SSH session using your management account name such as USERID.
   
2. From the CLI run the command to force re-applying the FSM update v1.1.0.1:
   
   

   smcli installupd -v -F -i 10.3.0.1 -u fsm_appliance_update_1.1.0.1

3. While the FSM update is being re-applied you will see messages similar to:
   
   

   ATKUPD725I The update install task has started. ATKUPD631I The update installation staging first needs to download 2 updates, the download is being launched.

4. Restart the FSM for the firmware updates to take effect using the following command:
   
   

   smshutdown -r -t now