White Papers

9 RESTful Server Configuration with iDRAC RESTful API

2 Using iDRAC RESTful API with Server Configuration Profiles

To create a Server Configuration Profile file for import to a new or to-be-reprovisioned server, create a

“golden configuration” on a PowerEdge server. After the server is configured as needed, it can act as a

template for other servers that need to use the same or similar server settings. To use these settings, an SCP

file must be created by exporting the current server settings to a file. The exported SCP file can be edited, as

needed, and used to either preview an import to a target server or be actually imported to configure a target

server.

Note: Ensure that the RESTful API is enabled for the iDRAC with Lifecycle Controller before you perform any

of the actions provided in the below scripts. For help in verifying and enabling the RESTful API, see

Appendix 1.

Let us now see how the iDRAC RESTful API SCP operations can be automated with the use of the Python

scripting language. Before explaining the SCP RESTful APIs, review the RACADM Command Line Interface

SCP operations. Following are examples of RACADM commands to export an SCP file from a server and

place the results into a CIFS or NFS network share:

# racadm get –f serverscp –t xml –u <CIFSuser> -p <CIFSpassword> -l

# racadm get –f serverscp –t xml –l <NFS Share path>

For 14th generation PowerEdge servers, additional RACADM options include:

# racadm –get –f serverscp –t JSON –u <HTTP/S user> -p <HTTP/S password> -l

In addition to the required parameters—SCP file name, network share pathname, and for CIFS share access,

a valid CIFS username and password—you can specify a few more optional parameters. These parameters

include:

 Selectors to include specific server component configuration information such as BIOS only

 Option to hash encode exported passwords

 Option to produce an SCP file in a form that clones the source server by not duplicating settings that

uniquely identify the server such as server service tag, or to produce an SCP file that can replace the

source server by duplicating all settings, including identifying settings.

Appendix 2 illustrates the available SCP export, preview, and import options available using the iDRAC SCP

RESTful API. This JSON-formatted output is produced using any iDRAC-supported web browser to access

the following URL:

https://<iDRAC IP> /redfish/v1/Managers/iDRAC.Embedded.1

In the Appendix 2 JSON output, under the “OEM” section, are the supported methods for SCP operations

including ExportSystemConfiguration, ImportSystemConfiguration and

ImportSystemConfigurationPreview. The required and optional parameters are detailed within each

method.