Users Guide
82 Advanced Configuration of the DRAC 5
The .cfg file can be:
•Created
• Obtained from a
racadm getconfig -f
<filename>
.cfg
command
• Obtained from a r
acadm getconfig -f
<filename>
.cfg
command, and then edited
NOTE: See "getconfig" for information about the getconfig command.
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 that detected the error, and a simple message
explains the problem. The entire file is parsed for correctness, and all errors
are displayed. Write commands are not transmitted to the DRAC 5 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 a write
operation to the DRAC 5.
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 DRAC 5 for that group.
Any objects within that group are simple modifications when the DRAC 5
is configured. If a modified object represents a new index, the index is
created on the DRAC 5 during configuration.
• You cannot specify an index of your choice 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 you do not
need to make exact index matches between all the RACs being managed.
New users are added to the first available index. A
.cfg
file that parses and
runs correctly on one DRAC 5 may not run correctly on another if all
indexes are full and you must add a new user.