White Papers

New Features and Usability Enhancements to RACADM Commands in iDRAC7

Configuring iDRAC, System, Lifecycle Controller, NIC, and BIOS

using file operations

The legacy method of using RACADM to configure the iDRAC is commonly called the file operations:

$ racadm getconfig –f <filename>

The output file for this command contains several iDRAC settings. The same file is used for configuring

a single or a set of iDRACs using the following command:

$ racadm config –f <filename>

In the newest RACADM version, file operations has been enhanced by:

 Using get and set in place of config:

— racadm get –f <filename>

— racadm set –f <filename>

 Server profile now includes Eventfilters, NIC objects, RAID Objects, BIOS, System, Lifecycle

Controller and iDRAC objects using:

$ racadm get –f <file.xml> -t xml/csv

and

$ racadm set –f <file.xml> -t xml/csv

 The –t option creates a configuration file in XML or CSV format based on the user input, and the

file created can be exported to:

— Remote file share using the –l option for a CIFS or NFS share destination

— Local file system of a management station (Remote RACADM) or server (Local RACADM)

Summary

RACADM has transformed to a standardized, user-friendly interface. It is becoming a comprehensive

CLI as Dell continues to provide new and unique features found only in the Dell PowerEdge server line

with iDRAC7 and Lifecycle Controller.

In the future, Dell will continue improving the RACADM CLI to make it compatible with all Dell

enterprise products, and further improve user experience in the overall configuration of server

deployment.

References

For more information on iDRAC7 version 1.30.30, visit Support for Integrated Dell Remote Access

Controller 7 Version 1.30.30 on Dell.com.

For additional info on iDRAC, visit Dell Remote Access Controller on Dell.com.