Users Guide

To enable provisioning server using iDRAC Settings utility:

1. Turn on the managed system.

During POST, press F2, and go to iDRAC Settings → Remote Enablement.

The iDRAC Settings Remote Enablement page is displayed.

3. Enable auto-discovery, enter the provisioning server IP address, and click Back.

NOTE: Specifying the provisioning server IP is optional. If it is not set, it is discovered using DHCP or DNS settings

(step 7).

4. Click Network.

The iDRAC Settings Network page is displayed.

5. Enable NIC.

6. Enable IPv4.

NOTE: IPv6 is not supported for auto-discovery.

7. Enable DHCP and get the domain name, DNS server address, and DNS domain name from DHCP.

NOTE: Step 7 is optional if the provisioning server IP address (step 3) is provided.

Conguring servers and server components using Auto Cong

The Auto Cong feature congures and provisions all the components in a server in a single operation. These components include

BIOS, iDRAC, and PERC. Auto Cong automatically imports a Server Conguration Prole (SCP) XML le containing all congurable

parameters. The DHCP server that assigns the IP address also provides the details for accessing the SCP le.

SCP les are created by conguring a gold conguration server. This conguration is then exported to a shared CIFS or NFS network

location that is accessible by the DHCP server and the iDRAC of the server being congured. The SCP le name can be based on

the Service Tag or model number of the target server or can be given a generic name. The DHCP server uses a DHCP server option

to specify the SCP le name (optionally), SCP le location, and the user credentials to access the le location.

When the iDRAC obtains an IP address from the DHCP server that is congured for Auto Cong, iDRAC uses the SCP to congure

the server’s devices. Auto Cong is invoked only after the iDRAC gets its IP address from the DHCP server. If it does not get a

response or an IP address from the DHCP server, then Auto Cong is not invoked.

NOTE:

• You can enable Auto Cong only if DHCPv4 and the Enable IPv4 options are enabled.

• Auto Cong and Auto Discovery features are mutually exclusive. Disable Auto Discovery for Auto Cong to work.

• The Auto Cong is disabled after a server has carried out an Auto Cong operation. For more information on enabling Auto

Cong, see Enabling Auto Cong using RACADM.

If all the Dell PowerEdge servers in the DHCP server pool are of the same model type and number, then a single SCP le

(cong.xml) is required. cong.xml is the default SCP le name.

You can congure individual servers requiring dierent conguration les mapped using individual server Service Tags or server

models. In an environment that has dierent servers with specic requirements, you can use dierent SCP le names to distinguish

each server or server type. For example, if there are two server models to congure—PowerEdge R730s and PowerEdge R530s,

use two SCP les,

R730-cong.xml and R530-cong.xml.

NOTE: On systems with iDRAC version 2.20.20.20 or later, if the le name parameter is not present in DHCP option 60,

the iDRAC server conguration agent automatically generates the conguration lename using the server Service Tag,

model number, or the default lename—cong.xml.

The iDRAC server conguration agent uses the rules in the following sequence to determine which SCP le on the le share to apply

for each iDRAC:

1. The lename specied in DHCP option 60.