Type
  • Best practice
Description
  • This article explains how to install the Hitachi Device Manager agent on Linux to get performance statistics from Hitachi Virtual Storage Platform (VSP)
Additional Keywords
  • Hitachi, Hitachi Device Manager, Hitachi Virtual Storage Platform, VSP

Related Topics

Knowledge Base

Installing the Hitachi Device Manager Agent on Linux

KB1101 - Nov 09, 2012

Objective

This article explains how to install the Hitachi Device Manager agent on Linux to get performance statistics from Hitachi Virtual Storage Platform (VSP).

Prerequisites

The monitoring of a Hitachi disk array relies on the SMI-S agent that is installed with Hitachi Device Manager. To get the performance statistics from Hitachi VSP, you’ll need:

  • Hitachi Device Manager Server to be installed on one server. Hitachi HiCommand Server will have to be connected to the agent. Hitachi’s Host Bus Adapter (HBA) and Device Command will also be required.
  • Hitachi Device Manager Agent to be installed on a different server. Hitachi’s Host Bus Adapter (HBA) and Device Command will be required and RMLib will also have to be installed.

Connecting Hitachi HiCommand Server to the Agent

On the server where the Hitachi Device Manager Server is installed

  1. Modify the server.properties file located into: ./DeviceManager/HiCommandServer/config/server.properties  
  2. Specify  the:
    • host name or IP address of the Web server with the server.http.host property
    • host name of the CIM Agent with the server.cim.agent property
  3. Run the following commands to stop and start the HiCommand Server:
    /opt/HiCommand/hicommand.sh
    /opt/HiCommand/hicommand.sh stop
    /opt/HiCommand/hicommand.sh start

On the server where the Hitachi Device Manager Agent is installed

Step 1: Installing the Device Manager Agent

To install the Device Manager agent:

  1. Insert the HiCommand Device Manager agent CD-ROM and mount it.
  2. Move to the directory that contains install.sh
  3. Run the command:
    # ./install.sh 
  4. A message appears, asking you whether you want to set the Device Manager server information. Enter Y.

    Note: If you enter N, Device Manager Agent could later be configured by running the command hdvmagt_setting.

  5. Enter the IP address or hostname of the Device Manager server and press the Enter key.
  6. Enter the port number of the Device Manager server and press the Enter key.
  7. Enter the user ID for logging on to the Device Manager server and press the Enter key.
  8. Enter the password for logging on to the Device Manager server and press the Enter key. A connection to the HiCommand Device Manager server will then be attempted.
  9. Set the execution period of for the HiScan command by entering h for an automatic hourly execution
  10. Specify the RAID Manager installation directory (default: /HORCM)
  11. Enter Y when a single host centrally manages the creation, status change, and deletion of copy pairs.
  12. Enter Y to enable the centrally manage pair configuration to  operate the Device Manager agent as a central manager server.

Step 2: Attaching a device from VSP

  1. Attach a device from VSP, with the CM Device attribute
  2. Run the following command to check the CM device is actually attached:
    [root@server_name logs]#  /opt/HDVM/HBaseAgent/util/bin/hldutil
    Warning: The information returned is in hexadecimal format.
  3. Edit the following file to declare command device inside the agent to get performance statistics: /opt/HDVM/HBaseAgent/mod/hdvm/config/perf_cmddev.properties

    The following format should be used: Raid-ID.serial-number.LDEV-number: deviceFileName (e.g.: R700.85678.0.92 : /dev/sde)
    Important: Decimal format is required.

    Note: All the information required is provided by the hldutil command.

  4. Run the following commands:
    • To set the command device in the perf_cmddev.properties file:
      [root@PC-HDS ~]# /opt/HDVM/HBaseAgent/bin/perf_findcmddev  write 
    • To display the settings for the command devices defined in the perf_cmddev.properties file:
        [root@PC-HDS ~]#  /opt/HDVM/HBaseAgent/bin/perf_findcmddev view  
    • To restart the agent:
       /opt/HDVM/HBaseAgent/bin/hbsasrv  stop and  /opt/HDVM/HBaseAgent/bin/hbsasrv  start   
    • To check the hbasaservice log:
      tail -f /opt/HDVM/HBaseAgent/bin/logs/hbsaservice.log 
    • To check the following lines in the access log:
      10.0.15.102 - - [08/Nov/2012:11:45:23 +0100] "POST /service/HDVMAgent HTTP/1.1" 200 21526 "-" "-"
      10.0.15.102 - - [08/Nov/2012:11:45:35 +0100] "POST /service/HDVMAgent HTTP/1.1" 200 2635 "-" "-"
      Run:
       tail -f /opt/HDVM/HBaseAgent/bin/logs/access.log      
    • To check the following lines in the service log:
      ‹HiCommandDeviceManagerAgent›‹APIInfo version="7.3" /›‹Response›‹EchoCommand name="GetPerformanceInfo" status="COMPLEAT" result="0" resultSource="PerformanceAdmin.GetPerformanceInfo" messageID="1352371442069" /›‹Performance›‹LogicalUnitStatistics model="R700" serialNumber="85678" devNum="0" statisticTime="1352371442082" totalIOs="0" kByteTransfer="0" readIOs="0" readHitIOs="0" writeIOs="0" writeHitIOs="0" /›‹LogicalUnitStatistics model="R700" serialNumber="85678" devNum="1" statisticTime="1352371442085" totalIOs="16916" kByteTransfer="6772853" readIOs="2094" readHitIOs="2073" writeIOs="14822" writeHitIOs="14822" /›
      Run:

      tail -f /opt/HDVM/HBaseAgent/bin/logs/service.log