ITM Integration Guide · 2014-05-22 · ITM Integration Guide. Note ... v In the main GUI window, select the File menu, point to New, and then select Traffic Template. ... Refer to

IBM Tivoli Netcool Performance Manager 1.3.2Wireless ComponentDocument Revision R2E1

ITM Integration Guide

��

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

© Copyright IBM Corporation 2007, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About This Documentation . . . . . . vAudience . . . . . . . . . . . . . . . v

Document Structure . . . . . . . . . vii

User Publications . . . . . . . . . . ix

Chapter 1. ITM Integration Overview . . 1

Chapter 2. ITM Integration Prerequisites 3

Chapter 3. Tivoli Netcool PerformanceManager Agent Installation andConfiguration . . . . . . . . . . . . 5Installing Tivoli Netcool Performance Manager agentson the ITM server . . . . . . . . . . . . 5

Agent installation. . . . . . . . . . . . 5Installing Tivoli Netcool Performance Manageragents on Tivoli Netcool Performance Managerservers . . . . . . . . . . . . . . . . 12

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

Chapter 4. Tivoli Netcool PerformanceManager Enablement . . . . . . . . 19Enable collection of ITM metrics . . . . . . . 19

Application server . . . . . . . . . . . 19Loaders. . . . . . . . . . . . . . . 21Gateways . . . . . . . . . . . . . . 23

Start Tivoli Netcool Performance Manager agentservice . . . . . . . . . . . . . . . . 24

Chapter 5. Gateways ITM AgentHistorical Data . . . . . . . . . . . 25Enabling Historical Data Collection . . . . . . 25

Updating Time Spans for Queries . . . . . . . 27Updating Time Spans for Bar and Line Charts . . 27Updating Time Spans for Tables . . . . . . 28

Managing Historical Data by Pruning . . . . . 30

Chapter 6. Alarm Integration . . . . . 31Existing application infrastructure . . . . . . . 31

Customer has Netcool/OMNIbus and othernon-IBM IT monitoring solutions . . . . . . 31Customer does not have Netcool/OMNIbus orITM . . . . . . . . . . . . . . . . 31Customer has ITM but other non-IBM FaultManagement solution . . . . . . . . . . 32

Generating the alarm package . . . . . . . . 32Parameter values - lists . . . . . . . . . 34Event types . . . . . . . . . . . . . 34Probable causes . . . . . . . . . . . . 34Trend Indications . . . . . . . . . . . 37Severity . . . . . . . . . . . . . . 37

Chapter 7. Tivoli Netcool PerformanceManager agent metrics and ITMnavigation layout . . . . . . . . . . 39Loader metrics and navigation layout . . . . . 39

Loader agent log files . . . . . . . . . . 39Default ITM navigation layout . . . . . . . 40

Application server metrics and navigation layout . . 42Application server agent log files . . . . . . 42Default ITM navigation layout . . . . . . . 44

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

Notices . . . . . . . . . . . . . . 51

Trademarks. . . . . . . . . . . . . 55

© Copyright IBM Corp. 2007, 2012 iii

iv IBM Tivoli Netcool Performance Manager: ITM Integration Guide

About This Documentation

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

The purpose of this guide is to provide details of integrating IBM Tivoli® Netcool®

Performance Manager with ITM. This document provides information for thedeployment of the following Tivoli Netcool Performance Manager agents on ITM:v application serverv loadersv gateways

AudienceThis guide is intended for administrators or operations specialists responsible forinstalling and administrating ITM and Tivoli Netcool Performance Manager.

Document Conventions

This document uses the typographical conventions shown in the following table:

Table 1: General Document Conventions

Format Examples Description

ALL UPPERCASE v GPS

v NULL

v MYWEBSERVER

Acronyms, device names,logical operators, registrykeys, and some datastructures.

Underscore See Document Conventions For links within a documentor to the Internet. Note thatTOC and index links are notunderscored. Color of text isdetermined by browsersettings.

Bold v Note : The busy hourdeterminer is...

Heading text for Notes, andWarnings.

Small Caps v The Stored SQL dialogbox...

v ...click View ...

v In the main GUI window,select the File menu, pointto New , and then selectTraffic Template .

