Troubleshooting
Problem
During an IBM Flex System Manager (FSM) update, Unified Extensible Firmware Interface (UEFI), Dynamic System Analysis (DSA) Preboot or Integrated Management Module (IMM) firmware updates fail. Firmware update failure can be determined if the FSM updatetask completes with an 'Update completed with Errors' message and the Task Job Log contains messages similar to the following: ATKUPD767W The installation of update "ibm_fw_dsa_dsytaa4us_anyos_32-64" was not successful for system "FSM_ibm 8731AC1FBI0540." DNZUPX059E An error occurred while installing update "ibm_fw_dsa_dsytaa4us_anyos_32-64" on system "FSM_ibm 8731AC1 FBI0540." Check the error log for more details. Error: ATKUPD767W The installation of update "ibm_fw_dsa_dsytaa4us_anyos_32-64" was not successful for system "FSM_ibm 8731AC1 FBI0540."
Resolving The Problem
Source
RETAIN tip: H207193
Symptom
During an IBM Flex System Manager (FSM) update, Unified Extensible Firmware Interface (UEFI), Dynamic System Analysis (DSA) Preboot or Integrated Management Module (IMM) firmware updates fail.
Firmware update failure can be determined if the FSM update task completes with an 'Update completed with Errors' message and the Task Job Log contains messages similar to the following:
| ATKUPD767W The installation of
update "ibm_fw_dsa_dsytaa4us_anyos_32-64" was not successful for
system "FSM_ibm 8731AC1 FBI0540." DNZUPX059E An error occurred while installing update "ibm_fw_dsa_dsytaa4us_anyos_32-64" on system "FSM_ibm 8731AC1 FBI0540." Check the error log for more details. Error: ATKUPD767W The installation of update "ibm_fw_dsa_dsytaa4us_anyos_32-64" was not successful for system "FSM_ibm 8731AC1 FBI0540." |
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:
- IMM versions 1.34 and 1.60
Workaround
Restart the IMM and, if necessary, the FSM system. Then, run the firmware update again.
- Restart the IMM. The IMM can be reset from the Chassis
Management Module (CMM) by the Action,
Remote Access, Launch Web Browser on the Chassis
Server, logging in to the CMM, right-clicking on the FSM
System and selecting Restart System Mgmt
Processor.
- Force the FSM update to run again from the FSM Command Line
Interface (CLI) by the command:
smcli installupd -v -i <IP-address> -u <update-name> -F
where:
- <IP-address> is the Internet Protocol (IP) address of the FSM. The internal IP address of 10.3.0.1 can be used for the FSM.
- <update-name> is the update name of the FSM update, in this case it will be 'fsm_appliance_update_1.1.0.1.' Users can list the update names by running 'smcli lsupd.'
If firmware fails to update, restart the FSM and run the FSM update again.
- Restart the FSM by clicking Home, then the
Administration tab and selecting
Shutdown or Restart Flex System
Manager.
- After FSM restarts, force the FSM update to run again as
described in step 2 previously.
Additional information
This behavior may occur in any case where the system is being updated from releases previous to GA2.
This intermittent error occurs infrequently. It is caused by the existing code, which must run to accomplish the update, and the existing code only can be replaced by completing the update process.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
16 May 2022
UID
ibm1MIGR-5092151