Users Guide

Table Of Contents
To clear the schedule details:
racadm AutoUpdateScheduler clear
Updating device firmware using RACADM
To update device firmware using RACADM, use the update subcommand. For more information, see the iDRAC RACADM CLI
Guide available at https://www.dell.com/idracmanuals.
Examples:
Upload the update file from a remote HTTP share:
racadm update -f <updatefile> -u admin -p mypass -l http://1.2.3.4/share
Upload the update file from a remote HTTPS share:
racadm update -f <updatefile> -u admin -p mypass -l https://1.2.3.4/share
To generate a comparison report using an update repository:
racadm update f catalog.xml l //192.168.1.1 u test p passwd --verifycatalog
To perform all applicable updates from an update repository using myfile.xml as a catalog file and perform a graceful
reboot:
racadm update f myfile.xml b “graceful l //192.168.1.1 –u test p passwd
To perform all applicable updates from an FTP update repository using Catalog.xml as a catalog file:
racadm update f Catalog.xml t FTP e 192.168.1.20/Repository/Catalog
Updating firmware using CMC web interface
You can update iDRAC firmware for blade servers using the CMC Web interface.
To update iDRAC firmware using the CMC Web interface:
1. Log in to CMC Web interface.
2. Go to iDRAC Settings > Settings > CMC.
The Deploy iDRAC page is displayed.
3. Click Launch iDRAC Web interface and perform iDRAC Firmware Update.
Updating firmware using DUP
Before you update firmware using Dell Update Package (DUP), make sure to:
Install and enable the IPMI and managed system drivers.
Enable and start the Windows Management Instrumentation (WMI) service if your system is running Windows operating
system,
NOTE:
While updating the iDRAC firmware using the DUP utility in Linux, if you see error messages such as usb 5-2:
device descriptor read/64, error -71 displayed on the console, ignore them.
If the system has ESX hypervisor installed, then for the DUP file to run, make sure that the "usbarbitrator" service is stopped
using command: service usbarbitrator stop
Some versions of DUPs are constructed in ways that conflict with each other. This happens over time as new
versions of the software are created. A newer version of software may drop support for legacy devices. Support for
new devices may be added. Consider, for example, the two DUPs Network_Firmware_NDT09_WN64_21.60.5.EXE and
Network_Firmware_8J1P7_WN64_21.60.27.50.EXE. The devices supported by these DUPs fit into three groups.
Group A are legacy devices supported only by NDT09.
Group B are devices supported by both NDT09 and 8J1P7.
Group C are new devices supported only by 8J1P7.
80
Setting up managed system