Reference Guide

Input
• <FQDD Alias>
• Examples for FQDDs
•
System.Power
•
System.Power.Supply
• System.Location
• LifecycleController.LCAttributes
• System.LCD
• iDRAC.Serial
For the list of supported groups and objects under the get command, see Database objects with get and set
commands
• <group>—Specifies the group containing the object that must be read.
• <object>—Specifies the object name of the value that must be read.
• <index>—Specifies where FQDD Aliases or Groups must be indexed.
• -f <filename>—This option enables you to export multiple object values to a file. This option is not
supported in the Firmware RACADM interface.
• -u—Specifies user name of the remote CIFS share to which the file must be exported.
• -p—Specifies password for the remote CIFS share to which the file must be exported.
• -l—Specifies network share location to which the file is exported.
• -t—Specifies the file type to be exported.
The valid values are:
• JSON—It exports the SCP JSON file to a network share file.
• xml—It exports the SCP xml format file, either to a local or network share file.
• ini—It exports the legacy configuration file. If -t is not specified, then the ini format file is exported. It can
only be exported to a local file.
NOTE:
To import or export Server Configuration Profile xml files, Lifecycle Controller version 1.1
or later is required.
• --clone—Gets the configuration .xml files without system-related details such as service tag. The .xml file
received does not have any virtual disk creation option.
• --replace—Gets the configuration .xml files with the system-related details such as service tag.
• -c—Specifies the FQDD or list of FQDDs separated by ',' of the components for which the configurations
should be exported. If this option is not specified, the configuration related to all the components are exported.
• --includeph—Specifies that the output of the passwords included in the exported configuration .xml file
are in the hashed format.
NOTE:
if --includeph is not used, the output of the passwords are in the .xml file in clear text.
NOTE: For --clone and --replace options, only .xml file template is received. These options --
clone and --replace cannot be used in the same command.
This command does not support proxy parameters. To perform the operation with http and https, the proxy
parameters has to be configured in the lifecyclecontroller.lcattributes. Once these proxy parameters are configured,
they become the part of default configuration. They have to be removed to ignore the proxy parameters.
The valid proxy parameters:
• UserProxyUserName
• UserProxyPassword
• UserProxyServer
• UserProxyPort
• UserProxyType
RACADM Subcommand Details
59