Monitoring Hitachi HNAS Storage Devices with Monitoring Studio

How to monitor Hitachi HNAS storage devices with Monitoring Studio v9.2 and higher.

Related Topics

Downloads

Introduction

This article explains how to import the pre-built configuration into Monitoring Studio to monitor the capacity and performance of the Hitachi HNAS storage devices through SNMP. The Sentry Storage Analyzer for TrueSight OM license is required to use Monitoring Studio.
The pre-built configuration does not cover all the monitoring aspects of Hitachi HNAS storage devices. It is provided as an example and can be used as a working base for advanced monitoring. No support will be provided for this prebuilt configuration. Should you need further assistance to customize it, please contact our Professional Services team.

The pre-built configuration collects the following metrics:

inline

Cluster

Cluster PNodes

  • Status. This parameter indicates the status of the physical node. Possible values are:
    • 1 - unknown
    • 2 - up
    • 3 - not up
    • 4 - on line
    • 5 - dead
    • 6 - dormant

Cluster VNodes

  • Status. This parameter indicates the status of the virtual node. Possible values are:
    • 1 - unknown
    • 2 - on line
    • 3 - off line

inline

Fibre Channel

FC Statistics

  • Bad CRC Errors
  • Bad RX Char Errors
  • Discarded Frame Errors
  • InRate
  • Link Fail Errors
  • Link Speed in Gbps
  • Link Status. The status of the fiber interface. Possible values are:
    • unknown(0)- the information could not be obtained.
    • up(1)- the interface is up.
    • isolated(2)- the interface is isolated.
    • down(3)- the interface is down.
  • Loss Sync Errors
  • OutRate
  • PeakInRate
  • PeakOutRate
  • Protocol Errors
  • RXEOFErrors
  • Signal Loss Errors
  • TotalRxBytes
  • TotalTxBytes

inline

File Protocol

CIFS

  • chkpthCalls
  • Clients
  • closeCalls
  • createCalls
  • dskattrCalls
  • echoCalls
  • findCloseCalls
  • flushCalls
  • getatrCalls
  • lockingXCalls
  • lseekCalls
  • mkdirCalls
  • mknewCalls
  • negProtCalls
  • netCancelCalls
  • netCreateXCalls
  • netTransCalls
  • openCalls
  • openXCalls
  • readBrawCalls
  • readCalls
  • readXCalls
  • renameCalls
  • rmdirCalls
  • searchCalls
  • sessSetupXCalls
  • setatrCalls
  • tconXCalls
  • tdisCalls
  • trans2Calls
  • transCalls
  • ulogoffXCalls
  • unlinkCalls
  • writeBrawCalls
  • writeCalls
  • writeCloseCalls
  • writeXCalls

 

inline

Network

Ethernet

  • CRC Errors
  • In Bytes
  • In FIFO Drops
  • In Octet Rate Bytes/s
  • In Packets
  • Out Bytes
  • Out Octet Rate Bytes/s
  • Out Packets
  • Peak In Octet Rate Bytes/s
  • Peak Out Octet Rate Bytes/s
  • Total Bytes
  • Total Packets

TCP

  • Invalid Segments
  • IP RxInvalid Pkts
  • IP Rx Pkts
  • IP Tx Pkts
  • Rx Invalid Chksum Pkts
  • Rx Segments
  • Tx Segments

inline

NVRAM

nvramFsStats

  • ActivityCheckpoints
  • Checkpoints
  • CurrentUsage
  • Waited Allocs
  • Waiting Allocs

nvramPoolStats

  • Maximum Used
  • Size
  • Total Current Usage
  • Waited Allocs
  • Waiting Allocs

inline

System Drive

  • Capacity in GB
  • Status. This parameter indicates the status of the system drive. Possible values are:
    • online(1) - the system drive is accessible through the fibre channel interface.
    • corrupt(2) - the system drives master boot record is corrupt.
    • failed(3) - the system drive has failed and is no longer accessible through the fiber channel interface.
    • notPresent(4) - device no longer present.
    • disconnected(5) - device is present but not accessible by the controller
    • offline(6) - all ports are offline
    • initializing(7) - not accessible until initialization phase has completed
    • formatting(8) - device is formatting
    • unknown(9) - unknown device status

 

inline

Volume

File System

  • Avg Operations/s

Volume

  • Capacity in GB
  • Free Capacity in GB
  • Status. The status of the volume (i.e. file system). Possible values are:
    • unformatted(1) - the volume does NOT contain a file system.
    • mounted(2) - the volume contains a file system and may be being accessed by users.
    • formatted(3) - the volume contains a file system, but is not accessible by users as it is not mounted.
    • needsChecking(4) - the file system has some errors and cannot be mounted. It must be checked and fixed before it can be accessed by users.

Importing the Pre-Built Configuration

Pre-requisites

Before using the pre-built configuration, make sure that:

  • You have access to the SNMP agent embedded on the Hitachi HNAS storage device through SNMP v1, v2c, or v3
  • PATROL Agent 9.6 or later is installed and properly configured
  • Monitoring Studio KM 9.4 or later is installed with the latest patches and loaded on the PATROL agent

Procedure

  1. Download the configuration file and copy it on the server where the PATROL Agent and the Monitoring Studio KM are installed.
  2. Right-click on the main Monitoring Studio icon > KM Commands > Configuration > Import Configuration
    Importing the Hitachi HNAS pre-built configuration

    Importing the Hitachi HNAS pre-built configuration

  3. Navigate to the folder where the downloaded cfg file is copied and choose the Hitachi-HNAS configuration file
    Selecting the Hitachi HNAS pre-built configuration to import

    Selecting the Hitachi HNAS pre-built configuration to import

  4. Monitoring Studio indicates the number of hosts found in the configuration file that require specific information before being imported. You can click the Hosts button to view the list. Click Next.
    Verifying the host information

    Verifying the host information

  5. Provide the hostname or IP address of the Hitachi HNAS storage device to be monitored and click Next.
    Providing the Hostname or IP address of the Hitachi HNAS storage device to be monitored

    Providing the Hostname or IP address of the Hitachi HNAS storage device to be monitored

  6. Specify the SNMP version used and click Next.
    Selecting the version of the SNMP used

    Selecting the version of the SNMP used

  7. For SNMP v1 and v2c, provide the SNMP community string; for SNMP v3 enter the credentials and click Next.
    Configuring SNMP settings

    Configuring SNMP settings

  8. Check the Import Summary and click Next.
  9. Click Finish to start the discovery.
    Specifying the tests to perform to check host availability

    Specifying the tests to perform to check host availability

Important Note: Thresholds are not set by default. We recommend you to set them as per your needs.

Learn More

To learn more about the monitor types used in this configuration template, please refer to the Specifying the Monitors Used section of the user documentation.

Please refer to Professional Services page to learn more about the consulting services available.