ViPR SRM 3.6.3.1 — SolutionPack for EMC ECS

Table of Contents

Overview

The SolutionPack for EMC ECS collects inventory, capacity, performance, and health metrics for object storage on EMC ECS 2.0 systems. Detailed metrics for the virtual data centers, nodes, and disks for object storage managed by ECS 2.0 are included. Collected data is displayed in easy-to-use reports in ViPR SRM 3.6.3 or later.

Licenses and installation scenarios

The SolutionPack for EMC ECS supports two licensing scenarios. Both require ViPR SRM 3.6.3 or later.

ECS Reporting for ECS 2.0
ECS Reporting is an optional feature of ECS 2.0. It provides reporting for ECS in a limited version of ViPR SRM 3.6.3 or later. The SolutionPack for EMC ECS installs the following features:
  • Basic set of ECS 2.0 reports into the Report Library
  • Consolidated alerts and health in the global Operations reports
ECS Reporting requires the VIPR_ECS_SP ELMS license embedded in the ViPR SRM license file. If you upgraded from ECS powered by ViPR 2.1, you have this license. For new ECS installations, you received a ViPR SRM license file containing this license with the ECS purchase.
Full EMC ViPR SRM 3.6.3 or later environment
Full ViPR SRM discovers, collect metrics for, and reports on an enterprise-wide storage environment. Global reports merge capacity, chargeback, storage usage, operational, and performance information across all storage platforms, providing a comprehensive view of the entire storage infrastructure. The SolutionPack for EMC ECS installs the following features:
  • Basic set of ECS 2.0 reports into the Report Library
  • Consolidated alerts and health in the global Operations reports
  • ECS object capacity metrics merged into the global capacity Dashboards and Explore reports
  • Additional inventory reports for ECS Namespaces and Buckets added to the Report Library
  • Chargeback reporting for ECS object storage, by Namespace and Bucket, including computed costs by service level
  • A new Bucket Service Level group based on replication policy, with cost assignments and capability to create custom service levels
To get all of the above features requires the VIPRSRM_ECS_TB ELMS license embedded in the ViPR SRM license file. You receive this license with the purchase of the SolutionPack for EMC ECS and ViPR SRM.

For information about installing license files, see Manage ViPR SRM Licensing.

Main reports

Summary Reports
Degraded or Bad Disks
Identifies rack and node location, disk ID, and affected storage pool. Provides drill-down into health and stress factors.
Degraded or Bad Nodes
Summarizes health statistics by node and supports drill-down into health and stress factors.
Health Dashboard/Virtual Data Centers
Shows general health and stress ratings; percentages of CPU usage, memory usage, and network usage; and network bandwidth rate. Provides drill-down capabilities into nodes, and then into services and disks of each node.
Health Dashboard/Remote Replication Status
Shows the local and remote virtual data center pairings and status of each. Supports drill-down into each replication group for graphs of the table columns.
Inventory Reports
Namespaces (available only with full ViPR SRM license)
For each namespace, provides bucket and object counts, objects created and deleted during the reporting period, amount of data uploaded and downloaded during the reporting period, namespace quota, and amounts and percentage of quota used. Supports drill-down into buckets within a namespace and other namespace details.
Nodes
By physical node and storage pool, shows number of associated disks, and amount of Usable, Used, and Available storage capacity. Also shows rack ID and version of node and supports drill-down into a node's disks.
Replication Groups
For each group, shows number of virtual data centers and buckets. Click a group name to display the storage pools in that group. Supports drill-down into nodes and disks.
Storage Pools
Summarizes number of nodes and number of disks in each storage pool, and shows total amount of Used and Available capacity per storage pool. Supports drill-down into nodes and then disks.
Virtual Data Centers
Provides the management IP address for each virtual data center, and summarizes Usable, Used, and Available capacity in various dashboard reports. Click a data center to see its capacity, storage pools, and nodes.
Performance Reports
Nodes
For each node, shows data transfer metrics for transactions, disks, and networks. Also shows transaction error rate per node. Supports drill-down into graphs for each column.
Storage Pools
For each storage pool, shows data transfer metrics for transactions, disks, and networks. Also shows transaction error rate per storage pool. Supports drill-down into graphs for each column.
Virtual Data Centers
For each virtual data center, shows data transfer metrics for transactions, disks, and networks. Also shows transaction error rate per virtual data center. Supports drill-down into graphs for each column.
Remote Replication Status
For each replication group, shows local and remote virtual data centers, ingress and egress data transfer rates, and percentage of progress on bootstrap and failover processes.
Capacity Reports
These reports show object capacity.
Configured Usable Capacity and Trends
Summarizes metrics for configured free, configured used, and reserved for system use. A trend report shows enterprise-wide historical usable capacity. Provides drill-down into storage pools and various graphs.
Object Count Trend
Shows enterprise-wide historical object count usage.
Used Capacity by Purpose
Summarizes used capacity by unprotected (not replicated), locally protected, remotely protected, and system used.
Storage Pools
Summarizes each storage pool, showing virtual data center, numbers of nodes and disks, and amount of usable, used, and available storage.
Operations Reports
Chargeback Reports (available only with full ViPR SRM license)
Chargeback by Namespace shows namespace usage by characteristics such as Locally vs Remotely protected, object counts, data downloads/uploads, and total cost . Click a row in the table to drill into chargeback details about a namespace, including:
  • Graphical representations of object counts, object activity, and used capacity for objects.
  • Chargeback by Service Level
  • Network Usage
  • Chargeback by Bucket, including computed costs
