Tivoli Netcool Performance Manager: IBM Tivoli Monitoring … · 2010-09-07 · 2 IBM Tivoli Netcool Performance Manager: IBM Tivoli Monitoring Integration Guide - Wireless Component

Tivoli Netcool Performance Manager: IBM Tivoli Monitoring Integration Guide - Wireless Component

Netcool Performance Manager

Version 1.2.1

Note

Before using this information and the product it supports, read the information in Notices on page 53.

This edition applies to version 1, release 2, modification 1 of Tivoli Netcool Performance Manager and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corp. 2007, 2009

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

1 About This Documentation . . . . . . . . . . . . 1Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Document Conventions . . . . . . . . . . . . . . . . . . . . 1

Blank pages . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Document Structure . . . . . . . . . . . . . . . . . . . . . . . 3User Publications . . . . . . . . . . . . . . . . . . . . . . . . 3

Viewing the Online Help . . . . . . . . . . . . . . . . 4

2 ITM Integration Overview . . . . . . . . . . . . . 5Integration steps . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 ITM Integration Prerequisites . . . . . . . . . . 7ITM installation . . . . . . . . . . . . . . . . . . . . . . . . . . 7ITM OS agents installation . . . . . . . . . . . . . . . . . 7

4 Tivoli Netcool Performance Manager Agent Installation and Configuration . . . . . . . . . 9Installing Tivoli Netcool Performance Manager agents on the ITM server . . . . . . . . . . . . . . . . . . . 9

Agent installation . . . . . . . . . . . . . . . . . . . . . . 9Installing Tivoli Netcool Performance Manager agents on Tivoli Netcool Performance Manager servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installation using remote deployment . . . . . . 13Local installation . . . . . . . . . . . . . . . . . . . . . . 18

5 Tivoli Netcool Performance Manager Enablement . . . . . . . . . . . . . . . . . . . . . . . . 19Enable collection of ITM metrics . . . . . . . . . . . 19

Application server . . . . . . . . . . . . . . . . . . . . . 19Loaders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Start Tivoli Netcool Performance Manager agent service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6 Gateways ITM Agent Historical Data . . . 27Enabling Historical Data Collection . . . . . . . . . 28Updating Time Spans for Queries . . . . . . . . . . . 29

Updating Time Spans for Bar and Line Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Updating Time Spans for Tables . . . . . . . . . 31

Managing Historical Data by Pruning . . . . . . . . 33

7 Alarm Integration . . . . . . . . . . . . . . . . . . . 35Existing application infrastructure . . . . . . . . . . 35Generating the alarm package . . . . . . . . . . . . . . 36

8 Tivoli Netcool Performance Manager agent metrics and ITM navigation layout . . . . . 41Loader metrics and navigation layout . . . . . . . . 41

Loader agent log files . . . . . . . . . . . . . . . . . . 41

Default ITM navigation layout . . . . . . . . . . . 42Application server metrics and navigation layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Application server agent log files . . . . . . . . . 44Default ITM navigation layout . . . . . . . . . . . 46

Gateway server metrics and navigation layout . 48Gateway agent log files . . . . . . . . . . . . . . . . . 48Default ITM navigation layout . . . . . . . . . . . 50

© Copyright IBM Corp. 2007, 2009 i

ii Tivoli Netcool Performance Manager: IBM Tivoli Monitoring Integration Guide - Wireless Component

1 About This Documentation

IBM Tivoli® Monitoring (ITM) helps monitor and optimize hardware and application performance. The ITM application operates by deploying agents to monitor the performance of target systems and to relay the data back to the ITM system, where it can be stored and reported on.

The purpose of this guide is to provide details of integrating IBM Tivoli® Netcool® Performance Manager with ITM. This document provides information for the deployment of the following Tivoli Netcool Performance Manager agents on ITM:

• application server• loaders• gateways

1.1 AudienceThis guide is intended for administrators or operations specialists responsible for installing and adminis-trating ITM and Tivoli Netcool Performance Manager.

1.2 Document ConventionsThis document uses the typographical conventions shown in the following table:

Table 1: General Document Conventions

Format Examples Description

ALL UPPERCASE

• GPS• NULL• MYWEBSERVER

Acronyms, device names, logical opera-tors, registry keys, and some data struc-tures.

Underscore See Document Conventions For links within a document or to the Inter-net. Note that TOC and index links are not underscored. Color of text is determined by browser settings.

Bold • Note: The busy hour determiner is... Heading text for Notes, and Warnings.

© Copyright IBM Corp. 2007, 2009 1

1.2.1 Blank pages

Blank pages are used at the end of chapters to ensure the following chapter begins on an odd numbered page. These pages are intentionally blank. If the guide is printed double-sided and bound, each chapter will begin on a right-hand page.

SMALL CAPS • The STORED SQL dialog box...• ...click VIEW...• In the main GUI window, select the

FILE menu, point to NEW, and then select TRAFFIC TEMPLATE.

Any text that appears on the GUI.

Italic • A busy hour is...• A web server must be installed...• See the User Guide

New terms, emphasis, and book titles.

Monospace • ./wminstall• $ cd /cdrom/cdrom0• /xml/dict• http://abc.com/products/• addmsc.sh• Type OK to continue.

Code text, command line text, paths, scripts, and file names. Text written in the body of a paragraph that the user is expected to enter.

Monospace Bold

[root] # pkginfo | grep -i perlsystem Perl5 On-Line Manual Pages

system Perl 5.005_03 (POD Docu-mentation)

system Perl 5.005_03

For contrast in a code example to show lines the user is expected to enter.

<Mono-space italics>

• # cd <oracle_setup> Used in code examples: command-line variables that you replace with a real name or value. These are always marked with arrow brackets.

[square bracket]

log-archiver.sh [-i][-w][-t] Used in code examples: indicates options.

Table 1: General Document Conventions (Continued)

Format Examples Description

2 IBM Tivoli Netcool Performance Manager: IBM Tivoli Monitoring Integration Guide - Wireless Component

1.3 Document StructureThis document is organized in to the following chapters and appendices:

1.4 User Publications

Tivoli Netcool Performance Manager software provides the following user publications in HTML or Adobe® Portable Document Format (PDF) formats.

Table 2: Document Structure

Chapter Description

ITM Integration Overview Overview of steps to integrate ITM with Tivoli Netcool Perfor-mance Manager.

ITM Integration Prerequisites Integration prerequisites, including ITM installation, ITM OS agent installation and notification target definition for gateways.

Tivoli Netcool Performance Manager Agent Installation and Configuration

Installing and configuring Tivoli Netcool Performance Manager agents for the application server, loaders and gateways.

Tivoli Netcool Performance Manager Enablement

Enabling Tivoli Netcool Performance Manager for the collection of ITM metrics. Starting

Gateways ITM Agent Historical Data Enabling historical data collection.

Alarm Integration Integrating Tivoli Netcool Performance Manager alarms.

Tivoli Netcool Performance Manager agent metrics and ITM navigation layout

Describes the metrics collected for each Tivoli Netcool Perfor-mance Manager agent, the log files used and the default ITM navi-gation layout.

Table 3: Tivoli Netcool Performance Manager User Documentation

Document Description

Administration Guide Provides instructions and general information on how to maintain and support Tivoli Netcool Performance Manager.

IBM Tivoli Monitoring Integration Guide

Provides instructions for integrating IBM Tivoli Monitoring with Tivoli Netcool Performance Manager.

Installation Guide Provides instructions for installing and configuring the Tivoli Netcool Performance Manager software.

ModelMaker Installation Guide

Provides instructions for installing the ModelMaker application.

ModelMaker User Guide Provides information and procedures for creating and modifying Busi-ness Objects universes to be used with Tivoli Netcool Performance Manager databases.

Netcool OMNIbus/Webtop Integration Guide

Provides instructions for integrating Netcool OMNIbus/Webtop with Tivoli Netcool Performance Manager.

Online Help Provides information and procedures for using Tivoli Netcool Perfor-mance Manager software for performance, trending analysis and per-formance alarms.

About This Documentation 3

1.4.1 Viewing the Online Help

You can view Online Help for the Tivoli Netcool Performance Manager Web client. Using the Tivoli Netcool Performance Manager user interface, you can select HELP tabs or the HELP links for context-sensitive Help.

Upgrade Guide Instructions for upgrading Tivoli Netcool Performance Manager soft-ware.

User Guide Provides conceptual information and procedures for using Tivoli Net-cool Performance Manager software for performance, trending analy-sis and performance alarms.

Table 3: Tivoli Netcool Performance Manager User Documentation (Continued)

Document Description


2 ITM Integration Overview

IBM Tivoli Monitoring (ITM) helps monitor and optimize hardware and application performance. The ITM application operates by deploying agents to monitor the performance of target systems and to relay the data back to the ITM system, where it can be stored and reported on.

There are three agents available to monitor the performance of the Tivoli Netcool Performance Manager (Tivoli Netcool Performance Manager) application.

• the Gateway agent monitors the performance and processing success of the Tivoli Netcool Performance Manager gateways.

• the Loader agent monitors the performance and processing success of the Tivoli Netcool Performance Manager loaders.

• the Application Server agent monitors the performance, usage and data availability progress of the Tivoli Netcool Performance Manager core functions.

Each agent is downloaded, installed and configured separately. System administrators can decide which agent or agents to install and configure.

2.1 Integration stepsA number of steps must be completed in order to set up ITM monitoring of Tivoli Netcool Performance Manager.

The order of these steps is:

1. Prerequisitesa. ITM installationb. ITM OS agents installation

2. Tivoli Netcool Performance Manager agent installation and configurationa. Tivoli Netcool Performance Manager agents installation on the ITM serverb. Tivoli Netcool Performance Manager agents installation on Tivoli Netcool Performance

Manager servers

3. Tivoli Netcool Performance Manager enablementa. Enable collection of ITM metricsb. Start a Tivoli Netcool Performance Manager agent service on ITM


6 Tivoli Netcool Performance Manager: IBM Tivoli Monitoring Integration Guide - Wireless Component

3 ITM Integration Prerequisites

This chapter describes the integration prerequisites for ITM integration.

These prerequisites include:

• ITM installation• ITM OS agents installation

3.1 ITM installationIf you do not currently have an ITM installation you must install ITM on the server to be used for monitoring Tivoli Netcool Performance Manager, this server will be referred to as the ITM server. ITM version 6.2.0 or higher is required.

Refer to Chapter 6 of the IBM Tivoli Monitoring Installation and Setup Guide for instructions on installing ITM.

Note: You can install ITM on the same server as one of the Tivoli Netcool Performance Manager serv-ers. However, be aware that this configuration adds a significant resource overhead to that server.

3.2 ITM OS agents installationITM OS agents must be installed on each of the Tivoli Netcool Performance Manager servers to be monitored. The OS agent installed must be appropriate for the server’s operating system.

Note: If a distributed system is being used, with Tivoli Netcool Performance Manager gateways and/or loaders installed over multiple servers, each Tivoli Netcool Performance Manager server must be installed with the OS agent appropriate for the server’s operating system.

Note: ITM requires that the SE Linux® feature is turned off before installation.

Refer to the section Installing Monitoring Agents of Chapter 6 of the IBM Tivoli Monitoring Installation and Setup Guide for instructions on how to deploy OS agents to a server.


The same section of the guide describes how to configure and start the OS agents. Once an agent has been correctly configured and started it should appear in the Navigator view of the Tivoli Enterprise Portal (TEP). The IBM Tivoli Monitoring User's Guide describes the configuration and use of the TEP GUI.


4 Tivoli Netcool Performance Manager Agent Installation and Configuration

This chapter describes the installation and configuration of Tivoli Netcool Performance Manager agents. You need only install the agents for those components of Tivoli Netcool Performance Manager that you intend to monitor.

This chapter describes:

• Installing Tivoli Netcool Performance Manager agents on the ITM server• Installing Tivoli Netcool Performance Manager agents on Tivoli Netcool Performance Manager

servers

4.1 Installing Tivoli Netcool Performance Manager agents on the ITM server

Each of the Tivoli Netcool Performance Manager agents that are to be used must be installed on the ITM (TEMS) server. There are three Tivoli Netcool Performance Manager agents:

• loader• application server (as)• gateways

4.1.1 Agent installation

Perform the following steps to install a Tivoli Netcool Performance Manager agent on the ITM server.

1. Unpack the contents of the agent archive.

Note: It is recommended that each agent is unpacked in to a different directory to avoid files being overwritten. Filenames and the directory structure for each agent are similar.

The CD_ROOT directory of the unpacked software packages contains a graphical installation wizard for each available architecture.

If installing on UNIX®, the installer requires X-window functionality.


2. Run the appropriate platform installer without parameters. For example, on a Windows® platform execute:<software_location>/CD_ROOT/setupwin32.exe

The Installer Wizard’s Welcome Screen is displayed.

The following instructions illustrate installing the Tivoli Netcool Performance Manager application server agent. The installation for each agent is the same.

3. Click NEXT, to proceed to ITM installation directory and installable media locations.

Enter the ITM installation directory. Enter the location of the installable media, this is the location the Tivoli Netcool Performance Manager agent installer was unpacked to.

4. Click NEXT, to proceed to ITM components.


Select the following options:• TIVOLI ENTERPRISE MONITORING SERVER (TEMS)• TIVOLI ENTERPRISE PORTAL SERVER (TEPS)• TIVOLI ENTERPRISE DESKTOP CLIENT (TEPD)

If required, also select options to perform a local install and TEMS depot install.• PERFORM A LOCAL INSTALL OF THE SOLUTION ON THIS MACHINE

This option is used only if the ITM server is also used as one of the Tivoli Netcool Performance Manager servers to be monitored. For example, if the ITM server is also used as the Tivoli Netcool Performance Manager application server. This allows the agent to be started and to monitor its Tivoli Netcool Performance Manager component.

• PERFORM A TEMS DEPOT INSTALL OF THE SOLUTION IN THIS MACHINE

Installs the Tivoli Netcool Performance Manager agent on the remote source depot of ITM. Selecting this option is recommended because it enables remote deployment of agents from the TEP GUI.

5. Click NEXT, to proceed to TEMS hostname and administrative credentials.

Enter the TEMS User ID, Password and Hostname.

6. Click NEXT, to proceed to applications to add.

This example illustrates installing the Tivoli Netcool Performance Manager application server agent. The appropriate option will be available for each Tivoli Netcool Performance Manager agent.

Tivoli Netcool Performance Manager Agent Installation and Configuration 11

Select MONITORING AGENT FOR TNPMW APPLICATION SERVER.

7. Click NEXT, to proceed to Confirmation.

Confirm your choices, and click NEXT to proceed to Installation.

8. When the installation is complete, Click FINISH to close the Wizard.

4.2 Installing Tivoli Netcool Performance Manager agents on Tivoli Netcool Performance Manager servers

Each of the Tivoli Netcool Performance Manager agents that are to be used must be installed on the appropriate Tivoli Netcool Performance Manager server. For example, installing the Tivoli Netcool Performance Manager application server agent on the Tivoli Netcool Performance Manager application server. There are three Tivoli Netcool Performance Manager agents:

• loader• application server (as)• gateways

There are two possible methods for installing Tivoli Netcool Performance Manager agents on Tivoli Netcool Performance Manager servers:

• Installation using remote deployment. Allows the Tivoli Netcool Performance Manager agent to be installed and configured in one step using the TEP GUI.


• Local installation. Installs the Tivoli Netcool Performance Manager agent locally on a Tivoli Netcool Performance Manager server.

4.2.1 Installation using remote deployment

Using the TEP GUI allows the Tivoli Netcool Performance Manager agent to be installed and configured in one step.

To install/deploy a Tivoli Netcool Performance Manager agent from TEP:

1. Start the TEP application.

2. Right click the server to install on and select ADD MANAGED SYSTEM.

Note: The OS agent must be running on the Tivoli Netcool Performance Manager server to con-tinue with remote installation. Refer to the section Installing Monitoring Agents of Chapter 6 of the IBM Tivoli Monitoring Installation and Setup Guide for instructions on how to run OS agents.


The Select a Monitoring Agent dialog is displayed.

3. Select the type of agent to install, and click OK.

The configuration parameters for the agent are displayed. See the following sections for details of each agent’s configuration:• Application server agent configuration• Loader agent configuration• Gateway agent configuration

The procedure for configuring an application server, loader, or gateway agent is similar.

Because multiple instances of loader and gateway agents can exist on a single server, you will also be asked for a name for the instance. This is not the case for an application server agent.

Note: The installation of the Tivoli Netcool Performance Manager agent only occurs the first time ADD MANAGED SYSTEM is performed for an agent. Subsequent operations will either add new instances or reconfigure the existing agent. Also, once an agent has been installed from TEP, the ITM command line can be used to perform the same configuration and start/stop actions directly on the server. This does not apply to the application server agent, since only one instance of that agent can be present on a server.


Application server agent configuration

1. Enter or amend any configuration settings, as required.

2. Click FINISH.

A dialog is displayed to indicate the deployment has been queued.


Loader agent configuration

1. Enter or amend any configuration settings, as required.

It is recommended that the agent instance name correspond to the technology pack for the loader. The log file directory and log file name must correspond to the itm.file and itm.folder values given in the loader’s properties file. See Loaders.

2. Click FINISH.

A dialog is displayed to indicate the deployment has been queued.

Gateway agent configuration

1. Provide a Gateway agent instance name.

2. Click OK.


3. Provide expressions for the Vendor Name, and Vendor Release name.

The expression for vendor sub-system name must be consistent with the vendor directory name in the configuration directory.

The expression for vendor Release must be consistent with the release directory name in the configuration directory.

A Gateway Agent Instance is able to monitor multiple Gateway Configurations. Include wildcards in the expression for multiple vendor and releases.

Important: Ensure that one Gateway Configuration is being monitored by one Gateway Agent Instance only. If a Gateway Configuration is being monitored by multiple Gateway Agent Instances, duplicate records of the same Gateway Configuration will be reported in the overall Tivoli Netcool Performance Manager Gateway workspace for every Gateway Agent node.

4. Click NEXT.


5. Provide the Username and Group name.

The Username must be the same as the username used for the Gateway Framework installation. This is usually: virtuo.

The Group name. Any group name can be used. The group name is usually: virtuo.

6. Click FINISH.

4.2.2 Local installation

To install an agent locally on a server, the procedure is similar to installing Tivoli Netcool Performance Manager agents on the ITM server. Refer to Chapter 6 of the ITM Installation and Setup Guide, for more information on installing agents locally.

Note: Each Tivoli Netcool Performance Manager agent once installed must be configured. Refer to the ITM Installation and Setup Guide, for more information.


5 Tivoli Netcool Performance Manager Enablement

This chapter describes enabling Tivoli Netcool Performance Manager for ITM.

This chapter describes how to:

• Enable collection of ITM metrics• Start Tivoli Netcool Performance Manager agent service

5.1 Enable collection of ITM metricsEnable collection of ITM metrics for each of the agents you intend to use.

• Application server• Loaders• Gateways

5.1.1 Application server

Note: Distributed systems only. In a distributed installation, this section need only be performed on the application server.

By default, the output of metrics required for the ITM agents to collect application server data is disabled. The property itm.logging.enabled must be set to true to enable the collection of metrics for ITM.

The property itm.logging.enabled is contained in the ITM properties file located on the Tivoli Netcool Performance Manager server in: $WMCROOT/conf/itm/default.properties.

Note: Following an update to the ITM properties file the application server must be re-started. Use the sap utility to restart the application server, for example on the application server as user virtuo:

sap stop assap start as


See the Tivoli Netcool Performance Manager Administration Guide.

The contents of this file are described below.

Note: If filenames are changed, the configuration of the Tivoli Netcool Performance Manager applica-tion server agent must be changed using the same values.

Coverage file

Each line in the coverage.txt file must be as follows:

Table 4: ITM properties

Property Descriptionitm.logging.enabled Enable or disable itm logging. Default is false, true

turns on itm logging. Any other value turns it off.itm.logging.dir The directory that itm logs will be written to. Default is

