Dell PowerEdge M1000e Chassis Management Controller Firmware Version 5.1 User’s Guide

You can update the server components firmware using the File method or the Network Share method.

You can install the next version of the firmware image for selected components or devices across one or more servers. The firmware image is available within the Lifecycle Controller for a rollback operation.

It is recommended to clear the job queue before initializing a server component firmware update. A list of all jobs on the server(s) is available on the Lifecycle Controller Jobs page. This page enables deletion of single or multiple jobs or purging of all jobs on the server. See the Troubleshooting section, "Managing Lifecycle Controller jobs on a remote system" .

BIOS updates are specific to the model of the server. The selection logic is based on this behavior. Sometimes, even though a single Network Interface Controller (NIC) device is selected for firmware update on a server, the update may get applied to all the NIC devices on the server. This behavior is inherent in the lifecycle controller functionality and particularly the programming contained with the Dell Update Package (DUP). Currently, Dell Update Packages (DUP) that are less than 48MB in size are supported.

If the update file image size is greater, the job status indicates that the download has failed. If multiple server component updates are attempted on a server, the combined size of all the firmware update files may also exceed 48MB. In such a case, one of the component updates fails as its update file is truncated.

To update multiple components on a server, it is recommended to update the Lifecycle Controller and 32-Bit Diagnostics components together first. The other components can then be updated together.

Firmware Update – Supported Components

* Indicates that though a system restart is not required, iDRAC must be restarted to apply the updates. iDRAC communication and monitoring will temporarily be interrupted.

** When iDRAC is updated from version 1.30.30 or later, a system restart is not necessary. However, firmware versions of iDRAC earlier than 1.30.30 require a system restart when applied using the out-of-band interfaces. 

All Lifecycle Controller updates are scheduled for immediate execution. However, the system services can delay this execution sometimes. In such situations, the update fails as a result of the remote share that is hosted by the CMC being no longer available.

All the LC component updates become effective immediately. However, in some cases, system services can delay the time taken for becoming effective. In such cases, the update is unsuccessful because of the remote share that is hosted by CMC not being available anymore.