Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Storage Manager (STM) > Storage Manager (STM) Documentation > SRM Profiler Administrator Guide > Appendices > Configure storage arrays > Hitachi Data Systems HDS provider

Hitachi Data Systems HDS provider

Updated: June 16, 2017

This information is provided 'as-is' as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor's SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you.

Pre-configuration requirements

Before beginning the host agent installation, you must create and assign command devices so that connectivity can be established between the host agent and the disk arrays.

Refer to your product's HDS documentation for the most up to date information.

Some guidance for installing the HDvM and HiCommand is provided below.

Install and configure the Hitachi Device Manager (HDvM)

  1. Install HDvM Agent on a host that can communicate to the HDvM Server.
    • You can install HDvM agent in HDvM Server itself (recommended) or you can use any Windows, Solaris and Linux machines.
  2. Map the HDvM Agent.
    • During the Agent installation, you will get a message to configure the agent now or later. If you configure it during the installation you have to setup the IP/HOSTNAME of HDvM Server along with Credentials to access it.
    • If you choose to do it later, you can do it via command line with the "hdvmagt_setting" command under <HDvM Agent Install Dir>\Hitachi\HDVM\HBaseAgent\bin\ directory.
  3. Navigate to the directory: <HDvM Agent Install Dir>\Hitachi\HDVM\HBaseAgent\bin\
    • Manually run the HiScan command to verify the connectivity:

"HiScan –s 'IP/HOSTNAME of HDvM Server'" by navigating to <HDvM Agent Install Dir>\Hitachi\HDVM\HBaseAgent\bin\ directory.

  1. Configure the HDvM agent to collect the performance files.
    • Navigate to the directory,
      <HDvM Agent Install Dir>\Hitachi\HDVM\HBaseAgent\bin\
    • Run the command to write a new file: perf_findcmddev write


    • You can also view and verify the results by perf_findcmddev view and perf_findcmddev verify commands.


  1. Restart the HDvM Agent.


  2. To collect performance data, configure HDvM Server to use your HDvM agent.
    • Edit the files and specify the exact hostname of the HDvM Agent under "server.cim.agent".


    • You must use the exact name of the server that is listed in the hosts tree of HDvM Server.


  1. After steps 1-6 are performed, restart the HDvM Server service then restart the HDvM Agent service.

Install the HiCommand Device Manager on Windows

The following section detail installation steps for Windows. The HDS provider is part of the HiCommand Device Manager and is a purchased product.


Disabling SNMP function has no effect on SMI-s provider.


  1. Double click the HiCommand Device Manager Install package.
  2. Click Next at the welcome screen.


  3. Accept the license agreement. Click Next.
  4. Select Disable SNMP trap function if port 162 is in use. Otherwise, skip this step. Click Next.


  1. Choose the Destination folder for HiCommand. Click Next.
  2. Choose the destination for the HiCommand Suite Common Component database. Click Next.


  3. Choose the destination for the HiCommand Device manager database. Click Next.


  4. Specify the IP address of the machine HiCommand Device Manager is being installed on and Port for HBase Storage Management Web Service. Click Next.


  5. Click Next at the adding to the windows firewall exceptions screen.


  6. Select YES for enabling the SMI-s provider service after installation. Click Next.


  7. Select NO for SSL, unless a secure connection is needed. Change port if needed. Click Next.


  8. Depending on the Array type, a Device Manager agent may be needed. If it is needed, select yes and specify an IP address. Refer to the "Which HDS arrays need a Device manager agent for performance metrics to be gathered from" question in the Troubleshooting section.


  9. Select YES for the SLP function to be enabled after installation. Click Next.


  10. Select YES to start the HiCommand Suite to start after installation. Click Next.


  11. Click Install at the Pre-Installation Summary page.


  12. Click Next at the Secure Socket Certificates Note.


  13. Click Finish.


Troubleshoot HDS

The following section details troubleshooting steps for HDS.

Q: Which HDS arrays need a Device manager agent for performance metrics to be gathered from?

A: Refer to the following image (USP V/VM, and TagmaStor USP).


Q: What is the default username/password for the provider?

A: The username and password for the Provider is the same for the DataCenter (not administrator/administrator). If need be, they can create a new one for SRM Profiler.

Q: What user permissions are required for the provider?

A: All resources with view privileges.

Q: What should I do if the test results window returns blank and I am using an admin ID to access the device manager?

A: Save the resource and check the SMI-S module log. If you see an Access denied error this means that the ID you are using doesn't have the proper permissions. Use the ID: System and Password: manager (both are case sensitive). This should solve your problem.

Q. How do I enable performance statistics?

A: To enable performance on a USP/USP-v/USP-vm series storage system:

There are two pieces of software that have to be installed on the command view (in case of HP XP)/device manager server.

  1. Hitachi/XP Raid Manager software which is only needed to create the device library.
  2. Device Manager agent which can access the command device to transfer the performance data. Device Manager agent requires the Hitachi/XP Raid Manager device library to function.

The system that Device Manager/Command View is running on must have SAN access to the command device.

Follow the instructions to install the XP Raid Manager, but you do not need to actually have the HORCM process running.

For further information see the XP Command View Advanced Edition software server Administrator Guide for Device Manager and Provisioning Manager ( in case HP XP) or Hitachi Storage Command Suite Software Server Installation and Configuration Guide for Hitachi Device Manager and Provisioning Manager

