BMC ProactiveNet - Tivoli Storage Manager Monitoring v2.7 · PDF fileIBM Tivoli Storage...

BMC ProactiveNet PerformanceManagement - Tivoli StorageManager Monitoring

STORAGE MONITORING

USER DOCUMENTATION

Version 2.7.02

September 2015

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

http://www.sentrysoftware.com

Contacting BMC Software

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

United States and Canada

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

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

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

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

All other trademarks belong to their respective companies.

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

Restricted Rights Legend

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

2

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Customer Support

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

Support Web Site

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

Read overviews about support services and programs that BMC Software offers

Find the most current information about BMC Software products

Search a database for problems similar to yours and possible solutions

Order or download product documentation

Report a problem or ask a question

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

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

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

Support by Telephone or E-mail

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

3

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

http://www.bmc.com/support_home


http://www.sentrysoftware.com


4

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

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

.....................................................................................................................................................................................10Business Value

.....................................................................................................................................................................................11Requirements

.......................................................................................................................................................................................11System Requirements

.......................................................................................................................................................................................11Software Requirements

.......................................................................................................................................................................................12Security Requirements

.....................................................................................................................................................................................19Adding Central Monitoring Administration Tags

.....................................................................................................................................................................................21Preparing for Installation

.....................................................................................................................................................................................22Creating a Component Installation Package

.....................................................................................................................................................................................24Editing a Component Installation Package

.....................................................................................................................................................................................25Downloading and Installing an Installation Package

.....................................................................................................................................................................................27Configuring General Settings

.......................................................................................................................................................................................28Managing Policies

.....................................................................................................................................................................................29Configuring Monitor Settings

.......................................................................................................................................................................................31Configuring Tivoli Storage Manager KM

......................................................................................................................................................................31Configuring the User Account

......................................................................................................................................................................34Enabling the Debug Mode

......................................................................................................................................................................38Configuring the Maximum Number of Instances

......................................................................................................................................................................41Configuring the Multi-Node Monitoring Mode

......................................................................................................................................................................46Configuring the TSM Server Discovery Overrides (Optional)

.......................................................................................................................................................................................50Filtering Elements to Monitor

.......................................................................................................................................................................................50Configuring the Log Scan Limit

.......................................................................................................................................................................................52Configuring Jobs

.......................................................................................................................................................................................53Configuring Mount Requests

.......................................................................................................................................................................................55Configuring Domains

.......................................................................................................................................................................................56Configuring Processes

.....................................................................................................................................................................................58Configuring Thresholds

.......................................................................................................................................................................................58Configuring Monitor Thresholds

.......................................................................................................................................................................................59Editing a Threshold Configuration

.......................................................................................................................................................................................59Deleting a Threshold Configuration

.....................................................................................................................................................................................60Using BMC ProactiveNet Performance Management

.......................................................................................................................................................................................60Navigating the BMC ProactiveNet Operations Console

5

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

.......................................................................................................................................................................................64Adding attributes to the graph

.......................................................................................................................................................................................64Viewing and manipulating attribute graphs

......................................................................................................................................................................65Viewing monitors for a device

.......................................................................................................................................................................................65Changing thresholds

.......................................................................................................................................................................................66Managing Baselines and Key Performance Indicators

.....................................................................................................................................................................................70Tivoli Storage Manager KM

.....................................................................................................................................................................................71TSM Automated Drive

.....................................................................................................................................................................................71TSM Automated Library

.....................................................................................................................................................................................72TSM Client

.....................................................................................................................................................................................73TSM Daemons

.....................................................................................................................................................................................73TSM Daemon

.....................................................................................................................................................................................74TSM Database

.....................................................................................................................................................................................77TSM Domain

.....................................................................................................................................................................................79TSM Domain Client Node

.....................................................................................................................................................................................79TSM Jobs

.....................................................................................................................................................................................81TSM Job

.....................................................................................................................................................................................83TSM Log

.....................................................................................................................................................................................84TSM Manual Drive

.....................................................................................................................................................................................84TSM Mount Request

.....................................................................................................................................................................................85TSM Process

.....................................................................................................................................................................................86TSM Storage Pool

Release Notes for v2.7.02

7

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

What's NewTSM-204: It is now possible to customize the TSM log scan limit from CMA.

TSM-248: Tivoli Storage Manager KM now supports Tivoli Storage Manager Server 7.1.x andTivoli Storage Manager Administrative Client 6.4.x and 7.1.x, as well as the two operatingsystems Solaris 11 and Windows 2012.

Changes and ImprovementsTSM-225: The KM Home Directory path can now be shared when multiple TSM instances aremonitored. The KM Temp Directory, KM Debug Directory and DSM Log paths must howeverremain different (see KB article “Monitoring Multiple IBM Tivoli Storage Manager ServerInstances (TSM)).

Fixed IssuesTSM-134: A configuration problem prevented the proper monitoring of different TSMinstances through different PATROL Agents on the same TSM server, causing the product tostop operating. A procedure is now available in the Knowledge Base of the Sentry’s Website that describes how to configure the monitoring solution in order to monitor multipleIBM Tivoli Storage Manager Server instances.

TSM-141: The Login Status attribute triggered false warning when errors from the JOB_TEXTcommand output occurred.

TSM-142: The product sometimes failed to trigger alerts for missing TSM daemons.

TSM-161 & TSM-168: When activated, the Daemon Collector Exec Time attribute was notappearing in the console under Daemons.

TSM-167: When monitoring multiple TSM instances using different PATROL Agents,dsmadmc interface hangs intermittently. The interface access is changed to lock acrossAgents to avoid simultaneous dsmadmc command executions.

TSM-179: Migration related attributes (Pool Space Migrated, Pool Space Migrated Percent &Pool Space Migration Elapsed) are not available for copy storage pools.

TSM-180: The monitoring solution would create unknown job instance (: @ <unknown>) attimes, with all offline attributes.

TSM-186: When upgrading the monitoring solution to version 2.7.01, custom log filters foralarm and warning were lost.

TSM-224: On Linux platforms, the commands were randomly corrupted and caused themonitoring solution to fail.

TSM-241: The product custom paths were lost when they were set through PCM and whenthe PATROL Agent was not restarted immediately after the update.

TSM-269: Due to a PATROL events limitation, the monitoring solution failed to trigger logevents when a large amount of errors were found in the TSM activity log.

TSM-285: The product failed to identify the creation error for PCM suppressed instances andcontinued running commands against it, affecting the collector performance.

http://www.sentrysoftware.com/kb/KB1136.asp



8

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

TSM-291: PATROL Agent was crashing when large actlogs were being processed. To solve thisissue, the TSM monitoring solution user related activity is no more processed in the actlog.As a consequence, the memory consumption has been reduced.

TSM-297: Tivoli Storage Manager KM failed to detect Node Status errors as configured in theCMA for Node Status Alarms and Node Status Warnings.

TSM-303: The Sudo configuration requirements have been updated in the SecurityRequirements chapter of the user documentation.

TSM-309: Old TSM jobs were not removed from the console if they were discovered ascompleted.

TSM-321: Full and incremental domain level backup summary attributes were not setcorrectly, preventing the product to properly monitor backups at the domain and nodelevels.

TSM-328: On Windows systems, if the PATROL Agent installation path contained spaces,scripts calls and output redirection commands failed.

TSM-329: The Login Status attribute was in warning due to an incorrect configuration variableused while checking the active cluster node.

TSM-330: The Microsoft Cluster active node was not properly detected when the monitoringsolution was operating in multi-node monitoring mode.

TSM-335: The main discovery cycle was irregular due to an asynchronous default discoveryinterval. It is now reduced to 30 seconds to avoid such irregularity.

Key Concepts

10

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

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

User Goals and Features

Business Value

Requirements

Note that for convenience and brevity, reference to BMC ProactiveNet Performance Management - TivoliStorage Manager Monitoring, may also be made as Tivoli Storage Manager KM.

User Goals and FeaturesTivoli Storage Manager KM enables you to monitor the following in your environment:

Jobs: size, duration, throughput, time elapsed since last backup, number of objects andstatus

Server and Storage Agent availability: status memory and CPU time consumption

Internal server processes: monitoring of database backups, data migration and spacereclamations

Server database and recovery logs: database and file system utilization, cache and bufferperformance, time elapsed since last backup and database reorganization, etc.

Storage pools: space utilization, status, capacity, logical occupancy, growth rates, etc.

Libraries and drives: number of available drives, status, and number of scratch volumesloaded, etc.

Client: working status

Business ValueBMC ProactiveNet Performance Management - Tivoli Storage Manager Monitoring providescurrent and historical information through a centralized console so you can easily view andmanage your entire Tivoli Storage Manager environment. The product collects and brings criticalperformance data and useful metrics into the BMC ProactiveNet Performance Managementenvironment and enables SAN Administrators to be warned whenever a problem occurs in theirTivoli Storage Manager environment.

BMC ProactiveNet Performance Management - Tivoli Storage Manager Monitoring:

11 Business Value

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Detects backup and restore errors

Ensures maximum data protection and maximum availability

Measures jobs progress

Helps diagnosing server problems

Analyzes trend

Detects disk or tapes space shortages

Ensures backups are successful

Helps identify bottlenecks and optimize backup domains.

RequirementsBefore installing the Tivoli Storage Manager KM, verify the:

software requirements

system requirements

security requirements.

System RequirementsOperating System Operating System Version

Sun® microsystems SolarisTM 8, 9, 10, 11

HP-UX 11.00, 11.11, 11iv2, 11iv3

IBM® AIXTM 5.1, 5.2, 5.3, 6.1

Red Hat® Linux® 7.2

Microsoft® Windows® 2003, 2008, 2008 R2, 2012

If the operating system is upgraded (or downgraded) at a later date, you will need to reload commands forthe Tivoli Storage Manager KM.

Software RequirementsThe Tivoli Storage Manager KM supports the following platforms:

Software Version

Tivoli Storage Manager Server 5.1.x, 5.2.x, 5.3.x, 5.4.x, 5.5.x, 6.1.x, 6.2.x, 6.3.x, 7.1.x

12Requirements

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Tivoli Storage Manager Administrative Client 5.1.x, 5.2.x, 5.3.x, 5.4.x, 5.5.x, 6.1.x, 6.2.x, 6.3.x, 6.4.x,7.1.x

BMC Software PATROL Agent 3.4.20, 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 9.x

BMC ProactiveNet Performance Manager 8.x, 8.5.x, 8.6.x, 9.x

BMC TrueSight Operations Management 10

If you're running the Tivoli Storage Manager KM on LINUX, or Microsoft Windows x64 managednodes, please verify these additional software requirements:

Purpose Software Version

