White Papers

37
• Configure by using system Service Tag: Export the server configuration file and rename as
<service tag>-config,xml. For each server, 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 that is
uniquely configured as required. When these servers are enabled for Auto Config, the iDRAC
server configuration agent searches the network share by using the <service tag>-
config.xml name.
• Configure by system model number: Export the server configuration file and rename as <model
number>-config.xml. For each server model to be configured, create a unique configuration
file by using the server model.
o To configure a PowerEdge R640, export the R640 configuration file and rename the file
“R640config.xml.”
o For R740s, export an R740 configuration file and rename “R740-config.xml.”
o Repeat for every model required. When an R740 is enabled for iDRAC Auto Config, the iDRAC
server configuration agent searches the network share for the file “R740-config.xml.” This
action takes place when there is no matching Service Tag-based configuration file.
• Configure with default configuration file: Export the server configuration file and name
config.xml. Each iDRAC enabled for Auto Config uses this file when there are no matching
Service Tag or model number-based configuration files on the network share.
For iDRAC9 firmware 3.00.00.00 and later versions, JSON format Profile files are supported. The following
file names are used when the Filename parameter is not present:
• “<service tag>-config.xml” (Example: CDVH7R1-config.xml)
• “<model number)-config.xml” (Example: R640-config.xml)
• “config.xml”
• “<service tag>-config.json” (Example: CDVH7R1-config.json)
• “<model number)-config.json” (Example: R640-config.json)
• “config.json”