ViPR SRM 3.6 – SolutionPack for EMC® VPLEX Summary Sheet

Table of Contents

Overview

Learn how to install and configure the SolutionPack for EMC VPLEX. The SolutionPack for EMC VPLEX collects performance, topology, and capacity data from your VPLEX systems and displays the data in easy-to-use reports within ViPR SRM.

With this SolutionPack, you can unify your view of multiple VPLEX systems, including physical storage to virtual storage relationships. Capacity reports, such as Thick, Thin, Allocated and Not Allocated, help you to improve the availability of business critical applications and services by ensuring that those applications have the storage resources they need to operate effectively.

SolutionPack for EMC VPLEX

SolutionPack for EMC VPLEX

Back to Top

Technical specifications

Main reports

SolutionPack / EMC VPLEX
Overview dashboard
Back-end Throughput (IOPS)
Reports the Back-end throughput (IOPS) for all VPLEX systems
Front-end Throughput (IOPS)
Reports the Front-end throughput (IOPS) for all VPLEX systems
Front-end Bandwidth (KB/s)
Reports the Front-end bandwidth (KB/s) for all VPLEX systems
Local Storage Capacity
Reports the overall storage capacity, including key indicators related to Capacity and Volumes
Distributed Storage Capacity
Reports the overall distributed storage capacity for all VPLEX systems
Shared Storage Capacity
Reports the overall shared storage capacity for all VPLEX systems
Clusters
Drill-down report containing a summary of all clusters, including the cluster name, version, management IP, directors count, arrays count and virtual volumes count
Performance Reports
Drill-down report that reports Directors Processor (Global), Directors Processor (per CPU), and the Heap Used (%)
Capacity Reports
Drill-down report containing key indicators of Host to Physical Array End-To-End View, Capacity per Array and Thick versus Thin
Port Inventory
Summarizes the ports on VPLEX systems
TopN Storage View Reports
Drill-down report containing key indicators of the TopN Storage Views per Capacity, IOPs and Throughput
Distributed Storage
Summarizes the distributed storage devices on VPLEX systems
Inactive Device and Components reports
Shows devices & sub-components which haven't been updated in more than 24 hours

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 http://support.emc.com.

Back to Top

Installing the SolutionPack

Before you begin

Procedure

  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 pre-configured alert details.
  10. From the Alerting on data collection drop-down menu, select the Primary Backend host.
  11. Click Next.
    The window displays data collection details.
  12. From the Data collection drop-down menu, select existing settings that have been specified for other components, or select Add a new data collection.
    If you select Add a new data collection, type information about the data collection. In Hostname or IP address to send data to, use localhost on port 2020, which is the Collector host where the Load Balancer Connector is installed.
  13. Leave Enable Topology Backend on data collected checked.
  14. From the Topology Service drop-down menu, select existing settings that have been specified for other components, or select Add a new Topology Service.
    If you select Add a new Topology service, provide information about the topology service and the web service. In Topology Service hostname or IP address, specify the Primary Backend.
    From the Web-Service Gateway drop-down menu, select existing settings that have been specified for other components, or select Add new gateway. If you select Add new gateway, provide information about the web-service gateway where the topology service resides.
  15. Select Use advanced settings to configure polling settings.
  16. Click Next.
    The window displays reports settings.
  17. Click Install.
  18. Click Ok when the installation is complete.
  19. Click Discovery Center > Devices Management.
  20. Click VPLEX.
  21. Click Add new device.
  22. In the VPLEX section, provide the cluster host and authentication details for your VPLEX system.
    The default username for the VPLEX is service and the default password is Mi@Dim7T.
    It is important to enter the cluster information correctly, clusters are mapped to their correct number. Interchanging cluster IPs and SN results in a failure to collect performance data.
    Be sure to select the correct VPLEX type while adding the device. If you are adding a VPLEX Metro or VPLEX Geo, select the Geo/Metro VPLEX type from the drop-down and enter both VPLEX cluster details. If you are adding a VPLEX Local, select the Local VPLEX type from the drop-down and enter the VPLEX cluster details. Do not add a Geo or Metro VPLEX System as two separate Local VPLEX Systems.
  23. Click Test to validate the credentials.
  24. Click Ok.
  25. Click Save.
    It will take approximately take three hours for data to start appearing on reports.

After you finish

Check that SolutionPack for EMC VPLEX has been able to successfully create virtual volume monitors:

  1. To ensure that virtual volume performance monitors are created, you can run the following command from the management server where these monitors were created: ll /monitoring/directors/*/*/*PERPETUAL*/*/file

    This command should list a file for each of the director (including directors on both cluster-1 and cluster-2).

Back to Top

Limitations

This SolutionPack does not support IBM DS arrays, HDS arrays, or HPXP arrays.

Only encapsulated virtual volumes are supported. LVM virtual volumes are not supported.

Chargeback, path details, and end-to-end reports only support encapsulated virtual volumes. Virtual Volumes created using logical volume management is not supported.

When an underlying virtual disk, on which the virtual volume is created, is also contributing to other virtual volumes, VPLEX and Host path details show incorrect values in the Storage View column for that particular virtual volume. Instead of listing only the Storage Views that it belongs to, it shows a pipe separated list of all the Storage Views that the underlying virtual disk is contributing to.

Back to Top

Confirming report creation

After you install a SolutionPack, you can view its reports.

To view the reports:

Procedure

  1. Go to User Interface > Report Library.
  2. Click the SolutionPack to view its reports.

Results

It may take up to an hour to display all relevant information in these reports.

Back to Top

Troubleshooting

Report display problems

Back to Top

What to do if data does not appear in any reports

Procedure

  1. After the completion of at least three collection cycles, verify if data is populating into the reports. If there is still no data in the reports, continue to the next step.
  2. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to the next step.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Running a scheduled task to import data into reports

After you push a new configuration into a collector, a scheduled task runs and populates the reports with new data. You can manually run the scheduled task to import the data more quickly.

Before you begin

Allow at least three polling cycles to pass before manually running the scheduled task.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Scheduled Tasks.
  4. Click Database.
  5. Select the import-properties-Default task.
  6. Click Run Now.
  7. Confirm success in running the task in the Last Result and Last Result Time columns.
Back to Top

What to do if data does not appear in some reports

Procedure

  1. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
  2. Search for the metric in the database.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Searching for metrics in the database

You can verify that a metric is being collected and used for reporting when you search and find the metric in the database.

Procedure

  1. Go to the Administration page.
  2. Under Modules, click Management of Database Metrics.
  3. On the Metric Selection page, create the filter, type the number of results, and select the properties to display for the metric.
    For example, to list up to 100 results of the Capacity metric with the properties of device and IP, type name=='Capacity' in the Filter field, 100 in the Maximum results field, and select device and IP for the Properties to show.
  4. Click Query.
    A list of the metric results appears. If nothing displays, the metric is not being collected.
Back to Top

Viewing collector errors in the Collector-Manager log files

Review the Collector-Manager log files to troubleshoot problems with data collection.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Collecting.
  4. Click the Collector-Manager for your collector instance.
    Collector-Manager::<Collector-Manager instance> - <host_ID>
  5. Expand Log Files and click the View File icon to review the configuration error messages.
Back to Top