Health Dashboard
Shows general health and stress ratings; percentages of CPU usage, memory usage, and network usage; and network bandwidth rate. Provides drill-down capabilities into nodes, and then into services and disks of each node.
Situations to Watch
The following reports flag possible developing problems:
  • Buckets Near Quota
  • Degraded or Bad Disks
  • Degraded or Bad Nodes
  • Namespaces Near Quota

Supported collection interfaces

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

Back to Top

Obtaining and uploading the SolutionPack for EMC ECS

Before you begin

The SolutionPack for EMC ECS is distributed in the EMC ViPR SRM 3.6.3 Patch1.

Procedure

  1. Go to the following URL:
  2. Click the gray banner at the bottom of the window.
  3. Provide the requested registration information.
  4. Download the ViPR SRM 3.6.3 Patch 1 zip file.
  5. Unzip the file and extract the emc-ecs-3.6.3.1.pkg file to a location accessible to the ViPR SRM Frontend host.
    A bundled readme file describes installation scenarios for upgrade and new situations.
  6. Log in to the ViPR SRM Console.
  7. Click Administration > Centralized Management > Packages Management.
  8. Click Upload in the right pane.
  9. Click Choose File and navigate to the location where the emc-ecs-3.6.3.1.pkg file was unzipped.
  10. Click OK.
    The SolutionPack is now available for installation.
Back to Top

