IBM 1.4.3 Tivoli Netcool Performance Manager Tivoli Monitoring Integration Guide

IBM Tivoli Netcool Performance Manager 1.4.3

Wireless Component

Document Revision R2E1

Tivoli Monitoring Integration Guide

IBM

Note

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

© Copyright IBM Corporation 2007, 2017.

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

Contents

About This Documentation . . . . . . v

Audience .

.

.

.

.

.

.

.

.

.

.

.

.

.

. v

What this publication contains .

.

.

.

.

.

.

. v

The Tivoli Netcool Performance Manager - Wireless component user publications.

.

.

.

.

.

.

.

. vi

Service Management Connect .

.

.

.

.

.

.

. vi

Tivoli Netcool Performance Manager technical training .

.

.

.

.

.

.

.

.

.

.

.

.

.

. vii

Support information .

.

.

.

.

.

.

.

.

.

. vii

Conventions used in this publication .

.

.

.

.

. vii

Typeface conventions .

.

.

.

.

.

.

.

.

. vii

Chapter 1. IBM Tivoli Monitoring

Integration Overview . . . . . . . . . 1

Chapter 2. IBM Tivoli Monitoring

Integration Prerequisites . . . . . . . 3

Chapter 3. Tivoli Netcool Performance

Manager Agent Installation and

Configuration . . . . . . . . . . . . 5

Installing the Tivoli Netcool Performance Manager

Agents .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 5

Upgrading the Tivoli Netcool Performance Manager

Agents .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 7

Installing the Tivoli Netcool Performance Manager agent by remote deployment .

.

.

.

.

.

.

.

. 8

Configuring the application server agent .

.

.

. 9

Configuring the loader agent .

.

.

.

.

.

. 10

Configuring the gateway agent .

.

.

.

.

.

. 12


Manager Enablement . . . . . . . . 15

Enabling the collection of IBM Tivoli Monitoring metrics .

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 15

Application server .

.

.

.

.

.

.

.

.

.

. 15

Loaders.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 17

Gateways .

.

.

.

.

.

.

.

.

.

.

.

.

. 19

Starting the Tivoli Netcool Performance Manager agent service .

.

.

.

.

.

.

.

.

.

.

.

.

. 20

Chapter 5. Processing the Gateways

IBM Tivoli Monitoring Agent Historical

Data . . . . . . . . . . . . . . . . 21

Enabling Historical Data Collection .

.

.

.

.

. 21

Updating Time Spans for Queries .

.

.

.

.

.

. 22

Updating Time Spans for Bar and Line Charts .

. 22

Updating Time Spans for Tables .

.

.

.

.

. 24

Managing Historical Data by Pruning .

.

.

.

. 25

Chapter 6. Integrating Alarm . . . . . 27

Existing application infrastructure .

.

.

.

.

.

. 27

Customer already has IBM Tivoli Monitoring and

Netcool/OMNIbus .

.

.

.

.

.

.

.

.

.

. 27

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

.

.

.

.

. 27

Customer does not have Netcool/OMNIbus or

IBM Tivoli Monitoring.

.

.

.

.

.

.

.

.

. 28

Customer has IBM Tivoli Monitoring but other non-IBM Fault Management solution .

.

.

.

. 28

Generating the alarm package .

.

.

.

.

.

.

. 28

Parameter values - lists .

.

.

.

.

.

.

.

. 29


Manager agent metrics and IBM Tivoli

Monitoring navigation layout . . . . . 35

Loader metrics and navigation layout .

.

.

.

. 35

Loader agent log files .

.

.

.

.

.

.

.

.

. 35

Default IBM Tivoli Monitoring navigation layout 36

Application server metrics and navigation layout .

. 38

Application server agent log files .

.

.

.

.

. 38


Gateway server metrics and navigation layout.

.

. 42

Gateway agent log files .

.

.

.

.

.

.

.

. 42


Notices . . . . . . . . . . . . . . 47

Trademarks .

.

.

.

.

.

.

.

.

.

.

.

.

. 49

Terms and conditions for product documentation.

. 50

© Copyright IBM Corp. 2007, 2017

iii

iv

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

About This Documentation

IBM Tivoli

®

Monitoring helps monitor and optimize hardware and application performance. The IBM Tivoli Monitoring application operates by deploying agents to monitor the performance of target systems and to relay the data back to the IBM

Tivoli Monitoring system, where it can be stored and reported on.

The purpose of the IBM Tivoli Monitoring Integration Guide is to provide details of integrating IBM Tivoli

®

Netcool

®

Performance Manager with IBM Tivoli

Monitoring. This document provides information for the deployment of the following Tivoli Netcool Performance Manager agents on IBM Tivoli Monitoring: v Application server v Loaders v Gateways

Audience

This information is intended for administrators or operations specialists responsible for installing and administrating IBM

®

Tivoli

®

Monitoring and Tivoli Netcool

®

Performance Manager.

What this publication contains

This publication contains the following sections: v

Chapter 1, IBM Tivoli Monitoring Integration Overview

Overview of steps to integrate Tivoli Monitoring with Tivoli Netcool


v

Chapter 2, IBM Tivoli Monitoring Integration Prerequisites

Integration prerequisites, including IBM Tivoli Monitoring installation, IBM

Tivoli Monitoring OS agent installation.

v

Chapter 3, Tivoli Netcool Performance Manager Agent Installation and

Configuration

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

v

Chapter 4, Tivoli Netcool Performance Manager Enablement

Enabling Tivoli Netcool Performance Manager for the collection of IBM Tivoli

Monitoring metrics.

v

Chapter 5, Gateways IBM Tivoli Monitoring Agent Historical Data

Enabling historical data collection.

v

Chapter 6, Alarm Integration

Integrating Tivoli Netcool Performance Manager alarms.

v

Chapter 7, Tivoli Netcool Performance Manager agent metrics and IBM Tivoli

Monitoring navigation layout

Describes the metrics that are collected for each Tivoli Netcool Performance

Manager agent, the log files that are used and the default IBM Tivoli Monitoring navigation layout.


v

The Tivoli Netcool Performance Manager - Wireless component user publications

Tivoli Netcool Performance Manager - Wireless component consists of the following publications:

Table 1. Tivoli Netcool Performance Manager - Wireless component user documentation

Document

Release Summary for Tivoli Netcool Performance

Manager

Installing Tivoli Netcool Performance Manager -

Wireless Component

Upgrading Tivoli Netcool Performance Manager -


Administering Tivoli Netcool Performance Manager -


Using Tivoli Netcool Performance Manager - Wireless

Component

Installing and Using Tivoli Netcool Performance

Manager - Application Studio - Wireless Component

Integrating with Tivoli Monitoring - Wireless

Component

Integrating with Tivoli Netcool/OMNIbus Web GUI -


Description

Additional release-specific information not in the guides.

Instructions for installing and configuring the

Tivoli Netcool Performance Manager software.

Instructions for upgrading Tivoli Netcool

Performance Manager software.

Instructions and general information about how to maintain and support Tivoli Netcool Performance

Manager

Conceptual information and procedures for using

Tivoli Netcool Performance Manager software for performance, trending analysis and performance alarms.

Provides instructions for installation and usage of the Tivoli Netcool Performance Manager -

Application Studio.

Provides instructions for integrating IBM Tivoli

Monitoring with Tivoli Netcool Performance

Manager.

