ViPR SRM: Top Services Topics

This document contains the list of Top Services Topics for ViPR SRM, identified by EMC Support as the most trending topics for the month of February 2019:

It is recommended that you also check for important information such as advisories (ETAs, ESAs), and other key resources on the Support by Product pages on the EMC Online Support portal.


ViPR SRM: Conflict Errors in DPA Collecting Logs

There are errors in the DPA collecting logs that indicate a conflict with either a report, schedule, time period or time period window. This will cause not all the required reports chosen in the SRM SolutionPack to be created on the DPA GUI.

ViPR SRM: Seeing severe errors in VMware collecting logs

After upgrading to ViPR SRM 4.0.1, user started noticing these errors in the VMware collecting logs. The reports do not seem to be affected. 

ViPR SRM; Can Not Discover Data Domain Array

ViPR SRM; Can Not Discover Data Domain Array

ViPR SRM:System Upgrade from SRM 4.0.1 to 4.1 stuck and not proceeding

System upgrade from SRM 4.0.1 to SRM 4.1 started. The upgrade procedure runs for some time and it is now hung and the upgrade does not complete. The status of the upgrade shows for 3 servers as "Preparing server for upgrade" while for the other servers status shows as "Waiting for remaining nodes...".

ViPR SRM : Some VPLEX arrays are not showing performance

The Customer upgraded from 3.6.2to 4.0.2 it was noticed we did not have performance data for 5 VPLEX Arrays associated to one Collector Host.

ViPR SRM, VNX M&R, Watch4net | How to stop, start, or restart services

ViPR SRM, VNX M&R, Watch4net | How to stop, start, or restart services

ViPR SRM: Can not discover Unity array OS 4.2.x

ViPR SRM 4.0.2 only support the API version 5.0. VNX Unity OS 4.2.x uses API version 6.0    

ViPR SRM: ViPR SRM Compliance Backend Service on Primary Backend is not starting after upgrade to v 4.2 SP1[4]

This issue is seen only on setups which are upgraded from older versions like 3.x to 4.x and now to 4.2.1.  This will not affect any newer versions which were deployed from version 3.7 onwards and then upgraded.   


Note: Please click “Follow” at the top right of this screen (when logged in) to receive update notifications.