The Auto Config feature configures and provisions all the components in a server (example, BIOS, iDRAC, and PERC) in a single operation by automatically importing a Server Configuration Profile (SCP) XML file containing all configurable parameters. The DHCP server that assigns the IP address also provides the details for accessing the SCP file.
SCP files are created by configuring a “gold configuration” server and exporting the server configuration to a shared location (CIFS or NFS) that is accessible by the DHCP server and the iDRAC of the server being configured. The SCP file name can be based on the service tag or model number of the target server or can be given a generic name. The DHCP server uses a DHCP server option to specify the SCP file name (optionally), SCP file location, and the user credentials to access the file location.
When the iDRAC obtains an IP address from the DHCP server that is configured for Auto Config, iDRAC uses the SCP to configure the server’s devices. Auto Config is invoked only after the iDRAC gets its IP address from the DHCP server. If it does not get a response or an IP address from the DHCP server, then Auto Config is not invoked.
If all the Dell PowerEdge servers in the DHCP server pool are of the same model type and number, then a single SCP file (config.xml) is required. config.xml is the default SCP file name.
You can configure individual servers requiring different configuration files mapped using individual server Service Tags or server models. In an environment that has different servers with specific requirements, you can use different SCP file names to distinguish each server or server type. For example, if there are two server models to configure — PowerEdge R730s and PowerEdge R530s, use two SCP files, R730-config.xml and R530-config.xml.