ViPR SRM 3.6 – SolutionPack for Hitachi Device Manager Summary Sheet

Table of Contents

Overview

Learn how to install and configure SolutionPack for Hitachi Device Manager. The SolutionPack for Hitachi Device Manager accesses performance data, configuration data, and capacity planning data pertaining to the Volumes, Disks, Ports, Dynamically Provisioned Pools, and Parity Groups of Hitachi storage systems.

SolutionPack for Hitachi Device Manager

SolutionPack for Hitachi Device Manager

Back to Top

Technical specifications

Main reports

Data center utilization
Capacity utilization across all Hitachi arrays
Disk utilization
Capacity utilization across various types of disks
Storage system -> Detailed Information
Summary report containing inventory information of all Hitachi devices:
  • Parity groups
  • Volumes
  • Disks
  • Frontend controllers
Resources
Contains various reports connected to the array
  • Hosts
  • Logical groups
Analytics
  • Capacity Reports - Breaks down capacity across storage pool, tier, host for each HDS array
  • Performance collection troubleshooting - Helps troubleshooting performance data collection

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 Hitachi Device Manager for discovery and data collection

Identify the information required to support resource discovery and data collection before installing the SolutionPack for Hitachi Device Manager

ViPR SRM communicates with the Hitachi Device Manager to poll information for HDS arrays.

Procedure

  1. Identify account credentials with administrator privileges on the Hitachi Device Manager system
  2. Record the IP address/hostname for SSH and CIMOM communication
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 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 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.
  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. Leave Enable alerting on data collected checked.
  15. 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.
  16. From the Frontend Web service drop-down menu, select existing settings that have been specified for other components, or select Add a new Frontend Web service.
    If you select Add a new Frontend Web service, type information about the Frontend Web service.
  17. Leave Enable Topology Backend on data collected checked.
  18. 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.
  19. Select Enable Passive Host Discovery if you want the system to intelligently resolve hostnames from Hitachi Device Manager.
  20. Select Use advanced settings to configure polling and alert settings.
  21. Click Next.
    The window displays reports settings.
  22. In Administration Web-Service Instance, select an existing instance or create a custom instance.
  23. Click Install.
  24. Click Ok when the installation is complete.
  25. Click Discovery Center > Devices Management.
  26. Click Hitachi Device Manager.
  27. Click Add new device.
  28. Select the server and collector instance where you want to store the configuration details for this device.
  29. From the HDS type drop-down menu, select either Device Manager Collection or Embedded Performance Collection depending on the type of collection you are configuring. Enter a unique friendly name such as the host or IP address.
  30. Enter the hostname or IP address of the host, supply the login credentials, and specify the appropriate configuration settings.
  31. Click Test to validate the credentials.
  32. Click OK.
  33. Click Save.
Back to Top

Operational Issues

These are common problems and their workarounds, if possible.

LUNS not visible in Path details

LUNs from Hitachi AMS200 arrays do not appear in Path details and E2E reports. There is no workaround for this problem.

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