appl/virtuo/logs/itm.itm.logging.report.userroles Log user role and group information when logging report

execution metrics, true turns on user and role logging. Any other value turns it off. Default is true.

itm.logging.report The name of the log file for report execution metrics. The default is itm-reports.log.

itm.logging.usage The name of the log file for usage metrics. Default is itm-usage.log.

itm.logging.sbh.completion The name of the log file for stored busy hour completion metrics Default is itm-sbh-completion.log.

itm.logging.sbh.completion.interval Frequency in minutes to log busy hour completion metrics. Default is 60.

itm.logging.sbh.execution The name of the log file for stored busy hour execution metrics Default is itm-sbh-execution.log.

itm.logging.summary.completion The name of the log file for summary completion metrics. Default is itm-summary-completion.log.

itm.logging.summary.completion.interval Frequency in minutes to log summary completion metrics. Default is 60.

itm.logging.summary.execution The name of the log file for summary execution metrics. Default is itm-summary-execution.log.

itm.logging.raw.coverage The name of the log file for raw coverage metrics. Default is itm-raw-data-coverage.log.

itm.logging.coverage.list The name of the file containing the list of KPIs to calculate coverage for. See below Coverage file. Default is /appl/virtuo/conf/itm/coverage.txt.


Vendor;Technology;Counter;Rollup Entity Name;Interval;Grace Period

The properties are:

• Vendor: Entities will be filtered by vendor name. There is no pattern matching, the name must match exactly. 'Neutral' is not a valid vendor name in this context. Vendor Neutral KPIs must specify a Vendor Specific name as the entity vendor.

• Technology: Entities will be filtered by technology name. There is no pattern matching, the name must match exactly.

• Counter: A KPI to calculate coverage for. It must be a raw counter, not a Pcalc or UDC.• Rollup Entity Name: This must be a parent of the KPI's entity. It cannot be the same as the

entity’s KPI.• Interval: How long the period used to calculate coverage is. This should be aligned to the

interval of the data it is monitoring. It should be the same as, or a multiple of, the data interval.• Grace Period: How far back in time to go to select the period. This should match the expected

loading latency of the KPI.For example:Ericsson;GSM;Cell.Ericsson.Traffic_Channels_HalfRate.Traffic_Halfrate_accumulator;BSC;30;60

In this case, the interval is 30 and the grace period is 60. If the current time is 14:02, the grace period will take this back to 13:02. Aligning the interval to the hour gives 13:00. The time period covered will be 13:00 to 13:30.See the Tivoli Netcool Performance Manager Administration Guide for more information on the grace period.

Cron jobsCoverage file

The coverage file is read, and coverage metrics produced by, the following cron job:2,17,32,47 * * * * /appl/virtuo/bin/run_itm_rawcoverage_logger > /dev/null 2>&1

By default this cron job runs every 15 minutes, 2 minutes after the quarter hour. The execution schedule can be altered to suit the data being loaded.

Coverage frequency

A further cron job controls the frequency and length of period coverage:1,16,31,46 * * * * /appl/virtuo/bin/run_itm_usage_logger 15 > /dev/null 2>&1

run_itm_usage_logger tracks the user and report execution counts. By default it runs every 15 minutes, 1 minute after the quarter hour and covers the previous 15 minute period. Generally, if the scheduling frequency is changed the parameter passed to the run_itm_usage_logger script should be changed to match.

Tivoli Netcool Performance Manager Enablement 21

5.1.2 Loaders

Note: Distributed systems only. In a distributed installation, this section need only be performed on the loader server.

By default the output of ITM metrics from Tivoli Netcool Performance Manager loaders is disabled. To enable the output of ITM metrics from a loader, a property for the loader’s configuration must be edited.

This property must be changed for each loader that is to be monitored. Properties in a loader configuration are set using the loader_admin tool’s load and unload parameters.

To change a loader’s configuration:

1. Export the existing set of loader properties on the Tivoli Netcool Performance Manager server, as user virtuo:# loader_admin -unload properties.xml -instance <instance_name>

The properties.xml file contains four properties relating to ITM:• itm.enabled - indicates whether to output metrics for ITM, true enables output false disables

output.• itm.file - the name of the file to output metrics to. The file name defaults to an amalgam of the

technology pack name and version. It is recommended that each loader instance for a technology pack on a server writes to the same file. This results in one ITM agent instance being used to monitor each technology pack on a server. In this case, in the TEP navigator tree is broken down to technology pack level. If required, each loader instance can write to its own file. In this case an ITM agent instance would be needed for each file. It is also possible for all loaders to write to a single file, with only one agent instance required.

• itm.folder - the folder to locate the itm.file property in.• itm.interval - how often to write metrics to the ITM file. Ideally, this should be the same as the

interval of the lif files being loaded by the loader. If multiple intervals are loaded, the interval should be a logical multiple. For example, if a loader is loading 20 minute data and 30 minute data, the itm.interval should be 60.

2. Edit the properties.xml file to set the itm.enabled value to true.

Save the file.

3. Update the instance configuration, as user virtuo:# loader_admin -load properties.xml -instance <instance_name>

Note: As described by the loader_admin usage statement, it is possible to update the configuration for all instances at one time. This may be easier if ITM logging is being turned on for all agents.

Note: When new loader instances are added ITM output will be disabled by default, regardless of the settings for existing instances.


4. Loader instances must be restarted to apply any changes to the ITM configuration, as user virtuo:sap stop <loader_name>

sap start <loader_name>

When ITM output is enabled, the loader will write metrics to the ITM file after each interval. The interval is aligned to the start of the hour that the loader was started in, for example if the interval is set to 15 and the current time is 13:10, the first metrics written will be output at 13:15, then 13:30 and so on.


5.1.3 Gateways

Note: Distributed systems only. In a distributed installation, this section need only be performed on the gateway server.

The NotificationConfig.pm file is used to configure gateway event notifications. These notifications must be configured to be sent to the correct directory in ITM. See the Gateway Framework User Guide for more information.

The notification target must be defined for each gateway, on the appropriate Tivoli Netcool Performance Manager server.

To define the notification target:

1. Copy a sample NotificationConfig.pm file from the $GATEWAY_ROOT/gateway-framework/example/NotificationConfig.pm into the vendor sub-system and release configuration directory, e.g. $GATEWAY_ROOT/config/<vendor-subsys>/<release>/

2. Edit the NotificationConfig.pm file, for the rule @rules_ITM on the configuration entry NOTIFICATION_TARGET for the vendor sub-system target log file:

my @rules_ITM = (

{

RULE_TYPE => 'ITM_Notification',

RULE_DESC => 'ITM Notification',

NOTIFICATION_TYPE => 'Alarm|Event',

NOTIFICATION_COMMAND => 'itmlog', # command line script

NOTIFICATION_TARGET => '/appl/virtuo/logs/itm/<vendor-subsys>_<release>',

ENABLE_PER_FILE_NOTIFICATION => 1,

},

);

Where <vendor-subsys> and <release> is consistent with the configuration directory of the vendor sub-system and release.

3. Edit the NotificationConfig.pm, for the sub-routine notification_config() to return the reference to @rules_ITM:

sub notification_config {

return \@rules_ITM;

}

External script customization

The Tivoli Netcool Performance Manager gateway agent uses an external script itmlog.sh within the gateway framework installation. The script is located in:

/appl/virtuo/gways/gateway-framework/vstart


By default, the itmlog.sh script will process the notification log files of the current gateway run or the last gateway run for each gateway configuration.

To report previous gateway notification logs in ITM, the itmlog.sh script can be customized to process the past number of hours of logs. The PASS_HOUR variable in the itmlog.sh script is used to define the number of past hours of logs to process.

Edit the itmlog.sh file and define the number hours for the variable PASS_HOUR. For example:# Sets a time period to collect logs for the pass N hours

export PASS_HOUR=2

5.2 Start Tivoli Netcool Performance Manager agent serviceThe agent service must be started for each Tivoli Netcool Performance Manager agent on each monitored Tivoli Netcool Performance Manager server, before performance metrics can be displayed in ITM.

Agents can be configured and started on a Tivoli Netcool Performance Manager server by running the command: <ITM_INSTALL_LOCATION>/bin/itmcmd manage

Use MANAGE TIVOLI ENTERPRISE MONITORING SERVICES to select and start an agent.

For example, to start a gateway agent instance, select the agent, right click and select START SERVICE.

Refer to your ITM documentation for more information on using ITM.



6 Gateways ITM Agent Historical Data

The Gateways ITM Agent is based on the script data source, and only the current or last Gateway process records are displayed. To see previous Gateway processes, you need to enable at least short-term historical data collection and storage. Short-term storage can store up to 24 hours of data, and long-term storage can store more than 24 hours of storage if necessary.

To enable historical data collection, complete the following steps:

• Enable Historical Data Collection for the attributes• Update queries for the workspace tables and charts• Set up pruning to delete old data in Tivoli Data Warehouse (TDW)

Important: Before enabling historical data collection, set the PASS_HOUR variable in /appl/virtuo/gways/gateway-framework/vstart/itmlog.sh back to the default value 0. If the itmlog.sh is config-ured to return more than just the most recent or currently running instances data, records from completed Gateway process are continuously reported and will be repeatedly collected and delivered to the ware-house. For details on Gateway agent external script customization, see Gateways on page 24.


6.1 Enabling Historical Data Collection To enable the collection of historical data:

1. Click the HISTORY CONFIGURATION icon in the toolbar, the HISTORY COLLECTION CONFIGURATION dialog box is displayed as shown in Figure 1.

Figure 1: History Collection Configuration

2. Select KNI GATEWAY, KNI PARSER and KNI TRANSFER as shown, and click CONFIGURE GROUPS and then START COLLECTION.

3. Click CLOSE.


6.2 Updating Time Spans for QueriesYou must update the queries for the bar/line charts and tables with the time spans.

Note: For some common queries, it may be possible to use the option APPLY TO ALL VIEWS ASSOCI-ATED WITH THIS VIEW’S QUERY. For more information, refer to the ITM documentation.

6.2.1 Updating Time Spans for Bar and Line Charts

Update the time span for the bar chart in the Tivoli Netcool Performance Manager Gateways workspace shown in Figure 4, and the line chart in "Gateway Instance" workspace shown in Figure 3.

Figure 2: Tivoli Netcool Performance Manager Gateways workspace

Gateways ITM Agent Historical Data 29

Figure 3: Gateway Instance workspace


To update the time span for a query:

1. Click the icon in the chart, the SELECT THE TIME SPAN dialog box is displayed as shown in Figure 4.

Figure 4: Select the Time Span

2. Select the REAL TIME PLUS LAST check box and enter a time span.

3. Click OK.

4. Save the workspace.

6.2.2 Updating Time Spans for Tables

Perform the following procedure for the FILE TRANSFERS and FILE PARSING tables in both the Tivoli Netcool Performance Manager Gateway and Gateway Instance workspaces.

1. Click the icon in the table.


2. Select the LAST check box and enter a time span.

3. Select the USE DETAILED DATA check box and in the TIME COLUMN drop down list, select TIMESTAMP

4. Click OK.

5. Save the workspace.


6.3 Managing Historical Data by PruningWith historical data being collected from agents and sent to Tivoli Data Warehouse (TDW), the storage space used in TDW will continue to grow if it is not managed. To manage this on an ongoing basis, you must set up pruning of TDW data according to any relevant data policies. For more detailed information, see the IBM Tivoli Monitoring: Administrator Guide.



7 Alarm Integration

The Tivoli Netcool Performance Manager ITM agents do not contain alarm definitions. Alarm definitions can be added to the agents as the customer sees fit. For details of how to configure alarms and actions, refer to your ITM documentation.

Tivoli Netcool Performance Manager provides a portable package that enables the generation of internal Tivoli Netcool Performance Manager alarms from the command line on a non-Tivoli Netcool Performance Manager core server. The recommended method of handling alarms depends on the existing application infrastructure:

• Customer already has ITM and Netcool/OMNIbus• Customer has Netcool/OMNIbus and other non-IBM IT monitoring solutions• Customer does not have Netcool/OMNIbus or ITM• Customer has ITM but other non-IBM Fault Management solution

7.1 Existing application infrastructureCustomer already has ITM and Netcool/OMNIbus

In this case the Tivoli Netcool Performance Manager agents can be integrated into the customer's existing ITM infrastructure. The customer may already have ITM / Netcool/OMNIbus integration configured.

Customer has Netcool/OMNIbus and other non-IBM IT monitoring solutions

In this case a single-server ITM solution would be deployed to monitor the Tivoli Netcool Performance Manager servers only. The alarms generated by this ITM deployment can be directly integrated into the customer's Netcool/OMNIbus system using the existing Tivoli EIF probe.

Customer does not have Netcool/OMNIbus or ITM

In this case a single-server ITM solution would again be deployed to monitor the Tivoli Netcool Performance Manager servers. Tivoli Netcool Performance Manager internal alarms can be generated using the alarm package, and the standard Tivoli Netcool Performance Manager alarm export functions can be used to forward these alarms to external systems, for example using E-Mail or SNMP.


Customer has ITM but other non-IBM Fault Management solution

In this case the custom Tivoli Netcool Performance Manager agents can be integrated into the customer's existing ITM infrastructure. The customer may already have ITM integration configured with an external non-IBM fault management system.

7.2 Generating the alarm packageTo generate the package:

1. Execute the following as user virtuo:$WMCROOT/admin/common/install/scripts/create_alarmgenerator_package -wmcr $WMCROOT

