SolutionPack for IBM XIV

Table of Contents

Overview

This article explains how to install and configure the SolutionPack for IBM XIV. The SolutionPack for IBM XIV enables you to monitor the status and performance of your IBM XIV disk storage system, and access performance and configuration data pertaining to the volumes, disks, pools and ports of IBM XIV systems.

This article applies to EMC ViPR SRM version 3.5.1.

Back to Top

Technical Specifications

SolutionPack for IBM XIV version

Compatible ViPR SRM version

Main reports

Volumes IOPS
Reports the read and write requests over time for all XIV systems
ReadRequests
Reports the read requests over time for all XIV systems
WriteRequests
Reports the write requests over time for all XIV systems
Volumes Throughput (/s)
Reports the volumes read and write throughput over time for all XIV systems
ReadThroughput
Reports the volumes read throughput over time for all XIV systems
WriteThroughput
Reports the volumes write throughput over time for all XIV systems
Systems detailed per array capacity and performance reports
Reports capacity and performance per array.

Back to Top

Preparing your IBM XIV system for discovery and data collection

Identify the information required to support resource discovery and data collection before installing the SolutionPack for IBM XIV.

ViPR SRM communicates with IBM XIV using the CIM agent.

Procedure

  1. Ensure that the CIM agent is installed.
    Starting with IBM XIV Storage System V10.1.0, the CIM agent is pre-installed on the administrative module. The embedded CIM agent is automatically enabled and preconfigured.
  2. Identify the access credentials.
  3. Record this information for use when you install the SolutionPack.
Back to Top

Installing the SolutionPack

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

Procedure

  1. Log in.
  2. Click Administration.
  3. Click Centralized Management.
  4. Click SolutionPacks.
  5. Select SolutionPack Center.
  6. Select the SolutionPack for IBM XIV in the Browse and Install SolutionPacks screen.
  7. Click Install.
  8. Type the instance name.
  9. Assign a server for each component.
    In a typical four server deployment, the components are assigned as shown below:
    • Data collection: Collector
    • Reports: Front End
  10. Click Next.
  11. Set the Data Collection settings.
    1. In the Data collection field, select existing settings from the drop-down list, or add a new host by selecting Add a new data collection. If you add a new host, in Hostname or IP address to send data to, type LocalHost. The default port is 2020.
    2. Leave Enable alerting on data collected checked.
    3. In the Alerting on data collection field, select existing settings from the drop-down list, or add a new host by selecting Add a new Alerting on data collection. If you add a new host, in Alerting Backend hostname or IP address, type the hostname or IP address of the Primary Backend host. The default port is 2010.
    4. Leave Enable alerting on data collected checked.
    5. Leave Enable Topology Backend on data collected checked.
    6. In the Topology Service field, select existing settings from the drop-down list, or add a new topology service. If you add a new topology service, in Topology Service hostname or IP addressto, type LocalHost. In the Web-Service Gateway field, select an existing gateway or add a new gateway.
  12. Click Next.
  13. In Administration Web-Service Instance, select the Frontend host.
  14. Click Install.
Back to Top

Limitations

Discovery of LDAP users requires active GUI session

Due to limitations in the IBM software, discovery using the LDAP users account will not succeed unless there is an active IBM XIV GUI user session. The session must be active either for the corresponding LDAP user or for a storage administrator.

Max Storage Volume Response Time metric not collected

The SolutionPack does not collect the Max Storage Volume Response Time (ms) metric needed for the All > Explore > Hosts > [host] > Device Summary > [host] report.

No support for Used for File, LUN alias, and Replica 2 and Replica 3 details

‘Used for File’ metrics are not supported. Therefore, the respective columns in the following reports will be empty.

‘LUN Alias’ column is empty in the following report:

Remote replication data is not exposed through the SMI provider; therefore, Replica 2 and Replica 3 columns details will be empty in the following report:

Back to Top