Managing and Monitoring Data Collection > Hitachi Block Storage Data Collector Policy
Version 9.1
Hitachi Block Storage Data Collector Policy
Prerequisites: A Data Collector must exist in the Portal, to which you will add Data Collector Policies. For specific prerequisites and supported configurations, see the APTARE StorageConsole 9.1 Certified Configurations Guide.
1. Select Admin > Data Collection > Collectors.
The list of currently configured Portal Data Collectors is displayed.
2. Select a Data Collector from the list.
3. Click Add and select Hitachi Block Storage.
4. Specify Data Collector Properties.
5. Add or select the parameters. Mandatory parameters are denoted by an asterisk (*):
Sample Value
The domain identifies the top level of your host group hierarchy. The name was supplied during the installation process. All newly discovered hosts are added to the root host group associated with this domain. Typically, only one Domain will be available in the drop-down list.
If you are a Managed Services Provider, each of your customers will have a unique domain with its own host group hierarchy.
To find your Domain name select Admin > Hosts and Domains > Domains.
Hitachi Device Manager Server*
The address of the Hitachi Device Manager Server—either the IP address or server name.
If this policy is being created to collect block storage shared with Hitachi NAS (HNAS), you must specify the IP address of the Hitachi Device Manager that manages the array that shares capacity with HNAS. See Configuring a Collector for Hitachi NAS Block Storage.
User ID*
Use the User ID and passcode as defined in Hitachi Device Manager (HDvM). This typically would be an administrator privilege, but must be a minimum privilege of a view-only user. Create a new user with view-only privileges and add the user to ViewGroup, a built-in HDvM group. See Configuring a Hitachi Device Manager User.
For Hitachi Device Manager 7.1.1 and 7.2, the user ID configured to access HDvM must have view permissions to HRpM and HTSM.
Note: The password is encrypted prior to saving in the database and is never visible in any part of the application.
Exclude Arrays
Enter one or more array names to be excluded.
Comma-separated names are supported. Example: USPV1_172.16.1.13, USPV1_172.16.1.14,
AMS - Corporate(5100)@
Array Details
Click the check box to activate array details collection. Click the clock icon to set the schedule.
For example:
*/30 * * * * means every 30 minutes
*/20 9-18 * * * means every 20 minutes between the hours of 9am and 6pm
*/10 * * * 1-5 means every 10 minutes Mon - Fri.
Array Performance
Click the check box to activate performance collection and enable entries and selections for the HTnM Install Location and the Performance Schedule.
Note that at least one collection from this array must be performed BEFORE array performance data can be collected.
Requirement: To collect performance data from Hitachi Tuning Manager, the Data Collector must be installed on the same server as Tuning Manager. And, a single Data Collector policy must be used to collect both the capacity data from the Device Manager server and the performance data from the Tuning Manager server.
HTnM Install Location
Specify the Tuning Manager server installation directory. By default, the Tuning Manager server will be installed in the following locations:
Windows Server 2003 (x86) and Windows Server 2008 (x86):
%SystemDrive%\Program Files\HiCommand\TuningManager
Windows Server 2003 (x64) and Windows Server 2008 (x64):
%SystemDrive%\Program Files (x86)\HiCommand\TuningManager
Solaris: /opt/HiCommand/TuningManager
HDT Collection
Activate HDT Collection. An HDT Schedule is not required if your HDvM is not managing VSP arrays running HDT.
Click the clock icon to create a schedule frequency. You can schedule the collection frequency by minute, hour, day, week and month. Relative schedules are relative to when the Data Collector is restarted. Advanced use of native CRON strings is also available.
6. Click OK to save the Policy and return to the Collection Administration window where the Policy will be listed under the Data Collector.
7. On the Data Collector server, install/update the Data Collector software.
Configuring a Hitachi Device Manager User
The Data Collector requires read-only permission to gather data from Hitachi Device Manager (HDvM). This requires an HDvM read-only user.
To configure a read-only user, take the following steps.
1. Login to Hitachi Device Manager.
2. From the Administration tab, click Users and Permissions.
3. Under Users and Permissions, select Users and click Add User.
4. For the User ID, enter aptare and fill in the required user fields and click OK.
5. Under Users and Permissions, select Users again to verify the account that you just created.
6. Click the Change Permission tab for the aptare user only.
7. Check the boxes under the View column to configure read-only permission for each component.: HTnM, HRpM, HTSM, and HCSM.
8. Click OK to save the permissions for the aptare user.
9. From the Administration tab, click User Groups.
10. Select ViewGroup, which is a built-in user group.
11. In the ViewGroup window, click Add Users.
12. Select the aptare user and click OK.
Validate the User ID Access
1. To list the aptare user configured on Hitachi Device Manager, use the Hitachi Device Manager XML API, connecting via:
Hitachi Device Manager IP address
Default port number allocated to this server
2. Copy and paste the following XML request into the Server Administration Service API window and click Submit.
<?xml version="1.0"?>
<APIInfo version="7.2"/>
<Get target="User">
Sample output from this request:
This XML response lists the aptare user as a Guest role. The Guest role has read-only permission, sufficient for collecting data from Hitachi storage arrays.
Configuring a Collector for Hitachi NAS Block Storage
If you are configuring a Hitachi Data Systems policy to collect block storage shared with Hitachi NAS (HNAS), you will need the IP address of the Hitachi Device Manager server.
1. In the HNAS UI, go to: Home > Storage Management > Hitachi Device Managers.
2. Use the Device Manager’s default user name and password.