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 January 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.
The Customer had recently upgraded FOS on the Brocade Switches from 6.x to 7.4.1d, and intermittently CPU utilization is going over threshold value 80%.
Customer gets the below error in his VPLEX Collecting logs even though all data is populated in reports.
The soft-link is missing to the newly added library that was deployed during the update of the MySQL database. The SRM 4.2.1 has an update SLES OS that is missing the libtinfo.so.5 file and will cause the mysql-client to fail.
ViPR SRM 4.1 : How to manually upgrade ViPR SRM
Found that there were over 900 connections to port 2013 (some dynamic) that were in different states.
This is due to some special characters being used in password, when entering credentials (in Discovery Center) such as @, $, & and #.
An incremental or other type of license was generated with a different Software ID (SWID) assigned to the new, secondary license.
Severs that are discovered fully within ViPR SRM and Fully Resolve within DNS do not present information within the Graphs for CPU, Memory, and File.
From SRM go to SNMP Device Discovery and make sure you can discover capabilities. If this fails you have a network issue, port or Data Domain is not setup correctly.
|Note: Please click “Follow” at the top right of this screen (when logged in) to receive update notifications.|