Users Guide

NOTE: On systems with iDRAC version 2.20.20.20 or later, if the filename parameter is not present in DHCP option 60, the

iDRAC server configuration agent automatically generates the configuration filename using the server Service Tag, model

number, or the default filename—config.xml.

The iDRAC server configuration agent uses the rules in the following sequence to determine which SCP file on the file share to

apply for each iDRAC:

1. The filename specified in DHCP option 60.

2. <ServiceTag>-config.xml — If a filename is not specified in DHCP option 60, use the system Service Tag to uniquely

identify the SCP file for the system. For example, CDVH7R1-config.xml

3. <Model number>-config.xml — If the option 60 filename is not specified and the <Service Tag>-config.xml

file is not found, use the system model number as the basis for the SCP filename to use. For example, R520-config.xml.

4. config.xml — If the option 60 filename, service tag-based, and model number-based files are not available, use the

default config.xml file.

NOTE: To set the workload profile along with other attributes using SCP, ensure that you run the SCP import job twice to

get the correct configuration changes.

NOTE: If none of these files are on the network share, then the server configuration profile import job is marked as failed

for file not found.

For iDRAC firmware 2.70.70.70 and later versions, JSON format profile files are supported. The following file names will be used,

if the Filename parameter is not present:

● "<service tag>-config.xml" (Example: CDVH7R1-config.xml)

● "<model number)-config.xml" (Example: R630-config.xml)

● "config.xml"

● "<service tag>-config.json" (Example: CDVH7R1-config.json)

● "<model number)-config.json" (Example: R630-config.json)

● "config.json"

Related concepts

Auto Config sequence on page 44

DHCP options on page 44

Related tasks

Enabling Auto Config using iDRAC web interface on page 48

Enabling Auto Config using RACADM on page 48

Auto Config sequence

1. Create or modify the SCP file that configures the attributes of Dell servers.

2. Place the SCP file in a share location that is accessible by the DHCP server and all the Dell servers that are assigned IP

address from the DHCP server.

3. Specify the SCP file location in vendor-option 43 field of DHCP server.

4. The iDRAC as part of acquiring IP address advertises vendor class identifier iDRAC. (Option 60)

5. The DHCP server matches the vendor class to the vendor option in the dhcpd.conf file and sends the SCP file location

and, if specified the SCP file name to the iDRAC.

6. The iDRAC processes the SCP file and configures all the attributes listed in the file

DHCP options

DHCPv4 allows many globally defined parameters to be passed to the DHCP clients. Each parameter is known as a DHCP

option. Each option is identified with an option tag, which is a 1-byte value. Option tags 0 and 255 are reserved for padding and

end of options, respectively. All other values are available for defining options.

Setting up managed system and management station