Any text that appears on theGUI.

Italic v A busy hour is...

v A web server must beinstalled...

v See the User Guide

New terms, emphasis, andbook titles.

© Copyright IBM Corp. 2007, 2012 v

Format Examples Description

Monospace v ./wminstall

v $ cd /cdrom/cdrom0

v /xml/dict

v http://abc.com/products/

v addmsc.sh

v Type OK to continue.

Code text, command linetext, paths, scripts, and filenames.

Text written in the body of aparagraph that the user isexpected to enter.

Monospace Bold

vi IBM Tivoli Netcool Performance Manager: ITM Integration Guide

Document Structure

This document is organized in to the following chapters and appendices:

Table 2: Document Structure

Chapter Description

ITM Integration Overview Overview of steps to integrate ITM withTivoli Netcool Performance Manager.

ITM Integration Prerequisites Integration prerequisites, including ITMinstallation, ITM OS agent installation andnotification target definition for gateways.

Tivoli Netcool Performance Manager AgentInstallation and Configuration

Installing and configuring Tivoli NetcoolPerformance Manager agents for theapplication server, loaders and gateways.

Tivoli Netcool Performance ManagerEnablement

Enabling Tivoli Netcool PerformanceManager for the collection of ITM metrics.Starting

Gateways ITM Agent Historical Data Enabling historical data collection.

Alarm Integration Integrating Tivoli Netcool PerformanceManager alarms.

Tivoli Netcool Performance Manager agentmetrics and ITM navigation layout

Describes the metrics collected for eachTivoli Netcool Performance Manager agent,the log files used and the default ITMnavigation layout.

© Copyright IBM Corp. 2007, 2012 vii

viii IBM Tivoli Netcool Performance Manager: ITM Integration Guide

User Publications

Tivoli Netcool Performance Manager software provides the following userpublications:v release notesv user guidesv online help

The documentation is available for viewing and downloading on the infocenter at:

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.html

© Copyright IBM Corp. 2007, 2012 ix



x IBM Tivoli Netcool Performance Manager: ITM Integration Guide

Chapter 1. ITM Integration Overview

IBM Tivoli Monitoring (ITM) helps monitor and optimize hardware andapplication performance.

The ITM application operates by deploying agents to monitor the performance oftarget systems and to relay the data back to the ITM system, where it can be storedand 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 in order to set up ITM monitoring of TivoliNetcool Performance Manager.

The order of these steps is:1. Prerequisites2. ITM installation3. ITM OS agents installation4. Tivoli Netcool Performance Manager agent installation and configuration5. Tivoli Netcool Performance Manager agents installation on the ITM server6. Tivoli Netcool Performance Manager agents installation on Tivoli Netcool

Performance Manager servers7. Tivoli Netcool Performance Manager enablement8. Enable collection of ITM metrics9. Start a Tivoli Netcool Performance Manager agent service on ITM

© Copyright IBM Corp. 2007, 2012 1

2 IBM Tivoli Netcool Performance Manager: ITM Integration Guide

Chapter 2. ITM Integration Prerequisites

This section describes the integration prerequisites for ITM integration.

ITM installation

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

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

Note: You can install ITM on the same server as one of the Tivoli NetcoolPerformance Manager servers. However, be aware that this configuration adds asignificant resource overhead to that server.

ITM OS agents installation

ITM OS agents must be installed on each of the Tivoli Netcool PerformanceManager servers to be monitored. The OS agent installed must be appropriate forthe server's operating system.

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

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

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

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



Chapter 3. Tivoli Netcool Performance Manager AgentInstallation and Configuration

This section describes the installation and configuration of Tivoli NetcoolPerformance Manager agents.

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

This chapter describes:v Installing Tivoli Netcool Performance Manager agents on the ITM serverv Installing Tivoli Netcool Performance Manager agents on Tivoli Netcool

Performance Manager servers

Installing Tivoli Netcool Performance Manager agents on the ITMserver

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

There are three Tivoli Netcool Performance Manager agents:v loaderv application server (as)v gateways

Agent installationAbout this task

Perform the following steps to install a Tivoli® Netcool® Performance Manageragent on the ITM server.

Procedure1. Unpack the contents of the agent archive.

Note: It is recommended that each agent is unpacked in to a different directoryto avoid files being overwritten. Filenames and the directory structure for eachagent are similar.The CD_ROOT directory of the unpacked software packages contains a graphicalinstallation wizard for each available architecture.If installing on UNIX, the installer requires X-window functionality.

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

The Installer Wizard's Welcome Screen is displayed.The following instructions illustrate installing the Tivoli Netcool PerformanceManager application server agent. The installation for each agent is the same.


3. Click Next , to proceed to ITM installation directory and installable medialocations.

Figure 1. Installer


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

4. Click Next , to proceed to ITM components.

Figure 2. Media locations

Chapter 3. Tivoli Netcool Performance Manager Agent Installation and Configuration 7

Select the following options:v Tivoli Enterprise Monitoring Server (TEMS)

v Tivoli Enterprise Portal Server (TEPS)

v Tivoli Enterprise Desktop Client (TEPD)

If required, also select options to perform a local install and TEMS depotinstall.v Perform a local install of the solution on this machine

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

v Perform a TEMS depot install of the solution in this machine

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

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

Figure 3. ITM components


Enter the TEMS User ID, Password and Hostname.6. Click Next , to proceed to applications to add.

Figure 4. TEMS hostname and administrator


This example illustrates installing the Tivoli Netcool Performance Managerapplication server agent. The appropriate option will be available for eachTivoli Netcool Performance Manager agent.Select Monitoring Agent for TNPMW Application Server .

7. Click Next , to proceed to Confirmation.

Figure 5. Applications


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

Figure 6. Confirmation


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

Installing Tivoli Netcool Performance Manager agents on Tivoli NetcoolPerformance Manager servers

Each of the Tivoli Netcool Performance Manager agents that are to be used mustbe installed on the appropriate Tivoli Netcool Performance Manager server.

For example, installing the Tivoli Netcool Performance Manager application serveragent on the Tivoli Netcool Performance Manager application server. There arethree Tivoli Netcool Performance Manager agents:v loaderv application server (as)v gateways

There are two possible methods for installing Tivoli Netcool Performance Manageragents on Tivoli Netcool Performance Manager servers:v Installation using remote deployment. Allows the Tivoli Netcool Performance

Manager agent to be installed and configured in one step using the TEP GUI.v Local installation. Installs the Tivoli Netcool Performance Manager agent locally

on a Tivoli Netcool Performance Manager server.

Figure 7. Progress


Installation using remote deploymentUsing the TEP GUI allows the Tivoli Netcool Performance Manager agent to beinstalled and configured in one step.

About this task

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

Procedure1. Start the TEP application.2. Right click the server to install on and select Add Managed System .

Note: The OS agent must be running on the Tivoli Netcool PerformanceManager server to continue with remote installation. Refer to the sectionInstalling Monitoring Agents of Chapter 6 of the IBM Tivoli Monitoring Installationand Setup Guide for instructions on how to run OS agents.The Select a Monitoring Agent dialog is displayed.

Figure 8. Right-click menu


3. Select the type of agent to install, and click OK .The configuration parameters for the agent are displayed. See the followingsections 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.Because multiple instances of loader and gateway agents can exist on a singleserver, you will also be asked for a name for the instance. This is not the casefor an application server agent.

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

Application server agent configurationInstruction on how to configure the application server agent.

Figure 9. Select a Monitoring Agent


About this task

Procedure1. Enter or amend any configuration settings, as required.2. Click Finish .

Results

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

Loader agent configurationInstructions on how to configure the loader agent.

Figure 10. New Managed System Configuration


About this task

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

It is recommended that the agent instance name correspond to the technologypack for the loader. The log file directory and log file name must correspond tothe itm.file and itm.folder values given in the loader's properties file. SeeLoaders.

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

Gateway agent configurationInstructions on how to configure the gateway agent.

Procedure1. Provide a Gateway agent instance name.



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

The expression for vendor sub-system name must be consistent with thevendor directory 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. If a Gateway Configuration is being monitoredby multiple Gateway Agent Instances, duplicate records of the same GatewayConfiguration will be reported in the overall Tivoli Netcool PerformanceManager Gateway workspace for every Gateway Agent node.

