FAQ

Creation of incorrect VRTX chassis group after server
discovery
When modular servers that were previously in another chassis are added to a VRTX chassis and discovered in OMIMSSC, the modular
servers carry previous chassis service tag information. Hence, a VRTX chassis group with old chassis information is created in the
Appliance instead of the latest chassis information.
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.
Empty cluster update group not deleted during
autodiscovery or synchronization
When a cluster is discovered in OMIMSSC, 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.
Failure to perform maintenance-related tasks on
rediscovered servers
When you delete a server or all the servers in an update group from OMIMSSC, and rediscover them you cannot perform any other
operations on these servers like updating rmware, exporting and importing LC logs, exporting and importing server proles.
As a workaround, after rediscovering the deleted server or servers, perform rmware updates using the Deploy Operational Template
feature in Server View and for other maintenance scenarios use iDRAC.
14
Discovery, synchronization and inventory scenarios in OMIMSSC