White Papers

39 Zero-touch, bare-metal server provisioning using the Dell EMC iDRAC with Lifecycle Controller Auto Config
6.4 File naming behavior with iDRAC firmware 2.20.20.20 or later
The Filename parameter is most useful when only a single configuration file is required for the servers by
using Auto Config. If multiple server configurations are to be supported, the Filename parameter must be
updated and the DHCP server restarted for each change in the configuration filename. To simplify the Auto
Config process, iDRAC firmware version 2.20.20.20 and later provides dynamic configuration filename
generation, making the Filename parameter optional.
Filename generation in iDRAC 2.20.20
If the Filename parameter is not present when using iDRAC 2.20.20.20 and later versions, the iDRAC server
configuration agent will automatically generate the configuration filename by using the server’s Service Tag,
the server’s model number, or using the default filename “config.xml.”
Here is the list of file names (in order) that the iDRAC 2.20.20.20 and later server configuration agent will use
if the Filename parameter is not provided in the DHCP configuration:
 “<service tag>-config.xml” (Example: CDVH7R1-config.xml)
 “<model number)-config.xml” (Example: R630-config.xml)
 “config.xml”
If none of these files are located on the network share, the server configuration profile import job is indicated
as “failed” because the file is not found.
Here are the examples of the dynamic file naming behavior of iDRAC 2.20.20.20 and later Auto Config, When
using this feature, the Filename parameter does not have to be changed nor DHCP services restarted to
support multiple, unique configuration files.
 Configure by using system Service Tag: Export the server configuration file and rename as
<service tag>-config,xml. For each server that will be configured, create a unique
configuration file by using the servers’ Service Tags. If three new servers with service tags
CDVH7R1, CDVH7R2, and CDVH7R3 are to use Auto Config, create three configuration files
“CDVH7R1-config.xml”, “CDVH7R2-config.xml” and “CDVH7R3-config.xml”—each file uniquely