TrueSight Operations Management - Hitachi Storage v1.4 · 7 TrueSight Operations Management - Hitachi Storage Version 1.4.05 What's New Support for Hitachi VSP Gxxxx Series. Changes

TrueSight Operations Management- Hitachi Storage

STORAGE MONITORING

USER DOCUMENTATION

Version 1.4.05

August 2016

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

http://www.sentrysoftware.com

Contacting BMC SoftwareYou 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 2015 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 applicable EndUser License Agreement for the product and the proprietary and restricted rights notices included inthis 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 forth inFAR 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

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Customer SupportYou 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

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

http://www.bmc.com/support_home


http://www.sentrysoftware.com


4

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Table of Contents.....................................................................................................................................................................................9User Goals and Features

.....................................................................................................................................................................................9Product at a Glance

.....................................................................................................................................................................................10Supported Platforms

.....................................................................................................................................................................................11Prerequisites

.......................................................................................................................................................................................12Monitoring Hitachi AMS, HUS, USP, and VSP Systems

......................................................................................................................................................................12Installing Hitachi Device Manager

..........................................................................................................................................................................12Installing the Hitachi Command Suite

..........................................................................................................................................................................15Installing the Device Manager Agent

..........................................................................................................................................................................22Configuring the Hitachi Device Manager

......................................................................................................................................................................30Enabling Statistics

.......................................................................................................................................................................................32Monitoring Hitachi VSP Series Systems

......................................................................................................................................................................32Starting the Embedded SMI-S Provider

......................................................................................................................................................................32Creating a User with "storage administrator View-only" Role

......................................................................................................................................................................32Enabling Statistics

.....................................................................................................................................................................................35Importing the Monitoring Solution into Central Administration

.....................................................................................................................................................................................36Creating the Installation Package

.....................................................................................................................................................................................37Downloading the Installation Package

.....................................................................................................................................................................................37Installing the Package

.....................................................................................................................................................................................41Enabling the Debug Mode

.....................................................................................................................................................................................43Configuring the Discovery Interval

.....................................................................................................................................................................................44Configuring the Polling Interval

.....................................................................................................................................................................................46Setting Discovery and Collect Timeouts

.....................................................................................................................................................................................47Filtering Volumes to Monitor

.....................................................................................................................................................................................49Setting Advanced Configuration Variables

.....................................................................................................................................................................................52Configuring Alert Actions

.....................................................................................................................................................................................53Scheduling Automatic Reports

.....................................................................................................................................................................................56Configuring Monitor Thresholds

.....................................................................................................................................................................................57Editing a Threshold Configuration

.....................................................................................................................................................................................58Deleting a Threshold Configuration

.....................................................................................................................................................................................62Creating Consolidated Data Views with Dashboards

.......................................................................................................................................................................................63Detecting Unbalanced Workload Distribution on Controllers

.......................................................................................................................................................................................66Identifying Busiest Volumes

5

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

.......................................................................................................................................................................................69Reporting Disk Space Consumption

.....................................................................................................................................................................................73Hitachi Disk Array

.....................................................................................................................................................................................75Hitachi Controller

.....................................................................................................................................................................................76Hitachi Fiber Port

.....................................................................................................................................................................................77Hitachi Device Manager

.....................................................................................................................................................................................78Hitachi Managed Array

.....................................................................................................................................................................................79Hitachi Storage Pool

.....................................................................................................................................................................................80Hitachi Volume

.....................................................................................................................................................................................81Managing Baselines and Key Performance Indicators

Release Notes for v1.4.05

7

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

What's New

Support for Hitachi VSP Gxxxx Series.

Changes and Improvements

Host information is now available for mapped volumes.

The password algorithm encryption is now handled by the PATROL Agent.

Fixed Issues

The Read Operation Percentage and Write Operation Percentage attributes of the HitachiVolume monitor type were not collected properly.

The Read Cache Hit Ratio and Write Cache Hit Ratio attributes of the Hitachi Controllermonitor type were not computed correctly.

Known Issues

The Consumed Capacity returned for Hitachi VSP Gxxxx Series volumes is not accurate due to abug identified on the Hitachi API.

Collect issues may occur if Hitachi VSP Gxxxx Series Storage Systems have been previouslyattached to a different SMI-S provider for other purposes such as provisioning. To solve thiscollect issue, you will have to upgrade your version of Hitachi Device Manager to version 8.2.0.-03.

Overview

9

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

The pages in this section provide a high-level overview of the product.

User Goals and Features

Product at a Glance

Supported Platforms

Note that for convenience and brevity, reference to TrueSight Operations Management - HitachiStorage, may also be made as Hitachi Storage Monitoring.

User Goals and FeaturesTrueSight Operations Management - Hitachi Storage product allows you to view, monitor, andmanage your entire Hitachi storage environment by viewing the current and historical informationthrough a centralized console. You can view detailed system metrics on all parts of yourenvironment.

TrueSight Operations Management - Hitachi Storage enables you to manage the following in yourenvironment:

Disk arrays: size, consumed and subscribed capacity, I/Os throughput...

Storage pools: Thin provisioning metrics, size and type...

Controllers: Hit ratio, data traffic...

Storage Volumes: data traffic, hit ratio, time utilization, response time...

Ports: Data traffic statistics, bandwidth utilization, I/Os throughput...

Product at a GlanceTrueSight Operations Management - Hitachi Storage provides current and historical informationthrough a centralized console so you can easily view and manage your entire Hitachi environment.The product collects and brings critical performance data and useful metrics into the BMC TrueSightOperations Management environment and enables SAN Administrators to be warned whenever aproblem occurs in their Hitachi environment.

10Product at a Glance

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Hitachi Storage Monitoring - Architecture Diagram

TrueSight Operations Management - Hitachi Storage:

collects storage performance and metrics to keep total control of your SAN environment

identifies performance bottlenecks (arrays, volumes, storage pools, etc.)

manages and helps rationalize disk space consumption

detects oversubscription situations (thin provisioning).

Supported PlatformsTrueSight Operations Management - Hitachi Storage supports the following storage devices:

Hitachi Adaptable Modular Storage 2000 family (AMS)

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

Hitachi Unified Storage (HUS)

Hitachi Virtual Storage Platform (VSP), including Gxxxx Series.

11 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

PrerequisitesIntegrated as a native module for BMC TrueSight Operations Management, TrueSight OperationsManagement - Hitachi Storage is designed to monitor the health and performance of your managedenvironment. Prior to install the KM, make sure that the following prerequisites are met.

BMC Framework

PATROL Agent, version 3.9 or higher (see BMC PATROL documentation)

PATROL Console (see BMC PATROL documentation)

Java 1.6 or higher (installed on the system where the PATROL Agent runs)

Hitachi AMS, HUS, USP, VSP Systems

Hitachi Device Manager must be properly installed and the statistics enabled. Refer to MonitoringHitachi AMS, HUS, USP, and VSP Systems for more details.

Hitachi VSP Gxxxx Series Systems

The embedded SMI-S provider must be started

A User with "storage administrator View-only" role must be created

Statistics must be enabled.

Refer to Monitoring Hitachi VSP Series Systems for more details.

12Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Monitoring Hitachi AMS, HUS, USP, and VSP

SystemsBefore installing TrueSight Operations Management - Hitachi Storage, you must ensure that HitachiDevice Manager is properly installed and statistics are enabled.

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

The server’s definitive name has been set. The installation of this software sets configurationvariables 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

13 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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

3. Click Next.

14Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

4. Choose the installation folder and click Next.

5. Click Install.

15 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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

16Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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

3. Click Next.

17 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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:

18Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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.

19 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

8. Click Install.

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

20Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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

11. Click OK.

21 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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) and clickNext.

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

22Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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 Systems tabs:

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:

23 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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

24Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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.

25 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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:

26Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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:

27 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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

28Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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 device LUN)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.

29 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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 above willbe 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=

30Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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 server variable: 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 TrueSight OperationsManagement - Hitachi Storage 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

31 Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

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 Measurement ItemsProperty.

Enabling Statistics - Changing measurement items

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

32Prerequisites

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Monitoring Hitachi VSP Series SystemsSince TrueSight Operations Management - Hitachi Storage leverages the embedded SMI-S providerto collect metrics about Hitachi VSP Series systems, there is no need to install a separate SMI-Sprovider. The only steps to follow are:

Starting the Embedded SMI-S provider

Creating a User with "storage administrator View-only" Role

Enabling Statistics

Starting the Embedded SMI-S ProviderTo start the embedded SMI-S Provider:

1. Click Start > All Programs > Hitachi Device Manager - Storage Navigator > StorageDeviceList

2. Click Start Service

3. Run the netstat -ano|findstr 5989 command to verify that a process is actually listening onport 5989.

Creating a User with "storage administrator View-only"

RoleTo create a user with the “storage administrator View-only” role:

1. Log on to the Hitachi Device Manager - Storage Navigator console

2. In the left pane, click Administration > Storage Administrator (View Only) User Group

3. In the right pane, select the Users tab and click Create User

4. Enter the required information and click Finish.

Enabling StatisticsStatistics need to be enabled to allow Hitachi Storage Monitoring to collect performance metrics.The procedure is as follows:

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

2. In the left pane, click Analytics > Performance Monitor

3. Click Edit Monitoring Switch

4. In the Edit Monitoring Switch window, select Enable and click Finish.

Installing the Monitoring Solution

34

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Once the latest version of the solution has been loaded into Central Monitoring Administration,administrators can create all the installation packages required for their different operating systemsand platforms and save them for later use in the Monitoring Installation Packages list. Thesepackages can then be deployed to multiple computers. Administrators just have to connect toTrueSight Operations Management from the server where they want to install the package,download it and launch the installation.

This section describes the different steps to follow to install Hitachi Storage Monitoring:

Importing Hitachi Storage Monitoring into Central Monitoring Administration

Creating the Installation Package

Downloading the Installation Package

Installing the Package

35

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Importing the Monitoring Solution intoCentral AdministrationThe TrueSight Central Monitoring Repository includes the current versions of TrueSight OperationsManagement - Hitachi Storage that you can use with BMC TrueSight. If the version available in theRepository does not correspond to the latest one, you will have to manually import it:

1. Log on to the BMC TrueSight Operations Management Console.

2. Launch Central Monitoring Administration.

3. Click the Repository drawer and select Manage Repository.

4. Check that the version of the BMC component available is actually the latest one. If not,download the latest version corresponding to your operating system (Windows or UNIX/Linux)available on the Sentry Software Website.

5. From TrueSight Operations Management, click Import .

6. Select Single solution.

7. Browse to the .zip source file.

8. Click Import.

The selected archive file is imported to the repository.

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

36Importing the Monitoring Solution into CentralAdministration

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Creating the Installation PackageThe installation package to deploy to managed systems can be created directly from TrueSightOperations Management:

1. Log on to TrueSight Operations Management

2. Click the Repository drawer and select Deployable Package Repository.

3. Click Add .

4. Select the operating system and platform for which you want to create a package. Thecomponents available in the repository for the selected operating system and platform aredisplayed.

5. Select the Installation Package Component:

From the Available components list, select the relevant component.

From the Version list, select the latest version.

Click the right arrow button to move the component into the Selected Components list.By default, the appropriate BMC PATROL Agent for the operating system and platform thatyou chose is included in the Selected components list.

Click Next. The Add Component Installation Package wizard are displayed.

6. Go through the wizard and specify the required PATROL information. The Installation PackageDetails is displayed.

7. Verify that:

the operating system and platform are correct

the components that you want to include are listed in the Included Components list.

8. Provide the following information:

Name: Enter a unique name for the package.

(Optional) Description: Enter a description of the package. The description is displayed in theMonitoring Installation Packages list on the Monitoring Repository window.

Format: Select a file compression format for the package.

9. Click Save Installation Package.

10. Click Close. The package is now available in the Monitoring Installation Packages list.

37 Creating the Installation Package

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Downloading the Installation PackageYou can download an installation package and install the components on one or more hosts. Theinstallation runs silently with the information entered during package creation.

RecommendationIf you defined the BMC TrueSight Integration Service variable for PATROL Agents in theinstallation package, ensure the agents are started in phases. Do not start newly deployedagents all at once. Start and configure monitoring for the agents in planned phases to reducethe performance impact on the Integration Service nodes and on the BMC TrueSight Serverassociated with the automatic workflow process.

1. Log on to TrueSight Operations Management from the computer on which the PATROL Agentis installed or to be installed.

2. Click the Repository drawer and select Deployable Package Repository.

3. (Optional) To filter the list of installation packages, select an operating system from the Filterby Operating System list.

4. Click the link for the installation package that you want to download.

5. Through the browser's download dialog box, save the installation package.

Installing the PackageThis chapter provides a step by step procedure to install a monitoring solution package:

1. From the computer on which you want to install the package, log on to TrueSight OperationsManagement.

2. (Optional) To filter the list of installation packages, select an operating system from the Filterby Operating System list.

3. Click the link for the installation package that you want to download.

4. Through the browser's download dialog box, save the installation package in a temporary file.

5. Extract the installation package that is appropriate for your operating system. The package isextracted to the bmc_products directory on the current host.

6. From the bmc_products directory, run the installation utility for your operating system:

(UNIX or Linux) RunSilentInstall.sh

(Microsoft Windows) RunSilentInstall.exe

The package is installed on the current host. If the package includes a BMC PATROL Agent, theagent sends a configuration request by passing its tags to Central Monitoring Administration, via theIntegration Service. Central Monitoring Administration evaluates policies that match the tags,determines the final configuration to be applied, and sends the configuration information back tothe agent. Monitoring is based on the configuration information received by the agent.

Configuring Monitor Settings

39

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

When you create or edit a policy, you can add and configure monitor types. The Add Monitor Typesdialog box presents configuration fields for compatible BMC PATROL monitoring solutions that arelocated in the Central Monitoring Repository. For a list of monitoring solutions that you canconfigure through Central Monitoring Administration, see the Monitoring solutions conf igurablethrough Central Monitoring Administration chapter in the BMC TrueSight online documentation.

For configuration details for a specific monitor type, see the monitor documentation. To configurecustom monitoring solutions through Central Monitoring Administration, ensure the solution isstructured correctly; for details, see the Building a PATROL Knowledge Module Developers Guide onBMC Support website.

To configure the Monitor Type settings using the Add Monitor Types

dialog box1. Log on to Central Monitoring Administration.

2. Create a Monitoring Policy:

In the Navigation pane, click the Policies drawer

Expand the Monitoring folder and select a policy view (e.g. All).

Click . The Monitoring Policy Configuration wizard is displayed.

Click Next

Define the general policy details and select the agent. For more information, refer to theBMC TrueSight Operations Management Documentation.

Click Next to configure the monitor type.

3. Add a Monitor Type:

Click Add

From the Monitoring Solution menu, select Hitachi Disk Arrays KM.

From the Version menu, select the required version.

40

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

4. Configure the Connection Settings for the Hitachi Device Manager or SMI-S provider (forHitachi VSP Gxxxx Series Systems) you wish to monitor:

Hitachi Storage Configuration - Global Settings

Hostname: Hostname of the embedded SMI-S provider if you wish to monitor a Hitachi VSPGxxxx Series storage system; the hostname of the system where the Hitachi Device Manageris running for any other Hitachi storage system supported by Hitachi Storage Monitoring

Port Number: By default, the Hitachi Device Manager runs on port 5989 when the encryptionoption is enabled, or on port 5988 when the encryption is disabled.

Encryption: Select this option to encrypt the connection.

Refresh Hitachi Information: Indicate how often the Hitachi Information will be refreshed(Never, Every Hour, or Once A Day). This automatic refresh is required to make sure thatconfiguration changes are taken into account by Hitachi Device Manager. Note thatrefreshing the Hitachi Device Manager is resource intensive and time consuming.

5. Enter the WBEM Credentials that will be used to connect to the Hitachi Device Manager.

6. Click Add to List to save the new connection to the Hitachi Device Manager.

41 Enabling the Debug Mode

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Enabling the Debug ModeWhen you encounter an issue and wish to report it to Sentry Software, you will be asked to enablethe Debug Mode and provide the debug output to the Sentry Software support team.

To enable the debug mode1. Edit the policy that applies to the PATROL Agent for which you need to enable the debug mode.

2. Click the Monitor Configuration link.

3. Select the Monitor Type to edit and click .

4. Click the Advanced button.

Enabling the Debug Mode

42Enabling the Debug Mode

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

5. Check the Enable Debug Mode option. The solution will store debug information in a log file. Bydefault debug files are stored in the %PATROL_HOME%\log folder

6. In the Debug End Time field, enter the date and time at which the system must stop loggingdebug information. Required format: yyyy/mm/dd hh:mm:ss.

7. Click Close to save your settings.

For the debug mode to be enabled, the Enable Debug Mode must be checked and the Debug End Timemust be properly set to a date and time in the future.

43 Configuring the Discovery Interval

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Configuring the Discovery IntervalTrueSight Operations Management - Hitachi Storage periodically performs discoveries to detectnew components in your monitored environment. By default, the solution runs a discovery everyhour, but you can customize this interval to match your specific needs.

To configure the discovery interval1. Edit the policy that applies to the PATROL Agent for which you need to configure the discovery

interval.



4. In the List - Hitachi Device Manager section, select the Hitachi device for which you need toconfigure the discovery interval.

Configuring the Discovery Interval

5. Enter the frequency of the discovery process. Use the spin button to enter the appropriatenumber of minutes.


44Configuring the Polling Interval

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Configuring the Polling IntervalA polling interval defines how often new data is collected. A new collect can be performed fromonce every second, to once in a day. TrueSight Operations Management - Hitachi Storage polls themanaged systems to collect performance and statistics data. By default, the polling interval for this"data-collect" is set to every 2 minutes.

The more the polling interval is low, the more the collection process is time consuming.

To configure the discovery interval1. Edit the policy that applies to the PATROL Agent for which you need to configure the discovery

interval.



4. In the List - Hitachi Device Manager section, select the Hitachi device for which you need toconfigure the polling interval.

Configuring the Pooling Interval

45 Configuring the Polling Interval

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

5. Enter the frequency of the polling process in the Polling Interval (in Minutes) field. Use the spinbutton to enter the appropriate number of minutes. By default, the polling interval is set to 2minutes.

6. Click Modify Selection.

7. Click Update to save your settings.

46Configuring the Polling Interval

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Setting Discovery and CollectTimeoutsIn order to optimize the monitoring on large environment, it is possible to customize the discoveryand the collect timeouts from the Central Monitoring Administration Console.

To set the discovery and the collect timeouts1. Edit the policy that applies to the PATROL Agent for which you need to configure the discovery

interval.



4. In the List - Hitachi Device Manager section, select the Hitachi device for which you need toset the discovery and/or the collect timeout.

Setting the Discovery and the Collect Timeout

47 Setting Discovery and Collect Timeouts

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

5. In the Discovery Timeout field, specify the number of minutes after which the discovery shouldbe stopped. By default the discovery timeout is set to 6000 minutes. When the timeout isreached, the Collection Status attribute of the Hitachi Device Manager monitor type is set to 2(Failed) and triggers an alert.

6. In the Collect Timeout field, specify the number of minutes after which the collect should bestopped. By default the collect timeout is set to 6000 minutes. When the timeout is reached,the Collection Status attribute of the related instance of the Hitachi Disk Array monitor type isset to 2 (Failed) and triggers an alert.

7. Click Modify Selection.


Filtering Volumes to MonitorBy default, the solution discovers and monitors all volumes in the storage systems. There may be avery large number of volumes to monitor and this may represent an important workload to theagents and the servers. Also, the monitoring of some of these volumes may be irrelevant forvarious reasons.

You can filter the volumes that will be monitored by the solution. You can either exclude volumesfrom the monitoring or keep only certain volumes.

48Filtering Volumes to Monitor

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

To filter volumes to monitor1. Edit the policy that applies to the PATROL Agent monitoring the LUNs or volumes you need to

exclude or keep in the monitoring process.



4. In the List - Hitachi Device Manager section, select the Hitachi device for which you need todisable the monitoring of volumes.

Selecting Volumes to monitor

5. Check the Disable Volumes Monitoring box if you want to limit the number of Volumeinstances created and therefore reduce the system resource consumption. Discovery andcollect requests and operations will no longer be performed.

6. In the Exclude Volumes field, enter the names of the volumes to be excluded from monitoring.A regular expression can also be used.

7. In the Keep Only Volumes field, enter the names of the volumes to be monitored. A regularexpression can also be used.


49 Setting Advanced Configuration Variables

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Setting Advanced ConfigurationVariablesAdvanced configuration variables are used to manually set variables that are normally not availablethrough the standard interface.

These variables should only be set when instructed so by Sentry Software Support.

50Setting Advanced Configuration Variables

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

To configure a variable1. Edit the policy that applies to the PATROL Agent for which you need to configure variables.

2. Click the Monitor Configuration tab.

3. Click the Advanced button.

Configuring variables

4. In the Configuration Variables section, enter the configuration variables you need to configure

and enter the value to be set. Please note that the Name field is case sensitive:

51 Setting Advanced Configuration Variables

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Variables DefaultValue

Description

collectionHubHeapSizeMax

None Maximum heap size in megabytes allocated to the Java Collection Hub.

collectionHubHeapSizeMin

None Minimum heap size in megabytes allocated to Java Collection Hub.

collectionHubOverrideJavaCommandLine

None Command line used by the monitoring solution to launch the JavaCollection Hub. This variable should only be set if instructed by SentrySupport.

defaultReinitializationOptions

None List of default options to be executed by TrueSight OperationsManagement - Hitachi Storage on reinitialization.

resetThresholds

resetThresholdManagementMode

resetAlertActions

resetOtherAlertSettings

resetDebugMode

resetRemovedPausedObjectList

resetReport

resetSecuritySettings

resetJavaSettings

Insert a colon “;” between the variable and its value: “resetThresholds;1”;and if you enter multiple variables, they need to be separated by a carriagereturn.Example: “resetThresholds;1” will display the remove thresholds optionselected by default in the Reinitialize KM wizard.

disableJRECheck 0 = JREvalidationtestsenabled

When set to 1, disable the validation tests of the JRE used by themonitoring solution to run Java code. This can be used to force the KM touse a non-Sun or non-Oracle JRE.

disablePslExecuteBugWorkaround

0 =activated

When set to ‘1’, deactivates the workaround in the monitoring solution fora bug in the PslExecute() PSL function. If the product detects that the version of the PATROL Agent is affected bythe PslExecute() bug, it uses an alternate technique to create asynchronousthreads with the event_trigger() function and the RemPsl standard event.The disablePslExecuteBugWorkaround variable disables this workaround.

forceClassicConfigMode

0 =disabled

When the product is used with TrueSight OM, all the KM configurationmenus are disabled in the PATROL Consoles. To enable them, set theforceClassicConfigMode variable to 1.

javaPassword None Password associated to the javaUsername variable.

javaPath None Path to the folder containing the Java executable used by the CollectionHub.Path to the folder containing the Java executable used by theCollection Hub.

52Setting Advanced Configuration Variables

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Variables DefaultValue

Description

javaUsername None Username used to launch the Java Collection Hub.

pausedObjectList n/a List of the PATROL object path of the paused objects. (i.e. for which nocollection will be performed).

psCommand n/a Command used on UNIX/Linux systems to retrieve the list of the currentlyrunning processes.Note: This command is used for debug purpose.

refresh None To specify the refresh behavior to be adopted by TrueSight OperationsManagement - Hitachi Storage .

removedObjectList

None List of instances that have been removed from the monitoring environmentthrough the Remove KM Command.

startupDelay 0 second To specify the number of seconds that TrueSight Operations Management -Hitachi Storage will wait before starting its discovery. This variable may beuseful on fast booting computers where the SMI-S Provider starts after themonitoring solution and triggers an alert.

5. Click Add to List.


You can easily modify or remove a variable by selecting it in the list and clicking either the ModifySelection or the Remove from List buttons.

Configuring Alert ActionsHitachi Storage Monitoring allows you to configure specific alert actions to be executed when aproblem occurs:

1. Log on to Central Monitoring Administration.

2. Edit the Monitoring Policy that applies to the PATROL Agent for which to need to configurevariables.

3. In the Global Alert Settings section, click Alert Actions.

Configuring Alert Actions

4. Select the type of event you want the solution to perform Upon a Storage Problem:

A STD 41 PATROL Event

A Specific PATROL Event (includes the alert origin — ApplicationClassName.ObjectID.ParameterName).

53 Configuring Alert Actions

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

No Event

These events are generated every time a threshold is exceeded. They contain a full Storage Health Reportdetailing the fault that has occurred.

5. (BPPM 9.5 and higher) Check the Enable Annotations option to make the solution annotate theparameter’s graph with a comprehensive report of the problem.


7. In the Add Monitor Types dialog box, click Add. If the monitor configuration has beensuccessfully added, click Close.

8. Click Finish to save your monitoring policy.

Scheduling Automatic ReportsTrueSight Operations Management - Hitachi Storage can automatically produce text reports aboutthe monitored storage systems.

To schedule automatic reports1. Log on to Central Monitoring Administration.

2. Edit the policy that applies to the PATROL Agent for which you need to configure the schedulingof automatic reports:

In the Navigation pane, click the Policies drawer.


Select your policy and click .

Click the Monitor Configuration link.

Select the Hitachi Storage Monitor Type and click .

3. Click the Schedule button.

Scheduling automatic reports

4. In the Schedule section, the time at which the report(s) must be generated.

5. Check the Activity report type to automatically generate the following reports:

Disk Array Activity: Reports on Read and Write Bytes for all monitored disk arrays

Controller Activity: Reports on Transfer Bytes for all monitored controllers

54Scheduling Automatic Reports

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Fiber Port Activity: Reports on Transfer Bytes for all monitored fiber ports

Storage Pool Activity: Reports on Read and Write Bytes for all monitored storage pools

Volume Activity: Reports on Read and Write Bytes for all monitored volumes

6. Check LUNs Mapping Table to automatically generate a text report of the LUNs-to-hostsmapping table.


The history retention period can be set from the PATROL Console or from the PATROL Agent using aconfiguration variable. The default collection (retention) period is one day. Whenever a stored parametervalue exceeds its retention period, it is automatically deleted from the parameter history f ile. Refer toBMC documentation for details.

Configuring Thresholds

56

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

When you are creating or editing a policy, you can add and configure monitor thresholds. The AddInstance Thresholds dialog box presents threshold configuration fields for TrueSight OperationsManagement monitors that are configured through Central Monitoring Administration.

For details about baselines and Key Performance Indicators (KPI), see TrueSight OperationsManagement or Central Monitoring Administration user documentation or refer to the ManagingBaselines and Key Performance Indicators chapter. For details about the monitored attributes, referto the specific monitor type in the Reference Guide chapter.

Before you begin

Ensure that your monitor configuration is complete before thresholds are applied. Thresholdscannot be applied to monitors that are not configured through Central Monitoring Administration.If you have not done so already, please refer to the Configuring Monitor Settings chapter.

Recommended Thresholds

Thresholds define acceptable high and/or low values for the data collected. Thresholds can becreated as part of a policy that can be applied to multiple monitor types on multiple BMC PATROLAgents.

The Reference Guide chapter provides a list of monitor types with their respective attributes andthe thresholds applied by default.

Do not set server thresholds for availability or Boolean oriented parameters or any other parameters thatwill have events generated for them by the PATROL Agents.

Configuring Monitor ThresholdsTo configure monitor thresholds:


2. Edit the Monitoring Policy that applies to the PATROL Agent for which you need to configurethresholds:




57 Configuring Monitor Thresholds

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

3. Check the Server Threshold Configuration box.

4. Click the Server Threshold Configuration link.

5. In the Server Threshold Configuration page, click .

6. Select the relevant Solution, Version, and Monitor Type.

7. In the Instance Name field, specify the instance to which the threshold configuration will beapplied. You can either use a string or the following regular expression patterns: ?, +, *, ( ), |,[ ], { }, ,̂ $,

8. Check the Match Device Name box if you want the entire <deviceName>\<instanceName>string to be considered.

9. From the Attribute list, select a monitor attribute.

10. In the Threshold section:

Select the threshold type.

Set the threshold parameters values.

Click Add.

11. Resume the procedure to configure all the monitor thresholds required.

12. Click Close. The configuration details are displayed in the Server Threshold Configuration page.

13. Click Finish.

New threshold configurations are pushed to BMC PATROL Agents with matching Central MonitoringConfiguration tags, IP address, hostname, etc.

Editing a Threshold ConfigurationTo edit a threshold configuration:


2. Edit the Monitoring Policy that applies to the PATROL Agent for which you need to editthresholds:





4. On the Server Threshold Configuration page, select an Instance Name and click .

5. Edit the threshold configuration values and click Update.

6. When you finish editing the threshold configuration, click Close.

7. Click Finish.

Updated threshold configurations are pushed to BMC PATROL Agents with matching CentralMonitoring Configuration tags.

58Deleting a Threshold Configuration

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Deleting a Threshold ConfigurationTo delete a threshold configuration:


2. Edit the Monitoring Policy that applies to the PATROL Agent for which you need to editthresholds:





4. On the Server Threshold Configuration page, select an Instance Name and click

5. Click Yes to confirm deletion.

6. After you delete one or more threshold configurations, click Finish to save changes to thepolicy. Deleted threshold configurations are removed from BMC PATROL Agents with matchingCentral Monitoring Configuration tags.

Monitoring your StorageEnvironment

60

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

The <%TSOM%> platform, combined with the powerful monitoring features of Hitachi StorageMonitoring, provides you with a visual representation of the monitored resources in yourenvironment to give you a full picture of your SAN; The solution proactively detects, automaticallypredicts, and resolves IT performance issues and sub-optimal configurations before users andservices are negatively impacted. Integrated as a native module for <%TSOM%>, Hitachi StorageMonitoring monitors the physical aspects your entire Hitachi environment. It reports hardwarefailures and monitors key performance metrics. It helps you diagnose any availability issue in theSAN, and ensures maximum data protection by monitoring a wide range of critical components.

Viewing the Overall Activity of a Device

The <%TSOM%> Monitoring menu gives you access to various options for viewing your monitoredenvironment: Applications, Devices, Events, Groups. This chapter focuses on the Devices page thatdisplays information about the Hitachi devices that TrueSight Operations Management - HitachiStorage monitors and to view the overall health of the system.

Log on to the <%TSOM%> console and select Monitoring > Devices to access basic information foreach monitors associated with a monitored device

Devices Page

The Devices page displays information about the devices that Hitachi Storage Monitoring monitorsand to a view at the overall health of the system.

61

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

To drill down and view a specific device details, click the device name or the events count.

Device name: Displays the Monitors tab in the Device Details page.

Events count: Displays the Events tab in the Device Details page.

Device Details

The Device Details page displays the device name, type, DNS name, IP address, and source name.The event status and severity matrix displays the number of events in each status and severity.

Device Monitors

This page displays all the monitors that are associated with the device.The action menu allows youto change and sort the view. In the tile view, you can show or hide the monitor type and sourcename. In the Table View, you can expand the monitor rows to drill down into the devicecomponents.

Device Events

This page displays all the events that are associated with the device. By default, events of Critical,Major, Minor, Warning, and Information severity and Open, Acknowledged, and Assigned status aredisplayed. To view events of a specific status and severity, click the appropriate event count in theevents matrix.

Refer to the BMC documentation for detailed information about the <%TSOM%>features andoptions.

https://docs.bmc.com/docs/display/TSPS101/Home

62

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Creating Consolidated Data Viewswith Dashboards<%TSOM%> provides dashboards to create consolidated and customized views of your monitoredIT environment. Dashboards are build from dashlet templates. Once you have selected the dashletthat corresponds to the type of view you wish to create, you can access a specific type of data andpresent it graphically.

TrueSight Operations Management - Hitachi Storage monitors availability, capacity, andperformance for Hitachi disk arrays. It makes this data available to you through different dashletsfor you to create a clear view of the performance and status of your storage environment within aprivate or shared dashboard. The product leverages the <%TSOM%> unified features andcapabilities to offer you a deep visibility into over 200 key metrics.

When a dashlet in the dashboard identif ies a problem, it also acts as an access point to investigate andtroubleshoot the root cause.

This chapter explains how to create consolidated views for some of the most critical elements ofyour Hitachi environment. Dashboards report on critical aspects of your Hitachi storage systems,and consolidate and normalize information from a variety of sources. While saving you considerabletime and effort, a unified view can help you rapidly and proactively detect poor storageperformance and hardware failures.

Tip

Once you have created a dashboard, you may want to use its settings to createanother dashboard for a different device. To do so, copy the dashboard from the Dashboards page:

1. Click My Dashboards or Shared Dashboards.2. In the action menu to the left of the dashboard name, select Copy

Dashboard.3. The new dashboard appears in the My Dashboards list as Copy of

<DashboardName>.

The following topics describe how to create dashboards for:

Detecting Unbalanced Workload Distribution on Controllers

Identifying Busiest Volumes

Reporting Disk Space Consumption

Use cases were performed with <%TSOM%> v.10.1.

63 Creating Consolidated Data Views with Dashboards

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Detecting Unbalanced Workload Distribution

on ControllersA storage controller manages the flow of information between the server and the data, assigningtwo paths, in case one of the paths fails or is overloaded. For the best levels of performance andavailability, every layer of technology must be balanced.

64Creating Consolidated Data Views with Dashboards

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

To Detect Unbalanced Workload Distribution Across Controllers1. Login to your <%TSOM%> console.

2. Select Dashboards from the navigation pane.

3. In the Dashboards page, click Add Dashboard or select Add Dashboard from the dashboard

action menu .

4. Enter a Title for your dashboard and configure a Global Filter, if needed.

5. Click Add Dashlet to open the dashlet library for the first column of the row.

6. From the dashlet library, select the Device Performance template, and then click Close.

7. Select Configure Dashlet by clicking the button.

8. In the panel of input fields and options that opens below the dashboard, enter a Title for thedashlet and specify a Refresh Rate (default is 5 minutes).

9. Select the Hitachi storage device for which you to compare processors utilization.

10. Select the Read Cache Hit Ration and the Transfer Byte Rate parameters for the first controller,and click Apply.


Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Tip

To quickly retrieve a component or a parameter, enter its namein the Search Parameters field and click Search.

11. Repeat this operation in the next column of the dashboard for another controller and click Save.

12. The dashboard is completed and shows the Processor Utilization and the Transfer Byte Ratefor both controllers.

For example, if the throughput on one controller is significantly higher than the other one, itindicates that one on the controllers may constitute a bottleneck for the subsystem that could bealleviated by better sharing the load between the controllers.It is recommended to pay close attention to which logical drive is handled by which controller,depending on the activity of this logical drives to be able to reallocates controller to drive I/Oactivity so that neither controller is overloaded.


Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Identifying Busiest VolumesMonitoring volumes to find out if the amount of data processed is dangerously growing close to thevolume's limit will help you not being caught short of space without warning.

To identify the volumes that generate the most traffic, you will need to create a simple two-columndashboard. Dashboards allow you to gather specific types of data and display them in aconsolidated graphical format. For detailed information about dashboards options and features,refer to the BMC documentation.

https://docs.bmc.com/docs/display/TSPS101/Getting+started+with+dashboards


Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

To Identify Busiest Volumes1. Login to your <%TSOM%> console.



action menu .






9. Select the Hitachi storage device for which you want to compare processors utilization.

10. Select the Read Byte Rate and the Write Byte Rate parameters for the first volume, and clickApply.


Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Tip


11. Repeat this operation in the next column of the dashboard for another volume and click Save.

12. The dashboard is completed and shows the Read Byte Rate and the Write Byte Rate for bothvolumes.


Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Reporting Disk Space ConsumptionMaking sure that a storage system has enough remaining disk space available is critical for severalreasons:

SAN administrators want to make sure to be able to provision disk space for new servers whenrequested, as quickly as possible.

The storage system itself may need additional disk space for specific features to work properly,like automatic snapshots, mirroring, etc.

If thin provisioning is used, the remaining disk space becomes dramatically critical since theinability to allocate additional space to a volume when requested by the subscriber host willlead to catastrophic data loss and corruption.

The disk space used is permanently monitored for each storage pool. The Subscribed Capacityparameter of a storage pool represents the amount of disk space that has been made available tothe subscriber hosts, or in other words, the amount of disk space that is seen by the serversconnected to the storage system.

The Consumed Capacity parameter of a storage pool represents the actual space usage in thestorage pool. For “thin” pools (when thin provisioning is enabled on the storage system), this valueis normally lower than the Subscribed Capacity, as it is the main purpose of thin provisioning. Fortraditional pools, the Consumed Capacity has the same value as the Subscribed Capacity, as theentirety of the subscribed disk space is fully allocated in the storage pool.

The Consumed Capacity Percentage parameter is the most critical one, even for non-thin storagepools, as a storage pool usage nearing 100% means that SAN administrators will not be able tocreate new volumes in the storage pool. By default, no alarm or warning threshold is set on thisparameter as the fullness of a storage pool may be a normal situation.

To determine the actual disk space consumption for a storage system, you will need to create asimple three-column dashboard. Dashboards allow you to gather specific types of data and displaythem in a consolidated graphical format. For detailed information about dashboards options andfeatures, refer to the BMC documentation.

https://docs.bmc.com/docs/display/TSPS101/Getting+started+with+dashboards


Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

To Report on Disk Space Consumption1. Login to your <%TSOM%> console.



action menu .






9. Select the Hitachi storage device for which you want to compare processors utilization.

10. Select the Subscribed Capacity parameter for a storage pool, and click Apply.


Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Tip


11. Repeat this operation in the next column of the dashboard for the Consumed Capacityparameter and click Apply.

12. Finally, in the third column of the dashboard, select the Consumed Capacity Percentageparameter and click Save.

13. The dashboard is completed and shows the disk space consumption for the selected storagepools.

Reference Guide

73

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by the TrueSight Operations Management - Hitachi Storage. It contains tables describingthe attributes used in the KM, grouped by Monitor Types, and provides a brief description of eachattribute and its default settings.

Monitor Types

Hitachi Disk Array

Hitachi Controller

Hitachi Fiber Port

Hitachi Device Manager

Hitachi Managed Array

Hitachi Storage Pool

Hitachi Volume

Baselines and Key Performance Indicators

Some attributes are identified by default as Key Performance Indicators (KPIs) and thereforeautomatically included in the base lining calculation. To learn more about auto baselining and KPIs,please refer to the "Managing Baselines and Key Performance Indicators" chapter.

In this guide, attributes flagged as KPIs and included by default in the baseline calculation processare respectively identified by the following icon: KPI

Hitachi Disk ArrayAttributes

Name Description Units Default AlertConditions

BMCProactiveNetAttribute Type

CollectionStatus

Status of the collection. {0= OK; 1 =Degraded;2= Failed}

Warning = 1Alarm = 2

CollectionStatus

AvailableCapacity

Total capacity less consumed capacity (Theconsumed capacity corresponds to theconsumed capacity of unallocated volumeswith DP pool + consumed capacity ofallocated volumes).

Terabytes(TB)

None Statistics

74Hitachi Disk Array

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Operation Rate Amount of operations transmitted persecond.

Operations/s None Statistics

Port Count Number of ports on the disk array. Ports None Statistics

Status Status of the array. {0= OK; 1 =Degraded;2= Failed}:


Availability

SubscribedCapacity

The sum of the host visible capacity of themapped volumes.

Terabytes(TB)

None Statistics

Transfer ByteRate

Count of data transferred per second. Megabytesper second(MB/s)

None Statistics

For detailed information about KPI, see Managing Baselines and Key Performance Indicators.

75 Hitachi Disk Array

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Hitachi ControllerAttributes



Read Cache HitRatio

Percentage of read requests that aresuccessfully served by a cache.

Percentage(%)

None Statistics

Transfer ByteRate


None Statistics

Write Cache HitRatio

Percentage of write requests that aresuccessfully served by a cache.

Percentage(%)

None Statistics


76Hitachi Controller

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Hitachi Fiber PortAttributes



BandwidthUtilization

Amount of bandwidth currently in use bythe FC port.

Percentage(%)

None Statistics

Operation Rate Amount of operations transmitted persecond.

Operations/s None Statistics

Transfer ByteRate


None Statistics


77 Hitachi Fiber Port

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Hitachi Device ManagerAttributes



CollectionStatus

Status of the collection. {0= OK; 1 =Degraded;2= Failed}


CollectionStatus

78Hitachi Device Manager

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Hitachi Managed ArrayAttributes



Refresh Rate SMI-S Provider refresh rate. minutes None Statistics

Statistics Indicates whether the statistics are enabledor not.

{0 =Enabled;1 =Disabled}

Alarm = 1 Statistics

79 Hitachi Managed Array

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Hitachi Storage PoolAttributes

Name Description Unit Default AlertConditions


ConsumedCapacity

Total size of the space actually allocated orreserved.

Terabytes(TB)

None Statistics

ConsumedCapacityPercentage

Percentage of the storage pool that isactually allocated or reserved.

Percentage (%)

Warning ≥80%Alarm ≥ 90%

Statistics

OversubscriptionSituation

This attribute reports an oversubscriptionsituation, that is when:

1.The storage pool is configured for thinprovisioning (“thin storage pool”)

2.the SubscribedCapacityPercentageparameter is greater than 100%, and

3.the ConsumedCapacityPercentageparameter is greater than 75%

Such situation is highly critical because theinability to allocate additional space to avolume when requested by the subscriberhost will lead to catastrophic data loss andcorruption.

{0= No; 1 =Yes}

Alarm = 1 Statistics

SubscribedCapacity

Total host visible capacity. Terabytes(TB)

None Statistics

SubscribedCapacityPercentage

Percentage of the storage pool that issubscribed.

Note: This parameter can exceed 100 % forthin provisioned storage pools.

Percentage (%)

Warning ≥80%Alarm ≥ 90%

Statistics

Transfer ByteRate

Count of data transferred per second. Megabytes persecond(MB/s)

None Statistics

80Hitachi Storage Pool

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Hitachi VolumeAttributes

Name Description Unit Default AlertConditions


ConsumedCapacity

Total size of the space actually allocated orreserved.

Gigabytes(GB)

None Statistics

ConsumedCapacityPercentage

Percentage of the storage pool that isactually allocated or reserved.

Percentage (%)

None Statistics

Host VisibleCapacity

Amount of space on the disk that is assignedto bound LUNs.

Gigabytes(GB)

None Statistics

Read Cache HitRatio

Percentage of read requests that aresuccessfully served by a cache.

Percentage (%)

None Statistics

Read OperationPercentage

Percentage of read operations. Percentage (%)

None Statistics

Read OperationRate

Count of operations read per second. Operation/s

None Statistics

Time Since LastActivity

Number of days since any activity occurredon the volume.

Days None Statistics

Transfer ByteRate

Count of data transferred per second. Megabytes persecond(MB/s)

None Statistics

Write Cache HitRatio

Percentage of write requests that aresuccessfully served by a cache.

Percentage (%)

None Statistics

WriteOperationPercentage

Percentage of write operations. Percentage (%)

None Statistics

WriteOperation Rate

Count of operations written per second. Operation/s

None Statistics

81 Managing Baselines and Key PerformanceIndicators

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Managing Baselines and KeyPerformance IndicatorsTo detect abnormalities on the monitored environment, BMC TrueSight Operations Managementcalculates baselines per attribute based on values collected over a specified period of time todetermine a normal operating range. When the collected values for these parameters are out ofrange, an alert is triggered. Some attributes are identified by default as Key Performance Indicators(identified with the icon) and automatically included in the base lining calculation.

Managing baselines

The baseline is the expected normal operating range for an attribute of a monitor. There are twobaselines: Baseline High and Baseline Low. Baseline High represents the point at which 95% of theweighted average of the historical values fall below this value for the selected time period; BaselineLow represents the point at which 90% of the weighted average of historical values for the selectedtime period fall above this line.

Baselines are generated for KPI attributes that have an active abnormality thresholds.

Managing Key Performance Indicators

Starting from v9.5 of BPPM, attributes that have not been initially designated in the KM as KeyPerformance Indicators (KPIs) cannot be flagged as KPIs from BPPM/TrueSight. Although enablingbaseline is possible through the Options > Administration > Intelligent Event Thresholds featureavailable in the Infrastructure Management Server operator console, BMC does not recommenddoing it.

For more information, refer to the BMC TrueSight Operations Management documentation availablefrom docs.bmc.com.

https://docs.bmc.com/docs/dashboard.action

Troubleshooting ConnectivityIssues

83

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

TrueSight Operations Management - Hitachi Storage leverages the Hitachi Device Manager .Because some connectivity issues may exist and cause TrueSight Operations Management - HitachiStorage to fail, it is highly recommended to test the connection to the Hitachi Device Managerbefore contacting the Sentry Support Team.

To troubleshoot connectivity issues:

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

2. Run the command java -jar troubleShooting-Tools-for-Hitachi-Device-Manager-<version>.jarto launch the connection tool.

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 will appear.In this case, the issue encountered has nothing to do with Hitachi Storage Monitoring. Checkyour configuration to diagnose the source of the issue.

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/support/troubleshooting-tools.asp

84

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Index

- A -Abnormalities 81

Add Monitor Types 39

Advanced Configuration Variables 49

Annotate

Graph 52Attributes 73

Available Capacity 73

Bandwidth Utilization 76

Collection Status 73, 77

Consumed Capacity 69, 79, 80

Consumed Capacity Percentage 69, 79,80

Host Visible Capacity 80

Operation Rate 73, 76

Oversubscription Situation 79

Port Count 73

Read Cache Hit Ratio 75, 80

Read Operation Percentage 80

Read Operation Rate 66, 80

Reresh Rate 78

Statistics 78

Status 73

Subscribed Capacity 69, 73, 79

Subscribed Capacity Percentage 79

Time Since Last Activity 80

Tranfer Byte Rate 73, 76

Transfer Byte Rate 75, 79, 80

Write Cache Hit Ratio 75, 80

Write Operation Percentage 80

Write Operation Rate 66, 80Automatic Reporting 53

- B -Baselines

BMC ProactiveNet Performance Management 81

Generation 81

Manage 81

Requirements 81BMC ProactiveNet Performance Management

Abnormalities 81

Baselines 81

Key Performance Indicators 81

KPI 81Busiest Volumes 66

- C -Changes and Improvements 7

Collect Timeout 46

Component Installation package

creating 36

downloading 37Configuration Variables 49

Configure

Alert Actions 52

Annotations 52

Hitachi Device Manager 22Configuring

discovery interval 43

monitor settings 39

polling interval 44Configuring Monitor Thresholds 56

Configuring thresholds 56

Connectivity

Issues 83Create

graph 63

view 63

- D -Debug Mode

enabling 41Deleting a Threshold Configuration 58

Device Manager Agent

Install 15Discovery Interval

configuring 43Discovery Timeout 46

Disk Space Consumption 69

Downloading 37

- E -Editing a Threshold Configuration 57

Enable

85

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Enable

Statistics 12, 32Enabling Statistics 30

- F -Features 9

Fixed Issues 7

- G -Generate

Baselines 81Goals 9

Graph

Annotate 52

create 63

- H -Hitachi AMS 12

Hitachi Command Suite

Install 12Hitachi Device Manager 11, 12

Configure 22

Install 12

Pre-requisites 12Hitachi HUS 12

Hitachi Storage Navigator Modular 30

Hitachi USP 12

Hitachi VSP 32

HSNM 30

- I -Identify

Busiest Volumes 66Importing the Monitoring Solution 35

Install

Device Manager Agent 15

Hitachi Command Suite 12

Hitachi Device Manager 12Installing 37

Installing the Monitoring Solution 34

Issues

Connectivity 83

Troubleshooting 83

- K -Key Concepts 9

Key Performance Indicators


Manage 81KPI


Manage 81

- M -Manage

Baselines 81

Key Performance Indicators 81

KPI 81Monitor Settings

configuring 39Monitor thresholds 56

Monitor Types 73

Hitachi Controller 75

Hitachi Device Manager 77

Hitachi Disk Array 73

Hitachi Fiber Port 76

Hitachi Managed Array 78

Hitachi Storage Pool 79

Hitachi Volume 80Monitoring

Storage 60

volumes 47Monitors

Hitachi Storage Pool 69

Hitachi Volume 66

- P -Package 36, 37

PATROL

Agent 11

Console 11PATROL Event

Specific 52

Standard 52

STD_41 52Polling Interval

86

Tru

eSig

ht

Op

erat

ion

s M

anag

emen

t -

Hit

ach

i Sto

rage

Ver

sio

n 1

.4.0

5

Polling Interval

configuring 44Prerequisite 11

Prerequisites 12

Pre-requisites 12

- R -Reference Guide 73

Reporting

Disk Space Consumption 69Reports

scheduling 53Role 11, 32

- S -Scheduling

Reports 53Setting

Collect Timeout 46

Discovery Timeout 46SMI-S Provider 11

Embedded 32

Start 32Start

SMI-S Provider 32Statistics 11, 30

Enable 12, 32Storage

Monitoring 60Storage administrator view only 32

- T -Thresholds 56

Transfer byte rate 63

Troubleshooting

Connectivity Issues 83

- U -Use Case 60

Use cases

Unbalanced workload 63User 32

- V -Variables 49

View

create 63Volumes

filtering 47

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, providescomprehensive multi-platform monitoring solutions that enable management of the hardwareand software aspects of all servers and SANs and covering up to 100 % of custom applicationswithin the BMC TrueSight environment. Sentry Software also develops adapters for BMC AtriumOrchestrator that enables IT administrators to automate the execution of common requests andtasks that occur 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 TrueSight CapacityOptimization to ensure IT administrators that their storage infrastructure is properly sized fortheir current and future needs.The combination of its monitoring, automation, and capacity optimization capabilities for IT

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 Direct programsells and supports third-partyproducts that complement and/oraugment BMC solutions. MarketZoneDirect products are available underBMC license and support terms.

About BMC Software™BMC Software helps leading companies around the world put technology at the forefront ofbusiness transformation, improving the delivery and consumption of digital services. Frommainframe to cloud to mobile, BMC delivers innovative IT management solutions that haveenabled more than 20,000 customers to leverage complex technology into extraordinarybusiness performance—increasing their agility and exceeding anything they previously thought

possible. For more information about BMC Software, visit www.bmc.com.

Business thrives when IT runs smarter, fasterand stronger. That’s why the mostdemanding IT organizations in the world relyon BMC Software across distributed,mainframe, virtual and cloud environments.Recognized as the leader in Business ServiceManagement, BMC offers a comprehensiveapproach and unified platform that helps ITorganizations cut cost, reduce risk and drivebusiness profit. For the four fiscal quartersended September 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

Documents

TrueSight Operations Management - Hitachi Storage v1.4 · 7 TrueSight Operations Management - Hitachi Storage Version 1.4.05 What's New Support for Hitachi VSP Gxxxx Series. Changes