Users Guide

Table Of Contents
Dell auto-discovery network setup specification
For information on auto-discovery error messages, descriptions, and response actions, see the Dell Auto-Discovery Network
Setup Specification document at delltechcenter.com
Troubleshooting the viewing and exporting of
Lifecycle Controller logs
When you view the Lifecycle Controller logs for a single system or a collection, the grid view could display the following values
-1 in the No. Column, Not Available in the Category, Description, and ID columns.
The possible reasons and resolutions are as follows:
Lifecycle Controller is running other tasks or processes and hence cannot retrieve the Lifecycle Controller logs for the
system or collection.
Resolution: Wait for sometime and retry retrieving or refreshing the logs for the system or collection to view the logs again.
Lifecycle Controller cannot access the given CIFS share.
Resolution: Check the permissions on CIFS share and make sure the share is accessible from Lifecycle Controller target
systems.
The Site Server cannot access the given CIFS share.
Resolution: Check the permissions on CIFS share and make sure the share is accessible from Site server.
The given CIFS share is read-only share.
Resolution: Provide the details for a share location with both read and write enabled.
The exported .XML file is not well formed.
Resolution: For more information, see the Dell Lifecycle Controller 2 Version 1.00.00 Users Guide available at dell.com/
support/home.
Upgrading the target system from Lifecycle Controller version 1.3 or 1.4 to Lifecycle Controller version 1.5.
Resolution: Export the Lifecycle Controller logs, run an Lifecycle Controller wipe through Unified Server Configurator,
reinstall Unified Server Configurator, and re-generate the Lifecycle Controller Logs.
Issues and resolutions
Issue 1
Issue: When you deploy an operating system on a target system with iDRAC configured in a shared network mode, the Windows
PE environment may fail to startup on the network drivers, causing the system to restart before reaching the task sequence.
Resolution: This is because the network does not assign IP addresses fast enough. To avoid this issue, ensure that you enable
Spanning Tree and Fast Link on the network switch.
Issue 2
Issue: If the Lifecycle Controller of a system is in use, the system is not discovered.
Resolution: If a system does not show up in a collection, verify whether the log file contains the following error message:
Lifecycle Controller in use. If it contains the error message:
1. Ensure that the system is not in Power On Self Test (POST) state. A system is in POST state after it is powered on and until
it boots to an operating system through any media.
2. Power off the system and wait for ten minutes for it to show up in the collection.
Troubleshooting
61