User's Manual

Using the RACADM Command Line Interface 89
Creating a CMC Configuration File
The CMC configuration file, <filename>.cfg, is used with the racadm
config -f <filename>.cfg command to create a simple text file.
The command allows you to build a configuration file (similar to an .ini file)
and configure the CMC from this file.
You may use any file name, and the file 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 Dell Chassis
Management Controller Administrator Reference Guide.
RACADM parses the .cfg file when it is first 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 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 display. Write commands are not
transmitted to the CMC if an error is found in the .cfg file. You must correct
all errors before any configuration can take place.
To check for errors before you create the configuration file, use the
-c option
with the config subcommand. With the
-c option, config only verifies
syntax and does not write to the CMC.
Use the following guidelines when you create a .cfg file:
• If the parser encounters an indexed group, it is the value of the anchored
object that differentiates the various indexes.
The parser reads in all of the indexes from the CMC for that group.
Any objects within that group are modifications when the CMC
is configured. If a modified object represents a new index, the index
is created on the CMC during configuration.
• You cannot specify a desired index in a
.cfg file.
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
modified. If an index is not present, the first available index is used.
This method allows flexibility 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 first available index. A
.cfg file 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.