
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.
The following table lists the components that are supported by the Firmware Update feature.
NOTE: When multiple firmware updates are applied through out-of-band methods or using the LC Web interface,
the updates are ordered in the most efficient possible manner to reduce unnecessary restarting of a system.
Firmware Update – Supported Components
Component Name Firmware
Rollback
Supported? (Yes
or No)
Out-of-band—
System Restart
Required?
In-band—System
Restart Required?
Lifecycle
Controller GUI—
Restart Required?
Diagnostics No No No No
OS Driver Pack No No No No
Lifecycle
Controller
No No No Yes
BIOS Yes Yes Yes Yes
RAID Controller Yes Yes Yes Yes
Backplanes Yes Yes Yes Yes
Enclosures Yes Yes No Yes
NIC Yes Yes Yes Yes
iDRAC Yes **No *No *No
Power Supply
Unit
Yes Yes Yes Yes
CPLD No Yes Yes Yes
FC Cards Yes Yes Yes Yes
PCIe SSD Yes Yes Yes Yes
* 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 iDRAC7 is updated from version 1.30.30 or later, a system restart is not necessary. However, firmware versions
of iDRAC7 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.
60
Commentaires sur ces manuels