hitachi device manager etl v7.1.00 for bmc truesight ... device manager etl for bmc truesight...

Hitachi Device Manager ETL for BMCTrueSight Capacity Optimization

USER DOCUMENTATION

Version 7.1.00

September 2015

STORAGE CAPACITY OPTIMIZATION

http://www.sentrysoftware.com

http://sentrysoftware.com/Solutions/Hardware_solution.asp

Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you canobtain information about the company, its products, corporate offices, special events, and careeropportunities.

United States and Canada

Address BMC Software, Inc.2101 CityWest Blvd. Houston TX77042-2827

Telephone 1 (713) 918 8800 or 1 (800) 841 2031 (Toll Free)

Copyright 2006 BMC Software, Inc. or licensors, as an unpublished work. All rights reserved.

BMC Software, the BMC Software logos, and all other BMC Software product or service names areregistered trademarks or trademarks of BMC Software, Inc.

All other trademarks belong to their respective companies.

BMC Software considers information included in this documentation to be proprietary andconfidential. Your use of this information is subject to the terms and conditions of the applicableEnd User License Agreement for the product and the proprietary and restricted rights noticesincluded in this documentation.

Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVEDUNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any dataand computer software by the U.S. Government is subject to restrictions, as applicable, set forthin FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, andDFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software,Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to thisaddress.

2

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Customer Support

You can obtain technical support by using the Support page on the BMC Software Web site or bycontacting Customer Support by telephone or e-mail.

Support Web Site

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support_home. From this Web site, you can:

Read overviews about support services and programs that BMC Software offers

Find the most current information about BMC Software products

Search a database for problems similar to yours and possible solutions

Order or download product documentation

Report a problem or ask a question

Subscribe to receive e-mail notices when new product versions are released

Find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers

You can also access product documents and search the Knowledge Base for help with an issue at http://www.sentrysoftware.com

Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web,call 800 537 1813. Outside the United States and Canada, please contact your local support centerfor assistance. To find telephone and email contact information for the BMC Software supportcenter that services your location, refer to the Contact Customer Support section of the Supportpage on the BMC Software Web site at http://www.bmc.com/support_home.

3

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

http://www.bmc.com/support_home


http://www.sentrysoftware.com


4

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Table of Contents.....................................................................................................................................................................................6Release Notes v7.1.00

.....................................................................................................................................................................................7Overview

.....................................................................................................................................................................................9Supported Platforms and Versions

.....................................................................................................................................................................................10Prerequisites

.......................................................................................................................................................................................10Installing Hitachi Device Manager

......................................................................................................................................................................10Installing the Hitachi Command Suite

......................................................................................................................................................................13Installing the Device Manager Agent

......................................................................................................................................................................20Configuring the Hitachi Device Manager

.......................................................................................................................................................................................28Enabling Statistics

.....................................................................................................................................................................................33Installing the ETL

.....................................................................................................................................................................................35Restarting the Scheduler Service

.....................................................................................................................................................................................36Configuring the ETL

.....................................................................................................................................................................................38Including Domain Suffix in System Name

.....................................................................................................................................................................................39Customizing Volumes Monitoring

.....................................................................................................................................................................................41Customizing Collection Level

.....................................................................................................................................................................................42Setting the Collect Frequency

.....................................................................................................................................................................................44Running the Extractor Service Task

.....................................................................................................................................................................................47Configuring Log Level

.....................................................................................................................................................................................48Collecting Logs for a Specific ETL

.....................................................................................................................................................................................50Grabbing All Logs

.....................................................................................................................................................................................54STOCONT Dataset Performance Metrics

.....................................................................................................................................................................................56STOGLB Dataset Performance Metrics

.....................................................................................................................................................................................66STOHOST Dataset Performance Metrics

.....................................................................................................................................................................................67STOSSW Dataset Performance Metrics

Introduction

6Release Notes v7.1.00

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Release Notes v7.1.00What's New

Support for HP XP P9000 and HP XP P9500 disk arrays.

The new metric ST_DISK was added to the STOGLB dataset to expose the total number ofused disks.

Changes and ImprovementsVolumes Monitoring configuration has been improved to be more user-friendly. A singleoption is now available to enable/disable volumes monitoring and volumes import.

The SA_CONTAINS_LUN and SP_CONTAINS_LUN relations have been respectively replacedby SA_CONTAINS_VOLUME and SP_CONTAINS_VOLUME.

The computation method for the ST_SYSTEM_SUBSCRIBED_CAPACITY andST_POOL_SUBSCRIBED_CAPACITY metrics has been modified and is now the sum of the hostvisible capacity of the mapped volume.

Fixed IssuesAn error occurred when deploying the ETL package v7.0.00 with BMC TrueSight CO 10.3 on anOracle database.

The ST_CONSUMED_CAPACITY and ST_AVAILABLE_FOR_STORAGE_POOLS metrics did notexpose the actual value for HP XP P9500 disk arrays.

Connector's loading has been improved to prevent failures when local store files arecorrupted.

7 Release Notes v7.1.00

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

OverviewHitachi Device Manager ETL for BMC TrueSight Capacity Optimization is a connector specificallydesigned for BMC TrueSight Capacity Optimization and can be defined as an ETL Service, named Storage - Hitachi Device Manager Extractor Service, that continuously polls and collects data fromthe Hitachi Device Manager. Once the ETL is properly configured, the Storage - Hitachi DeviceManager Extractor Service task collects all the metrics required for performing critical capacityoptimization tasks, such as: analysis, trending, simulation and analytic modeling.

Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization Architecture Diagram

Getting Started

9 Supported Platforms and Versions

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Supported Platforms and VersionsHitachi Device Manager ETL for BMC TrueSight Capacity Optimization supports the followingHitachi systems:

Hitachi Adaptable Modular Storage 2000 family (AMS)

Hitachi Unified Storage (HUS)

Hitachi Universal Storage Platform (USP, USP-V/USP-VM)

Hitachi Virtual Storage Platform (VSP systems with Basic Operating System)

as well as:

HP XP P9000

HP XP P9500

Supported Versions of BMC TrueSight Capacity Optimization

Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization supports:

