SolutionPack for EMC VPLEX
Table of Contents
This article applies to EMC ViPR SRM version 3.5.1.Back to Top
Compatible ViPR SRM version
- Arrays: model, name, status
- Directors: CPU, bytes in/out, exchange bytes, IOPS, serial number, health, model
- Clusters: Health, connectivity
- VirtualVolume: latency, read/write/ aborts/status
- Extents, Ports
- 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
- 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
Before you begin
- Before installing confirm that the VPLEX model is supported.
- ViPR SRM core modules must be up-to-date in all servers because not all module dependencies are validated during the SolutionPack installation or update process.
- Check that a sink file is listed for each of the directors on the cluster.
If the sink file is not listed for a director, check that the clusters and their associated directors are operating correctly. If the monitors are not created the SolutionPack can still be installed, but the performance data will be missing for the corresponding directors. For instance, if cluster-2 is down then you could still install the SolutionPack but it will not collect any performance data for directors on that cluster.
- While installing the SolutionPack for EMC VPLEX, ensure that cluster 1 IP and serial number are not interchanged with the cluster 2 IP and Serial Number.
- Log in.
- Click Administration.
- Click Centralized Management.
- Click SolutionPacks.
- Select SolutionPack Center.
- Navigate to SolutionPack for EMC VPLEX in the Storage section.
- Select the SolutionPack for EMC VPLEX in the Browse and Install SolutionPacks screen.
The steps below assume a typical four VM deployment.
- Enter an instance name.
- In the Data Collection field, select the Collector host.
- In the Reports field, select the Front End host.
- Click Next.
- In the
Data collection window, select a value for
If you select Add a new data collection, type information about the data collection. In Hostname or IP address to send data, use localhost on port 2020, which is the Collector host where the Load Balancer Connector is installed.
- Leave Enable alerting on data collected checked.
- Select a value for
Alerting on data collection.
If you select Add a new Alerting on data collection, type information about the alerting configuration. In Alerting Backend the hostname or IP address, select the Primary Backend host.
- Leave Enable Topology Backend on data collected checked.
- Select a value for
If you select Add a new Topology Service, type information about topology queries.
- In the Topology Service hostname or IP address field, select the Primary Backend host.
- Select a value for Web-Service Gateway.
- If you select Add new gateway, type information about the gateway.
- 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.
- Click Next.
- In the Administration Web-Service Instance field, select Default.
The SolutionPack installation begins. It will take approximately take three hours for data to start appearing on reports.
- Click Ok once installation is complete.
After you finish
Check that SolutionPack for EMC VPLEX has been able to successfully create virtual volume monitors:
- Login to the SRM collector host, where VPLEX collection block has been installed and navigate to the folder
/opt/APG/Collecting/Stream-Collector/emc-vplex/w4n_vplex/<VPLEX-cluster1_IP-Cluster2_IP>/virt-volumes on the collector appliance.
The equivalent Windows location is C:\Program Files\APG\Collecting\Stream-Collector\emc-vplex\w4n_vplex\<VPLEX-cluster1_IP-Cluster2_IP>\virt-volumes . Check to see if one log file per director has been created. The file will be deleted after it is parsed.
- 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).