Provides instructions for integrating IBM Tivoli

Netcool/OMNIbus Web GUI with Tivoli Netcool


The documentation is available on the knowledge center at http://www-

01.ibm.com/support/knowledgecenter/SSBNJ7/welcome.

Service Management Connect

Connect, learn, and share with Service Management professionals: product support technical experts who provide their perspectives and expertise.

Access Network and Service Assurance community at https://www.ibm.com/ developerworks/servicemanagement/nsa/index.html. Use Service Management

Connect in the following ways: v

Become involved with transparent development, an ongoing, open engagement between other users and IBM developers of Tivoli products. You can access early designs, sprint demonstrations, product roadmaps, and prerelease code.

v Connect one-on-one with the experts to collaborate and network about Tivoli and the Network and Service Assurance community.

v Read blogs to benefit from the expertise and experience of others.

v Use wikis and forums to collaborate with the broader user community.

Related information

:

Tivoli Netcool Performance Manager 1.4 community on developerWorks

vi


Tivoli Netcool Performance Manager technical training

For Tivoli Netcool Performance Manager technical training information, see the following Tivoli Netcool Performance Manager Training website at: https://tnpmsupport.persistentsys.com/training.

Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need:

Online

Access the IBM Software Support site at http://www.ibm.com/software/ support/probsub.html .

IBM Support Assistant

The IBM Support Assistant is a free local software serviceability workbench that helps you resolve questions and problems with IBM software products. The Support Assistant provides quick access to support-related information and serviceability tools for problem determination. To install the Support Assistant software, go to http://www.ibm.com/software/ support/isa.

Troubleshooting Guide

For more information about resolving problems, see the problem determination information for this product.

Conventions used in this publication

Several conventions are used in this publication for special terms, actions, commands, and paths that are dependent on your operating system.

Typeface conventions

This publication uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text v Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) v Keywords and parameters in text

Italic

