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
From All Clients, select a client.
Go to Setup > Integrations > Integrations.
From Available Integrations, select Adapter > Hitachi VSP Ops Center.
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.
Click Install. The Hitachi VSP Ops Center Integration page displays the installed integration under the CONFIGURATION section.
Step 2: Configure the integration
From CONFIGURATION, click + Add.
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.
From the Credentials section, select Custom and enter the target deviceUsername and Password.
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.From the Metrics section, select the metrics you want.
In the Discovery Schedule section, select Recurrence Pattern to add one of the following patterns:
- Hourly
- Daily
- Weekly
- Monthly
In the Monitoring Schedule section, select the target device monitoring frequency. The default frequency is 30 minutes
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 Component | Metric Name | Metric Display Name | Units | Graph Enabled Yes/No |
---|---|---|---|---|
Dynamic Provision | hitachivsp_dynamic_provision_Total_Efficiency_Ratio | Hitachivsp dynamic provision total efficiency ratio | percentage(%) | No |
hitachivsp_dynamic_provision_Data_Reduction_Ratio | hitachivsp dynamic provision data reduction ratio | percentage(%) | No | |
hitachivsp_dynamic_provision_Software_Saving_Ratio | hitachivsp dynamic provision software saving ratio | percentage(%) | No | |
hitachivsp_dynamic_provision_Software_Comp_Ratio | hitachivsp dynamic provision software comp ratio | percentage(%) | No | |
hitachivsp_dynamic_provision_Software_Dedup_Ratio | hitachivsp dynamic provision software dedup ratio | percentage(%) | No | |
hitachivsp_dynamic_provision_Software_Match_Ratio | hitachivsp dynamic provision software match ratio | percentage(%) | No | |
hitachivsp_dynamic_provision_AC_Saving_Ratio | hitachivsp dynamic provision ac saving ratio | percentage(%) | No | |
hitachivsp_dynamic_provision_AC_Comp_Ratio | hitachivsp dynamic provision software saving ratio | percentage(%) | No | |
hitachivsp_dynamic_provision_Software_Saving_Ratio | hitachivsp dynamic provision ac comp ratio | percentage(%) | No | |
hitachivsp_dynamic_provision_AC_Match_Ratio | hitachivsp dynamic provision ac match ratio | percentage(%) | No | |
hitachivsp_dynamic_provision_Provisioning_Efficiency_Rate | hitachivsp dynamic provision provisioning efficiency rate | megabytes per second(MB/sec) | No | |
hitachivsp_dynamic_provision_Snapshot_Efficiency_Rate | hitachivsp dynamic provision snapshot efficiency rate | megabytes 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.