White Papers
24 Zero-touch, bare-metal server provisioning using the Dell EMC iDRAC with Lifecycle Controller Auto Config
3.1 Getting Server Configuration Profiles
Getting server configuration profiles by using RACADM commands
Getting server configuration profiles by using WS-Man commands
The Auto Config feature provides server configuration settings by using a Server Configuration Profile—a file
that is typically created by exporting the settings from a “gold” configuration server. A common practice is to
create configuration profiles for each specific server model or class of server to be deployed. Server
Configuration Profiles can be created from a blank template, or more usually, exported from “gold”
configuration servers by using either RACADM, Redfish, or WS-Man, and saving the file to a supported NFS
or CIFS network share. Auto Config for iDRAC9 also supports HTTP and HTTPS file sharing options.
Getting Server Configuration Profiles by using Auto Config
Note: Make sure the selected file share is set up first and can be accessed without any issues.
For 12th and 13th generation PowerEdge servers prior to iDRAC 2.60.60.60 versions, the server
configuration profiles are supported in XML format, only. For 12
th
and 13
th
generation PowerEdge servers with
iDRAC 2.60.60.60 and later versions, and 14th generation PowerEdge servers with iDRAC 3.00.00.00 and
later versions, the server configuration profiles are supported in both the XML and JSON formats.
3.1.1 Getting server configuration profiles by using RACADM commands
An example is given here to describe the process of exporting server configuration profiles to an NFS share
by using RACADM commands in an SSH session. The export job is queried until the job is completed. These
commands can also be run on a remote system by preceding racadm –r <IPAddress> -u <UserName>
–p <Password> in the commands highlighted here.
1. Get the Server Configuration Profile.
racadm>>get -f system_config.xml -t xml -l 192.168.0.130:/nfs_share