To enable performance on an AMS/WMS/Thunder 9500v/Thunder 9200 series storage system:

See the XP Command View Advanced Edition software server Administrator Guide for Device Manager and Provisioning Manager ( in case HP XP) or Hitachi Storage Command Suite Software Server Installation and Configuration Guide for Hitachi Device Manager and Provisioning Manager

Q: What is the minimum provider version to get performance statistics?

A: Provider version must be High Command Device Manager 5.9 or later.

Q: What performance metrics are available?

A: Volume, port, and overall array performance metrics.

Q: Will disk or controller performance be available?

A: No. HDS does not plan to support those metrics via smi-s.

Q: Is performance supported on all arrays?

A: No. Performance is not available on the Lightning series arrays (9900, 9900-v).

NOTE: The Lightning series is obsolete and replaced by AMS/WMS.

Q: How do I enable performance on 9580?

A: Perform following steps:

  1. Start Storage Navigator
  2. Change the operation mode to Management Mode
  3. Selected Performance tab from Settings-->Configuration Settings menu.
  4. Select the Performance Statistics tab.
  5. Check all performance choices

Q: What is the difference between Tagma Store and USP?

A: Tagma Store is an outdated name, and has since been replaced with USP naming convention.

Storage System

HDS Models

Rebranded HP Models

Rebranded SUN Models

Lightning 9900

9910, 9960

XP48, XP512


Lightning 9900-V

9970V, 9980V

XP128, XP1024



R600, R601

XP20000, XP24000



USP100, USP600, USP1100, NSC55

XP10000, XP12000, SVS200


Thunder 9500-V

9520V, 9530V, 9570V, 9580V




9200, 9200L




AMS200, AMS500, AMS1000, AMS2100, AMS2300, AMS2500












  • Midrange arrays:
    9200 (thunder)
    9500 (thunder)
    9900, 9900-v (Lightning – obsolete and replaced by AMS, WMS)
    AMS, WMS (replacement for above 9900 series)
  • Enterprise:
    USP 100, USP 600, USP 1100, NSC (1st generation arrays)
    USP-V, USP-VM (2nd generation)

Q: What is the command for getting the Hdvm data base and logs dump?


  1. Go to the High Command installation directory from a command prompt.


    Windows: C:\Program Files\HiCommand\Base\bin

    Solaris/Linux: /opt/HiCommand/Base/bin

  2. Run the command below:
    • hcmdsgetlogs /dir <empty-directory-where-to-keep-the-dump> /arc <archive-file-name>


hcmdsgetlogs /dir C:\logs_work /arc hicmd_log

In this case the dump will be in the directory C:\logs_work.

Note: User needs administrator privilege on the system to run this command.

Q: How do I change the memory settings for Device Manager?

A: Steps to change the memory settings - from "Device Manager Server Installation and Configuration Guide" Setting Memory Heap Size When Using CIM/WBEM

If CIM/WBEM functions are being used, you might have to increase the memory heap size of the Device Manager server, depending on the conditions.

that the required memory heap size differs depending on the CIM client you are using.

To change the memory heap size:

  1. Use a text editor to open the following file:
  2. installation-folder-for-the-Device-Manager-server\HiCommandServer\Server.ini
  3. Change the value of JVM_XOPT_HEAP_MAX to new-setting-value (units: MB), which is calculated by using the two formulas below:
  • JVM_XOPT_HEAP_MAX = -Xmxnew-setting-valuem
  • calculation-value-for-SMI-S-Provider = 30,000 x number-of-LDEVs x number-ofpaths-per-LDEV / 1048576

If the value of number-of-paths-per-LDEV becomes less than 1, assume that this value is equal to 1 for the calculation.

The value of calculation-value-for-SMI-S-Provider is expressed in megabytes. Round this value up to the nearest whole number. If this value is less than 256 (MB), assume that it is equal to 256 for the calculation:

  • new-setting-value = current-setting-value + calculation-value-for-SMI-S-Provider

All of the values in the above formula are expressed in megabytes.

The value of new-setting-value obtained from the above formula is the memory heap size required for obtaining the class information that belongs to the bottom layer in a CIM class.

When an upper-layer class is specified, some SMI-S clients might obtain information of all the classes below that class at the same time. In this instance, the required capacity will be larger than the value of new-setting-value obtained from this formula.

  1. Restart the Device Manager server as follows:
  1. Select Start, Programs, HiCommand, Device Manager, and then Stop Server.
  2. After the Device Manager server has stopped, select Start, Programs, HiCommand, Device Manager, and then Start Server.

Q: How do I enable SMI-S on Device Manager if I didn't enable during installation?

A: Edit the file Program Files\HiCommand\DeviceManager\HiCommandServer\config and change from to Restart HiCommand Device Manager service.

Q: How do I enable?

A: Perform the following steps:

  1. Edit C:\ProgramFiles\HiCommand\DeviceManager\HiCommandServer\config\
  2. Edit following line and set to true

# whether the server supports CIM interface or not

Q: How do I Add a Subsystem?

A: Perform the following steps:

  1. Open HiCommand Device Manager GUI.
  2. Click Subsystems.
  3. Click Add Subsystem.


  1. Select the Type of subsystem to be added.
  2. Type in the IP Address of the Controllers.
  3. Click OK.
  4. Click OK when asked "Are you sure".
    You should see:
  5. Click Close.

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