Users Guide

The command requests the iDRAC configuration and generates the myfile.cfg file. If required, you
can configure the file with another name.
NOTE: Redirecting the iDRAC configuration to a file using getconfig -f is only supported
with the local and remote RACADM interfaces.
NOTE: The generated .cfg file does not contain user passwords.
The getconfig command displays all configuration properties in a group (specified by group name
and index) and all configuration properties for a user by user name.
2. Modify the configuration file using a simple text editor (optional).
NOTE: It is recommended that you edit this file with a simple text editor. The RACADM utility
uses an ASCII text parser. Any formatting confuses the parser, which may corrupt the RACADM
database.
3. Use the new configuration file to modify the target iDRAC using the command: racadm config -f
myfile.cfg
This loads the information into the other iDRAC. You can use config subcommand to synchronize
the user and password database with Server Administrator.
4. Reset the target iDRAC using the command: racadm racreset
Creating an iDRAC configuration file
The configuration file .cfg can be:
Created
Obtained from racadm getconfig -f <filename>.cfg command or racadm get -f
<filename>.cfg
Obtained from racadm getconfig -f <filename>.cfg command or racadm get -f
<filename>.cfg, and then edited
For information about the getconfig and get commands, see the iDRAC RACADM Command Line
Interface Reference Guide available at dell.com/idracmanuals.
The .cfg file is first parsed to verify that valid group and object names are present and the basic syntax
rules are being followed. Errors are flagged with the line number that detected the error, and a message
explains the problem. The entire file is parsed for correctness, and all errors are displayed. Write
commands are not transmitted to iDRAC if an error is found in the .cfg file. The user must correct all
errors before using the file to configure iDRAC. Use the -c option in the config subcommand, which
verifies the syntax and does not perform a write operation to iDRAC.
Use the following guidelines when you create a .cfg file:
If the parser encounters an indexed group, the index of the group is used as the anchor. Any
modifications to the objects within the indexed group are also associated with the index value.
For example:
If you have used the getconfig command:
[cfgUserAdmin]
# cfgUserAdminIndex=11
110