Type
  • Best Practice
Description
  • This article explains how to configure the monitoring of Hitachi AMS, HUS, USP, VSP and HP P9000 Disk Arrays with Sentry's solutions (Hardware Sentry KM for PATROL, BPM Express for Hardware, Hitachi Disk Arrays KM, and BMC Performance Manager Express for Hitachi Disk Arrays).
Additional Keywords
  • AMS, Hitachi, HUS, USP, VCP, HP9000

Related Topics

Knowledge Base

Monitoring Hitachi and HP 9000 Disk Arrays with Sentry's Solutions

KB1035 - Jul 12, 2010 - Last reviewed on Mar 19, 2014

Objective

This article explains how to configure the monitoring of Hitachi AMS, HUS, USP, VSP and HP 9000 disk arrays with Sentry software’s monitoring solutions.

The monitoring of Hitachi disk arrays and HP P9000 relies on the SMI-S agent that is installed with Hitachi Command Suite or the HP P9000 Command View Advanced Edition. Because the HP P9000 is a Hitachi rebranded USP-V disk array, the configuration procedure is the same for both the Hitachi Command Suite and the HP P9000 Command View Advance Edition.

This article is based on the Hitachi Command Suite (Hitachi Device Manager) which is a software suite that needs to be installed on a separate server.

Installing the Hitachi Device Manager

Pre-requisites

Before installing the Hitachi Device Manager, make sure that:

  • The server’s definitive name has been set. The installation of this software sets configuration variables based on the server’s DNS Name.
  • Adobe Flash Player is installed.

Installation Procedure

The installation files are contained on the Hitachi Device Manager Server DVD.

Installing the Hitachi Command Suite

  1. Double-click the Index.htm file
  2. Click Install to launch the Hitachi Command Suite installer:
  3. Click Next.
  4. Choose the installation folder and click Next.
  5. When the installation is complete, click Finish.
  6. Open the Hitachi Command Suite: http://127.0.0.1:23015/DeviceManagerWebService/index.jsp
  7. Click on Licenses and Install License.

Installing the Device Manager Agent

  1. Click Install to launch the Device Manager agent installer:
  2. Click Next.
  3. Choose the install folder and click Next. A screen will appear to ask you permission to add a firewall exception even if your server’s firewall is not enabled:
  4. Select YES and click Next.
  5. Select the user account to be used for launching the agent service.  Selecting NO will use the Local System Account (recommended). Click Next.
  6. When the installation is complete, click Yes to setup the Device Manager agent.  The agent will then check connection to Device Manage (Hitachi’s Name for Command View Advanced Edition).
  7. Select YES to specify the Device Manager server Information, change the IP address to 127.0.0.1 and click Next.
  8. Click OK.
     
  9. Select YES to enable the Execution Period of the HiScan Command.  Select pre-determined or random hour (do not use the default 2:30am) to prevent agent conflict. Click Next.
  10. Select NO in order not to set up the P9000 RAID Manager (it is not needed by Sentry / CVAE) and click Next.

Configuring the Hitachi Device Manager

  1. Log into the Hitachi Command Suite Console: http://localhost:23015/DeviceManagerWebService/index.jsp
  2. Click the Add Storage System button located under the Administration > Storage Systems tabs:
  3. Select the Storage System Type:
    1. For Hitachi Series Storage System (VSP / USP-V),  provide the IP address and Credentials:
    2. For Hitachi Series Storage System (AMS), provide the Controller’s IP addresses and Credentials:
  4. Click OK. A Data Collection Task will be generated to add the Storage System. Click View Task Status for details.
  5. Wait for the Data Collect Task to complete successfully:
  6. (USP-V and VSP only) Create the Administrative LUN:
    1. Click the Resources tab.
    2. Expand all storage systems and select the recently added storage system.
    3. Select Volumes.
    4. Under General Tasks, select Allocate Volume and fill the fields as follows:
      • Host: for Physical Servers, the name of the host where CVAE is installed; for Virtual Servers on ESX host, the name of the ESX host server.
      • Size:  Can be as small as 50MB since this LUN will not actually have data.
      • VolumeType:  Basic Volume
      • Location: Internal
    5. Click Show Plan.
    6. Verify that the allocation task has completed correctly:
  7. Make the Volume/LUN a Command Device:
    1. Log into the Storage System.
    2. Expand the Storage System folder and select Logical Devices.
    3. Select the Logical Device (LUN / Volume) that you want to make a Command Device.
    4. Click More Actions > Edit Command Devices.
  8. Enable the logical device as a Command Device:
  9. (Virtual Machines on ESX hosts only / For physical hosts, skip this section)  Raw Device Mapping or LUN allocation will not work for Virtual Machines on ESX Hosts. The HBA port or HBA Card must be allocated directly to the VM. The server needs to be vt-d compatible and have sufficient free HBA ports for each instance of the SMI-S provider you require. To allocate a port for passthrough:
    1. Under the ESX Host’s Configuration tab, select Advanced Settings and click Configure Passthrough:
    2. Select the HBA port(s) that you wish to allocate to VMs:
    3. Click OK.
    4. Restart the ESX Server.
    5. Add the HBA ports to the Virtual Machine:
    6. Once the VM or Physical server sees the LUN, Windows should find a new hard drive:
    7. Click OK to create an MBR (Master Boot Record).
    8. Run the following command:   C:\Program Files (x86)\HDVM\HBaseAgent\bin>perf_findcmddev.exe view
    9. If the Storage System does not appear, run:   C:\Program Files (x86)\HDVM\HBaseAgent\bin\hldutil
    10. Refer to the RAID ID Translation Table below to find the OPEN-V-CM (command device LUN) for the storage system:
    11. R700 for VSP
    12. R600 for USP-V
    13. R601 for USP-VM
    14. Edit the file: C:\Program Files (x86)\HDVM\HBaseAgent\mod\hdvm\config\type perf_cmddev.properties
    15. Translate the information from hldutil to perf_cmddev.properties

      Disk1     HITACHI  OPEN-V-CM        CL1-A 0     0    00:8C 14EAE
      R700   0-0   2100001B3284D3DD  2000001B3284D3DD
      R700.85678.0.140 : \\.\PhysicalDrive1
      The Disk Number and Model number can be copied directly.
      The Serial, CU, and LDEV Number need to be translated from HEX to Decimal.

    16. Run perf_findcmddev view to check configuration:
    17. Run perf_findcmddev verify to ensure configuration is valid:
    18. The verify command will highlight any invalid or non-functional lines in the configuration:
    19. If the configuration is valid, use the perf_findcmddev write command to save the configuration.  Any invalid configuration lines (such as PhysicalDrive2 in the example above will be removed from the configuration by the write command)
  10. Configure the Hitachi Command View server to use the agent:
    1. Edit Hitachi\HiCommandServer\config\server.properties
    2. Search for the following line:
      # host name for the CIM agent
      server.cim.agent=
    3. Add the hostname for the CIM agent.  The hostname should be the short, non-FQDN of the server:
      # host name for the CIM agent
      server.cim.agent=Hitachi-SMIS
    4. If the server is the same as the agent (by default), take the hostname from the server variable:
      server.http.host= Hitachi-SMIS
  11. Restart the Server (or restart all Hitachi Services).
  12. Log into Hitachi Command View Server after reboot to ensure that it is working.

