ViPR SRM 3.6 – SolutionPack for IBM SAN Volume Controller/Storwize Summary Sheet

Table of Contents

Overview

Learn how to install and configure the SolutionPack for IBM SAN Volume Controller/Storwize . The IBM System Storage SAN Volume Controller (SVC) is a member of the IBM Storwize family, which provides storage virtualization with a single point of control for storage resources.

The SolutionPack for IBM SAN Volume Controller/Storwize enables you to generate real-time and historical reports and access capacity and performance details to gain insight into the management of the underlying Storwize storage environment.

SolutionPack for IBM SAN Volume Controller/Storwize

SolutionPack for IBM SAN Volume Controller/Storwize

Back to Top

Technical Specifications

Main reports

Virtual Storage Dashboard
Drill-down report that provides details about virtual storage information of the Virtual Disks such as Configured Usable, Virtual Disks Usable, Virtual Disks Unused, Virtual Volume Usable, Virtual Volume Used, and Virtual Volume Free.
Clusters
Drill-down report that provides details about each cluster such as cluster nodes, virtual volumes, virtual disks, quorum disks, virtual pools, host association, path details, and connectivity.
Performance Reports
Drill-down report that provides details about read and write requests, read and write throughput on Virtual Disks, and Virtual Volumes for all SVC Clusters.
Capacity Reports
Drill-down report that provides a further breakdown of aggregated capacities such as Configured Usable, Virtual Disks Usable, Virtual Disks Unused, Virtual Volume Usable, Virtual Volume Used, Virtual Volume Free, and Usable Capacity by Pools.
Port Inventory
Drill-down report that provides details of ports per cluster node such as port connectivity, speed, and availability.
Inactive Devices and Components
Drill-down report that provides details of devices and components which have not been recently discovered.

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.

Back to Top

Preparing your SolutionPack for IBM SAN Volume Controller/Storwize for discovery and data collection

Identify the information required to support resource discovery and data collection before installing the SolutionPack for IBM SAN Volume Controller/Storwize .

Before you begin

  • Confirm that the IBM SVC model and version are supported.
  • ViPR SRM core modules must be up-to-date on all servers because not all module dependencies are validated during the SolutionPack installation or update process.
  • An SMI-S provider must be running on the IBM SVC server on port 5989.

Procedure

  1. Record the IBM SVC/Storwize cluster IP address and hostname (for SSH and CIMOM communication).
  2. Record the username and password for the cluster.
    Note: All performance, topology, and capacity metrics are supported for users who are members of the "Administrator," "SecurityAdmin," or "Monitor" user group. Performance data (such as CPU usage and port traffic statistics of non-configuration nodes) are not supported for users who are members of the "Service" or "CopyOperator" user group.
Back to Top

Installing the SolutionPack

After you log in as an administrator, you can install a SolutionPack from Centralized Management.

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 existing settings that have been specified for other components, or select Add a new alerting data collection.
    If you select Add a new alerting on data collection, type information about the alerting configuration. In Alerting Backend hostname or IP address, specify 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. In Administration Web-Service Instance, select an existing instance or create a custom instance.
  18. Click Install.
  19. Click Ok when the installation is complete.
  20. Click Discovery Center > Devices Management.
  21. Click IBM SAN Volume Controller/Storwize.
  22. Click Add new device.
  23. Select the server and collector instance where you want to store the configuration details for this device, and then enter the hostname or IP address of the host, supply the login credentials, and specify the appropriate configuration settings.
  24. Leave Enable performance synchronization checked.
    Enable performance synchronization allows ViPR SRM to collect and report performance statistics across all of the nodes. The performance statistics files are copied from the non-config nodes to the config node, and the copied files are purged after they are processed. None of the original performance statistics on any node are purged. Disabling performance synchronization will allow collection and reporting only on the config node.
  25. Click Test to validate the credentials.
  26. Click OK.
  27. Click Save.
Back to Top

Limitations

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 Modules.
  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 SignalWait Time metric with the properties of device and IP, type name=='SignalWaitTime' 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> - <physical_host_ID>
  5. Expand Log Files and click the View File icon to review the configuration error messages.
Back to Top