Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Configuring the RAID Agent to monitor Hitachi Enterprise Storage Systems

Before adding the Hitachi Enterprise Storage probe, you choose and configure the RAID Agent based on your monitoring environment and data collection requirements to monitor VSP, VSP F series, VSP G series, VSP 5000 series, or HUS VM.

Determining the appropriate agent for collecting data

You need to determine the agent to be used by the Hitachi Enterprise Storage probe from one of the following, depending on your environment. Both agents collect information from storage systems.

  • RAID Agent

    This agent is installed with Ops Center Analyzer

  • Tuning Manager - Agent for RAID

    This agent is used in environments where Tuning Manager had previously been used to monitor storage system performance.

The following table shows the correspondence between the environment you are using and the agent to be used by the Hitachi Enterprise Storage probe:

Monitoring environmentUse this AgentGo to this section
New installation of Ops Center AnalyzerRAID Agent installed with Ops Center AnalyzerSetting up RAID Agent
Migration from Tuning Manager to Ops Center AnalyzerRAID Agent installed with Ops Center AnalyzerSetting up RAID Agent
Migration from Tuning Manager to Ops Center Analyzer; both currently in useStorage systems previously monitored by Tuning Manager will now be monitored by Ops Center Analyzer.Tuning Manager - Agent for RAIDSetting up Tuning Manager - Agent for RAID
Newly installed storage systems to be monitored by Ops Center Analyzer.RAID Agent installed with Ops Center AnalyzerSetting up RAID Agent
Previous Tuning Manager and Ops Center Analyzer environment now only Ops Center AnalyzerRAID Agent installed with Ops Center AnalyzerSwitching from Tuning Manager - Agent for RAID to RAID Agent

The following figure shows the flow of monitoring Ops Center Analyzer when Tuning Manager is used in combination with Ops Center Analyzer:

GUID-3CA29047-804F-4E4E-A7CC-DE2A5B1C02F1-low.gif

RAID Agent and Tuning Manager - Agent for RAID cannot connect to the same storage system. Select one of the following:

  • To monitor storage systems that are newly installed, connect the storage systems to RAID Agent and monitor the storage systems in Ops Center Analyzer.
  • To monitor existing storage systems that were monitored by Tuning Manger using Ops Center Analyzer, use Tuning Manager - Agent for RAID.

Do not uninstall the Tuning Manager server if Tuning Manager - Agent for RAID is being used. The Tuning Manager server is necessary to maintain Tuning Manager - Agent for RAID.

Workflow for adding the Hitachi Enterprise Storage probe

To monitor VSP, VSP F series, VSP G series, VSP 5000 series, or HUS VM by using Ops Center Analyzer, you need to use the following procedure to add the Hitachi Enterprise Storage probe to Analyzer probe server.

  1. Verify the collection methods supported by the monitored storage systems, and determine the collection method to be used by the agent when collecting information.

    For details, see Selecting the data collection method.
  2. Add the Hitachi Enterprise Storage probe to be used to collect information from the monitored storage systems to the Analyzer probe server.

    • When collecting information by using RAID Agent bundled with Ops Center Analyzer

      Set up RAID Agent and add the Hitachi Enterprise Storage probe to Analyzer probe server. For details, see Setting up RAID Agent.

    • When collecting information by using Tuning Manager - Agent for RAID

      Set up Tuning Manager - Agent for RAID and add the Hitachi Enterprise Storage probe to Analyzer probe server. For details, see Setting up Tuning Manager - Agent for RAID.

    • When you want to change the agent used by the Hitachi Enterprise Storage probe that has already been added

      Change the settings for the Hitachi Enterprise Storage probe that has already been added to Analyzer probe server. For details, see Switching from Tuning Manager - Agent for RAID to RAID Agent.

Setting up RAID Agent

The Hitachi Enterprise Storage probe collects data from the monitored Hitachi Enterprise storage systems (VSP, VSP F series, VSP G series, VSP 5000 series, or HUS VM) using RAID Agent, which is bundled with Ops Center Analyzer.

The workflow for adding the Hitachi Enterprise Storage probe depends on the data collection method. You select the data collection method by specifying the Access Type when you create a RAID Agent instance environment, which designates the method used by the RAID Agent to collect data from the storage system.

RAID Agent supports the following values for Access Type:

  • Access Type: 1

    Data collection using command device and SVP

  • Access Type: 2

    Data collection using command device and REST API

  • Access Type: 3

    Data collection using SVP and REST API

  • Access Type: 4

    Data collection using REST API

Selecting the data collection method

The method for collecting data differs depending on the combination of the storage system configuration and the agent. Specify the collection method in Access Type when you create an instance environment. You can specify only one Access Type for each storage system.

Consider the above when determining the collection method. The procedure for setting up the Hitachi Enterprise Storage probe varies depending on the value specified in Access Type.
Performance data collection methods (for RAID Agent)

GUID-345D9017-D305-4A49-81D7-4973E0FEE379-low.gif

Data collection methods

The data collection method varies depending on the storage system.

To determine which method is supported by your storage systems, use the following table:

Storage systems to be monitoredData collection methodAccess Type to select
Command devicesSVPREST API of the storage system

HUS VM

VSP

VSP F400

VSP F600

VSP F800

VSP F1500

VSP G200

VSP G400

VSP G600

VSP G800

VSP G1000

VSP G1500

UsedUsed-1

VSP F350*

VSP F370*

VSP F700*

VSP F900*

VSP G350*

VSP G370*

VSP G700*

VSP G900*

VSP 5000 series

UsedUsed-1
Used-Used2
-UsedUsed3
--Used4

*: For details on the microcode version required to collect performance data using the REST API, see Monitoring target requirements.

Legend:

-: Not used

Performance data that can be collected

Depending on the data collection method, you can collect different types of performance data.

If RAID Agent bundled with Ops Center Analyzer will be used to monitor VSP F350, F370, F700, F900, VSP G350, G370, G700, or G900, VSP 5000 series, select the Access Type based on the information in the following table:

Do you use a network that uses Fibre Channel (use a command device)?Do you use the SVP?Do you want to track the following details?Access Type to select
YesYes
  • Storage system performance and configuration
  • Virtual IDs for parity groups
  • Pool names
  • Tier information
  • Saving capacity and ratio information
  • Current Capacity in License window
1
YesNo
  • Storage system performance and configuration
  • Pool names
  • Tier information
  • Saving capacity and ratio information
2
NoYes
  • Storage system performance and configuration
  • Virtual IDs for parity groups
  • Current Capacity in License window
3
NoNo
  • Storage system performance and configuration
4

The number of types of performance data to collect varies depending on the Access Type, as follows:

Access Type is 1 > Access Type is 2 > Access Type is 3 > Access Type is 4

This means that, if Fibre Channel is used for the network, more detailed information can be viewed about the storage system. In addition, if the selected Access Type is 1, the storage system can be monitored at the same level as the following storage systems:

HUS VM, VSP, VSP F400, F600, F800, F1500, VSP G200, G400, G600, G800, G1000, G1500

For details about performance data, see the Hitachi Ops Center Analyzer REST API Reference Guide and the Hitachi Ops Center Analyzer Detail View Metrics Reference Guide.

Workflow for setting up the Hitachi Enterprise Storage probe (when using RAID Agent)

To monitor Hitachi Enterprise Storage Systems by using RAID Agent, use the following workflow to add the Hitachi Enterprise Storage probe.

CautionBefore changing the agent used to monitor a storage system from Tuning Manager - Agent for RAID to RAID Agent, make sure that the instance of Tuning Manager - Agent for RAID is not running.

The operations differ depending on the combination of methods for collecting performance data (Access Type).

GUID-F9437028-9E50-424D-8DB1-D5C892F1A50A-low.gif

Configuring RAID Agent for data collection using command devices and SVP

Use this method to collect all available information about storage system capacity and performance metrics. To use this data collection method, you must specify 1 for Access Type when you create the RAID Agent instance environment.

Configuring Analyzer probe server

Confirm RAID Agent

Confirm that the RAID Agent and the Analyzer probe server are installed on the same host. RAID Agent is installed when the Analyzer probe server is installed.

Confirm RAID Manager LIB

If you used the installer to install Analyzer probe server, confirm that RAID Manager Library is installed on the RAID Agent host. In an environment that was created by deploying the OVA file for Analyzer probe server, the RAID Manager Library is already installed.

Configuring storage systems

Create user accounts for a storage system

On the storage system, verify that a user account to be used by RAID Agent was created. The user account must meet the following conditions:

  • SVP

    The account must belong to a user group that has been assigned one of the following roles:

    • Storage administrator (viewing)
    • Storage administrator (initial setup)
    • Storage administrator (system resource management)
    • Storage administrator (provisioning)
    • Storage administrator (performance management)
    • Storage administrator (local backup management)
    • Storage administrator (remote backup management)
  • Performance Monitor

    The user account must belong to a user group that has been assigned the Storage administrator (performance management) role.

For details about how to create a user account for a storage system, see the appropriate documentation for your storage system.

Set up a command device

Verify that a command device exists in the storage system. For details about command devices, see the appropriate documentation for the storage system you are using.

The following restrictions apply to command devices used by RAID Agent:

  • If a virtual ID is set on a command device, that command device cannot be monitored by RAID Agent.
  • Command devices must be defined as RAW devices. RAW devices must comply with the following rules:
    • Command devices for the ZFS file system cannot be used.
    • Do not create file systems in the logical devices specified as the command devices.
    • Do not mount file systems to the logical devices specified as the command devices.
  • If any of the following conditions are met, RAID Agent cannot obtain performance data:
    • A remote command device is used.
    • A virtual command device is used.
    • VMware Fault Tolerance (VMware vSphere Fault Tolerance) is used.
Configure Performance Monitor

Make sure that the following settings have been configured for the instance of Performance Monitor for the storage system. For details on how to configure these settings and the values that can be specified for each setting, see the applicable Performance Monitor documentation for your storage system.

Setting

Description

Monitor switch

Enable the monitoring switch setting

Monitoring-target CUs

Set the logical devices (on a CU basis) from which you want to collect performance data. This setting is not required if you use HUS VM.

Monitoring-target WWNs

Set the performance data collection-target WWNs.

Sampling interval

Set the interval to short range.

Connecting the RAID Agent host and the storage system

Verify that the RAID Agent host and the storage system are connected by the following methods:

  • TCP/IP connection for the SVP
  • Fibre Channel, Fibre Channel over Ethernet (FCoE), or iSCSI connection for the command device
Some functions cannot be run while performance data is being collected using the SVP. If you execute these functions while performance data is being collected using the SVP of RAID Agent, either the data collection or the execution of one or more functions will fail. Before using a function for which the problem occurs, run the htmsrv stop command (/opt/jp1pc/htnm/bin/htmsrv stop -all) to temporarily stop the RAID Agent instance.

The following are examples of tasks that cannot be performed while performance data is being collected using the SVP:

  • Data migration in Device Manager
  • Displaying the following Storage Navigator windows:
    • Server Priority Manager window
    • Volume Migration window
    • Usage Monitor window of True Copy (for HUS VM and VSP)
    • Usage Monitor window of Universal Replicator (for HUS VM and VSP)
  • Using the export tools described in the Performance Monitor manuals

Configuring access to the command device from RAID Agent

