Owner's Manual

Using the RACADM Command Line Interface 81
When using remote RACADM to capture the configuration groups into a file,
if a key property within a group is not set, the configuration group is not saved
as part of the configuration file. If these configuration groups are needed to
be cloned onto other CMCs, the key property must be set before executing
the getconfig -f command. Alternatively, you can manually enter the
missing properties into the configuration file 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
RACADM Error Messages
For information about RACADM CLI error messages, see "Troubleshooting"
on page 106.
Using RACADM to Configure the CMC
NOTE: In order to configure CMC the first time, you must be logged in as user root
to execute RACADM commands on a remote system. Another user can be created
with privileges to configure the CMC.
The CMC Web interface is the quickest way to configure the CMC (see
"Using the CMC Web Interface" on page 109
). However, if you prefer CLI or
script configuration or need to configure multiple CMCs, use Remote
RACADM, which is installed with the CMC agents on the management
station.
Configuring CMC Network Properties
Before you can begin configuring the CMC, you must first configure the
CMC network settings to allow the CMC to be managed remotely.
This initial configuration assigns the TCP/IP networking parameters that
enable access to the CMC.