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
33
Figure 27 Example Wireshark Packet Capture of DHCPv6 Response message.
5.5 Configuring a Linux DHCP server
The following instructions are specific to the ISC.org dhcpd server. If a different DHCP server package is
used, see its instructions for configuring the Vendor Class and Vendor-specific Information options.
1. Open the Linux DHCP configuration file (for example, /etc/dhcp/dhcpd.conf) by using a text editor and
add these lines:
Add this string at the top of the DHCP configuration file, outside the braces:
option myname code 43 = text;
Add these strings inside subnet entry braces:
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 sambashare/config_files –s 2 –d 0 –t 500";
The “option myname” string is an example of entering network share information for access to the Server
Configuration Profile file. Edit this information by using the filename and network share information. The list of
required and optional parameters for this string can be found in
section 6.1. Note: Test the network share first
and make certain that it can be accessed without any issues.
Note: NFS4 is not supported on iDRAC9 3.00.00.00 and earlier versions. Use NFS2 or NFS3 for NFS
network share.
An example of an edited dhcpd.conf file - lines in bold were added to the existing file: