with IBM Corp.€¦ · v Chapter 1, IBM T ivoli Monitoring Integration Overview Overview of steps to integrate T ivoli Monitoring with T ivoli Netcool Performance Manager . v Chapter

IBM Tivoli Netcool Performance Manager 1.4.3Wireless ComponentDocument Revision R2E1

Tivoli Monitoring Integration Guide

IBM

NoteBefore 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 Contractwith IBM Corp.

Contents

About This Documentation . . . . . . vAudience . . . . . . . . . . . . . . . vWhat this publication contains . . . . . . . . vThe Tivoli Netcool Performance Manager - Wirelesscomponent user publications. . . . . . . . . viService Management Connect . . . . . . . . viTivoli Netcool Performance Manager technicaltraining . . . . . . . . . . . . . . . viiSupport information . . . . . . . . . . . viiConventions used in this publication . . . . . . vii

Typeface conventions . . . . . . . . . . vii

Chapter 1. IBM Tivoli MonitoringIntegration Overview . . . . . . . . . 1

Chapter 2. IBM Tivoli MonitoringIntegration Prerequisites . . . . . . . 3

Chapter 3. Tivoli Netcool PerformanceManager Agent Installation andConfiguration . . . . . . . . . . . . 5Installing the Tivoli Netcool Performance ManagerAgents . . . . . . . . . . . . . . . . 5Upgrading the Tivoli Netcool Performance ManagerAgents . . . . . . . . . . . . . . . . 7Installing the Tivoli Netcool Performance Manageragent by remote deployment . . . . . . . . . 8

Configuring the application server agent . . . . 9Configuring the loader agent . . . . . . . 10Configuring the gateway agent . . . . . . . 12

Chapter 4. Tivoli Netcool PerformanceManager Enablement . . . . . . . . 15Enabling the collection of IBM Tivoli Monitoringmetrics . . . . . . . . . . . . . . . . 15

Application server . . . . . . . . . . . 15Loaders. . . . . . . . . . . . . . . 17Gateways . . . . . . . . . . . . . . 19

Starting the Tivoli Netcool Performance Manageragent service . . . . . . . . . . . . . . 20

Chapter 5. Processing the GatewaysIBM Tivoli Monitoring Agent HistoricalData . . . . . . . . . . . . . . . . 21Enabling Historical Data Collection . . . . . . 21Updating Time Spans for Queries . . . . . . . 22

Updating Time Spans for Bar and Line Charts . . 22Updating Time Spans for Tables . . . . . . 24

Managing Historical Data by Pruning . . . . . 25

Chapter 6. Integrating Alarm . . . . . 27Existing application infrastructure . . . . . . . 27

Customer already has IBM Tivoli Monitoring andNetcool/OMNIbus . . . . . . . . . . . 27Customer has Netcool/OMNIbus and othernon-IBM IT monitoring solutions . . . . . . 27Customer does not have Netcool/OMNIbus orIBM Tivoli Monitoring. . . . . . . . . . 28Customer has IBM Tivoli Monitoring but othernon-IBM Fault Management solution . . . . . 28

Generating the alarm package . . . . . . . . 28Parameter values - lists . . . . . . . . . 29

Chapter 7. Tivoli Netcool PerformanceManager agent metrics and IBM TivoliMonitoring navigation layout . . . . . 35Loader metrics and navigation layout . . . . . 35

Loader agent log files . . . . . . . . . . 35Default IBM Tivoli Monitoring navigation layout 36

Application server metrics and navigation layout . . 38Application server agent log files . . . . . . 38Default IBM Tivoli Monitoring navigation layout 40

Gateway server metrics and navigation layout. . . 42Gateway agent log files . . . . . . . . . 42Default IBM Tivoli Monitoring navigation layout 44

Notices . . . . . . . . . . . . . . 47Trademarks . . . . . . . . . . . . . . 49Terms 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 applicationperformance. The IBM Tivoli Monitoring application operates by deploying agentsto monitor the performance of target systems and to relay the data back to the IBMTivoli Monitoring system, where it can be stored and reported on.

The purpose of the IBM Tivoli Monitoring Integration Guide is to provide detailsof integrating IBM Tivoli® Netcool® Performance Manager with IBM TivoliMonitoring. This document provides information for the deployment of thefollowing Tivoli Netcool Performance Manager agents on IBM Tivoli Monitoring:v Application serverv Loadersv Gateways

AudienceThis information is intended for administrators or operations specialists responsiblefor installing and administrating IBM® Tivoli® Monitoring and Tivoli Netcool®

Performance Manager.

What this publication containsThis publication contains the following sections:v Chapter 1, IBM Tivoli Monitoring Integration Overview

