Users Guide

CMCs, the key property must be set before executing the getconfig -f command. Alternatively, you can manually enter the
missing properties into the conguration le after running the getconfig -f command. This is true for all the RACADM–indexed
groups.
This is the list of the indexed groups that exhibit this behavior and their corresponding key properties:
– cfgUserAdmin — cfgUserAdminUserName
– cfgEmailAlert — cfgEmailAlertAddress
– cfgTraps — cfgTrapsAlertDestIPAddr
– cfgStandardSchema — cfgSSADRoleGroupName
– cfgServerInfo — cfgServerBmcMacAddress
Modifying the CMC IP address
When you modify the CMC IP address in the conguration le, 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.
Example:
#
# Object Group "cfgLanNetworking"
#
[cfgLanNetworking]
cfgNicIpAddress=192.x.x.x
cfgNicGateway=10.35.10.1
This le is updated as follows:
#
# Object Group "cfgLanNetworking"
#
[cfgLanNetworking]
cfgNicIpAddress=10.35.9.143
# comment, the rest of this line is ignored
cfgNicGateway=10.35.9.1
The command racadm config -f <myfile>.cfg parses the le and identies any errors by line number. A correct le updates the
proper entries. Additionally, you can use the same getconfig command from the previous example to conrm the update.
Use this le to download company-wide changes or to congure new systems over the network with the command, racadm
getconfig -f <myfile>.cfg.
NOTE
: Anchor is a reserved word and should not be used in the .cfg le.
Conguring CMC 81