Supported Versions
Ops Center Analyzer 10.6.0-00
REST API: API version 10.3.0
Gateway version: 9.0 HF cg or higher

Hitachi VSP Ops Center Analyzer provides visibility and data analysis of heterogeneous IT resources across the application’s full data path, from hypervisors, servers, and SAN switches to shared storage resources.

You can monitor network switches, fabrics, and corresponding ports managed through OpsCenter Analyzer

Step 1: Install the integration

  1. From All Clients, select a client.

  2. Go to Setup > Integrations > Integrations.

  3. From Available Integrations, select Adapter > Hitachi VSP Ops Center.

  4. From Install Hitachi VSP Opscenter Integration, enter:

    • Name: Name of the integration.
    • Upload Logo: Hitachi device logo.
    • Gateway Profile: Select a gateway management profile to associate with the client.
  5. Click Install. The Hitachi VSP Ops Center Integration page displays the installed integration under the CONFIGURATION section.

Step 2: Configure the integration

  1. From CONFIGURATION, click + Add.

  2. On the Create Adapter Configuration page, enter:

    • Name: Configuration name.
    • Protocol:
      • HTTPS: Secure connection.
      • HTTP: If the connection is not secure.
    • Opscenter Port: Port number associated with the IP address of the device.
    • VSP IP Address: Target device IP address.
    • Agent for RAID Instance Name: VSP instance name as configured in RAID agent.
    • OpsCenter IP Address: IP address of Ops Center.
  3. From the Credentials section, select Custom and enter the target deviceUsername and Password.

  4. From the Resource Types & Metrics section, select the metrics and Availability.
    The Resource Types & Metrics section displays the target device resource type such as Hitachi VSP.

  5. From the Metrics section, select the metrics you want.

  6. In the Discovery Schedule section, select Recurrence Pattern to add one of the following patterns:

    • Hourly
    • Daily
    • Weekly
    • Monthly
  7. In the Monitoring Schedule section, select the target device monitoring frequency. The default frequency is 30 minutes

  8. Click Save.

After saving the integration, the Hitachi VSP Ops Center resources are discovered and monitoring is enabled specified by the configured metric criteria.

Step 3: View the HITACHI VSP Opscenter details

The Hitachi VSP Ops Center is successfully integrated and displayed in the Infrastructure > Hitachi VSP category. Click the name to view details.

Supported Metrics

VSP ComponentMetric NameMetric Display NameUnitsGraph Enabled Yes/No
Dynamic Provisionhitachivsp_dynamic_provision_Total_Efficiency_RatioHitachivsp dynamic provision total efficiency ratiopercentage(%)No
hitachivsp_dynamic_provision_Data_Reduction_Ratiohitachivsp dynamic provision data reduction ratiopercentage(%)No
hitachivsp_dynamic_provision_Software_Saving_Ratiohitachivsp dynamic provision software saving ratiopercentage(%)No
hitachivsp_dynamic_provision_Software_Comp_Ratiohitachivsp dynamic provision software comp ratiopercentage(%)No
hitachivsp_dynamic_provision_Software_Dedup_Ratiohitachivsp dynamic provision software dedup ratiopercentage(%)No
hitachivsp_dynamic_provision_Software_Match_Ratiohitachivsp dynamic provision software match ratiopercentage(%)No
hitachivsp_dynamic_provision_AC_Saving_Ratiohitachivsp dynamic provision ac saving ratiopercentage(%)No
hitachivsp_dynamic_provision_AC_Comp_Ratiohitachivsp dynamic provision software saving ratiopercentage(%)No
hitachivsp_dynamic_provision_Software_Saving_Ratiohitachivsp dynamic provision ac comp ratiopercentage(%)No
hitachivsp_dynamic_provision_AC_Match_Ratiohitachivsp dynamic provision ac match ratiopercentage(%)No
hitachivsp_dynamic_provision_Provisioning_Efficiency_Ratehitachivsp dynamic provision provisioning efficiency ratemegabytes per second(MB/sec)No
hitachivsp_dynamic_provision_Snapshot_Efficiency_Ratehitachivsp dynamic provision snapshot efficiency ratemegabytes per second(MB/sec)No

Risks, Limitations & Assumptions

  • The availability is shown unknown for few resources even if it is enabled on the respective resource metrics. This is because of the presence of multiple native type resources under the same resource type.