Figure 12. Instance Name



4. Click Next .5. Provide the Username and Group name.

The Username must be the same as the username used for the GatewayFramework installation. This is usually: virtuo.The Group name. Any group name can be used. The group name is usually:virtuo.

6. Click Finish .

Local installationTo install an agent locally on a server, the procedure is similar to installing TivoliNetcool Performance Manager agents on the ITM server.

Refer to Chapter 6 of the ITM Installation and Setup Guide , for more information oninstalling agents locally.

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



Chapter 4. Tivoli Netcool Performance Manager Enablement

This section describes enabling Tivoli Netcool Performance Manager for ITM.

This section describes how to:v Enable collection of ITM metricsv Start Tivoli Netcool Performance Manager agent service

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

Application serverDistributed systems only. In a distributed installation, this section need only beperformed on the application server.

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

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

Note:

Following an update to the ITM properties file the application server must bere-started. Use the sap utility to restart the application server, for example on theapplication server as user virtuo:sap stop assap start as

See the Tivoli Netcool Performance Manager Administration Guide.

The contents of this file are described below.

Table 1. ITM properties

Property Description

itm.logging.enabled Enable or disable itm logging. Default isfalse , true turns on itm logging. Any othervalue turns it off.

itm.logging.dir The directory that itm logs will be writtento. Default is appl/virtuo/logs/itm .

itm.logging.report.userroles Log user role and group information whenlogging report execution metrics, true turnson user and role logging. Any other valueturns it off. Default is true .

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


Table 1. ITM properties (continued)

Property Description

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 containing the list ofKPIs to calculate coverage for. See belowCoverage file. Default is/appl/virtuo/conf/itm/coverage.txt .

Note: If filenames are changed, the configuration of the Tivoli NetcoolPerformance Manager application server agent must be changed using 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:v Vendor : Entities will be filtered by vendor name. There is no pattern matching,

the name must match exactly. 'Neutral' is not a valid vendor name in thiscontext. Vendor Neutral KPIs must specify a Vendor Specific name as the entityvendor.

v Technology : Entities will be 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 must be a parent of the KPI's entity. It cannot be thesame as the entity's KPI.

v Interval : How long the period used to calculate coverage is. This should bealigned to the interval of the data it is monitoring. It should be the same as, or amultiple of, the data interval.


v Grace Period : How far back in time to go to select the period. This shouldmatch 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 will take this back to 13:02. Aligning the interval to thehour gives 13:00. The time period covered will be 13:00 to 13:30.

See the Tivoli Netcool Performance Manager Administration Guide for moreinformation on the grace period.

Cron jobsCron jobs.

Coverage file

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

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

Coverage frequency

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

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

LoadersDistributed systems only. In a distributed installation, this section need only beperformed on the loader server.

About this task

By default the output of ITM metrics from Tivoli Netcool Performance Managerloaders is disabled. To enable the output of ITM metrics from a loader, a propertyfor the loader's configuration must be edited.

This property must be changed for each loader that is to be monitored. Propertiesin a loader configuration are set using the loader_admin tool's load and unloadparameters.

To change a loader's configuration:

Chapter 4. Tivoli Netcool Performance Manager Enablement 21

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 four properties relating to ITM:v itm.enabled - indicates whether to output metrics for ITM, true enables

output false disables output.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 recommendedthat each loader instance for a technology pack on a server writes to thesame file. This results in one ITM agent instance being used to monitor eachtechnology pack on a server. In this case, in the TEP navigator tree is brokendown to technology pack level. If required, each loader instance can write toits own file. In this case an ITM agent instance would be needed for eachfile. It is also possible for all loaders to write to a single file, with only oneagent instance required.

v itm.folder - the folder to locate the itm.file property in.v itm.interval - how often to write metrics to the ITM file. Ideally, this

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

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

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

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

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

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

sap start <loader_name>

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


GatewaysDistributed systems only. In a distributed installation, this section need only beperformed on 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 ITM.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.

2.

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

4. Edit the NotificationConfig.pm file, for the rule @rules_ITM on theconfiguration entry NOTIFICATION_TARGET for the vendor sub-system 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 sub-system and release.

