White Papers

Troubleshooting issues in hardware and OS deployment on servers monitored by OpenManage Essentials
53 Server Hardware Provisioning and OS Deployment by using Dell EMC OpenManage Essentials
22.3 Troubleshoot the virtual I/O pool creation in OpenManage Essentials
Troubleshooting the creating or editing an identity type:
• Ensure that the identity type definition meets the requirements for that identity type. See Types of
identities.
• If you cannot edit a virtual I/O pool, it may be locked. To unlock (and enable editing), see Locking and
unlocking the Virtual I/O pool.
• If a virtual I/O pool runs out of identities to assign, a warning message is displayed during the
assignment process in the deploy wizard. In these scenarios, you can increase the size of the virtual
pool. See Increasing the size of the Virtual I/O Pool.
22.4 Troubleshoot the template deployment
The task execution history details provide troubleshooting information.
• Redfish streaming related messages are shown in case of any error.
• If the file share is used for servers, ensure that settings are entered correctly. See Troubleshooting
the file share.
• 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. See Additional
resources. The details tab also contains the results of applying individual attributes.
• In case of a ‘Cannot connect to server’ error, ensure that the target credentials are correct.
• In case of a ‘Server is being configured’ error, wait and retry later. If the task still fails, the server
may need a restart and/or iDRAC reset.
• If there is a server restart failure, restart the server by using the iDRAC GUI.
• 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 the attribute registry in Additional resources.
• If the task is not completed, the task will be timed out and exit after 30 minutes of inactivity. You need
to execute the task again. The restart and/or iDRAC reset may be necessary.