Users Guide

● If Lifecycle Controller (LC) is busy with other operations, then firmware update task on a cluster node fails. To check if the
update failed because of LC being busy, check for the following error message in each node of the cluster at the following
path: C:\dell\suu\invcolError.log
Inventory Failure: IPMI driver is disabled. Please enable or load the driver and then
reboot the system.
As a workaround, shut down the server, remove the power cables, and then restart the server. After reboot, update the
firmware on clusters.
NOTE: For more information on CAU failure, check the status of the CAU job in Microsoft fail-over cluster manager tool
and see, Cluster-Aware Update best practices section of Microsoft documentation.
Failure of firmware update because of job queue being full
Firmware update job submitted from OMIMSSC to iDRAC fails, and the OMIMSSC main log displays the following error:
JobQueue Exceeds the size limit. Delete unwanted JobID(s).
As a workaround, manually delete the completed jobs in iDRAC, and retry the firmware update job. For more information about
deleting jobs in iDRAC, see iDRAC documentation at dell.com/support/home.
Failure of firmware update when using DRM update source
Firmware update job may fail if you are using DRM update source with insufficient access to the share folders. If the
Windows credential profile provided while creating DRM update source is not a part of domain administrator group or the
local administrator group, the following error message is displayed: Local cache creation failure.
As a workaround, perform the following:
1. After creating the repository from DRM, right-click on the folder, click Security tab, and then click Advanced.
2. Click Enable inheritance and select the Replace all child object permission entries with inheritable permission
entries from this object option, and then share the folder with Everyone with read-write permission.
Firmware update on components irrespective of selection
The same components on identical servers get updated during a firmware update irrespective of the selection of components
made on these individual servers. This behavior is observed for 12
th
and 13
th
generation of PowerEdge servers with Enterprise
license of iDRAC.
As a workaround, do one of the following:
● First apply updates for common components on identical servers, and then apply updates for specific components on
individual servers.
● Perform staged updates with planned outage time to accommodate the firmware update.
Failure to delete a custom update group
After scheduling any job on a server belonging to a custom update group, if the server is deleted from Microsoft console and
you synchronize registered Microsoft console with OMIMSSC, the server is removed from the custom update group and the
server is moved to a predefined update group. You cannot delete such custom update group, because it is associated with a
scheduled job.
As a workaround, delete the scheduled job from Jobs and Logs page, and then delete the custom update group.
Failure to update WinPE image
When you try to update the WinPE image, update job may fail with the following error message: Remote connection to
console failed.
As a workaround, run the DISM command to clean up all previously mounted images in Microsoft console, and then retry to
update the WinPE image.
Troubleshooting
99