Users Guide

Table Of Contents
Troubleshooting
Topics:
Empty cluster update group does not get deleted during autodiscovery or synchronization
Discovery jobs not submitted
Duplicate VRTX chassis group gets created
Exporting configuration profile of another server after IP address is changed
Failure applying RAID configuration
Failure of creation of update source
Failure of firmware update because of job queue being full
Failure of firmware update while using DRM update source
Failure of a scheduled job on an update group
Failure of firmware update on cluster update group
Failure of firmware update on 11th generation of servers
Failure to connect to FTP using system default update source
Failure to create a repository during a firmware update
Failure to delete a custom update group
Failure to export LC logs in CSV format
Failure to view LC logs
Failure to export server profiles
Firmware update on a few components irrespective of the selection
IG installation issue while running multiple instances of the installer on the same server
Importing server profile job gets timed out after two hours
Hypervisor deployment failure
Hypervisor deployment failure due to driver files retained in library share
Latest inventory information is not displayed even after firmware update
SCVMM error 21119 while adding servers to active directory
Hypervisor deployment fails for 11th generation PowerEdge blade servers when using Active Directory
RAID configuration failure for virtual disks with RAID10
Configuration of RAID failure due to configuration of hot spares on software RAID S130
Empty cluster update group does not get deleted
during autodiscovery or synchronization
When a cluster group is discovered in the appliance, a cluster update group gets created in the Maintenance Center with
all the servers listed in the cluster update group. Later, if all the servers are removed from this cluster through SCVMM, and
an autodiscovery or synchronization with SCVMM operation is performed, the empty cluster update group is not deleted in
Maintenance Center.
As a workaround, to delete the empty server group, rediscover the servers.
Discovery jobs not submitted
When you press the backspace key to dismiss an error message on the discovery screen, subsequent discovery jobs are not
submitted for backend processing.
As a workaround, close the current discovery screen and relaunch the discovery screen from the Inventory page. Submit the
new discovery job after entering the required inputs.
12
46 Troubleshooting