Users Guide

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 (step 1) requests the CMC conguration for the active 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 use the getcong 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.
Related link
Creating a CMC Conguration File
Creating a CMC Conguration File
The CMC conguration le, <lename>.cfg, is used with the racadm config -f <filename>.cfgcommand to create a
simple text le. The command allows you to build a conguration le (similar to a .ini le) and congure the CMC from this le.
You may use any le name, and the le does not require a .cfg extension (although it is referred to by that designation in this
subsection).
NOTE: For more information about the getconfig subcommand, see the
Chassis Management Controller for Dell
PowerEdge M1000e RACADM Command Line Reference Guide
.
RACADM parses the .cfg le when it is rst loaded onto the CMC to verify that valid group and object names are present and that
some simple syntax rules are being followed. Errors are agged with the line number that detected the error, and a message explains
the problem. The entire le is parsed for correctness, and all errors display. Write commands are not transmitted to the CMC if an
error is found in the .cfg le. You must correct all errors before any conguration can take place.
To check for errors before you create the conguration le, use the -c option with the config subcommand. With the -c option,
config only veries syntax and does not write to the CMC.
Follow these guidelines when you create a .cfg le:
If the parser encounters an indexed group, it is the value of the anchored object that dierentiates the various indexes.
The parser reads in all of the indexes from the CMC for that group. Any objects within that group are modications when the
CMC is congured. If a modied object represents a new index, the index is created on the CMC during conguration.
You cannot specify a desired index in a .cfg le.
Indexes may be created and deleted. Over time the group may become fragmented with used and unused indexes. If an index is
present, it is modied. If an index is not present, the rst available index is used.
This method allows exibility when adding indexed entries where you do not need to make exact index matches between all the
CMCs being managed. New users are added to the rst available index. A .cfg le that parses and runs correctly on one CMC
may not run correctly on another if all indexes are full and you must add a new user.
Use the racresetcfg subcommand to congure both CMCs with identical properties.
Use the racresetcfg subcommand to reset the CMC to original defaults, and then run the racadm config -f
<filename>.cfg
command. Ensure that the .cfg le includes all desired objects, users, indexes, and other parameters. For a
complete list of objects and groups, see the database property chapter of the Chassis Management Controller for Dell
PowerEdge M1000e RACADM Command Line Reference Guide.
CAUTION: Use the racresetcfg subcommand to reset the database and the CMC Network Interface settings to
the original default settings and remove all users and user congurations. While the root user is available, other users’
settings are also reset to the default settings.
If you type racadm getconfig -f <filename> .cfg, the command builds a .cfg le for the current CMC conguration.
This conguration le can be used as an example and as a starting point for your unique .cfg le.
90