Users Guide

2. <ServiceTag>-cong.xml — If a lename is not specied in DHCP option 60, use the system Service Tag to uniquely identify
the SCP le for the system. For example, CDVH7R1-cong.xml
3. <Model number>-cong.xml — If the option 60 lename is not specied and the <Service Tag>-cong.xml le is not found,
use the system model number as the basis for the SCP le name to use. For example, R520-cong.xml.
4. cong.xml — If the option 60 lename, service tag-based, and model number-based les are not available, use the default
cong.xml le.
NOTE: If none of these les are on the network share, then the server conguration prole import job is marked as failed
for le not found.
Related links
Auto Cong sequence
DHCP options
Enabling Auto Cong using iDRAC web interface
Enabling Auto Cong using RACADM
Auto Cong sequence
1. Create or modify the SCP le that congures the attributes of Dell servers.
2. Place the SCP le 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 le location in vendor-option 43 eld of DHCP server.
4. The iDRAC as part of acquiring IP address advertises vendor class identier iDRAC. (Option 60)
5. The DHCP server matches the vendor class to the vendor option in the dhcpd.conf le and sends the SCP le location and, if
specied the SCP le name to the iDRAC.
6. The iDRAC processes the SCP le and congures all the attributes listed in the le
DHCP options
DHCPv4 allows many globally dened parameters to be passed to the DHCP clients. Each parameter is known as a DHCP option.
Each option is identied 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 dening options.
The DHCP Option 43 is used to send information from the DHCP server to the DHCP client. The option is dened as a text string.
This text string is set to contain the values of the XML lename, share location and the credentials to access the location. For
example,
option myname code 43 = text;
subnet 192. 168.0.0 netmask 255.255.255.0 {
# default gateway
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
option nis-domain "domain.org";
option domain-name "domain.org";
option domain-name-servers 192.168.1.1;
option time-offset -18000; #Eastern Standard Time
option vendor-class-identifier "iDRAC";
set vendor-string = option vendor-class-identifier;
option myname "-f system_config.xml -i 192.168.0.130 -u
user -p password -n cifs -s 2 -
d 0 -t 500";
where, -i is the location of the Remote File Share and –f is the le name in the string along with the credentials to the Remote File
Share.
The DHCP Option 60 identies and associates a DHCP client with a particular vendor. Any DHCP server congured to take action
based on a client’s vendor ID should have Option 60 and Option 43 congured. With Dell PowerEdge servers, the iDRAC identies
itself with vendor ID: iDRAC. Therefore, you must add a new ‘Vendor Class’ and create a ‘scope option’ under it for ‘code 60,’ and
then enable the new scope option for the DHCP server.
44