Users Guide

3. Modify the conguration le using a plain-text editor (optional). Any special formatting characters in the conguration le may
corrupt the RACADM database.
4. Use the newly created conguration le to modify a target CMC. At the command prompt, type:
racadm config -f myfile.cfg
5. Reset the target CMC that was congured. At the command prompt, type:
racadm reset
The getconfig -f myfile.cfg subcommand requests the CMC conguration for the CMC and generates the myle.cfg
le. If required, you can rename the le or save it to a dierent location.
You can run the getconfig command to perform the following actions:
• Display all conguration properties in a group (specied by group name and index).
• Display all conguration properties for a user by user name.
The config subcommand loads the information into other CMCs. The Server Administrator uses the config command to
synchronize the user and password database.
Parsing rules
• Lines that start with a hash character (#) are treated as comments.
A comment line must start in column one. A "#" character in any other column is treated as a # character.
Some modem parameters may include # characters in their strings. An escape character is not required. You may want to
generate a .cfg from a racadm getconfig -f <filename> .cfg command, and then perform a racadm config -f
<filename> .cfg command to a dierent CMC, without adding escape characters.
For example:
#
# This is a comment
[cfgUserAdmin]
cfgUserAdminPageModemInitString= <Modem init # not
a comment>
• All group entries must be surrounded by open- and close-brackets ([ and ]).
The starting [ character that denotes a group name must be in column one. This group name must be specied before any of the
objects in that group. Objects that do not include an associated group name generate an error. The conguration data is
organized into groups as dened in the database property chapter of the RACADM Command Line Reference Guide for iDRAC
and CMC. The following example displays a group name, object, and the object’s property value:
[cfgLanNetworking] -{group name}
cfgNicIpAddress=143.154.133.121 {object name}
{object value}
• All parameters are specied as "object=value" pairs with no white space between the object, =, or value. White spaces that are
included after the value are ignored. A white space inside a value string remains unmodied. Any character to the right of the =
(for example, a second =, a #, [, ], and so on) is taken as-is. These characters are valid modem chat script characters.
[cfgLanNetworking] -{group name}
cfgNicIpAddress=143.154.133.121 {object value}
• The .cfg parser ignores an index object entry.
You cannot specify which index is used. If the index already exists, it is either used or the new entry is created in the rst
available index for that group.
The racadm getconfig -f <filename>.cfg command places a comment in front of index objects, allowing you to see
the included comments.
NOTE: You may create an indexed group manually using the following command:
racadm config -g <groupname> -o <anchored object> -i <index 1-16> <unique anchor
name>
• The line for an indexed group cannot be deleted from a .cfg le. If you do delete the line with a text editor, RACADM stops when
it parses the conguration le and alert you of the error.
You must remove an indexed object manually using the following command:
racadm config -g <groupname> -o <objectname> -i <index 1-16> ""
71