Users Guide

Using the Local RACADM Command Line Interface 239
• For indexed groups the object anchor must be the first object after the [ ]
pair. The following are examples of the current indexed groups:
[cfgUserAdmin]
cfgUserAdminUserName=<
username >
• 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 iDRAC6 for that group.
Any objects within that group are simple modifications when iDRAC6 is
configured. If a modified object represents a new index, the index is
created on iDRAC6 during configuration.
• You cannot specify a desired index in a configuration 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 configuration
file that parses and runs correctly on one iDRAC6 may not run correctly on
another if all indexes are full and you must add a new user.
Modifying the iDRAC6 IP Address in a Configuration File
When you modify the iDRAC6 IP address in the configuration file, remove all
unnecessary <variable>=<value> entries. Only the actual variable group’s
label with "[" and "]" remains, including the two <variable>=<value>
entries pertaining to the IP address change.
For example:
#
# Object Group "cfgLanNetworking"
#
[cfgLanNetworking]
cfgNicIpAddress=10.35.10.110
cfgNicGateway=10.35.10.1