The package created is: /appl/virtuo/admin/itm/pkg/tnpmw_alarm_generator.tar

2. Copy the generated package to the server where alarm functionality is required.

Note: The package includes the password provided in the database configuration. If this password has not been encoded, the plain text password will be readable on the target server.

3. Untar the archive on the target server.

To generate an alarm from the target server:

1. Execute the following command:<package_loc>/bin/alarm_generator -g <notification_id> <ev_source> <ev_type> <monitored_attribute> <managed_object_class> <managed_object_instance> <alarm_predicate> <probable_cause> <specific_problem> <additional_text> <trend_indication> <report_id> <alarm_severity> [event_time]

Where:Table 5: Alarm generator parameters

Parameter CLI format PL-SQL format Description Defaultnotification_id Integer INTEGER Alarm notification Id. None.ev_source String VARCHAR2(255) Event/Alarm source. None.ev_type String VARCHAR2(255) Event type, see Event types. None.monitored_attribute String NUMBER Attribute value that triggered

the alarm, for example 51.3.None.

managed_object_class String VARCHAR2(255) Entity name, for example cell. None.managed_object_instance

String VARCHAR2(255) Entity instance name/local key, for example 12345.

None.

alarm_predicate String VARCHAR2(255) Alarm predicate. None.probable_cause String VARCHAR2(255) Probable alarm cause, see Prob-

able causes.None.

specific_problem String VARCHAR2(255) Specific alarm problem. None.additional_text String VARCHAR2(255) Any additional text. None.


Note: ITM actions can be configured to call the script above in order to generate internal Tivoli Netcool Performance Manager alarms.

Note: The alarm spool daemon asd sap process must be running in order to raise alarms in Tivoli Net-cool Performance Manager. The daemon is started and stopped, as user virtuo using the commands sap start asd and sap stop asd

Note: The script requires JavaTM Runtime Environment (JRE) version 1.5.0. The PATH set in the environ-ment must be use the 1.5.0 version of the Java executable.

Parameter values - lists

A number parameters have a defined values, including:

• Event types• Probable causes• Trend Indications• Severity

Event types

Note: Tivoli Netcool Performance Manager may accept non-standard values, but alarms with non-stan-dard values cannot be forwarded to SNMP recipients, such as Tivoli Netcool OMNIbus.

trend_indication String VARCHAR2(255) 'more severe' (raised) or 'less Severe' (cleared), see Trend Indications.

None.

report_id Integer NUMBER Associated report Id, given using alarmapi_admin -r.

None.

alarm_severity String VARCHAR2(255) Alarm severity, see Severity. None.event_time String:

yyyyMMddHHmmss.DATE Optional. Alarm time. When

the alarm reflects an event that happened in the past, this should be set to the event time. If not provided, it is assumed to be the current time.

Current time.

Table 5: Alarm generator parameters

Parameter CLI format PL-SQL format Description Default

Alarm Integration 37

The following table lists all the possible values for event types.

Probable causes

The following table lists all the possible values for probable_cause.

Table 6: Event Types

Event typeCommunications

QualityOfService

ProcessingError

Equipment

Environmental

Table 7: Probable Causes

Probable cause Probable causeadapterError lossOfRedundancy

airCompressorFailure lossOfSignal

airConditioningFailure lossOfSignalX733

airDryerFailure lossOfSynchronisation

aIS lowBatteryThreshold

antennaFailure lowCablePressure

applicationSubsystemFailture lowFuel

applicationSubsystemFailure lowHumidity

authenticationFailure lowTemperatue

backplaneFailure lowWater

bandwidthReduced materialSupplyExhausted

bandwidthReducedX733 memoryMismatch

batteryChargingFailure modulationFailure

batteryDischarging multiplexerProblem

batteryFailure multiplexerProblemX733

breachOfConfidentiality nEIdentifierDuplication

broadcastChannelFailure nonRepudiationFailure

cableTamper other

callEstablishmentError outOfCPUCycles

callSetUpFailure outOfHoursActivity

commercialPowerFailure outOfMemory

communicationsProtocolError outOfMemoryX733

communicationsSubsystemFailure outOfService

configurationOrCustomisationError outputDeviceError

configurationOrCustomizationError pathTraceMismatch

congestion payloadTypeMismatch

congestionX733 performanceDegraded

connectionEstablishmentError powerProblem

coolingFanFailure powerProblems

coolingSystemFailure powerSupplyFailure

corruptData pressureUnacceptable

coruptData proceduralError

cpuCyclesLimitExceeded processorProblem

databaseInconsistency processorProblems


dataSetOrModemError protectingResourceFailure

dataSetProblem protectionMechanismFailure

degradedSignal protectionPathFailure

degradedSignalX733 pumpFailure

delayedInformation pumpFailureX733

demodulationFailure queueSizeExceeded

denialOfService realTimeClockFailure

diskFailure receiveFailure

dteDceInterfaceError receiveFailureX733

duplicateInformation receiverFailure

enclosureDoorOpen receiverFailureX733

enclosureDoorOpenX733 rectifierFailure

engineFailure rectifierHighVoltage

equipmentIdentifierDuplication rectifierLowFVoltage

equipmentMalfunction reducedLoggingCapability

excessiveBER remoteAlarmInterface

excessiveErrorRate remoteNodeTransmissionError

excessiveResponseTime remoteNodeTransmissionErrorX733

excessiveRetransmissionRate replaceableUnitMissing

excessiveVibration replaceableUnitProblem

explosiveGas replaceableUnitTypeMismatch

externalEquipmentFailure resourceAtOrNearingCapacity

externalIFDeviceProblem responseTimeExcessive

externalPointFailure retransmissionRateExcessive

farEndReceiverFailure routingFailure

fileError sfwrDownloadFailure

fileErrorX733 sfwrEnvironmentProblem

fire signalLabelMismatch

fireDetected signalQualityEvaluationFailure

fireDetectorFailure smoke

flood softwareError

framingError softwareErrorX733

framingErrorX733 softwareProgramAbnormallyTerminated

frequencyHoppingFailure softwareProgramError

fuseFailure storageCapacityProblem

generatorFailure storageCapacityProblemX733

heatingVentCoolingSystemProblem synchronizationSourceMismatch

highHumidity systemResourcesOverload

highTemperature temperatureUnacceptable

highWind terminalProblem

humidityUnacceptable thresholdCrossed

iceBuildUp timeoutExpired

informationMissing timingProblem

informationModificationDetected timingProblemX733

informationOutOfSequence toxicGas

inputDeviceError toxicLeakDetected

inputOutputDeviceError tranceiverFailure

intrusionDetection transmissionError

invalidMessageReceived transmiterFailure


Probable cause Probable cause

Alarm Integration 39

Trend Indications