BMC TrueSight Capacity Optimization v10.0.00.01 with Cumulative HotFix 05 (CHF5)

BMC TrueSight Capacity Optimization v10.3

10Supported Platforms and Versions

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

PrerequisitesInstalling Hitachi Device ManagerBefore installing the Hitachi Device Manager, make sure that:

The server’s definitive name has been set. The installation of this software setsconfiguration variables based on the server’s DNS Name.

Adobe Flash Player is installed.

Monitoring history will be lost when upgrading to Hitachi Device Manager v.8.

Installing the Hitachi Command Suite

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

1. Double-click the Index.html file

11 Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

2. Click Install to launch the Hitachi Command Suite installer:

3. Click Next.

12Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

4. Choose the installation folder and click Next.

5. Click Install.

13 Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

6. When the installation is complete, click Finish.

7. Open the Hitachi Command Suite: http://<IP_Address>:22015/DeviceManagerWebService/index.jsp

8. Click on License and Install License.

Installing the Device Manager Agent1. Log into the Hitachi Command Suite Console: http://<IP_Address>:22015/

DeviceManagerWebService/index.jsp

14Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

2. Click Install to launch the Device Manager agent installer:

3. Click Next.

15 Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

4. Select the I accept the terms of the License Agreement option and click Next

5. Choose the install folder and click Next. A screen will appear to ask you permission to add afirewall exception even if your server’s firewall is not enabled:

16Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

6. Select YES and click Next.

7. Select the user account to be used for launching the agent service. Selecting NO will use theLocal System Account (recommended). Click Next.

17 Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

8. Click Install.

9. When the installation is complete, click Yes to setup the Device Manager agent. The agentwill then check connection to Device Manager (Hitachi’s Name for Command View AdvancedEdition).

18Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

10. Select YES to specify the Device Manager server Information, change the IP address to127.0.0.1 and click Next.

11. Click OK.

19 Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

12. Select YES to enable the Execution Period of the HiScan Command. Select pre-determined orrandom hour (do not use the default 2:30am) to prevent agent conflict. Click Next.

13. Select NO in order not to set up the RAID Manager (it is not needed by Sentry / CVAE) andclick Next.

14. A message "The Device Manager agent setup has completed successfully" appears. Click OKto finish the installation.

20Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Configuring the Hitachi Device Manager1. Log into the Hitachi Command Suite Console: http://<IP_Address>:22015/

DeviceManagerWebService/index.jsp

2. Click the Add Storage System button located under the Administration > Storage Systemstabs:

3. Select the Storage System Type.

For Hitachi Series Storage System (VSP / USP-V), provide the IP address and Credentials:

For Hitachi Series Storage System (AMS), provide the Controller’s IP addresses andCredentials:

21 Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

4. Click OK. A Data Collection Task will be generated to add the Storage System. Click View TaskStatus for details.

5. Wait for the Data Collect Task to complete successfully.

6. (USP-V and VSP only) Create the Administrative LUN:

Click the Resources tab.

Expand all storage systems and select the recently added storage system.

Select Volumes.

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 VirtualServers 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

22Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Location: Internal

Click Show Plan.

Verify that the allocation task has completed correctly:

7. Make the Volume/LUN a Command Device:

Log into the Storage System.

Expand the Storage System folder and select Logical Devices.

Select the Logical Device (LUN / Volume) that you want to make a Command Device.

Click More Actions > Edit Command Devices.

23 Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

8. Enable the logical device as a Command Device:

9. (Virtual Machines on ESX hosts only / For physical hosts, skip this section) Raw DeviceMapping or LUN allocation will not work for Virtual Machines on ESX Hosts. The HBA port orHBA Card must be allocated directly to the VM. The server needs to be vt-d compatible andhave sufficient free HBA ports for each instance of the SMI-S provider you require. To allocate a port for passthrough:

Under the ESX Host’s Configuration tab, select Advanced Settings and click ConfigurePassthrough:

24Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Select the HBA port(s) that you wish to allocate to VMs:

Click OK.

Restart the ESX Server.

Add the HBA ports to the Virtual Machine:

25 Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Once the VM or Physical server sees the LUN, Windows should find a new hard drive:

Click OK to create an MBR (Master Boot Record).

Run the following command: C:\Program Files (x86)\HDVM\HBaseAgent\bin>perf_findcmddev.exe view

26Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

If the Storage System does not appear, run: C:\Program Files (x86)\HDVM\HBaseAgent\bin\hldutil

Refer to the RAID ID Translation Table below to find the OPEN-V-CM (command deviceLUN) for the storage system:

R700 for VSP

R600 for USP-V

R601 for USP-VM

10. Edit the file: C:\Program Files (x86)\HDVM\HBaseAgent\mod\hdvm\config\typeperf_cmddev.properties

11. 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.

27 Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

The Serial, CU, and LDEV Number need to be translated from HEX to Decimal.

Run perf_findcmddev view to check configuration:

Run perf_findcmddev verify to ensure configuration is valid:

The verify command will highlight any invalid or non-functional lines in the configuration:

If the configuration is valid, use the perf_findcmddev write command to save theconfiguration. Any invalid configuration lines (such as PhysicalDrive2 in the example abovewill be removed from the configuration by the write command.

12. Configure the Hitachi Command View server to use the agent:

Edit Hitachi\HiCommandServer\config\server.properties

Search for the following line: # host name for the CIM agent

server.cim.agent=

28Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

13. Add the hostname for the CIM agent. The hostname should be the short, non-FQDN of theserver: # host name for the CIM agent

server.cim.agent=Hitachi-SMIS

14. If the server is the same as the agent (by default), take the hostname from the servervariable: server.http.host= Hitachi-SMIS

15. Restart the Server (or restart all Hitachi Services).

16. Log into Hitachi Command View Server after reboot to ensure that it is working.

Enabling StatisticsOn Hitachi storage systems, the statistics need to be enabled to allow Hitachi Device Manager ETLfor BMC TrueSight Capacity Optimization to monitor performance.

Log on to the Hitachi Storage Navigator Modular console with the administrator’s account.

1. In the left pane menu, expand Resource. Click Arrays.

2. Select the array from the Array Name list. The interface corresponding to the selected diskarray opens.

Selecting the array from the Array Name list

29 Prerequisites

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

3. In the tree view related to your disk array, click Performance > Monitoring.

Enabling Statistics - Monitoring

4. Click the Change Measurement Items button to display the Performance MeasurementItems Property.

Enabling Statistics - Changing measurement items

5. Check each item check-boxes and click OK to finish.

Getting the Installation Package

31

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

The installation package for Hitachi Device Manager ETL for BMC TrueSight Capacity Optimizationcan be downloaded from the BMC Electronic Product Distribution site or directly from the SentrySoftware Web site. The file can be saved on any server accessible via the BMC TrueSight CapacityOptimization Console.

http://www.bmc.com/support/downloads-patches/BMC-Support-Product-Downloads-and-Patches.html

http://www.sentrysoftware.com/Products/

http://www.sentrysoftware.com/Products/

Integrating the ETL

33

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization is a connector specificallydesigned to interact with the BMC TrueSight Capacity Optimization environment. It relies on theBMC TrueSight CO interface and features for integrating, managing and processing theperformance metrics of your Hitachi systems.

Before installing, make sure that all the prerequisite operations have been properly completed (refer tothe Getting Started chapter).

Installing Hitachi Device Manager ETLfor BMC TrueSight CapacityOptimizationThis section provides the step-by-step procedure to upload Hitachi Device Manager ETL for BMCTrueSight Capacity Optimization into the BMC TrueSight Capacity Optimization Console. Theupload procedure is quick and easy, as it relies on the Upload patch or additional packagemechanism accessible in the BMC TrueSight Capacity Optimization Console under the section Administration > System > Maintenance.

Uploading Hitachi Device Manager ETL for BMC TrueSight CapacityOptimization

To upload Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization into the BMCTrueSight Capacity Optimization Console:

1. Access the BMC TrueSight Capacity Optimization Console.

2. In the Administration tab, click System > Maintenance:

Verify the installation status of the already uploaded packages. If their status is "READY" or"RUNNING", wait for the installation to complete before proceeding.

At the bottom of the Maintenance page, locate the Upload patch or additional package filesection:

Click Browse.

Locate and select the file Hitachi-Device-Manager-ETL-for-BMC-TrueSight-CO-7.1.00.zip.

Click Upload.

34Installing the ETL

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

3. Read the Overview and click Next to continue.

4. Read and accept the End User License Agreement.

5. Select the server on which the operation must be executed; that is the server on which thepackage will be saved. Click Proceed to continue.

35 Installing the ETL

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

6. A successful installation will result in a green line in the Additional Packages table.

In case of unsuccessful outcome (e.g. a yellow WARNING line), click the icon to inspect the deploymentlog.

7. Manually restart the scheduler service to complete the installation.

Restarting the Scheduler ServiceA manual restart of the scheduler service is required to complete the installation of HitachiDevice Manager ETL for BMC TrueSight Capacity Optimization:

1. Open a shell command (SSH) on all the scheduler hosts and connect as cpit user

2. Navigate to the BCO home directory[cpit@bco ~]$ cd /opt/bmc/BCO

3. Execute the following script to restart the scheduler service[cpit@bco BCO]$ ./cpit restart scheduler

36Restarting the Scheduler Service

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Configuring the ETLThis chapter details every steps required to configure an ETL Service and add it as an ETL taskresponsible for extracting capacity and performance metrics on Hitachi storage systems from theHitachi Device Manager and feeding it into the BMC TrueSight Capacity Optimization DataWarehouse.

To configure the ETL:

1. Access the configuration window:

In the Administration tab, click ETL & System Tasks > ETL tasks.

Press the Add button, and select Add ETL.

2. Expand the Run configuration menu:

From the ETL module pull-down list, select Storage - Hitachi Device Manager Extractor Service.

3. Click the Edit button to add all the available datasets:

In the Available datasets list, select the datasets to be added.

Click .

Click Apply.

4. Expand the Entity catalog menu and select:

37 Configuring the ETL

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Shared Entity Catalog to avoid duplicates if several ETLs extract data from the sameresources. You will then have to specify the entity catalog with which this ETL will sharethe information.

Private Entity Catalog if only this ETL will extract data from the specified resources.

5. If you previously selected the [59] OBJREL - Object relationships dataset, you can expand theObject relationships menu to indicate the Domain tree the imported entities will populate:

choosing new Domain displays the domain default name: Storage - Hitachi Device ManagerExtractor Service. The default name is editable.

choosing existing Domain allows you to select a specific domain.

Expand the Connection settings menu:

Enter the hostname or the IP address of the server where the Hitachi Device Manager isrunning.

Indicate the port number used by the Hitachi Device Manager (default: 5989).

Enter the username and password to connect to the Hitachi Device Manager. The defaultusername is 'System'. This username is set with the mandatory administrator's rights. Ifyou wish to use a different username, make sure it has administrator's rights. For detailedinformation about the rights management, refer to the Hitachi Device Managerdocumentation.

Specify a refresh frequency for the Hitachi Device Manager to make sure configurationchanges are taken into consideration.

This operation is resource and time consuming in a large environment.

Select the Transport Protocol used by the Hitachi Device Manager (for HTTP, the default

38Configuring the ETL

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

port is 5988; for HTTPS the default port is 5989).

Include the domain suffix in the system name.

6. Click Save.

Including Domain Suffix in SystemNameBy default, Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization displays thesystem name without the domain name, which can cause several storage pools to appear withthe same name. This default behavior can however be modified by setting the option Leavedomain suffix to system name to true.

To include the domain suffix in the system name:

1. Create or edit the Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization RunConfiguration

2. Expand the Run configuration menu and click the Advanced button

39 Including Domain Suffix in System Name

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

3. Expand the Loader configuration menu.

4. Set Leave domain suffix to system name to true

5. Click Save.

Customizing Volumes MonitoringDiscovering volumes and collecting their performance metrics are resource-intensive actionsthat can create extra workload on the system. To reduce the system resource consumption,administrators can disable or enable the volumes monitoring at will and fine-tune the creation ofvolume entities into the BMC TrueSight Capacity Optimization environment.

40Customizing Volumes Monitoring

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

To customize volumes monitoring:1. Edit the Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization Run

Configuration.

2. Expand the ETL additional settings menu.

Customizing Volumes Monitoring

3. From the Volumes pull-down list, select one of the following options:

Option Result

Disabled Volumes are not discovered.Volumes-related metrics are not loaded in the console.

Use this conf iguration if the number of volumes to manage signif icantly slows downthe system performance. Disabling the volumes monitoring prevents the discovery ofany volumes and consequently does not allow the ETL to collect, save or process theirdata. Note that the calculation of metrics for other sources may be impacted (see tablebelow and reference guide).

Collected formetriccomputation(Default)

All volumes are discovered and their metrics are collected and processed.Volumes-related metrics are not loaded in the console.

Use this conf iguration if you wish to collect and process volume-related metrics withoutloading this information in the console. The collected data will however be used tocalculate metrics for other sources, when required. This will reduce the resourceconsumption of your system.

Collected andImported

All volumes are discovered and their metrics are collected and processed.Volumes-related metrics are saved in the database, processed and loaded in theconsole.

Use this conf iguration if your system is powerful enough to manage all the volumes tomonitor.

4. Click Save.

41 Customizing Volumes Monitoring

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

The table below lists the datasets and their respective metrics that are no longer collected andtherefore not displayed in the console when the volumes monitoring is disabled:

Dataset Metrics

STOGLB ST_AVAILABLE_CAPACITY (Available Capacity)

ST_AVAILABLE_CAPACITY_PCT (Available Capacity Percentage)

ST_AVAILABLE_FOR_STORAGE_POOLS (Available Capacity for Storage Pools)

ST_CAPACITY (Storage Capacity)

ST_CONSUMED_CAPACITY (Storage Consumed Capacity)

ST_CONSUMED_CAPACITY_PCT (Storage Consumed Capacity Percentage)

ST_DEVICECOUNT (Storage Devices Number)

ST_DEVICE_TOTAL (Device Space)

ST_HOSTCNT (Attached Hosts Number)

ST_OVERSUBSCRIBED_CAPACITY (Storage Oversubscribed Capacity)

ST_POOL_DEV_COUNT (Pool Devices Count)

ST_POOL_OVERSUBSCRIPTION_SITUATION (Pool Oversubscription Situation)

ST_POOL_SUBSCRIBED_CAPACITY (Pool Subscribed Capacity)

ST_POOL_SUBSCRIBED_CAPACITY_PCT (Pool Subscribed Capacity Percentage)

ST_PRIMARY_ALLOCATED (Primary Allocated Usable Space)

ST_SYSTEM_SUBSCRIBED_CAPACITY (Storage Subscribed Capacity)

ST_VOLUME_CONSUMED_CAPACITY (Volume Consumed Capacity)

ST_VOLUME_CONSUMED_CAPACITY_PCT (Volume Consumed Capacity Percentage)

ST_VOLUME_HOST_VISIBLE_CAPACITY (Host Volume Visible Capacity)

ST_VOLUME_MAPPED (Volume Mapped)

ST_VOLUME_RAID_LEVEL (Volume RAID Level)

ST_VOLUME_TIME_SINCE_LAST_ACTIVITY (Volume Time Since Last Activity)

ST_VOLUME_TRANSFER_BYTE_RATE (Volume Transfer Byte Rate)

STOHOST BYHOST_ALLOCATED (Allocated Space by Host)

BYHOST_SIZE (By Host Physical Size)

Customizing Collection LevelBy default, extended level metrics are not imported by the ETL when using v10.3 of BMCTrueSight Capacity Optimization. To import them, you will have to customize the collection leveland set it to [4] Extended.

To customize the collection level:

42Customizing Collection Level

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

1. Edit the Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization RunConfiguration.

2. Click the Advanced button.

3. Expand the Collection level menu.

4. From the Levels up to pull-down list, select [4] Extended.

5. Click Save.

6. Restart the Service ETL.

Setting the Collect FrequencyThe collect frequency is the rate at which data is collected. The collect frequency is set to 15minutes by default but can be modified to better suit your needs.

To set the collect frequency:

1. Edit the Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization RunConfiguration:


Click the link Storage - Hitachi Device Manager Extractor Service.

Click the Stop button to stop the service execution; then click the Edit button available inthe Run configurations section.

43 Setting the Collect Frequency

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Click the link provided at the bottom of the page You can manually edit ETL properties from thispage to display a list of editable options.

Locate the service.period option, and enter the number of milliseconds corresponding to thefrequency at which data will be collected.

3. Click Save.

4. Start the ETL.

44Setting the Collect Frequency

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Running Storage - Hitachi DeviceManager Extractor Service TaskThe Storage - Hitachi Device Manager Extractor Service task can be run manually to retrieveperformance metrics. Please note that the steps listed in this section are not mandatory and areonly required if the ETLs are not already scheduled for execution.

To run the Storage - Hitachi Device Manager Extractor Service task:

1. Access the BMC TrueSight Capacity Optimization Console

2. In the Administration tab, select ETL & System Tasks > ETL Tasks.

3. Click to execute the Storage - Hitachi Device Manager Extractor Service ETL task.

When the execution is complete, the value of the Status column in the ETL tasks table changes toSERVICE_ON.

Generating Log Files

46

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Introduction

The Sentry Software support team may ask you to provide log files to better diagnose the natureof a problem. You can either choose to:

Collect logs for a specific ETL (recommended)

Grab all logs

Please note that both methods require to:

Set the log level to 10 - Verbose

Wait for the connector to collect data (usually 1 hour). On some rare occasions, a highlydetailed collect (discovery) is required. In that case, the scheduler service will need to berestarted.

47

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Configuring Log LevelTo configure the log level:


2. Edit the Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization RunConfiguration:



Click the Stop button to stop the service execution; then click the Edit button availablein the Run configurations section.

48Configuring Log Level

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

From the Log level pull-down list, select 10 - Verbose to add detailed activity logs to the log file

Click Save.

3. Click the button to start the active configuration.

Collecting Logs for a Specific ETLSince version 6.0.00 of Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization, the Sentry Software's connectors logs are available in the BMC TrueSight CO console and can beeasily collected by clicking the Show Log button available in the Extractor Service page. Theprocedure to retrieve these logs is as follows:


2. Make sure that the log level is set to 10 - Verbose

3. Wait for the connector to collect data (usually 1 hour). On some rare occasions, a highlydetailed collect (discovery) is required. In that case, the scheduler service will need to berestarted.

4. Go to the Storage - Hitachi Device Manager Extractor Service page:



49 Collecting Logs for a Specific ETL

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

5. Click Show log.

6. Click Collect logs.

7. Wait for the archive to be generated.

8. Click to download the archive.

50Grabbing All Logs

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Grabbing All LogsThe log files of all BMC TrueSight Capacity Optimization components can be easily retrieved byrunning the log grabber. The procedure is as follows:


2. Set the log level to 10 - Verbose.

3. Wait for the connector to collect data (usually 1 hour). On some rare occasions, a highlydetailed collect (discovery) is required. In that case, the scheduler service will need to berestarted.

4. In the Administration tab, click System > Maintenance.

5. Open the Maintenance Activities tab.

6. Click to execute the Log Grabber.

51 Grabbing All Logs

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

7. Click Next.

8. Select the host for which you wish to obtain logs and click Proceed to execute the LogGrabber.

52Grabbing All Logs

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

9. Refresh the Maintenance Activities page to check the request status.

10. When the request status is "ENDED", click to view the deployment log.

11. Click to download the deployment log.

Reference Guide

54

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

This section provides detailed information on the performance metrics collected by the Storage -Hitachi Device Manager Extractor Service from the Hitachi Device Manager and made available inthe BMC TrueSight CO Console. Metrics are available in the following datasets:

STOCONT Dataset Performance Metrics

STOGLB Dataset Performance Metrics

STOHOST Dataset Performance Metrics

STOSSW Dataset Performance Metrics

For additional information about datasets management, refer to BMC TrueSight CapacityOptimization documentation.

[108] STOCONT Dataset PerformanceMetricsMetrics are presented in a table, where each column represents a particular variable, and eachrow corresponds to a given member of the STOCONT dataset.

Metric Unit Name Description Value Type Level1

BYCONT_PORT_NUM

N/A Number ofavailableports byController

Number ofavailableports byController.Thesubobjectspecifies thecontrollername.

Configuration data [4] Extended

BYCONT_TRANSFER_RATE

BYTE/S Transfer rateby Controller

Transfer ratebyController.Thesubobjectspecifies thecontrollername.

A frequency, inevents/sec

[4] Extended

1By default, extended level metrics will not be imported by the ETL when using v10.3 of BMC TrueSight CapacityOptimization. To import them, you will have to set the Collection level to [4] Extended. For moreinformation, refer to Customizing Collection Level.

55 STOCONT Dataset Performance Metrics

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Additional Columns

ColumnName

Unit Name Description

CONTNM N/A Storagecontroller name

Storage controller name

DS_SYSNM N/A System name inthe Datasource

The name of the system as in the Datasource (for lookup)

DURATION S Duration Duration of the sample

SYSNM N/A System name The name of the system proposed for identification in BMCCapacity Optimization; if absent, the DS_SYSNM is used

SYSTYPENM

N/A Object type Object type name

TS N/A Timestamp Start timestamp of the sample [YYYY-MM-DD HH:MI:SS]

For detailed information about datasets, refer to the BMC TrueSight Capacity Optimizationdocumentation.

https://docs.bmc.com/docs/display/public/btco103/Home


56STOCONT Dataset Performance Metrics

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

[30] STOGLB Dataset PerformanceMetricsMetrics are presented in a table, where each column represents a particular variable, and eachrow corresponds to a given member of the STOGLB dataset.

Metric Entity Unit Name Description

Value Type Level1

ST_AVAILABLE_CAPACITY2

StoragePool, StorageSystem

BYTES AvailableCapacity

Capacitynotconsumed (forstoragesystems:unusedrawspaceplusavailablecapacityinstoragepools)

Negativeaccumulation counter

[2] Basic

ST_AVAILABLE_CAPACITY_PCT2


PCT AvailableCapacityPercentage

Percentage of thestoragecapacitythat isnotconsumed

Percentage counter [2] Basic

ST_AVAILABLE_FOR_STORAGE_POOLS2

StorageSystem

BYTES AvailableCapacityforStoragePools

Rawspaceavailable forstoragepoolcreation


[2] Basic

ST_AVAILABLE_IN_STORAGE_POOLS

StorageSystem

BYTES AvailableCapacityinStoragePools

Sum ofspacenotconsumed in allstoragepools


[2] Basic

57 STOGLB Dataset Performance Metrics

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00


Value Type Level1

ST_CAPACITY2


BYTES StorageCapacity

Totalcapacity(forstoragesystems:unusedrawspaceplus sumof thecapacityfor allstoragepools)

Generic counter,absolute value

[2] Basic

ST_CONFIG_SIZE

StoragePool

BYTES StorageConfigured Space

Overallsize ofthecomponent (for astoragesystem,thisvalue isthe sumof theraw sizeof alldisks; fora storagepool thisvalue istheexternalsize)


[2] Basic

ST_CONSUMED_CAPACITY2


BYTES StorageConsumedCapacity

Actuallyconsumedcapacity


[2] Basic

ST_CONSUMED_CAPACITY_PCT2


PCT StorageConsumedCapacityPercentage

Percentage ofcapacityactuallyconsumed


ST_DEVICECOUNT2

StorageSystem

QTY StorageDevicesNumber

Numberofstoragedevices

Configuration data [2] Basic

58STOGLB Dataset Performance Metrics

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00


Value Type Level1

ST_DEVICE_TOTAL2

StorageSystem

BYTES DeviceSpace

Sum oflogicaldevicecapacityon thisarray orthearrays inthegroup


[2] Basic

ST_DISK StorageSystem

QTY TotalNumberof usedDisks

Totalnumberof useddisks


ST_HOSTCNT2

StorageSystem

QTY AttachedHostsNumber

Numberof hoststo whichdeviceson thisarray orthearrays inthegroupareallocated


ST_MICROCODE

StorageSystem

N/A Microcodeversion

Softwaremicrocodeversion


ST_OVERSUBSCRIBED_CAPACITY2


BYTES StorageOversubscribedCapacity

Storagesubscribedcapacityexceeding theactualcapacityof thecomponent


[2] Basic

ST_POOL_DEV_COUNT2

StoragePool

QTY Pooldevicescount

Pooldevicescount



Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00


Value Type Level1

ST_POOL_OVERSUBSCRIPTION_SITUATION2

StoragePool

N/A PoolOversubscriptionSituation

Identifythe over-subscribed poolsindangeri.e. thinpoolswhereSubscribedCapacityPercentage isgreaterthan 100% andtheConsumedCapacityPercentagecrossesthethreshold


ST_POOL_SUBSCRIBED_CAPACITY2

StoragePool

BYTES PoolSubscribedCapacity

Sum ofthe hostvisiblecapacityfor allvolumesin thestoragepool.Can begreaterthan theactualcapacityof thestoragepool forover-subscribed thinpools.



Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00


Value Type Level1

ST_POOL_SUBSCRIBED_CAPACITY_PCT2

StoragePool

PCT PoolSubscribedCapacityPercentage

Subscribedcapacity,inpercentage of thecapacityof thestoragepool.Canexceed100% forthinpools,thereforecalledoversubscribed


ST_POOL_TYPE

StoragePool

N/A ArrayPoolType

Type ofthe pool


ST_PRIMARY_ALLOCATED2

StorageSystem

BYTES PrimaryAllocated UsableSpace

Capacityofprimarylogicaldeviceson whichhost canperformI/Ooperations minuscapacitydefinedby theprotection level(mirrorsor parityRAID) forthedevices


[4] Extended

ST_SID StorageSystem

N/A StorageDeviceUniqueIdentifier

Uniqueidentifierof thestoragedevice



Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00


Value Type Level1

ST_SIZE StorageSystem

BYTES StorageSize

Overallsize ofthecomponent (for astoragesystem,thisvalue isthe sumof theraw sizeof alldisks; fora storagepool thisvalue istheexternalsize)


[2] Basic

ST_SYSTEM_BANDWIDTH

StorageSystem

BYTE/S SystemBandwidth

Bandwidthavailable instoragesystem


ST_SYSTEM_BANDWIDTH_UTIL

StorageSystem

PCT SystemBandwidthUtilization

Bandwidthconsumed instoragesystem


ST_SYSTEM_MODEL

StorageSystem

N/A StorageArrayModel

Model ofthesystem


ST_SYSTEM_PORT_NUM

StorageSystem

N/A StorageArrayPortNumber

Totalenumberof ports



Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00


Value Type Level1

ST_SYSTEM_SUBSCRIBED_CAPACITY2

StorageSystem

BYTES StorageSubscribedCapacity

Sum ofthe hostvisiblecapacityfor allvolumes.Can begreaterthan theactualcapacityof thestoragesystemwithover-subscribed thinpools


[2] Basic

ST_SYSTEM_TRANSFER_BYTE_RATE

StorageSystem

BYTE/S SystemTransferByte Rate

Totaldatatraffic(in andout, readandwrite)


[3] Standard

ST_SYSTEM_VENDOR

StorageSystem

N/A Vendor Vendor Configuration data [2] Basic

ST_THINDEV_COUNT

StorageSystem

QTY Thindevicescount

Thindevicescount

Positiveaccumulation counter

[2] Basic

ST_THINPOOL_CONFIG_TOTAL

StorageSystem

BYTES ThinPoolTotalcapacity

ThinPoolTotalcapacity


ST_THINPOOL_COUNT

StorageSystem

QTY Thinpoolscount

Thinpoolscount


[2] Basic

ST_THINPOOL_FREE

StorageSystem

BYTES Thinpool freespace

Totalamountof freespace onthe arrayin thinpooldevices


[2] Basic


Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00


Value Type Level1

ST_THINPOOL_USED

StorageSystem

BYTES Thinpoolusedspace

Totalamountof dataon thearrayresidingin thinpooldevices


[2] Basic

ST_VOLUME_CONSUMED_CAPACITY2

StorageVolume

BYTES VolumeConsumedCapacity

Amountofcapacitythat hasbeenactuallyconsumed by thehost (forthinvolumes,thisvaluewilltypicallybe lessthan thehostvisiblecapacity;fortraditionalvolumesthisvaluealwaysequalsthe hostvisiblecapacity)


[2] Basic


Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00


Value Type Level1

ST_VOLUME_CONSUMED_CAPACITY_PCT2

StorageVolume

PCT VolumeConsumedCapacityPercentage

Percentage of thevolumesubscribedcapacitythat hasbeenactuallyconsumed by thehost.Will betypicallyless than100% forthinvolumes.Will beexactly100% foralltraditionalvolumes


ST_VOLUME_HOST_VISIBLE_CAPACITY2

StorageVolume

BYTES HostVolumeVisibleCapacity

Amountofcapacitythat hasbeensubscribed andcan be"seen" bythe host


ST_VOLUME_MAPPED2

StorageVolume

N/A VolumeMapped

Whetherthe LUNismappedto atleast onehost


ST_VOLUME_RAID_LEVEL2

StorageVolume

N/A VolumeRAIDLevel

RAIDlevel ofthevolume



Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00


Value Type Level1

ST_VOLUME_TIME_SINCE_LAST_ACTIVITY2

StorageVolume

N/A VolumeTimeSinceLastActivity

Numberof dayssince thelast reador writeoperation hasbeenobservedon themonitoredvolume.


ST_VOLUME_TRANSFER_BYTE_RATE2

StorageVolume

BYTE/S VolumeTransferByte Rate

Datatraffic(readandwrite) onthevolume


[3] Standard


2These metrics will be missing if Storage Volumes are disabled.

Additional Columns

ColumnName





SYSNM N/A Storage name The name of the storage system

SYSTYPENM







Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

[63] STOHOST Dataset PerformanceMetricsMetrics are presented in a table, where each column represents a particular variable, and eachrow corresponds to a given member of the STOHOST dataset.


BYHOST_ALLOCATED2

BYTES AllocatedSpace byHost

AllocatedSpace byHost in Bytes


[2] Basic

BYHOST_SIZE2

BYTES By HostPhysical Size

Physicalcapacity byhost


[4] Extended


2These metrics will be missing if Storage Volumes are disabled.

Additional Columns

ColumnName





GOLEVELS N/A Grouping ObjectLevels

Levels for populating a grouping object, colon separated

SUBOBJNM

N/A Host name The name of the host

SYSNM N/A Storage name The name of the storage system

SYSTYPENM






67 STOHOST Dataset Performance Metrics

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

[55] STOSSW Dataset PerformanceMetricsMetrics are presented in a table, where each column represents a particular variable, and eachrow corresponds to a given member of the STOSSW dataset.


BYPORT_ADDRESS

N/A Storageswitch portaddress

Storageswitch portaddress


BYPORT_BANDWIDTH

BIT/S Bandwidthof thestorageswitch port

Bandwidthof thestorageswitch port


BYPORT_BANDWIDTH_UTIL

PCT Bandwidthutilization ofthe storageswitch port

Bandwidthutilization ofthe storageswitch port

Percentage counter [4] Extended

BYPORT_BYTE_RATE

BYTE/S Input/outputtraffic ratefor the port

Input/outputtraffic ratefor the port


[4] Extended

BYPORT_CONTROLLER_NAME

N/A Storageswitch portcontrollername

Storageswitch portcontrollername



Additional Columns

ColumnName





GOLEVELS N/A Grouping ObjectLevels

Levels for populating a grouping object, colon separated

LOCATIONNM

N/A Location Name Physical location of the measured object; if absent, assumedUNKNOWN

PORTNM N/A Storage switchport name

Storage switch port name

68STOSSW Dataset Performance Metrics

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

ColumnName


SYSNM N/A System name The name of the system proposed for identification in BMCCapacity Optimization; if absent, the DS_SYSNM is used

SYSTYPENM






Troubleshooting ConnectivityIssues

70

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization leverages the Hitachi DeviceManager to collect capacity and performance metrics. Because some connectivity issues mayexist and cause Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization to fail, it ishighly recommended to test the connection to the Hitachi Device Manager before contacting theSentry Support Team.

To troubleshoot connectivity issues:

1. Download the connection tool required from the Sentry Software Website (Downloadssection of your product). Please note that the connection tool requires Java v1.6 or higher.

2. Run the command java -jar Hitachi_ConnectionTool_V1.0.00.jar to launch the connectiontool.

3. Enter the information required to connect to the system and click Test Connection.

4. Wait for the test to complete. If a connectivity issue is detected, an error message willappear. In this case, the issue encountered does not concern Hitachi Device Manager ETL forBMC TrueSight Capacity Optimization. Check your configuration to diagnose the source of theissue.

5. Click Save As to export the connection test results into a txt file. You can then send thisinformation to the Sentry Support Team.

http://www.sentrysoftware.com/Products/index.asp

71

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Index

- A -Add ETL 36

Additional components 33

Architecture 7

- B -BCO Console 33

- C -Collection Level

Customize 41

Extended 41Columns

CONTNM 54

DS_SYSNM 54, 56, 66, 67

DURATION 54, 56, 66, 67

GOLEVELS 66, 67

Grouping Object Levels 66, 67

Host name 66

Location Name 67

LOCATIONNM 67

Object type 54, 56, 66, 67

PORTNM 67

Storage controller name 54

Storage name 56, 66

Storage switch port name 67

SUBOBJNM 66

SYSNM 54, 56, 66, 67

System name 54, 67

System name in the Datasource 54, 56, 66,67

SYSTYPENM 54, 56, 66, 67

Timestamp 54, 56, 66, 67

TS 54, 56, 66, 67Configuration 36

Configure

Hitachi Device Manager 20

Log Level 47Connection settings 36

Connectivity

Issues 70Customize

Collection Level 41

- D -Dataset

STOCONT 54

STOGLB 56

STOHOST 66

STOSSW 67Device Manager Agent

Install 13Domain Suffix 38

- E -Enabling Statistics 28

ETL tasks 36

Execute 44Extended

Collection Level 41

- H -Hitachi Command Suite

Install 10Hitachi Device Manager

Configure 20

Install 10

Pre-requisites 10Hitachi Storage Navigator Modular 28

HSNM 28

- I -Install

Device Manager Agent 13

Hitachi Command Suite 10

Hitachi Device Manager 10Installation 33

Issues

Connectivity 70

Troubleshooting 70

72

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

- L -License Agreement 33

Log

Files 50

Grabber 50

Show 48Log Grabber

Run 50Log Level

Configure 47

Verbose 47Lookup sharing 36

- M -Metrics

Missing 41Missing

Metrics 41

- O -Object relationships 36

Overview 7

- P -Performance Metrics

Allocated Space by Host 66

Array Pool Type 56

Attached Hosts Number 56

Available Capacity 56

Available Capacity for Storage Pools 56

Available Capacity in Storage Pools 56

Available Capacity Percentage 56

Bandwidth of the storage switch port 67

Bandwidth utilization of the storage switchport 67

By Host Physical Size 66

BYCONT_PORT_NUM 54

BYCONT_TRANSFER_RATE 54

BYHOST_ALLOCATED 66

BYHOST_SIZE 66

BYPORT_ADDRESS 67

BYPORT_BANDWIDTH 67

BYPORT_BANDWIDTH_UTIL 67

BYPORT_BYTE_RATE 67

BYPORT_CONTROLLER_NAME 67

Device Space 56

Host Volume Visible Capacity 56

Input/output traffic rate for the port 67

Microcode version 56

Number of available ports by Controller 54

Pool devices count 56

Pool Oversubscription Situation 56

Pool Subscribed Capacity 56

Pool Subscribed Capacity Percentage 56

Primary Allocated Usable Space 56

ST_AVAILABLE_CAPACITY 56

ST_AVAILABLE_CAPACITY_PCT 56

ST_AVAILABLE_FOR_STORAGE_POOLS 56

ST_AVAILABLE_IN_STORAGE_POOLS 56

ST_CAPACITY 56

ST_CONFIG_SIZE 56

ST_CONSUMED_CAPACITY 56

ST_CONSUMED_CAPACITY_PCT 56

ST_DEVICE_TOTAL 56

ST_DEVICECOUNT 56

ST_DISK 56

ST_HOSTCNT 56

ST_MICROCODE 56

ST_OVERSUBSCRIBED_CAPACITY 56

ST_POOL_DEV_COUNT 56

ST_POOL_OVERSUBSCRIPTION_SITUATION 56

ST_POOL_SUBSCRIBED_CAPACITY 56

ST_POOL_SUBSCRIBED_CAPACITY_PCT 56

ST_POOL_TYPE 56

ST_PRIMARY_ALLOCATED 56

ST_SID 56

ST_SIZE 56

ST_SYSTEM_BANDWIDTH 56

ST_SYSTEM_BANDWIDTH_UTIL 56

ST_SYSTEM_MODEL 56

ST_SYSTEM_PORT_NUM 56

ST_SYSTEM_SUBSCRIBED_CAPACITY 56

ST_SYSTEM_TRANSFER_BYTE_RATE 56

ST_SYSTEM_VENDOR 56

ST_THINDEV_COUNT 56

ST_THINPOOL_CONFIG_TOTAL 56

ST_THINPOOL_COUNT 56

ST_THINPOOL_FREE 56

ST_THINPOOL_USED 56

ST_VOLUME_CONSUMED_CAPACITY 56

73

Hit

achi

Dev

ice

Man

age

r E

TL f

or

BM

C Tr

ueSi

ght

Cap

acit

y O

ptim

izat

ion

Ver

sion

7.1

.00

Performance Metrics

ST_VOLUME_CONSUMED_CAPACITY_PCT 56

ST_VOLUME_HOST_VISIBLE_CAPACITY 56

ST_VOLUME_MAPPED 56

ST_VOLUME_RAID_LEVEL 56

ST_VOLUME_TIME_SINCE_LAST_ACTIVITY 56

ST_VOLUME_TRANSFER_BYTE_RATE 56

Storage Array Model 56

Storage Array Port Number 56

Storage Capacity 56

Storage Configured Space 56

Storage Consumed Capacity 56

Storage Consumed Capacity Percentage 56

Storage Device Unique Identifier 56

Storage Devices Number 56

Storage Oversubscribed Capacity 56

Storage Size 56

Storage Subscribed Capacity 56

Storage switch port address 67

Storage switch port controller name 67

System Bandwidth 56

System Bandwidth Utilization 56

System Transfer Byte Rate 56

Thin devices count 56

Thin pool free space 56

Thin Pool Total capacity 56

Thin pool used space 56

Thin pools count 56

Total Number of used Disks 56

Transfer rate by Controller 54

Vendor 56

Volume Consumed Capacity 56

Volume Consumed Capacity Percentage 56

Volume Mapped 56

Volume RAID Level 56

Volume Time Since Last Activity 56

Volume Transfer Byte Rate 56Platforms

Hitachi Adaptable Modular Storage 2000family 9

Hitachi Universal Storage Platform (USP,USP-V/USP-VM) 9

Hitachi Virtual Storage Platform (VSP) 9

USP 9

VSP 9Pre-requisites 10

- R -Reference Guide 54

Run configuration 36

- S -Show

Log 48Statistics 28

STOCONT Dataset 54

STOGLB Dataset 56

STOHOST Dataset 66

STOSSW Dataset 67

Supported

Platforms 9

Versions 9System Name 38

- T -Task properties 36

Troubleshooting

Connectivity Issues 70

- U -Upload 33

- V -Versions

BMC Capacity Optimization 9

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, providescomprehensive multi-platform monitoring solutions that enable management of thehardware and software aspects of all servers and SANs and covering up to 100 % ofcustom applications within the BMC ProactiveNet Performance Managementenvironment. Sentry Software also develops adapters for BMC Atrium Orchestrator thatenables IT administrators to automate the execution of common requests and tasks thatoccur in the daily course of IT operations. Combined with BMC’s servers and networkautomation tools, the adapters allow IT administrators to implement provisioning anddecommissioning workflows that cover all layers of their IT infrastructure. Finally, SentrySoftware designs connectors that bring storage capacity metrics into BMC TrueSightCapacity Optimization to ensure IT administrators that their storage infrastructure isproperly sized for their current and future needs.

Like us on Facebook:facebook.com/sentrysoftware

Follow us on Twitter:

twitter.com/sentrysoftware

LEARN MORE

To learn more about our solutions, please visit :www.sentrysoftware.com/solutions

© BMC Software, Inc. All rights reserved.

ABOUT MARKETZONE DIRECT PRODUCTS

The BMC MarketZone Directprogram sells and supportsthird-party products thatcomplement and/or augment BMCsolutions. MarketZone Directproducts are available under BMClicense and support terms.

About BMC Software™BMC Software helps leading companies around the world put technology at the forefrontof business transformation, improving the delivery and consumption of digital services.From mainframe to cloud to mobile, BMC delivers innovative IT management solutionsthat have enabled more than 20,000 customers to leverage complex technology intoextraordinary business performance—increasing their agility and exceeding anythingthey previously thought possible. For more information about BMC Software, visit

www.bmc.com.

Bus ines s thrives when IT runs s marter,fas ter and s tronger. That’s why the mos tdemanding IT organizations in the worldrely on BMC Software acros s dis tributed,mainframe, virtual and cloudenvironments . Recognized as the leader inBus ines s Service Management, BMC offersa comprehens ive approach and unifiedplatform that helps IT organizations cutcos t , reduce ris k and drive bus ines sprofit . For the four fis cal quarters endedSeptember 30,2011, BMC revenue wasapproximately $2.2 billion.

BUSINESS RUNS ON I.T .

I.T . RUNS ON BMC SOFT WARE

http://facebook.com/sentrysoftware

http://twitter.com/sentrysoftware

http://twitter.com/sentrysoftware

http://facebook.com/sentrysoftware

hitachi device manager etl v7.1.00 for bmc truesight ... device manager etl for bmc truesight...

Documents