White Papers

1. Make sure the identity type definition meets the requirements for that identity type. See the
Types
of identities section.
2. If you can’t edit a virtual IO pool, it is likely locked. To unlock it (and enable editing) see the How to
lock or unlock a Virtual IO Pool section.
3. If a virtual IO pool runs out identities to assign, a warning message appears during the assignment
process in the deploy wizard. The size of a virtual IO pool can be increased. See the
How to
increase the size of a Virtual IO Pool section.
19.4 Troubleshooting deploying a template
The task execution history details provide troubleshooting information.
1. Check that the file share settings are entered correctly (see the Troubleshooting the file share
section.
2. Double click the task execution history entry (or right click and select ‘Details’) to see the task
execution history details. The ‘Results’ tab displays information on task activities and any errors that
occurred. Errors with an ‘LC’ error code can be looked up in the iDRAC documentation (link in the
Additional resources
section). The details tab also contains the results of applying individual
attributes.
3. If there is a ‘cannot connect to server’ error, make sure the target credentials are correct.
4. For a ‘server is being configured’ error, wait and retry later. If the task still fails, the server may need
a reboot and/or iDRAC reset.
5. For a server reboot failure, reboot the server via the iDRAC interface.
6. If an attribute fails to be set, there may be an attribute dependency conflict. In some cases, re-
running the task allows additional configuration settings to be applied to targets. For more details
about attribute dependencies, refer to the attribute registry (link in the Additional resources
section).
7. If the task does not complete, the task will timeout and exit after 30 minutes of inactivity. Rerun
the task. A reboot and/or iDRAC reset may be necessary.
19.5 Troubleshooting auto deploying templates
Each time the ‘Deploy Configuration to Undiscovered Devices’ task runs, it looks for Service Tags in the
‘Auto Deployment’ list. The following situations may be encountered:
1. There are no Service Tags in the ‘Auto Deployment’ list. In this case, the task exits, and no entry is
created in the task execution history grid for that run.
2. The task finds one or more Service Tags in the ‘Auto Deployment’ list for devices that have not
been discovered by OME yet. In this case, a task execution history entry is created and it indicates
why the Service Tag was not processed.
3. The task finds one or more Service Tags in the ‘Auto Deployment’ list for devices that have been
discovered by OME. It creates tasks named ‘Deploy Configuration to Undiscovered Devices - Task
– timestamp’ to deploy to those devices. In this case, an execution history entry is created and the
entry specifies which Service Tags were processed for deployment.
47 Stateless Deployment with Dell OpenManage Essentials | Revision A00