Users Guide

If the update le 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 rmware update les may also exceed 85 MB. In such a case, one of the component
updates fails as its update le is truncated. To update multiple components on a server, it is recommended to update the Lifecycle
Controller and 32-Bit Diagnostics components together rst. These do not require a server reboot and are relatively quick to complete. The
other components can then be updated together.
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.
Upgrading server component rmware from le using CMC web interface
To upgrade the server components rmware version to the next version using the Update from File method:
1 In the CMC Web interface, in the system tree, go to Server Overview and then click Update > Server Component Update.
The Server Component Update page is displayed.
2 In the Choose Update Type section, select Update from File. For more information, see Choosing Server Component Firmware
Update Type
3 In the Component/Device Update Filter section, lter the component or device (optional). For more information see
CMC_Stmp_Filtering Components for Firmware Updates
4 In the Update column, select the checkbox(es) for the component or device for which you want to update the rmware to the next
version. Use the CRTL key shortcut to select a type of component or device for update across all the applicable servers. Pressing and
holding the CRTL key highlights all the components in yellow. While the CRTL key is pressed down, select the required component or
device by enabling the associated check box in the Update column.
A second table is displayed that lists the selected type of component or device and a selector for the rmware image le. For each
type of component, one selector for the rmware image le is displayed.
Few devices such as Network Interface Controllers (NICs) and RAID Controllers contain many types and models. The update selection
logic automatically lters the relevant device type or model based on the initially selected devices. The primary reason for this
automatic ltering behavior is that only one rmware image le for the category can be specied.
NOTE
: The update size limitation of either a single DUP or combined DUPs can be ignored if the Extended Storage feature
is installed and enabled. For information on enabling extended storage, see Conguring CMC Extended Storage Card
5 Specify the rmware image le for the selected component(s) or devic(es). This is a Microsoft Windows Dell Update Package (DUP)
le.
6 Select one of the following options:
Reboot Now — Reboot immediately. The rmware update is applied immediately
On Next Reboot — Manually reboot the server at a later time. The rmware update is applied after the next reboot.
NOTE
: This step is not valid for Lifecycle Controller and 32-bit Diagnostics rmware update. A server reboot is not
required for these devices.
7 Click Update. The rmware version is updated for the selected component or device.
Server component single click update using network share
The Servers or server component update from a network share using Dell Repository Manager and Dell PowerEdge FX2/FX2s modular
chassis integration simplies the update by using customized bundle rmware, so that you can deploy faster and more easily. Update from a
network share provides exibility to update all the 12G server components at the same time with a single catalog either from a CIFS or from
a NFS.
This method provides a quick and easy way to build a custom repository for connected systems that you own using the Dell Repository
Manager and the chassis inventory le exported using the CMC Web interface. DRM enables you to create a fully customized repository
that only includes the update packages for the specic system conguration. You can also build repositories that contain updates for only
54
Updating rmware