The following table lists all the possible values for trend_indication.

Severity

The following table lists all the possible values for alarm_severity.

iODeviceError transmitFailure

keyExpired transmitFailureX733

lanError transmitterFailure

leakDetected trunkCardProblem

lineCardProblem unauthorizedAccessAttempt

localNodeTransmissionError unavailable

localNodeTransmissionErrorX733 underlayingResourceUnavailable

lossOfFrame underlyingResourceUnavailable

lossOfFrameX733 unexpectedInformation

lossOfMultiFrame ventilationsSystemFailure

lossOfPointer versionMismatch

lossOfRealTimel versionMismatchX733

Table 8: Trend Indications

Trend IndicationMore Severe

Less Severe

No Change

Table 9: Severity values

SeverityCleared

Indeterminate

Critical

Major

Minor

Warning


Probable cause Probable cause


8 Tivoli Netcool Performance Manager agent metrics and ITM navigation layout

This chapter describes the metrics collected for each Tivoli Netcool Performance Manager agent, the log files used and the default ITM navigation layout.

This chapter describes:

• Loader metrics and navigation layout• Application server metrics and navigation layout• Gateway server metrics and navigation layout

8.1 Loader metrics and navigation layout

8.1.1 Loader agent log files

The default log file directory on the Tivoli Netcool Performance Manager loader logs is:/appl/virtuo/logs/loader

The ITM monitoring agent for Tivoli Netcool Performance Manager loaders has the following attributes:

• Loader Name• Technology Pack Name• Technology Pack Version• Reporting Start Time• Reporting End Time• Reporting Duration• Interval Start Time• Interval End Time• Interval Duration• File Processing Start Time• File Processing End Time


• File Processing Duration• Number of LIF files processed• Total Size of LIF files processed• Number of LIF files successfully processed• Percentage LIF files successfully processed• Number of LIF files unsuccessfully processed• Percentage LIF files unsuccessfully processed• Minimum Latency - the time between Interval End Time and File Processing Start Time• Maximum Latency - the time between Interval End Time and File Processing End Time• Late - "Yes" if Maximum Latency is greater than Interval Duration. "No" otherwise.

8.1.2 Default ITM navigation layout

An example default navigation layout is:

Enterprise UNIX Systems <<Hostname>> Tivoli Netcool Performance Manager Loaders <<Instance Name, e.g. technology pack>> File Processing

To configure ITM workspaces refer to your ITM product documentation.

Default Loader workspace

The default workspace for the Tivoli Netcool Performance Manager application Loaders item in the ITM Navigator contains four frames in addition to the default Navigator frame, as follows:

• Stacking bar chart showing loader file processing, aggregated for all technology packs on the platform:• LIF files successfully processed• LIF files unsuccessfully processed

• Bar chart showing maximum data latency, aggregated for all tech packs on the platform • File Processing Latency

• Table showing main loader file processing attributes:• Loader Name• Technology Pack Name• Technology Pack Version• Reporting Start Time• Interval Start Time• File Processing Start Time


• Number of LIF Files Successfully Processed• Percentage of LIF Files Successfully Processed• Number of LIF Files Unsuccessfully Processed• Percentage of LIF Files Unsuccessfully Processed

• Table showing loader data latency attributes:• Loader Name• Tech Pack Name• Tech Pack Version• Interval Start Time• File Processing Duration• Minimum Latency• Maximum Latency• Late

The corresponding cell within the file processing and latency tables is red for the following conditions:

• Table showing main loader file processing attributes:• Number of LIF Files Successfully Processed = 0• Number of LIF Files Unsuccessfully Processed > 1

• Table showing loader data latency attributes:• Late is set to 'Yes'

Default technology pack workspace

The default workspace for a technology pack selected beneath a loader contains four frames in addition to the default Navigator frame, as follows:

• Bar chart showing -• Total number of LIF files processed• LIF files successfully processed• LIF files unsuccessfully processed

• Bar chart showing - • File Processing Latency

• Table showing loader file processing attributes - • Loader Name• Technology Pack Name• Technology Pack Version• Reporting Start Time• Interval Start Time• File Processing Start Time

Tivoli Netcool Performance Manager agent metrics and ITM navigation layout 43

• Number of LIF files Successfully Processed• Percentage of LIF Files Successfully Processed• Number of LIF files unsuccessfully processed• Percentage of LIF Files Unsuccessfully Processed

• Table showing loader data latency attributes - • Loader Name• Technology Pack Name• Technology Pack Version• Interval Start Time• File Processing Duration• Minimum Latency• Maximum Latency• Late

The corresponding cell within the file processing and latency tables is red for the following conditions:

• Table showing main loader file processing attributes:• Number of LIF Files Successfully Processed = 0• Number of LIF Files Unsuccessfully Processed > 1

• Table showing loader data latency attributes:• Late is set to 'Yes'

8.2 Application server metrics and navigation layout

8.2.1 Application server agent log files

The default log file directory on the Tivoli Netcool Performance Manager application server is:/appl/virtuo/logs/itm

Containing the following logs.Table 10: Application server log files

Log DescriptionUsage Usage information includes:

• Time interval• Maximum number of user sessions• Number of active users• Number of scheduled reports run• Number of ad-hoc reports run


Reports For each report executed, the following is logged:• Report Id• Report Name• Report Folder• Report Type - ad-hoc or scheduled.• User - user that ran or scheduled the report.• Roles - the user's role(s).• Groups - the user's group(s).• Start Time - either the scheduled start time or the time a user executed an

Immediate report• Actual Start Time - the time the report was started by the system. This could

be significantly different on a busy system.• Actual End Time - the end time.• Preparation Time - the length of time from the actual start time to just before

the Reap query.• Resolution Time - the length of time the Reap query takes• Execution Time - the length of time the final report calculation takes.• Number of Entities - the number of entities returned by the Reap query, not

necessarily the same as the number in the final report.• Number of KPIs - the number of KPIs requested.• Number of Rows - the number of rows returned by the report, including roll

ups.• Time Interval

Raw data coverage Raw data coverage information includes:• Timestamp• Vendor• Technology• KPI• Rollup Node Name• Percent Complete

Busy hour execution Busy hour execution information includes:• Busy Hour Name• Start Time• End Time• Duration• Type (Daily, Weekly, Monthly)• Result• Number of rows

Busy hour completion Busy hour completion information includes:• Timestamp (Date / Time)• Total number of Busy Hours• Number of Busy Hours complete• % Busy Hours complete

Table 10: Application server log files

Log Description




Enterprise UNIX Systems <<Hostname>> Tivoli Netcool Performance Manager Application Server Usage Reports Coverage


The default workspace opened when the Tivoli Netcool Performance Manager application item is selected in the ITM Navigator contains four frames in addition to the default Navigator frame, as follows:

