•
An indexed object entry is ignored by the .cfg parser.
The user cannot specify which index is used. If the index already exists, it is used, or else the
new entry is created in the first available index for that group.
The racadm getconfig -f <filename>.cfg command places a comment in front of index
objects, which allows the user to see which comments are being used.
NOTE:
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 file.
•
The user must remove an indexed object manually using the following command:
racadm config -g < groupName > -o < objectName > -i < index 1-16 > ""
NOTE:
To view the contents of an indexed group, use the following command:
racadm getconfig -g < groupName > -i < index 1-16 >
For indexed groups the object anchor must be the first object after the brackets ([ ]) pair. The
•
following are examples of the current indexed groups:
[cfgUserAdmin]
cfgUserAdminUserName=< USER_NAME >
"
[cfgTraps]
cfgTrapsDestIpAddr=< IP_ADDRESS >
'
'
NOTE:
the current DRAC 4 configuration. This configuration file can be used as an example and as a starting
point for your unique .cfg file.
Configuration File Example
The following example describes the IP address of the DRAC 4. Remove all unnecessary
<variable>=value entries. In this situation, only the actual variable group's label with "[" and
"]" will remain along with the two <variable>=value entries pertaining to the IP address change.
136
Using the serial and racadm Commands
The user may create an indexed group manually using the following command:
""
A NULL string (two
characters) directs the DRAC 4 to delete the index for the specified group.
Type
racadm getconfig -f <
>.cfg
. This command builds a .cfg file for
myexample