If performance data is to be collected using a command device, make sure that the command device of the monitored storage system can be accessed from the host on which RAID Agent is installed.

  1. Set an LU path to a logical device designated as the command device.

    Set the LU path to the host in which RAID Agent is installed on the logical device designated as the command device. If the installation destination of RAID Agent is a guest OS of VMware ESXi, set the LU path to the host OS.

    Access to the command device of RAID Agent might temporarily occupy resources, such as the processor, of the storage system on the LU path. Therefore, when setting an LU path, make sure that the processor to be used is not being used by business applications that generate steady I/O traffic.

  2. Ensure that the command device can be accessed from a guest OS.

    This procedure is necessary if RAID Agent is installed on a guest OS of VMware ESXi. For details, see the VMware ESXi documentation.

    Use VMware vSphere Client to add a device to the guest OS. By doing so, if you designate a command device as the device to be added, the command device can be accessed from the guest OS.

    When configuring settings to add a device, make sure that the following requirements are met:

    • Device type: Hard disk
    • Disk selection: Raw device mapping
    • Compatibility mode: Physical

      Virtual disks (including VMware VVols) cannot be used for the command device.

  3. Make sure that the command device can be accessed from the host on which RAID Agent is installed.

    Run the jpctdlistraid command on the host on which RAID Agent is installed, and confirm that the information you set on the command device is output:
    /opt/jp1pc/tools/jpctdlistraid
    TipIn a Linux host environment, rescanning a disk device might change a device file name of the form /dev/sd. To prevent this, use the WWID based form of the device file name (/dev/disk/by-id/scsi-hexadecimal-WWID). To specify the WWID based file name:
    1. Use the jpctdlistraid command to display the /dev/sd form of the device file name:

      /opt/jp1pc/tools/jpctdlistraid
    2. Use the ls command to search for the symbolic links managed in the /dev/disk/by-id directory for the WWID device file name mapped to the corresponding /dev/sd file name.

      For example:

      ls -la /dev/disk/by-id/* | grep sdc
    3. Use the output as the Command Device File Name.

Creating an instance environment

To collect data from the Hitachi Enterprise Storage probe, you must create a RAID Agent instance environment on the host on which Analyzer probe server is installed.

Procedure

  1. On the Analyzer probe server, run the jpcinssetup command with the service key and instance name specified. Instance names must be no longer than 32 bytes, and only half-width alphanumeric characters (A-Z, a-z, 0-9) are allowed.

    For example, to create an instance environment for the instance named 35053 for RAID Agent, run the following command:

    /opt/jp1pc/tools/jpcinssetup agtd -inst 35053
  2. Set up the instance information for the storage system you will monitor.

    To use the default value (or no value), press Enter.

    The following table lists the instance information to specify.

    Item

    Description

    Storage model

    Specify the storage type.

    • 11: VSP
    • 12: VSP G1000, G1500, VSP F1500
    • 13: VSP 5000 series
    • 21: HUS VM
    • 22: VSP G200, G400, G600, G800, VSP F400, F600, F800
    • 23: VSP G350, G370, G700, G900, VSP F350, F370, F700, F900

    Serial No

    Specify the serial number of the storage system.

    Access Type

    Specify 1.

    If a value other than 13 and 23 is specified for Storage model, 1 is automatically specified.

    Command Device File Name

    Specify the device file name of the storage system specified for Serial No, from among the command devices in the list output by using the /opt/jp1pc/tools/jpctdlistraid command. RAID Agent uses this command device to collect information about the storage system.

    The /dev/sd* form of the device file name might be changed by rescanning the disk device. The best practice is to use the WWID based form of the device file name. See Configuring access to the command device from RAID Agent for details about assigning a WWID based device file name.

    Unassigned Open Volume Monitoring1

    Specify Y to monitor a logical device or a parity group for which an open system emulation type has been set and that has not been mapped to a port.

    • If no value is entered, the default value Y is set.

    • If you enter a value other than Y, y, N, or n, the system prompts you to enter a value again.

    Mainframe Volume Monitoring1

    Specify Y to monitor a logical device for which the emulation type used for a mainframe is set.

    • For HUS VM, mainframe emulation is not supported. Mainframe volumes are excluded from monitoring when an HUS VM is monitored.

    • If no value is entered, the default value Y is set.

    • If you enter a value other than Y, y, N, or n, the system prompts you to enter a value again.

    Ops Center Analyzer does not obtain information about mainframe devices. For this reason, you cannot identify the mainframe host with which a logical device is associated.

    SVP IP Address or Host Name

    Specify the IP address or host name of the SVP that manages the storage system that was specified for Serial No.

    Storage User ID for SVP

    Specify the user ID of the user account that was created to access the target storage system using the SVP.

    Storage Password for SVP

    Specify the password of the user account that was created to access the target storage system using the SVP.

    SVP Port No

    Specify the port number if Storage model is set to 22 or 23. You can specify a value from 0 to 65535. The default value is 1099.

    This value is the same as the initial value for the RMIIFRegist port number of the storage system. To change the port number of the storage system, see the storage system manual that explains how to change or initialize the port number to be used with the SVP.

    SVP HTTPS Port No

    If 22 or 23 is specified for Storage model, specify the port number that is used for connection using the HTTPS protocol, from a host on which RAID Agent is installed, to the SVP. You can specify a value from 0 to 65535. The default value is 443.

    This value is the same as the initial value for the MAPPWebServerHttps port number of the storage system. To change the port number of the storage system, see the storage system manual that explains how to change or initialize the port number to be used with the SVP.

    Java VM Heap Memory setting Method

    Specify the method to be used for setting the required memory size for the Java VM. The default value is 1.

    However, in a large-scale environment that exceeds an assumed value2, if you specify 1 for this item, processing might end abnormally because of insufficient memory. For this reason, for a large-scale environment, specify 2.

    • To specify a method that automatically calculates the required memory size based on the maximum number of volumes: 1
    • To specify a method where the user specifies the memory size: 2

    Maximum number of Volumes

    If you specified 1 for Java VM Heap Memory setting Method, specify the maximum number of volumes to be created on the target storage system. The required memory size for the Java VM will be automatically specified based on this setting.

    You can specify a value in the range from 1000 to 99999. The default value is 4000.

    Java VM Heap Memory for SVP

    If you specified 2 for Java VM Heap Memory setting Method, specify the required memory size for the Java VM. The default value is 1.
    • 1: 0.5 GB
    • 2: 1.0 GB
    • 3: 2.0 GB
    • 4: 4.0 GB
    • 5: 8.0 GB

    Notes:

    1. Depending on the microcode version of the storage system, you might not be able to use the Mainframe Volume Monitoring or Unassigned Open Volume Monitoring function even though you enabled the setting (and verified that it is enabled).

    2. The following values are assumed for the environment when the required memory size is calculated based on the maximum number of volumes and the data is collected by using the SVP:

    • Number of LU paths: 0
    • Sampling interval (in minutes): 1
  3. When configuring multiple instances, repeat steps 1 and 2 for each instance.

  4. Make sure that RAID Manager LIB is installed.

  5. Before you start operation in an instance environment, run the jpctdchkinst command to verify the instance settings.

    The command references the set instance information. (This command checks whether the settings allow information to be collected from the storage system monitored by RAID Agent.)
    /opt/jp1pc/tools/jpctdchkinst –inst instance-name
  6. (Optional) Configure the collection-time definition file (conf_refresh_times.ini).

    See Changing the configuration information collection time, and set the time for collecting configuration information. By specifying this setting, you can prevent the issue of not collecting performance data when there is a large amount of configuration information to collect from the storage system.

  7. Run the following command to start the RAID Agent instance services:

    /opt/jp1pc/htnm/bin/htmsrv start -all
    NoteYou must wait for approximately one hour to add the Hitachi Enterprise Storage probe after adding an instance on the RAID agent.

Next steps

Configuring RAID Agent for data collection using command device and REST API

Use this method to collect all available information about storage system capacity performance metrics through both Fibre Channel and IP connections without using an SVP. To use this data collection method, you must specify 2 for Access Type when you create the RAID Agent instance environment.

Configuring Analyzer probe server

Confirm RAID Agent

Confirm that the RAID Agent and the Analyzer probe server are installed on the same host. RAID Agent is installed when the Analyzer probe server is installed.

Confirm RAID Manager LIB

If you used the installer to install Analyzer probe server, confirm that RAID Manager Library is installed on the RAID Agent host. In an environment that was created by deploying the OVA file for Analyzer probe server, the RAID Manager Library is already installed.

Configuring storage systems

Create user accounts for a storage system

On the storage system, verify that a user account to be used by RAID Agent was created. The user account must meet the following conditions:

  • REST API

    The user account must belong to a user group for which All Resource Groups Assigned is enabled. If the user group is assigned to one of the following roles, All Resource Groups Assigned is enabled.

    • Security Administrator (View Only)
    • Security Administrator (View & Modify)
    • Audit Log Administrator (View Only)
    • Audit Log Administrator (View & Modify)
    • Support Personnel (Vendor Only)

For details about how to create a user account for a storage system, see the appropriate documentation for your storage system.

Set up a command device

Verify that a command device exists in the storage system. For details about command devices, see the appropriate documentation for the storage system you are using.

The following restrictions apply to command devices used by RAID Agent:

  • If a virtual ID is set on a command device, that command device cannot be monitored by RAID Agent.
  • Command devices must be defined as RAW devices. RAW devices must comply with the following rules:
    • Command devices for the ZFS file system cannot be used.
    • Do not create file systems in the logical devices specified as the command devices.
    • Do not mount file systems to the logical devices specified as the command devices.
  • If any of the following conditions are met, RAID Agent cannot obtain performance data:
    • A remote command device is used.
    • A virtual command device is used.
    • VMware Fault Tolerance (VMware vSphere Fault Tolerance) is used.
Acquire a server certificate

Acquire the server certificate of the storage system. This server certificate is required for server authentication, as well as for encryption by using HTTPS communication between RAID Agent and the storage system. If you are not using server authentication, you do not need to acquire a server certificate.

Connecting the RAID Agent host and the storage system

Verify that the RAID Agent host and the storage system are connected by the following methods:

  • TCP/IP connection for the GUM (CTL)
  • Fibre Channel, Fibre Channel over Ethernet (FCoE), or iSCSI connection for the command device

Configuring access to the command device from RAID Agent

If performance data is to be collected using a command device, make sure that the command device of the monitored storage system can be accessed from the host on which RAID Agent is installed.

  1. Set an LU path to a logical device designated as the command device.

    Set the LU path to the host in which RAID Agent is installed on the logical device designated as the command device. If the installation destination of RAID Agent is a guest OS of VMware ESXi, set the LU path to the host OS.

    Access to the command device of RAID Agent might temporarily occupy resources, such as the processor, of the storage system on the LU path. Therefore, when setting an LU path, make sure that the processor to be used is not being used by business applications that generate steady I/O traffic.

  2. Ensure that the command device can be accessed from a guest OS.

    This procedure is necessary if RAID Agent is installed on a guest OS of VMware ESXi. For details, see the VMware ESXi documentation.

    Use VMware vSphere Client to add a device to the guest OS. By doing so, if you designate a command device as the device to be added, the command device can be accessed from the guest OS.

    When configuring settings to add a device, make sure that the following requirements are met:

    • Device type: Hard disk
    • Disk selection: Raw device mapping
    • Compatibility mode: Physical

      Virtual disks (including VMware VVols) cannot be used for the command device.

  3. Make sure that the command device can be accessed from the host on which RAID Agent is installed.

    Run the jpctdlistraid command on the host on which RAID Agent is installed, and confirm that the information you set on the command device is output:
    /opt/jp1pc/tools/jpctdlistraid
    TipIn a Linux host environment, rescanning a disk device might change a device file name of the form /dev/sd. To prevent this, use the WWID based form of the device file name (/dev/disk/by-id/scsi-hexadecimal-WWID). To specify the WWID based file name:
    1. Use the jpctdlistraid command to display the /dev/sd form of the device file name:

      /opt/jp1pc/tools/jpctdlistraid
    2. Use the ls command to search for the symbolic links managed in the /dev/disk/by-id directory for the WWID device file name mapped to the corresponding /dev/sd file name.

      For example:

      ls -la /dev/disk/by-id/* | grep sdc
    3. Use the output as the Command Device File Name.

Creating an instance environment

To collect data from the Hitachi Enterprise Storage probe, you must create a RAID Agent instance environment on the host on which Analyzer probe server is installed.

  1. On the Analyzer probe server, run the jpcinssetup command with the service key and instance name specified. Instance names must be no longer than 32 bytes, and only half-width alphanumeric characters (A-Z, a-z, 0-9) are allowed.

    For example, to create an instance environment for the instance named 35053 for RAID Agent, run the following command:

    /opt/jp1pc/tools/jpcinssetup agtd -inst 35053
  2. Set up the instance information for the storage system you will monitor.

    To use the default value (or no value), press Enter.

    The following table lists the instance information to specify.

    Item

    Description

    Storage model

    Specify the storage type.

    • 13: VSP 5000 series
    • 23: VSP G350, G370, G700, G900, VSP F350, F370, F700, F900

    Serial No

    Specify the serial number of the storage system.

    Access Type

    Specify 2.

    Command Device File Name

    Specify the device file name of the storage system specified for Serial No, from among the command devices in the list output by using the /opt/jp1pc/tools/jpctdlistraid command. RAID Agent uses this command device to collect information about the storage system.

    The /dev/sd* form of the device file name might be changed by rescanning the disk device. The best practice is to use the WWID based form of the device file name. See Configuring access to the command device from RAID Agent for details about assigning a WWID based device file name.

    Unassigned Open Volume Monitoring1

    Specify Y to monitor a logical device or a parity group for which an open system emulation type has been set and that has not been mapped to a port.

    • If no value is entered, the default value Y is set.

    • If you enter a value other than Y, y, N, or n, the system prompts you to enter a value again.

    Mainframe Volume Monitoring1

    Specify Y to monitor a logical device for which the emulation type used for a mainframe is set.

    • For HUS VM, mainframe emulation is not supported. Mainframe volumes are excluded from monitoring when an HUS VM is monitored.

    • If no value is entered, the default value Y is set.

    • If you enter a value other than Y, y, N, or n, the system prompts you to enter a value again.

    Ops Center Analyzer does not obtain information about mainframe devices. For this reason, you cannot identify the mainframe host with which a logical device is associated.

    SVP IP Address or Host Name

    If 13 is specified for Storage model, specify the IP address or host name of the SVP that manages the storage system that was specified for Serial No.

    GUM(CTL) IP Address or Host Name (Primary)

    If 23 is specified for Storage model, specify the IP address or the host name (for which name resolution is possible) of the GUM (CTL) of the storage system that was specified for Serial No. The default value is blank. Connections with the connection destination set for GUM(CTL) IP Address or Host Name (Primary) will be prioritized.

    Note that you do not need to specify both GUM(CTL) IP Address or Host Name (Primary) and GUM(CTL) IP Address or Host Name (Secondary).

    GUM(CTL) IP Address or Host Name (Secondary)

    Storage User ID for REST-API

    Specify the user ID of the user account that was created for accessing the target storage system using the REST API.

    Storage Password for REST-API

    Specify the password of the user account that was created for accessing the target storage system using the REST API.

    REST-API Protocol

    Specify the protocol to be used for accessing the target storage system using the REST API. The default value is 1.
    • To use HTTP: 1
    • To use HTTPS: 2
    Java VM Heap Memory setting Method

    Specify the method to be used for setting the required memory size for the Java VM. The default value is 1.

    However, in a large-scale environment that exceeds an assumed value2, if you specify 1 for this item, processing might end abnormally because of insufficient memory. For this reason, for a large-scale environment, specify 2.

    • To specify a method that automatically calculates the required memory size based on the maximum number of volumes: 1
    • To specify a method where the user specifies the memory size: 2

    Maximum number of Volumes

    If you specified 1 for Java VM Heap Memory setting Method, specify the maximum number of volumes to be created on the target storage system. The required memory size for the Java VM will be automatically specified based on this setting.

    You can specify a value in the range from 1000 to 99999. The default value is 4000.

    Java VM Heap Memory for REST-API

    If you specified 2 for Java VM Heap Memory setting Method, specify the required memory size for the Java VM. The default value is 1.
    • 1: 128 MB
    • 2: 256 MB
    • 3: 512 MB
    • 4: 1.0 GB
    • 5: 2.0 GB
    • 6: 4.0 GB
    • 7: 8.0 GB

    Notes:

    1. Depending on the microcode version of the storage system, you might not be able to use the Mainframe Volume Monitoring or Unassigned Open Volume Monitoring function even though you enabled the setting (and verified that it is enabled).

    2. The following values are assumed for the environment when the required memory size is calculated based on the maximum number of volumes and the data is collected by using the REST API:

    • Number of LU paths per LDEV: 4
    • Number of SPM settings per LDEV: 4
    • Number of host groups assigned to each LDEV: 1
    • Number of WWNs assigned to the hosts of each LDEV: 2
  3. When configuring multiple instances, repeat steps 1 and 2 for each instance.

  4. Make sure that RAID Manager LIB is installed.

  5. Before you start operation in an instance environment, run the jpctdchkinst command to verify the instance settings.

    The command references the set instance information. (This command checks whether the settings allow information to be collected from the storage system monitored by RAID Agent.)
    /opt/jp1pc/tools/jpctdchkinst –inst instance-name
  6. (Optional) Configure the collection-time definition file (conf_refresh_times.ini).

    See Changing the configuration information collection time, and set the time for collecting configuration information. By specifying this setting, you can prevent the issue of not collecting performance data when there is a large amount of configuration information to collect from the storage system.

  7. Run the following command to start the RAID Agent instance services:

    /opt/jp1pc/htnm/bin/htmsrv start -all
    NoteYou must wait for approximately one hour to add the Hitachi Enterprise Storage probe after adding an instance on the RAID agent.

Importing a certificate to the truststore for RAID Agent

To enable verification of a storage system's server certificate in RAID Agent, import the storage system's certificate to the truststore for RAID Agent, and then edit the ipdc.properties file.

Before you begin

  • You must have the root permission of the OS to do this operation.

  • You must prepare the storage system's certificate.

    If you use a certificate issued by a certificate authority, the certificates of all the certificate authorities, from the certificate authority that issued the storage system's server certificate to the root certificate authority, must be connected in a chain of trust.

  • If the storage system's certificate already exists in the truststore, delete the existing certificate before importing new certificate. To delete the existing certificate, execute the following command:
    rm /opt/jp1pc/agtd/agent/instance-name/jssecacerts

Procedure

  1. Execute the following command to import the storage system's certificate to the truststore:

    /opt/jp1pc/htnm/HBasePSB/jdk/bin/keytool –import –alias alias-name –file certificate-file-name –keystore truststore-file-name –storepass access-password-for-truststore

    • For alias-name, specify a name that makes it possible to determine which storage system the server certificate belongs to.
    • For certificate-file-name, specify the absolute path of the location in which the certificate is stored.
    • For truststore-file-name, specify the following absolute path:

      /opt/jp1pc/agtd/agent/instance-name/jssecacerts

    • For access-password-for-truststore, specify a password of your choice.
  2. Enable verification of the server certificate by changing the following properties in the file /opt/jp1pc/agtd/agent/instance-name/ipdc.properties. If there is a hash mark (#) at the beginning of a property line, delete that hash mark.

    • ssl.check.cert:true
    • ssl.check.cert.self.truststore:true
    • ssl.check.cert.hostname:true
      Note
      • To check the name of the host of the SSL certificate, specify a host name that can be resolved for GUM(CTL) IP Address or Host Name in the RAID Agent instance information. If you cannot specify a host name that can be resolved, specify false because the host name cannot be verified.
      • If the web server certificate is not a wildcard certificate, specify false, because the host name cannot be verified.
  3. Execute the command jpctdchkinst and confirm the instance settings:

    /opt/jp1pc/tools/jpctdchkinst –inst instance-name
  4. Execute the following commands to restart the services of the RAID Agent instance:

    /opt/jp1pc/htnm/bin/htmsrv stop -all
    /opt/jp1pc/htnm/bin/htmsrv start -all

Next steps

Configuring RAID Agent for data collection using SVP and REST API

Use this method to collect all available information about storage system capacity and performance metrics through an IP network connection. To use this data collection method, you must specify 3 for Access Type when you create the RAID Agent instance environment.

Configuring Analyzer probe server

Confirm RAID Agent

Confirm that the RAID Agent and the Analyzer probe server are installed on the same host. RAID Agent is installed when the Analyzer probe server is installed.

Configuring storage systems

Create user accounts for a storage system

On the storage system, verify that a user account to be used by RAID Agent was created. The user account must meet the following conditions:

  • SVP

    The account must belong to a user group that has been assigned one of the following roles:

    • Storage administrator (viewing)
    • Storage administrator (initial setup)
    • Storage administrator (system resource management)
    • Storage administrator (provisioning)
    • Storage administrator (performance management)
    • Storage administrator (local backup management)
    • Storage administrator (remote backup management)
  • REST API

    The user account must belong to a user group for which All Resource Groups Assigned is enabled. If the user group is assigned to one of the following roles, All Resource Groups Assigned is enabled.

    • Security Administrator (View Only)
    • Security Administrator (View & Modify)
    • Audit Log Administrator (View Only)
    • Audit Log Administrator (View & Modify)
    • Support Personnel (Vendor Only)
  • Performance Monitor

    The user account must belong to a user group that has been assigned the Storage administrator (performance management) role.

For details about how to create a user account for a storage system, see the appropriate documentation for your storage system.

Configure Performance Monitor

Make sure that the following settings have been configured for the instance of Performance Monitor for the storage system. For details on how to configure these settings and the values that can be specified for each setting, see the applicable Performance Monitor documentation for your storage system.

Setting

Description

Monitor switch

Enable the monitoring switch setting

Monitoring-target CUs

Set the logical devices (on a CU basis) from which you want to collect performance data. This setting is not required if you use HUS VM.

Monitoring-target WWNs

Set the performance data collection-target WWNs.

Sampling interval

Set the interval to short range.

Acquire a server certificate

Acquire the server certificate of the storage system. This server certificate is required for server authentication, as well as for encryption by using HTTPS communication between RAID Agent and the storage system. If you are not using server authentication, you do not need to acquire a server certificate.

Connecting the RAID Agent host and the storage system

Verify that the RAID Agent host and the storage system are connected by the following methods:

  • TCP/IP connection for the SVP
  • TCP/IP connection for the GUM (CTL)
Some functions cannot be run while performance data is being collected using the SVP. If you execute these functions while performance data is being collected using the SVP of RAID Agent, either the data collection or the execution of one or more functions will fail. Before using a function for which the problem occurs, run the htmsrv stop command (/opt/jp1pc/htnm/bin/htmsrv stop -all) to temporarily stop the RAID Agent instance.

The following are examples of tasks that cannot be performed while performance data is being collected using the SVP:

  • Data migration in Device Manager
  • Displaying the following Storage Navigator windows:
    • Server Priority Manager window
    • Volume Migration window
    • Usage Monitor window of True Copy (for HUS VM and VSP)
    • Usage Monitor window of Universal Replicator (for HUS VM and VSP)
  • Using the export tools described in the Performance Monitor manuals

Creating an instance environment

To collect data from the Hitachi Enterprise Storage probe, you must create a RAID Agent instance environment on the host on which Analyzer probe server is installed.

  1. On the Analyzer probe server, run the jpcinssetup command with the service key and instance name specified. Instance names must be no longer than 32 bytes, and only half-width alphanumeric characters (A-Z, a-z, 0-9) are allowed.

    For example, to create an instance environment for the instance named 35053 for RAID Agent, run the following command:

    /opt/jp1pc/tools/jpcinssetup agtd -inst 35053
  2. Set up the instance information for the storage system you will monitor.

    To use the default value (or no value), press Enter.

    The following table lists the instance information to specify.

    Item

    Description

    Storage model

    Specify the storage type.

    • 13: VSP 5000 series
    • 23: VSP G350, G370, G700, G900, VSP F350, F370, F700, F900

    Serial No

    Specify the serial number of the storage system.

    Access Type

    Specify 3.

    SVP IP Address or Host Name

    Specify the IP address or host name of the SVP that manages the storage system that was specified for Serial No.

    Storage User ID for SVP

    Specify the user ID of the user account that was created to access the target storage system using the SVP.

    Storage Password for SVP

    Specify the password of the user account that was created to access the target storage system using the SVP.

    SVP Port No

    Specify the port number if Storage model is set to 22 or 23. You can specify a value from 0 to 65535. The default value is 1099.

    This value is the same as the initial value for the RMIIFRegist port number of the storage system. To change the port number of the storage system, see the storage system manual that explains how to change or initialize the port number to be used with the SVP.

    SVP HTTPS Port No

    If 22 or 23 is specified for Storage model, specify the port number that is used for connection using the HTTPS protocol, from a host on which RAID Agent is installed, to the SVP. You can specify a value from 0 to 65535. The default value is 443.

    This value is the same as the initial value for the MAPPWebServerHttps port number of the storage system. To change the port number of the storage system, see the storage system manual that explains how to change or initialize the port number to be used with the SVP.

    GUM(CTL) IP Address or Host Name (Primary)

    If 23 is specified for Storage model, specify the IP address or the host name (for which name resolution is possible) of the GUM (CTL) of the storage system that was specified for Serial No. The default value is blank. Connections with the connection destination set for GUM(CTL) IP Address or Host Name (Primary) will be prioritized.

    Note that you do not need to specify both GUM(CTL) IP Address or Host Name (Primary) and GUM(CTL) IP Address or Host Name (Secondary).

    GUM(CTL) IP Address or Host Name (Secondary)

    Storage User ID for REST-API

    Specify the user ID of the user account that was created for accessing the target storage system using the REST API.

    Storage Password for REST-API

    Specify the password of the user account that was created for accessing the target storage system using the REST API.

    REST-API Protocol

    Specify the protocol to be used for accessing the target storage system using the REST API. The default value is 1.
    • To use HTTP: 1
    • To use HTTPS: 2
    Java VM Heap Memory setting Method

    Specify the method to be used for setting the required memory size for the Java VM. The default value is 1.

    However, in a large-scale environment that exceeds an assumed value*, if you specify 1 for this item, processing might end abnormally because of insufficient memory. For this reason, for a large-scale environment, specify 2.

    • To specify a method that automatically calculates the required memory size based on the maximum number of volumes: 1
    • To specify a method where the user specifies the memory size: 2

    Maximum number of Volumes

    If you specified 1 for Java VM Heap Memory setting Method, specify the maximum number of volumes to be created on the target storage system. The required memory size for the Java VM will be automatically specified based on this setting.

    You can specify a value in the range from 1000 to 99999. The default value is 4000.

    Java VM Heap Memory for SVP

    If you specified 2 for Java VM Heap Memory setting Method, specify the required memory size for the Java VM. The default value is 1.
    • 1: 0.5 GB
    • 2: 1.0 GB
    • 3: 2.0 GB
    • 4: 4.0 GB
    • 5: 8.0 GB

    Java VM Heap Memory for REST-API

    If you specified 2 for Java VM Heap Memory setting Method, specify the required memory size for the Java VM. The default value is 1.
    • 1: 128 MB
    • 2: 256 MB
    • 3: 512 MB
    • 4: 1.0 GB
    • 5: 2.0 GB
    • 6: 4.0 GB
    • 7: 8.0 GB

    *: The following values are assumed for the environment when the required memory size is calculated based on the maximum number of volumes.

    • If data is collected by using the REST API

      • Number of LU paths per LDEV: 4
      • Number of SPM settings per LDEV: 4
      • Number of host groups assigned to each LDEV: 1
      • Number of WWNs assigned to the hosts of each LDEV: 2
    • If data is collected by using the SVP

      • Number of LU paths: 0
      • Sampling interval (in minutes): 1
  3. When configuring multiple instances, repeat steps 1 and 2 for each instance.

  4. Before you start operation in an instance environment, run the jpctdchkinst command to verify the instance settings.

    The command references the set instance information. (This command checks whether the settings allow information to be collected from the storage system monitored by RAID Agent.)
    /opt/jp1pc/tools/jpctdchkinst –inst instance-name
  5. (Optional) Configure the collection-time definition file (conf_refresh_times.ini).

    See Changing the configuration information collection time, and set the time for collecting configuration information. By specifying this setting, you can prevent the issue of not collecting performance data when there is a large amount of configuration information to collect from the storage system.

  6. Run the following command to start the RAID Agent instance services:

    /opt/jp1pc/htnm/bin/htmsrv start -all
    NoteYou must wait for approximately one hour to add the Hitachi Enterprise Storage probe after adding an instance on the RAID agent.

Importing a certificate to the truststore for RAID Agent

To enable verification of a storage system's server certificate in RAID Agent, import the storage system's certificate to the truststore for RAID Agent, and then edit the ipdc.properties file.

Before you begin

  • You must have the root permission of the OS to do this operation.

  • You must prepare the storage system's certificate.

    If you use a certificate issued by a certificate authority, the certificates of all the certificate authorities, from the certificate authority that issued the storage system's server certificate to the root certificate authority, must be connected in a chain of trust.

  • If the storage system's certificate already exists in the truststore, delete the existing certificate before importing new certificate. To delete the existing certificate, execute the following command:
    rm /opt/jp1pc/agtd/agent/instance-name/jssecacerts

Procedure

  1. Execute the following command to import the storage system's certificate to the truststore:

    /opt/jp1pc/htnm/HBasePSB/jdk/bin/keytool –import –alias alias-name –file certificate-file-name –keystore truststore-file-name –storepass access-password-for-truststore

    • For alias-name, specify a name that makes it possible to determine which storage system the server certificate belongs to.
    • For certificate-file-name, specify the absolute path of the location in which the certificate is stored.
    • For truststore-file-name, specify the following absolute path:

      /opt/jp1pc/agtd/agent/instance-name/jssecacerts

    • For access-password-for-truststore, specify a password of your choice.
  2. Enable verification of the server certificate by changing the following properties in the file /opt/jp1pc/agtd/agent/instance-name/ipdc.properties. If there is a hash mark (#) at the beginning of a property line, delete that hash mark.

    • ssl.check.cert:true
    • ssl.check.cert.self.truststore:true
    • ssl.check.cert.hostname:true
      Note
      • To check the name of the host of the SSL certificate, specify a host name that can be resolved for GUM(CTL) IP Address or Host Name in the RAID Agent instance information. If you cannot specify a host name that can be resolved, specify false because the host name cannot be verified.
      • If the web server certificate is not a wildcard certificate, specify false, because the host name cannot be verified.
  3. Execute the command jpctdchkinst and confirm the instance settings:

    /opt/jp1pc/tools/jpctdchkinst –inst instance-name
  4. Execute the following commands to restart the services of the RAID Agent instance:

    /opt/jp1pc/htnm/bin/htmsrv stop -all
    /opt/jp1pc/htnm/bin/htmsrv start -all

Next steps

Configuring RAID Agent for data collection using REST API

Use this method to collect basic information about storage system capacity and performance metrics through an IP connection. To use this data collection method, you must specify 4 for Access Type when you create the RAID Agent instance environment.

Configuring Analyzer probe server

Confirm RAID Agent

Confirm that the RAID Agent and the Analyzer probe server are installed on the same host. RAID Agent is installed when the Analyzer probe server is installed.

Configuring storage systems

Create user accounts for a storage system

On the storage system, verify that a user account to be used by RAID Agent was created. The user account must meet the following conditions:

  • REST API

    The user account must belong to a user group for which All Resource Groups Assigned is enabled. If the user group is assigned to one of the following roles, All Resource Groups Assigned is enabled.

    • Security Administrator (View Only)
    • Security Administrator (View & Modify)
    • Audit Log Administrator (View Only)
    • Audit Log Administrator (View & Modify)
    • Support Personnel (Vendor Only)

For details about how to create a user account for a storage system, see the appropriate documentation for your storage system.

Acquire a server certificate

Acquire the server certificate of the storage system. This server certificate is required for server authentication, as well as for encryption by using HTTPS communication between RAID Agent and the storage system. If you are not using server authentication, you do not need to acquire a server certificate.

Connecting the RAID Agent host and the storage system

Verify that the RAID Agent host and the storage system are connected by the following method:

  • TCP/IP connection for the GUM (CTL)

Creating an instance environment

To collect data from the Hitachi Enterprise Storage probe, you must create a RAID Agent instance environment on the host on which Analyzer probe server is installed.

  1. On the Analyzer probe server, run the jpcinssetup command with the service key and instance name specified. Instance names must be no longer than 32 bytes, and only half-width alphanumeric characters (A-Z, a-z, 0-9) are allowed.

    For example, to create an instance environment for the instance named 35053 for RAID Agent, run the following command:

    /opt/jp1pc/tools/jpcinssetup agtd -inst 35053
  2. Set up the instance information for the storage system you will monitor.

    To use the default value (or no value), press Enter.

    The following table lists the instance information to specify.

    Item

    Description

    Storage model

    Specify the storage type.

    • 13: VSP 5000 series
    • 23: VSP G350, G370, G700, G900, VSP F350, F370, F700, F900

    Serial No

    Specify the serial number of the storage system.

    Access Type

    Specify 4.

    SVP IP Address or Host Name

    If 13 is specified for Storage model, specify the IP address or host name of the SVP that manages the storage system that was specified for Serial No.

    GUM(CTL) IP Address or Host Name (Primary)

    If 23 is specified for Storage model, specify the IP address or the host name (for which name resolution is possible) of the GUM (CTL) of the storage system that was specified for Serial No. The default value is blank. Connections with the connection destination set for GUM(CTL) IP Address or Host Name (Primary) will be prioritized.

    Note that you do not need to specify both GUM(CTL) IP Address or Host Name (Primary) and GUM(CTL) IP Address or Host Name (Secondary).

    GUM(CTL) IP Address or Host Name (Secondary)

    Storage User ID for REST-API

    Specify the user ID of the user account that was created for accessing the target storage system using the REST API.

    Storage Password for REST-API

    Specify the password of the user account that was created for accessing the target storage system using the REST API.

    REST-API Protocol

    Specify the protocol to be used for accessing the target storage system using the REST API. The default value is 1.
    • To use HTTP: 1
    • To use HTTPS: 2
    Java VM Heap Memory setting Method

    Specify the method to be used for setting the required memory size for the Java VM. The default value is 1.

    However, in a large-scale environment that exceeds an assumed value*, if you specify 1 for this item, processing might end abnormally because of insufficient memory. For this reason, for a large-scale environment, specify 2.

    • To specify a method that automatically calculates the required memory size based on the maximum number of volumes: 1
    • To specify a method where the user specifies the memory size: 2

    Maximum number of Volumes

    If you specified 1 for Java VM Heap Memory setting Method, specify the maximum number of volumes to be created on the target storage system. The required memory size for the Java VM will be automatically specified based on this setting.

    You can specify a value in the range from 1000 to 99999. The default value is 4000.

    Java VM Heap Memory for REST-API

    If you specified 2 for Java VM Heap Memory setting Method, specify the required memory size for the Java VM. The default value is 1.
    • 1: 128 MB
    • 2: 256 MB
    • 3: 512 MB
    • 4: 1.0 GB
    • 5: 2.0 GB
    • 6: 4.0 GB
    • 7: 8.0 GB

    *: The following values are assumed for the environment when the required memory size is calculated based on the maximum number of volumes and the data is collected by using the REST API:

    • Number of LU paths per LDEV: 4
    • Number of SPM settings per LDEV: 4
    • Number of host groups assigned to each LDEV: 1
    • Number of WWNs assigned to the hosts of each LDEV: 2
  3. When configuring multiple instances, repeat steps 1 and 2 for each instance.

  4. Before you start operation in an instance environment, run the jpctdchkinst command to verify the instance settings.

    The command references the set instance information. (This command checks whether the settings allow information to be collected from the storage system monitored by RAID Agent.)
    /opt/jp1pc/tools/jpctdchkinst –inst instance-name
  5. (Optional) Configure the collection-time definition file (conf_refresh_times.ini).

    See Changing the configuration information collection time, and set the time for collecting configuration information. By specifying this setting, you can prevent the issue of not collecting performance data when there is a large amount of configuration information to collect from the storage system.

  6. Run the following command to start the RAID Agent instance services:

    /opt/jp1pc/htnm/bin/htmsrv start -all
    NoteYou must wait for approximately one hour to add the Hitachi Enterprise Storage probe after adding an instance on the RAID agent.

Importing a certificate to the truststore for RAID Agent

To enable verification of a storage system's server certificate in RAID Agent, import the storage system's certificate to the truststore for RAID Agent, and then edit the ipdc.properties file.

Before you begin

  • You must have the root permission of the OS to do this operation.

  • You must prepare the storage system's certificate.

    If you use a certificate issued by a certificate authority, the certificates of all the certificate authorities, from the certificate authority that issued the storage system's server certificate to the root certificate authority, must be connected in a chain of trust.

  • If the storage system's certificate already exists in the truststore, delete the existing certificate before importing new certificate. To delete the existing certificate, execute the following command:
    rm /opt/jp1pc/agtd/agent/instance-name/jssecacerts

Procedure

  1. Execute the following command to import the storage system's certificate to the truststore:

    /opt/jp1pc/htnm/HBasePSB/jdk/bin/keytool –import –alias alias-name –file certificate-file-name –keystore truststore-file-name –storepass access-password-for-truststore

    • For alias-name, specify a name that makes it possible to determine which storage system the server certificate belongs to.
    • For certificate-file-name, specify the absolute path of the location in which the certificate is stored.
    • For truststore-file-name, specify the following absolute path:

      /opt/jp1pc/agtd/agent/instance-name/jssecacerts

    • For access-password-for-truststore, specify a password of your choice.
  2. Enable verification of the server certificate by changing the following properties in the file /opt/jp1pc/agtd/agent/instance-name/ipdc.properties. If there is a hash mark (#) at the beginning of a property line, delete that hash mark.

    • ssl.check.cert:true
    • ssl.check.cert.self.truststore:true
    • ssl.check.cert.hostname:true
      Note
      • To check the name of the host of the SSL certificate, specify a host name that can be resolved for GUM(CTL) IP Address or Host Name in the RAID Agent instance information. If you cannot specify a host name that can be resolved, specify false because the host name cannot be verified.
      • If the web server certificate is not a wildcard certificate, specify false, because the host name cannot be verified.
  3. Execute the command jpctdchkinst and confirm the instance settings:

    /opt/jp1pc/tools/jpctdchkinst –inst instance-name
  4. Execute the following commands to restart the services of the RAID Agent instance:

    /opt/jp1pc/htnm/bin/htmsrv stop -all
    /opt/jp1pc/htnm/bin/htmsrv start -all

Next steps

Setting up Tuning Manager - Agent for RAID

If you are running Tuning Manager in your environment, then you can configure the Tuning Manager - Agent for RAID to collect performance data from the monitored Hitachi Enterprise storage systems (VSP, VSP F series, VSP G series, VSP 5000 series, or HUS VM).

Requirements for adding the Hitachi Enterprise Storage probe (when using Tuning Manager - Agent for RAID)

To use Tuning Manager - Agent for RAID to monitor Hitachi Enterprise storage systems, you must perform the following operations before adding the Hitachi Enterprise Storage probe.

Example system configuration for Ops Center Analyzer (when using Tuning Manager - Agent for RAID)GUID-28FEAE00-F61E-4689-8372-B7571695727C-low.gifOperation workflow for adding Hitachi Enterprise Storage probe (when using Tuning Manager - Agent for RAID)GUID-095A26C0-99A8-4C3D-9F10-4294DA1A05A7-low.gifPrerequisites

To use Tuning Manager - Agent for RAID, make sure that all of the following conditions are met:

  • The Tuning Manager server is set up to connect to Tuning Manager - Agent for RAID.
  • Version of Tuning Manager - Agent for RAID: 8.5.3 or later.
  • Performance database for Tuning Manager - Agent for RAID: Hybrid Store. If you are using a Store database, switch to Hybrid Store.
  • Value specified for Method for collecting (the connection method to be used when collecting performance data) in the Tuning Manager - Agent for RAID instance information: Verify that 3 (Collect from both command devices and SVP) is selected.

    For Ops Center Analyzer, the only value of Method for collecting that is supported is 3. If 3 is not selected, update the instance environment.

  • Disk capacity of Tuning Manager - Agent for RAID: There is sufficient space for the additional records that will be collected for Ops Center Analyzer analysis.

Changing the data collected by Tuning Manager - Agent for RAID

To enable Tuning Manager - Agent for RAID to collect the following additional records for use in Ops Center Analyzer, you must modify the existing data collection settings (Log property settings) in Tuning Manager - Agent for RAID:

  • PD_HGC
  • PD_HHGC
  • PD_LDCC
  • PD_LDD
  • PD_LHGC
  • PD_LWPC
  • PD_MPBC
  • PD_PWPC
  • PD_RGD

Procedure

  1. Log on to the Tuning Manager software as a user with administrator permissions.

  2. Start Performance Reporter.

  3. In the main window of Performance Reporter, in the Navigation frame, select the Services tab.

    This tab is displayed only for users with administrator permissions.
  4. In the main window of Performance Reporter, in the Navigation frame, select System Machines folder-representing-Tuning-Manager-Agent-for-RAID-installation-host Agent Collector Service.

  5. In the main window of Performance Reporter, in the method pane, select Properties, and then Detail Records.

    A list of records is displayed.
  6. Select the record for which you need to change the settings, and then change the Log property value to Yes.

    Note

    To use Tuning Manager - Agent for RAID after upgrading it from a version earlier than 8.5.2 to version 8.5.2 or a later version, change the Collection Interval value for the PD_RGD record to 3600.

Settings for communication from Analyzer probe server to Tuning Manager - Agent for RAID

To use the data collected by Tuning Manager - Agent for RAID in Ops Center Analyzer, you must specify the necessary settings for communication with Analyzer probe server.

  1. On the host on which Tuning Manager - Agent for RAID is installed, register the port that is to be used for communication with Analyzer probe server as a firewall exception.

    The default port number is 24221.
  2. (Optional) To limit the servers that can access the performance data of Tuning Manager - Agent for RAID, add Analyzer probe server to the htnm_httpsd.conf file managed by Tuning Manager - Agent for RAID.

    1. Stop the Tuning Manager Agent REST API component services.

    2. To the last line of the htnm_httpsd.conf file, register information about the Analyzer probe server that can connect to the agents on which use of the API is enabled.

    3. Start the Tuning Manager Agent REST API component services.

    NoteTo use the API functions that access RAID Agent, you also need to register information about Analyzer server in the htnm_httpsd.conf file.

Values used for estimating disk space when using Tuning Manager - Agent for RAID

The following information is necessary for calculating the disk space required to use Tuning Manager - Agent for RAID with Ops Center Analyzer.

Calculate the disk space required by Tuning Manager - Agent for RAID and verify that there is adequate disk space available. The calculation is performed based on information about records already collected by Tuning Manager - Agent for RAID, and information about records that will be additionally collected for Ops Center Analyzer by Tuning Manager - Agent for RAID.

The record information described here relates to records to be additionally collected by Tuning Manager - Agent for RAID. For details about other records, see Hitachi Command Suite System Requirements.

Methods for estimating number of instances
  • Record IDMethod for estimating number of instances
    PD_HGCNumber of host groups that exist in the storage system
    PD_HHGCTotal number of hosts that belong to the host groups that exist in the storage system
    PD_LDCCNumber of copied logical devices
    PD_LDDNumber of logical devices
    PD_LHGCTotal number of LUNs that belong to the host groups that exist in the storage system
    PD_LWPCSum of the number of settings related to LDEVs and the WWNs of host bus adapters*, and the number of settings related to LDEVs and iSCSI names*
    PD_MPBCNumber of MP blades
    PD_PWPCTotal number of settings related to ports and the WWNs of host bus adapters*
    PD_RGDNumber of parity groups

    *: To specify this setting, use Server Priority Manager, provided by Hitachi storage systems.

Size of each record
  • Record IDFixed part 1 (bytes)Variable part 1 (bytes)Fixed part 2 (bytes)Variable part 2 (bytes)
    PD_HGC80563----
    PD_HHGC68580----
    PD_LDCC72281----
    PD_LDD76265----
    PD_LHGC68272----
    PD_LWPC64617----
    PD_MPBC52113----
    PD_RGD80295----
    PD_PWPC80361----
Retention period for the records (default value)
  • Record IDRetention period (unit: hours)
    PD_HGC168
    PD_HHGC168
    PD_LDCC168
    PD_LDD168
    PD_LHGC168
    PD_LWPC168
    PD_MPBC168
    PD_RGD168
    PD_PWPC168

Migrating Hitachi Tuning Manager historical data

The Tuning Manager data migration feature copies storage systems historical data from the Tuning Manager to Analyzer detail view database. You can obtain the migrated data, which is preserved in the Analyzer detail view database, by using the Analyzer detail view REST API.

The Tuning Manager data migration feature supports deployments in which Tuning Manager and Tuning Manager - Agent for RAID are on the same or on different machines.

NoteThe Tuning Manager, Tuning Manager - Agent for RAID, and Analyzer probe server must belong to the same subnet.

Tuning Manager data migration workflow:

  1. The Analyzer probe server connects to Tuning Manager to identify the RAID Agent associated with it.
  2. The Analyzer probe server connects to the RAID Agent to collect the historical data.
  3. The Analyzer probe server transfers the collected data to the Analyzer detail view database.
  4. The user connects to the Analyzer detail view database using the REST API to obtain the migrated data.

Setting up a Tuning Manager connection

Set up a connection so that you can migrate the historical data stored in Tuning Manager to the Analyzer probe server.

Before you begin

Verify the following:

  • Tuning Manager server version is 8.5.3-00 or later.
  • Tuning Manager - Agent for RAID version is 8.5.3-04 or later.
  • Tuning Manager accessible host settings to allow a connection between Tuning Manager and the Analyzer probe server (using the HTTP protocol on port 22015 or the HTTPS protocol on port 22016).
  • Tuning Manager server, Tuning Manager - Agent for RAID, and Analyzer probe server all belong to the same subnet.
  • All storage systems about which you want to migrate data are registered in Tuning Manager.
  • Tuning Manager server services are running.
  • Tuning Manager - Agent for RAID REST service is running.
  • Tuning Manager server can recognize the Tuning Manager - Agent for RAID instance.
  • Tuning Manager server has an unexpired license.
  • The performance database for Tuning Manager - Agent for RAID is Hybrid Store.
  • Tuning Manager server and Tuning Manager - Agent for RAID can restrict API clients that connect to them. If this is configured, the Analyzer probe server must be registered to allow the connection.

Procedure

  1. Log on to the Analyzer probe as the admin user.

  2. In the application bar, click Manage.

  3. In the Administration section, click Migrate Hitachi Tuning Manager Data.

  4. In the Add Hitachi Tuning Manager window, provide the following details:

    • Connection Method HTTP or HTTPS
    • IP Address IP address of Tuning Manager
    • Port Number Port number based on the selected connection method. The default ports are:
      • HTTP: 22015
      • HTTPS: 22016
    • Username and Password Username and password for Tuning Manager.
  5. Click Add. After you have successfully set up the connection, the RAID Agents and storage systems associated with Tuning Manager are listed in the Migrate Hitachi Tuning Manager Data window.

Starting the data migration

Data migration is performed on a per-system basis. After you complete the data migration for storage systems, you cannot run it again.

NoteBy default, the Analyzer probe server uses HTTPS protocol on port 8443 to communicate with the Analyzer detail view server. If you specify a different port, ensure it is available for communication.

Procedure

  1. In the Migrate Hitachi Tuning Manager Data window, select the storage systems from which to migrate data. (You can migrate data simultaneously for four storage systems per Tuning Manager - Agent for RAID instance.)

  2. In the Duration column, select the duration in years for which you want to migrate the data.

    When you select the duration, the Remarks column shows the exact duration for which the data is available for migration. Make sure that you select the correct duration. You cannot migrate data with different durations for the same storage system.
  3. Click Start, and then click OK to begin the data migration.

    The Remarks column is updated with the status as the migration proceeds.

Accessing Tuning Manager historical data

You can use REST API to query the Ops Center Analyzer detail view database for the Tuning Manager historical data.

Sample query:

  • Configuration data: You can query the migrated configuration data as you would query any other probe data using the following request line:

    POST baseURL?action=retrieveResourceData&dataset=defaultDs
  • Performance Data: You can query the migrated performance data using the following request line:

    POST baseURL?action=query&dataset=defaultDs&processSync=true
    • You must specify the following parameters in the request body:
      • db=cdb1: Restricts the query to the migrated performance data.
      • inputInterval=supported-values: Collection intervals of the migrated data. The supported values are: h (hour), d (day), w (week), m (month), and y (year).

For more information, refer to Hitachi Ops Center Analyzer detail view REST API Reference Guide.

Changing the default migration connection settings

The Analyzer probe server uses HTTP: 24221 as a default connection setting. To change this default connection setting, do the following:

  1. In the Migrate Hitachi Tuning Manager Data window, in the RAID Agent column, click the RAID Agent IP address.

    The RAID Agent Connection Details window opens.
  2. Select the connection method and provide the corresponding port number. This setting applies to all storage systems associated with the selected RAID Agent.

  3. Click Ok.

Notes and restrictions

The following restrictions apply to the Tuning Manager data migration feature.

  • Historical performance data is migrated for the following frequencies:
    • Hourly
    • Daily
    • Weekly
    • Monthly
    • Yearly
  • Historical configuration data is migrated for a frequency of one day only.
  • Migration supports Hitachi Enterprise Storage probe resources and records only (except for RAID Agent instance name). For a specific list, refer to Hitachi Ops Center Analyzer detail view Metrics Reference Guide.
  • Migration does not support migrating Tuning Manager alarms and alerts.
  • Migration does not support migrating Hitachi Device Manager data.

Switching from Tuning Manager - Agent for RAID to RAID Agent

You can change the agent used by the Hitachi Enterprise Storage probe from Tuning Manager - Agent for RAID to RAID Agent bundled with Ops Center Analyzer.

NoteRAID Agent will not automatically inherit the settings of Tuning Manager - Agent for RAID. Configure the settings manually by performing the following steps.

Procedure

  1. Check the settings of Tuning Manager - Agent for RAID.

    1. Display a list of instance names by running the jpcinslist command on the host on which Tuning Manager - Agent for RAID is installed:

      jpcinslist agtd
    2. Check the instance information by running the jpctdchkinst command on the host on which Tuning Manager - Agent for RAID is installed:

      jpctdchkinst -inst instance-name
    3. If the collection intervals for Tuning Manager - Agent for RAID have been changed, check the collection intervals.

      For details about how to check the collection intervals for Tuning Manager - Agent for RAID, see the Hitachi Command Suite Tuning Manager Agent Administration Guide.
  2. Stop the Hitachi Enterprise Storage probe.

    For details about how to stop the probe, see Starting and stopping probes.
  3. Stop the instance of Tuning Manager - Agent for RAID by running the htmsrv command on the host on which Tuning Manager - Agent for RAID is installed:

    htmsrv stop -key agtd -inst instance-name
  4. Set up RAID Agent.

    1. Determine Access Type. (For details, see Selecting the data collection method.)

    2. Set up RAID Agent. (For details, see Workflow for setting up the Hitachi Enterprise Storage probe (when using RAID Agent) and the sections that follow.)

      Specify the instance information of the storage system to be monitored as follows:
      • The item Access Type in the instance information for RAID Agent corresponds to the item Method for collecting in the instance information for Tuning Manager - Agent for RAID.

        Example: The value 1 (Command-Device and SVP) for Access Type has the same meaning as the value 3 (both) for Method for collecting.

      • Make sure that the value of Serial No is the same as the value set for Tuning Manager - Agent for RAID.
      • (Optional) If you want RAID Agent to inherit other settings, specify the same values for those settings as were set for Tuning Manager - Agent for RAID.
  5. If the collection intervals for Tuning Manager - Agent for RAID have been changed, change the collection intervals for RAID Agent to match those for Tuning Manager - Agent for RAID.

    For details about how to change the collection intervals for RAID Agent, see Changing data collection intervals for RAID Agent.
  6. Change the agent used by the Hitachi Enterprise Storage probe from Tuning Manager - Agent for RAID to RAID Agent.

    For details about how to change the probe settings, see Editing probes.

    Change the following probe settings:

    • Connection Type: Select HTTP.
    • RAID Agent IP address: Specify the IP address of the RAID Agent host.
    • RAID Agent Hostname: Specify the name of the RAID Agent host.
    • RAID Agent Port: Specify the port number of the RAID Agent host.
    • Storage System Instance: Specify the name of the instance of RAID Agent that you created in a previous step.
  7. Start the Hitachi Enterprise Storage probe.

    For details about how to start the probe, see Starting and stopping probes.