Overview of steps to integrate Tivoli Monitoring with Tivoli NetcoolPerformance Manager.

v Chapter 2, IBM Tivoli Monitoring Integration PrerequisitesIntegration prerequisites, including IBM Tivoli Monitoring installation, IBMTivoli Monitoring OS agent installation.

v Chapter 3, Tivoli Netcool Performance Manager Agent Installation andConfigurationInstalling and configuring Tivoli Netcool Performance Manager agents for theapplication server, loaders, and gateways.

v Chapter 4, Tivoli Netcool Performance Manager EnablementEnabling Tivoli Netcool Performance Manager for the collection of IBM TivoliMonitoring metrics.

v Chapter 5, Gateways IBM Tivoli Monitoring Agent Historical DataEnabling historical data collection.

v Chapter 6, Alarm IntegrationIntegrating Tivoli Netcool Performance Manager alarms.

v Chapter 7, Tivoli Netcool Performance Manager agent metrics and IBM TivoliMonitoring navigation layoutDescribes the metrics that are collected for each Tivoli Netcool PerformanceManager agent, the log files that are used and the default IBM Tivoli Monitoringnavigation layout.

© Copyright IBM Corp. 2007, 2017 v

The Tivoli Netcool Performance Manager - Wireless component userpublications

Tivoli Netcool Performance Manager - Wireless component consists of thefollowing publications:

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

Document Description

Release Summary for Tivoli Netcool PerformanceManager

Additional release-specific information not in theguides.

Installing Tivoli Netcool Performance Manager -Wireless Component

Instructions for installing and configuring theTivoli Netcool Performance Manager software.

Upgrading Tivoli Netcool Performance Manager -Wireless Component

Instructions for upgrading Tivoli NetcoolPerformance Manager software.

Administering Tivoli Netcool Performance Manager -Wireless Component

Instructions and general information about how tomaintain and support Tivoli Netcool PerformanceManager

Using Tivoli Netcool Performance Manager - WirelessComponent

Conceptual information and procedures for usingTivoli Netcool Performance Manager software forperformance, trending analysis and performancealarms.

Installing and Using Tivoli Netcool PerformanceManager - Application Studio - Wireless Component

Provides instructions for installation and usage ofthe Tivoli Netcool Performance Manager -Application Studio.

Integrating with Tivoli Monitoring - WirelessComponent

Provides instructions for integrating IBM TivoliMonitoring with Tivoli Netcool PerformanceManager.

Integrating with Tivoli Netcool/OMNIbus Web GUI -Wireless Component

Provides instructions for integrating IBM TivoliNetcool/OMNIbus Web GUI with Tivoli NetcoolPerformance Manager.

The documentation is available on the knowledge center at http://www-01.ibm.com/support/knowledgecenter/SSBNJ7/welcome.

Service Management ConnectConnect, learn, and share with Service Management professionals: product supporttechnical 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 ManagementConnect 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 earlydesigns, sprint demonstrations, product roadmaps, and prerelease code.

v Connect one-on-one with the experts to collaborate and network about Tivoliand 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 IBM Tivoli Netcool Performance Manager 1.4.3 Wireless Component: Tivoli Monitoring Integration Guide

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7/welcome

http://www-01.ibm.com/support/knowledgecenter/SSBNJ7/welcome

https://www.ibm.com/developerworks/servicemanagement/nsa/index.html

https://www.ibm.com/developerworks/servicemanagement/nsa/index.html

https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=d4b565fd-04e5-47c2-965a-943ccdfabdb9

Tivoli Netcool Performance Manager technical trainingFor Tivoli Netcool Performance Manager technical training information, see thefollowing Tivoli Netcool Performance Manager Training website at:https://tnpmsupport.persistentsys.com/training.

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

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

IBM Support AssistantThe IBM Support Assistant is a free local software serviceability workbenchthat helps you resolve questions and problems with IBM softwareproducts. The Support Assistant provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe Support Assistant software, go to http://www.ibm.com/software/support/isa.

Troubleshooting GuideFor more information about resolving problems, see the problemdetermination information for this product.

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

Typeface conventionsThis publication uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), 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: "TheLUN address must start with the letter L.")

v New terms in text (except in a definition list): a view is a frame in aworkspace that contains data.

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

Monospace

About This Documentation vii

https://tnpmsupport.persistentsys.com/training

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/isa

http://www.ibm.com/software/support/isa

v Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Bold monospace

v Command names, and names of macros and utilities that you can typeas commands

v Environment variable names in textv Keywordsv Parameter names in text: API structure parameters, command

parameters and arguments, and configuration parametersv Process namesv Registry variable names in textv Script names

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

Chapter 1. IBM Tivoli Monitoring Integration Overview

IBM Tivoli Monitoring helps monitor and optimize hardware and applicationperformance.

The IBM Tivoli Monitoring application operates by deploying agents to monitorthe performance of target systems and to relay the data back to the system, whereit can be stored and reported on.

There are three agents available to monitor the performance of the Tivoli NetcoolPerformance 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. Systemadministrators 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 systemfor Tivoli Netcool Performance Manager.

The order of the steps is as follows:1. Prerequisites

a. IBM Tivoli Monitoring installation and configurationb. IBM Tivoli Monitoring OS agents installation and configuration

2. Tivoli Netcool Performance Manager agent installation and configuration3. Tivoli Netcool Performance Manager enablement

a. Enable collection of IBM Tivoli Monitoring metricsb. Start a Tivoli Netcool Performance Manager agent service on IBM Tivoli

Monitoring

© Copyright IBM Corp. 2007, 2017 1

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

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 mustinstall it on the server to be used for monitoring Tivoli Netcool PerformanceManager. This server is referred to as the IBM Tivoli Monitoring server. For TivoliNetcool Performance Manager version 1.4.3, IBM Tivoli Monitoring version 6.3 FixPack 6 is required.

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

Note: You can install IBM Tivoli Monitoring on the same server as one of theTivoli Netcool Performance Manager servers. However, this configuration increasesthe 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 NetcoolPerformance Manager servers to be monitored. The OS agent that is installed mustbe appropriate for the server's operating system.

Note: Consider that a distributed system is used, with Tivoli Netcool PerformanceManager gateways and loaders that are installed over multiple servers. In this case,each Tivoli Netcool Performance Manager server must be installed with the OSagent appropriate for the server's operating system.

For instructions on how to deploy OS agents to a server, see section InstallingMonitoring 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 Navigatorview of the Tivoli Enterprise Portal. The IBM Tivoli Monitoring User's Guidedescribes the configuration and use of the Tivoli Enterprise Portal GUI.



Chapter 3. Tivoli Netcool Performance Manager AgentInstallation and Configuration

The chapter details the installation and configuration of Tivoli Netcool PerformanceManager agents.

You must install the agents only for those components of Tivoli NetcoolPerformance Manager that you intend to monitor.

Tivoli Netcool Performance Manager Agent Installation and Configuration chapterdescribes:v Installing the Tivoli Netcool Performance Manager Agentsv Upgrading the Tivoli Netcool Performance Manager Agentsv Installing the Tivoli Netcool Performance Manager agent by remote deployment

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

Tivoli Netcool Performance Manager agents installer is packaged together with theCore installer. The packaged installer files are available as follows:v Loader agent: valueadd/itm_agents/TNPMWLoaderAgent.tar.gzv Application server agent: valueadd/itm_agents/TNPMWAppserverAgent.tar.gzv Gateways agent: valueadd/itm_agents/TNPMWGatewayAgent.tar.gz

Note: You must unpack the files with GNU tar version 1.14 and later. Unpack eachagent to a different directory to avoid overwriting the files. File names and thedirectory structure for each agent are similar. Always run the appropriate installerduring installation. For example:v On a Windows® system run: <image_location>/installIraAgentTEMS.batv On a non-Windows® system, as user root run: <image_location>/

installIraAgentTEMS.sh

Installing the Tivoli Netcool Performance Manager AgentsBefore 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 Serverv Installing Tivoli Enterprise Portal Server support on the Tivoli Enterprise Portal

Server


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

v Installing the Tivoli Netcool Performance Manager agent by remote deployment- Install and configure the Tivoli Netcool Performance Manager agent in onestep through the Tivoli Enterprise Portal GUI.

Note: The following example illustrates installing the Tivoli Netcool PerformanceManager loader agent. The installation steps for each agent are the same.

Procedure1. 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 EnterpriseMonitoring Server.# ./installIraAgentTEMS.sh <itm_install_location>

For example:./installIraAgentTEMS.sh /opt/IBM/ITM

4. Install the Tivoli Enterprise Portal Server support on Tivoli Enterprise PortalServer.# ./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 fromTivoli Enterprise Portal (TEP), run the steps to populate the agent depot onTivoli Enterprise Monitoring Server. To populate the agent depot with thetacmd 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 TivoliMonitoring: Command Reference.

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

Note: Repeat the installation steps for other agent at a particular softwarelocation. Always close all the open browser windows and relogin to TivoliEnterprise Portal (TEP) GUI for refreshed mode.

Related information:

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


http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/ic/landing_cmdref.htm

http://www-01.ibm.com/support/docview.wss?uid=swg24040390

Upgrading the Tivoli Netcool Performance Manager AgentsBefore you begin

You must upgrade the Tivoli Netcool Performance Manager agents from version6.2.1 to version 6.3 Fix Pack 6.

About this task

Perform the following steps to upgrade a Tivoli Netcool Performance Manageragent.v Upgrade Tivoli Enterprise Monitoring Server support on Tivoli Enterprise

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

Serverv Upgrade Tivoli Netcool Performance Manager agent on Tivoli Netcool

Performance Manager Server

Note: The following example illustrates installing the Tivoli Netcool PerformanceManager loader agent. The installation steps for each agent are the same.

Procedure1. 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 EnterpriseMonitoring Server.# ./installIraAgentTEMS.sh <itm_install_location>

For example:./installIraAgentTEMS.sh /opt/IBM/ITM

4. Upgrade the Tivoli Enterprise Portal Server support on Tivoli Enterprise PortalServer# ./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 fromTivoli Enterprise Portal, run the steps to populate the agent depot on TivoliEnterprise 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 PerformanceManager 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 theinstances. If the status is 'stop', the instance remains stopped after theinstallation.

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 remotedeployment

Using the Tivoli Enterprise Portal GUI allows the Tivoli Netcool PerformanceManager agent to be installed and configured in one step.

About this task

To install or deploy a Tivoli Netcool Performance Manager agent from TivoliEnterprise Portal:

Procedure1. 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 PerformanceManager server to continue with remote installation. Refer to the sectionInstalling Monitoring Agents of the IBM Tivoli Monitoring Installation andSetup Guide for instructions on how to run OS agents.The system displays the Select a Monitoring Agent dialog.


3. Select the type of agent to install, and click OK.The system displays the configuration parameters for the agent. See thefollowing sections for details of each agent 's configuration:v Application server agent configurationv Loader agent configurationv Gateway agent configurationThe procedure for configuring an application server, loader, or gateway agent issimilar.Multiple instances of loader and gateway agents can exist on a single server. Sosometimes the system displays a prompt to enter a name for the instance. Foran application server agent, this scenario is not applicable.

Note: The installation of the Tivoli Netcool Performance Manager agent occursonly the first time the Add Managed System is run for an agent. Subsequentoperations are either add new instances or reconfigure the existing agent. Whenyou install an agent from the Tivoli Enterprise Portal, you can use the IBMTivoli Monitoring command line for the same configuration. You can start orstop actions directly on the server. This situation is not applicable forapplication server agent because only one instance of that agent can be presenton a server.

Configuring the application server agentInstruction on how to configure the application server agent.

About this task

Figure 1. Select a Monitoring Agent


Procedure1. 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 agentInstructions on how to configure the loader agent.

About this task

Figure 2. New Managed System Configuration


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

We advise that the agent instance name corresponds to the technology pack forthe loader. The log file directory and log file name must correspond to theitm.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.



Configuring the gateway agentInstructions on how to configure the gateway agent.

Procedure1. 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 vendordirectory name in the configuration directory.The expression for vendor Release must be consistent with the release directoryname 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 oneGateway Agent Instance only. The Gateway Configuration is monitored bymultiple Gateway Agent Instances. Duplicate records of the same Gateway



Configuration are reported in the overall Tivoli Netcool Performance ManagerGateway 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 GatewayFramework installation and is usually: virtuo.The Group name. You can use any group name. It is usually: virtuo.

4. Click Finish.




Chapter 4. Tivoli Netcool Performance Manager Enablement

Enabling Tivoli Netcool Performance Manager for IBM Tivoli Monitoring.v Enabling the collection of IBM Tivoli Monitoring metricsv Starting the Tivoli Netcool Performance Manager agent service

Enabling the collection of IBM Tivoli Monitoring metricsEnable the collection of IBM Tivoli Monitoring metrics for each of the agents youintend to use.

Application serverDistributed systems only. In a distributed installation, you must run the sectiononly for the application server.

By default, the system displays the output of metrics that are required for the IBMTivoli Monitoring agents to collect application server data. The propertyitm.logging.enabled must be set to true to enable the collection of metrics forIBM Tivoli Monitoring.

The property itm.logging.enabled is contained in the IBM Tivoli Monitoringproperties 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 restartthe application server. Use the sap utility to restart the application server. Forexample, type the following on the application server as user virtuo:sap stop assap 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 Description

itm.logging.enabled Enable or disable IBM Tivoli Monitoringlogging. Default is false, true turns on IBMTivoli Monitoring logging. Any other valueturns it off.

itm.logging.dir The directory that IBM Tivoli Monitoringlogs are written to. Default is$WMCROOT/logs/itm.


Table 2. IBM Tivoli Monitoring properties (continued)

Property Description

itm.logging.report.userroles Log user role and group information whenyou are logging report execution metrics.true turns on the setting to log user roleinformation. Any other value turns it off.Default is true.

itm.logging.report The name of the log file for report executionmetrics. 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 busyhour completion metrics Default isitm-sbh-completion.log.

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

itm.logging.sbh.execution The name of the log file for stored busyhour execution metrics Default isitm-sbh-execution.log.

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

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

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

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

itm.logging.coverage.list The name of the file that contains the list ofKPIs to calculate coverage for. See Coveragefile. Default is $WMCROOT/conf/itm/coverage.txt.

Note: If file names are changed, the configuration of the Tivoli NetcoolPerformance Manager application server agent must be changed with the samevalues.

Coverage fileThe 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 patternmatching, the name must match exactly.


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

v Rollup Entity Name: This property must be a parent of the KPI's entity. Itcannot be the same as the entity's KPI.

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

v Grace Period: How far back in time to go to select the period. This propertymust 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 is14:02, the grace period takes this back to 13:02. Aligning the interval to the hourgives 13:00. The time period that is covered is 13:00 to 13:30.

See the Tivoli Netcool Performance Manager Administration Guide for informationabout 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 quarterhour. 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 itruns every 15 minutes, for 1 minute after the quarter hour and covers the previous15-minute period. Generally, if the scheduling frequency is changed, you must alsochange the parameter that is passed to the run_itm_usage_logger script to match.

LoadersDistributed systems only. In a distributed installation, you must run the sectiononly for the loader server.

About this task

By default the output of IBM Tivoli Monitoring metrics from Tivoli NetcoolPerformance Manager loaders is disabled. To enable the output of IBM TivoliMonitoring metrics from a loader, a property for the loader's configuration must beedited.

Chapter 4. Tivoli Netcool Performance Manager Enablement 17

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

To change a loader's configuration:

Procedure1. 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 TivoliMonitoring:v itm.enabled - indicates whether to output metrics for IBM Tivoli

Monitoring, true enables output false disables output. By default, the valueis 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 defaultsto an amalgam of the technology pack name and version. It is advised thateach loader instance for a technology pack on a server writes to the samefile. This results in one IBM Tivoli Monitoring agent instance that is used tomonitor each technology pack on a server. In this case, in the TivoliEnterprise Portal navigator tree is broken down to technology pack level. Ifrequired, each loader instance can write to its own file. In this case, a IBMTivoli Monitoring agent instance is needed for each file. It is also possible forall 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 bythe loader. If multiple intervals are loaded, the interval must be a logicalmultiple. For example, if a loader is loading 20-minute data and 30-minutedata, the itm.interval must be 60.

v itm.late.latency.offset - used to configure the late latency of loader. Thedefault value is 0 (zero). The valid range: must be >= 0 and <= 1440. Forexample, if value=0, and the file interval=15 minutes, Late flag if maximumlatency is >15. If value=10, and file interval=15 minutes, Late flag ifmaximum 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 toupdate the configuration for all instances at one time. It is easier if IBM TivoliMonitoring logging is turned on for all agents.

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

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

sap start <loader_name>

When IBM Tivoli Monitoring output is enabled, the loader will write metrics tothe IBM Tivoli Monitoring 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 isset to 15 and the current time is 13:10, the first metric that is written is outputat 13:15, then 13:30.

GatewaysDistributed systems only. In a distributed installation, you must run the sectiononly 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 IBMTivoli Monitoring. See the Gateway Framework User Guide for more information.

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

To define the notification target:

Procedure1. Copy a sample NotificationConfig.pm file from the $GATEWAY_ROOT/gateway-

framework/example/NotificationConfig.pm into the vendor subsystem andrelease configuration directory, for example, $GATEWAY_ROOT/config/<vendor-subsys>/<release>/

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

{RULE_TYPE => ’ITM_Notification’,RULE_DESC => ’ITM Notification’,NOTIFICATION_TYPE => ’Alarm|Event’,NOTIFICATION_COMMAND => ’itmlog’, # command line scriptNOTIFICATION_TARGET =>

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

},);

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

3. Edit the NotificationConfig.pm, for the subroutine notification_config() toreturn 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 scriptsThe Tivoli Netcool Performance Manager gateway agent uses an external scriptitmlog.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 currentgateway run or the last gateway run for each gateway configuration.

To report previous gateway notification logs in Tivoli Monitoring, the itmlog.shscript can be customized to process the past number of hours of logs. ThePASS_HOUR variable in the itmlog.sh script is used to define the number of pasthours 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 serviceYou must start the agent service for each Tivoli Netcool Performance Manageragent on each monitored Tivoli Netcool Performance Manager server before theperformance metrics displays in IBM Tivoli Monitoring.

You can configure and start the agents on a Tivoli Netcool Performance Managerserver 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, andselect Start Service.

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

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


