Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Integrated Dell Remote Access Controller 8 Version 2.70.70.70 User’s Guide

PDF

Configuring servers and server components using Auto Config

The Auto Config feature configures and provisions all the components in a server in a single operation. These components include BIOS, iDRAC, and PERC. Auto Config automatically imports a Server Configuration Profile (SCP) XML file containing all configurable parameters. The DHCP server that assigns the IP address also provides the details for accessing the SCP file.

SCP files are created by configuring a gold configuration server. This configuration 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 configured. The SCP filename 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 filename (optionally), SCP file location, and the user credentials to access the file location.

NOTE:CIFS supports both IPv4 and IPv6 addresses and NFS supports only IPv4 address.

When the iDRAC obtains an IP address from the DHCP server that is configured for Auto Config, iDRAC uses the SCP to configure the server’s devices. Auto Config 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 Config is not invoked.

NOTE:
  • You can enable Auto Config only if DHCPv4 and the Enable IPv4 options are enabled.
  • Auto Config and Auto Discovery features are mutually exclusive. Disable Auto Discovery for Auto Config to work.
  • The Auto Config is disabled after a server has carried out an Auto Config operation. For more information about enabling Auto Config, see Enabling Auto Config 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 file (config.xml) is required. config.xml is the default SCP filename.

You can configure individual servers requiring different configuration files mapped using individual server Service Tags or server models. In an environment that has different servers with specific requirements, you can use different SCP filenames to distinguish each server or server type. For example, if there are two server models to configure—PowerEdge R730s and PowerEdge R530s, use two SCP files, R730-config.xml and R530-config.xml.

NOTE:On systems with iDRAC version 2.20.20.20 or later, if the filename parameter is not present in DHCP option 60, the iDRAC server configuration agent automatically generates the configuration filename using the server Service Tag, model number, or the default filename—config.xml.
The iDRAC server configuration agent uses the rules in the following sequence to determine which SCP file on the file share to apply for each iDRAC:
  1. The filename specified in DHCP option 60.
  2. <ServiceTag>-config.xml — If a filename is not specified in DHCP option 60, use the system Service Tag to uniquely identify the SCP file for the system. For example, CDVH7R1-config.xml
  3. <Model number>-config.xml — If the option 60 filename is not specified and the <Service Tag>-config.xml file is not found, use the system model number as the basis for the SCP filename to use. For example, R520-config.xml.
  4. config.xml — If the option 60 filename, service tag-based, and model number-based files are not available, use the default config.xml file.
NOTE:To set the workload profile along with other attributes using SCP, ensure that you run the SCP import job twice to get the correct configuration changes.
NOTE:If none of these files are on the network share, then the server configuration profile import job is marked as failed for file not found.
For iDRAC firmware 2.70.70.70 and later versions, JSON format profile files are supported. The following file names will be used, if the Filename parameter is not present:
  • "<service tag>-config.xml" (Example: CDVH7R1-config.xml)
  • "<model number)-config.xml" (Example: R630-config.xml)
  • "config.xml"
  • "<service tag>-config.json" (Example: CDVH7R1-config.json)
  • "<model number)-config.json" (Example: R630-config.json)
  • "config.json"

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\