Type
  • Best Practice
Description
  • This article explains how to monitor Hitachi (HDS) AMS, HUS Storage Systems using the Hitachi Storage Navigator Modular 2 CLI and Hardware Sentry KM for PATROL.
Additional Keywords
  • Hitachi, Hitachi (HDS) AMS, Hitachi Device Manager, Hitachi HUS, HSNM2 CLI, Hitachi Storage Navigator Modular 2 CLI

Related Topics

Knowledge Base

Leveraging the HSNM2 CLI to Monitor Hitachi (HDS) AMS, HUS Systems

KB1148 - Jul 11, 2014

Introduction

An issue identified on the Hitachi Device Manager SMI-S provider causes the status of all storage components to always be "OK", whatever their actual status. Sentry Software therefore recommends using the Hitachi Storage Navigator Modular 2 CLI to monitor Hitachi (HDS) AMS, HUS Systems.

This article explains how to:

  • Install Hitachi Storage Navigator Modular 2 CLI
  • Configure Hitachi Storage Navigator Modular 2 CLI
  • Configure Hardware Sentry KM for PATROL.

Installing Hitachi Storage Navigator Modular 2 CLI

On a Windows Server

  1. Install the Hitachi Storage Navigator Modular 2 CLI
  2. Install the PATROL Agent on the server where Hitachi Storage Navigator Modular 2 CLI is installed
  3. Set the global environment variable STONAVM_HOME to the installation folder:

    e.g.  STONAVM_HOME=C:\Program Files\Storage Navigator Modular 2 CLI

On a Linux Server

  1. Create an installation folder (default:  /usr/stonavm)
  2. Untar the installation files to the installation folder.
  3. Set the following variables for the PATROL Agent:

    STONAVM_HOME to the installation folder
    LD_LIBRARY_PATH variable to $STONAVM_HOME/lib

    Example:

    STONAVM_HOME=/usr/stonavm
    LD_LIBRARY_PATH=/usr/stonavm/lib

Configuring Hitachi Storage Navigator Module 2 CLI

  1. Register the storage systems to be monitored. You can either use:
    • the auunitadduto command (automatic registering)
      auunitaddauto -ip 10.0.10.0 10.0.10.254
    • or the auunitadd command (manual registering):
      auunitadd -unit AMS2100_12345678 -ctl0  10.0.0.1 -ctl1 10.0.0.2
  2. Run the auunitref command to list the connected systems:
    Name                                                              Group            Type     Construction Connection Type Error  Monitoring Communication Type IP Address/Host Name/Device Name
    AMS2100_12345678                                                                  AMS2100  Dual         TCP/IP(LAN)     Enable           Non-secure         10.0.10.1                            10.0.10.2
  3. For each UNIT (i.e. AMS2100_12345678), test the login credentials to be used by the CLI to authenticate:
    audrive –unit  AMS2100_12345678 -status 
    The Account Authentication is enabled. Please login.
    User ID: username
    Password:
    Unit  HDU  Type        Status
    0    0  Data        Normal
    0    1  Data        Normal
    0    2  Data        Normal
    0    3  Data        Normal
    0    4  Undefined   Mounted

Configuring Hardware Sentry KM for PATROL

  1. In the PATROL Console, right-click the Hardware icon > KM Commands > Add a Remote System or an External Device...
  2. Read the license agreement, accept it, and click Next to continue.
  3. Identify the Hitachi Storage Systems to be monitored:
    1. System or Device Name: enter the name to be displayed in the consoles
    2. IP address: enter localhost
    3. System or Device Type: select “Storage (Array, Switch, Library)”
  4. Click Next.
  5. Select Manually choose which Connector to use and click Next.
  6. Select:
    • Hitachi HDS AMS/HUS - SNM2 CLI – Linux if the PATROL Agent is installed on a Linux Server
    • Hitachi HDS AMS/HUS - SNM2 CLI – Windows if the PATROL Agent is installed on a Windows Server
  7. Click Next.

    Note: If these connectors do not appear, install the patch P1553: Monitoring Hitachi (HDS) AMS, HUS with HSNM2 CLI.


  8. Keep SSH as the connection mode and click Next.
  9. Enter the Username and Password to be used by the CLI. These should be the credentials used when testing the audrive command. Should systems have different credentials, separate remote monitoring instances must be setup for each set of credentials.
  10. Click Next.
  11. Click Finish to trigger a new discovery.