Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Storage Resource Monitor (SRM) > SRM: Enable a Hitachi Device Manager SMI-S provider

SRM: Enable a Hitachi Device Manager SMI-S provider

Updated: 11/1/16

Overview

There are two different types of SMI-S providers supported by HDS.  One is the Device Manager, which is part of the Hitachi Command Suite which runs on a separate server. The other one is The Embedded Provider, which runs on the Storage Array's SVP ( Service Processor). Some models are only supported by the Embedded Provider, some models are only supported by the Device Manager, and some models are supported by both. 

The Embedded Provider is recommended if available.

Environment

  • SRM 6.2+

Credentials required to add the array

Ensure you have the following information:

  • IP address or hostname for the provider.
  • Provider username
  • Provider password
  • Protocol. The default is HTTPS
  • HTTP port. The default is 5988
  • HTTPS port. The default is 5989
  • Interop namespace.  The default is: /interop
  • Array namespace. The default is: root/smis/current

Enable SMI-S

  1. Locate the server.properties file.
    The location of the file is as follows:
    Windows: <Hitachi Command Suite installation folder>\Device Manager\HiCommandServer\ config\server.properties
    Linux: <Hitachi Command Suite installation folder>/HiCommandServer/config/ server.properties
  2. Ensure that the server.cim.support property in the server.properties file is set to true.
  3. Restart the Hitachi Command Suite product services.

Change the ports( if required)

The default ports used by the Device Manager are 5998 (for HTTP) and 5989 (for HTTPS).

If the ports need to be changed should there be a conflict with other applications.

For non-SSL (HTTP) communication

  1. Open the server.properties file for editing.
    The location of the file is as follows:
    Windows: <Hitachi Command Suite installation folder>\Device Manager\HiCommandServer\config\server.properties
    Linux: <Hitachi Command Suite installation folder>/HiCommandServer/config/ server.properties
  2. Change the following property value in the server.properties file:
    HTTP - server.cim.http.port
    to, for example: server.cim.http.port=5998
  3. Check If the server cim.support.protocol property is correctly set to use HTTP. The value should be either 1 or 3.
    server.cim.support.protocol=1, to open the HTTP port for communication.
    server.cim.support.protocol=3, to open both HTTP and HTTPS ports for communication.
  4. Save the file.
  5. Edit the cimxmlcpa.properties file and change the HTTPPort value to be the same as the one that was previously set. Save the file.
    The location of the file is as follows:
      Windows: <Hitachi Command Suite installation folder>\Device Manager\HiCommandServer\wsi\ server\jserver\bin
      Linux: <Hitachi Command Suite installation folder>/HiCommandServer/wsi/server/jserver/bin
    Create a backup copy of the file, as it will be deleted when the services restart.

    If the cimxmlcpa.properties file does not exist by default, create a new file by that file name and specify the property in the following format: HTTPPort=port-number.

  6. Restart the Hitachi Command Suite product services.

For SSL (HTTPS) communication

  1. Open the server.properties file for editing.
    The location of the file is as follows:
    Windows: <Hitachi Command Suite installation folder>\Device Manager\HiCommandServer\config\properties
    Linux: <Hitachi Command Suite installation folder>/HiCommandServer/config/ server.properties
  2. Change the following property value in the server.properties file:
    HTTPS - server.cim.http.port
    to, for example: server.cim.http.port=5989
  3. Check If the server cim.support.protocol property is correctly set to use HTTP. The value should be either 2 or 3.
    server.cim.support.protocol=2, to open the HTTPS port for communication.
    server.cim.support.protocol=3, to open both HTTP and HTTPS ports for communication.
  4. Save the file.
  5. Edit the cimxmlcpa.properties file and change the HTTPPort value to be the same as the one that was previously set. Save the file.
    The location of the file is as follows:
    Windows:<Hitachi Command Suite installation folder>\Device Manager\HiCommandServer\ wsi\server\jserver\bin
    Linux: <Hitachi Command Suite installation folder>/HiCommandServer/wsi/server/ jserver/bin
    Create a backup copy of the file as it will be deleted when the HP XP CVAE services restarts.

    If the cimxmlcpa.properties file does not exist by default, create a new file by that file name and specify the property in the following format: HTTPPort=port-number.

  6. Restart the Hitachi Command Suite product services.

Enabling Performance Data Collection

Enterprise class storage arrays (USP, USP-v, USP-VM, and VSP)

For enterprise class storage arrays, a Device Manager Agent is required which collects the performance data from the storage arrays using command devices and report the data back to the Device Manager Server which has the SMI-S provider.

  1. Prepare the command devices for each enterprise class storage arrays by using the Hitachi Command Suite GUI.
  2. Assign the command device to the server on which the Device Manager Agent is going to be installed.
  3. Install the Device Manager Agent and set it up to communicate with the Device Manager Server.

It is recommended to install the Device Manager Agent on the same server where the Device Manager Server is installed. Otherwise, it can be installed on a separate server with Windows, Solaris, or Linux.

During the agent installation, you will get a message to configure the agent now or later. Provide the IP address/hostname of the Device Manager Server along with the credentials to access it.