Chapter 5. Processing the Gateways IBM Tivoli MonitoringAgent Historical Data

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

To see previous Gateway processes, you must enable at least short-term historicaldata 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 attributesv Update queries for the workspace tables and chartsv 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 currentlyrunning instances data, records from completed Gateway process are continuouslyreported and are repeatedly collected and delivered to the warehouse. For detailson Gateway agent external script customization, see Gateways.

Enabling Historical Data CollectionInstructions 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 Yearlyv Quarterlyv Monthlyv Dailyv Hourly

5. In the pruning area, select the time period to be pruned. For example:v Yearlyv Quarterlyv Monthlyv Daily


v Hourly6. Click Apply to save the configuration.

Updating Time Spans for QueriesYou must update the queries for the bar or line charts and tables with the timespans.

Note: For some common queries, you can use the option: Apply to all viewsassociated with this view's query. For more information, refer to the IBM TivoliMonitoring documentation.

Updating Time Spans for Bar and Line ChartsInstructions on how to update the time span for the bar chart in the Tivoli NetcoolPerformance Manager Gateways workspace.

About this task

The workspace is shown in the following figures:

Figure 6. Tivoli Netcool Performance Manager Gateways workspace


To update the time span for a query:

Procedure

1. Click the

icon in the chart. The system displays the Select the Time Spandialog box.

Figure 7. Gateway Instance workspace

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

2. Select the Real time plus Last option and enter a time span.3. Click OK to save the workspace.

Updating Time Spans for TablesPerform the following procedure for the File Transfers and File Parsing tables inboth the Tivoli Netcool Performance Manager Gateway and Gateway Instanceworkspace.

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.

Figure 8. Select the Time Span


Managing Historical Data by PruningWith historical data collected from agents and sent to Tivoli Data Warehouse, thestorage space that is used in Tivoli Data Warehouse continues to grow if it is notmanaged.

To manage this issue on an ongoing basis, you must set up pruning of Tivoli DataWarehouse data according to any relevant data policies. For more information, seethe IBM Tivoli Monitoring: Administrator Guide.

Figure 9. Select the Time Span

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


Chapter 6. Integrating Alarm

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

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

Tivoli Netcool Performance Manager provides a portable package that enables thegeneration of internal Tivoli Netcool Performance Manager alarms from thecommand line on a non Tivoli Netcool Performance Manager core server. The mostsuitable method of handling alarms depends on the existing applicationinfrastructure:v Customer already has IBM Tivoli Monitoring and Netcool/OMNIbusv Customer has Netcool/OMNIbus and other non-IBM IT monitoring solutionsv Customer does not have Netcool/OMNIbus or IBM Tivoli Monitoringv Customer has IBM Tivoli Monitoring but other non-IBM Fault Management

solution

Existing application infrastructureThe existing application structure.

Customer already has IBM Tivoli Monitoring andNetcool/OMNIbus

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

Customer has Netcool/OMNIbus and other non-IBM ITmonitoring solutions

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

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


Customer does not have Netcool/OMNIbus or IBM TivoliMonitoring

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

Tivoli Netcool Performance Manager internal alarms can be generated using thealarm package. The standard Tivoli Netcool Performance Manager alarm exportfunctions can be used to forward these alarms to external systems, for examplethrough email or SNMP.

Customer has IBM Tivoli Monitoring but other non-IBM FaultManagement solution

In this case, the custom Tivoli Netcool Performance Manager agents can beintegrated into the customer's existing IBM Tivoli Monitoring infrastructure.

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

Generating the alarm packageInstructions on how to generate the package.

Procedure1. 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 isgenerated from the agents.

Note: The package includes the password that is provided in the databaseconfiguration. If this password is not encoded, then the plain text password isreadable on the target server.

3. Extract the archive on the target server. The following folders are created:v bin - contains the alarm_generator filev 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

ParameterCLIformat PL-SQL format Description Default

notification_id Integer INTEGER Alarm notification Id. None.


Table 3. Alarm generator parameters (continued)

ParameterCLIformat PL-SQL format Description Default

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 triggeredthe 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, seeProbable causes .

None.

specific_problem String VARCHAR2(255) Specific alarm problem. None.

additional_text String VARCHAR2(255) Any additional text. None.

trend_indication String VARCHAR2(255) 'more severe' (raised) or 'lessSevere' (cleared), see TrendIndications .

None.

report_id Integer NUMBER Associated report Id, which isgiven as alarmapi_admin -r.

None.

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

event_time String:

yyyyMMddHHmmss.

DATE Optional. Alarm time. Whenthe alarm reflects a past event,it must be set to the event time.If not provided, it is assumedto be the current time.

Currenttime.

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

