Users Guide

Troubleshooting

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.

Duplicate VRTX chassis group gets created

When modular servers that were previously in another chassis are added to a VRTX chassis and discovered, the modular servers

carry previous chassis service tag information and create a duplicate VRTX chassis group in the appliance.

To resolve, do the following:

1. Remove a modular server from one chassis, and add it in another chassis. For more information, see Server modules section in

Dell PowerEdge VRTX Enclosure Owner's Manual.

2. Configure CMC. For more information, see Installing and Setting Up CMC in Chassis Management Controller Version 2.1 for

Dell PowerEdge VRTX User's Guide, available at dell.com/support /home.

After you do the preceding tasks, if there are duplicate chassis group entries, then as a workaround, do the following:

1. Enable CSIOR and reset iDRAC on the newly added modular server.

2. Manually delete all the servers in the VRTX chassis group, and then rediscover the servers.

Exporting configuration profile of another server after IP address is

changed

After an Export Server Profile job on a server is scheduled, if the IP address of this server is assigned to another server, then the

appliance exports the server profile of this new server.

As a workaround, cancel the Export Server Profile job, rediscover the server whose IP address has changed, and then schedule the

Export Server Profile job on this server.