White Papers

36
6 File naming behavior with iDRAC Auto Config
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 supported, the Filename parameter must be
updated and the DHCP server must be restarted for each change in the configuration filename. To simplify
the Auto Config process, iDRAC firmware version 3.00.00.00 and later provides dynamic configuration
filename generation, making the Filename parameter optional.
Figure 28 Filename generation in iDRAC 3.00.00.00 and
later.
If the Filename parameter is not present, the iDRAC server configuration agent automatically generates the
configuration filename. iDRAC uses the server Service Tag, the server model number, or the default
filename “config.xml.”
The iDRAC server configuration agent uses the following list of file names (in order) when 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 these files are not 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 Auto Config. The Filename parameter
does not require changes nor a restart of DHCP services to support multiple, unique configuration files.