5. Edit the NotificationConfig.pm , for the sub-routine notification_config() toreturn the reference to @rules_ITM :sub notification_config {

return \@rules_ITM;}

External script customizationThe Tivoli Netcool Performance Manager gateway agent uses an external scriptitmlog.sh within the gateway framework installation.

The script is located in:/appl/virtuo/gways/gateway-framework/vstart

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

Chapter 4. Tivoli Netcool Performance Manager Enablement 23

To report previous gateway notification logs in ITM, the itmlog.sh script can becustomized to process the past number of hours of logs. The PASS_HOUR variable inthe 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

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

Agents can be configured and started on a Tivoli Netcool Performance Managerserver by running the command: <ITM_INSTALL_LOCATION> /bin/itmcmdmanage

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 .

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


Chapter 5. Gateways ITM Agent Historical Data

The Gateways ITM Agent is based on the script data source, and only the currentor last Gateway process records are displayed.

To see previous Gateway processes, you need to enable at least short-termhistorical data collection and storage. Short-term storage can store up to 24 hoursof 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 (TDW)

Note: Before enabling historical data collection, set the PASS_HOUR variable in/appl/virtuo/gways/gateway-framework/vstart/itmlog.sh back to the defaultvalue 0. If the itmlog.sh is configured to return more than just the most recent orcurrently running instances data, records from completed Gateway process arecontinuously reported and will be repeatedly collected and delivered to thewarehouse. For details on Gateway agent external script customization, see SeeGateways.

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 History Collection Configuration dialog box is displayed as shown in Figure1.


2. Select KNI GATEWAY, KNI PARSER and KNI TRANSFER as shown, and clickConfigure Groups and then Start Collection.

3. Click Close .

Figure 15. History Collection Configuration


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

Note: For some common queries, it may be possible to use the option Apply to allviews associated with this view's query. For more information, refer to the ITMdocumentation.

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 “Updating Time Spans for Bar and Line Charts.”

Figure 3:

Figure 16. Tivoli Netcool Performance Manager Gateways workspace

Chapter 5. Gateways ITM Agent Historical Data 27

To update the time span for a query:

Procedure

1. Click the icon in the chart, the Select the Time Span dialog box is displayedas shown in Figure 4.

2. Select the Real time plus Last check box and enter a time span .

3. Click OK.4. 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 Instanceworkspaces.

Procedure

1. Click the icon in the table.2. Select the Last check box and enter a time span.3. Select the Use detailed data check box and in the Time Column drop down list,

select Timestamp

4. Click OK .

Figure 17. Gateway Instance workspace

Figure 18. Select the Time Span


5. Save the workspace.

Figure 19. Select the Time Span

Chapter 5. Gateways ITM Agent Historical Data 29

Managing Historical Data by PruningWith historical data being collected from agents and sent to Tivoli Data Warehouse(TDW), the storage space used in TDW will continue to grow if it is not managed.

To manage this on an ongoing basis, you must set up pruning of TDW dataaccording to any relevant data policies. For more detailed information, see the IBMTivoli Monitoring: Administrator Guide .


Chapter 6. Alarm Integration

The Tivoli Netcool Performance Manager ITM agents do not contain alarmdefinitions.

Alarm definitions can be added to the agents as the customer sees fit. For detailsof how to configure alarms and actions, refer to your ITM 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. Therecommended method of handling alarms depends on the existing applicationinfrastructure:v Customer already has ITM and Netcool/OMNIbusv Customer has Netcool/OMNIbus and other non-IBM IT monitoring solutionsv Customer does not have Netcool/OMNIbus or ITMv Customer has ITM but other non-IBM Fault Management solution

Existing application infrastructure

Existing application infrastructureThe existing application structure.

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

In this case a single-server ITM solution would be deployed to monitor the TivoliNetcool Performance Manager servers only.

The alarms generated by this ITM deployment can be directly integrated into thecustomer's Netcool/OMNIbus system using the existing Tivoli EIF probe.

Customer does not have Netcool/OMNIbus or ITMIn this case a single-server ITM solution would again be deployed to monitor theTivoli Netcool Performance Manager servers.

Tivoli Netcool Performance Manager internal alarms can be generated using thealarm package, and the standard Tivoli Netcool Performance Manager alarmexport functions can be used to forward these alarms to external systems, forexample using E-Mail or SNMP.


Customer has ITM but other non-IBM Fault Managementsolution

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

The customer may already have ITM integration configured with an externalnon-IBM fault management system.

Generating the alarm packageInstructions on how to generate the package.

Procedure1. Execute the following as user virtuo :

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

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

2. Copy the generated package to the server where alarm functionality isrequired.

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

3. Untar the archive on the target server.To generate an alarm from the target server:

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

Where:

Table 2. Alarm generator parameters

Parameter CLI format PL-SQL format Description Default

notification_id Integer INTEGER Alarmnotification Id.

None.

ev_source String VARCHAR2(255) Event/Alarmsource.

None.

ev_type String VARCHAR2(255) Event type, seeEvent types .

None.

monitored_attributeString NUMBER Attribute valuethat triggeredthe alarm, forexample 51.3.

None.

managed_object_classString VARCHAR2(255) Entity name, forexample cell.

None.


Table 2. Alarm generator parameters (continued)

Parameter CLI format PL-SQL format Description Default

managed_object_instance

String VARCHAR2(255) Entity instancename/local key,for example12345.

None.

alarm_predicate String VARCHAR2(255) Alarm predicate. None.

probable_cause String VARCHAR2(255) Probable alarmcause, seeProbable causes .

None.

specific_problem String VARCHAR2(255) Specific alarmproblem.

None.

additional_text String VARCHAR2(255) Any additionaltext.

None.

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

None.

report_id Integer NUMBER Associatedreport Id, givenusingalarmapi_admin-r .

None.

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

None.

event_timeString:

yyyyMMddHHmmss.

DATE Optional. Alarmtime. When thealarm reflects anevent thathappened in thepast, this shouldbe set to theevent time. Ifnot provided, itis assumed to bethe current time.

Current time.

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

Note: The alarm spool daemon asd sap process must be running in order toraise alarms in Tivoli Netcool Performance Manager. The daemon is started andstopped, as user virtuo using the commands sap start asd and sap stop asd

Note: The script requires JavaTM Runtime Environment (JRE) version 1.5.0.The PATH set in the environment must be use the 1.5.0 version of the Javaexecutable.

Chapter 6. Alarm Integration 33

Parameter values - lists

A number parameters have a defined values, including:v Event types

v Probable causes

v Trend Indications

v Severity

Event typesTivoli Netcool Performance Manager may accept non-standard values, but alarmswith non-standard values cannot be forwarded to SNMP recipients, such as TivoliNetcool OMNIbus.

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

Table 6: Event Types

Event type

Communications

QualityOfService

ProcessingError

Equipment

Environmental

Probable causesThis section lists all the possible values for probable_cause .

Table 3. 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


Table 3. Probable Causes (continued)


broadcastChannelFailure nonRepudiationFailure

cableTamper other

callEstablishmentError outOfCPUCycles

callSetUpFailure outOfHoursActivity

commercialPowerFailure outOfMemory

communicationsProtocolError outOfMemoryX733

communicationsSubsystemFailure outOfService

configurationOrCustomisationError outputDeviceError

configurationOrCustomizationError pathTraceMismatch

congestion payloadTypeMismatch

congestionX733 performanceDegraded

connectionEstablishmentError powerProblem

coolingFanFailure powerProblems

coolingSystemFailure powerSupplyFailure

corruptData pressureUnacceptable

coruptData proceduralError

cpuCyclesLimitExceeded processorProblem

databaseInconsistency processorProblems

dataSetOrModemError protectingResourceFailure

dataSetProblem protectionMechanismFailure

degradedSignal protectionPathFailure

degradedSignalX733 pumpFailure

delayedInformation pumpFailureX733

demodulationFailure queueSizeExceeded

denialOfService realTimeClockFailure

diskFailure receiveFailure

dteDceInterfaceError receiveFailureX733

duplicateInformation receiverFailure

enclosureDoorOpen receiverFailureX733

enclosureDoorOpenX733 rectifierFailure

engineFailure rectifierHighVoltage

equipmentIdentifierDuplication rectifierLowFVoltage

equipmentMalfunction reducedLoggingCapability

excessiveBER remoteAlarmInterface

excessiveErrorRate remoteNodeTransmissionError

excessiveResponseTime remoteNodeTransmissionErrorX733

excessiveRetransmissionRate replaceableUnitMissing

excessiveVibration replaceableUnitProblem

explosiveGas replaceableUnitTypeMismatch

externalEquipmentFailure resourceAtOrNearingCapacity


Table 3. Probable Causes (continued)


externalIFDeviceProblem responseTimeExcessive

externalPointFailure retransmissionRateExcessive

farEndReceiverFailure routingFailure

fileError sfwrDownloadFailure

fileErrorX733 sfwrEnvironmentProblem

fire signalLabelMismatch

fireDetected signalQualityEvaluationFailure

fireDetectorFailure smoke

flood softwareError

framingError softwareErrorX733

framingErrorX733 softwareProgramAbnormallyTerminated

frequencyHoppingFailure softwareProgramError

fuseFailure storageCapacityProblem

generatorFailure storageCapacityProblemX733

heatingVentCoolingSystemProblem synchronizationSourceMismatch

highHumidity systemResourcesOverload

highTemperature temperatureUnacceptable

highWind terminalProblem

humidityUnacceptable thresholdCrossed

iceBuildUp timeoutExpired

informationMissing timingProblem

informationModificationDetected timingProblemX733

informationOutOfSequence toxicGas

inputDeviceError toxicLeakDetected

inputOutputDeviceError tranceiverFailure

intrusionDetection transmissionError

invalidMessageReceived transmiterFailure

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 IndicationsThis section lists all the possible values for trend_indication .

Table 4. Trend Indications

Trend Indication

More Severe

Less Severe

No Change

SeverityThis section lists all the possible values for alarm_severity .

Table 5. Severity values

Severity

Cleared

Indeterminate

Critical

Major

Minor

Warning



Chapter 7. Tivoli Netcool Performance Manager agent metricsand ITM navigation layout

This section describes the metrics collected for each Tivoli Netcool PerformanceManager agent, the log files used and the default ITM 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 describes 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:/appl/virtuo/logs/loader

The ITM monitoring agent for Tivoli Netcool Performance Manager loaders has thefollowing 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 ITM navigation layoutDefault ITM navigation layout.

An example default navigation layout is:Enterprise

UNIX Systems<<Hostname>>

Tivoli Netcool Performance Manager Application ServerUsage

ReportsCoverage

To configure ITM workspaces refer to your ITM product documentation.

The default workspace opened when the Tivoli Netcool Performance Managerapplication item is selected in the ITM Navigator contains four frames in additionto the default Navigator frame, as follows:v Bar chart showing report execution metrics (top ten)v Bar chart showing vendor raw data coverage (aggregated)v Table showing user session information:

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

v Table showing data coverage attributes (row per node):– Timestamp– Vendor– Technology– KPI– Rollup Node Name– Percent Complete

Default Loader workspaceThe default workspace for the Tivoli Netcool Performance Manager applicationLoaders item in the ITM Navigator contains four frames in addition to the defaultNavigator frame.

The structure is as follows:v Stacking bar chart showing loader file processing, aggregated for all technology

packs on the platform:– LIF files successfully processed– LIF files unsuccessfully processed

v Bar chart showing maximum data latency, aggregated for all tech packs on theplatform– 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 selected beneath a loader containsfour frames in addition to the default Navigator frame.

The structure is as follows:v Bar chart showing:

– Total number of LIF files processed– LIF files successfully processed– LIF files unsuccessfully processed

v Bar chart showing:– 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

Chapter 7. Tivoli Netcool Performance Manager agent metrics and ITM navigation layout 41

– 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'

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:/appl/virtuo/logs/itm

Containing the following logs.

Table 6. Application server log files

Log Description

UsageUsage information includes:

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 6. Application server log files (continued)

Log Description

ReportsFor each report executed, the following islogged:

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 role(s).

v Groups - the user's group(s).

v Start Time - either the scheduled starttime or the time a user executed anImmediate report

v Actual Start Time - the time the reportwas started by the system. This could besignificantly different 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 returned by the Reap query, notnecessarily the same as the number in thefinal report.

v Number of KPIs - the number of KPIsrequested.

v Number of Rows - the number of rowsreturned by the report, including roll ups.

v Time Interval

Raw data coverageRaw data coverage information includes:

v Timestamp

v Vendor

v Technology

v KPI

v Rollup Node Name

v Percent Complete


Table 6. Application server log files (continued)

Log Description

Busy hour executionBusy hour execution information includes:

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 includes:

v Timestamp (Date / Time)

v Total number of Busy Hours

v Number of Busy Hours complete

v % Busy Hours complete

Summary executionSummary execution information includes:

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 includes:

v Timestamp (Date / Time)

v Total number of Summaries

v Number of Summaries complete

v % Summaries complete

Default ITM navigation layoutDefault ITM navigation layout.



Tivoli Netcool Performance Manager Application ServerUsage

ReportsCoverage


The default workspace opened when the Tivoli Netcool Performance Managerapplication item is selected in the ITM Navigator contains four frames in additionto the default Navigator frame, as follows:v Bar chart showing report execution metrics (top ten)


v Bar chart showing vendor raw data coverage (aggregated)v Table showing user session information:


v Table showing 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 showing usage attributes:


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

Table showing 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 showing ad-hoc report attributes (top ten)v Bar chart showing scheduled report attributes (top ten)v Bar chart showing average report execution timesv Table showing user session attributesv Table showing 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 showing vendor raw data coverage metrics


v Table showing busy hour percent completion:– Timestamp (Date / Time)– Total number of Busy Hours– Number of Busy Hours complete– % Busy Hours complete

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

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

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

Using ITM threshold definitions, cells within the busy hour execution table are redfor the following conditions:v Number of rows = 0 AND Result != 'Completed'

Using ITM threshold definitions, cells within the summary execution table are redfor 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:/appl/virtuo/logs/itm

The ITM monitoring agent for Tivoli Netcool Performance Manager gateways logsthe following attributes:v Vendor SubSystem (e.g. nokia-utran)v Vendor Release (e.g. 6.0)v Gateway PIDv Gateway Stages included::

– TRANSFER-IN– PARSER– TRANSFER-OUT

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

Transfer IN/OUTThe information logged for the Transfer parts of the gateway.

The following information is logged for the Transfer parts of the gateway:v Vendor SubSystem (e.g. nokia-utran)v Vendor Release (e.g. 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 Filename 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 ITM navigation layout



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

File Processing


Default Gateways workspaceThe default workspace for the Tivoli Netcool Performance Manager applicationGateways item in the ITM Navigator contains three frames in addition to thedefault Navigator frame.

The structure is as follows:v Stacked bar chart showing gateway phase durations, aggregated for all vendor

subsystems on the platform:– Transfer IN– Parser– Transfer OUT


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

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

The corresponding cell within the attributes table is red for the 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 showing :

– # Files Transferred IN– # LIF Files Generated

v Table showing transfer attributes (for all gateways monitored by that agent):– Vendor SubSystem Name– Transfer Rule Name– Transfer Type (IN/OUT)– Transfer Start Time– Transfer End Time– Number of Files Transferred

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

The corresponding cell within the attributes table is red for the 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 U.S.A.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 give youany license to these patents. You can send license inquiries, in writing, to:

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

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

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

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 states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not 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 Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way 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 Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

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

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

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

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.

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 the names and addresses used by an actual businessenterprise is entirely coincidental.

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. 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 IBM‘s application programming interfaces.


If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

Notices 53


Trademarks

IBM, 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 http://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.

Cell Broadband Engine and Cell/B.E. are trademarks of Sony ComputerEntertainment, Inc., in the United States, other countries, or both and is used underlicense therefrom.

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.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and TrademarkOffice.

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

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

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

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

Other company, product, and service names may be trademarks or service marksof others.

For trademark attribution, visit the IBM Terms of Use Web site:http://www.ibm.com/legal/us/.


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

http://www.ibm.com/legal/us/


��

Printed in USA

Documents

ITM Integration Guide · 2014-05-22 · ITM Integration Guide. Note ... v In the main GUI window, select the File menu, point to New, and then select Traffic Template. ... Refer to