Note: The alarm spool daemon asd sap process must be running to raisealarms in Tivoli Netcool Performance Manager. The daemon is started andstopped, 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 typesIt is possible that the Tivoli Netcool Performance Manager accepts non-standardvalues, but alarms with non-standard values cannot be forwarded to SNMPrecipients, 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 causesLists all the possible values for probable_cause.

Table 5. Probable Causes

Probable cause Probable cause

adapterError 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


Table 5. Probable Causes (continued)


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


Table 5. Probable Causes (continued)


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

iODeviceError transmitFailure

keyExpired transmitFailureX733

lanError transmitterFailure

leakDetected trunkCardProblem

lineCardProblem unauthorizedAccessAttempt

localNodeTransmissionError unavailable

localNodeTransmissionErrorX733 underlayingResourceUnavailable

lossOfFrame underlyingResourceUnavailable

lossOfFrameX733 unexpectedInformation

lossOfMultiFrame ventilationsSystemFailure

lossOfPointer versionMismatch

lossOfRealTimel versionMismatchX733

Trend IndicationsList of all the possible values for trend_indication.

Table 6. Trend Indication

Trend Indication

More Severe

Less Severe

No Change


SeverityList of all the possible values for alarm_severity.

Table 7. Severity values

Severity

Cleared

Indeterminate

Critical

Major

Minor

Warning



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

This section describes the metrics that are collected for each Tivoli NetcoolPerformance Manager agent, the log files used, and the default IBM TivoliMonitoring navigation layout.

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

Loader metrics and navigation layoutThis section details the loader metrics and navigation layout.

Loader agent log filesThe list of loader agent log files.

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

The IBM Tivoli Monitoring agent for Tivoli Netcool Performance Manager loadershas the following attributes:v Loader Namev Technology Pack Namev Technology Pack Versionv Reporting Start Timev Reporting End Timev Reporting Durationv Interval Start Timev Interval End Timev Interval Durationv File Processing Start Timev File Processing End Timev File Processing Durationv Number of LIF files processedv Total Size of LIF files processedv Number of LIF files successfully processedv Percentage LIF files successfully processedv Number of LIF files unsuccessfully processedv Percentage LIF files unsuccessfully processedv Minimum Latency - the time between Interval End Time and File Processing

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

End Time


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

Default IBM Tivoli Monitoring navigation layoutDefault 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 Monitoringproduct documentation.

Default Loader workspaceThe default workspace for the Tivoli Netcool Performance Manager applicationLoaders item in the IBM Tivoli Monitoring Navigator contains four frames inaddition 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 thesystem:– 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– Interval Start Time– File Processing Duration– Minimum Latency– Maximum Latency– Late


The corresponding cell within the file processing and latency tables is red for thefollowing 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 workspaceThe default workspace for a technology pack that is selected beneath a loadercontains 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– 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– 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 thefollowing 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 layoutThis section describes the application server metrics and navigation layout.

Application server agent log filesThe list of application server agent log files.

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

It contains the following logs:

Table 8. Application server log files

Log Description

UsageUsage 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


Table 8. Application server log files (continued)

Log Description

ReportsFor 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 thereport.

v Roles - the user's roles.

v Groups - the user's groups.

v Start Time - either the scheduled starttime or the time a user ran an Immediatereport

v Actual Start Time - the time the reportwas started by the system. This can bedifferent on a busy system.

v Actual End Time - the end time.

v Preparation Time - the length of time fromthe actual start time to just before theReap query.

v Resolution Time - the length of time theReap query takes

v Execution Time - the length of time thefinal report calculation takes.

v Number of Entities - the number ofentities that are returned by the Reapquery, not necessarily the same as thenumber in the final report.

v Number of KPIs - the number of KPIsrequested.

v Number of Rows - the number of rowsthat are returned by the report, includingroll ups.

v Time Interval

Raw data coverageRaw data coverage information:

v Timestamp

v Vendor

v Technology

v KPI

v Rollup Node Name

v Percent complete


Table 8. Application server log files (continued)

Log Description

Busy hour executionBusy 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 completionBusy hour completion information:

v Timestamp (Date / Time)

v Total number of Busy Hours

v Number of Busy Hours complete

v % Busy Hours complete

Summary executionSummary 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 completionSummary completion information:

v Timestamp (Date / Time)

v Total number of Summaries

v Number of Summaries complete

v % Summaries complete

Default IBM Tivoli Monitoring navigation layout

An example of the default navigation layout is as follows:Enterprise


Tivoli Netcool Performance Manager Application ServerUsageReportsCoverage

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

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


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

UsageThe default workspace for Usage contains one frame in addition to the defaultNavigator 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 followingcondition:

Table displays main data coverage attributes -v % Complete < 95