When running Tivoli StorageManager KM on Linux managednodes

Korn shell binary (/bin/ksh) Any

When running Tivoli StorageManager KM on MicrosoftWindows x64 managed nodes

Reg.exe patch KB948698 (http://support.microsoft.com/kb/948698)

Any

The Microsoft Windows x64 Reg.exe patch, KB948698 is required to allow access to 64-bit registry keysfrom PATROL Agent. Access the above patch site f rom the managed node to obtain the correct patch forthat platform.

Security RequirementsA user account with administrative privileges must be configured in BMC PATROL to read andexecute Tivoli Storage Manager application programs and access file systems. Depending on theoperating systems used, several options will be available.

The following user accounts can be used:

On Unix platforms:

a root user

a non-root user, such as patrol, that has sudo privileges on Tivoli Storage Manager toexecute application programs and access file systems

a non-root account, such as patrol, configured in Tivoli Storage Manager application toadminister the Tivoli Storage Manager application.

On Windows platforms:

an administrator user

a non-administrator account, such as patrol, configured in Tivoli Storage Managerapplication to administer the Tivoli Storage Manager application.

The user login details are configured in the KM. The password is stored in the PATROL Agent in aDES encrypted format.

http://support.microsoft.com/kb/948698




13 Requirements

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

The encrypted password can be viewed by any user who has access to the PATROL Agent configurationvariables (pconfig). This user could then execute PSL statements using the encrypted password throughthe PATROL Console. This can be prevented by setting up an appropriate Access Control List (ACL) forusers. Please refer to the PATROL Agent Reference Manual for details on how to set up an ACL.

Access Permissions

The Tivoli Storage Manager KM user needs “read & execute” permission to executable andlibrary files under the paths listed below. The Tivoli Storage Manager installation path INSTALL_PATH, referenced below, is normally /usr/tivoli/tsm or /opt/tivoli/tsm (on Unix) orC:\Program Files\Tivoli\TSM (on Microsoft Windows).

Unix Microsoft Windows

INSTALL_PATH/client/ba/bin (or bin64) INSTALL_PATH\baclient

INSTALL_PATH/client/admin/bin INSTALL_PATH\Server

INSTALL_PATH/server/bin INSTALL_PATH\StorageAgent

INSTALL_PATH/StorageAgent/bin INSTALL_PATH\Server\tsmdiag

INSTALL_PATH/server/bin/tsmdiag INSTALL_PATH\StorageAgent\tsmdiag

INSTALL_PATH/StorageAgent/bin/tsmdiag/usr/lib C:\Windows\system32

If the KM is enabled to failover in a clustered environment, the login user needs executepermissions to the following cluster commands:

/opt/VRTSvcs/bin/hagrp (in Veritas Cluster Server)vxdctl (in Veritas Cluster File System)/usr/cluster/bin/clrg (in Oracle Solaris Cluster)C:\Windows\sysnative\cluster (in Microsoft Cluster)

The Tivoli Storage Manager KM includes some scripts which should be executable by the PATROLAgent user and the Tivoli Storage Manager KM user. These scripts are stored under KM_HOMEpath, normally PATROL_HOME/TSM.

To list all OS commands used by the Tivoli Storage Manager KM, execute the following PSL codefrom the PATROL Console, using PSL Task menu, after installing and loading the KM.

i=0; sudoers="";

foreach var (grep("^/Runtime/TSM/CommandControls/",pconfig("LIST")))

{

ctl=get(var);

opt=ntharg(grep("Option",ctl),"2-"," =");

nsa=ntharg(grep("NoSudoAttempt",ctl),"2-"," =");

sua=ntharg(grep("SingleUserAttempt",ctl),"2-"," =");

typ=ntharg(grep("CommandType",ctl),"2-"," =");

cmd=nthargf(grep("CommandText",ctl),"2-","=","=");

14Requirements

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

if((typ == "")||(typ == "OS"))

{

met="";

if(opt == "NoLogin") { met = "(run as patrol user)"; }

elsif(nsa == "YES") { met = "(run as configured user without sudo)"; }

elsif(sua == "YES") { met = "(run as supplied user - used in menu)"; }

else

{

scmd=cmd;

s=index(scmd,"%sudo");

if(s) { scmd=replace(substr(scmd,s,length(scmd)),"%sudo",""); }

sudoers=union(sudoers,ntharg(ntharg(scmd,1,"|"),"1-"," "," "));

}

printf("(%2d) %-30s %-40s: %s\n",i++,ntharg(var,"5","/"),met,cmd);

}

}

printf("\n\nCommands used with sudo:\n%s",sort(sudoers));

The PATROL Agent user (normally patrol) requires write permission to DSM_LOG directory anddsmerror.log file. For all other paths and files listed in the table below the PATROL Agent userneeds “read & execute” permission.

Unix Microsoft Windows

DSM_DIR (INSTALL_PATH/client/ba/bin or bin64) DSM_DIR (INSTALL_PATH\baclient)

DSM_LOG (KM_TEMP) DSM_LOG (KM_TEMP)

DSM_DIR/dsmadmc DSM_DIR\dsmadmc.exe

DSM_CONFIG (DSM_DIR/dsm.opt) DSM_CONFIG (DSM_DIR/dsm.opt)

If a monitored log file cannot be read by the PATROL Agent user, it will copied to KM_HOME path usingthe configured KM login account, and processed by the PATROL Agent user. On completion the copiedlog file will be removed. This may increase the file system usage under KM_HOME temporarily duringthis activity.

On Windows platforms the Tivoli Storage Manager installation is identified by checking theregistry sub-keys under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\.

The configured login user should have sufficient privileges to run regedit command on themanaged node.

Sudo User for Operating System Access

If a non-root user with sudo privileges is preferred as the Tivoli Storage Manager KM user,configure the account as a sudoer through the visudo utility using code appropriate for yourplatform as detailed below. This user should be able to execute TSM commands and OS

15 Requirements

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

commands.

The code below also applies to all non-root users who may execute Tivoli Storage Manager KMadministration and report menu commands using their sudo privileges. The Tivoli StorageManager KM accepts any non-root user with the following sudo configuration in the sudoers file.Please replace user1, user2, user3 with appropriate KM user name. The Tivoli Storage Managerinstallation path INSTALL_PATH, referenced below is normally /usr/tivoli/tsm or /opt/tivoli/tsmand PATROL_HOME is the path where the PATROL Agent is installed (including the target, like /opt/bmc/Patrol3/Solaris29-sun4/).

This non-root sudo user configured in the KM will be able to execute Tivoli Storage Manager commands.To prevent unauthorized access, ensure this user is only used within the KM and not made public forgeneral use.

Entering the non-root sudo user with ‘Use Sudo’ option selected in to the login configuration dialog,before updating the sudoers file, will generate sudo errors. Also if the sudo user is configureddifferently, the KM may run sudo commands using incorrect sudo settings, which may expose the sudouser password.

On Solaris:

User_Alias TSMKMUSERS = user1, user2, user3

Defaults:TSMKMUSERS !lecture,!authenticate,!requiretty,\

env_keep+="PATH LD_LIBRARY_PATH INSTALL_PATH KM_HOME KM_TEMP",env_reset

KM_TEMP DSM_CONFIG DSM_DIR DSM_LOG",env_reset

TSMKMUSERS ALL=/bin/*,/sbin/*,/usr/bin/*,/usr/sbin/*,\

INSTALL_PATH/server/bin/*,\

INSTALL_PATH/client/ba/bin/*,\

PATROL_HOME/lib/TSM/*,PATROL_HOME/bin/*

user1, user2, user3 must be replaced with username(s) used by the KM; INSTALL_PATH andPATROL_HOME with the relevant paths.

On HP-UX:



env_keep+="PATH SHLIB_PATH INSTALL_PATH KM_HOME KM_TEMP",env_reset







On AIX & Linux:

16Requirements

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02



env_keep+="PATH LIBPATH INSTALL_PATH KM_HOME KM_TEMP",env_reset







Admin Interface User Access

BMC ProactiveNet Performance Management - Tivoli Storage Manager Monitoring requires thatan administrator account (standard administrator with no other privileges) be added to the TivoliStorage Manager server for use by PATROL and the Tivoli Storage Manager KM.

This account is used to query the configuration details and resource utilization of the serverthrough the Tivoli Storage Manager Administrative Client interface (DSMADMC). No changes aremade by this user on the Tivoli Storage Manager server - the Tivoli Storage Manager KM operatesin “read-only” mode for normal operation.

The suggested name for this DSMADMC user account is patrol and it can be created as part of theconfiguration procedure described in Configuring the User Accounts. Alternatively, the useraccount can be set up directly in Tivoli Storage Manager, and the details simply entered duringKM configuration in the same way that the OS login details are entered. The password is storedin the PATROL Agent in a DES encrypted format.

MADMC command binary is executed using an OS user account matching the the DSMADMClogin. If this account does not exists, the PATROL Agent user account will be used. Therefore it isrecommended to create an operating system user account matching the DSMADMC usernamewith the same password to avoid invalid user login attempts and to improve the performance.This user should be able to access required paths and binaries of DSMADMC. This includesexecute permission to DSM_CONFIG path and dsmadmc (or dsmadmc.exe) file and writepermission to DSM_LOG path and dsmerror.log file.

The encrypted password can be viewed by any user who has access to the PATROL Agentconfiguration variables (pconfig). This user could then execute PSL statements using theencrypted password through the PATROL Console. This can be prevented by setting up anappropriate Access Control List (ACL) for users. Please refer to the PATROL Agent ReferenceManual for details on how to set up an ACL.

To list all DSMADMC commands used by the Tivoli Storage Manager KM, execute the followingPSL code from the PATROL Console, using “PSL Task” menu, after installing and loading the KM.

i=0;

17 Requirements

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

foreach var (grep("^/Runtime/TSM/CommandControls/",pconfig("LIST")))

{

ctl=pconfig("GET", var);

typ=ntharg(grep("CommandType",ctl),"2-"," =");

cmd=nthargf(grep("CommandText",ctl),"2-","=","=");

if(typ == "DSMADMC")

{

printf("(%2d) %-25s: %s\n",i++,ntharg(var,"3","/"),cmd);

}

}

Planning

19 Adding Central Monitoring Administration Tags

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Adding Central MonitoringAdministration TagsAdding Central Monitoring Administration tags should be taken into consideration beforeinstallation.

A policy specifies a set of actions to be taken when a specific condition on the BMC PATROLAgent is fulfilled. A policy enables you to perform the following actions:

Apply specific configuration to one or more BMC PATROL Agents

Configure thresholds and set baselines on BMC ProactiveNet Child Servers

Each policy is assigned a BMC ProactiveNet Central Monitoring Administration tag and each BMCPATROL Agent can have one or more tags assigned to it. When you assign a tag to a BMC PATROLAgent the associated policy is applied to the PATROL Agent. You can assign the tag value of apolicy to a PATROL Agent in the following ways:

You can add a PATROL Agent and set the tag as part of the configuration process that youperform from Central Monitoring Administration. For details, see Managing downloads inCentral Monitoring Administration.

If the PATROL Agent has already been installed, use PATROL Configuration Manager to setthe following ruleset that provides the tags:/AgentSetup/Identification/Tags/TAG/tagName =tagDescription

For example if the tag which has to be applied is oracleTag, the ruleset is as follows/AgentSetup/Identification/Tags/TAG/oracleTag= “ORACLE MONITORING”

In BMC ProactiveNet version 9.0, the tag description is ignored, and only the tag name is used to evaluatethe policy.

Installing

21

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

The creation of the Tivoli Storage Manager KM installation package is performed directly fromBMC ProactiveNet Central Monitoring Administration. An installation package for a componentcan be downloaded and installed on several servers. The component installation package can beedited and saved under a new name.

With Central Monitoring Administration, administrators select monitor installation components,such as the BMC PATROL Agent and monitoring solutions, from a repository to create aninstallation package. The components can then be installed together using the installationpackage. Administrators can reuse the installation packages, or deploy the packages to multiplecomputers.

Preparing for InstallationThe BMC ProactiveNet Central Monitoring Repository is a requirement on the BMC ProactiveNetCentral Server where Central Monitoring Administration is enabled. The Central MonitoringRepository includes the current versions of BMC components that you can use with BMCProactiveNet.

After creating a component installation package, administrators can save the package to theMonitoring Installation Packages list for future use, or download the package on the current hostwithout saving the package. For saved packages, administrators can download and install thepackage on any host, or edit a package.

For supported 64-bit Linux versions, you must install the Linux runtime package, glibc.i686, version 2.3.4 orlater. Without the Linux runtime package, BMC ProactiveNet component installations might fail.

For further details regarding the BMC ProactiveNet Central Monitoring Administration, please refer to theBMC documentation.

22Creating a Component Installation Package

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Creating a Component InstallationPackageIf you want to import the entire repository, first download Central Monitoring Repository filesfrom the BMC Electronic Product Distribution (EPD) facility, or copy the files from yourinstallation kit, to the BMC ProactiveNet Central Server file system.

To import a single or custom solution1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and

select Manage Repository.

2. Click Import.

3. In the Import a New Solution dialog box, select Single solution or Custom solution.

4. Browse to a source file in one of the following formats: zip, tar, or tar.gz.The solution must be located on the local computer from which you are running the CentralMonitoring Administration web-based console.

5. (Custom solution, only) provide the following details:

Custom solutions name: The name of the custom solution, as it will be displayed in CentralMonitoring Administration.

Custom solution version: The version number for the custom solution. Values in the firsttwo version boxes are required.

6. Click Import.

The selected archive file is imported to the repository and extracted. You can close the windowduring the import process.

23 Creating a Component Installation Package

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

To create a component installation package1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and

select Monitoring Repository.

2. Click Add .

3. Select the operating system for which you want to create a package, and then select aplatform on which you want to install the package.The list of components in the repository that are supported on the specified operatingsystem and platform is displayed.

4. From the Available components list, select components that you want to include in thepackage.

5. From the Version list, select the version of the component that you want to include in thepackage.You can select a specific version or you can select latest, which automatically updates thepackage with the latest versions of the components when new versions of thosecomponents are added to the Central Monitoring Repository. By default, the appropriate BMC PATROL Agent for the operating system and platform thatyou chose is included in the Selected components list.

6. Click the right arrow button to move the selected components into the SelectedComponents list, and then click Next.The installation wizards for the products that you selected are displayed. They'll varydepending on the products or components that you selected to include in the package. Gothrough the wizards to complete the installation.

7. The Installation Package Details is displayed. Verify that the operating system and platformare correct for the type of package that you want to create. Also verify that the componentsthat you want to include are listed in the Included Components list. Provide the followinginformation:

Name: Enter a unique name for the package.

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

Format: Select a file compression format for the package.

8. Perform one or both of the following actions:

To save the package for future installation on the current host or other hosts, click SaveInstallation Package. The package is available in the Monitoring Installation Packages list.

To download the package immediately, click Download.

If you click Download and do not click Save Installation Package, the package is not saved in theMonitoring Installation Packages list for later use or editing.

9. When you are finished, click Close.

24Editing a Component Installation Package

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Editing a Component InstallationPackageYou can edit any part of an existing component installation package except the operating systemand platform.

1. In the navigation pane of Central Monitoring Administration, click the Repository drawer andselect Monitoring Repository.

2. (Optional) To filter the list of packages, select an operating system from the Filter byOperating System list.

3. Select the row for a package and click Edit .

4. From the Available components list, add or remove components, and click Next.

5. Perform one or more of the following actions, depending on your requirements:

Edit the installation details of existing components.

Add installation details for new components.

Click Finish Update to skip to the Installation Package Details window.

If you add a component to the package, you must complete the conf iguration process. The Finish Updatebutton shows an explanatory tooltip and does not skip to the Installation Package Details window.

6. In the Installation Package Details window, modify the following information as needed:

Name: To save your changes to the same package, do not change the name. To save thepackage under a unique name, change the name.

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

Format: Select a file compression format for the installation package.

7. Perform one or both of the following actions:

To save the package for future installation on the current host or other hosts, click SaveInstallation Package.The package is available through the Monitoring Installation Packages list.

To download the installation package immediately, click Download.

If you click Download and do not click Save Installation Package, the changes are not saved in theMonitoring Installation Packages list for later use or editing.

8. When you are finished, click Close.

25 Downloading and Installing an InstallationPackage

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

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

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

To download and install an installation package1. From the computer on which you want to install the package, log on to BMC ProactiveNet

Central Monitoring Administration.

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

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

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

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

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

(UNIX or Linux) RunSilentInstall.sh

(Microsoft Windows) RunSilentInstall.exe

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

If no policy matches the tags associated with the agent, the agent does not receive configurationinformation. The agent does not begin monitoring until a matching policy is created.

For further information regarding the Repository management, please refer to the BMC ProactiveNetCentral Monitoring Administration documentation.

Configuring After Installation

27

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

You configure monitoring of Tivoli Storage Manager KM when you create a policy. A policy is atemplate containing the configuration of a PATROL Agent. A policy can be assigned to one ormore PATROL Agents using a unique tag (Central Monitoring Administration tag), and a PATROLAgent can be assigned one or more policies with different priorities.

If you have not already added the Central Monitoring Administration tag to your PATROL Agentsduring the solution installation, then you must manually assign the tag after you have configuredthe policy. For details, see Adding Central Monitoring Administration Tags.

Configuring General SettingsThrough the General tab of the Add Policy dialog, you can create a new policy. A policy specifiesa set of actions to be taken when a specific condition on the PATROL Agent is fulfilled. First andforemost, actions include monitor configuration. Once a monitor is configured, policies can alsospecify threshold creation and the setting of baselines. A policy can also include intelligentserver-side thresholds so that IT administrators can immediately be alerted on potentialproblems.

Field Instructions

Name Enter a policy name. Policy names must be unique. In an environment with tenants, policy names must be unique for a single tenant

Tenant(For environmentswith tenants)

Select a tenant name. See Policies and tenants for details. Global indicates a policy applicable to all tenants.Provider indicates a policy applicable to the cloud service provider

Enable policy Select this option to enable the policy, or clear the option to disable the policy. Theoption is selected by default. If you clear the option, the policy and itsassociations remain intact, but the policy configuration is not applied until thepolicy is enabled again.

Precedence Enter a number from 0 to 999.

Description (Optional) Enter a policy description.

Tag Enter a Central Monitoring Administration tag.Policies are applied to BMC PATROL Agents with matching tags.Tags are case sensitive and cannot contain spaces or any of the followingcharacters: /, \, {, }, <, >, ‘, “, &.

Policy precedence

When more than one policy is applied to a BMC PATROL Agent and BMC ProactiveNet ChildServer, configuration is a union of every attribute defined by the policies. If a conflict arises (thatis, two policies configure the same attributes), it is resolved in one of the following ways:

28Configuring General Settings

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Policies with the same tag: If conflicting policies have the same tag, the precedence valuedetermines the order the policies are applied. The policy with the lower number value forprecedence is the policy from which the final configuration is applied.

Policies with different tags: If conflicting policies have different tags, then the policies areapplied according to the order they are listed on the BMC PATROL Agent. The policy listedlast on the agent is the policy from which the final configuration is applied.

Managing PoliciesThis topic provides general instructions for the following policy management tasks: editing,deleting, enabling and disabling.

Before you begin

Enable Central Monitoring Administration and log on to Central Monitoring Administration.Refer to the BMC documentation and more especially to the section Enabling and configuringCentral Monitoring Administration for details.

Policies with only threshold conf iguration or server side conf iguration are applicable only after a policywith monitor conf iguration is applied.

To edit a monitoring policy1. In the navigation pane of Central Monitoring Administration, click the Policies drawer and

select a policy view.

2. Select a policy and click Edit .

3. Edit the Configuring general settings of the policy.

4. Edit information on one or more of the following tabs:

Configuring monitor settings.

Configuring threshold settings.

5. Click Update.

To delete a monitoring policy

Deleting a policy deletes all monitor instances and most settings configured through the policy. Devicesremain in the User Groups to which they have been added.

29 Configuring General Settings

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

1. In the navigation pane of Central Monitoring Administration, click the Policies drawer andselect a policy view.

2. Select one or more policies and click Delete .

3. Click Yes to confirm deletion.

To enable or disable a monitoring policy

Enable or disable policies for maintenance and troubleshooting. When a policy is disabled, thepolicy and its associations remain intact, but the policy configuration is not applied until thepolicy is enabled again.


2. Select one or more policies and click Enable or Disable.

Configuring Monitor SettingsWhen you create or edit a policy, you can add and configure monitor types. The Add MonitorTypes dialog box presents configuration fields for compatible BMC PATROL monitoring solutionsthat are located in the Central Monitoring Repository. For a list of monitoring solutions that youcan configure through Central Monitoring Administration, see the Monitoring solutionsconf igurable through Central Monitoring Administration chapter in the BPPM onlinedocumentation.

For configuration details for a specific monitor type, see the monitor documentation. Toconfigure custom monitoring solutions through Central Monitoring Administration, ensure thesolution is structured correctly; for details, see the Building a PATROL Knowledge ModuleDevelopers Guide on BMC Support website.

To configure the Monitor Type settings using the Add Monitor Typesdialog box

To add a monitor type:


2. Click Add to display the Add Policy dialog box.

3. Configure the policy general settings.

4. Click the Monitor Configuration tab.

30Configuring Monitor Settings

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

5. Click Add

Adding Monitor Types

6. From the Solution menu, select Tivoli Storage Manager.

7. From the Version menu, select the required version.

8. From the Monitor Type menu, select the required monitor:

Monitor Type Description

Tivoli Storage Manager KM To set the general settings of Tivoli Storage Manager KM (credentials, debugmode, instances, multi-node mode, etc.)

TSM Automated Drive Enables access to the filtering options to select the automated driveselements that will be monitored.

31 Configuring Monitor Settings

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

TSM Automated Library Enables access to the filtering options to select the automated librarieselements that will be monitored.

TSM Client Enables access to the filtering options to select the clients elements that willbe monitored.

TSM Daemon Enables access to the filtering options to select the daemons elements thatwill be monitored.

TSM Domain To:enable access to the filtering options to select the domains elements thatwill be monitoredset backup restrictions.

TSM Domain Client Node Enables access to the filtering options to select the domain client nodeselements that will be monitored.

TSM Job To indicate:how long the jobs in OK, Suspicious, and Failure status will be monitored.the status the jobs will have when the monitoring period is over.

TSM Manual Drive Enables access to the filtering options to select the manual drives elementsthat will be monitored.

TSM Mount Request To indicate how long the mount requests will be monitored.

TSM Process To indicate how long the processes will be monitored.

TSM Storage Pool Enables access to the filtering options to select the storage pools elementsthat will be monitored.

Configuring Tivoli Storage Manager KMBefore using Tivoli Storage Manager KM, you'll have to configure its general settings. This sectionwill learn you how to:

configure the user account

enable the debug mode

configure the maximum number of instances

configure the multi-node monitoring mode

configure the TSM server discovery overrides (Optional).

Configuring the User AccountA user account with administrative privileges must be configured in BMC ProactiveNet to readand execute Tivoli Storage Manager application programs and file systems. Depending on theoperating systems used, several options will be available.

On Unix platforms, you can use the following user accounts:


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

a root user

a non-root user, such as patrol, that has sudo privileges on Tivoli Storage Manager to executeapplication programs and access file systems

a non-root account, such as patrol, configured in the Tivoli Storage Manager application toadminister the Tivoli Storage Manager application.

On Windows platforms, you can use the following user accounts:


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

an administrator user

a non-administrator account, such as patrol, configured in the Tivoli Storage Managerapplication to administer the Tivoli Storage Manager application.

To configure the user account1. Add or edit a monitor type

2. From the Monitor Type menu, select Tivoli Storage Manager KM


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

3. In the Hostname field, enter:

localhost to apply these settings to all PATROL Agents installed on the Tivoli StorageManager servers

a hostname or IP address to apply these settings to a specific server

3. Set the TSM Credentials:

To use the default PATROL Agent Account, check the Use Agent Default Account box

To use a different user account, enter the login details in the Username and Passwordfields

(Unix Only) If the user account has sudo privileges, check the Use Sudo box and indicatethe sudo binary file path (by default: /usr/local/bin/sudo)

5. Specify the TSM Admin Client User ID and Password

6. Indicate the DSMADMC path. By default, the KM discovers the DSMADMC binary path underthe default installation path.

7. Click the Advanced button if you need to configure:

the debug mode

the maximum number of instances

the multi-node monitoring mode

the TSM Server discovery overrides (Optional).

6. Click Add to List.

7. Click Update.

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

To enable the debug mode1. Edit a Tivoli Storage Manager KM monitor type:

In the navigation pane of Central Monitoring Administration, click the Policies drawer andselect a policy view

Select a policy and click Edit

In the Monitor Configuration tab, select Tivoli Storage Manager KM monitor type and clickEdit


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Editing the Tivoli Storage Manager Monitoring Settings


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

2. From the List - TSM Monitoring Settings, select the host or localhost

3. Click the Advanced button

Advanced Settings


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

4. Click the Debug button

Configuring the Debug Mode

5. Select all the elements for which you want to obtain debug information

6. In the Options section, indicate:

when the system must stop logging debug information. The required format is: YYYY/MM/DD HH:MM:SS

where the debug file will be stored. The default path is: <PATROL_HOME>/lib/TSM/debug

7. Click Close on all pop-ups

8. Click Modify Selection in the main window and click Update.

When the debug end time is reached, a tar/zip file is automatically created under <PATROL_HOME>/lib/TSM/ and can be sent to the BMC Support for help. It is also recommendedto check the TSM.log file, stored in <PATROL_HOME>/log, for any error.


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Configuring the Maximum Number of Instances1. Edit a Tivoli Storage Manager KM monitor type:



In the Monitor Configuration tab, select a Tivoli Storage Manager monitor type and clickEdit

Editing the Tivoli Storage Manager Monitoring Settings


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02



Advanced Settings


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

4. Click the Instance Max button

5. For each monitored element, indicate the maximum number of instances to be displayed

6. Enter 0 in the relevant field to disable the monitoring of a specific element




BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Configuring the Multi-Node Monitoring ModeIf the Tivoli Storage Manager environment is installed in a cluster using Veritas Cluster Server,Veritas Cluster File System, Oracle Solaris Cluster or Microsoft Cluster, Tivoli Storage ManagerKM must be installed on all the cluster nodes to enable continuous monitoring and avoid singlepoint of failure. To avoid duplicate alerts from multiple nodes, it is recommended to configurethe solution to operate in multi-node monitoring mode.

To configure the multi-node monitoring mode1. Edit a Tivoli Storage Manager KM monitor type:



In the Monitor Configuration tab, select Tivoli Storage Manager KM monitor type and clickEdit


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Editing the Tivoli Storage Manager KM Monitor Type


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02



Advanced Settings


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

4. Select Enable Multi-node Monitoring Mode and click the Multi-node M... button

Configuring Multi-node Mode

5. Configure the Multi-node Mode:

Select the appropriate Cluster Application.

Indicate the Failover Group Name. Leave this field blank if you previously selected VeritasCluster File System. Then the Tivoli Storage Manager KM will monitor the entire clusterfrom the active master system, which is identified by “vxdctl -c mode” command. Thismethod requires vxconfigd in enable mode with its clustered state active.

In the Monitoring Node Names field, name all the nodes where the solution is installed.The list must be delimited by commas.

6. (Optional) Allow the solution to check the monitoring mode of the remote PATROL Agents. Ifthe Remote PATROL Agent Checking is disabled, the solution will monitor actively throughactive TSM Server system or on the node where failover group is online and will not checkthe monitoring status of the other nodes through PATROL Agent:

Check the Enable Remote PATROL Agent Checking box.

Click the Remote Agent button


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Configuring the Remote Agent

In the Monitoring Node Name field, indicate the cluster node used for multi-node modefailover

Indicate all the information required to communicate with the remote PATROL Agent(protocol, port number, and credentials)

In the Number of Attempts field, indicate how many times the solution will try tocommunicate with the remote PATROL Agent before failing over

Enter the timeout between attempts

Click Add to List

Resume the procedure for all the nodes previously listed in step 5



Tivoli Storage Manager will then be monitored through the active or online node. The othernodes, which are standing by for a failover, will be in passive multi-node mode and only thelocal Tivoli Storage Manager components will be monitored.


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

If a managed node is unable to determine the system which should be in Active Multi-node Mode, it willchange to Temporary Single-node Mode.

Configuring the TSM Server Discovery Overrides (Optional)The solution automatically discovers the Tivoli Storage Manager installation path, the DSM_DIRand DSM_LOG directory paths, the DSM_CONFIG file path, the temporary directory path used bythe TSM KM, the node type, and the node status. This information can however be overridden.

To configure TSM server discovery overrides1. Edit a TSM KM monitor type:



In the Monitor Configuration tab, select a Tivoli Storage Manager KM monitor type andclick Edit


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Editing the Tivoli Storage Manager KM Monitor Type


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02



Advanced Settings

4. In the TSM Server Discovery Overrides section, indicate:

the TSM installation path

the DSM_DIR directory path

the DSM_CONFIG file path

the DSM_LOG directory path

the temporary directory path

the node type

the node status alarms and warnings


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02




BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Filtering Elements to MonitorBy default, the solution monitors all the elements discovered, which may represent animportant workload to the agents and the BPPM servers. Because the monitoring of someelements may be irrelevant for various reasons, you can apply filters to indicate which elementswill be monitored or not.

Filtering options are available for the following monitor types: TSM Automated Drive, TSMAutomated Library, TSM Client, TSM Daemon, TSM Domain, TSM Domain Client Node, TSMManual Drive, and TSM Storage Pool.

To filter elements to monitor1. Add or edit a monitor type

2. Select the Monitor Type for which you wish to apply filters.


localhost to apply these settings to all PATROL Agents installed on Tivoli Storage ManagerServers


4. Indicate which elements will be monitored:

Click the Filtering button

In the Keep Only... section, indicate the regular expression for the element to bemonitored and click Add to List

In the Exclude... section, indicate the regular expression for the element not to bemonitored and click Add To List

Resume procedure to keep and/or exclude as many elements as required

Click Close

5. If needed, manually add elements to be monitored:

Click the Manual Add button

Indicate the element to be monitored and click Add to List

Resume procedure to add as many elements as required

Click Close


7. Click Add.

8. Finally, Update the policy.

Configuring the Log Scan LimitBMC ProactiveNet Performance Management - Tivoli Storage Manager Monitoring scans log filesby reading the new log entries since the last data collection cycle. By default, only 500 KBytes ofdata is scanned for each log file during each data collection cycle. This log scan limit can howeverbe modified to better suit your requirements.


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Increasing the Log Scan Limit may impact the performance of the data collector (TSMLogCollector), themonitoring solution, and the PATROL Agent.

To customize the log scan limit1. Add or edit a monitor type

2. Select TSM Log from Monitor Type list to display the TSM Server Logs panel.

Configuring the Log Scan Limit


localhost to apply these settings to all PATROL Agents installed on TSM Servers


4. In the Log Scan Limit field, indicate the amount of data (in KBytes) that will be read by themonitoring solution during each data collection cycle.

5. In the Actlog Query Limit field, indicate the maximum query limit (in minutes).


7. Click Add.



BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Configuring JobsBy default, the Tivoli Storage Manager KM monitors all scheduled jobs that completedsuccessfully for 24 hours and any other scheduled job for 72 hours. This monitoring duration canhowever be modified to better suit your requirements.

Increasing the monitoring duration may affect the performance of the application.

To configure jobs1. Add or edit a monitor type and select TSM Job as a Monitor Type.

Configuring Tivoli Storage Manager Jobs


localhost to apply these settings to all PATROL Agents installed on Tivoli Storage Managerservers



BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

3. In the Monitoring Duration section:

Indicate how many hours the jobs in OK, Suspicious, and Failure status will be monitored

Uncheck Keep Monitoring Active Jobs Indefinitely if you prefer not to monitor active jobswhen their duration exceeds the monitoring duration set above

5. Click Add to List

6. Click Add.


Configuring Mount RequestsBy default, the Tivoli Storage Manager KM monitors all mount requests for 24 hours. Thismonitoring duration can however be modified to better suit your requirements.


To configure mount requests:

1. Add or edit a monitor type and select TSM Mount Request as a Monitor Type.

Configuring Mount Requests


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02




3. In the Mount Request Configuration section, indicate how many hours the mount requestswill be monitored


5. Click Add.


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Configuring DomainsTo Configure Domains:

1. � Add or edit a monitor type and select TSM Domain as a Monitor Type.

Configuring Domains





BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

3. Set the filtering options. Refer to Filtering Elements to Monitor for more details.

4. If you want a warning to be triggered when a backup is started during a specific period oftime, configure a backup restriction window:

Check the Enable Backup Restriction Window box

Indicate the Restriction Start and End Time. The format required is HH:MM:SS and therestriction window must at least last 5 minutes.

5. Click Add to list.

6. Click Add.

Configuring TSM ProcessesBy default, the Tivoli Storage Manager KM monitors all processes for 24 hours. This monitoringduration can however be modified to better suit your requirements.


To configure TSM processes:


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

1. Add or edit a monitor type and select TSM Process as a Monitor Type.

Configuring Mount Requests




3. In the Process Configuration section, indicate how many hours the processes will bemonitored


5. Click Add.

58Configuring Thresholds

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Configuring ThresholdsWhen you are creating or editing a policy, you can add and configure monitor thresholds. The Add Thresholds dialog box presents threshold configuration fields for BMC ProactiveNetmonitors that are configured through Central Monitoring Administration.

For details about baselines and Key Performance Indicators (KPI), see BMC ProactiveNet CentralMonitoring Administration or BMC ProactiveNet documentation or refer to the ManagingBaselines and Key Perf ormance Indicators section. For details about the monitored attributes,refer to the specific monitor type in the Ref erence Guide section.

Before you begin

Ensure that your monitor configuration is complete before thresholds are applied. Thresholdscannot be applied to monitors that are not configured through Central MonitoringAdministration. If you have not done so already, please refer to the section Configuring MonitorSettings.

Recommended Thresholds

Thresholds define acceptable high and/or low values for the data collected. Thresholds can becreated as part of a policy that can be applied to multiple monitor types on multiple BMC PATROLAgents. The Ref erence Guide provides a list of monitor types with their respective attributes and, whenmeaningful, a recommended threshold.

Configuring Monitor ThresholdsTo configure monitor thresholds:

1. Create a new policy or edit an existing one.

2. Select the Threshold Configuration tab and click Add .

3. In the Add Thresholds dialog box, select the relevant Solution, Version, and Monitor Type.

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

5. Select Match Device Name if you want the entire <deviceName>\<instanceName> string tobe considered.

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

7. In the Threshold section:

Select the threshold type.

Set the threshold parameters values.

59 Configuring Thresholds

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Click Add.

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

9. Click Close. The configuration details are displayed in the table on the ThresholdConfiguration tab.

10. Click Save at the bottom of the Add Policy dialog box, or Update at the bottom of the EditPolicy dialog box.

After you save or update the policy, new threshold configurations are pushed to BMC PATROLAgents with matching Central Monitoring Configuration tags.

Editing a Threshold ConfigurationTo edit a threshold configuration:

1. Edit an existing policy

2. On the Threshold Configuration tab, select a threshold definition, and click Edit.

3. Edit the configuration values and click Update.

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

5. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.

After you update the policy, updated threshold configurations are pushed to BMC PATROLAgents with matching Central Monitoring Configuration tags.

Deleting a Threshold ConfigurationTo delete a threshold configuration:

1. Edit an existing policy

2. On the Threshold Configuration tab, select attributes, monitor types, versions, or solutions.

3. Click Delete.

4. After you delete one or more threshold configurations, click Close.

5. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.

After you update the policy, deleted threshold configurations are removed from BMC PATROLAgents with matching Central Monitoring Configuration tags.

60Using BMC ProactiveNet Performance Management

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Using BMC ProactiveNet PerformanceManagementThis section provides a brief overview of how to navigate and use the product in the BMCProactiveNet Operations Console.

Navigating the BMC ProactiveNet Operations Console

Adding attributes to the graph

Viewing and manipulating attribute graphs

Viewing monitors for a device

Changing Thresholds

For more detailed information, see BMC ProactiveNet User Guide in the PDF product guides.

Navigating the BMC ProactiveNet OperationsConsoleThe BMC ProactiveNet Operations Console is a Web-based application that provides options tonavigate through BMC ProactiveNet and view all of the information collected and computed bythe BMC ProactiveNet Server related to events, views, and graphs.

Navigation tree

The navigation tree shows an at-a-glance synopsis of events and views. Event and componentfolders are displayed hierarchically and are divided into the following categories, or nodes.

Object Definition

Global node The Global node contains the following default collectors:All Event Collectors—displays the entire event collector hierarchyAll Abnormalities—displays all the abnormality eventsAll Services—displays all the servicesAll Groups—displays all the groupsAll Devices—displays all the devicesBased on permissions, users can create event and component folders under this node toorganize the event view.

My Foldernode

Based on permissions, users can create event and component folders under this node toorganize the event view.

To further organize your display, beneath these top-level folders you can add event andcomponent folders, including folders for Component Instances (CIs) associated with a service

61 Using BMC ProactiveNet Performance Management

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

model. Your ability to add event and component folders depends on your permissions.

The severity icons for a collector dynamically change depending on the severity level of theevents for that collector.

For example, if there is a Critical event on one of the devices, the green icon changes to a redicon, indicating a Critical event. The icons enable you to see the status of devices on your systemimmediately.

For complete details, see the BMC ProactiveNet Getting Started Guide on the BMC Supportwebsite.

Navigation drawers

The navigation pane in the Operations Console contains a series of drawers that enable you tonavigate through BMC ProactiveNet functions and views. You can select which drawers to displayin the navigation pane.

The following table describes the available drawers in the navigation pane and describes theirfunctions.

Drawer Description

Main Provides access to event lists and displays event information and status.

Other cells Lists available remote cells connected to the BMC ProactiveNet Server and monitoredby BMC ProactiveNet.

Reports Enables you to generate and manage reports based on data collected by BMCProactiveNet.Note: You must have permission to view this drawer.

Views & graphs Provides options for the management of views and graphs in the Operations Console

Bookmarks Enables you to view, rename, and delete bookmarks of objects and their related viewsthat you create in the navigation tree.

Find CI Provides a search mechanism so that you can search for Component Instances thatmeet the specified search criteria.Note: You must have permission to view this drawer.

Event and component folders

Event and component folders enable you to organize cells and collectors to make event displaysmeaningful for operators. For example, you might create an event folder for collectors thatgather database warning events and allow only operators who are database administratorsaccess to that event folder. You can drag components from one existing folder to another within


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

the top-level folders in the navigation tree. You also can drag and drop CIs from the Tile or Graphview to an existing folder in the All Services folder.

Event folders

An event folder is a grouping of collectors that shows the relationship of events or abnormalitiesthrough the hierarchy of the navigation tree. Administrators define event folders and associatethem with one or more collectors. Each level of the collector is shown as a node under the eventfolder. An event list is associated with the lowest level nodes of an event folder. The parentlevel of an event folder represents all of the events or abnormalities associated with thecollectors.

Event collectors

Event collectors gather events for display in an event list to provide operators with meaningfulgroups of events or abnormalities and to show relationship through the hierarchy of the nodes inthe navigation tree. To access the event list for a collector, operators click the collector node inthe navigation tree. Event collectors are dynamic or static. Nodes for dynamic collectors appearor disappear from the navigation tree based on whether or not events are present that meet thecriteria for those collectors. Nodes for static collectors remain in the navigation tree regardlessof whether events are present or not.

Component folders

A component folder is a grouping of groups, services, or devices from several different eventlists (collectors) that shows the relationship of groups, services, or devices through the hierarchyof the navigation tree. Administrators define component folders and associate them with one ormore groups, services, or devices. Each level of the component folder is shown as a node underthe parent component folder. An event list is associated with the lowest level nodes of acomponent folder. The parent level of a component folder represents all of the eventsassociated with the groups, services, or devices. Component folders are static or dynamic. Youpopulate static component folders by selecting from a list of objects. You populate dynamiccomponent folders by creating a query. Static folders always contain only the objects that youmanually select. Dynamic folders contain the objects that match the query, so the contents ofthese folders can change without further editing.

Operations Console views

The following table shows the different views that are available, depending on what object youselect in the navigation tree. Each view is accessed by clicking the associated Console view icon.If a view is not available for the object that is selected in the navigation tree, the icon for thatview is not displayed in the toolbar.


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

View Description

Event The Event view displays all events in an event list. This is the default view for all objects. Usethe Event view to check the details of events and to address events that highlight incorrectstate. Probable Cause Analysis can help you to identify the cause of the event. An event couldbe assigned to other users, who can acknowledge and take ownership of the event, fix theproblem, and close the event. You can also address the incorrect condition by invoking remoteactions, detailed diagnostics, and local actions. The Graph view helps check the impactingservice and you can cross-launch to Impact Model Designer, Service Level Manager andProduct Catalog in BMC Remedy IT Service Management (BMC Remedy ITSM).You can display an Event view for:

Event collectors

Abnormalities

Services

Groups

Devices

Monitors

Title The Canvas view enables you to create a graphical representation of the components that arebeing monitored in your environment. The components are represented by objects that you canplace on a background image. The objects can be graphics, such as images or connectors, ormetrics information represented in a tile.You can create and display a Canvas view for:

Event collectors

services

Groups

Devices

Tree/Graph

The Tree/Graph view displays information for a selected object as a tree that represents thehierarchy of the object. The Tree view is available for groups and services. You can use the Treeview to get a real-time, interactive visualization of the event status and other details of theselected group or service. In the Group hyperbolic tree, the entire group hierarchy and devicesare visible on a hyperbolic pane that is mapped to a circular display region. Service tree isapplicable only for the selected service.If a service is selected in the navigation tree, this view displays a graphical representation ofthe configuration items in the service model and shows how those configuration items relateto each other. Use the Graph view to monitor events for published service models thatrepresent your business services.You can display a Tree/Graph view for:

Services

Groups

Grid Grid view displays information for the selected object in a tabular format. you can view theevent status and other details of the selected object through hyperlinks to graphs, views, etc.You can display a Grid view for:

Abnormalities

Groups

Devices

For more detailed information, BMC ProactiveNet Getting Started Guide on the BMC Support


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

website.

Adding attributes to the graphFollowing configuration, only one attribute is enabled for the graph of each monitor. You mightwant to add additional attributes to the monitor graph.

1. In the BMC ProactiveNet Operations console, select the Navigation drawer.

2. Select Global > Devices.

3. Select the Grid view.All the monitored devices are displayed in table format.

4. Select a device from the displayed table.

5. Select a monitor.

6. Click Tools >Show Graph

7. Select the Attributes & Indicators tab.

8. Select one or more attributes.Up to 12 attributes of a monitor can be displayed on a single graph. Though only two units ofmeasurement can be used.

Viewing and manipulating attribute graphsThe graph provides a visual display of the attributes of a monitor. Up to 12 attributes of a monitorcan be displayed on a single graph.

1. In the BMC ProactiveNet Operations console, select the Navigation drawer.


3. Select the Grid view. All the monitored devices are displayed in table format.

4. Select a device from the table.


6. Click Tools > Show Graph

If Collect Data is not enabled then no data is available.

The Graph Display window opens, displaying a graph displaying the values of the selectedattributes for this monitor.You can use the options available on this tab to manipulate the graph. For complete details, referto BMC ProactiveNet User Guide on the BMC Support website.


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Viewing monitors for a deviceThis section provides a brief overview of how to view the monitors for a selected device. Forcomplete details, refer to BMC ProactiveNet User Guide on the BMC Support website.

To view the Monitor types for a device1. In the BMC ProactiveNet Operations console, select the Navigation drawer.



4. Select a device from the table. A hierarchical tree listing the monitors for that device isdisplayed. You can click the + and - to expand and collapse nodes of the hierarchical tree.

The following information is displayed:

Information Description

Monitor Name Device name or process name, a device might appear more than once if it ismonitored by several PATROL Agents

Monitor Type Name of the monitor type.This will correspond to the element displayed in the Monitor Name column,specifying the type of device or process monitored

Source Agent ProactiveNet server where the PATROL Agent and integration service are running

Open Number of open alerts, a green globe is displayed if no alerts are open

Closed Number of closed alerts

Enabled Enabled if data is being collected

Changing thresholdsYou can adjust the thresholds for the attributes of a monitor type either globally or for a specificdevice instance. In the BMC ProactiveNet Operations console, select the Navigation drawer.



3. Select a device from the table.


5. Select Tools > Thresholds. A menu containing the available thresholds is displayed.

Global thresholds are applied to all monitor instances of the selected monitor type. Instance thresholds areapplied to the selected monitor instance.

6. Edit the Threshold settings

7. Click Apply.


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Managing Baselines and Key PerformanceIndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMCProactiveNet calculates baselines per attributes based on values collected over a specifiedperiod of time to determine a normal operating range. When the collected values for theseattributes are out of range, an alert is triggered.

Some attributes are identified by default as Key Performance Indicators (identitied with the icon) and therefore automatically included 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 aspecified time period and establishing a low baseline value (consisting of the 10th percentile ofall the values for a given time period) and a high baseline value (consisting of the 90th percentileof all the values for a given time period), taking a weighted average of these values over time. Ahigher weight is given to the latest data being factored into the baseline average. The accuracyof the baseline improves over time.

Requirements for baseline generation

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

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

Managing Key Performance Indicators

The KPI attribute of an attribute can be activated or deactivated manually through the BMCProactiveNet Administration Console. In this KM, some attributes have been designated asimportant indicators of performance (KPIs). We do not recommend that these default settingsare modified.

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


BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Administration Console.

To add or remove Key Performance Indicator (KPI) attributes for a monitor 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 removeKPI attributes. 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 PerformanceIndicators:

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 thatmonitor type

For complete and detailed information on this procedure, please refer to the BMC ProactiveNetdocumentation available f rom BMC Web site.

Reference Guide

69

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Introduction

This chapter provides statistical information about resources, operating status, andperformances managed by the Tivoli Storage Manager KM. It contains tables describing theattributes used in the monitoring solution, grouped by Monitor Types, and provides a briefdescription of each attribute and its default settings.

Monitor Types

Tivoli Storage Manager KM

TSM Automatic Drive

TSM Automatic Library

TSM Client

TSM Daemons

TSM Daemon

TSM Database

TSM Domain

TSM Domain Client Node

TSM Job

TSM Jobs

TSM Log

TSM Manual Drive

TSM Mount Request

TSM Process

TSM Storage Pool

Baselines and Key Performance Indicators

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

In this guide, attributes flagged as KPIs are respectively identified by the following icon: .

70

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Tivoli Storage Manager KMAttributes

Name Description Units Recommended AlertConditions

BMC ProactiveNetAttribute Type

Login Status Monitors the status ofthe TSM KM logindetails (username/password) for theoperating system andDSMADMC.

If no valid username/password is detectedfor the operatingsystem or DSMADMC,this attribute will beset to Failure. If thereare any suspiciouscommand exits, thisattribute will be set toSuspicious.

0 = OK1 =Suspicious2 = Failure

Warning = 1Alarm = 2

Collection Status

Monitoring Mode Monitors the failovermode of the TSM KM.By default TSM KMruns in PermanentSingle-node Mode.

0 =PermanentSingle-nodeMode1 =TemporarySingle-nodeMode2 = ActiveMulti-nodeMode3 = PassiveMulti-nodeMode-1 =Unknown

n/a Collection Status

Node Status Monitors the errormessages generatedfor the Tivoli StorageManager applicationon the managedsystem.



Availability

71 Tivoli Storage Manager KM

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

TSM Automated DriveAttributes



State Displays the state ofthe automated librarydrive. This isdetermined from theautomated librarydrive controlinformation.

0 = Online1 = Empty2 = Loaded3 =Unloaded4 = Reserved5 =Unavailable6 = DriveOffline7 = PathOffline-1 =Unknown

None Availability

Status Monitors the status ofthe automated librarydrive



Availability

TSM Automated LibraryAttributes



State Displays whether thepath for the automatedlibrary is online oroffline. It will notperform any remoteautomated library testcommand on thestorage agent.

0 = Online1 = Offline2 = PathOffline-1 =Unknown

None Availability

Status Monitors the status ofthe automated library.



Availability

Up Drive Count Displays the numberup / online state drivesin this robotic library.

Count None Statistics

72TSM Automated Library

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Volume Count Displays the totalnumber of volumeloaded in thisautomated library.


Volume PrivateCount

Displays the number ofprivate volumes in theautomated library.


Volume ScratchCount

Displays the number ofscratch volumes in theautomated library.


Volume ScratchPercent

Monitors thepercentage of scratchvolume against thetotal number of volumeloaded in thisautomated library.

Percentage(%)

None Statistics

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

TSM ClientAttributes



Last Access ElapsedTime

Displays the timeelapsed since the lastcommunication fromthe client.

Hours None Statistics

Space Used Displays the amount ofspace used on theclient node.

Gigabytes(GB)

None Statistics

State Displays the state ofthe client.

0 = Running1 = Locked2 = NeverCommunicated-1 =Unknown

None Availability

Status Displays the clientstatus. The followingState to Statusmapping rule is used:

NeverCommunicated >FailureUnknown > FailureLocked > SuspiciousAll other states > OK

0 = OK1 =Suspicious 2 = Failure

Warning = 1Alarm =2

Availability


73 TSM Daemons

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

TSM DaemonsAttributes


BMCProactiveNetAttribute Type

Exec Time Inactive standard attributemonitors the collector executiontime. To activate this attribute,use the PSL below, and restart thePATROL Agent:

%PSL pconfig("REPLACE",

"/Runtime/TSM/

TSMDeamonsCollectorExecT

ime", 1);

When activated it will run everyminute and trigger a warningwhen the collector runs for morethan the observed maximumtime. This maximum time can beoverridden by a preset value(example: 3600 seconds), usingthe PSL below:

%PSL pconfig("REPLACE",

"/Runtime/TSM/

NBUDaemonCollectorWarn",

3600);

Seconds Warning:> presetvalue orobservedmaximum(default)

CollectionStatus

TSM DaemonAttributes



CPU Duration Displays the CPUseconds consumed bythe daemon.

Seconds None Statistics

CPU Utilization Displays thepercentage of CPU used by the daemon.

Percentage(%)

None Statistics

Memory Size Displays the coreimage size of thedaemon in the virtualmemory.

Kilobytes(KB)

None Statistics

Processes Count Displays the number ofdaemon processes/threads found.

Processes None Statistics

74TSM Daemon

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

State Displays the state ofthe daemon asreported in thecommand executed bythe data collector.

0 = Running1 = Sleeping2 = Waiting3 = Queued4 =Intermediate5 =Terminated6 = Stopped/Disabled7 = Growing8 =Nonexistent/NotResponding9 = NotRunning-1 =Unknown

None Availability

Status Monitors the status ofthe daemon. Thefollowing State toStatus mapping rule isused:

Nonexistent/NotResponding > FailureNot Running >FailureTerminated orStopped >SuspiciousGrowing or Unknown> SuspiciousAll other states > OK

0 = OK1 =Suspicious 2 = Failure

None Availability


TSM DatabaseAttributes



Backup Elapsed * Displays the elapsedtime since the lastsuccessful databasebackup.


75 TSM Database

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Buffer Request

Count *Displays thecumulative number ofrequests for databasepages since the bufferpool was last reset (orsince the server waslast started).


Cache Hit Percent * Displays (as apercentage of the totalnumber of requests)the number of requestsfor a database pagesthat are already in thebuffer pool.

Percentage(%)

None Statistics

Cache Wait Percent

*Displays (as apercentage of the totalnumber of requests)the number of requestsfor database bufferpool pages where nopages are available,because all pages arein use.

Percentage(%)

None Statistics

File System Space

Used Percent *Monitors thepercentage of spaceused by the file systemwhere the databaseresides.

Percentage(%)

Warning = 95-98 Alarm > 98

Statistics

Log Consumed Size * Displays thecumulativeconsumption of the logspace used by theserver since the lastreset of this attribute.

Megabytes(MB)

None Statistics

Log Pool Used

Percent *Displays (as apercentage of allrecovery log bufferpool pages) thenumber of buffer poolpages used to writechanges to therecovery log after atransaction iscommitted.

Percentage(%)

None Statistics

76TSM Database

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Log Pool Wait

Percent *Set by TSMDatabaseCollector.Displays (as apercentage of allrecovery log bufferpool requests) thenumber of requests forbuffer pool pageswhere no pages areavailable because all

pages are in use.

Percentage(%)

None Statistics

Pool Hit Percent * Displays (as apercentage of the totalnumber of requests)the number of requestsfor database pagesthat are already in thebuffer pool.

Percentage(%)

None

Reorg Elapsed * Displays the elapsedtime since the lastdatabasereorganization.


Space Available Monitors the amountof assigned spaceremaining availablefor use by the serverdatabase.

Megabytes(MB)

Warning = 2-5Alarm < 2

Availability

Space Changed * Displays the databasepages (in megabytes)that have changedsince the last backup.

Megabytes(MB)

None Statistics

Space Changed

Percent *Displays thepercentage of databasepages that havechanged since the lastbackup.

Percentage(%)

None Statistics

Space Growth Rate Displays the growthrate of the space usedby the server database.

Megabytesper second(MB/s)

None Statistics

Space MaxExtension

Displays the maximumamount the databasecan be extended by.

Megabytes(MB)

None Statistics

Space MaxReduction

Displays the maximumamount the databasecan be reduced by.

Megabytes(MB)

Warning: 4-8Alarm: less than 4

Statistics

77 TSM Database

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Space Used Displays the amount ofassigned space usedby the serverdatabase.

Megabytes(MB)

None Statistics

Space Used Percent Monitors thepercentage of assignedspace used by theserver database.

The total assignedspace is the usedspace (Space Used)plus the availablespace (SpaceAvailable).

Percentage(%)

None Statistics

* This attribute is only available for the server database (db).


TSM DomainAttributes



Backup Elapsed Displays the elapsedtime since the lastbackup for thisdomain, regardless ofcompletion status ofthe backup.


Backup Throughput Displays thethroughput of the lastsuccessful backup forthis domain.

Gigabytesper second(GB/s)

None Statistics

Full BackupDuration

Displays the durationof the last successfulfull backup for thisdomain.


Full BackupElapsed

Displays the elapsedtime since the lastsuccessful full backupfor this domain.


Full Backup ObjectCount�

Displays the number ofobjects backed up inthe last successful fullbackup for thisdomain.


78TSM Domain

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Full Backup Size Displays the size of thelast successful fullbackup for thisdomain.

Gigabytes(GB)

None Statistics

Incremental BackupDuration

Displays the durationof the last successfulincremental backupfor this domain.


Incremental BackupElapsed

Displays the elapsedtime since the lastsuccessful incrementalbackup for thisdomain.


Incremental BackupObject Count

Displays the number ofobjects backed up inthe last successfulincremental backupfor this domain.


Incremental BackupSize�

Displays the size of thelast successfulincremental backupfor this domain.

Gigabytes(GB)

None Statistics

State Displays the state ofthe domain.

0 = Idle1 = Running2 = Runningin RestrictedWindow3 = NotStarted4 = Inactive-1 =Unknown

None Availability

Status Monitors the status ofthe domain. Thefollowing State toStatus mapping rule isused:

Running inrestricted window >FailureRunning for morethan 600 minutes >SuspiciousUnknown >SuspiciousAll other states > OK


None Availability

Successful BackupElapsed

Displays the elapsedtime since the lastsuccessful backup forthis domain.

hours None Statistics


79 TSM Domain Client Node

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

TSM Domain Client NodeAttributes



Backup Throughput

Displays thethroughput of the lastsuccessful backup forthis client node.


None Statistics

Last Full BackupDuration

Displays the durationof the last successfulfull backup for thisclient node.


Last Full BackupObject Count �

Displays the number ofobjects backed up inthe last successful fullbackup for this clientnode.


Last Full Backup Size�

Displays the size of thelast successful fullbackup for this clientnode.

Megabytes(MB)

None Statistics

Last IncrementalBackup Duration

Displays the durationof the last successfulincremental backupfor this client node.


Last IncrementalBackup ObjectCount

Displays the number ofobjects backed up inthe last successfulincremental backupfor this client node.


Last IncrementalBackup Size

Displays the size of thelast successfulincremental backupfor this client node.

Megabytes(MB)

None Statistics


TSM JobsAttributes



80TSM Jobs

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Active BackupCount

Displays the number ofactive backup jobscurrently discoveredand monitored.


Active Count Displays the number ofactive jobs currentlydiscovered andmonitored.


Active Non-BackupCount

Displays the number ofactive non-backup jobscurrently discoveredand monitored.



81 TSM Jobs

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

TSM JobAttributes


BMC ProactiveNet

Duration Displays the durationof the job from thestart.


Error Count Monitors the numberof client node errorslogged in the serveractivity log during thisjob.

Count Warning when > 100 Statistics

NetworkThroughput

Displays thethroughput of the jobon the network.


None Statistics

Object Count Displays the number ofobjects inspected forthis job.


Object ExpiredCount

Displays the totalnumber of objects forthis job that haveexpired.


Object Failed Count Displays the totalnumber of objects forthis job that havefailed.

Count Warning when > 100 Statistics

Object ProcessedCount

Displays the totalnumber of objects forthis job that have beenprocessed.


Object ReboundCount �

Displays the totalnumber of objects forthis job that have beenrebound.


Object UpdatedCount

Displays the totalnumber of objects forthis job that have beenupdated.


Size Displays the amount ofdata backed up for thejob.

Megabytes(MB)

None Statistics

State Displays the state ofthe job.

0 =Completed1 = Future2 = Pending

None Availability

82TSM Job

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

3 = InProgress4 = Started5 = Restarted6 =Completed/Errors7 = Started/Errors8 =Restarted/Errors9 = Failed -No Restart10 = Missed11 = Severed12 =Uncertain13 = Failed-1 =Unknown

Status Monitors the status ofthe job. The followingState to Statusmapping rule is used:

Missed, Severed, orFailed > FailurePending for morethan 1 hour >SuspiciousStarted for morethan 5 hours >SuspiciousRestarted for morethan 5 hours >SuspiciousCompleted/Errors >SuspiciousStarted/Errors >SuspiciousRestarted/Errors >SuspiciousAll other states > OK



Availability

Throughput Displays thethroughput of the job.


None Statistics


83 TSM Log

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

TSM LogAttributes



Alarm MessageCount

Monitors the numberof alarm messages.

Count Alarm > 1 Statistics

File Space GrowthRate*

Displays the growthrate of the amount ofspace used by the logfile.

Kilobytesper second(KB/s)

None Statistics

File Space Used* Displays the amount ofspace used by the logfile.

Kilobytes(KB)

None Statistics

File System SpaceUsed Percent*

Monitors thepercentage of spaceused by the file system(where the log fileresides).

Percentage(%)

Warning = 95-98Alarm: > 98

Statistics

Space Available* Monitors theavailable space for thelog file to use (this isalso the availablespace on the filesystem).

Megabytes(MB)

Warning = 2-5Alarm < 2

Availability

Space Used Percent* Monitors thepercentage of capacityused by the log file.

The total capacity isthe used space (LogSpace Used) plusavailable space (LogSpace Available).

Percentage(%)

Warning = 95-98Alarm: > 98

Statistics

Warning MessageCount

Monitors the numberof warning messages.

Count Warning > 1 Statistics

*This attribute is not available for the activity log (actlog).


84TSM Manual Drive

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

TSM Manual DriveAttributes



State Displays the state ofthe automated librarydrive. This isdetermined from theautomated librarydrive controlinformation.

0 = Online1 = Empty2 = Loaded3 = Unloaded4 = Reserved5 =Unavailable6 = DriveOffline7 = PathOffline-1 =Unknown

None Availability

Status Monitors the status ofthe automated librarydrive.

0 = OK 1 =Suspicious2 = Failure


Availability

TSM Mount RequestAttributes



Elapsed Displays the elapsedtime since the mountrequest was issued.

Minutes None Statistics

State Displays the state ofthe mount request asreported in thecommand executed bythe data collector.

0 =Completed1= Pending-1 =Unknown

None Availability

Status Monitors the status ofthe mount request. Thefollowing State toStatus mapping rule isused:

Pending for morethan 30 minutes >FailurePending or Unknown> Suspicious



Availability

85 TSM Mount Request

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

All other states > OK

Timeout Displays the timeremaining until themount request timesout.

Minutes Alarm = 0-30 Statistics


TSM ProcessAttributes



Duration Displays the durationof the process.


Item Count Displays the number ofitems found.


Size Displays the processsize.

Megabytes(MB)

None Statistics

State Displays the state ofthe process.

0 = Running1 = Running/Errors2 =Completed/Success3 =Completed /Failure-1 =Unknown

None Availability

Status Monitors the status ofthe process. Thefollowing State toStatus mapping rule isused:

Completed/Failure >FailureRunning/Errors orUnknown >SuspiciousRunning for morethan 10 hours >SuspiciousAll other states > OK.



Availability

Throughput Displays thethroughput of theprocess.


None Statistics


86TSM Storage Pool

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

TSM Storage PoolAttributes



Space Available Monitors the availablevolume space for thebackup data to use inthis storage pool.

Gigabytes(GB)

Warning < 1Alarm = 0

Availability

Space Growth Rate Displays the growthrate of the totalvolume space used bythe backup data in thisstorage pool.

Gigabytesper second(GB/s)

None Statistics

Space LogicalPercent

Displays the logicaloccupancy of thestorage pool as apercentage of the totaloccupancy.

Percentage(%)

None Statistics

Space Migrated Displays the amount ofdata that has beenmigrated, if migrationis in progress. Ifmigration is not inprogress, this valueindicates the amountof data migratedduring the lastmigration.Note: This attribute isnot available for copystorage pools.

Gigabytes(GB)

None Statistics

Space MigrationPercent

Displays an estimateof the percentage ofdata in the storagepool that can bemigrated.Note: This attribute isnot available for copystorage pools.

Percentage(%)

None Statistics

87 TSM Storage Pool

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Space MigrationElapsed �

Displays the amount oftime that has elapsedsince migration of thestorage pool began, ifmigration is active. Ifmigration is not active,this value indicatesthe amount of timerequired to completethe last migration.Note: This attribute isnot available for copystorage pools.


Space Reclaimable Displays the amount ofspace in the storagepool that isreclaimable.

Gigabytes(GB)

None Statistics

Space ReclaimablePercent

Displays the amount ofreclaimable space as apercentage of the totalstorage pool space.

Percentage(%)

None Statistics

Space Used Displays the totalvolume spaceoccupied by thebackup data in thisstorage pool.

Gigabytes(GB)

None Statistics

Space Used Percent Monitors thepercentage of totaloccupied volumespace against the totalvolume capacity ofthis storage pool (notincluding any scratchvolumes).

Percentage(%)

Warning > 95Alarm > 98

Statistics

Volumes ActiveCount

Displays the number ofactive volumes in thisstorage pool.

Active volumes areavailable disk volumeswith a status of"Online" or tapevolumes with a statusof "Filling", where datahas been written butthe volume is not yetfull.


Volume ActivePercent�

Monitors thepercentage of activevolumes against thetotal number ofvolumes in thisstorage pool.

Percentage(%)

None Statistics

88TSM Storage Pool

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Volume AvailableCount

Displays the number ofvolumes assigned tothis storage pool.


Volume AvailablePercent

Monitors thepercentage ofavailable volumesagainst the totalnumber of volumes inthis storage pool.

Percentage(%)

None Statistics

Volume Count Displays the totalnumber of volumes inthis storage pool.


Volume EmptyCount

Displays the number ofempty volumes in thisstorage pool.

Empty is a possiblestatus for a tapevolume, indicating thatno data is stored onthat volume.


Volume Full Count Displays the number offull volumes in thisstorage pool.


Volume Full Percent Monitors thepercentage of fullvolumes against thetotal number ofvolumes in thisstorage pool.

Percentage(%)

None Statistics

Volume OfflineCount

Displays the number ofoffline volumes in thisstorage pool.

"Offline" is a possiblestatus for a diskvolume.


Volume PendingCount

Displays the number ofpending volumes inthis storage pool.

"Pending" is a possiblestatus for a tapevolume, where all fileshave been deleted buta delay has beenplaced on the volumebefore reuse.



89

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Index

- A -Abnormalities 66

Access

Permissions 12

User 12Actlog Query Limit 50

Add Monitor Types 29

Attribute 64

Attributes

Active Backup Count 79

Active Count 79

Active Non-Backup Count 79

Alarm Message Count 83

Backup Elapsed 74, 77

Backup Throughput 77, 79

Buffer Request Count 74

Cache Hit Percent 74

Cache Wait Percent 74

CPU Duration 73

CPU Utilization 73

Duration 81, 85

Elapsed 84

Error Count 81

Exec Time 73

File Space Growth Rate 83

File Space Used 83

File System Space Used Percent 74, 83

Full Backup Duration 77

Full Backup Elapsed 77

Full Backup Object Count 77

Full Backup Size 77

Incremental Backup Duration 77

Incremental Backup Elapsed 77

Incremental Backup Object Count 77

Incremental Backup Size 77

Item Count 85

Last Access Elapsed Time 72

Last Full Backup Duration 79

Last Full Backup Object Count 79

Last Full Backup Size 79

Last Incremental Backup Duration 79

Last Incremental Backup Object Count 79

Last Incremental Backup Size 79

Log Consumed Size 74

Log Pool User Percent 74

Log Pool Wait Percent 74

Login Status 70

Memory Size 73

Monitoring Mode 70

Network Throughput 81

Node Status 70

Object Count 81

Object Expired Count 81

Object Failed Count 81

Object Processed Count 81

Object Rebound Count 81

Object Updated Count 81

Pool Hit Percent 74

Processes Count 73

Reorg Elapsed 74

Size 81, 85

Space Available 74, 83, 86

Space Changed 74

Space Changed Percent 74

Space Growth Rate 74, 86

Space Logical Percent 86

Space Max Extension 74

Space Max Reduction 74

Space Migrated 86

Space Migration Elapsed 86

Space Migration Percent 86

Space Reclaimable 86

Space Reclaimable Percent 86

Space Used 72, 74, 86

Space Used Percent 74, 83, 86

State 71, 73, 77, 81, 84, 85

Status 71, 72, 73, 77, 81, 84, 85

Successful Backup Elapsed 77

Throughput 81, 85

Timeout 84

Up Drive Count 71

Volume Active Percent 86

Volume Available Count 86

Volume Available Percent 86

Volume Count 71, 86

Volume Empty Count 86

Volume Full Count 86

Volume Full Percent 86

Volume Offline Count 86

Volume Pending Count 86

Volume Private Count 71

90

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Attributes

Volume Scratch Count 71

Volume Scratch Percent 71

Volumes Active Count 86

Warning Message Count 83Automated Drives

Debug 34Automated Libraries

Debug 34

- B -Baseline 69

Baselines

BMC ProactiveNet Performance Management 66

Generation 66

Manage 66

Requirements 66BMC PATROL

Changes 11BMC ProactiveNet Performance Management

Abnormalities 66

Baselines 66

Key Performance Indicators 66

KPI 66Business Value 10

- C -Changes 7

Client

Maximum Instances 38Clients

Debug 34Cluster Application 41

Component

folders 60Component Installation package

creating 22

downloading 25

editing 24Configure

Domains 55

Hostname 52

Jobs 52

Log Scan Limit 50

Maximum Instances 38

Monitoring Duration 52

Mount Request 53

Multi-node monitoring mode 41

Overrides 46

Processes 56Configuring

monitor settings 29Configuring Monitor Thresholds 58

Configuring thresholds 58

- D -Daemon

Maximum Instances 38Daemons

Debug 34Database

Maximum Instances 38Databases

Debug 34Debug

Automated Drives 34

Automated Libraries 34

Clients 34

Daemons 34

Databases 34

Directory Path 34

Domains 34

End Time 34

Jobs 34

Logs 34

Mount Requests 34

Processes 34

Server 34

Storage Pools 34Deleting a Threshold Configuration 59

Disk Pool

Maximum Instances 38Disk Storage

Maximum Instances 38Disk Volume

Maximum Instances 38Domains

Configure 55

Debug 34Downloading 25

Duration

Duration 53, 56

91

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

Duration

Monitoring 53, 56

- E -Editing a Threshold Configuration 59

Event

collectors 60

folders 60

- F -Failover Group Name 41

Features 10

Filtering Options

TSM Automated Drive 50

TSM Automated Library 50

TSM Client 50

TSM Daemon 50

TSM Domain 50

TSM Domain Client Node 50

TSM Manual Drive 50

TSM Storage Pool 50Filters



TSM Client 50

TSM Daemon 50

TSM Domain 50

TSM Domain Client Node 50

TSM Manual Drive 50

TSM Storage Pool 50Fixed Issues 7

- G -Generate

Baselines 66Goals 10

Graphs 64

- I -Improvements 7

Information

Closed 65

Enabled 65

Open 65

Source Agent 65Installation 21

configuring 27Installing

Preparation 21Instances

Client 38

Configure 38

Daemon 38

Database 38

Disk Pool 38

Disk Storage 38

Disk Volume 38

Job 38

Log 38

Maximum 38

Mount Request 38

Policy 38

Policy Client 38

Robotic Drive 38

Robotic Library 38

Standalone Drive 38

Volume Pool 38

- J -Job

Maximum Instances 38Jobs

Active 52

Configure 52

Debug 34

Monitoring 52

- K -Key Concepts 10



Manage 66KPI 69


Manage 66

92

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

- L -Log

Maximum Instances 38Log Scan Limit

Configure 50Logs

Debug 34

- M -Manage

Baselines 66


KPI 66Monitor

name 65

type 65Monitor Settings

configuring 29Monitor thresholds 58

Monitor Type

TSM Daemons 73Monitor Types

Tivoli Storage Manager KM 69, 70



TSM Automatic Drive 69

TSM Automatic Library 69

TSM Client 69, 72

TSM Daemon 69, 73

TSM Database 69, 74

TSM Domain 69, 77

TSM Domain Client Node 69, 79

TSM Job 69, 81

TSM Jobs 69, 79

TSM Log 69, 83

TSM Manual Drive 69, 84

TSM Mount Request 69, 84

TSM Process 69, 85

TSM Storage Pool 69, 86Monitoring

Configure 53, 56

Duration 53, 56Monitoring Duration

Jobs 52Monitoring Node Names 41

Mount Request

Configure 53


Monitoring Duration 53Mount Requests

Debug 34Multi-node monitoring mode

Configure 41

- N -Navigation

drawers 60

tree 60

- O -Operations Console views

Event 60

Grid 60

Title 60

Tree/Graph 60Overrides

Configure 46

TSM Server Discovery 46

- P -Package 22, 24, 25

PATROL Configuration Manager 19

Policies

Manage 28Policy

Maximum Instances 38Policy Client

Maximum Instances 38Process

Configure 56

Monitoring Duration 56Processes

Debug 34

- Q -Query Limit

Actlog 50

93

BM

C P

roac

tive

Net

Per

form

ance

Man

age

men

t -

Tivo

li St

orag

e M

anag

er

Mon

itor

ing

Ver

sion

2.7

.02

- R -Reference Guide 69

Remote PATROL Agent Checking 41

Requirements

Security 12

Software 11

System 11Robotic Drive

Maximum Instances 38Robotic Library


- S -Security

Requirements 12Server

Debug 34Software

Requirements 11Standalone Drive

Maximum Instances 38Storage Pools

Debug 34Sudo 12, 31

System

Requirements 11

- T -Tags 19

Thresholds 58

modifications 65Tivoli Storage Manager

Changes 11TSM Server Discovery

Overrides 46

- U -UNIX 31

User Account

Configure 31

patrol 31

Privileges 31

Sudo 31

- V -Volume Pool


- W -Windows 31

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, providescomprehensive multi-platform monitoring solutions that enable management of thehardware and software aspects of all servers and SANs and covering up to 100 % ofcustom applications within the BMC ProactiveNet Performance Managementenvironment. Sentry Software also develops adapters for BMC Atrium Orchestrator thatenables IT administrators to automate the execution of common requests and tasksthat occur in the daily course of IT operations. Combined with BMC’s servers andnetwork automation tools, the adapters allow IT administrators to implementprovisioning and decommissioning workflows that cover all layers of their ITinfrastructure. Finally, Sentry Software designs connectors that bring storage capacitymetrics into BMC TrueSight Capacity Optimization to ensure IT administrators that theirstorage infrastructure is properly sized for their current and future needs.

Like us on Facebook:facebook.com/sentrysoftware

Follow us on Twitter:

twitter.com/sentrysoftware

LEARN MORE

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

© BMC Software, Inc. All rights reserved.

ABOUT MARKETZONE DIRECT PRODUCTS

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

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

www.bmc.com.

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

BUSINESS RUNS ON I.T .

I.T . RUNS ON BMC SOFT WARE

http://facebook.com/sentrysoftware

http://twitter.com/sentrysoftware

http://twitter.com/sentrysoftware

http://facebook.com/sentrysoftware

BMC ProactiveNet - Tivoli Storage Manager Monitoring v2.7 · PDF fileIBM Tivoli Storage...

Documents

Transcript of BMC ProactiveNet - Tivoli Storage Manager Monitoring v2.7 · PDF fileIBM Tivoli Storage...