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
24
5 Configuring Windows and Linux DHCP servers to support
Auto Config
Configuring Windows DHCP server option 43
Configuring Windows DHCP server option 60
Configuring a Linux DHCP server
Configuring a Linux DHCPv6 Server
The following server “roles” are required:
• DHCP server
• File server (must support CIFS or NFS file sharing).
5.1 Auto Config Server Configuration Profile String Format for DHCP
Option 43 and DHCPv6 Option 17
In general, both Windows and Linux DHCP and DHCPv6 servers must be configured to do two things:
1. To recognize and respond to the Vendor Class Identifier option value “iDRAC” (DHCP Option 60, or
DHCPv6 Option 16) sent by the iDRAC.
2. To respond to the iDRAC by sending the Vendor-specific Information option (DHCP Option 43, or
DHCPv6 Option 17.) This information contains the specific string of parameters the iDRAC must connect
and download a Server Configuration Profile from the SCP server on the network.
The arguments in the parameter string are identical for both DHCP and DHCPv6. They are defined here as a
reference for the following sections.
The list of required and optional parameters to be entered as the string value:
• -f (Filename): Name of exported Server Configuration Profile file
Note: If the -f parameter is not used, see the "File Naming Behavior with iDRAC Auto Config”
section.
Note: For DHCP, the length of this string is limited to 255 characters by the DHCP protocol. For DHCPv6, the
iDRAC limits the length to 1023 characters.
• -n (Sharename): Name of network share (mandatory for NFS or CIFS)
• -s (ShareType): Type 0 for NFS, or 2 for CIFS (mandatory)
• -i (IPAddress): IP address of the network share (mandatory)
• -u (Username): Username that has access to network share (mandatory only for CIFS)
• -p (Password): User password that has access to network share (mandatory only for CIFS)
• -d (ShutdownType): Type 0 for graceful or 1 for forced (default setting: 0) (optional)
• -t (Timetowait): Time to wait for the host to shut down (default setting: 300) (optional)
• -e (EndHostPowerState): Type 0 for OFF or 1 for ON (default=1) (optional)
Along with supporting NFS and CIFS-based file sharing, iDRAC9 firmware 3.00.00.00 and later also
supports accessing profile files using HTTP and HTTPS. The -s option flag is updated as follows: