ibm ds6000, ds8000 series km for patrol 1.2 · ibm ds6000, ds8000 series km for patrol version...

User Documentation December 2012

IBM DS6000, DS8000 SeriesKM for PATROL

Version 1.2.00

Contacting BMC SoftwareYou can access the BMC Software Web site at http://www.bmc.com/. From this Web site, you can obtaininformation about the company, its products, corporate offices, special events, and career opportunities.

United States and Canada Outside United States and Canada

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

Telephone (01) 713 918 8800

Telephone 713 918 8800 or 800 841 2031

Fax (01) 713 918 8000

Fax 713 918 8000

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.

IBM is a registered trademark of International Business Machines Corporation.

DB2 is a registered trademark of International Business Machines Corporation.

Oracle is a registered trademark, and the Oracle product names are registered trademarks ortrademarks of Oracle Corporation.

All other trademarks belong to their respective companies.

BMC Software considers information included in this documentation to be proprietary and confidential.Your use of this information is subject to the terms and conditions of the applicable End User LicenseAgreement for the product and the proprietary and restricted rights notices included in thisdocumentation.

Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDERTHE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data andcomputer software by the U.S. Government is subject to restrictions, as applicable, set forth in FARSection 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.

2

Version 1.2.00

IBM DS6000, DS8000 Series KM for PATROL

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. To expedite your inquiry, please see "BeforeContacting BMC Software."

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-mailaddresses, fax numbers, and telephone numbers

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, call800 537 1813. Outside the United States and Canada, please contact your local support center forassistance. To find telephone and email contact information for the BMC Software support center thatservices your location, refer to the Contact Customer Support section of the Support page on the BMCSoftware Web site at http://www.bmc.com/support_home.

Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support canbegin working on your problem immediately:

Product information

product name

product version (release number)

license number and password (trial or permanent)

Operating system and environment information machine type operating system type, version, andservice pack or other maintenance level such as:

PUT or PTF

system hardware configuration

serial numbers

related software (database, application, and communication) including type, version, and service

pack or maintenance

level

Sequence of events leading to the problem

Commands and options that you used

Messages received (and the time and date that you received them)

product error messages

messages from the operating system, such as "file system full"

3


Version 1.2.00

http://www.bmc.com/support_home



Table of Contents 4


Version 1.2.00

Table of Contents...........................................................................................................................11Product at a Glance

...........................................................................................................................12Synergy with Hardware Sentry KM for PATROL

...........................................................................................................................13Supported Platforms

...........................................................................................................................16Prerequisites

...........................................................................................................................17Getting the BMC Software Installation Utility

...........................................................................................................................18Packages

...........................................................................................................................19Extracting the Setup Files

...........................................................................................................................20IBM Storage Manager (Windows)

...........................................................................................................................20Installing the IBM DS6000/DS8000 Storage Manager (Windows)

...........................................................................................................................22Configuring the IBM DS6000/DS8000 Storage Manager

...........................................................................................................................24Installing the IBM CIM Agent for DS Open API

...........................................................................................................................29Installing IBM DS6000, DS8000 Series KM for PATROL

...........................................................................................................................41Uninstalling IBM DS6000, DS8000 Series KM for PATROL

...........................................................................................................................49Integrating with BMC Portal

...........................................................................................................................50Integrating with BMC ProactiveNet Performance Management

...........................................................................................................................51Creating and Importing an Adapter for a BMC PATROL KM

...........................................................................................................................59Updating an Adapter for a BMC PATROL KM

...........................................................................................................................59Importing and Customizing Thresholds

...........................................................................................................................61Managing Baselines and Key Performance Indicators

...........................................................................................................................65Configuring the KM

...........................................................................................................................65Adding a Connection to an IBM DS Storage Manager

...........................................................................................................................67Editing IBM DS Storage Manager Connection Settings

...........................................................................................................................68Monitoring with the KM

...........................................................................................................................68Viewing the Overall Activity of a Storage Unit

...........................................................................................................................69Reporting the Total Traffic on an Hourly or Daily Basis

...........................................................................................................................7 0Monitoring the Efficiency of the Caching Mechanism

...........................................................................................................................7 3Reporting Disk Space Consumption

...........................................................................................................................7 6Reporting the Overall Available Disk Space

...........................................................................................................................7 7Reclaiming Space of Unused LUNs

...........................................................................................................................81Diagnosing Slow LUNs

...........................................................................................................................82Identifying the Hosts that can Access a Logical Drive

...........................................................................................................................83Identifying the Busiest Logical Drives

Table of Contents 5


Version 1.2.00

...........................................................................................................................86Diagnosing Fiber Performance Issues

...........................................................................................................................87Diagnosing a Bad Physical Disk Layout

...........................................................................................................................88Search WWN

...........................................................................................................................90Reporting

..................................................................................................................90Storage Units Activity Report

..................................................................................................................91Ranks Activity Report

..................................................................................................................92Fiber Ports Activity Report

..................................................................................................................93Volumes Activity Report

..................................................................................................................94LUNs Mapping Table

..................................................................................................................95Per Host Storage Allocation

..................................................................................................................96Per LUN Storage Allocation

..................................................................................................................96Scheduling Reports

...........................................................................................................................98Administrative Tasks

...........................................................................................................................98Configuring Java Settings

...........................................................................................................................102Customizing the Discovery Interval

...........................................................................................................................103Customizing the Polling Interval

...........................................................................................................................103Enabling the Debug Mode

...........................................................................................................................104Managing Internal KM Issues Notifications

...........................................................................................................................106Managing Unknown Status

...........................................................................................................................106Pausing/Resuming Monitoring

...........................................................................................................................107Reinitializing the KM

...........................................................................................................................109Restoring Monitoring

...........................................................................................................................110Removing Device Monitoring

...........................................................................................................................110Triggering a KM Discovery

...........................................................................................................................111Thresholds, Alerts and Notifications

...........................................................................................................................111Threshold Mechanism Selection

...........................................................................................................................112Modifying Alert Thresholds

...........................................................................................................................113Alert Actions

...........................................................................................................................114Alert Actions Macros

...........................................................................................................................115Edit Alert Actions

..................................................................................................................117Trigger a PATROL Event

..................................................................................................................118Annotate the Parameter’s Graph

..................................................................................................................119Execute an OS Command

..................................................................................................................120Execute a PSL Command

..................................................................................................................121Send a Pop-up to the PATROL Consoles

..................................................................................................................122Write a Line to a LOG File

Table of Contents 6


Version 1.2.00

..................................................................................................................123Send a Basic SNMP Trap

..................................................................................................................124Send a custom SNMP Trap (advanced)

..................................................................................................................125Send an E-mail

...........................................................................................................................128Classes and Parameters

...........................................................................................................................129SEN_I68_MAIN

...........................................................................................................................131SEN_I68_EXTENTPOOL

...........................................................................................................................132SEN_I68_EXTENTPOOL_CONT

...........................................................................................................................133SEN_I68_FCPORT

...........................................................................................................................135SEN_I68_FCPORT_CONT

...........................................................................................................................135SEN_I68_RANK

...........................................................................................................................137SEN_I68_RANK_CONT

...........................................................................................................................138SEN_I68_SMISPROVIDER

...........................................................................................................................139SEN_I68_SMISPROVIDER_CONT

...........................................................................................................................140SEN_I68_STORAGEUNIT

...........................................................................................................................142SEN_I68_VOLUME

...........................................................................................................................144SEN_I68_VOLUME_CONT

...........................................................................................................................146Configuration Variables

Release Notes for v1.2.00

8


Version 1.2.00

What's NewIBM DS6000, DS8000 Series KM for PATROL is now compatible with BMC ProactiveNet CentralMonitoring Administration. This feature is supported by BMC ProactiveNet PerformanceManagement version 9.0.00.

Reporting:

FC ports are now listed in the LUNs Mapping Table report.

The list of mapped/unmapped LUNs can now be sorted by storage unit.

The Per Host Storage Allocation and Per LUN Storage allocation reports, were added toindicate how much storage is allocated to each monitored LUN and Host.

Reports Scheduling: Activity and LUNs Mapping Table reports can now be generated every dayat a specific time. The information, retrieved as a text file, can later be used by other tools suchas BMC Capacity Optimization.

Additional information were added to the product's Infobox.

A connection to a subsystem can now be directly configured from the SEN_I68_SMISPROVIDER_CONT application class.

The new TimeSinceLastActivity parameter reports the number of days since the last read orwrite operation has been observed on the monitored LUN.

Changes and ImprovementsIt is now possible to disable the validation tests of the JRE used by the KM to run Java code andtherefore force the KM to use a non-Sun or non-Oracle JRE. To disable the validation test, set the /SENTRY/SEN_68/disableJRECheck variable in the PATROL Agent's configuration. Warning: ApacheJRE is not supported.

The Debug mode was modified to ensure BPPM 9.x compatibility

KM Commands

The KM commands menu has been reorganized.

The “Modify Alert Thresholds” KM Command has been removed from most classes, as thethresholds can now be managed by PATROL administrators in a standard way through the EventManagement KM and PCM (or any other method used in their environment).

The Restore Device Monitoring KM Command has been renamed Restore Monitoring. The userinterface was also simplified to reduce the number of operations required to restore the monitoringof a component.

Fixed IssuesThe Restore Monitoring KM command lists devices to restore even when the SMI-S Provider wasremoved from the monitored environment.

Overview

10


Version 1.2.00

IBM DS6000, DS8000 Series KM for PATROL monitors all your IBM storage assets within a centralizedmanagement console. All the information concerning disk arrays, storage pools, controllers, storagevolumes, and ports are directly displayed in your BMC Framework. By monitoring all your IBM storagedevices within a centralized management console, you can respond quickly to performance problems,easily determine capacity requirements, and effectively plan for network expansions.

IBM DS6000, DS8000 Series KM for PATROL works in conjunction with Hardware Sentry KM for PATROL.Hardware Sentry KM discovers and monitors all the hardware aspects of the IBM disk array: disks,RAIDs, controllers, temperature sensors, fans, power supplies, Ethernet cards, fiber ports, etc. IBMDS6000, DS8000 Series KM for PATROL discovers and monitors all the software aspects of the array:overall capacity, spare disks, data traffic, oversubscription, etc.

11Product at a Glance


Version 1.2.00

Product at a Glance

IBM DS6000, DS8000 Series KM for PATROL enables you to monitor their IBM environment from thePATROL console avoiding the need to use a separate monitoring solution. The KM collects and bringscritical performance data and useful metrics into your BMC Framework.

PA TROL Console – IBM DS6000, DS8000 Series KM for PA TROL

As part of the Sentry Software Storage solution, IBM DS6000, DS8000 Series KM for PATROL coversperformance counters while Hardware Sentry KM for PATROL collects hardware-related information.

To properly collect metrics and performances from your IBM storage env ironment IBM DS6000, DS8000 Series KM for

PATROL requires access to the IBM Storage Manager.

12Synergy with Hardware Sentry KM for PATROL


Version 1.2.00

Synergy with Hardware Sentry KMfor PATROL

To benefit from a complete monitoring of your IBM environment, IBM DS6000, DS8000 Series KM forPATROL needs to be used in conjunction with Hardware Sentry KM for PATROL.

Hardware Sentry KM for PATROL discovers all the physical components of your storage devices,that is: controllers, disks, power supplies, fans, network and fiber ports, and reports hardwarefailures on these components. Additionally, it monitors the traffic on each network and fiber port. Hardware Sentry KM for PATROL is part of the Sentry Software monitoring product line.

IBM DS6000, DS8000 Series KM for PATROL monitors all of the performance metrics and usagestatistics of your IBM environment, such as file disk space usage, storage utilization, I/Os on thestorage units/ranks/volumes, etc. It continuously monitors the activity of each component and isalso able to build reports on past utilization statistics.

Architecture

The complete storage monitoring solution architecture is composed of the elements represented in thefigure below:

IBM DS6000, DS8000 Series KM for PA TROL – A rchitecture

13Supported Platforms


Version 1.2.00

Supported Platforms

IBM DS6000, DS8000 Series KM for PATROL supports the following IBM equipment:

IBM DS6000 series IBM DS8000 series

Preparing for Installation

15


Version 1.2.00

This chapter provides information about the tasks that must be performed before you start installing IBMDS6000, DS8000 Series KM for PATROL. Make sure to carefully read the following sectionsrequirements:

Review the Installation and Configuration Requirements

Get the BMC Software Installation Utility

Download the Installation Packages

Extract the Setup Files

Install and Configure IBM Storage Manager

16Prerequisites


Version 1.2.00

Prerequisites

Integrated as a native module for BMC ProactiveNet Performance Management, IBM DS6000, DS8000Series KM for PATROL is designed to monitor the health and performance of your IBM storageenvironment.

Prior to install IBM DS6000, DS8000 Series KM for PATROL, make sure that the following elements areinstalled and properly configured:

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

PATROL Console (see BMC PATROL documentation)

IBM Storage Manager

Java 1.5 or higher.

Finally, make sure that IBM DS6000, DS8000 Series KM for PATROL is installed on a server that hasaccess to the IBM Storage Manager.

17Getting the BMC Software Installation Utility


Version 1.2.00

Getting the BMC SoftwareInstallation Utility

In order to install IBM DS6000, DS8000 Series KM for PATROL, you need the latest version of the BMCSoftware Installation Utility. You can download the latest Installation Utility from the BMC Software EPD(Electronic Product Download) from: http://webapps.bmc.com/signon/content/logon.jsp on the BMCSoftware Website, or from the IBM DS6000, DS8000 Series KM for PATROL page on the SentrySoftware Website.

Choose the appropriate package depending on the platform you plan to install IBM DS6000, DS8000Series KM for PATROL on:

For UNIX/Linux systems: ins_ALL_<version>.tar

For Windows systems: ins_WINDOWS_<version>.zip

The packages are valid for all the PATROL components: Agent, Console, Console Server, etc.

Place the Installation Utility package in the same folder as the IBM DS6000, DS8000 Series KM forPATROL packages.

http://webapps.bmc.com/signon/content/logon.jsp

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

18Packages


Version 1.2.00

Packages

The IBM DS6000, DS8000 Series KM for PATROL packages are available on the Sentry Software Website.

There are two packages, each of which can be used to install the KM on every PATROL component(Agent, Console, etc.) according to the platform you are using.

Downloading from Sentry Software Web site

For Windows systems: seni68_WINDOWS_<version>.zip

For UNIX and Linux systems: seni68_UNIX_<version>.tar

Java Runtime Environment Package

Java Runtime Environment version 1.5.00 or higher is required in some cases for the KM to operateproperly.A package with a suitable Java Runtime Environment, designed for use with the BMC SoftwareInstallation Utility, is made available to download on:

the Sentry Software Web site.

The IBM DS6000, DS8000 Series KM for PATROL packages are designed for use with the BMCSoftware Installation Utility (formerly known as Thorium). They need to be merged with the latestavailable version of the BMC Software Installation Utility. Please see instructions.

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



19Extracting the Setup Files


Version 1.2.00

Extracting the Setup Files

Like most Knowledge Modules for PATROL, you need to install IBM DS6000, DS8000 Series KM forPATROL on the following components of your PATROL architecture:

Every managed system with a PATROL Agent

Every PATROL Console (Classic) that will show IBM performance-related information and alerts

The Console Server

PATROL Central – Web Edition

On Windows

The packages for Windows are to be extracted in the consecutive order:

1. First, unzip the BMC Installation Utility: ins_Windows_<version>.zip

2. Next, unzip the IBM DS6000, DS8000 Series KM for PATROL package in the same folder: seni68_WINDOWS_<version>.zip

3. Then, unzip the senjre_<version>_WINDOWS.zip package if you need to install the latest JavaRuntime Environment program

The content of the packages merges into a subfolder named bmc_products.

A pache JRE is not supported.

Windows may ask for your confirmation to overwrite files and folders. This is normal behav ior and you can accept alloverwrite confirmation requests.

On UNIX/Linux

The packages for UNIX/Linux are to be extracted with the tar utility:

1. First, untar the BMC Installation Utility: tar xvf ins_ALL_<version>.tar

2. Next, untar the IBM DS6000, DS8000 Series KM for PATROL package named: LYV39_<version>_Storage_KM.tar if downloaded from BMC Software EPD Web site orseni65_UNIX_<version>.tar if downloaded from the Sentry Software Web site.

The files are extracted into a sub-directory named bmc_products.

http://www.bmc.com/available/epd.html

http://www.sentrysoftware.net/link.asp?topic=86

20IBM Storage Manager (Windows)


Version 1.2.00

IBM Storage Manager (Windows)

To fully monitor IBM DS6000 and IBM DS8000 disk systems, you are required to install IBM DS StorageManager. IBM Storage Manager needs to be installed on any server that has network access to theDS6000 and/or DS8000 Management Card.

The IBM Storage Manager is usually already installed and configured in most environments. In thatcase, proceed directly to installing the IBM CIM Agent for DS Open API.

Installing the IBM DS6000/DS8000 StorageManager (Windows)The DS Storage Manager is installed using graphical or unattended (silent) mode for Windows operatingsystems. It can be accessed remotely from any location that has network access using a Web browser.The result of the installation is access to a configuration tool that can be used in offline or onlinesettings.

Port ConfigurationSpecify Ports for the DS Storage Manager to use (or accept defaults):

SSL Configuration Specify the location of an existing certificate, or



Version 1.2.00

Enter key file and trust file passwords to generate a certificate:

SSL Configuration (Generate Certificate – AdditionalInformation)

Enter additional information for the SSL certificate (optional):

Click Install on the next page.

The Server will need to be rebooted after installation:



Version 1.2.00

Configuring the IBM DS6000/DS8000 StorageManagerThis section provides an overview of the configuration steps required after you install the DS StorageManager.

The installation of the IBM created two new services:

Several new items will also be available from the Start menu:

Open the "Open DS Storage Manager":



Version 1.2.00

The default username is "admin", and password is "admin".

On the Main Storage Manager page:

Specify a new admin password on the next page.

Under Real-Time Manager > Manage Hardware, select Storage Complexes.

Select a management console (tick the highlighted box).

In the --- Select Action --- list, select Assign Storage Unit

Assign Storage Unit :



Version 1.2.00

Enter a Nickname

Enter the two IP addresses of the DS6000 series controller cards.

Enter the last 7 digits of the serial number listed on the storage unit.

(The serial number can be found under the right hand bezel of the storage unit:

Click Next

Enter Gateway and Subnet Mask information

Click Next and then Finish

The DS6000 Storage Manager will now try to add your unit. This process can take some time. Ifyou have multiple units to add, you can click "Close and View Summary"

Repeat Process for Each DS6000 unit.

Once All Assign Storage Unit processes are finished (see Long Running Task Summary Page)

Installing the IBM CIM Agent for DS Open APIOnce the IBM DS6000/DS8000 Storage Manager is installed and configured so that it can see allDS6000/DS8000 units, the CIM Agent needs to be installed. The CIM Agent can be installed on anyserver that has network access to the server on which the IBM DS6000/DS8000 Storage Manager hasbeen installed.

Access the IBM Web site to get the complete package for the IBM CIM Agent for DS Open API andproceed with its installation. Finally, follow the configuration instructions provided below to ensure a fullinteraction with IBM DS6000, DS8000 Series KM for PATROL.

http://www.ibm.com



Version 1.2.00

Configuration Instructions

Server Communication Configuration

Select which protocols (http / https) and ports to install the CIM Agent on.

These are the protocols and ports that need to be entered in the WBEM Credentials page of the Adda Connection to an IBM DS Storage Manager wizard.

Configuration Parameters

Specify a user name and password. The user name and password specified here are those thatneed to be entered in the WBEM Credentials page of the Add a Connection to an IBM DS StorageManager wizard.

Click Add

Fill in the information related to the new device:

Device Type: Type DS

IP Address: Enter the IP Address of the Server on which the IBM DS6000/DS8000 StorageManager has been installed (not of the DS array).

Alternative IP: Leave Blank

Username / Password: Enter the username and password needed to access the IBM DS6000/DS8000 Storage Manager.



Version 1.2.00

If the DS arrays are split across multiple management servers, or if you have both DS6000 &DS8000 management server, repeat the above procedure for each management server.

Checking the installation

Run dscimcli.bat lsdev. This will list all the management servers that the CIM Agent is connected to.

C:\Program Files\IBM\dsagent\bin>dscimcli.bat lsdev

Type IP IP2 Username

===== ======================================= ======================================= =========

DS SERVER-1 - admin

The dscimcli.bat file can also be used to add new management servers.

Installing the KM

28


Version 1.2.00

Introduction

This chapter describes the installation procedure for IBM DS6000, DS8000 Series KM for PATROL on anyPATROL component (Agents, Consoles, Console Server, etc.). As the setup is based on the BMCSoftware Installation Utility, this procedure applies to all operating systems supported by IBM DS6000,DS8000 Series KM for PATROL. Although not covered by this section, the installation through theDistribution Server is fully supported. Please refer to the Distribution Server documentation, provided byBMC, for a detailed description of the deployment procedure.

29Installing IBM DS6000, DS8000 Series KM forPATROL


Version 1.2.00

Installing IBM DS6000, DS8000Series KM for PATROL

Installing IBM DS6000, DS8000 Series KM for PATROL is an automated process managed by a wizard.The wizard goes through the necessary steps to install the KM and all files associated with it. You aresimply prompt for the product's folder location and the product/components to install.

IBM DS6000, DS8000 Series KM for PATROL must be installed on a server that has access to the IBMStorage Manager.

Browse to the bmc_products folder where the files have been extracted (both IBM DS6000, DS8000Series KM for PATROL and the Common Installer).



Version 1.2.00

On Windows: Launch the setup.exe program

On UNIX: Launch the setup.sh script

To install IBM DS6000, DS8000 Series KM forPATROL1. Allow the perl.exe program listen on this port: Click Allow access.

2. The Welcome screen of the installer appears. Click Next to continue.

Installation Wizard - Step 2: Welcom e



Version 1.2.00

3. Read the license agreement, click the Accept option and then click Next to continue.

Installation Wizard - Step 3: A ccepting License A greem ent



Version 1.2.00

4. Select Install products on this computer now and click Next to continue.

Installation Wizard - Step 4: Selecting Installation Options



Version 1.2.00

5. Specify the BMC Software products folder. See the BMC Software documentation for moreinformation about the BMC Software products folder. Click Next to continue.

Installation Wizard - Step 5: Selecting the Installation Directory



Version 1.2.00

6. Select the Default option. Installing IBM DS6000, DS8000 Series KM for PATROL does not requireany customization.Click Next to continue.

Installation Wizard - Step 6: Selecting an Installation Ty pe

7. Select one or several of the following options:

Managed System to install IBM DS6000, DS8000 Series KM for PATROL on a PATROL Agent.

Console Systems role to install IBM DS6000, DS8000 Series KM for PATROL on a PATROLClassic Console.

Common services to install IBM DS6000, DS8000 Series KM for PATROL on the Console Serveror on PATROL Central – Web Edition.

Click Next to continue.



Version 1.2.00

Installation Wizard - Step 7: Selecting Roles



Version 1.2.00

8. Check the IBM DS6000, DS8000 Series KM for PATROL box to install the KM (it should beselected by default).Select the Java Runtime Environment program if you want to install it along with the KM (thisoption is only provided when you have previously downloaded the package).Click Next to continue.

Installation Wizard - Step 8: Selecting Products and Com ponents



Version 1.2.00

9. Review the installation parameters and click Start Install to launch the installation procedure.

Installation Wizard - Step 9: Rev iewing Installation Options



Version 1.2.00

10. The setup program displays the actions performed and indicates the percentage of completion.Once the installation complete, click Next to view the installation results.

Installation Wizard - Step 10: Installation Status



Version 1.2.00

11. The wizard displays the installation results.Click View Log to display a detailed log of the installation procedure.Click Next and then Finish to exit the setup program.

Installation Wizard - Step 11: Installation Results

12. Press the Finish button to complete and close the installation wizard.



Version 1.2.00

Installation Wizard - Step 12: Com pleting and closing the Installation Wizard

A Help button in available at each step of the procedure. Click to display the installation online help. The Exit buttonallows you to stop the installation procedure.

41Uninstalling IBM DS6000, DS8000 Series KM forPATROL


Version 1.2.00

Uninstalling IBM DS6000, DS8000Series KM for PATROL

Uninstalling IBM DS6000, DS8000 Series KM for PATROL is an automated process managed by a wizard.The wizard goes through the necessary steps to remove the KM and all files associated with it. You aresimply prompt for the product's folder location and the product/components to uninstall.

To uninstall IBM DS6000, DS8000 Series KM forPATROL1. Locate the Uninstall folder under the BMC products directory (typically under C:\Program Files\BMC

Software, or /opt/bmc):

On Windows systems, launch uninstall.exe

On UNIX, launch uninstall.sh

Un-install Wizard — Welcom e Step



Version 1.2.00

2. Specify the BMC Software products folder. See the BMC Software documentation for moreinformation about the BMC Software products folder.

Un-install Wizard — Specify ing folder



Version 1.2.00

3. To uninstall the KM, select IBM DS6000, DS8000 Series KM for PATROL.

Un-install Wizard — Selecting Products and Com ponents Directory



Version 1.2.00

4. Click Start Uninstall to run the program.

Un-install Wizard — Rev iewing Selected Products & com ponents and start uninstalling



Version 1.2.00

5. A page displays the list of products/components processed and the percentage of completion.Click Next to continue.

Un-install Wizard — Status



Version 1.2.00

6. The last page informs you of the success or failure of the process.Click Finish to close the wizard.

Un-install Wizard — Uninstall Results

Integrating the KM into the BMC Framework

48


Version 1.2.00

Introduction

This section provides detailed information about the integration of IBM DS6000, DS8000 Series KM forPATROL with BMC ProactiveNet Performance Management.

49Integrating with BMC Portal


Version 1.2.00

Integrating with BMC Portal

An integration component for BMC Portal is released along with the Knowledge Module (KM) in the formof a PAR file: SentrySoftware-PM-PATROL-SENI68-<version>.par. It enables visualization ofparameter data of all objects monitored by the KM, in the BMC Portal environment.

This integration component is valid on BMC Portal v2.3 upwards.

To integrate IBM DS6000, DS8000 Series KM for PATROL with BMC Portal:

1. Install the KM on top of a PATROL Agent as detailed in the Installation Guide. A PATROL Console willbe required to configure the KM

2. In the PATROL Console, make sure the KM properly discovered the IBM storage systems and iscollecting data

3. Upload the PAR file in BMC Portal:

Place the SentrySoftware-PM-PATROL-SENI68-<version>.par file in a known location onyour file system.

Login to BMC Portal with the superadmin credentials.

Click on Portal, then under Tasks click Performance Managers.

Click Upload and then click Browse to open a file selection dialog box.

Select SentrySoftware-PM-PATROL-SENI68-<version>.par and click Upload.

4. Create a new managed element:

Login to BMC Portal with administrator credentials

Click the Configure tab > Elements > Add

Select Infrastructure Element and click Next

Select an RSM to collect data about the infrastructure element and click Next

Enter the name of the machine on which the PATROL agent is running, the Host Name and clickNext

Select the group to which your PM will belong and click Next

Select the PATROL category, the Application Classes to add and click Next

Set the Properties and Credentials that the RSM must have to access the specified elementsand click Next. The list of thresholds is displayed. You can update these settings withoutimpacting the values set in PATROL.

5. Click Finish.

Thresholds are set in the PATROL console. To get the last configurations made, click the Refresh PA TROLIntegration button available in the Elem ents page.

50Integrating with BMC ProactiveNet PerformanceManagement


Version 1.2.00

Integrating with BMC ProactiveNetPerformance Management

Overview

To integrate a BMC PATROL KM into BMC ProactiveNet, you need to create a specific adapter. Anadapter for BMC PATROL facilitates pulling of performance data from existing BMC PATROL solutionsinto BMC ProactiveNet. Using an Adapter, you can import BMC PATROL application classes (provided in aKnowledge Module –KM) into BMC ProactiveNet. The Adapter periodically synchronizes the performancedata collected by these application classes into BMC ProactiveNet.

A dapter for BMC PA TROL A rchitecture



Version 1.2.00

Creating and Importing an Adapter for a BMCPATROL KM

Creating an Adapter for a BMC PATROL KM1. Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration Console

is displayed as shown in the following figure:

A ccessing the A dm inistration tab in the A dm inistration Console



Version 1.2.00

2. Right-click the Adapters folder and select Import Monitor Type and Add Adapter > BMCPATROL.

Im porting Monitor Ty pes and A dding A dapter



Version 1.2.00

3. In the Configuration tab, enter the required information:

Setting the connection param eters

In the Instance Name field, enter a name for this instance of the Adapter that will perform theintegration of the ‘targeted KM’ into BMC ProactiveNet.

Select the Agent where this instance of the Adapter will be executed

Enter the Integration Service Agent hostname or IP address

Enter the Integration Service Agent Port. The default port is 3182.

Enter the required credential to connect to the Integration Service Agent



Version 1.2.00

4. Click Next to continue

Rev iewing the Integration Serv ice configuration



Version 1.2.00

5. Click Next to let the system load the BMC PATROL application classes.

Selecting A pplication Classes to im port

6. Select the application classes to import

Unselecting will delete the application classes that have already been imported during a previousoperation. Application classes ready to be deleted are marked with a red x.



Version 1.2.00

7. Click Next to start the import process. The system displays a summary of the application classimport, click Next to continue.

8. Select the application classes you wish to auto-synchronize with the Integration Service Agent.

Selecting A pplication Classes for A uto-sy nc



Version 1.2.00


10. Set the Filter details if need.

Setting filter details



Version 1.2.00

11. Click Next to continue.

12. Set the Auto-sync poll scheduling, if needed.

Scheduling A uto-sy nc polls

13. Click Next to continue. The system displays a summary of your settings, click Finish to confirm. TheAdapter has been added to the Adapters folder of the Administration Console.

14. To see the class instances that have been imported by the Adapter, expand the Adapters folder,right-click the Adapter and select Details.

We strongly recommend that you create a specific adapter for each KM you need to integrate intoBMC ProactiveNet to enable the update of a single KM independently.



Version 1.2.00

Updating an Adapter for a BMC PATROL KM

Updating an Adapter1. Delete the Adapter instance

2. Go through the Add an Adapter wizard to actually delete the monitor types that had been createdbased on the previous version of the KM

3. Close

4. Resume the entire Creating an Adapter for a BMC PATROL KM procedure

For complete and detailed information on these procedures, please refer to the BMC ProactiveNet documentationavailable from BMC Web site.

Importing and Customizing Thresholds1. Launch the BMC ProactiveNet PW Commands. On Windows 2008, you need to run the PW

Commands as Administrator.

Launching BMC Proactiv eNet PW Com m ands

2. Execute the following command line:-pproxy_port <port_number>] [-pproxy_user <username>] [-pproxy_passwd <password>] -i -v



Version 1.2.00

where

-get_thresholds <file name> = File name with absolute path at which thresholds

will be imported

-pproxy_host <hostname|ipaddress> = Host name or IP Address of Patrol Proxy Server

-pproxy_port <port_number> = Port at which Patrol Proxy Agent communicates with Patrol

Proxy Server

-pproxy_user <username> = User name of Patrol Proxy user

-pproxy_passwd <password> = Password to authenticate Patrol Proxy user

-i = import Instance level thresholds

-v = run in "verbose" mode, producing extra lines of output during extraction and

conversion processes

The command has produced a text file with all the parameter threshold settings.

3. Open the file in a text editor. Check that the global thresholds have been properly interpreted.

4. Then go to the # INSTANCE LEVEL THRESHOLDS section of the file.

5. Uncomment all instance level thresholds for the _PATROL__SEN_I68_ prefixed instances.

Search the file for the 'NOT_IMPLEMENTED' occurrences to detect thresholds that were not properlyconverted by the PATROL Adapter.

6. Save the file.

7. Execute the following command:pw threshold loadpatrolthreshold [<thresholdfilename> [-v]]

where:

<thresholdfilename> is a thresholds file name. If no file path is specified

then the default '<Installation Directory>/pw/tmp/' is used

-v enables the Verbose mode

Class-level thresholds can be displayed using the Absolute Global Thresholds panel in the BMCProactiveNet Operator Console, while instance-level thresholds are displayed in the Absolute InstanceThresholds panel:



Version 1.2.00

Visualizing instance-lev el thresholds

Thresholds have been successfully imported into BMC ProactiveNet.

Managing Baselines and Key PerformanceIndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNetcalculates baselines per parameter (metrics or attributes) based on values collected over a specifiedperiod of time to determine a normal operating range. When the collected values for these parametersare out of range, an alert is triggered.

Some parameters are identified by default as Key Performance Indicators and therefore automaticallyincluded in the base lining calculation.

Managing baselines

The baseline is the expected normal operating range for a metric or attribute of a monitor.

The baseline is calculated by collecting the values for a monitor’s attributes and metrics over a specifiedtime period and establishing a low baseline value (consisting of the 10th percentile of all the values for agiven time period) and a high baseline value (consisting of the 90th percentile of all the values for agiven time period), taking a weighted average of these values over time. A higher weight is given to thelatest data being factored into the baseline average. The accuracy of the baseline improves over time.

Requirements for baseline generation

For baselines to be generated for an attribute, that abnormality threshold means that the thresholdexists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have anactive abnormality threshold and are also KPI attributes will have baselines generated for them.

Absolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements.

Managing Key Performance Indicators

The KPI attribute of a parameter can be activated or deactivated manually through the BMC ProactiveNetAdministration Console. In this KM, some parameters or attributes have been designated as importantindicators of performance (KPIs). We do not recommend that these default settings are modified.

However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet AdministrationConsole.



Version 1.2.00

To add or remove Key Performance Indicator (KPI) attributes for amonitor type

1. In the Administration Console, from the menu bar, choose Tools > KPI Administration. TheKPI Administration dialog box is displayed.

2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPIattributes. A list of attributes for the selected monitor type is displayed.

3. In the KPI column for the attributes that you want to add or remove as Key Performance Indicators:

select the KPI check box to add the corresponding attribute as a KPI

deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitortype

For complete and detailed information on this procedure, please refer to the BMC ProactiveNet documentation availablefrom BMC Web site.

Parameters for which the system by default calculates baselines as well as parameters considered asKPIs are respectively identified by the following icons:

Baselining

KPI

Monitoring your Storage Environment

64


Version 1.2.00

Introduction

IBM DS6000, DS8000 Series KM for PATROL monitors all of the performance metrics and usagestatistics of your IBM storage environment, such as file disk space usage, storage utilization, I/Os on thestorage units/ranks/volumes, etc.. It continuously monitors the activity of each storage unit and is alsoable to build reports on past utilization and statistics.

This chapter provides detailed information on how to manage connections to IBM DS Storage Manager,monitor your IBM storage environment, perform basic administrative tasks, and how to managethresholds and alert actions with IBM DS6000, DS8000 Series KM for PATROL.

To setup a complete monitoring of your IBM env ironment, we strongly recommend you to also use Hardware SentryKM for PATROL that covers all the physical aspect of the IBM equipment (status of the disks, ports, temperature,power supplies, power consumption, etc).

65Configuring the KM


Version 1.2.00

Configuring the KM

IBM DS6000, DS8000 Series KM for PATROL relies on the IBM DS Storage Manager installed on one ofyour server to properly monitor the IBM storage units metrics and performances.

IBM DS Storage Manager is a software suite that needs to be installed on a separate server. See the IBM DS StorageManager section in the Installation Guide for further information.

To efficiently monitor an IBM storage element, you need to create a connection between the KM and theelement you wish to monitor. This chapter deals with the management of connections with the IBM DSStorage Manager which basically consists in:

Adding a connection

Editing a connection

Adding a Connection to an IBM DS StorageManagerAdding the monitoring of an IBM storage element in your monitored environment requires the creationand the setting-up of a connection to an IBM DS Storage Manager:

1. Right-click the KM main icon > KM Commands > Add a Connection to an IBM DS StorageManager

2. Enter the Server Host Name and the Server IP address (leave blank to user the Server HostName address)



Version 1.2.00

Identify ing the IBM DS Storage Manager Connection


4. Set connection parameters and enter WBEM Credentials:

Enter the port number through which the connection must be established

Click the Encrypt data using the HTTPS protocol, if necessary (The port typically used toencrypt data for WBEM queries is 5989)

Enter a valid username and password for the CIM server

Set Connection Param eter

5. Click Finish to create a new connection to an IBM Storage Manager.



Version 1.2.00

Editing IBM DS Storage Manager ConnectionSettingsShould you need to edit an IBM DS Storage Manager connection settings:

1. Right-click a IBM DS Storage Manager connection icon > KM Commands > Edit ConnectionSettings

2. Modify the Server name (or IP address)

Identify ing the Hitachi Dev ice Manager Connection


4. Modify the connection parameters and the WBEM Credentials, if required:

Modify the port number through which the connection must be established

Click the Encrypt data using the HTTPS protocol, if necessary (The port typically used toencrypt data for WBEM queries is 5989)

Modify the username and password for the CIM server

5. Click Finish to save your changes.

68Monitoring with the KM


Version 1.2.00

Monitoring with the KM

Monitoring your IBM storage environment with IBM DS6000, DS8000 Series KM for PATROL is verysimple. Once the KM is properly installed, as per the instructions given in the Installation Guide, the KMautomatically detects the various IBM storage devices and components of your storage environment anddisplays them in the PATROL interface.

This chapter provides various use cases that cover the basic operations a SAN administrator may berequired to perform to obtain a complete and detailed picture of the IBM storage environment typicallyinstalled in a data center.

For detailed information about the performance metrics and usage statistics that are detected on each system,please see the Classes and Parameters section in the Reference Guide.

Viewing the Overall Activity of a Storage UnitIn order to visualize the activity of a storage unit, refer to the ReadByteRate and WriteByteRateparameters of the SEN_I68_STORAGEUNIT class. These parameters represent the overall traffic inmegabytes per second for each monitored storage unit, or more precisely, each IBM storage unit that isexposed through the IBM Storage Manager (see the Installation Guide for more information about theIBM System Storage DS Storage Manager).

Verifying a storage unit activity

1. In the console, double-click the ReadByteRate parameter of the storage unit you are interestedin. A graph is automatically displayed in the graph pane.

2. Drag the WriteByteRate parameter of the same storage unit in the graph.

Selecting Storage Unit's Param eters



Version 1.2.00

The overall activity can also be reported in GB per hour or per day (instead of MB/sec) so SANadministrators can visualize how much data has been written to or read off the storage unit each hourof the day or each day of the week (see the Reporting the total traffic on an hourly or daily basis sectionfor more information on this subject).

Reporting the Total Traffic on an Hourly or DailyBasisIBM DS6000, DS8000 Series KM for PATROL not only monitors the traffic and activity of the storageunits, extent pools, and volumes in MB/sec, but also in GB per hour or per day. The exact amount ofdata that was transferred to the storage units, extent pools and volumes is calculated for each hour ofthe day and each day of the week.

The hourly report graph will represent the amount of data in GB from 12:00am to 12:59am, from1:00am to 1:59am, from 2:00am to 2:59am, etc, while the daily report graph will represent the amountof data in GB for Monday, for Tuesday, for Wednesday, etc.

This report is notably helpful to SAN administrators to understand the impact of the nightly backups, ofthe amount of data a specific application writes to a drive and how this evolves (with upgrades forexample). In general, this will help administrators analyze the impact on various features of the storageunit on the long term.

Generating a storage unit activity report

1. In the console, right-click the Storage Unit icon> KM Commands > Reporting > Storage UnitActivity...

2. Select the parameter for which you wish to generate a report:

read byte traffic,

write byte traffic, or

read/write bytes traffic.



Version 1.2.00

Configuring the Report Settings

3. Select the report range and interval

4. Select the specific storage unit(s) you wish to include in the report. By default all the monitoredstorage units are included in the report.

The Storage Unit selection option is only available when at least two storage units are monitored.

5. Click Show Report

The ability of the product to report on a given period of time depends on the history retention period of the PATROLAgent.

Monitoring the Efficiency of the CachingMechanismIBM DS6000, DS8000 Series KM for PATROL monitors the efficiency of the different caching mechanismsof the DS6000 and DS8000 disk arrays. The monitoring is performed on a per-volume basis with thefollowing parameters:

CacheFastWriteHitRatio: reports on the number of blocks that were successfully served by CacheFast Write (CFW).

DASDFastWriteHitRatio: reports on the number of blocks that were successfully served by DASDFast Write (DFW).

VolumeReadCacheHitRatio: reports on the number of blocks that were successfully read and servedby one of the available cache mechanisms.

The CacheFastWriteHitRatio and DASDFastWriteHitRatio parameters deal more specifically withthe physical writing of data to the disk, while the VolumeReadCacheHitRatio parameter reflects the



Version 1.2.00

cache efficiency for the read operations on the volume. The higher the values, the better.

CacheFastWriteHitRatio and DASDFastWriteHitRatio values dropping below 50% for a significantamount of time indicates a lack of cache memory for the current workload, and that the physicalbandwidth on the disk constitutes the limiting performance factor.

Querying 'HitRatio' parameters

1. Create a PATROL Query in the PATROL Console to show the value of theCacheFastWriteHitRatio, DASDFastWriteHitRatio and VolumeReadCacheHitRatioparameters of the SEN_I68_VOLUME class; In the main menu bar, click Action > New Query…

PA TROL Query – General Tab



Version 1.2.00

2. Enter the Query name (example: Caching Efficiency)

3. Enter the Query description (optional)

4. In the Query Result Filter section, select Show Selected Objects and check the Parametersbox

5. In the Additional Filtering section, select the Enable Application Class level filtering and theEnable Parameter level filtering options

6. Open the Application Class tab

7. In the Pattern Matching section, select Like and type SEN_I68_VOLUME

PA TROL Query – A pplication Class Tab

8. Open the Parameter tab



Version 1.2.00

9. In the Pattern Matching section, select Like and type .*HitRatio

PA TROL Query – Param eter Tab

10. Click OK to display a table displaying the amount of actually consumed capacity in all the extentpools of your monitored IBM environment.

Another easy way to get detailed information regarding the Hit Ratio parameters consists in generatinga graph for each of them. Simply double-click the CacheFastWriteHitRatio, DASDFastWriteHitRatio and VolumeReadCacheHitRatio parameters of a volume to display agraph in the right pane of your PATROL Console. Then, adjust the display and history range according toyour needs (refer to your PATROL Console documentation for detailed information on graphs).

Reporting Disk Space ConsumptionMaking sure that a disk array has enough remaining disk space available is critical for several reasons:

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

The extent pool itself may need additional disk space for specific features to work properly.

The ConsumedCapacity parameter of the SEN_I68_EXTENTPOOL class represent the actual spaceusage in the extent pool.

The ConsumedCapacityPercentage parameter is the most critical one, since an extent pool usagenearing 100% indicates that SAN administrators will not be able to create new ranks. By default, noalarm or warning threshold is set on this parameter as the fullness of an extent pool may be a normalsituation.



Version 1.2.00

Verifying the available disk space in extent pools

1. Create a PATROL Query in the PATROL Console to show the value of theConsumedCapacityPercentage parameter of the SEN_I68_EXTENTPOOL class; In the mainmenu bar, click Action > New Query…




Version 1.2.00

2. Enter the Query name (example: Disk Space Consumption)


4. In the Query Result Filter section, select Show Selected Objects and check the Parametersbox

5. In the Additional Filtering, select the Application Class level filtering and the EnableParameter level filtering options


7. In the Pattern Matching section, select Like and type SEN_I68_EXTENTPOOL





Version 1.2.00

9. In the Pattern Matching section, select Like and type ConsumedCapacityPercentage


10. Click OK to display a table with the amount of the actually consumed capacity in all of the extentpools of your monitored IBM environment.

Reporting the Overall Available Disk SpaceAmong other various useful performance metrics, the SEN_I68_STORAGEUNIT class covers metricsregarding the disk space in the storage unit:

The size of the storage unit (the Size parameter is available in the infobox subsystem instance)

The total subscribed capacity, i.e. the total amount of disk space exposed to the servers

The total amount of free disk space

For a more granular view of the disk space usage in the storage unit, analyze the parameters of the SEN_I68_EXTENTPOOL class.



Version 1.2.00

StorageUnit and ExtentPool Param eters

Reclaiming Space of Unused LUNs

Identifying Unmapped (Orphans) LUNs

Over time, as servers connected to a SAN get decommissioned, administrators find an increasingnumber of unmapped logical drives that are no longer used by any server. These logical drives, whileunused, still occupy disk space in the storage unit. Being able to identify such unmapped logical drivesand reclaim the disk space uselessly consumed by these drives will help administrators avoidunnecessary upgrades and extensions of their storage unit.

To list the logical drives that are not mapped to any server and therefore safe to remove, right-click the Storage Unit icon > KM Commands > Reporting > LUNs Mapping Table... . Refer to the LUNsMapping Table section for further details on this feature.

Whether a logical drive is actually mapped or not is also shown in the infobox of each volume instance.



Version 1.2.00

Volum e Properties - Infobox tab

Identifying Unused LUNs

When a server is decommissioned or reconfigured, its associated LUNs can stay mapped preventingstorage administrator from accurately identifying unused LUNs. Since the KM monitors permanently thetraffic on each LUN, it becomes easy to detect LUNs for which the activity is null.



Version 1.2.00

1. Create a PATROL Query in the PATROL Console to show the value of the TimeSinceLastActivityparameter of the SEN_I68_VOLUME class; In the main menu bar, click Action > New Query…




Version 1.2.00

2. Enter the Query name (example: Unused LUNs)


4. In the Query Results Filter section, select Show Selected Objects and check the Parametersbox

5. In the Additional Filtering, select the Application Class level filtering and the EnableParameter level filtering options



7. In the Pattern Matching section, select Like and type SEN_I68_VOLUME




Version 1.2.00


9. In the Pattern Matching section, select Like and type TimeSinceLastActivity

10. Click OK to display a list of the monitored LUNs and their respective number of days since when theKM has not recorded any activity.

The TimeSinceLastA ctiv ity parameter is evaluated from the date the KM was initially started.

Diagnosing Slow LUNsIf a system administrator complains that his servers are experiencing slow I/Os performance and that itis caused by the SAN, you may want to verify the actual response time of the LUNs the server is relyingon.

The ReadResponseTime and the WriteResponseTime parameters of the SEN_I68_VOLUME classrepresents the average time it took to complete the read and write operations on the LUN during thecollection interval. Typically, the average response time is below 10 milliseconds. You may also want tocompare this value with the response time of the other LUNs to see whether one server is really gettingworse I/O performance than another.



Version 1.2.00

1. In the console, double-click the VolumeReadResponseTime parameter of the storage unit youare interested in. A graph is automatically displayed in the graph pane.

2. Drag the VolumeWriteResponseTime parameter of the same storage unit in the graph.

Selecting Graph's Param eters

If the response time is low, you will need to check the amount of data that is written on and read offthis LUN. The bad performance may simply be due to an abnormally large amount of data to process.Otherwise, the problem may lie between the disk array and the server, in the fiber links.

Identifying the Hosts that can Access a LogicalDriveIn most SAN configuration, each logical drive belongs to a host group whose host members are the onlyones authorized to access the logical drive. This is called logical drive masking. For each logical drive,the solution displays its World Wide Name (WWN), the storage group to which it belongs to as well asthe host member of this group. In most cases, identifying the storage group of a LUN is sufficient torecognize the server that is using it.



Version 1.2.00

Identifying the Busiest Logical DrivesTo identify the logical drives that generate the most traffic on the storage unit, use the DiskReadByteRate, DiskWriteByteRate, VolumeReadByteRate and VolumeWriteByteRateparameters of the SEN_I68_VOLUME class.

The VolumeReadByteRate and VolumeWriteByteRate parameters represent the overall traffic oneach volume while the DiskWriteByteRate and DiskReadByteRate parameters only represents theamount of data that is read off and written on the physical disks. The difference between thesesparameters illustrates the various caching mechanisms in place.

IBM DS6000, DS8000 Series KM for PATROL offers you two methods to visually represent traffic on alogical drive .



Version 1.2.00

Create a multi-parameter graph to compare two logical drive activity

1. In the console, double-click the DiskReadByteRate parameter of the logical drive you areinterested in. A graph is automatically displayed in the graph pane.

Logical Driv es Param eters



Version 1.2.00

2. Then drag and drop the DiskReadByteRate parameter of the other logical drive in the graphwindow.Repeat the operation for the DiskWriteByteRate parameters of both logical drives to obtain agraph showing four parameters. You will then be able to easily evaluate which drive is the mostused in your storage unit.

Use the Reporting…Command

Should you need to compare more than two logical drives, the KM provides a report to facilitate thereading of the VolumeReadByteRate and the VolumeWriteByteRate of multiple volumes as well asthe DiskReadByteRate and the DiskWriteByteRate parameters. However, these two set ofparameters cannot be viewed in the same report.

1. Right-click the Volumes container > KM Commands > Reporting > Volumes Activity

2. Select the parameter for which you wish to generate a report for; in this case, select the Volumeread/write byte traffic parameter.



4. Press the Volumes Selection button to select the volumes you wish to include in your report. Bydefault, all the monitored volumes are selected.

5. Click Show Report.

Once you have identified the busiest logical drives, check the infobox of the suspected logical drives to find theirstorage groups and the hosts that generate such traffic.



Version 1.2.00

Diagnosing Fiber Performance IssuesEach external data port is represented by a Fiber Port instance. The parameters of this class provide anin-depth picture of the traffic on each fiber link. This will notably help administrators identify which portor which type of traffic (open systems, mainframes, etc.) constitutes a bottleneck or diagnose 'multi-pathing' issues.

There are several groups of parameters for each instance of the SEN_I68_FCPORT class that representthe different types of traffic on the port:

ECDK-prefixed parameters for mainframe traffic

PPRC-prefixed parameters for unit to unit replication traffic

SCSI-prefixed parameters for open system traffic (standard SCSI over fiber channel traffic)

To report on the traffic of each port, it is recommended to start looking at the Total-prefixedparameters (notably TotalReceivedByteRate and TotalSentByteRate). If these parameters show abottleneck, the other parameters will help identify the type of traffic that is causing this performanceissue.

Generating a fiber port activity report

1. Click the specific Fiber Port icon > KM Commands > Fiber Port Activity

2. Select the Total received/sent byte traffic parameter






Version 1.2.00

Diagnosing a Bad Physical Disk LayoutA non-optimal physical disk layout can cause an array of physical disks to become the bottleneck of aSAN. To verify that the I/Os are well-balanced across all arrays and ranks you can check the ReadByteRate and WriteByteRate parameters as well as the ReadResponseTime andWriteResponseTime of each rank and make sure they have similar average values.

Verifying the activity on physical disks

1. In the console, right-click the KM icon > KM Commands > Reporting > Volumes Activity

2. Select the volume read/write bytes traffic parameter



4. Press the Volumes Selection button to select the specific volume(s) you wish to include in thereport. By default all the monitored volumes are included in the report.

The Volume selection option is only available when at least two volumes are monitored.



Version 1.2.00

Verifying physical disks response time

1. In the console, double-click the DiskReadResponseTime parameter of the storage unit you areinterested in. A graph is automatically displayed in the graph pane.

2. Drag the DiskWriteResponseTime parameter of the same storage unit in the graph.

Selecting Graph's Param eters

Search WWNEvery component is uniquely identified on the SAN with an obfuscated series of letters and digits calleda World Wide Name (WWN): logical drives, arrays, servers, etc. Retrieving a device corresponding to aWWN found in error log or any other administration GUI may easily become a painful task for SANadministrators. The Search WWN feature has been designed to facilitate the retrieval of anycomponent based on its complete or partial WWN.



Version 1.2.00

1. In the console, click the KM Icon > KM Commands > Search WWN.

2. Select a search option, Contains, Start with, or Ends with.

3. Type the value to search for.

Search WWN Setting Panel

4. Click Search to display the search results

Search WWN Results

5. The search results panel lists the WWN corresponding to the search options you have defined.



Version 1.2.00

ReportingThis section deals with the various reports the IBM DS6000, DS8000 Series KM for PATROL enables youto generate based on the data collected from monitored devices. Reports are available for:

Storage Units

Fiber Ports

Ranks Activity

Volumes

To help administrators manage their IT infrastructure, IBM DS6000, DS8000 Series KM for PATROL alsoprovides the LUNs Mapping Table report related to LUNs

Two reports gather information about the volume of storage allocated per hosts and LUNs:

Per Host Storage Allocation

Per LUN Storage Allocation

Finally, administrators can schedule Activity and LUNs Mapping Table reports.

To generate a report, right-click the KM icon or the component instance > KM Commands >Reporting and then the report you wish to obtain.

Storage Units Activity ReportIBM DS6000, DS8000 Series KM for PATROL enables you to generate a report for one or several of themonitored subsystems:

1. Click the KM main icon > KM Commands > Reporting > Storage Units Activity Report



Version 1.2.00



read byte traffic,


read/write byte traffic.


4. Select the specific storage unit(s) you wish to include in the report. By default all the monitoredstorage units are included in the report.

The Storage Unit selection option is only available when at least two storage units are monitored.


Ranks Activity ReportIBM DS6000, DS8000 Series KM for PATROL enables you to generate a report for one or several of themonitored ranks:

1. Click the KM main icon > KM Commands > Reporting > Ranks Activity



read byte traffic,


read/write byte traffic.


4. Press the Ranks Selection button and select the specific rank(s) you wish to include in the report


You can generate a report directly from a specific rank:



Version 1.2.00

1. Right-click the Rank icon > KM Commands > Rank Activity.

2. Select the parameter for which you wish to generate a report for:

read bytes traffic

write bytes traffic

read/write bytes traffic



Fiber Ports Activity ReportIBM DS6000, DS8000 Series KM for PATROL enables you to generate a report for one or several of themonitored fiber port:

1. Click the KM main icon > KM Commands > Reporting > Fiber Ports Activity



ECKD read byte traffic,

ECKD write byte traffic,

ECKD read/write byte traffic,

PPRC received byte traffic,

PPRC sent byte traffic,

PPRC received/sent byte traffic,

SCSI read byte traffic,

SCSI write byte traffic,

SCSI read/write byte traffic,

Total sent byte traffic,

Total received byte traffic, or

Total received/sent byte traffic.



Version 1.2.00


4. Press the Fiber Ports Selection button and select the specific Fiber Port(s) you wish to include inthe report


You can generate a report directly from a specific fiber port:

1. Click the Fiber Port icon > KM Commands > Fiber Port Activity.



Volumes Activity ReportIBM DS6000, DS8000 Series KM for PATROL enables you to generate a report for one or several of themonitored volumes:

1. In the console, right-click the KM main icon > KM Commands > Reporting > VolumesActivity



disk read byte traffic,

disk write byte traffic,

disk read/write bytes traffic

volume read byte traffic

volume write byte traffic

volume read/write bytes traffic.



Version 1.2.00


4. Press the Volumes Selection button and select the specific volume(s) you wish to include in thereport


You can generate a report directly from a specific volume:

1. Right-click the Volume icon > KM Commands > Volume Activity.

2. Select the parameter for which you wish to generate a report for:

disk read byte traffic,

disk write byte traffic,

disk read/write bytes traffic

volume read byte traffic

volume write byte traffic

volume read/write bytes traffic.



LUNs Mapping TableIn order to facilitate the servers management, administrators can use the LUNs Mapping Table to list:mapped and/or not mapped LUNs.

1. In the console, right-click the KM main icon > KM Commands > Reporting > LUNs MappingTable

2. Define the setting of the list you wish to create

Table Param eters Settings

Select the type of logical drive you wish the list to display: Not mapped, mapped or all

Select the sorting order: Storage Unit, LUN, Size, Host Group, Host, Host WWN, FC Ports



Version 1.2.00

Select the format: Standard or CSV

3. Click Show Report to display a list of LUNs corresponding to your requirements

Per Host Storage AllocationThe Per Host Storage Allocation reports on the volume of storage allocated to each monitored host.

1. In the console, right-click the KM main icon > KM Commands > Reporting > Per Host StorageAllocation...

2. The report show the total amount of consumed and subscribed storage capacity for each monitoredhost.

Per Host Storage A llocation Report



Version 1.2.00

Per LUN Storage Allocation

The Per LUN Storage Allocation reports on the volume of storage allocated to each monitored LUN.

1. In the console, right-click the KM main icon > KM Commands > Reporting > Per LUN StorageAllocation...

2. The report show the total amount of consumed and subscribed storage capacity for each monitoredLUN.

Per LUN Storage A llocation Report

The list of results will be truncated in large env ironments if the buffer size is not sufficient to display all the LUNsavailable. Refer to the BMC documentation to know how to change the buffer size.

Scheduling ReportsAdministrators can schedule the production of activity reports and LUNs Mapping Table reports everyday at a specific time. The information retrieved as a text file can later be used by other tools such asBMC Capacity Optimization.

To schedule reports:



Version 1.2.00

1. Right-click the KM main icon > KM Commands > Reporting > Reports Scheduling. TheReports Scheduling wizard appears:

Scheduling Reports

2. Specify the time when the reports are automatically generated

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

Storage Units Activity: Reports on Read and Write Bytes for all the monitored subsystems

Fiber Ports Activity: Reports on ECKD, PPRC, and SCSI Read and Write Bytes and on TotalReceived and Sent Bytes for all monitored fiber ports

Ranks Activity: Reports on Read and Write Bytes for all monitored ranks.

Volumes Activity: Reports on Read and Write Bytes for all monitored disks and volumes.

4. Select LUNs Mapping Table to list mapped and unmapped LUNs

5. Click OK.

The generated file(s) are time-stamped and stored in %PATROL_HOME%/log for the specific time setthrough the History Retention Period parameter.

The history retention period can be set from the PATROL Console or from the PATROL Agent using a configurationvariable. The default collection (retention) period is one day . Whenever a stored parameter value exceeds itsretention period, it is automatically deleted from the parameter history file. Refer to BMC documentation for details.

98Administrative Tasks


Version 1.2.00

Administrative Tasks

This section deals with information on basic configuration and administrative tasks such as:

Configure Java settings

Customize the Discovery Cycle

Customize the Polling Interval

Enable the Debut Mode

Manage Internal KM Issues Notification

Manage Unknown Status

Pause the monitoring of a component

Resume the monitoring of a component

Reinitialize the KM

Restore Monitoring

Terminate the monitoring of a component

Trigger a KM Discovery

Configuring Java SettingsThe Java Settings wizard enables you to define which Java instance is to be used by IBM DS6000,DS8000 Series KM for PATROL (only when using the version lower than 3.6.0.11 of PATROL agent).

You can either use the automatic detection, select a pre-detected java path or enter manually the pathleading to the Java executable directory to be used.

The minimum version required is Java 1.5

To access the Java Settings wizard, right-click the main KM icon > KM commands > KM Settings >Java Settings.



Version 1.2.00

Jav a Settings Wizard — Method Selection

Select the Java executable detection method: Select one of the three following options:

Automatic: Select this option if you wish the KM to detect the Java executable directory by itselfupon each discovery.

User selection: Select this option if you wish to select a Java executable directory within a list ofpre-detected executables.

Manual: Select this option if you wish to manually enter the Java executable directory path.

Click Next to continue.

Automatic Detection

If you have selected the automatic detection at the previous step of the wizard, the KM displays the pathof the Java executable directory that will be used when performing commands requiring Java features.



Version 1.2.00

Jav a Settings Wizard — A utom atic Detection

If needed, specify a different Username and Password to run Java. Leave the fields blank to use thedefault PATROL account to run Java.

Click Finish to save your settings.

User Selection

If you have selected the user selection option at the previous step of the wizard, the KM displays a list ofall the Java executable directory found on your machine:



Version 1.2.00

Jav a Settings Wizard — User Selection

1. Select the Java executable directory you wish the KM to use when performing commands requiringJava features

2. If needed, specify a different Username and Password to run Java. Leave the fields blank to usethe default PATROL account to run Java

3. Click Finish to save your settings.

Manual

Jav a Settings Wizard — Manual Settings



Version 1.2.00

If you have selected the Manual option at the previous step of the wizard:

1. Enter the path to the Java executable directory you wish the application to use when performingcommands requiring Java features

2. If needed, specify a different Username and Password to run Java. Leave the fields blank to usethe default PATROL account to run Java

3. Click Finish to save your settings.

Once you have modified a java setting, you must restart the PATROL in order to make your changes.

Customizing the Discovery IntervalIBM DS6000, DS8000 Series KM for PATROL periodically performs discoveries to detect newcomponents in your monitored environment. By default, the KM runs a discovery every hour, but you cancustomize this interval by right-clicking the KM icon > KM Commands > KM Settings > DiscoveryInterval.

Custom izing the Discov ery Interv al



Version 1.2.00

Customizing the Polling IntervalA polling interval defines how often new data is collected. IBM DS6000, DS8000 Series KM for PATROLpolls the managed systems to collect performance and statistics data. By default, the polling interval forthis "data-collect" is set to 2 minutes.

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

To change the polling interval for the managed system, right-click the KM icon > KM Commands >KM Settings > Polling Interval…

Custom izing Polling Interv al

In addition to the polling interval that is a global setting, i.e. it is applicable to the whole managed system, you canalso manually trigger a poll at any time on indiv idual instances to refresh parameter values. Right-click the instanceicon > Refresh Parameters.

Enabling the Debug ModeBy default, IBM DS6000, DS8000 Series KM for PATROL sends only the most critical information,warning and error messages to the System Output Window of the PATROL Consoles. Most often, thisinformation is accurate enough to ensure that IBM DS6000, DS8000 Series KM for PATROL is workingproperly.



Version 1.2.00

If you encounter an issue and wish to report it to Sentry Software, you will be asked to enable theDebug Mode and provide the debug output to the Sentry Software support team.

To enable the debug mode:

1. Right-click the main IBM DS6000, DS8000 Series KM icon > KM Commands > KM Settings >Debug...

Enabling the Debug Mode

2. Check the Enable Debug Mode option

3. Indicate the date and time at which the system must stop logging debug information.. The requiredformat is: YYYY/mm/dd HH:MM:SS

4. Check the Reinitialize IBM DS6000, DS8000 Series for PATROL option (optional).

5. Click OK. The debug files will automatically be saved in $PATROL_HOME/log.

Managing Internal KM Issues NotificationsThis notification feature enables IBM DS6000, DS8000 Series KM for PATROL to notify you of anyinternal problems that may occur or of any special operations it may perform. The objective of thisnotification is to help resolve an issue (if any), other than hardware problems – which are reportedthrough the regular system of warnings and alerts. This feature is useful to find out more about anyanomalies that may occur.

By right clicking on the KM icon > KM Commands > KM Settings > Additional Settings >Internal KM Issues Notifications, you can set the kind of messages you would like to be notifiedabout:



Version 1.2.00

All internal messages

Only internal problems

No internal message

Internal KM Issues Notification

By default, all internal messages are sent to the System Output Window and are also registered asPATROL events (event ID "SentryI68Internal" of the SEN_I68_MAIN event catalog).

Internal errors are registered as events type "ERROR" (they appear in orange in PATROL Event Manager).Internal warnings are registered as "WARNING"Informational messages are registered as "INFORMATION".



Version 1.2.00

Managing Unknown StatusAt times, although rare, IBM DS6000, DS8000 Series KM for PATROL is unable to detect the status of amonitored device, and returns the poll with "Unknown Status".

When this situation occurs, you can configure the KM to perform specific actions:

Set the Status parameter to OK (default)

Ignore value and do not feed parameter

Trigger a WARNING on the Status parameter

Trigger an ALARM on the Status parameter

To access this feature, right-click the KM icon > KM Commands > KM Settings > AdditionalSettings > Unknown Status Management:

Unknown Status Managem ent

In addition to the selected actions, if you select the option to Trigger an Internal KM IssueNotification, an error message is displayed in the System Output Window of the PATROL console.

Pausing/Resuming MonitoringIn order to perform certain tasks (maintenance for example), it is often useful to pause the monitoringof an object or even of the whole system. To pause the monitoring of a specific component, right-clickthe component icon > KM Commands > Pause Monitoring.

When paused, the object/system is still displayed in the PATROL Console but displayed with an OFFLINEstatus. The collect for that particular object is no longer executed, and thus, no alert is longer triggered.



Version 1.2.00

To restart the monitoring of the object/system click Resume Monitoring in the menu.

Reinitializing the KMIf ever IBM DS6000, DS8000 Series KM for PATROL does not function properly (ex: display ofcomponents as missing while actually present or failure to detect several components as it should etc.),it is possible to reinitialize the configuration and let the KM re-start monitoring from scratch.

The above cases of malfunction could occur after a configuration change or especially after a software/hardware upgrade etc.

In such a case, you can reinitialize the KM, and the KM will then run a full discovery and re-start themonitoring of existing and new components. Thresholds will be set to default so all previously manuallyset thresholds will be lost, unless specified otherwise in the Reinitialize KM setting window shownbelow.



Version 1.2.00

1. To reinitialize IBM DS6000, DS8000 Series KM for PATROL: Right-click the KM Icon > KMCommands > Reinitialize KM

2. In the settings window, select the options according to your specific needs.

Setting the Reinitialize Options

Alert thresholds and actions

Remove manually customized alert thresholds and polling intervals: removes allcustomized thresholds and reset polling intervals to default.

Reset the threshold mechanism mode to default: makes the KM revert to the default modei.e. IBM DS6000, DS8000 Series KM for PATROL selects the mechanism that best suits thesystem.

Reset Alert Actions: removes all manually set Alert Actions and reverts to basic default actions



Version 1.2.00

i.e. Trigger a PATROL event and Annotate a parameter graph.

Reset other alert and threshold settings: reverts any manually done configuration changesto the default KM values.

Misc. options

Deactivate the debug mode: Selection deactivates the debug mode if manually enabled.

Restore and resume paused/removed objects: Selection restores all paused or removedobjects.

Remove Java Settings: Selection removes the custom Java Settings (path and credentials).The KM will try to automatically find a suitable JRE

Monitoring settings

Remove the connection settings: Selection discards the WBEM connection settings to the IBMStorage Manager.

Save reinitialize settings

Save reinitialize setting: Selection saves the defined settings that will then be considered asdefault.

In cases where configurations have been manually set in the PATROL Agent, there will be an additional section calledInternal KM engine options display ing the used configuration variables and the option whether or not to removethem.

3. Click Reinitialize.

Restoring MonitoringIt is possible to restore the monitoring of a device after it has been removed from the monitoringprocess through the Remove option.

To see the list of the removed objects or to restore the monitoring of a specific device:

1. Right-click the KM Icon > KM commands > KM Settings > Additional Settings > RestoreMonitoring...

Restore Monitoring

2. Select:

<All> if you want to restore the monitoring of all the devices that had been previously removed,in the PATROL Console

One or more objects if you only want to restore specific devices (press down the Ctrl-key to allowmultiple selection)



Version 1.2.00

3. Click Restore.

Removing Device MonitoringWhenever the supervision of a device becomes irrelevant, administrators can terminate its monitoringby right-clicking the device Icon > KM Commands > Remove.

The device icon is then removed from the Console and the data collection for this particular device willno longer be performed.

Triggering a KM DiscoveryIBM DS6000, DS8000 Series KM for PATROL automatically executes a discovery every hour of all IBMobjects for the monitored system. This enables discovering and then monitoring any new objects addedor removed etc.You can also force a discovery manually by right-clicking on the KM icon > KM Commands > Triggera KM Discovery.

With a v iew to optimization, the discovery process is as paralleled as possible. A ll independent objects are processedat the same time.

111Thresholds, Alerts and Notifications


Version 1.2.00

Thresholds, Alerts and Notifications

This section deals with thresholds, alerts and notification. Alert thresholds are dynamically set by IBMDS6000, DS8000 Series KM for PATROL. However, it is possible to change the settings, as well as thethreshold mechanism itself. The KM also offers you the possibility of selecting the type of notification(Alert actions) to be performed once an alert is raised.

Threshold Mechanism Selection

Alert Actions

Alert Actions Macros

Threshold Mechanism SelectionManaging thresholds means selecting/modifying the mechanism by which IBM DS6000, DS8000 SeriesKM for PATROL sets thresholds for all parameters of the monitored components. This is done throughthe menu command: KM Settings > Threshold Mechanism Selection.

By default, IBM DS6000, DS8000 Series KM for PATROL automatically sets alert thresholds on themonitored parameters.

The different threshold mechanisms

To set the thresholds, IBM DS6000, DS8000 Series KM for PATROL uses one of the following twomechanisms, best suited to the managed system:

Tuning: A standard internal PATROL mechanism, known as the Override parameters in PATROL butcalled Tuning in IBM DS6000, DS8000 Series KM for PATROL. With this mechanism, IBM DS6000,DS8000 Series KM for PATROL sets the thresholds of each parameter of each monitored object bysetting a specially formatted variable under the /___tuning___ tree in the PATROL Agentconfiguration.

Or

Event Management: PATROL for Event Management (formerly known as EventSpring)

By default, IBM DS6000, DS8000 Series KM for PATROL determines which of the above two mechanismsis best suited to the managed system and uses that. This is the Automatic setting in the ThresholdMechanism Selection wizard.

To see which mode is currently used for the system, or to modify the Automatic mechanism, right-click:the KM icon > KM Commands > KM Settings > Additional Settings > Threshold MechanismSelection...



Version 1.2.00

Threshold Mechanism Selection

Select one of the following options:

Automatic (default): the KM determines and uses the threshold mechanism best suited to themanaged system

Tuning: If selected, the KM will manage its thresholds through the standard the internal PATROLmechanism (Override parameters). Thresholds are stored in the PATROL Agent configuration underthe /___tuning___ tree.

Event Management: If this option is selected, the KM will manage its thresholds through theEvent Management mechanism. Thresholds are stored in the PATROL Agent configuration under the/AS tree. This option requires that you set up the PATROL for Event Management KM on yourPATROL Agent. PATROL for Event Management has to be enabled and preloaded.

If you use PATROL for Event Management to manage thresholds in PATROL, it is strongly recommended that you usethis option in IBM DS6000, DS8000 Series KM for PATROL too.

In order to avoid side effects and unpredictable behavior, if you change the threshold mechanism(from “Event Management” to “Tuning” or the other way around), the KM will automaticallyrecreate the default thresholds settings using the new threshold mechanism. Manually customizedthresholds however are not automatically migrated.

No Thresholds: the KM will not set any thresholds on the monitored objects. You are required toset them manually.

Modifying Alert ThresholdsWhenever possible, IBM DS6000, DS8000 Series KM automatically sets thresholds for parameters.These thresholds are retrieved from the information available from the hardware agents and they aregenerally accurate.

Generally, there is no need to modify these thresholds but in case IBM DS6000, DS8000 Series KMcannot obtain them, or if you prefer a more fault-tolerant monitoring, you can modify the thresholds ofeach parameter through the command menu.



Version 1.2.00

1. Right-click on the Extent Pool instance > KM Commands > Modify Alert Thresholds.

Modify A lert Thresholds — Selecting Mode

3. Select the alert threshold mode. Click Next to continue.

If you have selected the option Let IBM DS6000, DS8000 Series KM for PATROL setappropriate alert thresholds, the KM automatically determines and sets the alert thresholdsbest suited to the parameter/device/system. Click Next to view the threshold values and thenFinish to validate the operation.

If you have selected the option Manually customize alert thresholds, a panel is displayedallowing you to define new threshold values for the parameter/device/system. Click Finish tovalidate the operation.

If you select the Automatic thresholds mechanism option (see Managing the Threshold Mechanism), your customizedthresholds are stored in the PATROL Agent configuration and then can be modified. If the threshold mechanism is settuning, the threshold will be set under the /___tuning___ tree, while if the threshold mechanism is set tuning Event

Management, the thresholds will be set under the /AS tree.

Alert ActionsAlert Actions enables the PATROL administrator to choose specific actions to be executed when a failureis detected. With the Alert Actions, it is possible to either:

Customize the way a problem notification is performed, or

Specify a recovery action to be run when a problem occurs.

IBM DS6000, DS8000 Series KM for PATROL can be configured to run one, several, or all types of AlertActions when an alert is triggered regarding the monitored device.

By default, upon a failure, the KM triggers a PATROL event and annotates the parameter’s graph with acomprehensive report of the problem, giving details about the failure, the possible consequences andthe recommended action to solve the problem.

The Alert Actions that can be performed by IBM DS6000, DS8000 Series KM for PATROL are:



Version 1.2.00

Trigger a PATROL event

Annotate the parameter's graph

Execute an OS command

Execute a PSL command

Send a pop-up to the PATROL consoles

Write a line to a LOG file

Send a basic SNMP trap (using the PATROL MIB)

Send a custom SNMP trap

Send an E-mail

Alert Actions are highly customizable. One can customize the text that is sent through SNMP, set theusername/password that is used to execute the OS Command, define the content of the PATROL eventsent by IBM DS6000, DS8000 Series KM for PATROL, etc.

Additional information regarding the alert, such as the parameter name or its value, is available throughthe Alert Actions macros. This information can be used to further customize the Alert Action triggeredby IBM DS6000, DS8000 Series KM for PATROL and provide more details about the problem that occurs.

Alert Actions MacrosA macro is a variable whose value is replaced when an Alert Action is triggered. Macros can be used tocustomize the content of each Alert Action.

For example: %{VALUE} is replaced by the actual current value of the parameter that triggered thealert. When used in the text field for a PATROL event Alert Action, the percentage value is replaced bythe actual current value of the parameter that triggered the alert.

Each macro listed in the tables below contains information about what triggered the PATROL alert.

Macros Description

%{HOSTNAME} Name of the computer monitored with the PATROL Agent

%{PARAMETER_NAME}

Name of the parameter that triggered the alert

%{VALUE} Formatted value (with unit) of the parameter that triggered the alert

%{ALARM_TYPE} Type of alarm to be triggered

%{INFORMATION} Gets the status information from the IBM DS Storage Manager

%{OBJECT_ID} PATROL internal ID of the instance that triggered the alert

%{OBJECT_LABEL} Display name of the instance that triggered the alert

%{OBJECT_CLASS} Class of the instance that triggered the alert

%{PARENT_...} Gets the parent's object of a macro

%{PARENT_ID} PATROL internal ID of the object that the faulty instance is attached to

%{PARENT_LABEL} Display name of the object that the faulty instance is attached to

%{PARENT_CLASS} Class of the object that the faulty instance is attached to



Version 1.2.00

Macros Description

%{DATE} Current date in the YYYY-MM-dd format

%{TIME} Current time in the HH:MM:SS format

%{ASCTIME:…} Current date and time formatted as specified in the macro

%{/…} Recommended for advanced users only.Provides an internal instance variable name to be inserted. The path is relative to the objecttriggering the alert

%{NEWLINE} Linefeed. This is useful to produce multi-line information

Edit Alert ActionsTo modify the Alert Actions executed by IBM DS6000, DS8000 Series KM for PATROL upon a hardwarefailure, right-click on the KM icon > KM Commands > KM Settings > Alert Actions…

Select the Alert Actions to be executed

By default, IBM DS6000, DS8000 Series KM for PATROL triggers a PATROL event and annotates theparameter that raises the alert, but there are all the actions that can be triggered:

Editing A lert A ctions — Selecting Param eters

The available alert actions are:



Version 1.2.00

Trigger a PATROL event

Annotate the parameter's graph

Execute an OS command

Execute a PSL command

Send a pop-up to the PATROL Consoles

Write a line to a log file

Send a basic SNMP trap

Send a custom SNMP trap (advanced)

Send an e-mail

After selecting and defining Alert Actions, you need to validate your changes by clicking the Finishbutton.

Editing A lert A ctions — Validation



Version 1.2.00

Trigger a PATROL Event

If you select Trigger a PATROL Event, you need to enter the string that will be displayed with theevent.

Editing A lert A ctions — A lert A ction: Trigger a PA TROL Ev ent

A PATROL Event can be viewed from:

Standard PATROL Consoles (Classic Console, PATROL Central)

PATROL Enterprise Manager

BMC Impact Manager

Other third-party products that interface with PATROL.

The PATROL event that is triggered is the ‘41’ event from the standard PATROL catalog. You can use macros that willbe replaced at runtime. The A lert A ctions Macro Variables states the list of available macros.



Version 1.2.00

Annotate the Parameter’s Graph

If you select the Annotate the parameter’s graph action, you need to enter the string that will bedisplayed within the annotation point.

Editing A lert A ctions — A lert A ction: A nnotate Param eter's Graph

You can use macros that will be replaced at runtime. The A lert A ctions Macro Variables states the list of availablemacros.



Version 1.2.00

Execute an OS Command

If you select the Execute an OS command action:

Editing A lert A ctions — A lert A ction: Execute an OS Com m and

Enter a command line to be executed

Enter the username and password used to run the command.

The command can be a program utility or a script shell, and can have arguments.

The command must be non-interactive (no window, no user input)




Version 1.2.00

Execute a PSL Command

If you select the Execute a PSL command action, you need to enter the PSL statement to be executedby the PATROL Agent. Although only a single line is permitted, it can have several PSL instructions.

Editing A lert A ctions — A lert A ction: Execute a PSL Com m and

The PSL command is recommended for advanced user of PATROL.

You can use macros that will be replaced at runtime. The A lert A ctions Macro Variables section states the list of all theavailable macros.



Version 1.2.00

Send a Pop-up to the PATROL Consoles

If you select the Send a pop-up to the PATROL Consoles action, you need to enter the messagethat will be displayed in the pop-up as well as the in title of the pop-up window.

Editing A lert A ctions — A lert A ction: Send a Pop-up to the PA TROL Consoles

Too many pop-ups could annoy the operators.




Version 1.2.00

Write a Line to a LOG File

If you select the Write a line to a LOG file action:

Editing A lert A ctions — A lert A ction: Write a Line to a LOG File

Enter the LOG file path and the content of the line.




Version 1.2.00

Send a Basic SNMP Trap

If you select the Send a basic SNMP trap action:

Editing A lert A ctions — A lert A ction: Send a Basic SNMP Trap

Enter the following:

IP address or Hostname of the SNMP trap destination

SNMP port and community string

Text that will be sent in the SNMP trap

Upon a hardware failure, IBM DS6000, DS8000 Series KM for PATROL will send the trap that is defined in the PATROLMIB (Trap number 11, Enterprise ID: 1.3.6.1.4.1.1031.1.1.2, the tex t is stored in the 1.3.6.1.4.1.1031.1.1.2.1OID). You can use macros that will be replaced at runtime. The A lert A ctions Macro Variables section states the list ofavailable macros.



Version 1.2.00

Send a custom SNMP Trap (advanced)

If you select the Send a custom SNMP trap action, you need to enter the following:

Editing A lert A ctions — A lert A ction: Send a Custom SNMP Trap

Enter the following:

IP address or Hostname of the SNMP trap destination

SNMP port and community string

All the characteristics of the trap: Enterprise ID, trap number and up to 4 varbinds.



Version 1.2.00

Send an E-mail

If you select the Send an E-mail action, you need to complete the following panel:

A lert A ctions: Send an E-m ail

Enter the sender and the recipient email addresses in respectively the From and To fields, and type theSMTP server name. Finally, enter the email Subject and type the Body of the message you wish tosend.

Reference Guide

127


Version 1.2.00

Introduction

This chapter provides statistical information about resources, operating status, and performancesmanaged by the IBM DS6000, DS8000 Series KM for PATROL. It contains tables describing theparameters used in the KM, grouped by Application Classes, and provides a brief description of eachparameters and its default settings. Additionally, it contains a section dedicated to the KM configurationvariables that will prove useful to successfully implement the integration of the KM with a third party(BMC Event Management, BMC Capacity Optimization, Remedy, etc.).

128Classes and Parameters


Version 1.2.00

Classes and Parameters

This section lists the 12 application classes of IBM DS6000, DS8000 Series KM for PATROL. It gives youdetails on the icons that represent the class, Infobox, parameters and the menu commands available foreach application class. There are 7 main application classes and 5 “container” classes. The containerclasses have no parameters.

SEN_I68_MAIN

SEN_I68_EXTENTPOOL

SEN_I68_EXTENTPOOL_CONT

SEN_I68_RANK

SEN_I68_RANK_CONT

SEN_I68_FCPORT

SEN_I68_FCPORT_CONT

SEN_I68_STORAGEUNIT

SEN_I68_VOLUME

SEN_I68_VOLUME_CONT

SEN_I68_SMISPROVIDER

SEN_I68_SMISPROVIDER_CONT

Baselines and Key Performance Indicators

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

In this guide, parameters flagged as KPIs and included by default in the baseline calculation process arerespectively identified by the following icons:

Baselining

KPI



Version 1.2.00

SEN_I68_MAIN

Icon

Parameters

None.

InfoBox

Name Description

Product Name of the product.

Version Current version of the product.

Release Date Release date of the current version of the product.

Copyright Copyright information

Web site Web site address.

Support Support contact information.

Menu Commands

Function Description

Add a Connection to IBM DSStorage Manager

Enables you to add a subsystem to the monitored environment

Reporting > Storage UnitsActivity

Generates activity reports for the storage units.

Reporting > Fiber PortsActivity

Generates activity reports for the fiber ports.

Reporting > Ranks Activity Generates activity reports for the ranks.

Reporting > Volumes Activity Generates activity reports for the volumes.

Reporting > LUNs MappingTable

Generates a report listing mapped and unmapped LUNs.

Reporting > Per Host StorageAllocation

Generates a report on the volume of storage allocated to each monitored host.

Reporting > Per LUN StorageAllocation

Generates a report on the volume of storage allocated to each monitored LUN.

Reporting > ReportsScheduling

Schedules the production of activity reports and LUNs Mapping Table reports every dayat a specific time.

Search WWN Enables you to find any component based on its complete or partial World Wide Name.

KM Settings Displays all the command options for different monitoring settings



Version 1.2.00


KM Settings > Java Settings Enables you to define which Java instance is to be used by the KM.

KM Settings > DiscoveryInterval

Enables you to customize the discovery cycle. By default, discovery is performed everyhour

KM Settings > Polling Interval Enables you to customize the polling cycle. By default, the polling interval is done every2 minutes

KM Settings > Alert Actions Enables you to select the Alert Actions (different methods of notification) to beexecuted by the KM when a parameter breaches its threshold

KM Settings > AdditionalSettings

Enables you to perform additional settings such as restoring device monitoring,displaying settings for UNIX Console and enabling/disabling debug mode.

KM Settings > AdditionalSettings > ThresholdMechanism Selection

Allows you to select the threshold mechanism:

Automatic (by default): the KM determines the mode of threshold management bestsuited to the system. The different modes are:

Tuning: the KM uses the internal PATROL mechanism to set thresholds

Event Management: the KM automatically sets thresholds through the EventManagement

No thresholds: the KM does not set any thresholds and lets you specify themmanually.

KM Settings > AdditionalSettings > Unknown StatusManagement

Enables you to set actions to be performed when the KM is unable to detect the statusof a monitored device.

KM Settings > AdditionalSettings > Internal KM IssuesNotification

Allows you to enable/disable and select the type of information messages displayed byKM in the system output window of the PATROL Console.

KM Settings > AdditionalSettings > Restore Monitoring

Brings up the "Restore Monitoring" wizard to restore one or several objects after theirmonitoring has been stopped

KM Settings > Debug Activates or deactivates the debug mode. The debug Mode displays debug messages inthe PATROL System Output Window or saves it in a file if you enter the file path.

Trigger a KM Discovery Enables you to trigger a forced discovery and rediscover the hardware devices of themonitored system.

Pause All Pauses the monitoring of all currently monitored objects.

Resume All Resumes the monitoring of all objects after it has been paused.

Reinitialize KM Triggers a complete re-initialization of the KM. Customized settings are lost unlessspecified otherwise in the Reinitialize wizard.

About States basic product information and BMC Software support contact information.



Version 1.2.00

SEN_I68_EXTENTPOOL

Icon

Parameters

Name Description Units DefaultAlertConditions

Type

ConsumedCapacity Total size of the space actually allocated or reserved GB None Statistics

ConsumedCapacityPercentage

Percentage of the array that is actually allocated orreserved

% None Statistics

OperationRate I/O Throughput for the entire extent pool operations/s

None Statistics

SubscribedCapacity Sum of the subscribed capacity of each volume in theextent pool

GB None Statistics

SubscribedCapacityPercentage

Percentage of the subscribed capacity of each volumein the extent pool

% None Statistics

For detailed information about B a se lining and KP I, see Managing Baselines and Key Performance Indicators.

Infobox

Name Description

Extent Type Type of the Extent Pool to which the rank belongs

Pool ID Unique identifier for the Extent Pool

Ranks The Rank Group that this Extent Pool is assigned to. Valid values are 0 and 1.

Size Size of the Extent Pool

Menu Commands


Modify Alert Thresholds Allows you to modify the alert thresholds

Pause Monitoring Pauses the monitoring of the extent pool

Resume Monitoring Resumes the monitoring of the extent pool after it has been paused

Remove Removes the extent pool from the monitoring environment



Version 1.2.00

SEN_I68_EXTENTPOOL_CONT

Icon

Parameters

None.

Infobox

None.

Menu Commands


Pause Monitoring Pauses the extent pool monitoring

Resume Monitoring Resumes the extent pool monitoring after it has been paused




Version 1.2.00

SEN_I68_FCPORT

Icon

Parameters


Type

ECKDReadByteRate Accumulated time of ECKD read data onchannel

MB/s None Statistics

ECKDReadOperationRate Accumulated time of ECKD read Operationson channel

operation/s

None Statistics

ECKDWriteByteRate Accumulated time of ECKD write data onchannel


ECKDWriteOperationRate Accumulated time of ECKD writeOperations on channel

operation/s

None Statistics

PPRCReceivedByteRate Accumulated time of PPRC received dataon channel


PPRCReceivedOperationRate Accumulated time of PPRC receivedOperations on channel

operation/s

None Statistics

PPRCSentByteRate Accumulated time of PPRC sent data onchannel


PPRCSentOperationRate Accumulated time of PPRC sent Operationson channel

operation/s

None Statistics

ReadTimePercentage Percentage of read time % None Statistics

SCSIReadByteRate Accumulated time of SCSI read data onchannel


SCSIReadOperationRate Accumulated time of SCSI read Operationson channel

operation/s

None Statistics

SCSIWriteByteRate Accumulated time of SCSI write data onchannel


SCSIWriteOperationRate Accumulated time of SCSI write Operationson channel

operation/s

None Statistics

TotalReadOperationRate Total of time spent on read operations operation/s

None Statistics

TotalReceivedByteRate Total of received data on channel MB/s None Statistics

TotalSentByteRate Total of sent data on channel MB/s None Statistics

TotalWriteOperationRate Total of write operations on channel operation/s

None Statistics

WriteTimePercentage Percentage of write time on channel % None Statistics



Version 1.2.00


Infobox


WWN WWN of the fiber port

Menu Commands


Fiber Port Activity Enables you to generate an activity report for the fiber port

Pause Monitoring Pauses the monitoring of the fiber port

Resume Monitoring Resumes the monitoring of the fiber port




Version 1.2.00

SEN_I68_FCPORT_CONT

Icon

Parameters

None.

Infobox

None.

Menu Commands


Fiber PortsActivity

Generates activity reports for the all the monitored fiber ports

Pause Monitoring

Pauses the monitoring of all the fiber ports

ResumeMonitoring

Resumes the monitoring of all the fiber ports after it has been paused

Remove Removes all the fiber ports from the monitoring environment

SEN_I68_RANK

Icon

Parameters


Type

ReadByteRate Count of data read per second MB/s None Statistics

ReadOperationRate

Amount of read operation per second operations/s

None Statistics



Version 1.2.00

ReadOperationPercentage

Percentage of read operations % None Statistics

ReadResponseTime

Average time taken by the controller to complete readrequests during the polling period.

ms Alarm ≥ 20(After 5consecutiveoccurrences)

ResponseTime

WriteByteRate Amount of data written per second MB/s None Statistics

WriteOperationRate

Amount of write operation per second operations/s

None Statistics

WriteOperationPercentage

Percentage of write operations % None Statistics

WriteResponseTime

Average time taken by the controller to complete writerequests during the polling period.

ms Alarm ≥ 20(After 5consecutiveoccurrences)

ResponseTime


Infobox

Name Description

RAID Level Raid level of the rank

Size Total managed space

Extent Pool Extent Pool ID

Extent Type Type of the Extent Pool

Arrays Identifier of the array

Menu Commands


Rank Activity Generates an activity report for the rank

Pause Monitoring Pauses the monitoring of the rank

Resume Monitoring Resumes the monitoring of the rank after it has been paused

Remove Removes the rank from the monitoring environment



Version 1.2.00

SEN_I68_RANK_CONT

Icon

Parameters

None.

Infobox

None.

Menu Commands


Ranks Activity Generates activity reports for all the monitored ranks

Pause Monitoring Pauses the monitoring of all the monitored ranks

Resume Monitoring Resumes the monitoring of all the monitored ranks after they have been paused

Remove Removes all the monitored ranks from the monitoring environment



Version 1.2.00

SEN_I68_SMISPROVIDER

Icon

Parameters


Type

ManagedArrays Lists the disk arrays currently managed by the KM n/a None --

Status Status of the SMIS Provider {0= OK;1 =Degraded; 2=Failed}

Warning = 1Alarm = 2

CollectionStatus

StatusInformation Provides additional detailed information about theStatus parameter

n/a None --

Infobox

None.

Menu Commands


Edit ConnectionSettings

Enables you to modify the settings of the connection to the IBM Storage Manager

Pause Monitoring Pauses the monitoring of the rank

Resume Monitoring Resumes the monitoring of the rank after it has been paused

Remove Removes the rank from the monitoring environment

Refresh Parameters Refreshes all parameters of the application class



Version 1.2.00

SEN_I68_SMISPROVIDER_CONT

Icon

Parameters

None.

Infobox

None.

Menu Commands


Add a Connection toan IBM DS StorageManager

Enables you to add a subsystem to the monitored environment

Pause Monitoring Pauses the extent pool monitoring

Resume Monitoring Resumes the extent pool monitoring after it has been paused



Version 1.2.00

SEN_I68_STORAGEUNIT

Icon

Parameters


Type

AvailableCapacity Amount of storage capacity available for allocation TB None Statistics

OperationRate Amount of operation transmitted per second operations/s

None Statistics

ReadByteRate

Count of data read per second MB/s None Statistics

Status Status of the storage unit {0= OK; 1=Degraded;2= Failed}

Warning = 1Alarm = 2

Availability

SubscribedCapacity

Number of terabytes reserved in the storage unit TB None Statistics

WriteByteRate

Count of data written per second MB/s None Statistics


Infobox

Name Description

Internal ID Internal identifier of the storage unit

Controller 0 IPAddress

IP address of Controller 0

Controller 0 DNSName

DNS name of Controller 0

Controller 1 IPAddress

IP address of Controller 1

Controller 1 DNSName

DNS name of Controller 1

SMC IP Address IP address of the storage manager console

MTMS MTMS label that enables you to identify a specific storage unit

Machine Signature Signature of the storage unit

WWNN World Wide Node Name of the storage unit

Size Size of the storage unit



Version 1.2.00

Menu Commands


Reporting Enables you to generate activity reports for the storage unit

Search WWN Enables you to find any component based on its complete or partial World Wide Name

Pause Monitoring Pauses the monitoring of the storage unit

Resume Monitoring

Resumes the monitoring of the storage unit after it has been paused

Remove Removes the storage unit from the monitoring environment



Version 1.2.00

SEN_I68_VOLUME

Icon

Parameters

Name Description Unit Default AlertConditions

Type

CacheFastWriteHitRatio

Percentage of write operations that weresuccessfully served by the cache

% None Statistics

DASDFastWriteHitRatio

Percentage of write operations that weresuccessfully served by the DASD FastWrite cache

% None Statistics

DiskReadByteRate Amount of data read per second from thedisk


DiskReadOperationRate

Percentage of operations read per secondon the disk

operations/s

None Statistics

DiskReadResponseTime

Average time for a disk to complete a readrequest

ms Warning ≥ 20(After 5 consecutiveoccurrences)

ResponseTime

DiskTimeUtilization Percentage of disk time utilization % None Statistics

DiskWriteByteRate Amount of data written per second fromthe disk


DiskWriteOperationRate

Percentage of operations written persecond on the disk

operations/s

None Statistics

DiskWriteResponseTime

Average time for a disk to complete a writerequest

ms Warning ≥ 20(After 5 consecutiveoccurrences)

ResponseTime

TimeSinceLastActivity Number of days since any activity occurredon the volume

days None Statistics

VolumeReadByteRate

Amount of data read per second on thevolume


VolumeReadCacheHitRat

io

Percentage of read operations that weresuccessfully served by the cache on thevolume

% None Statistics

VolumeReadOperationRa

te

Percentage of operations read per secondon the volume

operations/s

None Statistics

VolumeReadResponseTi

me

Average time for a volume to complete aread request

ms Warning ≥ 10(After 5 consecutiveoccurrences)Alert ≥ 100(After 2 consecutiveoccurrences)

ResponseTime

VolumeWriteByteRate

Amount of data written per second on thevolume




Version 1.2.00

VolumeTimeUtilization Percentage of volume time utilization % None Statistics

VolumeWriteOperationR

ate

Percentage of operations written persecond on the volume

operations/s

None Statistics

VolumeWriteResponseTi

me

Average time for a volume to complete awrite request

ms Warning ≥ 10(After 5 consecutiveoccurrences)Alert ≥ 100(After 2 consecutiveoccurrences)

ResponseTime


Infobox

Name Description

RAID Level Level of the RAID

Hosts Hosts to which the volume is associated

Mapped Indicates if the volume is mapped or not

Menu Commands


Volume Activity Enables you to generate an activity report for the volume

Pause Monitoring Pauses the monitoring of the volume

Resume Monitoring Resumes the monitoring of the volume after it has been paused

Remove Removes the volume from the monitoring environment



Version 1.2.00

SEN_I68_VOLUME_CONT

Icon

Parameters

None.

Infobox

None.

Menu Commands


Reporting Generates activity reports for the volumes

Pause Monitoring Pauses the monitoring of the monitored volumes

ResumeMonitoring

Resumes the monitoring of the volumes after it has been paused

Remove Removes the volumes from the monitoring environment



Version 1.2.00

146Configuration Variables


Version 1.2.00

Configuration Variables

This section lists the configuration variables used by IBM DS6000, DS8000 Series KM for PATROL.Configuration variables are stored in the PATROL Agent configuration and can be managed through:

PATROL Configuration Manager (PCM)

Wpconfig.exe (Windows)

xpconfig (UNIX/Linux)

The following table recapitulates the global configuration variables used by the KM, i.e that apply to allof the monitored hosts. These configuration variables are stored under /SENTRY/SEN_68 in the PATROLAgent’s configuration.

Variable DefaultValue

Description

AlertActions n/a List of alert actions to be executed by the KM upon a hardware failure.Default: A PATROL event and an annotation on the parameter

collectionHubHeapSizeMax

n/a Maximum heap size in megabytes allocated to the Java Collection Hub.Default: Not set

collectionHubHeapSizeMin

n/a Minimum heap size in megabytes allocated to the Java Collection Hub.Default: Not set

collectionHubOverrideJavaCommandLine

n/a Command line used by the KM to launch the Java Collection Hub.Default: Not setThis variable should only be set if instructed by Sentry Support.

collectorLockTimeout

18000 Time in seconds during which the collect is locked and no other collect can beexecuted.Default: Not set

debugEndTime None Specifies when the debug mode will be disabled. Format required: YYYY/MM/DD HH:MM:SS

debugMode 0 When set to '1', enables the debug mode of the KM.Default: Not set

defaultReinitializationOptions

None List of default options to be executed by IBM DS6000, DS8000 Series KM forPATROL on reinitialization. The default values are: 0=unchecked; 1=checked

resetThresholds

resetThresholdManagementMode

resetAlertActions

resetOtherAlertSettings

resetDebugMode

resetRemovedPausedObjectList

resetReport

resetSecuritySettings

resetJavaSettings

Insert a colon “;” between the variable and its value: “resetThresholds;1”; and ifyou enter multiple variables, they need to be separated by a carriage return.Example: “resetThresholds;1” will display the remove thresholds option selected bydefault in the Reinitialize KM wizard.



Version 1.2.00

disableJavaInformationMessage

0 = activated When set to ‘1’, disables the pop-up information message displayed when the javasettings are modified.Default: Not set

disableJRECheck 0 = activated When set to '1', disabled the validation tests of the JRE used by the KM to runJava code and therefore force the KM to use a non-Sun or non-Oracle JRE.

disablePslExecuteBugWorkaround

0 = activated When set to ‘1’, deactivates the workaround in the KM for a bug in the PslExecute() PSL function. If the KM detects that the version of the PATROL Agent is affected by thePslExecute() bug, it uses an alternate technique to create asynchronous threadswith the event_trigger() function and the RemPsl standard event. ThedisablePslExecuteBugWorkaround variable disables this workaround.

discoveryLockTimeout

18000 Time in seconds during which the discovery is locked and no other discovery canbe executed. Default: Not set

exportActivityReports

None When set to 1, the SEN_I68_activity*.csv report is automatically generated andstored in the %PATROL_HOME%\log folder.

exportLUNsMappingTable

None When set to 1, the SEN_I68_LUNs_mapping_table*.csv report is automaticallygenerated and stored in the %PATROL_HOME%\log folder.

exportScheduling None Time when the activity and/or LUNs Mapping Table reports will be generated.Format required: HH:MM:SS

forceClassicConfigMode

0 = disabled When the KM is used with BMC ProactiveNet, all the KM configuration menus aredisabled in the PATROL Consoles. To enable them, set the forceClassicConfigModevariable to 1.

forceDiscoveryFromSMISProviderCollector

0 = disabled Set to '1' to force a discovery when the status of an SMI-S Provider changes. Bydefault, no discovery is performed in such case.

javaPassword None Password associated to the javaUsername variable.

javaPath None Path to the folder containing the Java executable used by the Collection Hub.Default: Net set (The KM will search for a suitable JRE automatically).

javaUsername None Username used to launch the Java Collection Hub.Default: Not set.

nameSpace root/ibm SMI-S Provider name space.

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

pemMessages all How much internal information should be sent as PATROL events.

When set to ‘all’, all internal KM messages (problems and informationalmessages).

When set to ‘problems’, only errors and problems.

When set to ‘none’, no internal message at all.

This doesn’t affect the reporting of actual hardware problems

Default: all

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

removedObjectList n/a List of instances that have been removed from the monitoring environmentthrough the Remove KM Command.

sowMessages all How much internal information should be displayed in the System Output Windowin the PATROL Console.

When set to ‘all’, all internal KM messages (problems and informationalmessages).



Version 1.2.00

When set to ‘problems’, only errors and problems.

When set to ‘none’, no internal message at all.

This doesn’t affect the reporting of actual hardware problems.Default: All

startupDelay 0 This variable allows the administrator to specify a number of seconds that the KMwill wait before starting its discovery. This variable may be useful on fast-bootingcomputers where the PATROL Agent starts before the IBM DS Storage Manager (ifany) and consequently triggers false.Default: Not set (zero)

staticThresholdsParameterList

n/a List of parameters for which custom thresholds have been set through the ModifyThresholds KM command.

tableJoinTimeout 18000 Timeout in seconds when performing a Table JoinDefault: Not set (assumed 60 seconds)

telnetConnectionMethod

swGetTelnetConnectionMethod()

Method used by the KM to perform telnet connections.Default (Windows): Java (if configured in the KM)Note: If the PATROL agent version is 3.6.011 or later the connection method usedby the KM is sopen; otherwise it is left blankDefault (UNIX): Telnet

ThresholdsManagementMode

swGetThresholdsManagementType()

Specifies how the KM should manage the alert thresholds on parameters. Pleaseread carefully the User Guide chapter for more information on this topic.Possible values:

'empty' (automatic detection of the suitable threshold management)

‘as’ (through PATROL for Event Management)

‘tuning’ (through the standard "Override parameter" mechanism)

‘none’ (No threshold is set by the KM)

unexpectedStatusInternalIssueNotification

None Specifies the action to be performed when the product is unable to interpret astatus value.Format: <alarm type>;<internal issue notification>.

Possible alarm type values:OKDEGRADEDFAILED

unexpectedStatusManagement

0 Specifies the action to be performed when the product is unable to interpret astatus value.Format: <alarm type>;<internal issue notification>Possible alarm type values:

ALARM

OK

WARN

Default: OK

Possible internal issue notification values:

1: trigger an internal issue notification

0: do not trigger an internal issue notification

wbemEncryption (1) 0 = Noencryption

Use of encryption when performing WBEM queries. Possible values are: '0' (no encryption), '1' (encrypt data).Note: The port usually used to encrypt data for WBEM queries is 5989.

wbemPassword None Password used to perform WBEM queries.

wbemPort 5988 Port used to perform WBEM queries.

WBEMQueryMode enumeration WBEM execution method.



Version 1.2.00

Possible values are: enumeration; association.

wbemTimeout None Timeout in seconds when performing a WBEM query.

wbemUsername None Username used to perform WBEM queries.

(1) This setting is only used if the SMI-S Prov ider specific configuration is empty .

Configuration variables specific to the DS Storage Manager are listed in the table below. Theseconfiguration variables are stored under /SENTRY/SEN_I68/<DS Storage Manager ID> in the PATROLAgent’s configuration.

Variable DefaultValue

Description

collectorLockTimeout 18000 Time in seconds during which the collect is locked and no other collect for the SMI-SProvider can be executed.

discoveryLockTimeout