If the Device Manager Agent is already installed, but not setup to communicate with the Device Manager Server, do the following steps:

  1. Stop the Device Manager Agent service.
  2. Run the hdvmagt_setting command.
    The location is as follows:
    Windows: <Device Manager Agent installation folder>\bin
    Linux: <Device Manager Agent installation folder>/bin
    Solaris: /opt/HDVM/HBaseAgent/bin
  3. Provide the IP Address or Hostname of the Device Manager Server.
  4. Provide the Port Number. The default is 2001.
  5. Provide the User ID and Password. Enter the user ID and password for the Device Manager Agent registered with the Device Manager Server.
  1. Register the command devices from the storage arrays to the Device Manager Agent.
    1. Create a backup of the perf_cmddev.properties file.
      The location is as follows:
      Windows: <Device Manager Agent installation folder>\mod\hdvm\config
      Linux: <Device Manager Agent installation folder>/mod/hdvm/config
      Solaris: /opt/HDVM/HBaseAgent/mod/hdvm/config

    2. Use the perf_findcmddev command to register command devices.
      The location is as follows:
      Windows: <Device Manager Agent installation folder>\bin
      Linux: <Device Manager Agent installation folder>/bin
      Solaris: /opt/HDVM/HBaseAgent/bin
    3. Run the perf_findcmddev write command.
      This will discover all command devices mapped to this server and update the perf_cmddev.properties file with the information.
    4. Open the perf_cmddev.properties file and verify that the command devices from the enterprise storage arrays are listed.
      Entries in the file are in the following format:
      RAID-ID.serial-number.[SLPR-number.]LDEV-number: deviceFileName
      For example, R600.44332.456: \\.\PhysicalDrive3
      Where,
      • RAID-ID
        • R700 - VSP
        • R600 - USP-v
        • R601 - USP VM
        • R500 - USP VM
      • Serial Number is the serial number of the storage array expressed as base 10 number.
      • SLPR Number - is optional. This represents the number of SLPR to which the command device belongs. It is also in base 10 format.
      • LDEV-number is the CU:LDEV number of the command device in base 10 format.
      • deviceFileName is the command device identifier that the server recognizes.
        • Windows: \\.\PhysicalDriveX or \\.\Volume{GUID}
        • Linux: /dev/sdx
        • Solaris: /dev/rdsk/cxtxdxs2
  2. Restart the Device Manager Agent service.
  3. Configure the Device Manager Server to communicate with the Device Manager Agent.
    1. Open the server.properties file on the Device Manager Server.
    2. Set the server.cim.agent property value to the hostname of the server where the Device Manager Agent is installed.

      You must use the exact hostname as registered with the Device Manager Server. If these hostnames are different, you cannot acquire performance data. To locate the registered hostname, open the Device Manager Server GUI and locate the hosts tree.

  4. Restart the Hitachi Command Suite (with Device Manager Server).

Mid-range storage arrays (HUS 100, AMS, WMS, and SMS)

For mid-range storage arrays, the Device Manager Server collects directly from the storage arrays over the management interface. There is no Device Manager Agent required.

  1. Create a user account on the storage array with read-only permission for collecting data performance data from the storage arrays. Using this account prevents locking of the storage system when performance data is being requested. If more than one mid-range is being monitored in the Device Manager, the user account must be created for each storage array.
  2. Register the created user account with the Device Manager Server for collection performance information.
  3. Execute the hdvmmodpolluser command.
    The location is as follows:
    Windows: <Hitachi Command Suite installation folder>\DeviceManager\HiCommandServer\ tools
    The syntax is as follows:
    hdvmodpolluser -u <Device Manager Server user id> -p <Device Manager Server user password> <user id of the user created in step 1> <password of the user created in step 1>

    The <Device Manager user> used must have a Device Manager role as Admin and that All Resources must be assigned as the resource group.

Increase the memory heap size

To increase the memory heap size:

  1. Edit the memory configuration file.
    The location is as follows:
    Windows: <Hitachi Command Suite installation folder>\Device Manager\HiCommandServer \Server.ini
    Linux: <Hitachi Command Suite installation folder>/hicommand.sh
  2. Change the value for JVM_XOPT_HEAP_MAX.
    For example: to update to 4GB, JVM_XOPT_HEAP_MAX = -Xmx4096m
  3. Save the file.
  4. Restart the Hitachi Command Suite service.

Memory requirement for the Device Manager

Follow the memory requirement for the Device Manager as suggested by Hitachi. Refer to the following information for the required memory for the HDS HDVm SMI-S provider.

heap max size for smi-s provider = (30000 x number of LDEVs x number of paths per LDEV) / 1048576 megabytes

If the value of the number of paths per LDEV becomes less than 1, assume that this value is equal to 1 for the calculation. Round up this value to the nearest whole number. If this value is less than 256 MB, assume that it is equal to 256 for the calculation.

Starting/Stopping Hitachi Command Suite

Windows Server 2008 R2

To start: Select Start > All Programs > Hitachi Command Suite > Manage Services > Start - HCS

To stop: Select Start > All Programs > Hitachi Command Suite > Manage Services > Stop - HCS

Windows Server 2012

To start: From the Start window, open the application list window and select Hitachi Command Suite and then, Start - HCS

To stop: From the Start window, open the application list window and select Hitachi Command Suite and then, Stop - HCS

Linux

To start: Execute <Hitachi Command Suite installation folder>/Base64/bin/hcmds64srv -start

To stop: Execute <Hitachi Command Suite installation folder>/Base64/bin/hcmds64srv -stop

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

 

 

Last modified
15:12, 10 Nov 2016

Tags

Classifications

Public