White Papers

54 Zero-touch, bare-metal server provisioning using the Dell EMC iDRAC with Lifecycle Controller Auto Config
7 Troubleshooting Auto Config issues
Issue
Resolution
The server fails to restart or turn on
after enabling Auto Config.
1) Check the job queue and determine the status of the Server Configuration
Profile import job. If the job failed, check the job status message for
indications about why the job failed. Some examples of causes of job
failure:
 iDRAC is unable to access network share
 file not located on the network share
2) Check the job queue for an import job created. If no import job ID is created
within ten minutes after enabling Auto Config, there was likely an issue
reading the DHCP configuration file. Check the Linux DHCP configuration
file or Windows DHCP configuration panels for typos and input format. If
corrections are made to the Linux or Windows DHCP server, be certain to
restart the DHCP services.
The import job ID failed because of
inability to access the network share.
Check for these common issues:
 If a firewall is enabled, ensure that the correct ports are open for NFS and
CIFS and that the iDRAC IP address can access that subnet.
 Ensure that permissions to access the NFS or CIFS share are properly set.
 For NFS shares, Auto Config currently does support secured access;
ensure everyone is enabled to access the NFS share.
 For CIFS, ensure that the username and password being passed in the
DHCP configuration file have read and write access to the share.
When using the Windows DHCP server,
the Auto Config import job fails by
indicating that file is not found.
Check for Option 60 and ensure there is a white space character before the first
option.