• Bar chart showing report execution metrics (top ten)• Bar chart showing vendor raw data coverage (aggregated)• Table showing user session information -

• Time Interval• Maximum number of user sessions• Number of active users• Number of scheduled reports run• Number of ad-hoc reports run

• Table showing data coverage attributes (row per node) - • Timestamp

Summary execution Summary execution information includes:• Summary Name• Start Time• End Time• Duration• Type (Hourly, Weekly, Monthly)• Result• Number of rows

Summary completion Summary completion information includes:• Timestamp (Date / Time)• Total number of Summaries• Number of Summaries complete• % Summaries complete

Table 10: Application server log files

Log Description


• Vendor• Technology• KPI• Rollup Node Name• Percent Complete

Usage

The default workspace for Usage contains one frame in addition to the default Navigator frame, as follows:

• Table showing usage attributes• Time Interval• Maximum number of user sessions• Number of active users• Number of scheduled reports run• Number of ad-hoc reports run

The corresponding cell within the data coverage table is red for the following condition:

Table showing main data coverage attributes -

• % Complete < 95

Reports

The default workspace for Reports contains five frames in addition to the default Navigator frame, as follows:

• Bar chart showing ad-hoc report attributes (top ten)• Bar chart showing scheduled report attributes (top ten)• Bar chart showing average report execution times• Table showing user session attributes• Table showing report execution attributes

Coverage

The default workspace for Coverage contains three frames in addition to the default Navigator frame, as follows:

• Bar chart showing vendor raw data coverage metrics• Table showing busy hour percent completion

• Timestamp (Date / Time)• Total number of Busy Hours• Number of Busy Hours complete• % Busy Hours complete


• Table showing summary percent completion• Timestamp (Date / Time)• Total number of Busy Hours• Number of Busy Hours complete• % Busy Hours complete

• Table showing busy hour data coverage metrics • Busy Hour Name• Start Time• End Time• Duration• Type (Daily, Weekly, Monthly) • Result• Number of rows

• Table showing summary data coverage metrics • Summary Name• Start Time• End Time• Duration• Type (Daily, Weekly, Monthly)• Result• Number of rows

Using ITM threshold definitions, cells within the busy hour execution table are red for the following conditions:

• Number of rows = 0 AND Result != 'Completed'

Using ITM threshold definitions, cells within the summary execution table are red for the following conditions:

• Number of rows = 0 AND Result == 'failed'

8.3 Gateway server metrics and navigation layout

8.3.1 Gateway agent log files

The default log file directory on the Tivoli Netcool Performance Manager gateways logs is:/appl/virtuo/logs/itm

The ITM monitoring agent for Tivoli Netcool Performance Manager gateways logs the following attributes:

• Vendor SubSystem (e.g. nokia-utran)


• Vendor Release (e.g. 6.0)• Gateway PID• Gateway Stages included:

• TRANSFER-IN• PARSER• TRANSFER-OUT

• Period of Execution (crontab)• Execution Start Time• Execution End Time• Execution Duration• Status: Normal Exit or Aborted/Killed

Transfer IN/OUT

The following information is logged for the Transfer parts of the gateway:

• Vendor SubSystem (e.g. nokia-utran)• Vendor Release (e.g. 6.0)• Gateway PID• Transfer Rule Name• Transfer Type: IN or OUT• Transfer Protocol (FTP, SCP, RCP, CP)• Transfer Host (IP)• Transfer Start Time• Transfer End Time• Number of files transferred• Total Size of files transferred• Maximum file size

Tivoli Netcool Performance Manager gateways agents can be configured to log per-file information. If configured, the following per-file information is logged:

• In File Name• In File Size• In Filename Time Stamp (if available from source)• File Processing Start Time• File Processing End Time• Out File Name• Out File Size


Parser

The following information is logged for the parser part of the gateway:

• Vendor SubSystem (e.g. nokia-utran)• Vendor Release (e.g. 6.0)• Gateway PID• Engine Rule Name• Engine Start Time• Engine End Time• Number of input files processed• Total Size of input files processed• Number of PIF files produced• Total Size of PIF files produced• Number of LIF files produced• Total Size of LIF files produced

Tivoli Netcool Performance Manager gateways agents can be configured to log per-file information. If configured, the following per-file information is logged:

• Input File Name• Input File Size• Input Filename Time Stamp (if available from source)• File Processing Start Time• File Processing End Time• Out File Name(s) : PIFs and LIFs• Out File(s) Size



Enterprise UNIX Systems <<Hostname>> Tivoli Netcool Performance Manager Gateways <<Instance Name, e.g. vendor subsystem>> File Processing



Default Gateways workspace

The default workspace for the Tivoli Netcool Performance Manager application Gateways item in the ITM Navigator contains three frames in addition to the default Navigator frame, as follows:

• Stacked bar chart showing gateway phase durations, aggregated for all vendor subsystems on the platform:• Transfer IN• Parser• Transfer OUT

• Table showing main file transfer attributes (for all gateways, all vendor subsystems):• Vendor SubSystem Name• Transfer Rule Name• Transfer Type (IN/OUT)• Transfer Start Time• Transfer End Time• Number of Files Transferred

• Table showing main PIF and LIF file processing attributes (for all gateways, all vendor subsystems):• Vendor SubSystem Name• Engine Rule Name• Engine Start Time• Engine Duration• Number of PIF Files Produced• Number of LIF Files Produced

The corresponding cell within the attributes table is red for the following conditions:

• Number of Files Transferred IN = 0• Number of Files Transferred OUT = 0• Number of LIF Files Produced = 0

Individual instance

The default workspace for an individual Gateways instance contains three frames in addition to the default Navigator frame, as follows:

• Line chart showing :• # Files Transferred IN• # LIF Files Generated

• Table showing transfer attributes (for all gateways monitored by that agent):• Vendor SubSystem Name• Transfer Rule Name


• Transfer Type (IN/OUT)• Transfer Start Time• Transfer End Time• Number of Files Transferred

• Table showing PIF and LIF attributes (for all gateways monitored by that agent):• Vendor SubSystem Name• Engine Rule Name• Engine Start Time• Engine End Time• Number of PIF Files Produced• Number of LIF Files Produced

The corresponding cell within the attributes table is red for the following conditions:

• Number of Files Transferred IN = 0• Number of Files Transferred OUT = 0• Number of LIF Files Produced = 0


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785,U.S.A.

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.3-2-12, Roppongi, Minato-ku, Tokyo 106-8711Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and


products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information in softcopy format, the photographs and color illustrations may not appear.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

55


Printed in the Republic of Ireland.

IBM©

©© Copyright IBM Corp. 2007, 2009 57

Documents

Tivoli Netcool Performance Manager: IBM Tivoli Monitoring … · 2010-09-07 · 2 IBM Tivoli Netcool Performance Manager: IBM Tivoli Monitoring Integration Guide - Wireless Component