White Papers
Table Of Contents
- 1 Zero-Touch Overview
- 2 Introduction
- 2.1 Interactions between components in Auto Config architecture
- 2.2 DHCP provisioning options
- 2.3 DHCP—current and new configuration options
- 2.4 Prerequisites for enabling Auto Config
- 2.5 iDRAC interfaces to enable Auto Config
- 2.5.1 Enabling Auto Config using RACADM (local or remote)
- 2.5.2 Enabling Auto Config using Redfish
- 2.5.3 Enabling Auto Config using iDRAC UI
- 2.6 Using Auto Config in an IPv6 Network
- 2.7 Server Configuration Profiles
- 3 Performing Firmware Repository Update During Auto Config
- 4 Performing Operating System Deployment During Auto Config
- 5 Configuring Windows and Linux DHCP servers to support Auto Config
- 5.1 Auto Config Server Configuration Profile String Format for DHCP Option 43 and DHCPv6 Option 17
- 5.2 Configuring Windows DHCP server option 43
- 5.3 Configuring Windows DHCP server option 60
- 5.4 Configuring Windows DHCPv6 server options 16 and 17
- 5.5 Configuring a Linux DHCP server
- 5.6 Configuring a Linux DHCPv6 Server
- 6 File naming behavior with iDRAC Auto Config
- 7 Workflow Examples
- 8 Troubleshooting Auto Config issues
- 9 Conclusion
- A Technical support and resources
![](/manual/dell/enterprise-solution-resources/74-73-72-71-70-69-68-67-66-65-64-63-62-61-60-59-58-57-56-55-54-53-52-51-50-49-48-47-46-45-44-43-42-41-40-39-38-37-36-35-34-33-32-31-30-29-28-27-26-25-24-23-22-21-20-19-18-17-16-15-14-13-12-11-10-9-8-7-6-5-4-3-2-1-white-papers-english/images/img-34.png)
34
option myname code 43 = text;
subnet 192.168.0.0 netmask 255.255.0.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";
range dynamic-bootp
192.168.0.128 92.168.0.254;
default-lease-time
21600;
max-lease-time
43200;
}
An example of a static DHCP reservation from a dhcpd.conf file:
# Applying a config to a particular system specified by MAC address
host my_host {
hardware ethernet b8:2a:72:fb:e6:56;
fixed-address 192.168.0.211;
option host-name "my_host";
option myname " -f r630_raid.xml -i 192.168.0.1 -n /nfs -s 0 -d 0 -t 300";
}
Note: After editing the dhcpd.conf file, ensure to restart the dhcpd service for the changes to take effect.
5.6 Configuring a Linux DHCPv6 Server
If DHCPv6 is being used to send the Vendor-specific Information option, the following steps can be used to
configure the ISC.org dhcpd daemon. If using this daemon, it is recommended that version 4.4.1 or later be
used, for improved IPv6 support.
1. Open the Linux DHCP configuration file /etc/dhcp/dhcp6.conf.
a. Add these lines at the top of the DHCP configuration file, outside any brackets, to define the Vendor
Class and Vendor-specific Information DHCPv6 options:
option dhcp6.vendor-class code 16 = {integer 32, integer 16, string};
option dhcp6.vsi code 17 = {integer 32, integer 16, integer 16, string};
2. Add these lines below the vendor-class line, modifying the vendor-opts parameter string for your specific
environment. See section 6.1
for details on the required and optional parameters for this string.
The three numbers on the “option dhcp6.vsi” line, before the string are fields in the DHCPv6 Vendor-specific
Information option as defined in RFC 8415 section 21.17
, and are, in order:
674: The IANA Enterprise Number assigns to Dell. This value must match exactly.
17: Vendor-specific Information suboption 17. This value must match exactly
98: The length in bytes of the string that follows. In the example below, the length of the “-f config.xml” string
is 98 bytes.