Enabling Monitoring

 With BMC Performance Manager Express for Hardware:

  1. Add the server onto which the Hitachi Device Manager was installed as an element of type "Storage" in Portal.
  2. In the Configure tab of the BMC Portal, click the Element to which you wish to add the Disk Arrays solution and the Element Properties page appears. Scroll down to Application Classes › Add. Make sure that the element's platform is defined as Storage.
  3. On the Properties – ‹Element› – Add Application Classes page › Select Category › Storage.
  4. In the available Application Class list, select the application class applicable to the element and click Next.
  5. The Properties and Credentials page is displayed; enter the username and password specified when installing the CIM agent. Check the protocol (http/https) and port (5988 / 5989).

With Hardware Sentry KM for PATROL:

  1. Right click the local host’s 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 system you want to monitor remotely and click Next
    1. Enter the host name of the remote system (Server on which the Hitachi Device Manager is installed)
    2. Leave the "IP address or fully qualified name" field blank if you specify the host name above
    3. Select the Storage (Array, switch, Library) platform from the drop down list to specify the system type.

    Note: If the PATROL Agent and Hardware Sentry KM run on the same system where the Hitachi Device Manager has been installed, specify "localhost" for the IP address or hostname of the device.

  1. Select the Hitachi HDS Disk Arrays connector for Hardware Sentry to use to monitor the remote system and click Next.
  2. Enter the WBEM credentials and click Next
    1. Check the protocol (http (not encrypted) / https (encrypted)) and port (5988 / 5989).
    2. Enter a Login and a Password (the username and password specified when installing the CIM agent)
  3. Hardware Sentry needs to perform a full discovery to add the remote device, click Finish to launch the discovery.
  4. A new Hardware icon will automatically be added in the console

With BMC Performance Manager Express for Hitachi Disk Arrays:

  1. In the Configure tab: Click the Element to which you wish to add the Hitachi Disk Arrays solution and the Element Properties page appears. Scroll down to Application Classes > Add. Make sure that the element's platform is defined as Storage.
  2. On the Properties – <Element> – Add Application Classes page > Select Category > Storage.
  3. In the available Application Class list, select the application class applicable to the element and click Next.
  4. The Properties and Credentials page appears asking for the information required for monitoring the disk array. Enter the WBEM username and password valid on the Hitachi Device Manager.

With Hitachi Disk Arrays KM for PATROL:

  1. Right-click the Disk Array Icon › KM Commands › Add a Connection to a Hitachi Device Manager...
  2. Define the provider information:
    1. Enter the server host name (Server on which the Hitachi Device Manager is installed)
    2. Enter the IP address or the fully qualified name.
  3. Click Next
  4. Define the WBEM Credentials:
    1. Enter the Port number that will be used for the connection to the CIM server
    2. Check the Encrypt data using HTTPS protocol box to turn on the encryption when performing WBEM queries, if necessary
    3. Enter the Login and Password that will be used for the connection to the CIM server

      Note: When the login and password are left blank the default PATROL credentials will automatically be used for the connection

    4. Click Next
  5. A refresh of the Hitachi Device Manager needs to be periodically performed to make sure that configuration changes are taken into consideration.
    Define the auto refresh frequency.
    Note: Refreshing the Hitachi Device Manager is resource intensive and time consuming
  6. Click Finish to save your settings