White Papers

Version 2.0.0 11
7 Auto-Discovery Implementation Alternatives
248
If more than one discovery method is used simultaneously, the provisioning server address acquisition
249
sequence is the following:
250
1. Provisioning Server Set in iDRAC settings
251
2. DHCP Vendor Scope Option
252
3. DNS SRV record
253
4. Default Host A record
254
7.1 Manually Setting the Provisioning Server
255
This is not zero touch but if DHCP and DNS services are not available, or if there is a desire to skip the
256
discovery process, the iDRAC can have the provisioning server set manually. This can be done in either
257
the iDRAC settings page (Cntrl E on 11
th
generation servers and F2 on 12
th
generation servers) or the
258
System Services/Lifecycle Controller Page (F10) during boot. For more information on manually setting
259
the provisioning server see Checking iDRAC Configuration Settings (11
th
generation servers)
260
7.2 Provide Provisioning Server information within DHCP scope options
261
To enable the Auto-Discovery feature, the default iDRAC NIC setting out of the box is required to be
262
DHCP rather than statically assigned IP address. The iDRAC sets a vendor class identifier (option 60) in
263
the DHCPREQUEST message to LifecycleController. This enables DHCP servers to optionally respond
264
uniquely to the iDRAC.
265
There are three possible valid responses and outcomes to the DHCPREQUEST sent by the iDRAC:
266
The request times out and an IP address is unobtainable. The iDRAC retains its DHCP setting
267
indefinitely with no login credentials. To change this setting, you would have to be physically
268
present at the server.
2
269
The DHCP server responds, but does not provide any option 43 data. In this case the iDRAC
270
attempts to locate a server using DNS (see Figure 2).
271
Option 43 data is present and includes an IP address and or hostname to use for the handshake.
272
The data will have a format that can easily be set up on a Windows or Linux DHCP server. The
273
sub option number for option 43 is “1” (see RFC2132) and has this format:
274
(FQDN | Hostname | IP Address)[:port] [, (FQDN | Hostname | IP Address)[:port] ] [, …]
275
NOTE: If the iDRAC is using a custom trusted CA to validate the provisioning provisioning server,
276
the value of sub option 1 for that provisioning server must match the CN value in the provisioning
277
server certificate or the TLS connection will fail. For example if the CN=provserv1.dell.com the
278
sub option 1 value must also be provserv1.dell.com
279
Where either the hostname or the ipaddress are provided, followed optionally by a port number.
280
Examples of string values are as follows (no spaces allowed) :
281
Provisioning.dell.com:4433 (resolve using DNS, TCP port specified.)
282
2
The iDRAC Configuration Utility using ctrl-E during boot up provides an opportunity for a static IP address and user
credentials to be specified. Also, local RACADM commands can be used.