Installing the SolutionPack for EMC ECS

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 a note about Alert Consolidation.
  10. Click Next.
    The window displays pre-configured alert details.
  11. From the Alerting on data collection drop-down menu, select the Primary Backend host.
  12. Click Next.
    The window displays data collection details.
  13. 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.
  14. From the Alert Consolidation drop-down menu, select existing settings that have been specified for other components, or select Add a new Alert consolidation.
    If you select Add a new Alert consolidation, type information about the alerting configuration. In Alerting Backend hostname or IP address, specify the Primary Backend host.
  15. Select Use advanced settings to configure polling settings or to disable a polling type.
  16. In each polling period drop-down menu, select a polling period or select Disabled to turn off the polling.
  17. Click Next.
    The window displays reports settings.
  18. Click Install.
  19. Click Ok when the installation is complete.
  20. Click Discovery Center > Devices Management.
  21. Click EMC ECS.
  22. Click Add new device.
    For ECS, a device is a VDC, and the term ECS system refers to a VDC. A VDC consists of one or more ECS appliances (racks) with 4 or 8 nodes each and attached storage systems.
    In a multi-site federation of VDCs, provide information for each VDC as a separate device.
  23. Verify that the first two fields are correct for the collection instance.
  24. In Virtual Data Center name, type the VDC name as configured in ECS.
  25. In IP address or host name, provide the public IP address for one of the nodes in one of the ECS racks in the VDC. For example, use the public IP address for the first node in the first rack in the VDC.
  26. For Username and Password, provide the administrator credentials configured for the VDC.
    The authentication user account must have System Administrator privileges on the ECS system. On ECS, navigate to Manage > Users > Management Users > accountname, and make sure the System Administrator field is set to Yes.
  27. For Configured for remote replication, check this box if the VDC is part of a geo-replicated federation of VDCs.
    When you check this box, the Collect namespace and bucket data field appears.
  28. In Collect namespace and bucket data, check this box for only one of the VDCs in a geo-replicated federation of VDCs.
    This field configures the one VDC in the geo-replicated federation that provides the namespace and bucket metrics for reporting.
    Note Image
    Enabling namespace and bucket data from multiple VDCs in a geo-replicated federation causes duplicate counting and duplication of billing data.

  29. Click Test to validate the credentials.
  30. Click Ok.
  31. Click Save.
    It takes approximately take three hours for data to start appearing on reports from the new VDC.
  32. To add another VDC, click Add new device and provide information for another VDC.
    Note Image
    In a multi-site federation, add each VDC in the federation, but collect namespace and bucket data for only one of them.

Back to Top

Remove old ECS hosts from the Physical Host SP

This procedure applies if you are upgrading from ECS powered by ViPR 2.1.

In the older system, the ECS hosts were added manually to the Physical Host list and monitored by the Physical Host SolutionPack. In ECS 2.0, the ECS hosts are automatically monitored by the SolutionPack for ECS. You should remove the hosts from the Physical Host list.

Note Image
This step is optional. However, metrics will no longer be reported for these hosts from this location, so there is no benefit to leaving them.

Procedure

  1. In the ViPR SRM Console, navigate to Administration > Centralized Management > Discovery Center > Devices Management .
  2. Click in the first column for each ECS host.
  3. Click Delete, and then click Save.
Back to Top

Expand ECS

You can expand an existing VDC by adding more storage, more nodes, or more ECS racks, without any additional configurations in ViPR SRM.

A new VDC must be added into Discovery Center as a new device before ViPR SRM can collect metrics for it.

Procedure

  1. Navigate to Administration > Centralized Management > Discovery Center.
  2. Click EMC ECS.
  3. Click Add new device.
  4. Verify that the first two fields are correct for the collection instance.
  5. In Virtual Data Center name, type the VDC name as configured in ECS.
  6. In IP address or host name, provide the public IP address for one of the nodes in one of the ECS racks in the VDC. For example, use the public IP address for the first node in the first rack in the VDC.
  7. For Username and Password, provide the administrator credentials configured for the VDC.
    The authentication user account must have System Administrator privileges on the ECS system. On ECS, navigate to Manage > Users > Management Users > accountname, and make sure the System Administrator field is set to Yes.
  8. For Configured for remote replication, check this box if the VDC is part of a geo-diverse federation of VDCs.
    When you check this box, the Collect namespace and bucket data field appears.
  9. In Collect namespace and bucket data, check this box for only one of the VDCs in a geo-replicated federation of VDCs.
    Configure one VDC in the federation to provide the namespace and bucket metrics.
    Note Image
    Enabling namespace and bucket data from multiple VDCs in a geo-replicated federation causes duplicate counting and duplication of billing data.

  10. Click Test to validate the credentials.
  11. Click Ok.
  12. Click Save.
    It takes approximately take three hours for data to start appearing on reports from the new VDC.
  13. To add another VDC, click Add new device and provide information for another VDC.
    Note Image
    In a replicated federation, add each VDC in the federation, but configure namespace and bucket data for only one of them.

Back to Top

Limitations

The following items apply to a full ViPR SRM installation:

The following items apply if you upgraded from ECS powered by ViPR:

Back to Top