Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

iDRAC 8/7 v2.70.70.70 RACADM CLI Guide

PDF

get

Table 1. Details of get The following table provides the details of get subcommand:
Description

Displays the value of one or more objects. The getsub-command has two forms.

  • Displays the value of a single object.
  • Exports the value of multiple objects to a file.

It supports multiple object value export in two file formats

  • JSON format— SCP JSON files can be exported to a network share file.
  • INI format — The INI format files can be exported to a local file only

    NOTE: : INI file format is deprecated. It is recommended to use XML or JSON formats.

  • Server Configuration Profile XML/JSON format — XML/JSON format files can be exported to a local file, to an NFS network share or to a CIFS network share.

    NOTE: : To run theGet sub-command for Server Configuration Profile XML files, use the Lifecycle Controller version 1.1 or later.

NOTE: : Some objects may have a pending value if a Set operation is performed on the object through a reboot job. To complete the pending operation, schedule the job using a jobqueue command, and then check for completion of the job using the returned Job ID. For more information, see jobqueue

NOTE: : This command supports both IPV4 and IPV6 formats. IPV6 is applicable only for CIFS, HTTP, and HTTPS remote shares.

Synopsis

Single-object Get

racadm get <FQDD Alias>.<group>
racadm get <FQDD Alias>.<group>.<object>
racadm get <FQDD Alias>.<group>.[<index>].<object>
racadm get <FQDD Alias>.<index>.<group>.<index>.<object>

Multi-object Get

racadm get -f <filename>
racadm get -f <filename> -t xml -l <NFS share> [--clone | --replace ] [--includeph]
racadm get -f <filename> -t xml -l <NFS share> -c <FQDD>[,<FQDD>*]
racadm get -f <filename> -t xml -u <username> -p <password> -l <CIFS share> [--clone | --replace ] [--includeph]
racadm get -f <filename> -t xml -u <username> -p <password> -l <CIFS share> -c <FQDD>[,<FQDD>*]
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 has to be exported.
  • -p—Specifies password for the remote CIFS share to which the file has to be exported.
  • -l—Specifies network share location to which the file will be 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/JSON 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/JSON file are in the hashed format.

    NOTE: : if –includeph is not used, the output of the passwords will be in the .xml/JSON 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.

Examples
  • Get system LCD information.
    racadm get system.lcdLCDUserString
  • Display an entire group, in this case the topology configuration.
    racadm get system.location
  • Display a single object from a particular group.
    racadm get system.location.rack.name
  • Export the xml configuration to a CIFS share.
    racadm get -f file -t xml -u myuser -p xxx -l //192.168.0/share
  • Export the xml configuration to an NFS share.
    racadm get -f file -t xml -l 192.168.0:/myshare
  • Export a “cloned” xml configuration to a CIFS share
    racadm get -f xyz_temp_clone -t xml -u Administrator -p xxx -l //192.168.0/xyz --clone
  • Export a “replace” xml configuration to a CIFS share
    racadm get -f xyz_temp_replace -t xml -u Administrator -p xxx -l //192.168.0/xyz --replace
  • Export the xml configuration to an HTTP share
    racadm get -f file -t xml -u httpuser -p httppwd -l http://test.com/myshare
  • Export the xml configuration to an HTTPS share
    racadm get -f file -t xml -u httpuser -p httpspwd -l https://test.com/myshare
  • Export the xml configuration of the iDRAC component to a CIFS share.
    racadm get -f file -t xml -u myuser -p xxx -l //192.168.0/share  -c iDRAC.Embedded.1
  • Include password hash in the configuration .xml file.
    racadm get -f<filename> -t xml -l<NFS or CIFS share> -u<username> -p<password> -t xml --includeph

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\