ViPR SRM 3.6 – SolutionPack for Storage Compliance Summary Sheet

Table of Contents


Learn how to install and configure the SolutionPack for Storage Compliance.

The SolutionPack for Storage Compliance allows users to manage compliance policies and rules and perform ESM matching. It also generates breach, track configuration changes, and policy reports. This enables the identification of any deviation from configuration best practices, including items that do not comply with the EMC ViPR SRM Release Notes. The compliance reports can be found under Operations > Storage Compliance. The Policy & Rule Management and ESM management screen can be launched by clicking on the Storage Compliance link in the Administration screen.

SolutionPack for Storage Compliance

SolutionPack for Storage Compliance

Back to Top

Technical specifications

Main reports

Breach Report

Track Configuration Changes

View Policies

Supported collection interfaces

For information about supported collection interfaces, refer to the ViPR SRM Support Matrix.

Back to Top

Where to find the latest SolutionPack software

Install the latest core software update for your product suite. SolutionPacks distributed with core software have a 30-day free evaluation period. If you plan to use the software longer than 30 days, you must install a SolutionPack license before the trial period ends.

This 30-day free evaluation only applies to new installations and is not available for upgraded installations. If you upgrade the core software and want to try a new SolutionPack, you must request a license for that SolutionPack by completing a Support Request (SR) form, which is available on the EMC Online Support website at

Back to Top

Installing the SolutionPack

Before you begin


  1. Click Administration.
  2. Click Centralized Management.
  3. Click SolutionPacks.
  4. Click SolutionPack Center.
  5. Select the SolutionPack in the Browse and Install SolutionPacks window.
  6. Click Install.
  7. Type the instance name.
  8. Assign a server for each component.
    In a typical four server deployment, the recommended servers are selected automatically.
  9. Click Next.
    The window displays compliance notification details.
  10. Select an item in Breach Notification Details. If you select Add a new Breach Notification Details, select an instance to receive breach notifications.
  11. Click Next.
  12. From Frontend Web service, select the Frontend host details.
  13. Select a Topology Service. To add a new gateway configuration, select Add a new Topology Service.
  14. Select a configuration for Breach Notification Details.
    Reuse the answers if another solution pack is using Alerting backend. Otherwise create a new configuration by selecting Add a new Breach Notification Details. In the Alerting Backend hostname or IP address, type the Primary Backend host. Type 2010 as the port.
  15. Select a configuration for Alert Consolidation Details.

    Reuse the answers if another solution pack is using Alert Consolidation Details. Otherwise create a new configuration by selecting Add a new Alert Consolidation Details. In the Alert Consolidation hostname field, type the Primary Backend host. Type 2040 as the port.

    If SOM RCA installation needs to be done, the alert consolidation configuration is required. For more details, refer to the "How to" article for SOM.

  16. Click Next.
  17. From Administration Web-Service Instance, select Default.
  18. In Compliance Backend Host, for 4 VM installations, enter the Primary Backend host.
  19. Click Next.
  20. Click Install.
  21. After Install of all the compliance components, click Ok.
    After installation is complete, you need to restart the Tomcat for Compliance Frontend to point to the configured Backend. If the Web Service password is changed, then the Compliance Backend block needs to be reconfigured.
Back to Top