Users Guide
-s (ShareType): pass in either 0 for NFS, 2 for CIFS, 5 for HTTP and 6 for HTTPS. This is a mandatory field for iDRAC firmware
versions 3.00.00.00.
-i (IPAddress): IP address of the network share. This is a mandatory field.
-u (Username): username that has access to network share. This is a mandatory field for CIFS.
-p (Password): user password that has access to network share. This is a mandatory field for CIFS.
-d (ShutdownType): either 0 for graceful or 1 for forced (default setting: 0). This is an optional field.
-t (Timetowait): time to wait for the host to shutdown (default setting: 300). This is an optional field.
-e (EndHostPowerState): either 0 for OFF or 1 for ON (default setting 1). This is an optional field.
The additional option flags are supported in iDRAC firmware 3.00.00.00 or later to enable the configuration of HTTP proxy parameters and
set the retry timeout for accessing the Profile file:
—pd (ProxyDefault): Use default proxy setting. This is an optional field.
—pt (ProxyType): The user can pass in http or socks (default setting http). This is an optional field.
—ph (ProxyHost): IP address of the proxy host. This is an optional field.
—pu (ProxyUserName): username that has access to the proxy server. This is required for proxy support.
—pp (ProxyPassword): user password that has access to the proxy server. This is required for proxy support.
—po (ProxyPort): port for the proxy server (default setting is 80). This is an optional field.
—to (Timeout): specifies the retry timeout in minutes for obtaining config file (default is 60 minutes).
For iDRAC firmware 3.00.00.00 or later, 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: R640-config.xml
• config.xml
• <service tag>-config.json, Example:CDVH7R1-config.json
• <model number>-config.json, Example: R630-config.json
• config.json
NOTE:
More information about HTTP can be found in the
14G Support for HTTP and HTTPS across IDRAC9 with
Lifecycle Controller Interfaces
white paper at www.dell.com/support.
NOTE:
• Auto Config can only be enabled when 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.
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. The config.xml file name is used as the default SCP file name. In addition to .xml file, .json files can also be used with
14G systems. The file can be config.json.
The user 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, different SCP file names can be used to distinguish each
server or server type. For example, if there are two server models to configure — PowerEdge R740s and PowerEdge R540s, use two
SCP files, R740-config.xml and R540-config.xml.
NOTE:
iDRAC server configuration agent automatically generates the configuration filename using the server Service
Tag, model number, or the default filename — config.xml.
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.
Auto Config sequence
1. Create or modify the SCP file that configures the attributes of Dell servers.
2. Place the SCP file in a share location that is accessible by the DHCP server and all the Dell servers that are assigned IP address from
the DHCP server.
46
Setting up managed system