Users Guide
NOTE:
● The Reset iDRAC function is not supported for the devices under an MCM chassis that are in a 'Proxied' onboarding
state and for updating only the drivers of the devices. For more information about onboarding states, see Onboarding
devices on page 108.
● The firmware or driver compliance status of network switches, modular IOAs, and Dell storage devices is displayed as
Unknown as these are not updatable using the Dell catalog. It is recommended to perform individual firmware or driver
updates for these devices using their respective individual Update package. To perform individual firmware or driver
updates, select a device on the All Devices page, and click View Details > Firmware/Drivers and select the individual
package option. For more information about the list of unsupported devices, refer Firmware/driver compliance baseline
reports— devices with 'Unknown' compliance status on page 163
When updating MX7000 chassis and sled belonging to the multi-chassis management (MCM) group, you must
consider the following:
● Chassis and sled firmware updates must be undertaken separately.
● The lead chassis must be updated separately as the final step after updating all the member chassis.
● Firmware can be updated for only up to 9 member chassis at a time.
● Firmware update is supported on a maximum of 43 sleds at a time irrespective of onboarding state (Managed or Proxied).
The driver updates are available only on devices discovered as 64-bit Windows servers. Before updating the drivers,
do the following:
● Be aware that the rollback of the driver updates is not supported.
● In-band driver updates are only supported on Windows with OpenSSH. Driver updates on third party SSH hosted on
Windows, such as the CygwinSSH, are not supported.
● To collect the inventory information, the Inventory Collector and Dell System Update must be available on the Windows
server. If these components are not available on the server, then initiate an inventory job and select Collect driver
inventory. The discovery job also collects driver inventory information, but only the inventory job installs the necessary
components on the server. To collect the driver inventory information, create or edit an inventory job and select the Collect
driver inventory check box. For more information, see Create an inventory job on page 118 and Edit an inventory schedule
job on page 120.
To update a device firmware and/or driver by using the baseline compliance report:
1. On the Configuration > Firmware/Driver Compliance page, select the check box corresponding to the baseline to which
the device is attached, and then click View Report in the right pane.
On the Compliance Report page, the list of devices associated with the baseline and their compliance level is displayed. For
field descriptions, see View the baseline compliance report on page 57.
2. Select the check box corresponding to the device whose firmware or driver must be updated. You can select more than one
device with similar properties.
3. Click Make Compliant.
4. In the Make Devices Complaint dialog box, you can do the following:
● Under Schedule Update, click Additional Information to view the important information and select one of the
following:
a. Update Now: To apply the firmware/driver updates immediately.
b. Schedule Later: Select to specify a date and time when the firmware and/or driver version must be updated. This
mode is recommended if you do not want to disturb your current tasks.
● Under Server Options select one of the following reboot options :
a. To reboot the server immediately after the firmware/driver update, choose Reboot server immediately and from
the dropdown menu select one of the following options:
i. Graceful Reboot without Forced Shutdown
ii. Graceful Reboot with Forced Shutdown
iii. PowerCycle for a hard reset of the device.
b. Select Stage for next server reboot to trigger the firmware/driver update when the next server reboot happens.
NOTE:
If the firmware/driver update jobs are created with the 'Stage for next server reboot' option, then the
inventory and baseline check must be executed manually after the package is installed in the remote device.
● Clear Job Queue: Select to delete all jobs (scheduled, completed, and failed) on the target device, before the update
job is initiated.
NOTE: This function is not supported for updating the drivers.
Manage the device firmware and drivers 59