User's Manual
l Displaying all configuration properties in a group (specified by group name and index)
l Displaying all configuration properties for a user by user name
l Including password (other than user password) information in the generated .cfg file
The config subcommand loads the information into other DRAC 4s. Other options for config enable you to perform such actions as:
l Removing passwords in the racadm.cfg file used to configure the card
l Synchronizing the user and password database with Server Administrator
The initial configuration file, racadm.cfg, is named by the user. In the following example, the configuration file is named myfile.cfg. To obtain this file, type the
following command at the command prompt:
racadm getconfig –f myfile.cfg
Creating a DRAC 4 Configuration File
The DRAC 4 configuration file <filename>.cfg is used with the racadm config -f <filename>.cfg command. The configuration file is a simple text file that
allows the user to build a configuration file (similar to an .ini file) and configure the DRAC 4 from this file. You may use any file name, and the file does not
require a .cfg ending (although it is referred to by that designation in this subsection). The .cfg file can be:
l Created
l Obtained from a racadm getconfig -f <filename>.cfg command
l Obtained from a racadm getconfig -f <filename>.cfg command, and then edited
The .cfg file is first parsed 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 in which the error was detected, and a simple message explains the problem. The entire file is parsed for correctness, and all errors are
displayed. Writes are not performed to the DRAC 4 if an error is found in the .cfg file. The user must correct all errors before any configuration can take place.
The -c option may be used in the config subcommand, which verifies syntax only and does not perform writes to the DRAC 4.
Remember the following important points:
l 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 DRAC 4 for that group. Any objects within that group are simple modifications at configuration time. If a
modified object represents a new index, the index is created on the DRAC 4 during configuration.
l The user cannot specify a desired index in a .cfg file.
Indexes may be created and deleted, so 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 the user does not
need to make exact index matches between all of the RACs being managed; new users are added to the first available index. A .cfg file that parses and
runs correctly on one DRAC 4 may not run correctly on another if all of indexes are full and a new user was to be added.
l Use the racresetcfg subcommand to keep all DRAC 4s the same.
To keep all DRAC 4s the same, use the racresetcfg subcommand to reset the DRAC 4 to original defaults, and then run the racadm config -f
<filename>.cfg command. Ensure that the .cfg file has all the desired objects, users, indexes, and other parameters.
Parsing Rules
l All lines that start with '#' 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 have #
characters as part of their string. An escape character is not required. The user 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 different DRAC 4, without adding escape characters).
Example:
#
# This would be a comment
[cfgUserAdmin]
cfgUserAdminPageModemInitString=<Modem init # not a comment>
l All group entries must be surrounded by [ and ] characters.
The starting [ character denoting a group name must start in column one. This group name must be specified before any of the objects in that group.
Objects that do not have an associated group name, generate an error. The configuration data is organized into groups as defined in "DRAC 4 Property
Database Group and Object Definitions."
NOTICE: It is recommended that you edit this file with a simple text editor; the racadm utility uses an ASCII text parser, and any formatting confuses
the parser and might corrupt the racadm database.
NOTE: See "config/getconfig" for information about the getconfig command.
NOTICE: Use the racresetcfg subcommand to reset the database and the DRAC 4 NIC settings to the original default settings and remove all users
and user configurations. While the root user is available, other users' settings are also reset to the default.