18000 Time in seconds during which the discovery is locked and no other discovery forthe SMI-S Provider can be executed.

IBMDSStorageManagerHostname

n/a Hostname of the IBM DS Storage Manager server where the SMI-S Provider isrunning and where WBEM requests will be sent to.

nameSpace root/ibm Specifies a name space different from the one used by default to execute WBEMqueries.

wbemEncryption 0 = noencryption

Whether WBEM queries have to be encrypted using HTTPS or not.Possible values are: '0' (no encryption), '1' (encrypt data)Note: The port usually used to encrypt data for WBEM queries is 5989

wbemPassword n/a Encrypted password associated to wbemUsername (see below)

wbemPort 5988 Port used to perform WBEM queries

WBEMQueryMode enumeration WBEM execution method.Possible values are: enumeration; association

wbemTimeout 18000 Timeout when performing a WBEM query.

wbemUsername n/a Username used to connect to the IBM DS Storage Manager SMI-S Provider (a validuser on the IBM DS Storage Manager server).

Customer Support

151


Version 1.2.00

You can obtain technical support by using the Support page on the BMC Software Web site or bycontacting Customer Support by telephone or email. To expedite your inquiry, please see "BeforeContacting BMC Software."

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 email notices when new product versions are released

Find worldwide BMC Software support center locations and contact information, including emailaddresses, fax and telephone numbers

Support by Telephone or Email

In the United States and Canada, if you need technical support and do not have access to the Web, call800 537 1813. Outside the United States and Canada, please contact your local support center forassistance. To find telephone and email contact information for the BMC Software support center thatservices your location, refer to the Contact Customer Support section of the Support page on the BMCSoftware Web site at http://www.bmc.com/support_home.

Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Supportcan begin working on your problem immediately:

Product information

Product name

Product version (release number)

Operating system and environment information, machine type, operating system type, version, andservice pack or other maintenance level, such as:

PUT or PTF

system hardware configuration

serial numbers

related software (database, application, and communication) including type, version, and service

pack or maintenance

level

Sequence of events leading to the problem

Commands and options that you used

Messages received (and the time and date that you received them)

product error messages

messages from the operating system, such as "file system full"




152


Version 1.2.00

messages from related software

Index 153


Version 1.2.00

Index

- A -Abnormalities 61

Access

Logical Drives 82Activity

Overall 68

Report 69

Storage Unit 68

Total 69

View 68Activity Report 90

Adapter 50

Add 51, 59

Create 51

Update 59Add

Connection to an IBM DS Storage Manager 65

Alert

Actions 113Alert Actions

Annotate the Parameter’s Graph 118

Edit 115

Execute a PSL Command 120

Execute an OS Command 119

Send a Basic SNMP Trap 123

Send a custom SNMP trap 124

Send a Pop-up to the PATROL Consoles 121

Send an E-mail 125

Trigger a PATROL Event 117

Write a Line to a LOG File 122Alerts 111

Allocation

Per Host Storage 95

Per LUN Storage 96Application Classes 128

SEN_I68_EXTENTPOOL 73, 76, 131

SEN_I68_EXTENTPOOL_CONT 132

SEN_I68_FCPORT 86, 133

SEN_I68_FCPORT_CONT 135

SEN_I68_MAIN 129

SEN_I68_RANK 135

SEN_I68_RANK_CONT 137

SEN_I68_SMISPROVIDER 138

SEN_I68_SMISPROVIDER_CONT 139

SEN_I68_STORAGEUNIT 68, 76, 140

SEN_I68_VOLUME 70, 81, 83, 142

SEN_I68_VOLUME_CONT 144Architecture 12

- B -Baselines 128

BMC ProactiveNet Performance Management 61

Generation 61

Manage 61

Requirements 61BMC


BMC ProactiveNet Performance Management

Abnormalities 61

Baselines 61

Key Performance Indicators 61

KPI 61

- C -Check

Installation 24Command

Non-interactive 119

OS 119

PSL 120Commands

About 129

Add a Connection to an IBM DS StorageManager 139

Add a Connection to IBM DS Storage Manager 129

Additional Settings 129

Alert Actions 129

Debug 129

Discovery Interval 129

Edit Connection Settings 138

Fiber Port Activity 133

Fiber Ports Activity 129, 135

Internal KM Issues Notification 129

Java Settings 129

Index 154


Version 1.2.00

Commands

KM Settings 129

LUNs Mapping Table 129

Modify Alert Thresholds 131

Pause All 129

Pause Monitoring 131, 132, 133, 135, 137,138, 139, 140, 142, 144

Per Host Storage Allocation 129

Per LUN Storage Allocation 129

Polling Interval 129

Rank Activity 135

Ranks Activity 129, 137

Refresh Parameters 138

Reinitialize KM 129

Remove 131, 132, 133, 135, 137, 138, 140,142, 144

Reporting 129, 140, 144

Restore Monitoring 129

Resume All 129

Resume Monitoring 131, 132, 133, 135,137, 138, 139, 140, 142, 144

Search WWN 129, 140

Storage Units Activity 129

Threshold Mechanism Selection 129

Trigger a KM Discovery 129

Unknown Status Management 129

Volume Activity 142

Volumes Activity 129Configuration

Basic 98

Parameters 24

Port 20

Server Communication 24

SSL 20Configure

IBM DS600/ DS8000 Storage Manager 22Configuring

KM 65Connection

Add 65Connection Settings

Edit 67Consumption

Disk Space 73Customize

Discovery interval 102

Polling Interval 103

- D -Deactivate

Debug Mode 107Debug Mode

Deactivate 107

Enable 103Detection

Automatic 98

Manual 98

Selection 98Diagnose

Bad Physical Disk Layout 87Discovery

Trigger 110Discovery interval

Customize 102Disk

Layout 87Disk Space

Available 76DS Manager 20

- E -Edit

Connection Settings 67Enable

Debug Mode 103Execute

OS Command 119

PSL Command 120

- F -Fiber

Performance 86Fiber Activity 86

Fiber Port

Activity 92

- G -Generate

Baselines 61

Index 155


Version 1.2.00

- I -IBM

IBM CIM Agent for DS Open API 24

IBM DS Storage Manager 65, 67

IBM DS6000 Storage Manager 22

IBM DS8000 Storage Manager 22

IBM Storage Manager 20IBM DS6000 Storage Manager

Configure 22IBM DS6000/DS8000 Storage Manager

Installation 20IBM DS8000 Storage Manager

Configure 22InfoBox

Copyright 129

Product 129

Release Date 129

Support 129

Version 129

Web site 129Install 17

Introduction 28Installation

Check 24

IBM CIM Agent for DS Open API 24

IBM DS6000/DS8000 Storage Manager 20

Procedure 29Integration

BMC Portal 48, 49

BMC ProactiveNet Performance Management 48, 50

Integration Service Agent 51

Internal KM Issues Notifications 104

Issues

Fixed 8

Notifications 104

- J -Java settings 98

- K -Key Performance Indicators


Manage 61KPI 128


Manage 61

- L -Layout

Disk 87

Physical Disk 87Logical Drives

Access 82

Busiest 83LUNs

mapped 94

Mapping Table 94

Not mapped 94

Slow 81LUNs Mapping Table 77

- M -Macros

%{/…} 114

%{ALARM_TYPE} 114

%{ASCTIME:…} 114

%{DATE} 114

%{HOSTNAME} 114

%{NEWLINE} 114

%{OBJECT_CLASS} 114

%{OBJECT_ID} 114

%{OBJECT_LABEL} 114

%{OBJECT_TYPE} 114

%{PARAMETER_NAME} 114

%{PARENT_CLASS} 114

%{PARENT_ID} 114

%{PARENT_LABEL} 114

%{PARENT_TYPE} 114

%{PROBLEM} 114

%{TIME} 114

%{VALUE} 114Manage

Baselines 61

Key Performance Indicators 61

KPI 61

Notifications 104

Unknown Status 106

Index 156


Version 1.2.00

Modify

Alert Threshold 112Monitor Type 51

Monitoring

Caching Mechanism 70

Device 109, 110

Efficiency 70

IBM Storage Environment 68

Introduction 64

Pause 106

Resume 106

- N -New 8

Notifications 111

Issues 104

Manage 104

- P -Packages 18

Parameters 128

AvailableCapacity 140

CacheFastWriteHitRatio 70, 142

ConsumedCapacity 73, 131

ConsumedCapacityPercentage 73, 131

DASDFastWriteHitRatio 70, 142

DiskReadByteRate 83, 142

DiskReadOperationRate 142

DiskReadResponseTime 142

DiskTimeUtilization 142

DiskWriteByteRate 83, 142

DiskWriteOperationRate 142

DiskWriteResponseTime 142

ECDK 86

ECKD read byte traffic 92

ECKD read/write byte traffic 92

ECKD write byte traffic 92

ECKDReadByteRate 133

ECKDReadOperationRate 133

ECKDWriteByteRate 133

ECKDWriteOperationRate 133

ManagedArray 138

OperationRate 131, 140

PPRC 86

PPRC received byte traffic 92

PPRC received/sent byte traffic 92

PPRC sent byte traffic 92

PPRCReceivedByteRate 133

PPRCReceivedOperationRate 133

PPRCSentByteRate 133

PPRCSentOperationRate 133

read byte traffic 90, 91, 93

read/write byte traffic 90, 91, 93

ReadByteRate 68, 87, 135, 140

ReadOperationPercentage 135

ReadOperationRate 135

ReadResponseTime 81, 87, 135

ReadTimePercentage 133

ResponseTime 81

SCSI 86

SCSI read byte traffic 92

SCSI read/write byte traffic 92

SCSI write byte traffic 92

SCSIReadByteRate 133

SCSIReadOperationRate 133

SCSIWriteByteRate 133

SCSIWriteOperationRate 133

Status 138, 140

StatusInformation 138

SubscribedCapacity 131, 140

SubscribedCapacityPercentage 131

TimeSinceLastActivity 142

Total received byte traffic 92

Total received/sent byte traffic 92

Total sent byte traffic 92

TotalReadOperationRate 133

TotalReceivedByteRate 86, 133

TotalSentByteRate 86, 133

TotalWriteOperationRate 133

VolumeReadByteRate 83, 142

VolumeReadCacheHitRatio 70, 142

VolumeReadOperationRate 142

VolumeReadResponseTime 81, 142

VolumeTimeUtilization 142

VolumeWriteByteRate 83, 142

VolumeWriteOperationRate 142

VolumeWriteResponseTime 81, 142

write byte traffic 90, 91, 93

WriteByteRate 68, 87, 135, 140

WriteOperationPercentage 135

WriteOperationRate 135

WriteResponseTime 81, 87, 135

WriteTimePercentage 133PATROL

Agent 16, 17, 19, 49

Index 157


Version 1.2.00

PATROL

BMC Impact Manager 117

Central 19

Console 16, 17, 19, 49

Console Server 17

Consoles 121

Event 117

PATROL Configuration Manager 111

PATROL Console 70

PATROL Consoles 117

PATROL Enterprise Manager 117

PATROL Query 73

Query 70Pause

Monitoring 106Physical Disk

Layout 87Platforms

Linux 17

UNIX 17

UNIX/Linux 17

Windows 17Polling Interval

Customize 103Prerequisite 16

ProactiveNet 50, 51

Product at a glance 11

PW Commands 59

- Q -Query 70, 73

- R -Reference Guide 127

Reinitialize

KM 107Release Notes 8

Remove

Device Monitoring 110Report 90

Activity 69, 96

Available Disk Space 76

Fiber Port Activity 86, 92

LUNs Mapping Table 96

Rank Activity 91

Scheduling 96

Storage Units Activity 90

Volume Activity 93

Volumes Activity 87Reporting 90

Disk Space Consumption 73Restore

Monitoring 109Resume

Monitoring 106

- S -Scheduling

Report 96Search

WWN 88Setup Files

Extract 19SMCli 20

Status

Management 106

Unknown 106Support

Customer 151

Technical 151Supported Platforms

IBM DS 8000 series 13

IBM DS6000 series 13Systems

Linux 29

Unix 18

Windows 18, 29

- T -Task

Administrative 98Threshold

Mode 112

Modify 112Thresholds 111

Automatic 111

Customize 59

Import 59

Mechanism 111

PCM/Event Management 111

Remove 107

Reset 107

Index 158


Version 1.2.00

Thresholds 111

Selection 111

Tuning 111TimeSinceLastActivity 77

Trigger

KM Discovery 110

PATROL Event 117

- U -Uninstall

Procedure 41Unmapped LUNs 77

Utility

BMC Software Installation Utility 17

- V -Variables

AlertActions 146

collectionHubHeapSizeMax 146

collectionHubHeapSizeMin 146

collectionHubOverrideJavaCommandLine 146

collectorLockTimeout 146

debugEndTime 146

debugMode 146

defaultReinitializationOptions 146

disableJavaInformationMessage 146

disableJRECheck 146

disablePslExecuteBugWorkaround 146

discoveryLockTimeout 146

exportActivityReports 146

exportLUNsMappingTable 146

exportScheduling 146

forceClassicConfigMode 146

forceDiscoveryFromSMISProviderCollector1 146

IBMDSStorageManagerHostname 146

javaPassword 146

javaPath 146

javaUsername 146

nameSpace 146

pausedObjectList 146

pemMessages 146

psCommand 146

removedObjectList 146

sowMessages 146

startupDelay 146

staticThresholdsParameterList 146

tableJoinTimeout 146

telnetConnectionMethod 146

ThresholdsManagementMode 146

unexpectedStatusInternalIssueNotification 146

unexpectedStatusManagement 146

wbemEncryption 146

wbemPassword 146

wbemPort 146

WBEMQueryMode 146

wbemTimeout 146

wbemUsername 146View

Overall Activity 68

- W -WWN 94

Search 88

About BMC® SoftwareBMC Software, Inc. NYSE:BMC, is a leading provider of enterprise managementsolutions that empower companies to manage their IT infrastructure from abusiness perspective. Delivering Business Service Management, BMC Softwaresolutions span enterprise systems, applications, databases, and servicemanagement. Founded in 1980, BMC Software has offices worldwide and fiscal2004 revenues of more than $1.4 billion. For more information about BMC

Software, visit www.bmc.com.

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software,provides key monitoring solutions specifically designed to expand thecapabilities of BMC Performance Manager, thus enabling up to 100% coverage ofany infrastructure. Sentry Software specializes in single solutions for multi-platform monitoring of hardware, custom applications or any IT component, andblackout windows. Sentry Software products are deployed in 45 countries acrossthe globe and lead the list of BMC Software’s third-party product sales. For more

information about Sentry Software, please visit www.sentrysoftware.net.

ibm ds6000, ds8000 series km for patrol 1.2 · ibm ds6000, ds8000 series km for patrol version...

Documents