ReportsThe default workspace for Reports contains five frames in addition to the defaultNavigator 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 timesv Table that displays the user session attributesv Table that displays the report execution attributes

CoverageThe default workspace for Coverage contains three frames in addition to thedefault Navigator frame.

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


– 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 hourexecution table are red for the following conditions:v Number of rows = 0 AND Result != 'Completed'

Using IBM Tivoli Monitoring threshold definitions, cells within the summaryexecution table are red for the following conditions:v Number of rows = 0 AND Result == 'failed'

Gateway server metrics and navigation layoutThis section describes the gateway server metrics and navigation layout.

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

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

The IBM Tivoli Monitoring agent for Tivoli Netcool Performance Managergateways logs the following attributes:v Gatewayv Transfer IN/OUT


v Parser

GatewayThe 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 PIDv Gateway Stages including the duration for:

– TRANSFER-IN– PARSER– TRANSFER-OUT

v Period of Execution (crontab)v Execution Start Timev Execution End Timev Status: Normal Exit or Aborted/Killed

Transfer IN/OUTThe 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 PIDv Transfer Rule Namev Transfer Type: IN or OUTv Transfer Protocol (FTP, SCP, RCP, CP)v Transfer Host (IP)v Transfer Start Timev Transfer End Timev Number of files transferredv Total Size of files transferredv Maximum file size

Tivoli Netcool Performance Manager gateways agents can be configured to logper-file information. If configured, the following per-file information is logged:v In File Namev In File Sizev In file name Time Stamp (if available from source)v File Processing Start Timev File Processing End Timev Out File Namev Out File Size

ParserThe information logged for the parser part of the gateway.

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


v Vendor SubSystem (e.g. nokia-utran)v Vendor Release (e.g. 6.0)v Gateway PIDv Engine Rule Namev Engine Start Timev Engine End Timev Number of input files processedv Total Size of input files processedv Number of PIF files producedv Total Size of PIF files producedv Number of LIF files producedv Total Size of LIF files produced

Tivoli Netcool Performance Manager gateways agents can be configured to logper-file information. If configured, the following per-file information is logged:v Input File Namev Input File Sizev Input Filename Time Stamp (if available from source)v File Processing Start Timev File Processing End Timev Out File Name(s) : PIFs and LIFsv Out File(s) Size

Default IBM Tivoli Monitoring navigation layout

An example of the default navigation layout is as follows:Enterprise


Tivoli Netcool Performance Manager Gateways<<Instance Name, e.g. vendor subsystem>>

GatewayParserTransfer

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

Default Gateways workspaceThe default workspace for the Tivoli Netcool Performance Manager applicationGateways item in the IBM Tivoli Monitoring Navigator contains three frames inaddition 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 vendorsubsystems):


– 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 allgateways, all vendor subsystems):– Vendor subsystem Name– 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 followingconditions:v Number of Files Transferred IN = 0v Number of Files Transferred OUT = 0v Number of LIF Files Produced = 0

Individual instanceThe default workspace for an individual Gateways instance contains three framesin 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 bythat agent):– 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 PIF and LIF attributes (for all gateways that are monitored bythat agent):– Vendor subsystem Name– 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 followingconditions:v Number of Files Transferred IN = 0v Number of Files Transferred OUT = 0v Number of LIF Files Produced = 0


Notices

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

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

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

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

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

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement maynot apply to you.

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

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of those


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

IBM may use or distribute any of the information you provide in any way itbelieves appropriate without incurring any obligation to you.

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

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

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

The client examples cited are presented for illustrative purposes only. Actualperformance results may vary depending on specific configurations and operatingconditions.

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

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

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

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

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to actual people or business enterprises is entirelycoincidental.

COPYRIGHT LICENSE:


This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sampleprograms are provided "AS IS", without warranty of any kind. IBM shall not beliable 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 mustinclude 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_.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational 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 andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks 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 andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

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

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of TheMinister for the Cabinet Office, and is registered in the U.S. Patent and TrademarkOffice.

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

Notices 49

http://www.ibm.com/legal/us/en/copytrade.shtml

Java and all Java-based trademarks and logosare trademarks or registered trademarks ofOracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

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

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the followingterms and conditions.

Applicability

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

Personal use

You may reproduce these publications for your personal, noncommercial useprovided that all proprietary notices are preserved. You may not distribute, displayor make derivative work of these publications, or any portion thereof, without theexpress consent of IBM.

Commercial use

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

Rights

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

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

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


IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDINGBUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

Notices 51


IBM®

Printed in USA

Documents

with IBM Corp.€¦ · v Chapter 1, IBM T ivoli Monitoring Integration Overview Overview of steps to integrate T ivoli Monitoring with T ivoli Netcool Performance Manager . v Chapter