Users Guide

Table Of Contents
Enabling provisioning server
The provisioning server feature allows newly installed servers to automatically discover the remote management console that
hosts the provisioning server. The provisioning server provides custom administrative user credentials to iDRAC so that the
unprovisioned server can be discovered and managed from the management console. For more information about provisioning
server, see the Lifecycle Controller Remote Services Quick Start Guide available at https://www.dell.com/idracmanuals.
Provisioning server works with a static IP address. DHCP, DNS server, or the default DNS host name discovers the provisioning
server. If DNS is specified, the provisioning server IP is retrieved from DNS and the DHCP settings are not required. If the
provisioning server is specified, discovery is skipped so neither DHCP nor DNS is required.
You can enable the Provisioning Server feature using iDRAC Settings Utility or using Lifecycle Controller. For information on
using Lifecycle Controller, see Lifecycle Controller User's Guide available at https://www.dell.com/idracmanuals .
If the Provisioning Server feature is not enabled on the factory-shipped system, the default administrator account (the default
iDRAC user name and password are provided on the system badge) is enabled. Before enabling Provisioning Server, make sure
to disable this administrator account. If the Provisioning Server feature in Lifecycle Controller is enabled, all the iDRAC user
accounts are disabled until the provisioning server is discovered.
To enable provisioning server using iDRAC Settings utility:
1. Turn on the managed system.
2. 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.
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 or JSON 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 NFS, CIFS,
HTTP or HTTPS network location that is accessible by the DHCP server and the iDRAC of the server being configured. The SCP
file name can be based on the Service Tag or model number of the target server or can be given as a generic name. The DHCP
server uses a DHCP server option to specify the SCP file name (optionally), SCP file location, and the user credentials to access
the file location.
When the iDRAC obtains an IP address from the DHCP server that is configured for Auto Config, iDRAC uses the SCP to
configure the servers 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.
HTTP and HTTPS file sharing options are supported for iDRAC firmware 3.00.00.00 or later. Details of the HTTP or HTTPS
address need to be provided. In case the proxy is enabled on the server, the user needs to provide further proxy settings to
allow HTTP or HTTPS to transfer information. The -s option flag is updated as:
Table 10. Different Share Types and pass in values
-s (ShareType) pass in
NFS 0 or nfs
46 Setting up managed system