v Citations (examples: titles of publications, diskettes, and CDs) v Words defined in text (example: a nonswitched line is called a

point-to-point line) v Emphasis of words and letters (words as words example: "Use the word

that to introduce a restrictive clause."; letters as letters example: "The

LUN address must start with the letter L.") v New terms in text (except in a definition list): a view is a frame in a workspace that contains data.

v Variables and values you must provide: ... where myname represents....

Monospace

About This Documentation

vii

v Examples and code examples v

File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options

Bold monospace

v Command names, and names of macros and utilities that you can type as commands v Environment variable names in text v Keywords v

Parameter names in text: API structure parameters, command parameters and arguments, and configuration parameters v Process names v Registry variable names in text v Script names

viii


Chapter 1. IBM Tivoli Monitoring Integration Overview

IBM Tivoli Monitoring helps monitor and optimize hardware and application performance.

The IBM Tivoli Monitoring application operates by deploying agents to monitor the performance of target systems and to relay the data back to the 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.

v The Gateway agent monitors the performance and processing success of the

Tivoli Netcool Performance Manager gateways.

v The Loader agent monitors the performance and processing success of the Tivoli

Netcool Performance Manager loaders.

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

Integration steps

A number of steps must be completed to set up the IBM Tivoli Monitoring system for Tivoli Netcool Performance Manager.

The order of the steps is as follows:

1.

Prerequisites a.

IBM Tivoli Monitoring installation and configuration b.

IBM Tivoli Monitoring OS agents installation and configuration

2.

Tivoli Netcool Performance Manager agent installation and configuration

3.

Tivoli Netcool Performance Manager enablement a.

Enable collection of IBM Tivoli Monitoring metrics b.

Start a Tivoli Netcool Performance Manager agent service on IBM Tivoli

Monitoring


1

2


Chapter 2. IBM Tivoli Monitoring Integration Prerequisites

Integration prerequisites for IBM Tivoli Monitoring integration.

IBM Tivoli Monitoring installation

If you do not currently have an IBM Tivoli Monitoring installation, you must install it on the server to be used for monitoring Tivoli Netcool Performance

Manager. This server is referred to as the IBM Tivoli Monitoring server. For Tivoli

Netcool Performance Manager version 1.4.3, IBM Tivoli Monitoring version 6.3 Fix

Pack 6 is required.

For instructions on installing IBM Tivoli Monitoring, see section Installation procedure of the IBM Tivoli Monitoring Installation and Setup Guide.

Note:

You can install IBM Tivoli Monitoring on the same server as one of the

Tivoli Netcool Performance Manager servers. However, this configuration increases the processor usage and affects the server.

IBM Tivoli Monitoring OS agents installation

IBM Tivoli Monitoring OS agents must be installed on each of the Tivoli Netcool

Performance Manager servers to be monitored. The OS agent that is installed must be appropriate for the server's operating system.

Note:

Consider that a distributed system is used, with Tivoli Netcool Performance

Manager gateways and loaders that are installed over multiple servers. In this case, each Tivoli Netcool Performance Manager server must be installed with the OS agent appropriate for the server's operating system.

For instructions on how to deploy OS agents to a server, see section Installing

Monitoring Agents of the IBM Tivoli Monitoring Installation and Setup Guide.

The same section of the guide describes how to configure and start the OS agents.

When an agent is correctly configured and started, it displays in the Navigator view of the Tivoli Enterprise Portal. The IBM Tivoli Monitoring User's Guide describes the configuration and use of the Tivoli Enterprise Portal GUI.


3

4


Chapter 3. Tivoli Netcool Performance Manager Agent

Installation and Configuration

The chapter details the installation and configuration of Tivoli Netcool Performance

Manager agents.

You must install the agents only for those components of Tivoli Netcool

Performance Manager that you intend to monitor.

Tivoli Netcool Performance Manager Agent Installation and Configuration chapter describes: v

Installing the Tivoli Netcool Performance Manager Agents

v

Upgrading the Tivoli Netcool Performance Manager Agents

v

Installing the Tivoli Netcool Performance Manager agent by remote deployment

There are three Tivoli Netcool Performance Manager agents: v Loader v Application server (as) v Gateways

Tivoli Netcool Performance Manager agents installer is packaged together with the

Core installer. The packaged installer files are available as follows: v

Loader agent: valueadd/itm_agents/TNPMWLoaderAgent.tar.gz

v Application server agent: valueadd/itm_agents/TNPMWAppserverAgent.tar.gz

v Gateways agent: valueadd/itm_agents/TNPMWGatewayAgent.tar.gz

Note:

You must unpack the files with GNU tar version 1.14 and later. Unpack each agent to a different directory to avoid overwriting the files. File names and the directory structure for each agent are similar. Always run the appropriate installer during installation. For example: v On a Windows

® system run: <image_location>/installIraAgentTEMS.bat

v On a non-Windows

® system, as user root run: <image_location>/ installIraAgentTEMS.sh

Installing the Tivoli Netcool Performance Manager Agents

Before you begin

To install the Tivoli Netcool Performance Manager agent version 6.3 Fix Pack 6, you must have the Tivoli Netcool Performance Manager version 1.4.3.

About this task

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

The installation involves: v Installing Tivoli Enterprise Monitoring Server support on the Tivoli Enterprise

Monitoring Server v Installing Tivoli Enterprise Portal Server support on the Tivoli Enterprise Portal

Server


5

v Adding Bundles on the Tivoli Enterprise Monitoring Server - The bundles enable remote deployment of agents from the Tivoli Enterprise Portal GUI. It installs the Tivoli Netcool Performance Manager agent on the remote source depot of


v Installing the Tivoli Netcool Performance Manager agent by remote deployment

- Install and configure the Tivoli Netcool Performance Manager agent in one step through the Tivoli Enterprise Portal GUI.

Note:

The following example illustrates installing the Tivoli Netcool Performance

Manager loader agent. The installation steps for each agent are the same.

Procedure

1.

As user root, unpack the contents of the agent archive on target server.

2.

Run the appropriate script at installable media path. It is the same location where you unpacked the Tivoli Netcool Performance Manager agent installer.

For example:

/root/LOADER/TNPMWLoaderAgent

3.

Install the Tivoli Enterprise Monitoring Server support on Tivoli Enterprise

Monitoring Server.

# ./installIraAgentTEMS.sh <itm_install_location>

For example:

./installIraAgentTEMS.sh /opt/IBM/ITM

4.

Install the Tivoli Enterprise Portal Server support on Tivoli Enterprise Portal

Server.

# ./installIraAgentTEPS.sh <itm_install_location> -r

For example:

./installIraAgentTEPS.sh /opt/IBM/ITM –r

5.

Before you install or deploy a Tivoli Netcool Performance Manager agent from

Tivoli Enterprise Portal (TEP), run the steps to populate the agent depot on

Tivoli Enterprise Monitoring Server. To populate the agent depot with the tacmd addBundles command, run the following command at

<itm_install_location>/bin .

# ./tacmd addbundles -i <image_location>

For example:

./tacmd addbundles -i /root/LOADER/TNPMWLoaderAgent

Note:

For the full syntax, including parameter descriptions, see the IBM Tivoli

Monitoring: Command Reference.

6.

To install agent, proceed to “Installing the Tivoli Netcool Performance Manager agent by remote deployment” on page 8.

Note:

Repeat the installation steps for other agent at a particular software location. Always close all the open browser windows and relogin to Tivoli

Enterprise Portal (TEP) GUI for refreshed mode.

Related information

:

IBM Tivoli Monitoring 6.3.0 Fix Pack 6 (6.3.0-TIV-ITM-FP0006)

6


Upgrading the Tivoli Netcool Performance Manager Agents

Before you begin

You must upgrade the Tivoli Netcool Performance Manager agents from version

6.2.1 to version 6.3 Fix Pack 6.

About this task

Perform the following steps to upgrade a Tivoli Netcool Performance Manager agent.

v Upgrade Tivoli Enterprise Monitoring Server support on Tivoli Enterprise

Monitoring Server v Upgrade Tivoli Enterprise Portal Server support on Tivoli Enterprise Portal

Server v Upgrade Tivoli Netcool Performance Manager agent on Tivoli Netcool

Performance Manager Server

Note:

The following example illustrates installing the Tivoli Netcool Performance

Manager loader agent. The installation steps for each agent are the same.

Procedure

1.

As user root, unpack the contents of the agent archive on target server.

2.

Run the appropriate script at installable media path. It is the same location where you unpacked the Tivoli Netcool Performance Manager agent installer.

For example:

/root/LOADER/TNPMWLoaderAgent

3.

Upgrade the Tivoli Enterprise Monitoring Server support on Tivoli Enterprise

Monitoring Server.

# ./installIraAgentTEMS.sh <itm_install_location>

For example:

./installIraAgentTEMS.sh /opt/IBM/ITM

4.

Upgrade the Tivoli Enterprise Portal Server support on Tivoli Enterprise Portal

Server

# ./installIraAgentTEPS.sh <itm_install_location> -r

For example:

./installIraAgentTEPS.sh /opt/IBM/ITM –r

5.

Before you install or deploy a Tivoli Netcool Performance Manager agent from

Tivoli Enterprise Portal, run the steps to populate the agent depot on Tivoli

Enterprise Monitoring Server. Run the following command at

<itm_install_location>/bin to populate the agent depot.

# ./tacmd addbundles -i <image_location>

For example:

./tacmd addbundles -i /root/LOADER/TNPMWLoaderAgent

6.

To upgrade the agent on Tivoli Netcool Performance Manager server: v

For new Tivoli Netcool Performance Manager server without the agent that

is installed before, proceed to “Installing the Tivoli Netcool Performance

Manager agent by remote deployment” on page 8

Chapter 3. Tivoli Netcool Performance Manager Agent Installation and Configuration

7

v For existing Tivoli Netcool Performance Manager server with installed agent, run the following command:

# ./installIraAgent.sh <itm_install_location>

For example:

./installIraAgent.sh /opt/IBM/ITM

Note:

If the instance of agents status is running, the installer restarts the instances. If the status is 'stop', the instance remains stopped after the installation.

7.

Repeat step 1-6 for other upgrading another agent.

8.

Close all the open browser windows and relogin to Tivoli Enterprise Portal

(TEP) GUI for refreshed mode.

Installing the Tivoli Netcool Performance Manager agent by remote deployment

Using the Tivoli Enterprise Portal GUI allows the Tivoli Netcool Performance

Manager agent to be installed and configured in one step.

About this task

To install or deploy a Tivoli Netcool Performance Manager agent from Tivoli

Enterprise Portal:

Procedure

1.

Start the Tivoli Enterprise Portal 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 continue with remote installation. Refer to the section

Installing Monitoring Agents of the IBM Tivoli Monitoring Installation and

Setup Guide for instructions on how to run OS agents.

The system displays the Select a Monitoring Agent dialog.

8


Figure 1. Select a Monitoring Agent

3.

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

The system displays the configuration parameters for the agent. See the following sections for details of each agent 's configuration: v

Application server agent configuration

v

Loader agent configuration

v

Gateway agent configuration

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

Multiple instances of loader and gateway agents can exist on a single server. So sometimes the system displays a prompt to enter a name for the instance. For an application server agent, this scenario is not applicable.

Note:

The installation of the Tivoli Netcool Performance Manager agent occurs only the first time the Add Managed System is run for an agent. Subsequent operations are either add new instances or reconfigure the existing agent. When you install an agent from the Tivoli Enterprise Portal, you can use the IBM

Tivoli Monitoring command line for the same configuration. You can start or stop actions directly on the server. This situation is not applicable for application server agent because only one instance of that agent can be present on a server.

Configuring the application server agent

Instruction on how to configure the application server agent.

About this task


9

Figure 2. New Managed System Configuration

Procedure

1.

Enter or amend any configuration settings, as required.

2.

Click Finish.

Results

The system displays a dialog to indicate that the deployment is queued.

Configuring the loader agent

Instructions on how to configure the loader agent.

About this task

10



Procedure

1.

Enter or amend any configuration settings, as required.

We advise that the agent instance name corresponds 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 that are given in the loader's properties file.

See Loaders.

2.

Click Finish.

The system displays a dialog to indicate that the deployment is queued.


11

Configuring the gateway agent

Instructions on how to configure the gateway agent.

Procedure

1.

Provide expressions for the Gateway Agent Instance Name, Vendor Sub-system name, and Vendor Release name.


The expression for vendor subsystem 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.

Note:

Ensure that one Gateway Configuration is being monitored by one

Gateway Agent Instance only. The Gateway Configuration is monitored by multiple Gateway Agent Instances. Duplicate records of the same Gateway

12


Configuration are reported in the overall Tivoli Netcool Performance Manager

Gateway workspace for every Gateway Agent node.

2.

Click Next.

3.

Provide the Username and Group name.


The Username. It must be the same as the user name used for the Gateway

Framework installation and is usually: virtuo.

The Group name. You can use any group name. It is usually: virtuo.

4.

Click Finish.


13

14


Chapter 4. Tivoli Netcool Performance Manager Enablement

Enabling Tivoli Netcool Performance Manager for IBM Tivoli Monitoring.

v

Enabling the collection of IBM Tivoli Monitoring metrics

v

Starting the Tivoli Netcool Performance Manager agent service

Enabling the collection of IBM Tivoli Monitoring metrics

Enable the collection of IBM Tivoli Monitoring metrics for each of the agents you intend to use.

Application server

Distributed systems only. In a distributed installation, you must run the section only for the application server.

By default, the system displays the output of metrics that are required for the IBM

Tivoli Monitoring agents to collect application server data. The property itm.logging.enabled

must be set to true to enable the collection of metrics for


The property itm.logging.enabled is contained in the IBM Tivoli Monitoring properties file on the Tivoli Netcool Performance Manager server in:

$WMCROOT/conf/itm/default.properties

.

Note:

Following an update to the IBM Tivoli Monitoring properties file, you must restart the application server. Use the sap utility to restart the application server. For example, type the following on the application server as user virtuo: sap stop as sap start as

See the Tivoli Netcool Performance Manager Administration Guide.

$WMCROOT is the location where you install Tivoli Netcool Performance Manager.

The recommended installation directory is: /appl/virtuo. In this document,

$WMCROOT = /appl/virtuo .

The contents of this file are as follows:

Table 2. IBM Tivoli Monitoring properties

Property

itm.logging.enabled

itm.logging.dir

Description

Enable or disable IBM Tivoli Monitoring logging. Default is false, true turns on IBM

Tivoli Monitoring logging. Any other value turns it off.

The directory that IBM Tivoli Monitoring logs are written to. Default is

$WMCROOT/logs/itm

.


15

Table 2. IBM Tivoli Monitoring properties (continued)

Property

itm.logging.report.userroles

itm.logging.report

itm.logging.usage

itm.logging.sbh.completion

itm.logging.sbh.completion.interval

Description

Log user role and group information when you are logging report execution metrics.

true turns on the setting to log user role information. Any other value turns it off.

Default is true.

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

The name of the log file for usage metrics.

Default is itm-usage.log.

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

.

Frequency in minutes to log busy hour completion metrics. Default is 60.

itm.logging.sbh.execution

itm.logging.summary.completion

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

.

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

itm.logging.raw.coverage

itm.logging.coverage.list

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

.

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

.

The name of the file that contains the list of

KPIs to calculate coverage for. See Coverage file. Default is $WMCROOT/conf/itm/

coverage.txt

.

Note:

If file names are changed, the configuration of the Tivoli Netcool

Performance Manager application server agent must be changed with the same values.

Coverage file

The format of the coverage file.

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

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

The properties are as follows: v Vendor : Entities are 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.

v Technology : Entities are filtered by technology name. There is no pattern matching, the name must match exactly.

16


v Counter : A KPI to calculate coverage for. It must be a raw counter, not a Pcalc or UDC.

v Rollup Entity Name

: This property must be a parent of the KPI's entity. It cannot be the same as the entity's KPI.

v Interval : How long the period used to calculate coverage is. This property must be aligned to the interval of the data it is monitoring. It must be the same as, or a multiple of, the data interval.

v

Grace Period

: How far back in time to go to select the period. This property must 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 takes this back to 13:02. Aligning the interval to the hour gives 13:00. The time period that is covered is 13:00 to 13:30.

See the Tivoli Netcool Performance Manager Administration Guide for information about the grace period.

Cron jobs

Coverage file

The following cron job reads the coverage file and produces the coverage metrics:

2,17,32,47 * * * * /appl/virtuo/bin/run_itm_rawcoverage_logger >

/dev/null 2>&1

By default this cron job runs every 15 minutes, for 2 minutes after the quarter hour. You can alter the execution schedule to suit the data to be 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, for 1 minute after the quarter hour and covers the previous

15-minute period. Generally, if the scheduling frequency is changed, you must also change the parameter that is passed to the run_itm_usage_logger script to match.

Loaders

Distributed systems only. In a distributed installation, you must run the section only for the loader server.

About this task

By default the output of IBM Tivoli Monitoring metrics from Tivoli Netcool

Performance Manager loaders is disabled. To enable the output of IBM Tivoli

Monitoring metrics from a loader, a property for the loader's configuration must be edited.

Chapter 4. Tivoli Netcool Performance Manager Enablement

17

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

To change a loader's configuration:

Procedure

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 five properties that relate to IBM Tivoli

Monitoring: v itm.enabled

- indicates whether to output metrics for IBM Tivoli

Monitoring, true enables output false disables output. By default, the value is set to false. If you want to enable itm, set the value to true.

v 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 advised that each loader instance for a technology pack on a server writes to the same file. This results in one IBM Tivoli Monitoring agent instance that is used to monitor each technology pack on a server. In this case, in the Tivoli

Enterprise Portal navigator tree is broken down to technology pack level. If required, each loader instance can write to its own file. In this case, a IBM

Tivoli Monitoring agent instance is needed for each file. It is also possible for all loaders to write to a single file, with only one agent instance required.

v itm.folder

- the folder to locate the itm.file property in.

v itm.interval

- how often to write metrics to the IBM Tivoli Monitoring file.

Ideally, it must be the same as the interval of the lif files that are loaded by the loader. If multiple intervals are loaded, the interval must be a logical multiple. For example, if a loader is loading 20-minute data and 30-minute data, the itm.interval must be 60.

v itm.late.latency.offset

- used to configure the late latency of loader. The default value is 0 (zero). The valid range: must be >= 0 and <= 1440. For example, if value=0, and the file interval=15 minutes, Late flag if maximum latency is >15. If value=10, and file interval=15 minutes, Late flag if maximum latency is >25.

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. It is easier if IBM Tivoli

Monitoring logging is turned on for all agents.

Note:

When new loader instances are added IBM Tivoli Monitoring output is disabled by default, regardless of the settings for existing instances.

4.

Loader instances must be restarted to apply any changes to the IBM Tivoli

Monitoring configuration, as user virtuo: sap stop <loader_name> sap start <loader_name>

When IBM Tivoli Monitoring output is enabled, the loader will write metrics to the IBM Tivoli Monitoring file after each interval. The interval is aligned to the

18


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 metric that is written is output at 13:15, then 13:30.

Gateways

Distributed systems only. In a distributed installation, you must run the section only for the gateway server.

About this task

The NotificationConfig.pm file is used to configure gateway event notifications.

These notifications must be configured to be sent to the correct directory in IBM

Tivoli Monitoring. 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:

Procedure

1.

Copy a sample NotificationConfig.pm file from the $GATEWAY_ROOT/gatewayframework/example/NotificationConfig.pm

into the vendor subsystem and release configuration directory, for example, $GATEWAY_ROOT/config/<vendorsubsys>/<release>/

2.

Edit the NotificationConfig.pm file, for the rule @rules_ITM on the configuration entry NOTIFICATION_TARGET for the vendor subsystem target log file: my @rules_ITM = (

{

RULE_TYPE => ’ITM_Notification’,

RULE_DESC => ’ITM Notification’,

NOTIFICATION_TARGET =>

’/appl/virtuo/logs/itm/<vendor-subsys>_<release>’,

ENABLE_PER_FILE_NOTIFICATION => 1,

},

NOTIFICATION_TYPE => ’Alarm|Event’,

NOTIFICATION_COMMAND => ’itmlog’, # command line script

);

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

3.

Edit the NotificationConfig.pm, for the subroutine notification_config() to return the reference to @rules_ITM: sub notification_config { return \@rules_ITM;

}

Note:

Refer to Gateway Framework User Guide to configure the transfer rules

(IN/OUT) metrics for gateway in TransferConfig.pm

Customizing the external scripts

The Tivoli Netcool Performance Manager gateway agent uses an external script itmlog.sh

within the gateway framework installation.

The script is in: $WMCROOT/gways/gateway-framework/vstart

Chapter 4. Tivoli Netcool Performance Manager Enablement

19

By default, the itmlog.sh script processes 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 Tivoli Monitoring, 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

Starting the Tivoli Netcool Performance Manager agent service

You must start the agent service for each Tivoli Netcool Performance Manager agent on each monitored Tivoli Netcool Performance Manager server before the performance metrics displays in IBM Tivoli Monitoring.

You can configure and start the agents 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.

For more information, refer to the IBM Tivoli Monitoring documentation.

Note:

The 'itmcmd manage' command requires the X-window function to launch the Manage Tivoli Enterprise Monitoring Services interface.

20


Chapter 5. Processing the Gateways IBM Tivoli Monitoring

Agent Historical Data

The Gateways IBM Tivoli Monitoring Agent is based on the script data source, and displays only the current or last Gateway process records.

To see previous Gateway processes, you must 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: v Enable Historical Data Collection for the attributes v Update queries for the workspace tables and charts v Set up pruning to delete old data in Tivoli Data Warehouse

Note:

Before you enable historical data collection, set the PASS_HOUR variable in

$WMCROOT/gways/gateway-framework/vstart/itmlog.sh

back to the default value 0.

If the itmlog.sh is configured to return more than just the most recent or currently running instances data, records from completed Gateway process are continuously reported and are repeatedly collected and delivered to the warehouse. For details

on Gateway agent external script customization, see Gateways.

Enabling Historical Data Collection

Instructions on how to enable historical data collection.

About this task

To enable the collection of historical data:

Procedure

1.

Click the History Configuration icon in the toolbar.

The system displays the History Collection Configuration dialog box.

2.

Select a monitored application from the tree. In this case, TNPM Gateways.

3.

Select KNI GATEWAY, KNI PARSER, and KNI TRANSFER.

4.

In the summarization area, select the time period to be aggregated. For example: v Yearly v Quarterly v

Monthly v Daily v Hourly

5.

In the pruning area, select the time period to be pruned. For example: v Yearly v Quarterly v Monthly v Daily


21

v Hourly

6.

Click Apply to save the configuration.

Updating Time Spans for Queries

You must update the queries for the bar or line charts and tables with the time spans.

Note:

For some common queries, you can use the option: Apply to all views associated with this view's query. For more information, refer to the IBM Tivoli

Monitoring documentation.

Updating Time Spans for Bar and Line Charts

Instructions on how to update the time span for the bar chart in the Tivoli Netcool

Performance Manager Gateways workspace.

About this task

The workspace is shown in the following figures:

Figure 6. Tivoli Netcool Performance Manager Gateways workspace

22


Figure 7. Gateway Instance workspace

To update the time span for a query:

Procedure

1.

Click the dialog box.

icon in the chart. The system displays the Select the Time Span

Chapter 5. Processing the Gateways IBM Tivoli Monitoring Agent Historical Data

23

Figure 8. Select the Time Span

2.

Select the Real time plus Last option and enter a time span.

3.

Click OK to save the workspace.

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

Procedure

1.

Click the icon in the table.

2.

Select the Last option and enter a time span.

3.

Select the Use detailed data option.

4.

Select Timestamp from the Time Column drop down list.

5.

Click OK to save the workspace.

24


Figure 9. Select the Time Span

Managing Historical Data by Pruning

With historical data collected from agents and sent to Tivoli Data Warehouse, the storage space that is used in Tivoli Data Warehouse continues to grow if it is not managed.

To manage this issue on an ongoing basis, you must set up pruning of Tivoli Data

Warehouse data according to any relevant data policies. For more information, see the IBM Tivoli Monitoring: Administrator Guide.

Chapter 5. Processing the Gateways IBM Tivoli Monitoring Agent Historical Data

25

26


Chapter 6. Integrating Alarm

The Tivoli Netcool Performance Manager IBM Tivoli Monitoring agents do not contain alarm definitions.

Alarm definitions can be added to the agents as the customer sees fit. For details on how to configure situation for agents on IBM Tivoli Monitoring with action to generate alarm, refer to Manage Situation and Take Action sections in IBM Tivoli

Monitoring 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 most suitable method of handling alarms depends on the existing application infrastructure: v

Customer already has IBM Tivoli Monitoring and Netcool/OMNIbus

v

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

v

Customer does not have Netcool/OMNIbus or IBM Tivoli Monitoring

v

Customer has IBM Tivoli Monitoring but other non-IBM Fault Management solution

Existing application infrastructure

The existing application structure.

Customer already has IBM Tivoli Monitoring and

Netcool/OMNIbus

In this case, the Tivoli Netcool Performance Manager agents can be integrated into the customer's existing IBM Tivoli Monitoring Infrastructure. It is possible that the customer already has IBM Tivoli Monitoring / Netcool/OMNIbus integration configured.

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

In this case, a single-server IBM Tivoli Monitoring solution would be deployed to monitor the Tivoli Netcool Performance Manager servers only.

The alarms that are generated by this IBM Tivoli Monitoring deployment can be directly integrated into the customer's Netcool/OMNIbus system through the existing Tivoli EIF probe.


27

Customer does not have Netcool/OMNIbus or IBM Tivoli

Monitoring

In this case, a single-server IBM Tivoli Monitoring 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. The standard Tivoli Netcool Performance Manager alarm export functions can be used to forward these alarms to external systems, for example through email or SNMP.

Customer has IBM Tivoli Monitoring 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 IBM Tivoli Monitoring infrastructure.

The customer already has IBM Tivoli Monitoring integration that is configured with an external non-IBM fault management system.

Generating the alarm package

Instructions on how to generate the package.

Procedure

1.

Run the following as user virtuo:

$WMCROOT/admin/common/install/scripts/create_alarmgenerator_package -wmcr $WMCROOT

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

.

2.

Copy the generated package to the server where alarm is required. The alarm is generated from the agents.

Note:

The package includes the password that is provided in the database configuration. If this password is not encoded, then the plain text password is readable on the target server.

3.

Extract the archive on the target server. The following folders are created: v bin - contains the alarm_generator file v conf - contains the file vtdb.properties that can be configured for database connection information.

v lib - contains the necessary .jar files.

4.

To generate an alarm from the target server, run 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 3. Alarm generator parameters

Parameter

notification_id

CLI format PL-SQL format Description

Integer INTEGER Alarm notification Id.

Default

None.

28


Table 3. Alarm generator parameters (continued)

Parameter

CLI format PL-SQL format Description Default

ev_source ev_type

String

String

VARCHAR2(255) Event/Alarm source.

VARCHAR2(255) Event type, see Event types .

monitored_attribute String NUMBER Attribute value that triggered the alarm, for example 51.3.

None.

None.

None.

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

None.

managed_object_ instance alarm_predicate

String

String

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

VARCHAR2(255) Alarm predicate.

None.

None.

probable_cause String VARCHAR2(255) Probable alarm cause, see

Probable causes .

None.

specific_problem additional_text trend_indication report_id alarm_severity event_time

String VARCHAR2(255) Specific alarm problem.

String VARCHAR2(255) Any additional text.

String VARCHAR2(255) 'more severe' (raised) or 'less

Severe' (cleared), see Trend

Indications .

Integer NUMBER Associated report Id, which is given as alarmapi_admin -r.

None.

None.

None.

None.

String

VARCHAR2(255) Alarm severity, see Severity .

String: yyyy

MMdd

HHmm ss.

DATE Optional. Alarm time. When the alarm reflects a past event, it must be set to the event time.

If not provided, it is assumed to be the current time.

None.

Current time.

Note:

IBM Tivoli Monitoring actions can be configured to call the script to generate internal Tivoli Netcool Performance Manager alarms. You can type the full path of the alarm_generator script with the required parameters mentioned in step 4 at the system command in the action screen.

Note:

The alarm spool daemon asd sap process must be running to raise alarms in Tivoli Netcool Performance Manager. The daemon is started and stopped, as user virtuo with the commands sap start asd and sap stop asd.

Note:

The script requires JavaTM Runtime Environment (JRE) version 1.6.0.

The PATH set in the environment must use the 1.6.0 version of Java.

Parameter values - lists

A number of parameters have defined values, including: v

Event types

v

Probable causes

v

Trend Indications

v

Severity

Chapter 6. Integrating Alarm

29

Event types

It is possible that the Tivoli Netcool Performance Manager accepts non-standard values, but alarms with non-standard values cannot be forwarded to SNMP recipients, such as Tivoli Netcool OMNIbus.

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

Table 4. Event type

Event type

Communications

QualityOfService

ProcessingError

Equipment

Environmental

Probable causes

Lists all the possible values for probable_cause.

Table 5. Probable Causes

Probable cause

adapterError airCompressorFailure airConditioningFailure airDryerFailure aIS antennaFailure applicationSubsystemFailture applicationSubsystemFailure authenticationFailure backplaneFailure bandwidthReduced bandwidthReducedX733 batteryChargingFailure batteryDischarging batteryFailure breachOfConfidentiality broadcastChannelFailure cableTamper callEstablishmentError callSetUpFailure commercialPowerFailure communicationsProtocolError communicationsSubsystemFailure configurationOrCustomisationError configurationOrCustomizationError

Probable cause

lossOfRedundancy lossOfSignal lossOfSignalX733 lossOfSynchronisation lowBatteryThreshold lowCablePressure lowFuel lowHumidity lowTemperatue lowWater materialSupplyExhausted memoryMismatch modulationFailure multiplexerProblem multiplexerProblemX733 nEIdentifierDuplication nonRepudiationFailure other outOfCPUCycles outOfHoursActivity outOfMemory outOfMemoryX733 outOfService outputDeviceError pathTraceMismatch

30


Table 5. Probable Causes (continued)

Probable cause

congestion congestionX733 connectionEstablishmentError coolingFanFailure coolingSystemFailure corruptData coruptData cpuCyclesLimitExceeded databaseInconsistency dataSetOrModemError dataSetProblem degradedSignal degradedSignalX733 delayedInformation demodulationFailure denialOfService diskFailure dteDceInterfaceError duplicateInformation enclosureDoorOpen enclosureDoorOpenX733 engineFailure equipmentIdentifierDuplication equipmentMalfunction excessiveBER excessiveErrorRate excessiveResponseTime excessiveRetransmissionRate excessiveVibration explosiveGas externalEquipmentFailure externalIFDeviceProblem externalPointFailure farEndReceiverFailure fileError fileErrorX733 fire fireDetected fireDetectorFailure flood

Probable cause

payloadTypeMismatch performanceDegraded powerProblem powerProblems powerSupplyFailure pressureUnacceptable proceduralError processorProblem processorProblems protectingResourceFailure protectionMechanismFailure protectionPathFailure pumpFailure pumpFailureX733 queueSizeExceeded realTimeClockFailure receiveFailure receiveFailureX733 receiverFailure receiverFailureX733 rectifierFailure rectifierHighVoltage rectifierLowFVoltage reducedLoggingCapability remoteAlarmInterface remoteNodeTransmissionError remoteNodeTransmissionErrorX733 replaceableUnitMissing replaceableUnitProblem replaceableUnitTypeMismatch resourceAtOrNearingCapacity responseTimeExcessive retransmissionRateExcessive routingFailure sfwrDownloadFailure sfwrEnvironmentProblem signalLabelMismatch signalQualityEvaluationFailure smoke softwareError


31

Table 5. Probable Causes (continued)

Probable cause

framingError framingErrorX733 frequencyHoppingFailure fuseFailure generatorFailure heatingVentCoolingSystemProblem highHumidity highTemperature highWind humidityUnacceptable iceBuildUp informationMissing informationModificationDetected informationOutOfSequence inputDeviceError inputOutputDeviceError intrusionDetection invalidMessageReceived iODeviceError keyExpired lanError leakDetected lineCardProblem localNodeTransmissionError localNodeTransmissionErrorX733 lossOfFrame lossOfFrameX733 lossOfMultiFrame lossOfPointer lossOfRealTimel

Probable cause

softwareErrorX733 softwareProgramAbnormallyTerminated softwareProgramError storageCapacityProblem storageCapacityProblemX733 synchronizationSourceMismatch systemResourcesOverload temperatureUnacceptable terminalProblem thresholdCrossed timeoutExpired timingProblem timingProblemX733 toxicGas toxicLeakDetected tranceiverFailure transmissionError transmiterFailure transmitFailure transmitFailureX733 transmitterFailure trunkCardProblem unauthorizedAccessAttempt unavailable underlayingResourceUnavailable underlyingResourceUnavailable unexpectedInformation ventilationsSystemFailure versionMismatch versionMismatchX733

Trend Indications

List of all the possible values for trend_indication.

Table 6. Trend Indication

Trend Indication

More Severe

Less Severe

No Change

32


Severity

List of all the possible values for alarm_severity.

Table 7. Severity values

Severity

Cleared

Indeterminate

Critical

Major

Minor

Warning


33

34


Chapter 7. Tivoli Netcool Performance Manager agent metrics and IBM Tivoli Monitoring navigation layout

This section describes the metrics that are collected for each Tivoli Netcool

Performance Manager agent, the log files used, and the default IBM Tivoli

Monitoring navigation layout.

This section describes: v Loader metrics and navigation layout v Application server metrics and navigation layout v Gateway server metrics and navigation layout

Loader metrics and navigation layout

This section details the loader metrics and navigation layout.

Loader agent log files

The list of loader agent log files.

The default log file directory on the Tivoli Netcool Performance Manager loader logs is $WMCROOT/logs/loader.

The IBM Tivoli Monitoring agent for Tivoli Netcool Performance Manager loaders has the following attributes: v Loader Name v Technology Pack Name v Technology Pack Version v Reporting Start Time v Reporting End Time v Reporting Duration v Interval Start Time v Interval End Time v Interval Duration v

File Processing Start Time v File Processing End Time v File Processing Duration v Number of LIF files processed v Total Size of LIF files processed v Number of LIF files successfully processed v Percentage LIF files successfully processed v Number of LIF files unsuccessfully processed v Percentage LIF files unsuccessfully processed v

Minimum Latency - the time between Interval End Time and File Processing

Start Time v Maximum Latency - the time between Interval End Time and File Processing

End Time


35

v Late - "Yes" if Maximum Latency is greater than Interval Duration. "No" otherwise.

Default IBM Tivoli Monitoring navigation layout

Default IBM Tivoli Monitoring navigation layout.

An example default navigation layout is as follows:

Enterprise

UNIX Systems

<<Hostname>>

Tivoli Netcool Performance Manager Loaders

<<Instance Name, e.g. technology pack>>

File Processing

To configure IBM Tivoli Monitoring workspaces, refer to the IBM Tivoli Monitoring product documentation.

Default Loader workspace

The default workspace for the Tivoli Netcool Performance Manager application

Loaders item in the IBM Tivoli Monitoring Navigator contains four frames in addition to the default Navigator frame.

The structure is as follows: v Stacking bar chart displays the loader file processing, aggregated for all technology packs on the system:

– LIF files successfully processed

– LIF files unsuccessfully processed v

Bar chart showing maximum data latency, aggregated for all tech packs on the system:

– File Processing Latency v 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 v Table showing loader data latency attributes:

– Loader Name

– Tech Pack Name

– Tech Pack Version


– File Processing Duration

– Minimum Latency

– Maximum Latency

– Late

36


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

Table showing main loader file processing attributes:

– Number of LIF Files Successfully Processed = 0

– Number of LIF Files Unsuccessfully Processed > 1 v Table showing loader data latency attributes:

– Late is set to 'Yes'

Default technology pack workspace

The default workspace for a technology pack that is selected beneath a loader contains four frames in addition to the default Navigator frame.

The structure is as follows: v Bar chart displays:

– Total number of LIF files processed

– LIF files successfully processed

– LIF files unsuccessfully processed v Bar chart displays:

– File Processing Latency v Table showing loader file processing attributes:

– Loader Name



– Reporting 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 v Table showing loader data latency attributes:

– Loader Name




– File Processing Duration

– Minimum Latency

– Maximum Latency

– Late

The corresponding cell within the file processing and latency tables is red for the following conditions: v Table showing main loader file processing attributes:

– Number of LIF Files Successfully Processed = 0

– Number of LIF Files Unsuccessfully Processed > 1 v Table showing loader data latency attributes:

– Late is set to 'Yes'

Chapter 7. Tivoli Netcool Performance Manager agent metrics and IBM Tivoli Monitoring navigation layout

37

Application server metrics and navigation layout

This section describes the application server metrics and navigation layout.

Application server agent log files

The list of application server agent log files.

The default log file directory on the Tivoli Netcool Performance Manager application server is $WMCROOT/logs/itm.

It contains the following logs:

Table 8. Application server log files

Log

Usage

Description

Usage information: v Time interval v Maximum number of user sessions v Number of active users v Number of scheduled reports run v Number of ad hoc reports run

38


Table 8. Application server log files (continued)

Log

Reports

Description

For each report run, the following is logged: v Report Id v Report Name v Report Folder v Report Type - ad hoc or scheduled.

v User - user that ran or scheduled the report.

v Roles - the user's roles.

v Groups - the user's groups.

v Start Time - either the scheduled start time or the time a user ran an Immediate report v Actual Start Time - the time the report was started by the system. This can be different on a busy system.

v Actual End Time - the end time.

v Preparation Time - the length of time from the actual start time to just before the

Reap query.

v Resolution Time - the length of time the

Reap query takes v Execution Time - the length of time the final report calculation takes.

v Number of Entities - the number of entities that are returned by the Reap query, not necessarily the same as the number in the final report.

v Number of KPIs - the number of KPIs requested.

v Number of Rows - the number of rows that are returned by the report, including roll ups.

v Time Interval

Raw data coverage

Raw data coverage information: v Timestamp v Vendor v Technology v KPI v Rollup Node Name v Percent complete


39

Table 8. Application server log files (continued)

Log

Busy hour execution

Description

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

Busy hour completion

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

Summary execution

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

Summary completion

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


An example of the default navigation layout is as follows:

Enterprise

UNIX Systems

<<Hostname>>

Tivoli Netcool Performance Manager Application Server

Usage

Reports

Coverage

To configure IBM Tivoli Monitoring workspaces, refer to your IBM Tivoli

Monitoring product documentation.

The default workspace that opens when the Tivoli Netcool Performance Manager application item is selected in the IBM Tivoli Monitoring Navigator contains four frames in addition to the default Navigator frame, as follows: v Bar chart that displays the report execution metrics (top 10)

40


v Bar chart that displays the vendor raw data coverage (aggregated) v

Table that displays the 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 v Table that displays the data coverage attributes (row per node)

– Timestamp

– Vendor Technology

– KPI

– Rollup Node Name

– Percent complete

Usage

The default workspace for Usage contains one frame in addition to the default

Navigator frame.

The structure is as follows: v Table displays 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 displays main data coverage attributes v % Complete < 95

Reports

The default workspace for Reports contains five frames in addition to the default

Navigator frame.

The structure is as follows: v Bar chart that displays the ad hoc report attributes (top 10) v Bar chart that displays the scheduled report attributes (top 10) v Bar chart that displays the average report execution times v Table that displays the user session attributes v Table that displays the report execution attributes

Coverage

The default workspace for Coverage contains three frames in addition to the default Navigator frame.

The structure is as follows: v Bar chart displays the vendor raw data coverage metrics v Table showing busy hour percent completion:


41

– Timestamp (Date / Time)

– Total number of Busy Hours

– Number of Busy Hours complete

– % Busy Hours complete v Table displays the summary percent completion:

– Timestamp (Date / Time)

– Total number of Busy Hours

– Number of Busy Hours complete

– % Busy Hours complete v Table displays the busy hour data coverage metrics:

– Busy Hour Name

– Start Time

– End Time

– Duration

– Type (Daily, Weekly, Monthly)

– Result

– Number of rows v Table displays the summary data coverage metrics:

– Summary Name

– Start Time

– End Time

– Duration

– Type (Daily, Weekly, Monthly)

– Result

– Number of rows

Using IBM Tivoli Monitoring threshold definitions, cells within the busy hour execution table are red for the following conditions: v Number of rows = 0 AND Result != 'Completed'

Using IBM Tivoli Monitoring threshold definitions, cells within the summary execution table are red for the following conditions: v

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

Gateway server metrics and navigation layout

This section describes the gateway server metrics and navigation layout.

Gateway agent log files

The location of gateway agent log files and the list of available attributes.

The default log file directory on the Tivoli Netcool Performance Manager gateways logs is $WMCROOT/logs/itm.

The IBM Tivoli Monitoring agent for Tivoli Netcool Performance Manager gateways logs the following attributes: v Gateway v Transfer IN/OUT

42


v Parser

Gateway

The information that is logged for the gateway.

The following information is logged for the gateway: v Vendor subsystem (for example, nokia-utran) v Vendor Release (for example, 6.0) v Gateway PID v Gateway Stages including the duration for:

– TRANSFER-IN

– PARSER

– TRANSFER-OUT v Period of Execution (crontab) v Execution Start Time v Execution End Time v Status: Normal Exit or Aborted/Killed

Transfer IN/OUT

The information that is logged for the Transfer parts of the gateway.

The following information is logged for the Transfer parts of the gateway: v Vendor subsystem (for example, nokia-utran) v

Vendor Release (for example, 6.0) v Gateway PID v Transfer Rule Name v Transfer Type: IN or OUT v Transfer Protocol (FTP, SCP, RCP, CP) v Transfer Host (IP) v Transfer Start Time v Transfer End Time v Number of files transferred v Total Size of files transferred v 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: v In File Name v In File Size v In file name Time Stamp (if available from source) v File Processing Start Time v File Processing End Time v Out File Name v Out File Size

Parser

The information logged for the parser part of the gateway.

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


43

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

Vendor Release (e.g. 6.0) v Gateway PID v Engine Rule Name v Engine Start Time v Engine End Time v Number of input files processed v Total Size of input files processed v Number of PIF files produced v Total Size of PIF files produced v Number of LIF files produced v 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: v Input File Name v Input File Size v Input Filename Time Stamp (if available from source) v File Processing Start Time v File Processing End Time v Out File Name(s) : PIFs and LIFs v Out File(s) Size


An example of the default navigation layout is as follows:

Enterprise

UNIX Systems

<<Hostname>>

Tivoli Netcool Performance Manager Gateways

<<Instance Name, e.g. vendor subsystem>>

Gateway

Parser

Transfer

To configure IBM Tivoli Monitoring workspaces, refer to your IBM Tivoli

Monitoring product documentation.

Default Gateways workspace

The default workspace for the Tivoli Netcool Performance Manager application

Gateways item in the IBM Tivoli Monitoring Navigator contains three frames in addition to the default Navigator frame.

The structure is as follows: v Stacked bar chart that displays the gateway phase durations, aggregated for all vendor subsystems on the system:

– Transfer IN

– Parser

– Transfer OUT v Table that displays the main file transfer attributes (for all gateways, all vendor subsystems):

44


– Vendor subsystem Name

– Vendor Release

– Transfer Rule Name

– Transfer Type (IN/OUT)

– Transfer Start Time

– Transfer End Time

– Number of Files Transferred v Table that displays the main PIF and LIF file processing attributes (for all gateways, all vendor subsystems):


– Vendor Release

– 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: v Number of Files Transferred IN = 0 v Number of Files Transferred OUT = 0 v 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.

The structure is as follows: v Line chart that displays the following:

– # Files Transferred IN

– # LIF Files Generated v Table that displays transfer attributes (for all gateways that are monitored by that agent):


– Vendor Release

– Transfer Rule Name

– Transfer Type (IN/OUT)

– Transfer Start Time

– Transfer End Time

– Number of Files Transferred v Table that displays PIF and LIF attributes (for all gateways that are monitored by that agent):


– Vendor Release

– Engine Rule Name

– Engine Start Time

– Engine End Time


45

– Number of PIF Files Produced

– Number of LIF Files Produced

The corresponding cell within the attributes table is red for the following conditions: v Number of Files Transferred IN = 0 v Number of Files Transferred OUT = 0 v Number of LIF Files Produced = 0

46


Notices

This information was developed for products and services offered in the US. This material might be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.

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 Licensing

IBM Corporation

North Castle Drive, MD-NC119

Armonk, NY 10504-1785

US

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 Licensing

Legal and Intellectual Property Law

IBM Japan Ltd.

19-21, Nihonbashi-Hakozakicho, Chuo-ku

Tokyo 103-8510, Japan

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 jurisdictions 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 websites are provided for convenience only and do not in any manner serve as an endorsement of those


47

websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide 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 Director of Licensing

IBM Corporation

North Castle Drive, MD-NC119

Armonk, NY 10504-1785

US

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.

The performance data discussed herein is presented as derived under specific operating conditions. Actual results may vary.

The client examples cited are presented for illustrative purposes only. Actual performance results may vary depending on specific configurations and operating conditions.

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.

Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

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 actual people or business enterprises is entirely coincidental.

COPYRIGHT LICENSE:

48


This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to

IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows:

© (your company name) (year).

Portions of this code are derived from IBM Corp. Sample Programs.

© Copyright IBM Corp. _enter the year or years_.

Trademarks

IBM, 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, Acrobat, PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer and

Telecommunications Agency which is now part of the Office of Government

Commerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,

Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

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

Microsoft and Windows are trademarks of Microsoft Corporation in the United

States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of The

Minister for the Cabinet Office, and is registered in the U.S. Patent and Trademark

Office.

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

Notices

49

Java and all Java-based trademarks and logos are trademarks or registered trademarks of

Oracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the

United States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

Terms and conditions for product documentation

Permissions for the use of these publications are granted subject to the following terms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBM website.

Personal use

You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations.

50


IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE

PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT

WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING

BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,

NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

Notices

51

52


IBM®

Printed in USA

IBM 1.4.3 Tivoli Netcool Performance Manager Tivoli Monitoring Integration Guide

Assistant Bot

IBM Tivoli Netcool Performance Manager 1.4.3

Wireless Component

Document Revision R2E1

Tivoli Monitoring Integration Guide

Contents

About This Documentation

Audience

What this publication contains

The Tivoli Netcool Performance Manager - Wireless component user publications

Service Management Connect

Tivoli Netcool Performance Manager technical training

Support information

Conventions used in this publication

Typeface conventions

Chapter 1. IBM Tivoli Monitoring Integration Overview

Integration steps

Chapter 2. IBM Tivoli Monitoring Integration Prerequisites

IBM Tivoli Monitoring installation

IBM Tivoli Monitoring OS agents installation

Chapter 3. Tivoli Netcool Performance Manager Agent

Installation and Configuration

Installing the Tivoli Netcool Performance Manager Agents

Before you begin

About this task

Procedure

Upgrading the Tivoli Netcool Performance Manager Agents

Before you begin

About this task

Procedure

Installing the Tivoli Netcool Performance Manager agent by remote deployment

About this task

Procedure

Configuring the application server agent

About this task

Procedure

Results

Configuring the loader agent

About this task

Procedure

Configuring the gateway agent

Procedure

Chapter 4. Tivoli Netcool Performance Manager Enablement

Enabling the collection of IBM Tivoli Monitoring metrics

Application server

Coverage file

Cron jobs

Coverage file

Coverage frequency

Loaders

About this task

Procedure

Gateways

About this task

Procedure

Customizing the external scripts

Starting the Tivoli Netcool Performance Manager agent service

Chapter 5. Processing the Gateways IBM Tivoli Monitoring

Agent Historical Data

Enabling Historical Data Collection

About this task

Procedure

Updating Time Spans for Queries

Updating Time Spans for Bar and Line Charts

About this task

Procedure

Updating Time Spans for Tables

Procedure

Managing Historical Data by Pruning

Chapter 6. Integrating Alarm

Existing application infrastructure

Customer already has IBM Tivoli Monitoring and

Netcool/OMNIbus

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

Customer does not have Netcool/OMNIbus or IBM Tivoli

Monitoring

Customer has IBM Tivoli Monitoring but other non-IBM Fault

Management solution

Generating the alarm package