datamart configuration and operation guide · ibmtivoli netcool performance manager 1.3.2 wirelines...

IBM Tivoli Netcool Performance Manager 1.3.2Wirelines ComponentDocument Revision R2E1

DataMart Configuration and OperationGuide

��

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

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

Contents

Preface . . . . . . . . . . . . . . viiIntended audience . . . . . . . . . . . . viiTivoli Netcool Performance Manager - WirelineComponent . . . . . . . . . . . . . . vii

Chapter 1. Introduction . . . . . . . . 1Configuring DataMart GUI . . . . . . . . . 1Opening DataMart GUI. . . . . . . . . . . 4The Tivoli Netcool Performance Manager DataMarttabs and utilities . . . . . . . . . . . . . 4

Configuration . . . . . . . . . . . . . 5Data Manager . . . . . . . . . . . . . 5Metric . . . . . . . . . . . . . . . 5Monitor . . . . . . . . . . . . . . . 5Resource. . . . . . . . . . . . . . . 6

Where to go from here . . . . . . . . . . . 6

Chapter 2. Configuring users andgroups . . . . . . . . . . . . . . . 7Creating a user . . . . . . . . . . . . . 7

Deleting a user . . . . . . . . . . . . 8Creating a group of users . . . . . . . . . . 8

Deleting a group . . . . . . . . . . . . 9Granting rights to groups . . . . . . . . . . 9

Understanding the DataMart modules . . . . 10

Chapter 3. Configuring inventory . . . 13Before you begin . . . . . . . . . . . . 13Configuring your network inventory . . . . . . 13

Using the Inventory Tool . . . . . . . . . 14Creating an inventory profile . . . . . . . . 15Configuring your discovery . . . . . . . . . 16

Selecting your network discovery method . . . 17Specifying IP addresses . . . . . . . . . 18Defining an SNMP configuration . . . . . . 19Specifying SNMP community names . . . . . 21Specifying an ICMP configuration . . . . . . 23Configuring labels for subelements . . . . . 24Specifying synchronization . . . . . . . . 25Inserting resources . . . . . . . . . . . 25Specifying automatic grouping . . . . . . . 26Specifying repository group rules . . . . . . 27Selecting modules . . . . . . . . . . . 27

Running an inventory profile . . . . . . . . 28Viewing the log file. . . . . . . . . . . 29Reloading collectors . . . . . . . . . . 29Deleting a profile . . . . . . . . . . . 29

SNMP bandwidth control and collection smoothing 29Bandwidth control . . . . . . . . . . . 30Collection smoothing . . . . . . . . . . 30

Understanding file formats . . . . . . . . . 33Element file . . . . . . . . . . . . . 34Subelement file . . . . . . . . . . . . 34

Managing dynamic changes . . . . . . . . . 35Guidelines . . . . . . . . . . . . . . 36

CME formula command template . . . . . . 37Example based on process illustration . . . . 37Example for 2233_IF family . . . . . . . . 38CME processing . . . . . . . . . . . . 39Discovery server responsibilities . . . . . . 40Logging policy . . . . . . . . . . . . 40

Configuring a bulk collector inventory . . . . . 41Understanding a bulk collector inventory . . . . 42

Importing bulk files . . . . . . . . . . 42Bulk collector inventory file sets . . . . . . 43pollinv and pollprofile commands . . . . . . 44Inventory polling and the cron table . . . . . 44

Directories and files (location, naming, and format) 45Bulk file format examples . . . . . . . . . 46

Element resources . . . . . . . . . . . 46Subelement resources . . . . . . . . . . 46Inventory arguments . . . . . . . . . . 46

Chapter 4. Creating grouping rules . . 47Before you begin . . . . . . . . . . . . 47Creating grouping rules . . . . . . . . . . 47

Using operators and functions . . . . . . . 48Using conditions . . . . . . . . . . . 52

Using grouping rules . . . . . . . . . . . 53Testing grouping rules . . . . . . . . . . . 53

Saving test results . . . . . . . . . . . 55Copying grouping rules . . . . . . . . . 55Moving grouping rules . . . . . . . . . 55Deleting Grouping Rules . . . . . . . . . 56Understanding the file format . . . . . . . 56

Viewing rule database information . . . . . . 56Viewing properties . . . . . . . . . . . . 57Using syntax for grouping rules . . . . . . . 58

Using static text . . . . . . . . . . . . 58Creating variables . . . . . . . . . . . 58

Using a text editor to create grouping rules. . . . 58Exporting grouping rules . . . . . . . . . 58Importing grouping rules . . . . . . . . . 59

Understanding the file format . . . . . . . . 59Grouping rule example . . . . . . . . . . 59

Name with static text . . . . . . . . . . 60Name with a variable . . . . . . . . . . 60Nested variable . . . . . . . . . . . . 61Condition . . . . . . . . . . . . . . 61

Example of nested conditions . . . . . . . . 62Condition . . . . . . . . . . . . . . 62Nested condition . . . . . . . . . . . 62Second nested condition . . . . . . . . . 63Variable . . . . . . . . . . . . . . 63

Example of combining text, a variable, and acondition . . . . . . . . . . . . . . . 64

Chapter 5. Collection and aggregation 65Before you begin . . . . . . . . . . . . 65Configuring data collection requests . . . . . . 65

© Copyright IBM Corp. 2012 iii

Setting the collection period . . . . . . . . 66Configuring aggregation requests . . . . . . . 66

Configuring a percentile value . . . . . . . 66Filtering requests . . . . . . . . . . . . 67

Sorting columns . . . . . . . . . . . . 67Validating the requests . . . . . . . . . . 67

Chapter 6. Configuring calendars . . . 69Using the Calendar Configuration Tool . . . . . 69Creating customized calendars . . . . . . . . 69

Creating a one-time calendar . . . . . . . 71Creating a daily calendar . . . . . . . . . 71Creating a weekly calendar . . . . . . . . 72Creating a monthly calendar. . . . . . . . 72

Deleting a calendar . . . . . . . . . . . . 73Using the Calendar Selector . . . . . . . . . 73

Chapter 7. Writing custom formulas . . 75Before you begin . . . . . . . . . . . . 75What is a formula? . . . . . . . . . . . . 75

Merging discovery results . . . . . . . . 76Creating formulas . . . . . . . . . . . . 77

Editing the inventory_subelement.txt file . . . 77Testing formulas. . . . . . . . . . . . 78Saving formulas . . . . . . . . . . . . 79Modifying a custom formula . . . . . . . 80

Standard rules for writing formulas . . . . . . 80Dim declaration . . . . . . . . . . . . 80OIDVAL expression line . . . . . . . . . 82

OIDINST instruction . . . . . . . . . . . 83Example . . . . . . . . . . . . . . 85

Types of variables . . . . . . . . . . . . 86Instance variables . . . . . . . . . . . 86Temporary variables . . . . . . . . . . 87Host variable . . . . . . . . . . . . . 88

Returning a result . . . . . . . . . . . . 88Comments in formulas . . . . . . . . . . 88Syntax for functions . . . . . . . . . . . 88

Mathematical functions . . . . . . . . . 88Other functions . . . . . . . . . . . . 89SNMP-specific functions . . . . . . . . . 90Aggregate functions . . . . . . . . . . 90Filter functions . . . . . . . . . . . . 91Distribution function . . . . . . . . . . 91

AddForMissing() operator . . . . . . . . . 92Example . . . . . . . . . . . . . . 92

Using the Formula Selector . . . . . . . . . 93Creating a formula group. . . . . . . . . 93Finding a formula . . . . . . . . . . . 93Copying formulas . . . . . . . . . . . 94Deleting a formula . . . . . . . . . . . 94Renaming a formula . . . . . . . . . . 94Discovery formula for a Redback Ethernetinterface . . . . . . . . . . . . . . 95Collection formula example . . . . . . . 102Merge formulas example . . . . . . . . 105inventory_sub-element.txt . . . . . . . . 1051213_IF . . . . . . . . . . . . . . 1052233_IF . . . . . . . . . . . . . . 1052233_HCOctets_Support . . . . . . . . . 106

2233_HCPackets_Support . . . . . . . . 1061213_IF_Invariant . . . . . . . . . . . 1062233_IF_Invariant . . . . . . . . . . . 106<CustomerSpecific>_KEY . . . . . . . . 107

Formula error messages . . . . . . . . . . 107Understanding the inventory_subelements.txt file 108

SysObjId . . . . . . . . . . . . . . 109FilterFormulaName . . . . . . . . . . 110SubElementFamilyName to cancel . . . . . 110

Chapter 8. Configuring thresholds . . 111About thresholds . . . . . . . . . . . . 111Threshold types . . . . . . . . . . . . 111

User profiles and threshold types. . . . . . 112Basic computation . . . . . . . . . . . 112Statistic used for processing . . . . . . . 112Exceeding a threshold level. . . . . . . . 113Interpolation. . . . . . . . . . . . . 113

Threshold deployment . . . . . . . . . . 113Examples . . . . . . . . . . . . . . 114

TRAP generation rules . . . . . . . . . . 118Using the threshold definition period setting . . . 118

Processing traps . . . . . . . . . . . 118Launching the threshold tool . . . . . . . . 119Adding a threshold . . . . . . . . . . . 121

Selecting metrics . . . . . . . . . . . 121Applying thresholds to a group of subelements 122Specifying subelements . . . . . . . . . 122

Configuring burst or period thresholds . . . . . 123Configuring thresholds . . . . . . . . . 123Configuring mode . . . . . . . . . . . 123Configuring maximum percent over for burstand period thresholds . . . . . . . . . 124Configuring burst values . . . . . . . . 124Configuring period values . . . . . . . . 125

Configuring baseline thresholds . . . . . . . 126Trapping threshold violations . . . . . . . . 129

Trapping threshold violations to the log file . . 129Sending trapped threshold violations tospecified hosts . . . . . . . . . . . . 130

Chapter 9. Managing MIBs . . . . . . 131MIB groups . . . . . . . . . . . . . . 131Compiling a MIB . . . . . . . . . . . . 131

Printing or saving trace information . . . . . 133Deleting a MIB . . . . . . . . . . . . 133Viewing MIB file source . . . . . . . . . 134Browsing MIB files . . . . . . . . . . 134Viewing compiled MIB files . . . . . . . 134

Chapter 10. Editing resources . . . . 139Filtering elements and subelements . . . . . . 139Viewing resource information . . . . . . . . 140

Viewing elements . . . . . . . . . . . 140Viewing subelements . . . . . . . . . . 141Viewing subelement groups . . . . . . . 141Viewing property details . . . . . . . . 142Viewing reports . . . . . . . . . . . 143Viewing thresholds . . . . . . . . . . 143

Exporting resources . . . . . . . . . . . 144

iv IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

Importing resources . . . . . . . . . . . 145Adding resources . . . . . . . . . . . . 145

Adding elements . . . . . . . . . . . 145Adding subelements . . . . . . . . . . 146Adding composite subelement relations . . . 147Adding reports . . . . . . . . . . . . 147Adding thresholds. . . . . . . . . . . 148Creating a property . . . . . . . . . . 152

Modifying resources . . . . . . . . . . . 158Modifying an element . . . . . . . . . 158Modifying a subelement . . . . . . . . . 159Modifying a report . . . . . . . . . . 160Modifying Thresholds . . . . . . . . . 161

Deleting resources . . . . . . . . . . . . 165Deleting elements or subelements . . . . . 166Deleting subelement groups . . . . . . . 166Deleting resources within groups . . . . . . 166Deleting properties . . . . . . . . . . 166Deleting composite Subelement relations . . . 167

Deploying reports . . . . . . . . . . . . 167

Chapter 11. Viewing collected data 169Viewing graphical charts for files . . . . . . . 169Viewing graphical charts for subelements . . . . 170Viewing graphical charts for subelement groups 171Saving a graph . . . . . . . . . . . . . 171Printing a graph . . . . . . . . . . . . 172Configuring graphs . . . . . . . . . . . 172

Displaying crosshairs . . . . . . . . . . 172Displaying a grid . . . . . . . . . . . 173Configuring a title . . . . . . . . . . . 173Configuring the X-Axis . . . . . . . . . 174Customizing the Y-Axis . . . . . . . . . 174Configuring curves . . . . . . . . . . 174Configuring a graph legend . . . . . . . 175

Chapter 12. Viewing the list ofcollectors . . . . . . . . . . . . . 177Viewing collector information . . . . . . . . 177Viewing scheduler information . . . . . . . 179Viewing data manager information . . . . . . 181

Viewing target information . . . . . . . . . 184Viewing detailed technical information . . . . . 185Stopping and restarting a local collector . . . . 187

Restarting a local collector . . . . . . . . 187Configuring watchdog for collector memorychecking . . . . . . . . . . . . . . . 187

Parameters . . . . . . . . . . . . . 187Activation of memory checking . . . . . . 188Setting lower and upper limits . . . . . . 188Setting inflation limit . . . . . . . . . . 188

Chapter 13. Viewing status . . . . . 191Viewing DataMart status . . . . . . . . . 191Removing a lock from the database . . . . . . 192

Chapter 14. Viewing databaseinformation . . . . . . . . . . . . 193Viewing database free space status . . . . . . 194Viewing database parameters . . . . . . . . 195Viewing database statistics . . . . . . . . . 195Viewing the Tivoli Netcool Performance Managerversion information . . . . . . . . . . . 195Viewing MetaData. . . . . . . . . . . . 195Viewing MetricData . . . . . . . . . . . 196Viewing client information . . . . . . . . . 197Viewing database status . . . . . . . . . . 197Viewing disk information . . . . . . . . . 199

Chapter 15. Exporting or ImportingMetadata . . . . . . . . . . . . . 201Exporting data . . . . . . . . . . . . . 201

Export files . . . . . . . . . . . . . 204Importing data . . . . . . . . . . . . . 210

Glossary . . . . . . . . . . . . . 215

Notices . . . . . . . . . . . . . . 221

Trademarks . . . . . . . . . . . . 225

Contents v

vi IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

Preface

The purpose of this manual.

lBM® Tivoli Netcool Performance Manager 1.3.2 is a bundled product consisting ofa wireline component and a wireless component. .

The purpose of this guide is to help you work with Tivoli Netcool PerformanceManager DataMart.

Intended audienceThe audience for this guide is the Tivoli Netcool Performance Manageradministrators who assign permissions, create groups, associate users with reports,and manages Tivoli Netcool Performanc Manager DataMart.

Tivoli Netcool Performance Manager - Wireline ComponentIBM® Tivoli Netcool Performance Manager consists of a wireline component(formerly Netcool/Proviso) and a wireless component (formerly Tivoli® Netcool®

Performance Manager for Wireless).

Tivoli Netcool Performance Manager - Wireline Component consists of thefollowing subcomponents:v DataMart is a set of management, configuration, and troubleshooting GUIs. The

Tivoli Netcool Performance Manager System Administrator uses the GUIs todefine policies and configuration, and to verify and troubleshoot operations.

v DataLoad provides flexible, distributed data collection and data import of SNMPand non-SNMP data to a centralized database.

v DataChannel aggregates the data collected through Tivoli Netcool PerformanceManager DataLoad for use by the Tivoli Netcool Performance ManagerDataView reporting functions. It also processes online calculations and detectsreal-time threshold violations.

v DataView is a reliable application server for on-demand, web-based networkreports.

v Technology Packs extend the Tivoli Netcool Performance Manager system withservice-ready reports for network operations, business development, andcustomer viewing.

The following figure shows the different Tivoli Netcool Performance Managermodules.

© Copyright IBM Corp. 2012 vii

Tivoli Netcool Performance Manager documentation consists of the following:v Release notesv Configuration recommendationsv User guidesv Technical notesv Online help

The documentation is available for viewing and downloading on the informationcenter at http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.html.

viii IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide

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

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

Chapter 1. Introduction

Tivoli Netcool Performance Manager DataMart supports a graphical user interfacethat lets you perform various administrative tasks. You can also manage, andreview information about the resources and metrics being collected and stored inthe Oracle database.

The initial startup steps vary depending on whether you installed a minimaldeployment or a distributed environment deployment. For a distributedenvironment deployment, the $PVHOME variable is defined as /opt/datamart bydefault. For a minimal deployment, the default is /opt/proviso/datamart.

Configuring DataMart GUIExplains how to configure DataMart GUI after a Tivoli Netcool PerformanceManager installation.

About this task

The $PVMHOME variable is defined as /opt/datamart by default. For minimaldeployment, the default is /opt/proviso/datamart.

To configure DataMart GUI, follow these steps:

Procedure1. Log in as pvuser (or the user name that you specified during installation) on

the system where DataMart is installed.

Note: When you run the pvm command to access the DataMart for the firsttime, you must log in as pvuser.

2. Ensure that the Oracle database and Listener are running. For moreinformation, see the IBM Tivoli Netcool Performance Manager: Installation Guide.

3. Source the DataMart environment using the following command:. /opt/datamart/dataMart.env

4. Execute the following command:pvm

The following information and prompt is displayed:------------------------------------------------------Tivoli Netcool/Proviso - Wed Apr 7 09:34:34 IST 2010Licensed Materials - Property of IBM5724-P55, 5724-P57, 5724-P58, 5724-P59Copyright IBM Corporation 2007. All Rights Reserved.US Government Users Restricted Rights- Use,duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

Script revision 30.20DataMart configuration

- Default Association------------------------------------------------------

Enter password for PV_ADMIN:

© Copyright IBM Corp. 2012 1

11. The following output shows that the process to start the DataMart iscompleted successfully.

Complete with Success ..._______________________________________________________________________________________________The following Time Zone has been modified :_________________________________________________________________________________________

id | Date (in GMT) | offset in | Name |Aggset status| | seconds | |

_________________________________________________________________________________________

1 | 2010/04/07 08:42:06 | 3600 | Greenwich Mean Time_2010_DST |Aggset not created1 | 2010/10/31 01:00:00 | 0 | Greenwich Mean Time_2010 |Aggset not created1 | 2011/03/27 01:00:00 | 3600 | Greenwich Mean Time_2011_DST |Aggset not created1 | 2011/10/30 01:00:00 | 0 | Greenwich Mean Time_2011 |Aggset not created1 | 2012/03/25 01:00:00 | 3600 | Greenwich Mean Time_2012_DST |Aggset not created1 | 2012/10/28 01:00:00 | 0 | Greenwich Mean Time_2012 |Aggset not created1 | 2013/03/31 01:00:00 | 3600 | Greenwich Mean Time_2013_DST |Aggset not created1 | 2013/10/27 01:00:00 | 0 | Greenwich Mean Time_2013 |Aggset not created1 | 2014/03/30 01:00:00 | 3600 | Greenwich Mean Time_2014_DST |Aggset not created1 | 2014/10/26 01:00:00 | 0 | Greenwich Mean Time_2014 |Aggset not created1 | 2015/03/29 01:00:00 | 3600 | Greenwich Mean Time_2015_DST |Aggset not created1 | 2015/10/25 01:00:00 | 0 | Greenwich Mean Time_2015 |Aggset not created1 | 2016/03/27 01:00:00 | 3600 | Greenwich Mean Time_2016_DST |Aggset not created1 | 2016/10/30 01:00:00 | 0 | Greenwich Mean Time_2016 |Aggset not created1 | 2017/03/26 01:00:00 | 3600 | Greenwich Mean Time_2017_DST |Aggset not created1 | 2017/10/29 01:00:00 | 0 | Greenwich Mean Time_2017 |Aggset not created1 | 2018/03/25 01:00:00 | 3600 | Greenwich Mean Time_2018_DST |Aggset not created1 | 2018/10/28 01:00:00 | 0 | Greenwich Mean Time_2018 |Aggset not created1 | 2019/03/31 01:00:00 | 3600 | Greenwich Mean Time_2019_DST |Aggset not created1 | 2019/10/27 01:00:00 | 0 | Greenwich Mean Time_2019 |Aggset not created1 | 2020/03/29 01:00:00 | 3600 | Greenwich Mean Time_2020_DST |Aggset not created1 | 2020/10/25 01:00:00 | 0 | Greenwich Mean Time_2020 |Aggset not created1 | 2021/03/28 01:00:00 | 3600 | Greenwich Mean Time_2021_DST |Aggset not created1 | 2021/10/31 01:00:00 | 0 | Greenwich Mean Time_2021 |Aggset not created1 | 2022/03/27 01:00:00 | 3600 | Greenwich Mean Time_2022_DST |Aggset not created1 | 2022/10/30 01:00:00 | 0 | Greenwich Mean Time_2022 |Aggset not created1 | 2023/03/26 01:00:00 | 3600 | Greenwich Mean Time_2023_DST |Aggset not created1 | 2023/10/29 01:00:00 | 0 | Greenwich Mean Time_2023 |Aggset not created1 | 2024/03/31 01:00:00 | 3600 | Greenwich Mean Time_2024_DST |Aggset not created1 | 2024/10/27 01:00:00 | 0 | Greenwich Mean Time_2024 |Aggset not created1 | 2025/03/30 01:00:00 | 3600 | Greenwich Mean Time_2025_DST |Aggset not created1 | 2025/10/26 01:00:00 | 0 | Greenwich Mean Time_2025 |Aggset not created1 | 2026/03/29 01:00:00 | 3600 | Greenwich Mean Time_2026_DST |Aggset not created1 | 2026/10/25 01:00:00 | 0 | Greenwich Mean Time_2026 |Aggset not created1 | 2027/03/28 01:00:00 | 3600 | Greenwich Mean Time_2027_DST |Aggset not created1 | 2027/10/31 01:00:00 | 0 | Greenwich Mean Time_2027 |Aggset not created1 | 2028/03/26 01:00:00 | 3600 | Greenwich Mean Time_2028_DST |Aggset not created1 | 2028/10/29 01:00:00 | 0 | Greenwich Mean Time_2028 |Aggset not created1 | 2029/03/25 01:00:00 | 3600 | Greenwich Mean Time_2029_DST |Aggset not created1 | 2029/10/28 01:00:00 | 0 | Greenwich Mean Time_2029 |Aggset not created1 | 2030/03/31 01:00:00 | 3600 | Greenwich Mean Time_2030_DST |Aggset not created1 | 2030/10/27 01:00:00 | 0 | Greenwich Mean Time_2030 |Aggset not created

==> Press <Enter> to continue ....

12. Press Enter. The DataMart GUI appears.

Chapter 1. Introduction 3

Opening DataMart GUIExplains how to start and open DataMart GUI after it has been configured

About this task

To start Datamart GUI after it has been configured, follow these steps:

Note: The $PVMHOME variable is defined as /opt/datamart by default. Forminimal deployment, the default is /opt/proviso/datamart .If the main toolbar appears gray, the database is not running.

Procedure1. Log in as pvuser (or the user name that you specified during installation) on

the system where DataMart is installed.2. Ensure that the Oracle database and Listener are running. For more

information, see the IBM Tivoli Netcool Performance Manager: Installation Guide.3. Source the DataMart environment using the following command:

. /opt/datamart/dataMart.env

4. Enter the following command:$PVMHOME/bin/pvm

The Tivoli Netcool Performance Manager DataMart tabs and utilitiesThe Tivoli Netcool Performance Manager DataMart GUI supports the followingtabs:v Configurationv Metricv Resourcev Monitorv Data Manager

Note: Each tab contains various graphical utilities that allow you to performadministrative tasks.


Note: Tivoli Netcool Performance Manager DataMart supports an Adobe AcrobatPDF help system. You can access the online help system by selecting TivoliNetcool Performance Manager DataMart Help... from the Help menu.

ConfigurationThe Configuration tab supports the following utilities:v Import-Export Configuration - lets you import and export metadata

(configuration data), such as requests, elements, and formulas between twoTivoli Netcool Performance Manager DataMart systems. For example, you canshare information with other Tivoli Netcool Performance Manager DataMartusers in different locations.

v Users Configuration - lets you create, modify, or delete user and group accountsand assign access privileges.

v Calendar Configuration - lets you define time ranges for data collection.v Request Editor - lets you manage data collection parameters such as frequency

and storage.

Data ManagerThe Data Manager tab supports the following utility:v Data Viewer - lets you view and verify collected data in the database in

graphical charts.

MetricThe Metric tab supports the following utilities:v Formula Editor - lets you create, modify, or delete formulas, which are a series

of operations applied to one or more MIB objects.v MIB Browser - lets you browse a MIB-tree structure. You can test a specific OID

before using it in a new formula or a request. You can drag an OID to anotherapplication where you want it to be used (such as Formula Editor, RequestEditor, or Dashboard Editor).

v MIB Compiler - lets you convert a management information base (MIB) file inStructure of Management Information (SMI) format to the Tivoli NetcoolPerformance Manager DataMart internal format. You can also add new MIBs inaddition to the MIBs provided with Tivoli Netcool Performance ManagerDataMart.

MonitorThe Monitor tab supports the following utilities:v Collector Information - provides information about collector parameters and

activities.v DataMart Status - lets you browse through a list of Tivoli Netcool Performance

Manager DataMart modules that are registered in the current database, and themodules that are locked. Lets you unlock modules when necessary.

v Database Information - provides detailed statistical and graphical informationabout the Tivoli Netcool Performance Manager DataMart database.

Chapter 1. Introduction 5

ResourceThe Resource tab supports the following utilities:v Inventory Tool - lets you import, analyze, and discover elements and

subelements in your network.v Rule Editor - lets you create and edit grouping rules.v SNMP Configuration - lets you define and maintain Simple Network

Management Protocol (SNMP) parameters such as community names, portnumber, timeout value, and retry values.

v Resource Editor - lets you add, modify, export, and import elements,subelements, element groups, subelement groups, reports, and thresholds.

Where to go from hereThe following chapters explain how to use the various DataMart utilities toadminister Tivoli Netcool Performance Manager.


Chapter 2. Configuring users and groups

Explains how to create users and groups so that customers can access TivoliNetcool Performance Manager DataMart. It also explains how to grant accessrights.

Creating a userExplains how to create one or more user accounts for end-users that need access toTivoli Netcool Performance Manager DataMart. You can specify whether a useraccount has read-only or full access rights to the Tivoli Netcool PerformanceManager DataMart modules.

About this task

To create a user, follow these steps:

Procedure1. Click Users Configuration in the Configuration tab. The User Configuration

Toolwindow appears. By default, the following users appears in the Users tab:v pvuser - an anonymous user account that you can provide to any authorized

person for access to Tivoli Netcool Performance Manager DataMart. Bydefault, the pvuser user account belongs to the admin group and has readand write access rights to all modules. You can modify the pvuser useraccount.

Note: You can choose the name for this user account during installation. Forexample, instead of pvuser, you can choose Jerry or operations. See the IBMTivoli Netcool Performance Manager: Installation Guide for more details.

v root - the user account for the person(s) responsible for managing the TivoliNetcool Performance Manager DataMart system on a network. By default,the root user account belongs to the admingroup and has read and writeaccess rights to all modules. You cannot modify the root user account.

Note: The daemon user is a special account used by Oracle. You cannotmodify this account.

2. Click New from the File menu. The New User window appears.3. Enter the end user's operating system login name (in alphanumeric characters

only) in the Login name box.4. Optionally, enter the user's full name in the Full Name box.5. Click on a group name in the Not member of box. For example, admin.6. Click the left arrow button to add the user to that group. The group name you

selected appears in the Member of box.7. Click OK to accept your selections.8. Repeat steps 2 through 6 to create as many user accounts as needed.9. Grant the required user access rights to Tivoli Netcool Performance Manager

DataMart modules.See the section entitled “Granting rights to groups” on page 9 for instructionson granting user access rights to Tivoli Netcool Performance Manager DataMartmodules.


Deleting a userProcedure1. Select the user name from the Users tab.2. Click Delete from the Edit menu. A message box appears, asking you to

confirm your choice.3. Click Yes to confirm the deletion. The user is removed.

Creating a group of usersExplains how to create a group for users that need access to Tivoli NetcoolPerformance Manager DataMart. When you add users to a group, the usersbelonging to that group automatically inherit the rights from the group.

About this task

To create a group, follow these steps:

Procedure1. Click Users Configuration in the Configuration tab.2. Click the Groups tab. The following groups appear in the Groups tab by

default:v admin - this group has write access privileges to all Tivoli Netcool

Performance Manager DataMart modules. At least one user account mustbe a member of this group. You cannot modify or delete this group.

v default - this group has read-only access to the Data Viewer module (bydefault), which can be used to view data that is collected for verificationpurposes.

v pvUsers - this group has read-only access to all Tivoli Netcool PerformanceManager DataMart modules (by default).

3. Click New from the File menu. The New Group window appears.4. Enter the name of the group in the Group name box. For example,

Operations.

Note: The group name must consist of only alphanumeric characters.5. Optionally, enter a unique description for the group in the Description box.6. Click a user name in the Are not members box. You can make multiple

selections.7. Click the left arrow button to add a user or users to the group. The user name

appears in the Are members box.8. Click OK to accept your selections.9. Repeat steps 3 through 7 to add as many users to the group as needed.

10. See the section entitled “Granting rights to groups” on page 9 for instructionson granting access rights to Tivoli Netcool Performance Manager DataMartmodules.


Deleting a groupAbout this task

You must ensure that you do not delete the following DataMart user groups:

Group Name Description

default Default users.

admin Tivoli Netcool Performance ManagerDataMart Administrators.

pvUsers Tivoli Netcool Performance ManagerDataMart users.

To delete a group, follow these steps:

Procedure1. Select the group name from the Group tab.2. Click Delete from the Edit menu. Confirm your choice.3. Click Yes to confirm the deletion. The group is removed.

Granting rights to groupsAbout this task

After you create groups as detailed in “Creating a group of users” on page 8, youcan assign rights to specific Tivoli Netcool Performance Manager DataMartmodules for that group.

To grant rights to groups, follow these steps:

Procedure1. Create a group as detailed in the section “Creating a group of users” on page 8

Or2. Double-click an existing group to edit it.3. Click the Permissions at the bottom of the dialog box. The dialog box expands

and displays the Permissions group.4. Click in the Read or Write column to grant access for the wanted module. An

"X" appears signifying that the module is selected. If you select Write access fora module, Read access is automatically included.For example, you might want to give full access rights for all modules tonetwork operators and read-only rights to corporate executives.See the next section entitled " “Understanding the DataMart modules” on page10" for descriptions of each module.

Note: Click again in a column if you must remove an "X."5. Click OK when you are finished.6. Repeat steps 2 through 4 until you granted all necessary rights to all groups.

Chapter 2. Configuring users and groups 9

Understanding the DataMart modulesAbout this task

The following tables list the Tivoli Netcool Performance Manager DataMartmodules for which you can grant access rights.

Table 1. Configuration tools

Module Description

Import/Export ConfigurationLets you transfer hosts, subelements,dashboards, requests, formulas, calendars,and thresholds between two Tivoli NetcoolPerformance Manager DataMart systems.

Users Configuration Lets you create user and group accounts andassign access privileges.

Calendar Configuration Lets you define and modify time ranges fordata collection.

Request Editor Lets you manage data collection parameterssuch as frequency and storage.

Table 2. Metric tools

Module Description

Formula Editor Lets you create formulas, which are a seriesof operations applied to one or more MIBobjects.

MIB Browser Lets you browse a MIB tree structure.

MIB Compiler Lets you convert a management informationbase (MIB) file in Structure of ManagementInformation (SMI) format to the TivoliNetcool Performance Manager DataMartinternal format.

Table 3. Resource tools

Module Description

Inventory Tool Lets you search for all SNMP hosts on anetwork and discover elements andsubelements.

Rule Editor Lets you create and edit grouping rules.

SNMP Configuration Lets you define and maintain SimpleNetwork Management Protocol (SNMP)community names.

Resource Editor Lets view resource information, importresources, export resources, and to deleteresources.

Table 4. Monitor tools

Module Description

Collector Information Provides information about collector activity.

Tivoli Netcool Performance ManagerDataMart Status Tool

Lists all modules that are currently active.Lets you unlock modules when necessary.

Dashboard Manager Lets you launch dashboards requests.


Table 4. Monitor tools (continued)

Dashboard Editor Lets you create dashboard requests in real-time.

Table 5. Data Manager tools

Module Description

Data Viewer Lets you use view and verify collected datain the database.

Table 6. Selector tools

Module Description

Formula Selector Lets you select a formula from the formulalibrary.

Dashboard Selector Displays a list of configured dashboardsrequests.

Calendar Selector Lets you designate a time to automaticallylaunch one or more requests.

Table 7. Command Line Interfaces

Module Description

Resource Manager (resmgr) Lets you import, export, modify, and deleteobjects in the database. These objects includeelements, subelements, element andsubelement groups, properties, thresholds,inventory profiles, Tivoli NetcoolPerformance Manager DataMart users andgroups, web users, web reports, and webaccess.

Database Manager (dbMgr) A utility that lets you create a databasechannel.

Chapter 2. Configuring users and groups 11

Chapter 3. Configuring inventory

Explains how to import, analyze, and discover elements and subelements in yournetwork using Resource Manager or the Inventory Tool.

Before you begin

Before configuring your network inventory, ensure that:v Your computer is connected to a TCP/IP network and has a valid IP address.v The default collector is running. For more information, see the Viewing the list of

collectors section from IBM Tivoli Netcool Performance Manager: DataMartConfiguration and Operation Guide.

v You have installed Tivoli Netcool Performance Manager Technology Packs if youwant to use default grouping rules. For instructions on installing Tivoli NetcoolPerformance Manager Technology Packs, see the IBM Tivoli Netcool PerformanceManager: Installation Guide.

Note: The Discovery Server uses the dig command from your operating system tointeract with a DNS server. If the system is not configured correctly and thecommand does not work, then Tivoli Netcool Performance Manager fails indiscovery from DNS. Consult your operating system configuration guide fortroubleshooting information. The dig command with the axfr option uses aninsecure method of retrieving the entire contents of a DNS server. For safetyreasons, many DNS servers are now configured to reject such a command. For asecure DNS server, the dig command does not return anything. For such DNSservers, the Discovery Server with DNS import does not work. Either reconfigurethe DNS to allow the axfr option, or try another import mechanism, such as filesor /etc/hosts.

Configuring your network inventoryExplains how to gather information about elements and subelements in yournetwork using the Inventory Tool.

When you execute an inventory, the discovery phase searches for SNMP andnon-SNMP elements and subelements (known as resources). As these resourcesrespond, their addresses are stored in the database for use in the analysis phase.The analysis phase stores the addresses of associated subelements.

You can also configure an inventory using the inventory and resmgr commands.For more information, see the IBM Tivoli Netcool Performance Manager: CommandLine Interface Guide.

Note: The Inventory Tool can find only operational elements. If an element isdown, it is not detected.


Using the Inventory ToolProcedure

Click Inventory Tool in the Resource tab. The Inventory Tool window appears. Alist of defined profiles appears. An example profile called default also appears, butit is not functional.

Important: The Tivoli Netcool Performance Manager default inventory profilesettings are used as examples. You must supply settings that are valid for yournetwork.To create new profile, see “Creating an inventory profile” on page 15.The following information is provided in the Configuration tab:

Item Description

Name The name that you specify for the profile.

Mode The discovery mode. See “Creating aninventory profile” on page 15 forinstructions on selecting a discovery mode.

Collector IDThe collector identifier. Elements andsubelements discovered while running theprofile are assigned to this collector.

To view the status on collectors, see ViewingCollector Information in the IBM Tivoli NetcoolPerformance Manager: DataMart Configurationand Operation Guide.

Information Additional information about the profile,such as the IP addresses you are includingor excluding. If you are importing data froma file, the file name is displayed.

StatusProvides the following information:

v Ready appears after you create or edit aprofile.

v EndDiscovery appears after you completea discovery.

v SynchroReady appears afterpre-synchronization when you run theprofile from the command line (see note).

v EndSynchro appears aftersynchronization.

v GroupingReady appears afterpre-grouping when you run the profilefrom the command line (see note).

v EndGrouping appears after grouping.

Module to Run Indicates the modules that are enabledwithin the selected profile. A module can beenabled or disabled by clicking its name.

Note: The inventory command-line interface (CLI) command launches theInventory Tool from the command line. See the IBM Tivoli Netcool PerformanceManager: Command Line Interface Guide for instructions on using this CLI.


Creating an inventory profileThe Inventory Tool Wizard lets you create and modify one or more profiles. Aprofile lets you define your network inventory. You can create different profiles fordifferent resources in your network.

About this task

You can create a profile to do the following:v Divide your network between different SNMP community names. Grouping

resources using alternative SNMP community names improves performance byproviding collectors with multiple community names that limit the number oftimeouts.

v Separate resources with invariants that require editing during synchronizationfrom those that require no editing.

v Separate requests that you want to run at different times or different intervals.v Have one profile for each collector.

CAUTION: If you include the same resource in two profiles, running the secondprofile overwrites the results of the first profile.

To use the Inventory Tool Wizard, follow these steps:

Procedure1. Select New profile from the Edit menu.

Note: Select Edit profile from the Edit menu if you want to edit an existingprofile.

2. Enter a name for the profile in the Profile name field. If you are editing anexisting profile, this field is automatically populated with the name of theprofile.

Important: You must not use any of the following reserved terms in the nameof your profile:

elt inventory slowwan

exclude ipaddress snmpconf

fastlan lan subelt

filestoinsert mode subeltinv

grouping objectfilter synchro

icmp objectfilter wan

include rulefilter ||ROOTROOT||

3. If you are managing multiple networks where there is a possibility ofduplicate IP addresses, select the Use duplicate IP addresses option. Thisoption indexes a subelement name with a collector number so that identical IPaddresses can be differentiated.

4. If you want to check invariants assigned to new resources against only othersub-elements that belong to the same element, select the Enforce Sub-elementinvariant uniqueness per element option.

Chapter 3. Configuring inventory 15

5. If you want to poll or collect SNMP data from a network where the IP addressis dynamic, select Target devices use dynamic DNS. Typically, residentialcable modems use the dynamic IP address assignment.

6. Select an identifier for the collector in the Collector number and DiscoverySNMP collector number lists. All elements and subelements discovered whilerunning this profile are assigned to this collector.If you are importing a bulk file for a Bulk Collector inventory, ensure that youselect a valid Bulk Collector number. For more information, see the IBM TivoliNetcool Performance Manager: Installation Guide.A network discovery is performed using the default collector that can later beassigned to a secondary collector. Ensure that the default collector can reachall nodes in the inventory.

7. In the Directory Configuration field, click Browse to g to the directory whereyou want to write the files generated by the inventory process. The default isthe importexport directory where you installed Tivoli Netcool PerformanceManager DataMart.

8. Click Next to proceed.9. Select the modules that you want to configure for this profile. By default, all

modules are selected. If you are editing an existing profile, modules that youdo not configure retain the existing values. If you are creating a profile,modules that you do not configure retain the default values.The following table lists the supported modules:

Module Description

Discovery Lets you specify the parts of your networkto include in the profile.

Synchronization Lets you synchronize new data for yourprofile with existing data.

Automatic GroupingLets you specify grouping rules for thisprofile (default or custom).

See Chapter 4, “Creating grouping rules,” onpage 47 for step-by-step instructions oncreating custom grouping rules.

10. Click Next. To complete the configuration, see “Configuring your discovery.”

Note: This section assumes that you select all three modules. If you disableone or more of the modules, the window sequence might differ.

Configuring your discoveryExplains how to use the Discovery Tool Wizard to specify what resources areincluded in your network inventory profile.

To fully configure your profile, you must complete the tasks detailed in thefollowing sections.

Note: The window sequences displayed in the Discovery Tool Wizard might differaccording to the selections you made.


Selecting your network discovery methodExplains how to specify the discovery method for your network. You can choose toeither discover network elements using SNMP requests, or import networkelements from a Domain Name Server (DNS), Network Information Service (NIS),or host file.

Note: Ensure that a running collector is available in your environment beforeselecting either the Discover elements & Analyze or Import elements & Analyzeoptions. No running collector is required for the import from ASCII file option asthe element and subelement files are produced by the bulk collector or an externalprovisioning system.

Discovering network resourcesAbout this task

To discover network resources, follow these steps:

Procedure1. Click the Discover elements & Analyze check box. This option uses SNMP

requests to discover the IP addresses you specify in “Specifying IP addresses”on page 18.

Important: IBM recommends that you use this option only for small networks,since the length of time required to run might make it impractical to use on alarge network.This network discovery method uses SNMP Get commands to retrieve MIBOIDs from target devices that are used to identify device types and theircharacteristics.

2. Click Next. See “Specifying IP addresses” on page 18 to continue.

Importing network resourcesAbout this task

To import network resources, follow these steps:

Procedure1. Click the Import elements & Analyze check box. This option allows you to

import resources from a domain-based (for example, DNS or NIS) or file-based(for example, /etc/host, HP OpenView, or elements list) source. This mode isrecommended for large networks.If you import network resources and also list specific IP addresses (asexplained in “Specifying IP addresses” on page 18), Tivoli Netcool PerformanceManager discovers only elements that appear in both the imported list and thelist of specific IP addresses.

Note: The “Import elements & Analyze” mode must be used if you plan torun the inventory profile using the subprofile option.

2. To import resources from a domain-based source, select one of the followingoptions:v From DNS: lets you import elements by specifying a valid Domain Name

Server (DNS). Specify the DNS in the box to the right. The Inventory Tooldisplays the DNS in /etc/resolv.conf.


v From NIS: lets you import elements by specifying a valid NetworkInformation Service (NIS) domain name. Specify the NIS domain name in thebox to the right. The Inventory Tool displays the result of the UNIXcommand domainname if it is valid.

3. To import resources from a file-based source, select one of the followingoptions:v From /etc/hosts file format: lets you import elements by specifying a file in

the same format as the /etc/hosts file. For example:

IP address HostName UNIX alias

195.2.53.9 Cisco24 Cisco2500_BOSTON

195.2.53.15 Cisco25 Cisco2500_NEWYORK

Click Browse to specify the path and file name of the input file.v From HP OpenView file format: lets you import elements by specifying a

file in the HPOpenView format. This file can be created by the command:$OV_BIN/ovtopodump -r

Redirect the output to a file, then click Browse to specify the path and filename of the input file.

v From elements list: lets you import elements by specifying a file. The filecontains a list of IP addresses with one address on each line. This file can bea .txt file.

Note: The From elements list option must be used if you plan to run theinventory profile using the subprofile option.

Click Browse to specify the path and file name of the input file.4. Click Next. See “Specifying IP addresses” to continue.

Specifying IP addressesExplains how to include or exclude IP addresses from your network inventoryprofile. The IP address options are displayed.

Procedure1. Enter the IP addresses you want to include or exclude from your network

discovery in the IP address entry box.

Note: The Discovery Tool Wizard supports both IPv4 and IPv6 addressformats.

2. Click <<Add to add it to the list of IP addresses to include in the discovery, orclick Add>> to add it to the list of IP addresses to exclude from the discovery.

3. To modify an existing IP address: highlight the entry, so that it appears in theIP address entry box. Modify the entry in the IP address entry box, then clickModify.

4. To delete an IP address: highlight it and click Delete. To delete all the entries inthe IP address include area, click <<Clear. To delete all the entries in the IPaddress exclude area, click Clear>>.

5. Click the ARP Query (Address Resolution Protocol) option if you want to useARP tables to discover the elements specified in the IP address include area.

6. Click Next. See “Specifying SNMP community names” on page 21 to continue.


Defining an SNMP configurationExplains how to use the SNMP Configuration Tool to define general parameters forSNMP requests. The SNMP Configuration Tool is launched.

Procedure1. Click Open for the SNMP Configuration Tool.

Note: You can also launch the SNMP Configuration tool from the commandline using the snmpconf command-line interface (CLI) command. See the IBMTivoli Netcool Performance Manager: Command Line Interface Guide forinstructions on using this CLI.

2. Click Apply Filter to list all of the elements currently in the SNMPconfiguration database. The following information is displayed for each entry:

Item Description

Name Specifies the name of the device associatedwith this SNMP configuration.

IP Address Specifies the IP address, mask, subnets, oraddress list for the device. Both IPv4 or IPv6address formats are acceptable.

Type Specifies the type of the device.

Read community Specifies the name of the SNMP readcommunity.

Collector ID Identifies the collector associated with thisSNMP configuration. A setting of 0 appliesthe SNMP configuration to all collectors.

Write Community Specifies the name of the SNMP writecommunity.

Timeout Specifies the length of time (in seconds) towait for a response from a request.

Retries Specifies the number of times that a requestis tried again in the event of a requestfailure.

Port Specifies the number of the port associatedwith this SNMP configuration.

Bandwidth Specifies the maximum amount of traffic (inKbps) permitted for the corresponding IPaddress. For more information, see “SNMPbandwidth control and collectionsmoothing” on page 29.

Version Specifies the SNMP version associated withthis SNMP configuration.

3. To add or modify an entry, click Add or Update as appropriate.4. Specify the name of the device associated with this SNMP configuration in the

Element field.v Click Browse to launch the Resource Editor, where you can drag entries

from the Resource Editor Elements tab to the Element field of the SNMPConfiguration: Add/Update Configuration window.

v Click Resolve to attempt to resolve the name in the Element field, and ifpossible, update the IP Address fields accordingly.


5. Specify the IP address, mask, subnets, or address list in the IP Address field.You can either drag entries from the addresses listed in the Range Defined onProfile field, or you can enter address information manually.v To specify an individual IP address, enter the address in the IP Address

field. For example:192.168.64.1 (IPv4 address format)Orabcd:ef01:2345:6789:ABCD:EF01:2345:6789 (IPv6 address format)

v To specify a mask of IP addresses, enter the mask information in the IPaddress field.Entering a range in IPv4 format:192.168.1-3.1 : Indicates an address list of 192.168.1.1, 192.168.2.1, and 192.168.3.1.192.168.64.* : Indicates an address range of 192.168.64.0 to 192.168.64.255.192.168.10,16.* : Indicates two address ranges, one from 192.168.10.0 to192.168.10.255, and another from 192.168.16.0 to 192.168.16.255.

Entering a range in IPv6 format:

Note: IPv6 ranges can be specified using the CIDR notation. The characters'*' and '-' are not accepted.– To specify a CIDR subnet, enter the subnet information in the IP address

field. For example:192.168.1.0/24 : Indicates an address range of 192.168.1.0 to 192.168.1.255.192.168.1.0/25 : Indicates an address range of 192.168.1.0 to 192.168.1.127.2620:0:860:2::/64: Indicates an address range of 2620:0:860:2:: to2620:0:860:2:FFFF:FFFF:FFFF:FFFF

– To specify several IP entries for the same SNMP configuration, enter theaddress information in the IP Address field with each entry separated bysemi-colon characters. For example:192.168.64.1;192.168.1-4.1;192.168.64.*;192.168.1.0/24

6. Specify the SNMP version used for this configuration from the Version list.Selecting a specific SNMP version inserts a corresponding version prefix at thebeginning of the Read Community field, while selecting Auto omits theversion prefix.

Note: The ReadCommunity field is automatically populated for the followingVersion options and does not need updating:

SnmpV3-No-AuthSnmpV3-Auth-MD5SnmpV3-Auth-SHASnmpV3-Auth-MD5-Priv-DESSnmpV3-Auth-SHA-Priv-DESSnmpV3-Auth-MD5-Priv-AES,SnmpV3-Auth-SHA-Priv-AES

7. Specify the name of the SNMP read community in the Read Community field.If you selected a specific SNMP version from the Version list, thecorresponding version prefix must be used in the SNMP read communityname. The Read Community field takes the parameters from the followingcontrols and uses them to build the Read Community string:v Security Name: Specifies the user name to be used for this SNMP V3

elementv Auth. Password: Specifies the password to be used for authentication

(MD5) for this SNMP V3 element.


v Priv. Password: Specifies the private password to be used with thefollowing Version options:

SnmpV3-Auth-MD5-Priv-DESSnmpV3-Auth-SHA-Priv-DESSnmpV3-Auth-MD5-Priv-AESSnmpV3-Auth-SHA-Priv-AES

v Context Name: Specifies the context name to be used for this SNMP V3element.

8. Specify the name of the SNMP write community in the Write Communityfield.

9. Specify the length of time (in seconds) to wait for a response from a request inthe TimeOut field.

10. Specify the number of times that a request must be tried again in the event ofa request failure in the Retries field.

11. Specify the number of the port associated with this SNMP configuration in thePort field. A setting of 0 indicates that this SNMP configuration applies to allports.

12. Specify the bandwidth limit for traffic (in Kbps) permitted for this SNMPconfiguration IP addresses in the Bandwidth field. For more information, see“SNMP bandwidth control and collection smoothing” on page 29.

13. Specify the collector associated with this SNMP configuration from theCollector ID list. A setting of 0 indicates that this SNMP configuration isapplicable to all collectors.

14. After specifying the SNMP configuration, click OK.

Specifying SNMP community namesExplains how to specify alternative community names, and determine if the SNMPconfiguration database must be updated if alternative community names are used.The SNMP community name options are displayed

About this task

To specify an SNMP community name, follow these steps:

Procedure1. To add a community name, type the name in the Alternative community names

box, then click Add . You also use the Alternative community names box tospecify an SNMP V3 community name, using the following syntax:&V3[{separator}{option}={value}...]

where:v &V3 - Specifies a required string that indicates that this entry is an SNMP V3

community name.v separator - Specifies a character used to separate options specified in the

community name. The separator can be any character, but the same separatorcharacter must be used to separate all of the options specified in thecommunity name. Typically, you use a ,(comma) character as the separator.However, if the , (comma) character is used in any of the passwords, youcan substitute the comma with any other separator character (for example, /,@, -, and so on).


v option - Specifies one or more option keywords that define an SNMP V3community string. Each option keyword is followed by an = (equals sign).

v value - Specifies a valid value for the specified option. The following tablelists the option keywords along with their associated valid values:

Option Values

SecurityName Specifies the user name to be used for thisSNMP V3 community name.

ContextName Specifies the context name to be used forthis SNMP V3 community name.

AuthPasswd Specifies the password to be used forauthentication (MD5) for this SNMP V3community name.

EngineIdSpecifies the value for the engine ID for thisSNMP V3 community name. This optionkeyword is optional.

AccessModeSpecifies the level of security required forthis SNMP V3 community name. Thefollowing are the valid values for thisoption:

v No-Auth - Indicates that this SNMP V3community name is no more secure thanthe community string provided in SNMPV1 or SNMP V2c.

v Auth-MD5 - Indicates that this SNMP V3community name security levelcorresponds to an unencrypted traffic,authenticated with MD5 hash. Specifyingthis value means that you must alsospecify the SecurityName, ContextName,and AuthPasswd options.

The following example specifies an SNMP V3 community name that uses anMD5 authentication:&V3,AccessMode=Auth-MD5SecurityName=user2ContextName=context2AuthPasswd=1234567890abcdef

2. To modify an existing entry, highlight the entry so that it appears in theAlternative community names box. Modify the entry in the Alternativecommunity names box, then click Modify.

3. To delete an entry, highlight the entry and click Delete. To delete all the entries,click Clear.

4. Click Update SNMP configuration tool with new matching community nameto update the community names in the SNMP configuration database with thealternative community name for elements queried.

5. Click Next to proceed. You can specify which types of elements to include inthe discovery. The left pane displays all the known element types. The rightpane displays the element types currently included in the discovery.

Note: By default, all known element types are included in the discovery.

Important: Ensure that you have installed Tivoli Netcool Performance ManagerTechnology Packs; otherwise the Groups folder does not display any element


type subfolder. See the IBM Tivoli Netcool Performance Manager: Installation Guideand IBM Tivoli Netcool Performance Manager: Pack Installation and ConfigurationGuide for instructions on installing Tivoli Netcool Performance ManagerTechnology Packs.To filter the objects included in the discovery do the following tasks:a. To exclude a specific type of object, drag the object type from the right pane

to the left pane.b. To add a specific type of object, click Unselect All, then drag a specific

object type from the left pane to the right pane.

Important: You can include only those objects that you want to rundiscovery against and not the entire tree.

c. Clear the Insert unknown elements option so that unknown element typesare excluded from the inventory. If you select this option, unknownelements are included in the discovery and are added to a folder calledNONE.

6. Click Next to proceed. See “Specifying SNMP community names” on page 21to continue.

Specifying an ICMP configurationExplains how to specify Internet Control Message Protocol (ICMP) parameters foryour inventory profile.

Procedure1. Choose a network type from the Network type group. Each network type has

different defaults.2. Specify the ICMP parameters, either by accepting the defaults or by modifying

them. The following options are available:

Option Description

Message data size Data size of the ICMP packet. The entry canbe 1 - 64,000 bytes.

Tries Number of times to ping specific IPaddresses if no response is received from theping. Your entry can be 1 - 10.

Time outLength of time (in seconds) to wait for aresponse to a ping before sending anotherping. The length doubles for each additionalping.

For example, if the Timeout value is 5seconds:

v After the first ping, wait 5 seconds.

v After the second ping, wait 10 seconds.

v After the third ping, wait 20 seconds.

Ping interval Length of time (in milliseconds) betweenpings.


Option Description

Ping Window ConfigurationAllows you to configure a pause whensending pings to avoid congestion on thenetwork. If you do not select this option,pings are sent equally spaced, withoutpause, as specified by the Ping Interval.

v Window interval: Length of time (inseconds) to pause in sending pings. Yourentry can be from 0.1 to 100 seconds.

v Window size: Number of pings to sendbefore pausing. Your entry can be from 2to 65,000 pings. It can also be 0, whichdisables the window. Using 0 is the sameas clearing Ping Window Configurationoption.

3. Click Next to proceed. See “Configuring labels for subelements” to continue.

Configuring labels for subelementsExplains how to configure labels (naming conventions) for subelements in yourinventory profile.

Procedure1. Choose the type of element name you want to use. The following options are

available

Option Description Example

Subelement file and formulasconfiguration

Specifies which discovery fileand formulas are used toperform the inventoryprocess.

/opt/datamart/conf/inventory_subelements.txt

Do not use element names Name of the subelement isused alone.

Dlci 10 (Cir 0 b/s)

Use element names Name of the element isconcatenated with the nameof the subelement. Thisoption is enabled by default.

bost_Dlci 10 (Cir 0 b/s)

Use DNS element names Full DNS name of theelement is concatenated withthe name of the subelement.If a DNS name is not foundthen the IP address is used.

bost.forxh001.sample.fr_Dlci10 (Cir 0 b/s)

2. Click Next to proceed. See “Specifying synchronization” on page 25 tocontinue.

Option Description Example

Sub-element file andformulas configuration

Specifies which discovery fileand formulas are used toperform the inventoryprocess.

/opt/datamart/conf/.inventory_subelements.txt

Do not use element names Name of the sub-element isused alone.

Dlci 10 (Cir 0 b/s)


Use element names Name of the element isconcatenated with the nameof the sub-element. Thisoption is enabled by default.

bost_Dlci 10 (Cir 0 b/s)

Use DNS element names Full DNS name of theelement is concatenated withthe name of the sub-element.If a DNS name is not foundthen the IP address is used.

bost.forxh001.sample.fr_Dlci10 .(Cir 0 b/s)

3. Click the Next button to proceed. See See Specifying Synchronization tocontinue.

Specifying synchronizationExplains how to specify the data source for the synchronization of your inventoryprofile.

Procedure1. In the Select Datasource area, select the source of the data to be synchronized

with the results of this discovery from one of the following options:v From database (default) - Tivoli Netcool Performance Manager DataMart

synchronizes the results of this discovery with the data currently in thedatabase.

v From file - Tivoli Netcool Performance Manager DataMart synchronizes theresults of this discovery with the data in the files you specify. Click Browseto specify the path and file name for each of the files.

Note: See “Specifying IP addresses” on page 18 for details on file formats.2. Click Next to proceed. See “Inserting resources” to continue.

Inserting resourcesExplains how to add, remove, or update resources in your network inventory thatyou created or changed since the last network discovery operation.

Procedure1. In the Resources table, select the resources you want to add, update, or delete.

You can select each type of resource and action separately by clicking theappropriate columns. The following actions are supported:

Selection Description

New Add resources found during the discoverythat do not exist in the current data.

Update Update the existing resource data with datafound during the discovery.

Delete Delete the existing resource data that is notfound during the discovery.

The grouping files for your profile are created in the $PVMHOME/importexport/profilename/grouping directory.

2. In the Specify the retry count... area of the window, specify the number oftimes previously existing resources that are not discovered are retried beforethey are deleted from the network inventory.


3. In the Specify the age for resources... area of the window, specify how longpreviously existing resources that are not discovered are retained before theyare deleted from the network inventory.

Note: If the creation date or date of the last update for this resource is olderthan the date specified, the resource is deleted. If the creation date or date ofthe last update for this resource is more recent than the date specified, theresource is not deleted.

4. Click Next to proceed.

Specifying automatic groupingExplains how to group resources together automatically. When you use automaticgrouping, a link is created in the database for each resource that is included in agroup.

About this task

Regrouping the resources modifies these links; however, database changes for theresources are not made. Default grouping rules are only provided if you installedTivoli Netcool Performance Manager Technology Packs. See the IBM Tivoli NetcoolPerformance Manager: Installation Guide for instructions on installing Tivoli NetcoolPerformance Manager Technology Packs.

You need to create custom grouping rules by using the Rule Editor in TivoliNetcool Performance Manager DataMart. See Chapter 4, “Creating grouping rules,”on page 47 for details on creating custom grouping rules.

To specify automatic grouping, follow these steps:

Procedure1. In the Resource table, select the resources you want to add, update, or delete.

You can select each type of resource and action separately by clicking theappropriate columns. The following actions are supported:

Item Description

New Adds links between resources and groups,which adds the resources to the groups.

Update Updates links between resources andgroups. Does not add or delete any links,but only updates existing links.

Delete Deletes links between resources and groups,which removes the resources from thegroups.

The grouping files for your profile are created in the $PVMHOME/importexport/profilename/grouping directory.



Specifying repository group rulesExplains how to set rules for groups in your network inventory.

About this task

The Repository group rules side of the window displays all of the grouping rulesthat can be applied during the grouping operation. The Rules to be used for thisprofile side of the window displays the grouping rules selected for the specifiedprofile. By default, Tivoli Netcool Performance Manager DataMart executes all ofthe grouping rules during the grouping operation.

To specify repository group rules, follow these steps:

Procedure1. Under the Repository group rules side of the window, click Unselect All.

Tivoli Netcool Performance Manager DataMart removes all of the groupingrules from the Rules to be used for this profile side of the window.

2. To apply selected grouping rules to your inventory profile, drag the groupingrules you want to apply from the Repository group rules side of the windowto the Rules to be used for this profile side of the window. Tivoli NetcoolPerformance Manager DataMart refreshes the window to display the groupingrules you selected.

3. To apply all grouping rules to your inventory profile, under the Repositorygroup rules side of the window, click Select All. Tivoli Netcool PerformanceManager DataMart refreshes the window to display all of the grouping rulesfor the specified profile.


Selecting modulesExplains how to specify the modules that are run with your inventory profile.

Procedure1. Select one or all of the following:

v Discovery - gathers information about your network as specified in theprofile.

v Synchronization - synchronizes the new data for this profile with theexisting information.

v Automatic Grouping - applies default or custom grouping rules for thisprofile. To apply custom grouping rules, you must create them and set theirstatus to "active." See Chapter 4, “Creating grouping rules,” on page 47 fordetails.

2. Click Next to proceed. This window displays a summary of the profile that youcreated. Ensure that the profile contains the correct values. If you want tochange any of the values, click Previous to return to the appropriate window.

3. Click Finish to complete your profile. See “Running an inventory profile” onpage 28 for instructions on running your profile, or you can also run a profilefrom the command line.


Running an inventory profileAfter you configure an inventory profile, you need to run it to perform adiscovery.

About this task

To run an inventory profile, follow these steps:

Procedure1. Open the Inventory Tool window, as explained in “Configuring your network

inventory” on page 13.2. Click the name of the inventory profile to be run to select it.3. Specify which modules are to be used with the inventory profile by clicking the

appropriate check boxes in the Module to run field. The module optionsinclude the following:

Note: You can select or clear these check boxes to make immediate andpermanent changes to the database. For example, you might want to run just adiscovery for a bulk inventory. These options are also available when youcreate a profile in the Inventory Tool Wizard.v Discovery - Gathers information about your network as specified in the

profile.v Synchronization - Synchronizes the new data for this profile with the

existing information.v Automatic Grouping - Applies default or custom grouping rules for this

profile. To apply custom grouping rules, you must create them and set theirstatus to active. See Chapter 4, “Creating grouping rules,” on page 47 fordetails.

Note: If you plan to use custom grouping rules, they must be created beforerunning the profile.

v subProfile option - Gathers information about listed network resources thatare imported from a file. The subProfile option is typically used to run adiscovery on a subset of the entire profile. This option can be used withinventory profiles configured as described in “Importing network resources”on page 17.

v Reload collectors - Reloads the collectors at the same time that the inventoryprofile is run.

Important: The Tivoli Netcool Performance Manager default inventoryprofile settings are used as examples. You must supply settings that are validfor your network.

4. Select Run profile from the Actions menu.The Live information tab displays messages about the status of the profile. Themessages are color coded as follows:v Red - Error messagesv Blue - Warning messagesv Black - Informational messages


Viewing the log fileThe last line in the Live Information tab provides the path to theTraceInventory.log file, which you can view and print with a text editor.

Note: This file can be long depending on the size of your network discovery

Reloading collectorsEach profile is assigned to a collector. If the resources included in the profilechange, you need to reload the collector, which updates the collector with thechanges. For optimal performance, you must always reload the collector after youmodify a profile.

About this task

To reload a collector, follow these steps:

Procedure1. Select a profile.2. Select Reload collectors at the bottom of the window, along with the modules

you want to run for this profile.3. Select Run profile from the Actions menu. The profile runs and the collector is

reloaded.Or

4. Click Reload collector at the top of the window. The collector is reloaded butprofile is not run.

Deleting a profileTo delete a profile, follow these steps:1. Open the Inventory Tool, as explained in “Configuring your network

inventory” on page 13.2. Highlight the profile you want to delete. To delete more than one profile

simultaneously, hold down the Ctrl key while selecting the profiles.3. Select Delete profile from the Edit menu. A confirmation dialog box appears.4. Click Yes.

SNMP bandwidth control and collection smoothingThe Bandwidth Control and Collection Smoothing features are used to optimizethe performance of SNMP collectors in your environment.

Before using Bandwidth Control and Collection Smoothing, you must considerhow these features function and how that might impact the operation of yournetwork.


Bandwidth controlSNMP Bandwidth Control is used to prevent SNMP collectors from consumingexcessive bandwidth during periods of heavy network activity. The SNMPbandwidth control feature defines a bandwidth limitation that allows you tomaximize the performance of the collectors without requiring an overly cautiousapproach to collection management.

Bandwidth Control is configured by defining an SNMP configuration in TivoliNetcool Performance Manager DataMart. An SNMP configuration primarilyconsists of a bandwidth limitation that is imposed on the specified collector for thetarget IP addresses listed within the definition. Once defined, SNMP configurationsare propagated to the collectors during the Tivoli Netcool Performance Managerprocessing cycle.

After the SNMP configurations are loaded, Bandwidth Control monitors outboundtraffic originating from the specified target IP addresses. Any collection requestdestined for these target IP addresses is queried to determine if there is sufficientbandwidth available to allow the collection to take place without exceeding thedefined bandwidth limit. If sufficient bandwidth is available, the collection request,along with any similarly grouped requests, is permitted to take place. Whilepermitting grouped collection activity can cause a spike that exceeds thebandwidth limitation for a short time (for example, 5 - 30 seconds), the bandwidthlimitation is enforced based on the average traffic monitored at the collector. Oncethe bandwidth limit is reached, no collections are permitted to take place on thatportion of the network until the bandwidth utilization falls below the definedthreshold. If collection activity is suspended on any portion of the network due toexcessive bandwidth consumption, Bandwidth Control attempts to begin collectionon the next portion of the network.

Note: If several SNMP configurations and bandwidth limits apply to a set of IPaddresses, the lowest defined limit is used to control collection activity for thecollector. For example, if a bandwidth limit of 256 Kbps applies to the IP addressrange 10.64.*.*, but another limit of 64 Kbps is defined for 10.64.1.*, then collectionactivity on the collector is suspended if the network bandwidth exceeds 64 Kbps.

Configuring SNMP bandwidth control in DataMartYou can configure bandwidth control in DataMart using the SNMP ConfigurationTool as described in “Defining an SNMP configuration” on page 19.

Note: You can also configure SNMP Bandwidth Control using the CLI Utility. Seethe IBM Tivoli Netcool Performance Manager: Command Line Interface Guide forinstructions on using this CLI.

Collection smoothingCollection smoothing is used to prevent spikes in collector activity that occur at thebeginning of the polling period. Typically, the collector attempts to execute asmany collection requests as it can in the shortest time possible, which leads to apattern of a brief period of intense activity followed by an extended period ofsparse collection activity.

When enabled, collection smoothing imposes a bandwidth limit on the collectorthat is based on monitored network activity. This bandwidth limit is dynamicallyadjusted and serves to constrain the collector so that collection activity isperformed throughout the polling interval.


Defining a collection smoothing period directs the collector to distribute collectionactivity across a percentage of the polling period, which leaves the remaining timeavailable for other network tasks such as discovery activity. Care must be exercisedin defining this value as specifying too long of a collection smoothing period mightleave insufficient time to recover from unexpected issues and ultimately result inlost collections. Similarly, as collection smoothing essentially delays collectoractivity, you must consider that any network issues such as unexpected latency,high traffic volume, or heavy processor bandwidth utilization might result in slipsin the collection schedule.

Note: If you intend on using collection smoothing with bandwidth control, thelowest bandwidth limitation is used to control collection activity for the collector.For example, if the bandwidth control limit is 64 Kbps and the dynamicallycalculated collection smoothing limit is 100 Kbps, then collection activity on thecollector is suspended if network bandwidth exceeds 64 Kbps. To avoid collectionloss, ensure that bandwidth collection limits are not lower than the range ofbandwidth limits that are expected for collection smoothing activity.

Configuring collection smoothing in DataLoadAbout this task

To configure collection smoothing in DataLoad, follow these steps:

Procedure1. Log in as root on the server where the Topology Editor is installed.2. Set and export your DISPLAY variable.3. Change your working directory to the directory where the Topology Editor is

installed. For example:# cd /opt/IBM/proviso/topologyEditor

4. Start the Topology Editor using the following command:# ./topologyEditor

5. In the Topology Editor, select Topology > Open existing topology. The OpenTopology window is displayed.

6. For the topology source, select From database (v. 443) and click Next.7. Verify that all of the fields for the database connection have the correct values:

v Database hostname - The name of the database host. The default value islocalhost.

v Port - The port number used for communication with the database. Thedefault value is 1521.

v Database user - The user name used to access the database. The defaultvalue is pv_admin.

v Database Password - The password for the database user account. Forexample, pv.

v SID - The SID for the database. The default value is PV.

Click Finish.8. In the Logical View, click the DataChannels folder.9. Click the Global DataChannel properties component, then click the

Advanced Properties tab.10. Search for the following parameters:

SNMP.BANDWIDTHCONTROL.parameter=value


Where:

Parameter/Value Description Recommended Value

AUTOSMOOTHING=false The AUTOSMOOTHINGparameter enables CollectionSmoothing on SNMPcollectors. The parametermust be set to true to activatethe feature.

true

SMOOTHINGSAFETYRATIO=75The SMOOTHINGSAFETYRATIOparameter determines howcollection activity isdistributed (in percentage oftime) throughout the pollinginterval.

The default, andrecommended, value of 75specifies that collectionactivity occurs over 75% ofthe polling interval, leaving25% of the time available forother network tasks,unexpected networkproblems, and so on.

Using too high a setting (forexample, 95), might not leavesufficient time for othernetwork events and mightresult in lost collections.

75

SMOOTHINGCHECKFREQUENCY=60TheSMOOTHINGCHECKFREQUENCYparameter determines howoften (in seconds) dynamiccollection smoothingrequirements arerecalculated.

The default, andrecommended, value of 60specifies that the dynamiccollection smoothingrequirements are recalculatedevery 60 seconds. This valueis used to achieve thegreatest precision in thecalculation.

If less precision in dynamicbandwidth control values isrequired or processor usageis too high, adjust the valueto a higher setting (forexample, 90 seconds).

60


Parameter/Value Description Recommended Value

DISCINITIALQUOTA=512The DISCINITIALQUOTAparameter determines theinitial value (in Kbps) for thedynamic bandwidth controllimitation (in Kbps) fordiscovery activity.

The default, andrecommended, value of 512specifies that the initialbandwidth limitation fordiscovery is 512 Kbps. Ifcollections proceed smoothlyand there is a high level ofdiscovery activity, thediscovery limit isautomatically increased. Ifcollections are blocked, thediscovery limit isautomatically decreased orput on hold until collectionactivity is improved.

512

11. When you are satisfied with your settings, select Topology > Save topology tosave the topology.

12. Select Run > Run Installer and pass it the newly configured topology.13. After the updated configuration is stored in the database, you must restart the

SNMP DataLoad server to initialize the SNMP collectors by issuing the dccmdfrom a command line. See IBM Tivoli Netcool Performance Manager: CommandLine Interface Guide for more information.

Understanding file formatsExplains the formats required for the discovery files and the synchronization files.

See “Specifying synchronization” on page 25 for details about the synchronizationfiles.

The following files are required for a discovery:v element file - contains information about the elements that are imported and

then analyzed.v sub-element file - contains information about the subelements that are imported

and then analyzed.

The following files are required for synchronization:v element file - contains information about the elements that are synchronized

with the results of the current discovery.v sub-element file with invariants - contains information about the subelements

that are synchronized with the results of the current discovery. It contains onlysubelements that have invariants. An invariant is a constant; it does not change.

v sub-element file without invariants - contains information about thesubelements that are synchronized with the results of the current discovery. Itcontains only subelements that do not have invariants. An invariant is aconstant; it does not change.


Element fileThe fields for each element are separated by |_|. If a field has no value it must beleft empty: |_||_|.

An example of the correct format:

Note: The width of this page forces this example to wrap onto several lines. Theinformation for each element must be on one line in the file.

The fields to be included for each element are listed in the following table:

Field Value in Example

Smallest IP address of any interface for theelement.

127.0.0.1

Resolution of the largest IP address of anyinterface for the element.

intranet.sample.fr

sysName for the element. intranet

Name of the element. intranet.sample.fr

Date of discovery, as the number of secondssince 1 January 1970.

950170809

State of the element. on

sysObjectID of the element. 1.3.6.1.4.1.4.1.2.5

IP address of the element. 10.2.4.2

Community name of the element. public

sysDescr of the element. 4BSD/ISODE SNMP

Identifier of the collector. 1

Name of the profile. example

Subelement fileThe fields for each subelement are separated by |_|. If a field has no value it mustbe left empty: |_| |_|.

An example of the correct format:

Note: The width of this page forces this example to wrap onto several lines. Theinformation for each element must be on one line in the file.

The fields to be included for each subelement are listed in the following table:


Field Value in Example

Invariant of the subelement. If thesubelement does not have an invariant, thisfield is the instance of the subelement.

Interface<1>DLCI<0>CIR<0>

Name of the subelement. forxh001.sample.fr_Interface<1>DLCI<0>CIR<0>

Date of discovery, as the number of secondssince 1 January 1970.

950170809

Instance of the subelement. Interface<1>DLCI<0>CIR<0>

Label of the subelement. Dlci 10 (Cir 0 b/s)

Name of the element to which thesubelement is attached.

forxh001.sample.fr

State of the subelement. on

Name of the family of the subelement. Generic_PVC_FrameRelay

The properties of the subelement are after these fields. The properties form a list of theform "name|_|value".

Name of the property of the subelement. State

Value of the property with the name in theprevious field.

active

Name of the property of the subelement. Interface


1

Name of the property of the subelement. DLCI


0

Name of the property of the subelement. CIR


0

Managing dynamic changesExplains how to ensure that Tivoli Netcool Performance Manager detects dynamicchanges, such as index shifting, and updates its state in real time. Doing soprevents unreliable and incorrect information from being stored and minimizesdata loss.

Tivoli Netcool Performance Manager provides a method to automatically detectand reconcile processing when resource invariants change in near real time. Thismethod, implemented in the CME, includes triggering inventory for the elementand updating a running system after information about that element is refreshed.

You can enable/disable collection on a subelement using a CME formula. You canalso start the Inventory for the element, to which the subelement belongs, whenthat subelement becomes disabled. You do so by starting a CME formula designedas an invariant check formula. This formula is based on the SNMP-collectedinvariant for the subelement. When the invariant formula determines that aproperty is changed (the index for example,) it disables the subelement. The CMEthen determines to which element the subelement belongs and passes the elementto the appropriate Discovery server. This Discover server is co-located with the


Inventory process running the element Inventory profile. The Discovery serverrequests the Inventory to do a full reinventory for the specified element.

After the reinventory of the element is complete and the database is updated, theSNMP Collector is reloaded and the subsequent flow of data to the CME correctsitself. From this point on, invariant properties stop triggering reinventory requests.

GuidelinesYou can associate a CME formula with an invariant property to create a formulawith two inputs:v SNMP-collected invariant metricv Invariant property

The formula needs to compare its two input arguments.

About the processThe following example illustrates the process by which the invariant managementoccurs:

v As a result of Inventory, the subelement is assigned instance IF<1> and invariantproperty foo.

v Inventory stores the Invariant property for the subelement in the database.v SNMP Collector is reloaded and starts collecting for the subelement using

instance IF<1>. collectedInvariant metric is also foo.


v InventoryCheck formula compares collectedInventory metric and Inventoryproperty. If they do not match, gate for all other formulas is closed.

v Reinventory request is sent to the correct Discovery server.v Discovery server starts reinventory for the element.v Inventory updates subelement and replaces instance with IF<3>.v Inventory reloads SNMP Collector.v SNMP Collector starts using IF<3> for data collection for the subelement.v collectedInventory becomes foo again.v InventoryCheck formula succeeds.v Gates for all the subelement formulas are open again.

CME formula command templateThe following template:^selfcheckInvariant: (collectedInvariant ~= invariant)old: <anOldValue>new: <aNewValue>

Example based on process illustrationThe following example includes a formula called InvariantCheck that takes thefollowing two arguments:v SNMP collectedInvariant metric (for example, value of ifName)v Invariant property

The Invariant property is set by the inventory and is not changed by the CME.The CME uses this value to check for invariant shift (change) condition. Theformula returns a number (0 or 1). If output is 1, the invariant is valid, otherwise itis invalid.

The built-in method checkInvariant: has an argument which is either true or false.If the argument is true, the subelement invariant is valid, otherwise it is invalid.

When an index shifts, the stored value of the Invariant property for a resource wasfoo. Until this value is updated in the database, the value of the Invariantargument for the formula for this subelement remains foo. At the same time, theSNMP Collector keeps collecting collectedInvariant metric for this resource andgets foo every time. When the CME processes this string record, the Invariantformula compares its first and second arguments and uses the result of thiscomparison to call checkInvariant. Until the collected invariant changes, thisargument remains true.

When an index shift occurs, the SNMP Collector (still using the old index) collectsa different value for the invariant (for example, bar.) When this string metricrecord is processed by the CME, the first argument is now bar and the second(stored invariant) will still be foo. When checkInvariant: is called, the argument isfalse.

A sequence of corrective actions occurs. First, the CME marks this subelementinternal state as DISABLED. While disabled, no deployed CME formulas for thissubelement are evaluated and the metrics are dropped. The subelement locks outall its formulas. Also, no thresholding activity occurs and metrics are not produced.All delta formulas are reset and their stored values are erased. To turn it back toENABLED and to unlock the formulas, checkInvariant: with true must be called;


which occurs when either the Invariant property is changed in the database to bar,or if the collectedInvariant property becomes foo once more.

The CME requests the inventory for this subelement element to be performedimmediately (only when the subelement internal state changes from ENABLED toDISABLED.) The CME locates the appropriate Discovery server and requests areinventory of the element. It also marks the internal status of element as DISABLED.

Once reinventory of the element is complete and the database is updated, theSNMP Collector is reloaded. It now uses the correct instance to collect data fromthe device, and the value of collected invariant metric becomes foo again. WheninvariantCheck is evaluated, both collectedInvariant and Invariant argumentsare foo, so checkInvariant: is started with true. This switches the internalsubelement state to ENABLED, thus unlocking all the subelement formulas. This alsoswitches the internal state of the element to ENABLED. From that point on, if asubelement of this element is disabled, it triggers another reinventory request.

Example for 2233_IF familyThe following example is based on a profile called invTest, a property namedifAlias, an SNMP Collection formula ifAlias, and a change in the value of theifAlias property.

Discovery formulaThe discovery formula is for the 2233_IF family, standard (Extended MIB-II)interfaces:Dim I1 AS Integer Default * NAME If;V1 = OIDVAL(ifType.%I1 format clean, once);V2 = OIDVAL(sysLocation.0, once);V3 = OIDVAL(ifSpeed.%I1, once);V4 = OIDVAL(int(%V3/1000000), once);V5 = OIDVAL(ifName.%I1 format clean, once);V6 = OIDVAL(ifAdminStatus.%I1 format clean, once);V7= OIDVAL(ifAlias.%I1 format clean, once);%V1 index "If<%I1>||IF: %I1 (%V5)(%V4Mbps)||type<%V1>location<%V2>physicalCapacity<%V3>name<%V5>status<%V6>siteID<IP:%H1ifIndex:%I1>ifAlias<%V7>||%V7";

SNMP FormulaSNMP formula:Name: ifAliasSource:ifAlias.%I1

SNMP collection requests:

Formula Group Interval in Minutes Storage

ifAlias Sub-ElementCollect~RFC-2233~Frequent

5 No

ifAlias Sub-ElementCollect~RFC-2233~Normal

15 No


CME FormulaUse the CME invariant metric as the CME invariant formula input argument. Theformula must be associated with subelement invariant property and return either 0or 1. The formula code must include the following statement:self checkInvariant: <true or false>

The formula uses the current input argument. If the argument is false, thesubelement invariant is changed and it must be reinventoried. If the value is true,the subelement is not changed.

CME formula for invariant check:Name: invCheckInput bindings:collectedInvariant - String bound to ifAlias formulainvariantProperty - Property bound to ifAlias propertySource:^selfcheckInvariant: (collectedInvariant = invariantProperty)old: invariantPropertynew: collectedInvariantXML Source:<formula genericId="100010591"><inputBindinglocalName="collectedInvariant" metricId="100010506"type="String"></inputBinding><inputBindinglocalName="invariantProperty" metricId="100004697"type="Property"></inputBinding><source> ^selfcheckInvariant: (collectedInvariant = invariantProperty) old:invariantProperty new:collectedInvariant</source></formula>

Requests for invariant check:

Formula Group Interval in Minutes Storage

invCheck Sub-ElementCollect~RFC-2233~Frequent

5 No

invCheck Sub-ElementCollect~RFC-2233~Normal

15 No

CME processingThe results of starting checkInvariant include:v Disables subelement if enabledv Obtains subelement elementv Acts according to the following table

The following table lists the supported arguments:

Argument Value Internal Element State Action


false ENABLEDObtain remote reference toassociated discovery server

Request reinventory ofspecified element

Set element internal state toDISABLED

false DISABLED No action

true DISABLED Set element internal state toENABLED

true ENABLED No action

In addition, the CME uses a timeout to periodically send reinventory requests tothe Discovery Server. This allows the Discovery Server to be relatively lax with therequests. If a request was missed for any reason and reinventory did not happen(for example, Discovery Server restarted), the request is repeated a few minuteslater.

Discovery server responsibilitiesWhen the Discovery server receives reinventory request, it must run inventoryprocessing for that element. The processing occurs as follows:v Runs discovery for this address or addresses.v Runs synchronization.v Returns result to the sender.

No persistent state is needed.

Logging policyThe logging messages perform the following functions:v Documents the flow or reinventory requests, including origination, any failures

and retries, arrival at Discovery server, attempts to start inventory and outcomeof every attempt. Change in the element internal state (between ENABLED andDISABLED) are also logged. Target element is listed with each of these messages.

v Sends a log message for each element reinventory with the followinginformation:– Date, time, element name, following ENABLED log message conventions– Success or delay/ retry/ failure due to other Inventory lock– Identification of the subelement that triggered the reinventory, with the last

property and new property– Time/date of last reinventory triggered by shift– Time and date of Inventory finished– Confirmation the subelement was put back in collection with reconciled

property


Configuring a bulk collector inventoryExplains how to configure a bulk collector inventory. Bulk collector inventoryprofiles run automatically by default using the pollinv command; however,profiles can be edited and default parameters can be changed.

About this task

See “Understanding a bulk collector inventory” on page 42 for details onimporting files to a bulk collector, inventory file sets, polling commands, anddirectories and file locations.

Important: IBM does not recommend changing the profile name or file names andlocations.

To configure a bulk collector inventory, follow these steps:

Procedure1. Click Inventory Tool in the Resource tab.

Note: The Tivoli Netcool Performance Manager default inventory profilesettings are used as examples. You must supply settings that are valid foryour network.

2. Select New Profile... from the Edit menu.3. Click Next to proceed.

Discovery of files, synchronization of the database, and automatic(out-of-the-box) grouping is selected by default.If you want to changes, clear a box. For example, you might want to discoverfiles only and insert new subelement from the bulk files into the TivoliNetcool Performance Manager database.

4. Click Next to proceed.5. Click Next to proceed.6. Click Next to proceed.

Modify as needed. For example, you can choose not to delete any elementsfrom the database during the inventory by clearing all the “X” symbols fromthe Delete column.

7. Click Next to proceedModify as needed. For example, you can choose not to update any existinggrouping links by clearing all the “X” symbols from the Update column.

8. Click Next to proceed9. Click Next to proceed

10. Click Finish. See “Running an inventory profile” on page 28 for instructionson running an inventory profile.


Understanding a bulk collector inventoryThis section explains the following:v Importing files to a bulk collectorv Bulk collector inventory file setsv pollinv and pollprofile commandsv Inventory polling and the cron tablev Directories and files

Importing bulk filesWhen bulk files are imported to the bulk collector, the collector creates resourcefiles that are sent to the $PVMHOME/importExportBulk/bulk_N/Do directory on theDataMart machine, where N indicates the bulk collector number. Once the resourcefiles arrive in the directory, DataMart starts an inventory based on the gathereddata and transfers the resource files to the $PVMHOME/importExportBulk/bulk_N/Done directory when processing is complete.

About this task

To import files to the Bulk Collector, follow these steps:

Procedure1. Log in as pvuser to the server where the DataChannel is installed.2. Change your working directory to the DataChannel bin directory

(/opt/datachannel/bin by default), as follows:cd /opt/datachannel/bin

3. Enter the following command to start the Bulk Collector:./dccmd -action start -channel N -application BCOL -collector N

For more information about using the dccmd command, see the IBM TivoliNetcool Performance Manager: Command Line Interface Guide.

4. Copy the bulk files to a valid poll directory path. For example:$DCHOME/bcolN/do

where N equals the collector number you specified during Bulk Collectorinstallation, and $DC_HOME is equal to the path where you installed DataChannel.Resource files related to a Bulk Collector profile are stored into the same profiledirectory on the DataMart machine. The name of the directory is the name ofthe profile, for example, bulk_65.Discovered resources are assigned to a profile of bulk_N and FTP to asubdirectory of the same name. The pollinv command automatically creates aprofile with the same name.


Bulk collector inventory file setsFor each inventory session, a Bulk collector creates one or multiple resource filesets. Each file set contains a file containing the following files:

Note: The files belonging to the same file set have a file name with a common<suffix> string.v element.<suffix>.dat - file containing the elements resources.v subelement.<suffix>.dat - file containing the subelements resources.v args.<suffix>.dat - file containing the special inventory arguments. This file

contains a single line (no comments allowed). The content of the line is theoptions string to append in the inventory command.

Where <suffix> equals a timestamp identifier with the format:<YYYYMMDD_H24mmSS>.[FileType]

where:v YYYYMMDD is the year, month, and dayv H24mmSS is the time (hour, minutes, and seconds)v [FileType] is either: full or delta

Inside the bulk_N directory, a bulk collector creates two subdirectories called Doand Done. During transfer staging, a bulk collector first copies the files into the dodirectory. When the transfer is complete, the files are then moved from the Dodirectory into the Done directory.

The following diagram illustrates the directory structure and data flow:


pollinv and pollprofile commandsThe inventory polling process uses the pollinv command, which is configured inthe machine cron and runs once an hour on the DataMart machine. The pollinvcommand browses the importExportBulk directory for profiles, and launches thepollprofile command, one per profile. The inventory command then inserts theresources (metadata) from the file set into the Tivoli Netcool Performance Managerdatabase.

Each time the pollprofile command is run, it does the following:v Creates the corresponding inventory profile.v Browses all the file sets in the profile directoryv Reduces the number of inventory processes to launch by reducing the number of

file sets (one inventory command is launched for each file set). To reduce thenumber of file sets, all file sets that have the same arguments string are mergedtogether. This makes the pollprofile run faster. The files that do not havespecial arguments files are assumed to have default arguments and are mergedtogether.

Log files for the pollinv command are located in $PVMHOME/log/logFile.POLLINVENTORY.

Inventory polling and the cron tableThe Tivoli Netcool Performance Manager DataMart setup program inserts thefollowing line into the DataMart user (for example, pvuser) crontab during setup.0 * * * * [ -f /opt/datamart/dataMart.env ] && [ -x/opt/datamart/bin/pollinv ] && . /opt/datamart/dataMart.env&& pollinv -noX

where /opt/datamart is the path where Tivoli Netcool Performance ManagerDataMart is installed.

< 0 * * * * > is where you can change the frequency.

At every period configured, the system cron launches the pollinv command toimplement the inventory polling. The default period string is "0 * * * * " (thisspecifies that pollinv is launched every hour).

You can change the pollinv period in the cron table:1. Ensure that you are logged in a pvuser as pollinv is configured in pvuser cron

table.2. Get the current content of the pvuser cron table (except the pollinv line) and

save it into a temporary file (for example, tempCronFile):su pvuser -c crontab -l | grep pollinv > tempCronFile

3. Edit the file tempCronFile and insert a new line containing the modifiedpollinv cron command with the suitable period.

4. Replace the current cron table of pvuser by the content of the file$tempCronFile:su pvuser -c " crontab tempCronFile "


Directories and files (location, naming, and format)The DataMart bulk resources directory has the following structure:

v $PVM_BULK_HOME - (for example, this inventory FTP directory is/opt/datamart/importExportBulk) root directory for the bulk collector file sets,which is created when you install Tivoli Netcool Performance ManagerDataMart. It is the location where the Bulk Collector pushes its profiledirectories (and file sets inside the profile directories). This is also the sourceprofile directory for the pollinv command. It defaults to $PVM_HOME/importExportBulk.

v bulk_N - all files related to a profile are stored in this directory (where N = thebulk collector number (ID) that you specified during Bulk Collector installation).All subelements created into the database using the current inventory profile areassigned to this collector.

v Do - temporary directory used by the Bulk Collector when transferring files toTivoli Netcool Performance Manager DataMart. When the transfer is complete,the Bulk Collector moves the files from this directory to the done directory. Thisdirectory is created by the Bulk Collector.

v Done - source file sets directory for the inventory polling process (pollprofilecommand). Each resources file set is composed of two types of files (elementand subelement). An optional file containing the inventory command arguments(args) can be appended to the file set. After each successful inventory commandis run by the pollprofile command, the associated file set is deleted from thisdirectory. This directory and its file sets are created by the Bulk Collector.

v Dm - source file set directory for the inventory process (launched by thepollprofile command). Each inventory launched using this profile get its sourcefiles from this directory, and uses this directory as its working space. This is thecase whether the inventory is launched automatically (pollprofile) or manually(by using the Inventory Tool or CLI). After each inventory (manual orautomatic), the last file set used is not deleted. Since this directory workingdirectory for the inventory command, it creates its working files and workingdirectories at <profilename>/grouping, <profilename>/ groupingWait,<profilename>/inventory, <profilename>/synchro, profilename>/synchroWait.These directories are created by the pollinv command.


Bulk file format examplesSome bulk file format examples:

Element resourcesThe following is an example of an element.<suffix>.dat file:# col = eprp.ipAddressMin:value eprp.ipName:valueeprp.sysName:value name date state encl.oid eprp.ipAddress:valuescf.rcommunity eprp.sysDescr:value collector profile# filter =# type = elt10.5.1.1|_|10.5.1.1|_|10.5.1.1|_|10.5.1.1|_|1004036438|_|on|_|1.3.6.1.4.1.2929|_|<NULL>|_||_|<NULL>|_|2|_|bulk_2|_|

Subelement resourcesThe following is an example of a subelement.<suffix>.dat file:# col = invariant elt.name name date instance label state fam.nameseprp.name:name seprp.value:name#filter =# type = seLPort<66>|_|10.5.1.1|_|10.5.1.1_LPort<66>|_|1004036885|_|LPort<66>|_|<NULL>|_|on|_|Cascade_ATM_LPort|_|ifSpeed|_|1544000|_|portIndex|_|4|_|slotIndex|_

|16|_|portType|_|UNI|_|privateNetID|_|0|_|ifOperStatus|_|1|_|ifIndex|_|66|_|hostIPAddr|_|10.5.1.1|_|msrmtPeriod|_|900|_|customerID|_|0|_|

Inventory argumentsThe following is an example of an args.<suffix>.dat. This file contains a singleline (no comments allowed). The content of the line is the options string to appendin the inventory command.

Example:-reload 1 -action synchro

This means that the inventory reloads the collectors and perform only thesynchronization (no discovery or grouping).


Chapter 4. Creating grouping rules

Explains how to create custom grouping rules to group and edit resources on yournetwork to use with your network inventory, data collection, and reporting.

Note: You can also import resources from the command line. For moreinformation, see the IBM Tivoli Netcool Performance Manager: Command Line InterfaceGuide.

Note: For instructions on creating grouping rules for composite subelements(CSEs), see the IBM Tivoli Netcool Performance Manager: Composite SubelementConfiguration Guide.

Before you beginBefore creating and testing grouping rules, you need to configure a networkinventory to add elements and subelements to the database, as detailed inChapter 3, “Configuring inventory,” on page 13.

Grouping acts like a taxonomy. The intent of grouping is to identify objects thathave a common set of attribute and property values, and to organize the objects ina common place (by creating a group membership relation) expressing thecircumstance of satisfying the criteria for selection.

Grouping rules are organized hierarchically. Each level in the hierarchy is intendedto represent an incremental refinement in categorization. The first rule in agrouping branch, which we call a root, typically selects a broad range of objects,for example: all active objects (that is, state = on). The next level of refinement in abranch intended to organize technologically would perhaps have rules todiscriminate by type of device. For example, router or switch. And the next levelmight further classify in terms of device capacity, or capability.

A grouping rule is evaluated by the conjunction of all rule conditions definedalong a branch in the grouping hierarchy. Group membership is granted at the leaflevel, the most precise taxonomic location, when the complete condition of agrouping rule (the aggregate of all conditions from root to leaf) is met.

Creating grouping rulesThe "ruleconf" command-line interface (CLI) command launches the Rule Editorfrom the command line.

About this task

For more information, see the IBM Tivoli Netcool Performance Manager: CommandLine Interface Guide.

To create rules, follow these steps:

Procedure1. Click Rule Editor in the Resource tab. The Rule Editor window is displayed.2. Click the Rule Sub-Element tab to create a rule for a subelement.


Note: For instructions on creating grouping rules for composite subelements(CSEs), see the IBM Tivoli Netcool Performance Manager: Composite SubelementConfiguration Guide.

3. Expand the tree in the left pane and click the name of a rule to select it. Thisrule must be at the level of the tree just above where you want to insert thenew rule.

4. Right-click and select New. Tivoli Netcool Performance Manager DataMartinserts a new rule with a temporary name. For example, "NEW_GROUP_1."

5. Name the rule by entering up to 50 characters in the Name box. The namecan be either static text or a variable. You can drag the properties from theProperties listbox to the Name box.

Note: Conditions are not allowed in the Name box. See “Using syntax forgrouping rules” on page 58 for more information.

6. Optional: In the Label text box, assign a label to the group. Labels are used asan alias for group names, providing another level of abstraction. Whencreating reports, Tivoli Netcool Performance Manager DataView first looks fora label, and if one is not defined it displays the group name.

7. If the rule requires a condition, enter the condition in the Condition box. See“Using conditions” on page 52 for more information about conditions.You can drag properties from the Properties list and operators from theOperator listbox to the Condition box.See “Using operators and functions” for details on operators and functionavailable in the Operator listbox.

8. Click an option in the Status group:v Idle - the rule remains in the database, but it is not used by the Inventory

Tool during autogrouping. The rule appears in “red” within the tree. Thisrule (and each rule below it within the tree) is ignored by the InventoryTool during autogrouping.

v Active - the rule is used by the Inventory Tool during grouping. See“Specifying automatic grouping” on page 26 for more information.

9. Click Apply. The temporary name changes to the name of one or more of theproperties you selected. Values for Type, Updated On, and Origin are filledautomatically by Tivoli Netcool Performance Manager DataMart.

10. See “Testing grouping rules” on page 53 to test your grouping rules.

Using operators and functions

Operator or Function Description

ANDJoins two conditions. Resources are includedin the results if they match both conditions.This operator has the same effect as creatingnested conditions.

For example:

%(Element.PROFIL) = `public’ AND%(ifType) = `ethernetCsmacd’

Resources are included in the results if theprofile name is public and the ifType isethernetCsmacd.


ORJoins two conditions. Resources are includedin the results if they match either condition.

For example:

%(Element.PROFIL) = `public’ OR%(ifType) = `ethernetCsmacd’

Resources are included in the results ifeither the profile name is "public" or theifType is ethernetCsmacd.

=Tests if the variable is equal to a value. Usethis operator to test against only one value.

For example:

%(VENDOR) = `Cisco’

Resources with the vendor "Cisco" areincluded in the results.

Use IN to test against a list of values. UseLIKE to test against a value with a wildcard(%).

!=Tests if the variable is not equal to a value.Use this operator to test against only onevalue.

For example:

%(VENDOR) != `Cisco’

Resources with any vendor except "Cisco"are included in the results.

Use NOT IN to test against a list of values.Use NOT LIKE to test against a value with awildcard (%).

<Tests if the variable is less than the value.Use this operator to test against only onevalue. It does a comparison based on anASCII sort, if the value is enclosed in doublequotation marks. It does a comparison basedon a numeric sort, if the value is notenclosed in double quotation marks. Forexample:

%(Element.COLLECTOR) < 3

Resources with a collector number less than"3" are included in the results.Note: Do not use double quotation marksfor the collector number. The collectornumber is an Int column in the database andmust use a numeric comparison.

It is also possible to use <=.

Chapter 4. Creating grouping rules 49

>Tests if the variable is greater than the value.Use this operator to test against only onevalue. It does a comparison based on anASCII sort, if the value is enclosed in doublequotation marks. It does a comparison basedon a numeric sort, if the value is notenclosed in double quotation marks. Forexample:

%(Element.COLLECTOR) > 3

Resources with a collector number greaterthan "3" are included in the results.Note: Do not use double quotation marksfor the collector number. The collectornumber is an Int column in the database andmust use a numeric comparison.

It is also possible to use >=.

IS NULLTests if the variable is NULL. For example:

%(FAMILY) IS NULL

Resources with the FAMILY property"NULL" are included in the results.

IS NOT NULLTests if the variable is not NULL. Forexample:

%(FAMILY) IS NOT NULL

Resources with the FAMILY property "notNULL" are included in the results.

LIKETests if the variable is equal to a valuecontaining a wildcard (%). For example:

%(ipAddress) LIKE `182.168.%’

Resources with IP address that begin with182.168 are included in the result.

Use IN to test against a list of values.

NOT LIKETests if the variable is equal to a valuecontaining a wildcard (%). For example:

%(ipAddress) NOT LIKE `182.168.%’

Resources with IP address that begin withanything other than 182.168 are included inthe result.

Use NOT IN to test against a list of values.


INTests if the variable is equal to the value.Use this operator to test against one value,or a list of values. For example:

%(ifType) IN (`ppp’,’slip’)

Resources with ifType PPP or SLIP areincluded in the result.

Use LIKE to test against a value with awildcard (%).

NOT INTests if the variable is not equal to the value.Use this operator to test against one value,or a list of values. For example:

%(ifType) NOT IN (`ppp’,’slip’)

Resources with any ifType other than PPP orSLIP are included in the result.

Use NOT LIKE to test against a value with awildcard (%).

pub.PVM_TO_NUMBERCasts a string to a number. Use this functionwith operators such as < and > to perform anumeric comparison rather than a stringcomparison. Place the function before thevariable.

For example:

pub.PVM_TO_NUMBER(%(ifSpeed)) >= 100000000

pub.FormatIPReformats an IP address so that each set ofnumbers in the address contains three digits.This is necessary to do an accuratecomparison. It converts this IP address:

194.68.211.8

to this IP address:

194.068.211.008

For example, this is not correct:

%(ipAddress) < `182.168.78.5’AND %(ipAddress) >`182.168.78.3’

It is not correct, because this rule includesboth the IP addresses 182.168.78.4 and182.168.78.48.

This is correct:

pub.FormatIP(%(ipAddress))< `182.168.078.005’ AND

pub.FormatIP((%(ipAddress))> `182.168.078.003’

This rule includes the IP address182.168.78.4, but not 182.168.78.48.


Using conditionsYou can use any property in the database as a variable in a condition. A conditioncan test against any value that is valid for the property.

To test against multiple values use the OR, IN, and LIKE operators. See “Usingoperators and functions” on page 48 for more information.

The syntax for conditions is similar to SQL syntax. A condition has the followingformat:%(property) operator`value’

Part of Condition Description Syntax Requirements

% Creates a variable from aproperty.

No space between % and theproperty.

property Specifies the property to betested.

Parenthesis are required.

operator Defines the relationshipbetween the variable and thevalue. See “Using operatorsand functions” on page 48for more information.

Spaces before and after theoperator are recommended,but not always required.

value Specifies the test. v Single Quotation marksare required around eachvalue for a stringcomparison.

v Double quotation marksaround the values are notallowed for a numericcomparison.

Note: Do not use doublequotation marks for thecollector number. Thecollector number is an Intcolumn in the database andmust use a numericcomparison.

v If the condition testsagainst a list of values,parentheses are requiredaround the list.

v If the condition testsagainst a list of values,each value needs to beseparated by a comma.Spaces before and after thecomma are optional.

v The value in the conditionneeds to match the valuein the database.Capitalization andpunctuation must be thesame.

You can nest conditions. For example:


A resource must match all of the conditions to be included in the results. See“Example of nested conditions” on page 62 for details. Only the result of thelowest level of the tree is used by the Inventory Tool to create groups.

Using grouping rulesExplains how to use custom grouping rules after you create them.

About this task

To use grouping rules, follow these steps:

Procedure1. Ensure that you have performed an inventory of your network or imported

resources from the command line.See Managing Resources in the IBM Tivoli Netcool Performance Manager: CommandLine Interface Guide for information about importing resources.

2. If you want to use properties that are not included with Tivoli NetcoolPerformance Manager DataMart, create properties and add them to thedatabase. See Managing Resources in the IBM Tivoli Netcool Performance Manager:Command Line Interface Guide for more information about adding properties tothe database.

Note: After you create properties, you must exit the Rule Editor and reopen itfor the new properties to appear.

3. Create grouping rules. See Chapter 4, “Creating grouping rules,” on page 47 fordetails.

4. Run the Autogrouping option in the Inventory Tool Wizard to execute thegrouping rules. See “Configuring your network inventory” on page 13 forinstructions. Profiles created with the Inventory Tool Wizard use the groupingrules that you create with the Rule Editor.

5. Use the groups to create collection requests. See “Configuring data collectionrequests” on page 65 for information about using the Request Editor to createrequests.

Testing grouping rulesAfter you create custom grouping rules, you can test them using databaseinformation.

About this task

To obtain database information configure an inventory to add elements andsubelements to the database, as detailed in “Configuring your network inventory”on page 13. You can also import resources. See Managing Resources in the IBM TivoliNetcool Performance Manager: Command Line Interface Guide for details.

When you test a grouping rule, the results are displayed in a tree structure in theTest Result tab.


Grouping rules can contain the following:v Static text - provides another level to the tree, but does not sort or filter the

results. It lets you create meaningful names for your rules.v Variables - used alone, sort the results according to the variable, but do not filter

the results. If you use a variable to sort according to ifSpeeds, all the resourcesare included in the result and are grouped according to the different ifSpeeds ofthe resources.

You can also nest variables. The results of nested variables are sorted according toeach variable. See “Creating variables” on page 58 for details. Only the result ofthe lowest level of the tree is used by the Inventory Tool to create groups.v Conditions - use variables to filter the results. Only resources that match the

condition are included in the result. A condition does not sort the results. All theresources that match the condition are grouped together.If you use a condition to filter according to :ifSpeed, only the resources thatmatch the condition are included in the result. Unlike with variables, all theresources that match the condition are grouped together. They are not sortedaccording to the different ifSpeeds.Conditions can also be nested. A nested condition filters the results again. Onlyresources that match all the conditions are included in the result. Only the resultof the lowest level of the tree is used by the Inventory Tool to create groups.See “Example of combining text, a variable, and a condition” on page 64.

To test a grouping rule, follow these steps:

Procedure1. Open the Rule Editor as explained in Chapter 4, “Creating grouping rules,” on

page 47.2. Expand the tree in the left pane to display the rule that you want to test.3. Select the rule by clicking the name of the rule. To select multiple rules, hold

down the Shift key and click the names of the rules you want to select.

Note: You must expand the tree to display all the rules you want to select. Ifthe branch of the tree is not expanded, only the rule that is visible is selected.The rules below it in the tree are not selected and are not tested.

4. Right-click and select Test from the menu. The Test Result tab is displayed.5. Display every resource included in the group by clicking the plus sign or the

folder icon to expand the tree.OrDisplay only the number of resources included in the group by clicking thename of the group to select it, then holding down the Ctrl key and right-click.If a group is not created, check the syntax of the rule. See “Using syntax forgrouping rules” on page 58 for details.Each property must have a default value. If an element has no value for aproperty, and there is no default value for the property, then the element is notincluded in the results for grouping rules that use that property.


Saving test resultsThis saves the test results in a file. It does not save the results in the database. Tomodify the groups in the database, run Automatic Grouping in the Inventory Tool.

Procedure1. Test the rule as explained in “Testing grouping rules” on page 53.2. Click the Save result in file button.3. Specify a path and file name.4. Click Save.

Copying grouping rulesProcedure1. Open the Rule Editor.2. Expand the tree in the left pane to display the rules that you want to copy.3. Click the name of the rule to select it. To copy several rules, select the highest

rule in the tree.4. Right-click and select Copy from the menu. The rule changes to the color blue.5. Expand the tree in the left pane to display the rule where you want to paste

the rule.6. Click the name of the rule to select it.7. Right-click to open the menu.8. Select Paste on the menu.9. Expand the tree to display the rules you copied.

Moving grouping rulesAbout this task

To move grouping rules, follow these steps:


page 47.2. Expand the tree in the left pane to display the rules that you want to move.3. Click the name of the rule to select it. To move several rules, select the highest

rule in the tree.4. Right-click and select Cut on the menu. The rule changes to the color blue.5. Expand the tree in the left pane to display the rule where you want to paste

the rule.6. Click the name of the rule to select it.7. Right-click to open the menu.8. Select Paste from the menu.9. Expand the tree to display the rules you moved.


Deleting Grouping RulesProcedure1. Open the Rule Editoras explained in Chapter 4, “Creating grouping rules,” on

page 47.2. Expand the tree in the left pane to display the rule that you want to delete.3. Click the name of the rule to select it.4. Right-click.5. Select Delete from the menu.6. Click Yes. The selected rule is deleted along with each rule below it in the tree.

Understanding the file formatAbout this task

A file with the test results contains fields for the following:v Path and name for the rulev Identifier for the resourcev Database index for the rule

Each line of the file represents one resource. The fields are separated by |_|.For example:

Viewing rule database informationProcedure1. Open the Rule Editor as explained in Chapter 4, “Creating grouping rules,” on

page 47.2. Expand the tree in the left pane to display the rule you want.3. Click the name of the rule to select it.4. Hold down the Ctrl key and right-click. A pop-up window containing the

database information appears.

The parameters in the pop-up window are as follows:

Parameter Description

Heading Path and name for the rule. The pathseparator is a tilde (~).

dbIndex Database index for the rule.


Name Name of the rule.

type Type of rule (static or rule).

cond Condition for the rule. This is blank if therule does not have a condition.

stateIndicates whether the rule is used by theInventory Tool during grouping.

v on - indicates that the rule is used. Thiscorresponds to the Status: active in thegraphical user interface.

v off - indicates that the rule is not be used.This corresponds to the Status: idle in thegraphical user interface.

date Modification date as the number of secondssince 1 January 1970.

origin How the rule was created.

Viewing propertiesGrouping rules are based on properties.

About this task

Properties are any attribute of an element or subelement, such as:v MIB attributes, such as sysDesc or ifSpeed. These attributes must first be

included in the discovery formulas.v Attributes from Tivoli Netcool Performance Manager DataMart, such as the

collector number or the name of the profile.v Attributes created by your company, such as customer name, or location.

In grouping rules, these properties become variables. For example, the propertyifSpeed becomes the variable %(ifSpeed).You can use any property in the databaseas a variable.

To view properties, follow these steps:


page 47.2. Click the Rule Element tab if you want to view a description of a property for

an element.OrClick the Rule Sub-Element tab if you want to view a description of a propertyfor a subelement.

3. Click the Description tab.4. Click the name of the property to select it.5. Hold down the Ctrl key and click the right mouse button. A pop-up window

containing a description of the property appears.You can create additional properties. They must be in the database before youcan use them in a grouping rule. See Managing Tivoli Netcool Performance


Manager Objects in the IBM Tivoli Netcool Performance Manager: Command LineInterface Guide for details on adding properties to the database.

Using syntax for grouping rulesExplains the syntax to use when creating rules.

See pages “Grouping rule example” on page 59, “Example of nested conditions”on page 62, and “Example of combining text, a variable, and a condition” on page64 for examples.

Using static textDo not use the percent sign (%) in static text. It is reserved for creating variables.

You can use operators, which are treated as text.

Creating variablesYou can create variables by using the percent sign (%) with the name of a property.For example: %(COLLECTOR)

About this task

You can create variables by dragging a property from the Properties listbox anddropping it in the Name box or the Condition box.

Note: Parenthesis around the name of the property are recommended, but notrequired.

You can use variables without conditions in the Name box, but not in theCondition box.

You can nest variables. The results of nested variables are sorted according to eachvariable. See Chapter 4, “Creating grouping rules,” on page 47 for details. Only theresult of the lowest level of the tree is used by the Inventory Tool to create groups.See “Specifying automatic grouping” on page 26 for more information.

Using a text editor to create grouping rulesYou can use a text editor to create grouping rules. Using a text editor lets youcreate grouping rules quickly because you can export the existing rules from theRule Editor, edit the file, then import the grouping rules back into the Rule Editor.The format for this file is explained in “Understanding the file format” on page 59.

Exporting grouping rulesProcedure1. Open the Rule Editor as explained in Chapter 4, “Creating grouping rules,” on

page 47.2. Select Export from the File menu. The Export dialog box appears.3. Specify a path and file name for the export file.4. Click Save to save the file.


Importing grouping rulesProcedure1. Open the Rule Editor as explained in Chapter 4, “Creating grouping rules,” on

page 47.2. Select Import from the File menu. The Import dialog box appears.3. Select the file that you want to import.4. Click Open to import the file.

Understanding the file formatThe file format for a grouping rule file is the same for an import file and an exportfile. You can export the rules from the Rule Editor, edit the file in a text editor, thenimport the rules back into the Rule Editor.

About this task

A file of the grouping rules contains parameters for:v Path and name for the rule - the path separator is a tilde (~). A tilde must be

the first character for each line.v Condition - the condition in this file has the same syntax as the condition in the

graphical user interface. If there is no condition, this is blank (|_||_|).v Type - either static or rule.v Status - on (meaning it is used by the Inventory Tool during autogrouping) or

off (meaning it is not used by the Inventory Tool during autogrouping). See“Specifying automatic grouping” on page 26 for more information.

Each line of the file represents one rule. The fields are separated by |_|. Forexample:

Grouping rule exampleThis example illustrates grouping rules containing:v Name with static textv Name with a variablev Nested variablev Condition


Name with static textTo create this name with static text, the entry in the Name box is: "An Example".There is no entry in the Condition box.

The test results for static text are based on the previous level of the tree. Theresults for this example are the ROOT.

Name with a variableTo create this name with a variable, the entry in the Name box is:"%(Element.COLLECTOR)". There is no entry in the Condition box.

The test results are sorted according to the collector, but are not filtered.


Nested variableTo create this variable the entry in the Name box is:%(ifType)

T

here is no entry in the Condition box.

The test results are sorted according to a collector, and are then filtered accordingto interface speed. Those results are then sorted according to interface type.

Only the result of this lowest level of the tree is used by the Inventory Tool tocreate groups. See “Specifying automatic grouping” on page 26 for moreinformation.

ConditionTo create this condition the entry in the Name box is:High Speed > 100Mbps

The entry in the Condition box is:pub.PVM_TO_NUMBER(%(ifSpeed)) >= 100000000

Because operators are not processed in the Name box, the greater than operator (>)in the name is text. Because operators are processed in the Condition box, thegreater than or equal to operator (>=) in the condition filters the results.

The function pub.PVM_TO_NUMBER casts the string to a number to perform a numericcomparison rather than an ASCII comparison.

The test results are sorted according to a collector and are then filtered accordingto interface speed. Resources are only included in the test results if the interfacespeed is more than 100 Mbps. Resources with a slower interface speed are ignored.


Example of nested conditionsThis example illustrates nested conditions.

ConditionTo create this condition the entry in the Name box is:Active state

The entry in the Condition box is:%(State) = `active’

The test results are filtered according to the state of the subelement. Subelementsare only included in the test results if they are active. Inactive subelements areignored.

Nested conditionTo create a nested condition, the entry in the Name box is:Speed

The entry in the Condition box is:pub.PVM_TO_NUMBER(%(ifSpeed)) <= 100000000

The function pub.PVM_TO_NUMBER casts the string to a number to perform a numericcomparison rather than an ASCII comparison.


The test results are filtered according to the state, and are then filtered according tointerface speed. Resources are only included in the test results if they are active,and the interface speed is less than 100 Mbps.

Inactive resources are ignored. Resources with faster interface speeds are ignored.

Second nested conditionTo create this condition, the entry in the Name box is:Type

The entry in the Condition box is:%(ifType) IN (`ppp’,’frame-relay’)

The test results are filtered according to the state, then filtered according tointerface speed, and then filtered according to interface type. Resources are onlyincluded in the test results if they are active, and the interface speed is less than100 Mbps, and the interface is either PPP or Frame Relay. Inactive resources areignored. Resources with faster interface speeds are ignored. Resources with othertypes of interfaces are ignored.

The results include resources that are either PPP or Frame Relay. The results do notspecify the interface for each resource.

VariableTo create this variable, the entry in the Name box is:%(ifType)

There is no entry in the Condition box.

The test results are filtered according to the state, then filtered according tointerface speed, then filtered according to interface type, and finally sortedaccording to interface type.

The list of resources is the same as before, but are sorted according to interfacetype.


Only the result of this lowest level of the tree is used by the Inventory Tool tocreate groups. See “Specifying automatic grouping” on page 26 for moreinformation.

Example of combining text, a variable, and a conditionThis example illustrates using text, a name with a variable, and a condition.

To create this rule, the entry in the Name box is:Ethernet for Collector no.: %(Element.COLLECTOR)

The entry in the Condition box is:%(ifType) = `ethernet-csmacd’

The test results are sorted according to the collector, then filtered according tointerface type. The text is included in the display of the results.


Chapter 5. Collection and aggregation

Explains how to collect and store network performance and service analysis datafor monitoring subelements on your network using SNMP, Bulk, and ComplexMetric formulas. It also explains how to configure aggregation requests andpercentile information for presentation in reports.

After collection, and possibly aggregation, this data can be integrated into TivoliNetcool Performance Manager DataView or the reporting tool of your choice.

Before you beginBefore you request data collection, you need to:v Configure an inventory of elements and subelements in your network, as

detailed in Chapter 3, “Configuring inventory,” on page 13.v Group the elements and subelements automatically or manually, as detailed in

Chapter 4, “Creating grouping rules,” on page 47.

Configuring data collection requestsExplains how to configure data collection requests for the subelements in yournetwork. Results of the data collection are stored in the Tivoli Netcool PerformanceManager database for use in reporting.

About this task

In addition to the Request Editor, you use the following Tivoli NetcoolPerformance Manager DataLoad modules to configure data collection:v Formula Selector to select a formula for collecting data.v Resource Editor to select resources, such as subelements and subelement groups.

Procedure1. Click Request Editor in the Configuration tab.2. Click the + sign next to Sub-Element Collect in the Sub-Element Groups pane

to expand it and display the collection groups. These groups do not havetimezones attached to them.

3. Go to the collection group you want by expanding the top-level folders tolocate the group.

4. Click the + sign next to AP in the Formulas pane to expand it and display theformula groups.

5. Go to the formulas you want to apply to the data collection,6. Click New. The newly created requests appear in the list.7. You can click Cancel to undo the requests created or click Save to save your

requests. If you want to create additional requests, repeat steps 3 through 7before clicking Save.


Setting the collection periodYou can set the time you want data collection to run in the Details area of theCollection tab.

Procedure1. Select an existing request or create a new one. The selected request is

highlighted in blue.2. Enter a value in the Hours text box and press Enter or use the up and down

arrows to increase or decrease the value.3. Enter a value in the Minutes text box and press Enter or use the up and down

arrows to increase or decrease the value.4. Click Cancel to undo the changes you made to the data collection period or

click Save to save your edits. If you want to create additional requests, repeatsteps 1 through 3 before clicking Save.

Configuring aggregation requestsExplains how to configure aggregation requests and percentile values.

Procedure1. From the Request Editor, click the Aggregation tab.2. Click the + sign next to NOC Reporting to expand it and display a list of

report groups for aggregation. These groups have Calendars and timezonesassociated with them.

3. Go to the report group you want by expanding the top-level folders to locatethe group.

4. Click the + sign next to AP in the Formulas pane to expand it and display theformula groups.

5. Go to the formulas you want to apply to the data collection. Aggregation isusually against generic formulas.

6. Select the formulas pressing Ctrl or Shift while clicking to selectnon-contiguous or a continuous block or formulas.

7. Click New. The newly created requests appear in the list.8. Click Cancel to undo the requests created or click Save to save your requests. If

you want to create additional requests, repeat steps 3 through 7 before clickingSave.

Configuring a percentile valueYou can use a percentile value instead of the average or max statistics to betterrepresent a metric that includes the occasional burst or spike. Occasional bursts orspikes render a min or max value meaningless, and throw off average and meancalculations. In these cases, using a percentile calculation allows you to see moreaccurately how the metric is performing over time. Percentile values are applied toraw data.

Procedure1. Select the requests to which you want to apply the percentile.2. Enter the percentile value in the Percentile text box and press Enter or use the

up and down arrows to increase and decrease the value.The percentile value you enter appears in the Percentile column in the requesttable.


3. Click Cancel to undo the requests created or click Save to save your requests. Ifyou want to create additional requests, repeat steps 3 through 7 before clickingSave.

Filtering requestsExplains how to filter the requests displayed in both the Collection andAggregation tabs. The Request Editor displays a filtering toolbar that's the same onboth tabs.

The filter expressions are applied to the requests displayed in the table. Thecolumn heads effected by the expressions change to reflect the filter applied.

Sorting columnsYou can click column headings to sort the contents. A single click to a column headchanges the order which the line items in the request table are displayed. A secondclick reverses the order.

Validating the requestsExplains how to validate all the Collection and Aggregation requests. Click Saveafter creating or modifying a request to make the system validate all requests, eventhose populated by other tools.

Chapter 5. Collection and aggregation 67

Chapter 6. Configuring calendars

Explains how to configure calendars by using the Calendar Configuration Tool.You use this tool exclusively for SNMP collector data requests to restrict the SNMPcollection time period.

IBM recommends that you collect data on a 24 x 7 basis, which is the defaultcollection period in the Request Editor. For more information, see “Configuringdata collection requests” on page 65.

You use a calendar to define periods for SNMP data collection. For example, youcan stop SNMP data collection times for a customer site that is closed for businessand the network is not being used (no data collection before 8:00 a.m. or after 8p.m.). This is known as planned outage for Service Level Agreement purposes. TheService Provider has no obligation to the customer during a planned outage.

Using the Calendar Configuration ToolAbout this task

The Calendar Configuration Tool provides calendars to use with Tivoli NetcoolPerformance Manager DataMart data collection requests.

Note: The calsel command-line interface (CLI) command launches the CalendarSelector from the command line. The calconf CLI command launches theCalendar Selector from the command line. For more information, see the IBM TivoliNetcool Performance Manager: Command Line Interface Guide.

To start the Calendar Configuration Tool, follow these steps:

Procedure1. Click Calendar Configuration in the Configuration tab. The Calendar

Configuration Tool dialog box appears2. TheCalendar Configuration Tool lets you create your own calendar from

scratch. For more information, see “Creating customized calendars.”

Creating customized calendarsExplains how to create customized calendars for scheduling data collection.

About this task

When creating a custom calendar for an SNMP data collection request, be awarethat if you apply to a CME formula data collection request using ResourceManager, it has the opposite affect.

For example, if you create a calendar for a planned outage that collects data from 8a.m. to 8 p.m. on Tuesday, if applied to the CME, it doesl not collect data from 8a.m. to 8 p.m. on Tuesday. The CME expresses outages in this way.


IBM recommends that you use the CME Permanent calendar for all Bulk file/CMEformula data requests. The CME Permanent calendar is a 24 x 7 calendar thatcollects data every hour on a daily basis from 0:00 to 23:59 (12:00 a.m. to 11:59p.m.)

To create a custom calendar, follow these steps:

Procedure1. Select Add item from the Action menu.2. Select one of the following options from the menu:

v Once item - to configure a one-time schedule.v Daily item - to configure daily schedules.v Weekly item - to configure weekly schedules.v Monthly item - to configure monthly schedules.These options are explained in the next sections.Tivoli Netcool Performance Manager DataMart supports Greenwich Mean Time(GMT). When creating a calendar using GMT timezones, use this table as aguide.

Value Location

-12 Eniwetok, Kwajalein

-11 Midway Island, Samao

-10 Hawaii

-9 Alaska

-8 Pacific Time (U.S. and Canada); Tijuana

-7 Mountain Time (U.S. and Canada)

-6 Central Time (U.S. and Canada)

-5 Eastern Time (U.S. and Canada)

-4 Atlantic Time (U.S. and Canada)

-3 Buenos Aires, Georgetown, Brasilia

-2 Mid-Atlantic

-1 Azores, Cape Verde

+1 Amsterdam, Copenhagen, Madrid, Paris,Belgrade, Brussels, Berlin, Rome, Stockholm,Vienna, and so on.

+2 Athens, Istanbul, Cairo, Israel, and so on.

+3 Baghdad, Kuwait, Moscow, St. Petersburg,Nairobi, Tehran, and so on.

+4 Abu Dhabi, Muscat, Baku, and Tbilisi

+5 Ekaterinburg, Islamabad, Karachi, Tashkent

+6 Almaty, Dhaka, Colombo

+7 Bangkok, Hanoi, Jakarta

+8 Beijing, Chongging, Hong Kong, Urumqi,Perth, Singapore, Taipei

+9 Osaka, Sapporo, Tokyo, Seoul, Yakutsk

+10 Brisbane, Canberra, Melbourne, Sydney,Guam, Port Moresby, Hobart, Vladivostok


+11 Magadan, Solomon Island, New Caledonia

+12 Auckland, Wellington, Fiji, Kamchatka,Marshall Island

Creating a one-time calendarExplains how to configure a calendar to run once within your local time zone. Forexample, you might want to schedule a planned outage to occur once only.

About this task

To configure a one-time calendar within your time zone, follow these steps:

Procedure1. Select Once item. The Add Once Item dialog box appears.2. From the Date selector group, specify times for data collection in the From and

To options in the Date selector group.Hours are in military time. For example, 06:00 to 17:00 schedules data collectionfrom 6 a.m. to 5 p.m.

3. Click a date list to specify dates for the collection (day-month-year format). Acalendar pop-up window appears.

4. Double-click a specific day.

Note: The time and date are based on the date and time properties of yourcomputer.

5. Click OK to accept your selections and close the Add Once Item dialog box.6. Select Save from the File menu to save your calendar configuration.7. Enter a unique name for your calendar in the Name box. You can also override

the name of a pre-set calendar if you modified that calendar type.

Creating a daily calendarYou can schedule daily data collection.

Procedure1. Select Add item from the Action menu.2. Select Daily item. The Add Daily Item dialog box appears.3. Select one of the following options from the Daily item group:

v All days - lets you schedule data collection for each day of the week.v Working days (Monday - Friday) - lets you schedule data collection from

Monday through Friday. Excludes weekends.v Weekend days (Saturday - Sunday) - lets you schedule data collection for

Saturday and Sunday. Excludes week days.4. Click 24h a day to clear if you want to specify times in the From and To spin

boxes. Hours are in military time. For example, 06:00 to 17:00 schedules datacollection from 6 a.m. to 5 p.m.

5. Click OK to accept your selections.

Chapter 6. Configuring calendars 71

Creating a weekly calendarExplains how to create a weekly calendar to use for SNMP and bulk file datacollection. A calendar for a data request that uses a bulk file works inversely froma calendar for an SNMP data request.

About this task

To schedule weekly data collection, follow these steps:

Procedure1. Select Add item from the Action menu.2. Select Weekly item, the Add Weekly Item dialog box appears.

The default setting collects data every day of the week from 00:00 to 23:59(12:00 a.m. to 11:59 p.m.)

3. From the Days selector group, select which days you want to collect data (on aweekly basis). For example, you can select Monday, Tuesday, and Thursday,and exclude Wednesday and Friday.

4. Specify a time range in the lists by clicking the 24h a day button. Clicking thisbutton disables the default setting, which is to collect data every hour (12:00a.m. to 11:59 a.m.) For example, you can choose to collect data from 8:00 a.m. to8 p.m. (08:00 to 20:00).Orv Select the starting day from the Range day selector to select a range of days.

For example, Monday to Friday.v Specify a time range in the lists. For example, from 8:00 a.m. to 8 p.m. (08:00

to 20:00).5. Click OK to accept your selections.

If you apply this calendar to an SNMP data collection request, it collects dataevery hour on Monday, Wednesday, and Friday (includes - ON).If you apply it to a bulk file/CME formula data collection request, it collectsdata on Tuesday, Thursday, Saturday, and Sunday. It does NOT collect data onMonday, Wednesday, and Friday (excludes - OFF).

Creating a monthly calendarYou can schedule monthly data collection.

About this task

To schedule monthly data collection, follow these steps:

Procedure1. Select Add item from the Action menu.2. Select Monthly item. The Add Monthly Item dialog box appears.3. From the Day range selector group, select the time and day of the month in

which you want to start data collection, and the time and day of the month inwhich you want to end data collection. For example, from the first day of themonth at 8:00 a.m. to the 15th day of the month at 8 p.m.Or

4. From the Week range selector, select the time in the From list.5. Select the first, 2nd, 3rd, 4th or last week from the next list.6. Select a day from the next list.



Deleting a calendarProcedure1. Ensure the calendar is not being used for any data collection requests.2. Select Load from the File menu to access available calendars.3. Click Delete from the File menu. The calendar is deleted.

Using the Calendar SelectorYou can load a calendar that already exists in the database from the CalendarSelector.

About this task

To select a calendar, follow these steps:

Procedure1. Click Calendar Selector > File > Selector The Calendar Selector window

appears.2. Select one or more calendars to use in the Request Editor.3. Click Close to exit the Calendar Selector window.

Chapter 6. Configuring calendars 73

Chapter 7. Writing custom formulas

Explains how to create and modify custom formulas.

You use the following Tivoli Netcool Performance Manager DataMart modules tocreate or modify formulas:v Formula Selector to select a formula for editing.v Formula Editor to edit and test formulas.v MIB Browser to display a compiled MIB.v MIB Compiler (optional) to add a new MIB.

Before you beginEnsure the collector is running.

For more information, see Chapter 11, “Viewing collected data,” on page 169.

What is a formula?A formula (sometimes called a metric) is a script, written in a proprietary languagedeveloped by IBM Corporation. A formula is a collection of object identifiers(OIDs,) functions, and standard mathematical operations applied to a subelementto perform a computation. A formula lets you customize the information gatheredby Tivoli Netcool Performance Manager DataMart.

There are two types of formulas:v Discovery formulas are used by the Inventory Tool during the process of

discovering and analyzing the network. Discovery formulas are used againsthosts only (not against subelements) and are designed to return a list of results.Discovery formulas collect information using OIDVAL()functions and store thevalues into Vxx vectors. The last lines in the Discovery formula are the ones thatsend results to the Inventory.Discovery formulas for most interfaces are already included with Tivoli NetcoolPerformance Manager DataMart. You can write a new discovery formula toinclude a device that is new to the market.

v Collection formulas are used by the Request Editor to collect information aboutthe status of various devices in the network. Collection formulas are appliedagainst a subelement to produce a result (string or numeric) that is saved in thedatabase. There are numerous collection formulas included with Tivoli NetcoolPerformance Manager DataMart; however, you can write additional formulas fora customized collection process.


Merging discovery resultsYou can create Discovery formulas that merge results to create a uniquesubelement. Instead of creating one large Discovery formula, you can createmultiple smaller Discovery formulas that can run sequentially with the resultsbeing merged if a common key (formed by the pair of element name andsubelement instance field) is detected.

About this task

The process of creating multiple Discovery formulas that can be used for the mergeprocess includes creating one base formula and multiple expansion formulas to usewith the base.v base formula: the main formula that discovers the subelement along with basic

propertiesv expansion formula: additional formulas that define and populate additional

properties for the subelement

The merge process applies to the following three fields:v SubElement Labelv Propertiesv Invariant

The merge occurs between the version of a subelement produced by a Discoveryformula (the base formula) and already stored in memory and the more currentversion of that subelement returned by a subsequent Discovery formula (expansionformula.).

You add the merge capability to Discovery formulas by including one of thefollowing characters as the initial character in the SubElement Label, Property, andInvariant fields.v * (asterisk) value of current version of the subelement always overwrites

previous valuev + (plus sign) value of the current version of the subelement overwrites previous

value if the previous value was empty or missingv - value of the current version of the subelement overwrites the previous value if

it is missing.

See “Standard rules for writing formulas” on page 80 for information about usingthese characters when creating formulas.

Note: Do not use any of these characters as the initial character when naming aSubElement label, Property, or Invariant.

The character is removed by the Discovery server before the production of the filefor the Inventory process.


Creating formulasYou can create custom formulas to use for discovery and data collection inaddition to the formula library included with Tivoli Netcool Performance ManagerDataMart.

For example, if you want to know the number of IP packets discarded on a hostfrom MIB-II, you would use this formula:ipInDiscards.0 + ipOutDiscards.0

where ipInDiscards.0 is the number of incoming discarded IP packets andiPOutDiscards.0 is the number of outgoing discarded IP packets.

A valid formula needs to have a MIB that is compiled in Tivoli NetcoolPerformance Manager DataMart. Without a valid MIB, the formula returns an errormessage to the request.

Editing the inventory_subelement.txt fileWhen you create a Discovery formula, you need to edit theInventory_sublement.txt file to include the formula so it can be used by theInventory tool. The Inventory_sublement.txt file lists the rules that Discovery usesand you need to create rules for any Discovery formulas you create.

About this task

To create a formula, follow these steps:

Procedure1. Click the Metric > Formula Editor. The Formula Editor window appears.2. Select the following formula type from the Options menu:

v SNMP (Simple Network Management Protocol) - a network managementprotocol that is used to monitor routers and attached networks. SNMP is anapplication layer protocol. Information about devices managed is definedand stored in the application's Management Information Base (MIB).Operates on several OIDs.

3. Click a function button in the calculator. Your choices are as follows:

Function Description

ABS Takes the absolute value of an expression oran object.

MOD Takes the modulus of an expression(remainder from the full division) or of anobject. This function is typically used withthe INT function.

LN Takes the Naperian logarithm of anexpression or an object.

LOG Takes the decimal logarithm of anexpression or an object.

e* Takes the exponential of an expression or anobject.

10* Takes 10 to the power of an expression or anobject.

Chapter 7. Writing custom formulas 77


INT Converts the value of an expression or anobject into an integer value.

LAST Displays the previous measurement value.

∆ (delta) Displays the difference between the lastmeasurement and the previous one (x -last(x)). Results are always positive. Thisfunction is used for data whose valueincreases after reaching a maximum peak.This function is typically used for "counter"type MIB data.

DIFF Displays the difference between the lastmeasurement and the previous one (x - last(x)). Results can be negative. This function istypically run on gauge type objects.

Ô Deletes the last operation.

C Clears the Data of Formula box.

( Open parenthesis.

) Closed parenthesis.

4. Alternatively, you can drag a function from the Functions listbox into the Dataof Formula box to create a formula. Many of these functions are also availableas buttons in the calculator.Or

5. Select a data type from the Type listbox. Your choices are:v float - a numerical value (floating point).v string - a character string.

Enter a comment in the Comment box. The maximum character length is4000.

6. Select File > Save to save your formula in the database.

Testing formulasYou can test a formula after you create it. This step is important to ensure that theformula is valid.

About this task

Note: The Resource field accepts both IPv4 and IPv6 IP address formats.

To test a formula, follow these steps:

Procedure1. Ensure that the default collector is started.2. Click the Test tab.3. Specify an element, subelements, or group of subelements for which to test the

formula from the Target listbox.You must specify an appropriate target to test against. For example, an Ethernetformula requires a target with an ethernet interface. A token ring formularequires a target with a token ring interface.

4. Click the refresh button to update this listbox with available resources.


5. Specify an instance from the Instance box. For example, a single instance suchas 1, or multiple instances such as 1,3,5-4.1.2,7.*,8.1.*,9-10.You can override the default instances specified in the formula by using theInstance field. For example, if the formula specifies all instances:Dim I1 AS Integer Default * NAME Interface

You can use the Instance field to specify only instances 2 through 5:Interface<2-5>

If you do not specify any instances, Tivoli Netcool Performance ManagerDataMart uses the default instances specified in the formula, and inserts theminto the Instance field when testing the formula.

6. Enter a community name in the Community box.7. Optional: You can select an SNMP Collector for the formula test from the

SNMP Collector listbox. When you selected resources in step 3, the associatedcollector appears by default.

8. Click Test to test the validity of the formula. The selected target andcommunity name are also tested.In a few moments, the results are displayed in the Trace box.If the test passed, the formula is correct and the element or subelement isactive. The numerical results of the test are displayed.If the test failed, an error message is displayed. For example, the messagemight tell you that no data was found.

9. Right-click the Trace > Reset to clear the Trace box or select Save to print theresults or save them to a file.

Saving formulasWhen you save a formula, Tivoli Netcool Performance Manager DataMart searchesall the MIBs that have been compiled. It creates a link from the formula to thecompiled MIB containing the MIB objects used in the formula.

If a MIB object occurs in only one compiled MIB, the link is created automatically.However, if the MIB object occurs in more than one compiled MIB, you mustspecify which MIB should be used. Tivoli Netcool Performance Manager DataMartautomatically displays a list of MIBs in the MIB Selection window. Click on thedesired MIB, then click OK.

You can view the details of any of the MIBs by using the MIB Browser. For moreinformation about the MIB Browser, see Chapter 9, “Managing MIBs,” on page 131.

When you save a discovery formula, you must save it under the "Alias Instanceand Label Inventory" branch of the formula tree. Before the formula can be usedautomatically by the Inventory Tool, the path to the formula must be specified intheinventory_subelements.txt file. This file can only recognize a location withinthe "Alias Instance and Label Inventory" branch of the formula tree.


Modifying a custom formulaYou can modify an existing formula by using the Formula Selector.

Procedure1. Select File > Load. The Formula Selector dialog box appears.2. Expand the branches and select the formula you want to modify and click OK.

Or3. Drag a formula into the Data of Formula box. The contents of the formula are

inserted rather than the name of the formula.4. Modify as necessary.5. If prompted when you save the formula, restart the collector.

Standard rules for writing formulasDescribes the standard rules you need to follow when writing formulas.

Every line of a formula must end with a semi-colon(;). Each line of a formula mustbe on one line. Long lines cannot wrap. The lines of a formula are processedsequentially. There are no statements such as loops, switches, or cases.

Dim declarationThe Dim declaration defines the format of an input variable. If the formularequires more than one input variable, there must be a separate Dim declarationfor each input variable.

The syntax is:Dim <Var> As <Type> [Default <val>] [Name <label>];

Part of Formula Purpose Syntax Requirements

Dim A keyword to indicate thatan input variable is beingdeclared.

Not case-sensitive.

Var The input variable.Must be of the form "I1", "I"must be capitalized, andmust be followed by anumber.

As A keyword to indicate thatthe data type of the inputvariable is being declared.

Not case-sensitive.

Type The data type of the inputvariable. Not case-sensitive. The valid

types are listed in “Instancevariables” on page 86.

Default A keyword to indicate thatdefault instances are beingdeclared.

Optional, not case-sensitive.If both the Default andName parameters are used,the Default parameter mustcome before the Nameparameter.



val The instances to use if noother instances are specified. Default instances can be a

list of values

- or -

* to indicate that all instancesmust be used.

See “Instance variables” onpage 86 for more informationabout the format for defaultinstances.

Name A keyword to indicate that aname for the input variableis being declared.


label The name to use for thisinput variable in the instancefield of the Formula Editor.

Can contain only letters andnumbers; spaces are notallowed.

; Indicates the end of the line. Required for every line ofthe formula, includingcomments.

Every formula must begin with a Dim declaration. This allows the formula be usedwith subelements.

A correct example:Dim I1 As Integer Default *;ifInOctets.%I1;

An obsolete example:ifInOctets.*;

Although the second example works in most cases, IBM Corporation recommendsthat you use the first method.

There is only one type of formula that does not require a Dim declaration. If theformula is applied to a scalar object (which therefore has only one instance), theDim declaration can be omitted. In this case, the instance is specified as "0".

For example:sysName.0


OIDVAL expression lineThe OIDVAL expression line executes an expression based on OIDs or statisticsvariables and stores the results to temporary variables. The syntax is:Vn = OIDVAL(<Expression> [, Validity]);

The OIDVAL expression evaluates the expression by retrieving a list of all the OIDsrequired for the execution of the <Expression.> It retrieves the list by replacing allvariables contained in the <Expression> with their substitution values. Allsubstitutions must be resolved in order for the <Expression> to be obtained.

Depending on the Validity settings, the different OIDs and stats variables are eitherrestored from preceding executions or are queried from target devices.

The following table lists the syntax requirements:


Vn A temporary variable.Must be of the form "V1","V" must be capitalized, andmust be followed by anumber.

= Indicates that the result ofthe expression on the rightmust be assigned to thetemporary variable on theleft.

Spaces before and after areoptional.

OIDVAL A keyword that indicatesthat the value of anexpression is being assignedto a temporary variable.

Not case-sensitive.

Expression The expression; thecalculation to be done. Contains at least one OID

(MIB object with a fixedinstance or MIB object with avariable instance) statvariable, or mathematicaloperation.

The expression can be simpleor complex, and can includemore than one OID. Theexpression must be enclosedin parentheses.



Validity Specifies how often tore-evaluate the expression. The choices include:

v Once, evaluate theexpression only at the firstpolling.

v Every, evaluate theexpression at each polling.This is the default.

v xxP, evaluate theexpression at a specifiednumber of pollings. Forexample, 10P meansre-evaluate the expressionon each 10th polling.

v ssss, a specific period, inseconds. For example, 3600means re-evaluate theexpression once each hour.


ExampleDim I1 as integer default *V1=OIDVAL (ifInOctets.%I1 / ifSpeed.%I1 * 100.0, every) ;

When executed with instance string = 2 and the list of required OID includes:ifInOctets.%I1 ; ifSpeed.%I1 ; with I1 in { 2 } forces the execution of SNMPGet :ifInOctets.2 ; ifSpeed.2

Results from SNMPGet include:

ifInOctets [I1 = (int) 2] Æ (int) 1000

ifSpeed [I1 = (int) 2] Æ (int) 512

This produces the following result:

result [I1 = (int) 2] Æ (int) 195.31

Stored in V1, for future use.

OIDINST instructionThe OIDINST expression line stores the values of a key for which the expression istrue (different from zero.) The instruction is primarily used for Discovery formulasto filter a subset of indexes from a large set, based on properties. If the filter isunsuccessful, the row is skipped. If the filter is successful, the value of the indexfor the row is assigned to the temporary variable, and processing continues withthe next line of the formula.

The syntax is:Vn = OIDINST(<Boolean Expression> [, Validity]);



Vn A temporary variable.Must be of the form "V1","V" must be capitalized, andmust be followed by anumber.

=Indicates that the result ofthe expression on the rightmust be assigned to thetemporary variable on theleft.


OIDINST A keyword to indicate that aconditional filter is beingused.

Not case-sensitive.

Expression The expression to be filtered.OID, stat variable, ormathematical operationswith a Boolean result.

Valid operators for filteringare:

like, <, >, <=, >=, ==, !=

More information aboutthese operators can be foundin “Syntax for functions” onpage 88.


Validity specifies how often tore-evaluate the expression The choices include:

v Once, evaluate theexpression only at the firstpolling.

v Every, evaluate theexpression at each polling.This is the default.

v P, evaluate the expressionat a specified number ofpollings. For example, 10Pmeans re-evaluate theexpression on each10thpolling.

v A specific period, inseconds. For example, 3600means re-evaluate theexpression once each hour.

; Indicates the end of the line.Required for every line ofthe formula, includingcomments.


ExampleV1=OIDINST (ifStatus.%1 like `up’)

Based on substitutions of I1 and SNMP query, the SNMP stack returns thefollowing:

ifStatus [I1 = (int) 1] Æ (string) "up"

[I1 = (int) 2] Æ (string) "down"

[I1 = (int) 3] Æ (string) "up"

The Boolean expression that compares the result of ifStatus to up producesfollowing result:

result [I1 = (int) 1] Æ (int) 1

[I1 = (int) 2] Æ (int) 0

[I1 = (int) 3] Æ (int) 1

OIDINST stores all keys of a result that point to a result different from 0 in the V1vector, in the value field.

Two keys (I1=1, and I1=3) are selected.

V1 is constructed with no dimension and multiple values.

V1 [] Æ { (int) 1 ; (int) 3 }

Such a V1 variable can be used in another expression line, exactly in the same wayas an Ix variable, because it has no dimension and that supports multiple possiblesubstitutions.

This OIDINST operator only works when the index is composed of only onedimension. If the index comprises more than one dimension, all substitutionsvalues are concatenated and separated by character dot. Types of each dimensionare lost and the resulting type of V1 variables is string (this is default type, whenno explicit type is declared). Not using explicit types has more side effects thanbenefits. Do not use this OIDINST operator when there is more than one dimension.

The following illustrates a dlci status example:V1=OIDINST( dlciStatus.%I1.%I2 like "up" )

V1 [] Æ { (int) 1 ; (int) 3 }

Such a V1 variable can be used in another expression line, exactly in the same wayas an Ix variable, because it has no dimension and that supports multiple possiblesubstitutions.

This OIDINST operator only works when the index is composed of only onedimension. If the index comprises more than one dimension, all substitutionsvalues are concatenated and separated by character dot. Types of each dimensionare lost and the resulting type of V1 variables is string (this is default type, when


no explicit type is declared). Not using explicit types has more side effects thanbenefits. Do not use this OIDINST operator when there is more than one dimension.

The following illustrates a dlci status example:V1=OIDINST( dlciStatus.%I1.%I2 like "up" )

dlciStatus [I1 = (int) 1]; [I2 =(int) 101]

Æ (string) "up"

[I1 = (int) 1]; [I2 =(int) 102]

Æ (string) "down"

[I1 = (int) 2]; [I2 =(int) 103]

Æ (string) "up"

Two keys ( I1=1,I2=101 and I1=2,I2=103 ) are selected because more than onedimension involved, keys are transformed to 1.101 and 2.103 and V1 is set to:

V1 [] Æ { (string) "1.101" ;(string) "2.103" }

On the next substitution using V1 values, the <interface>.<dlci> information is lost.

Types of variablesFormulas can include the following three classes of variables:v instancev temporaryv host

In most cases, these variables are actually vectors.

Instance variablesInstance variables represent the input values for a formula.

They are declared as a capital I, followed by a number (single digit) between 1 and9. For example:

I1, I2, I3, and so on.

You can use the following two methods to set values for the instance variables:v Setting values in the Instance field of the Formula Editorv Assigning a subelement to a request using the Request Editor

The instance field is an ASCII string, which must be constructed as the followingsequence:[name]<values>

The name is only used as a comment, for clarification of the formula syntax,expectations of the values. Values are exact strings that will be used forreplacement of

To use the value of the instance variable in a formula, add %:


%I1, %I2, %I3, and so on.

Only values whose responses do not return errors are retained for interpreting theremaining lines of the formula.

The valid types for an instance variable correspond to SNMP types. They are:v Integerv IP addressv Gaugev Counterv MacAddressv OctetStringv DisplayStringv Timeticks

These names are not case-sensitive when used in a formula.

Default instances can include a list of values or * to indicate that all instances mustbe used. Spaces are not allowed within a list of values for an instance variable.These are valid:v integer, for example: 3v list of integers, for example: 1,3,6,9,8,109v interval, for example: 4-59v list of integers and intervals, for example: 1,3,6,9,8-96,109,200-250v character string, enclosed in double quotation marks, for example: "this is a

STRING"v pointer to a string, for example: 128.3.56.7v wildcard: *

Temporary variablesTemporary variables hold an intermediate SNMP result or a partial result. You donot need to use temporary variables in a formula. Only use temporary variables ina collection formula when strictly required, because of the possible performanceimpact.

These temporary variables can be used as parameters for subsequent queries. Theyare created with the OIDINST instruction or the OIDVAL instruction.

The type of the result of the function on the right side of the equation is assignedautomatically as the type of the variable. The previous contents of the variable areoverwritten at each assignment.

Temporary variables are declared as a capital V, followed by a number:v If fewer than nine variables are defined, numbering is 1 - 9. For example, V1,

V2, V3, and so on.v If up to 99 variables are defined (even if less than 10 are used,) numbering is 01

- 99. You must use two digits. For example, V09, V11, V34, and so on.

To use the value of the variable in a formula, add %:

%V1, %V2, %V3, and so on.


Host variableThe host variable (Hx) represents the current host name.

Because multihost formulas are not supported, the only instance of this variable isH1. You can set the value by using the Formula Editor, by setting a target elementor subelement for test, or by defining a target in the Request Editor table.

Returning a resultOnly the result of the last line of a formula is returned. This was illustrated in theexample formulas. Prior lines made calculations, and manipulated variables, butonly the last line returned a result.

The MIB objects returned by the last line of a discovery formula become propertiesin the database, and can be used to create grouping rules with the Rule Editor.

For more information about the Rule Editor, see Chapter 4, “Creating groupingrules,” on page 47.

Comments in formulasTo add comments to a formula:v put each comment on a line by itselfv start each line with the pound sign (#)v end each line with a semi-colon (;)# This is a comment;

Do not include a comma (,) or semi-colon (;) within the body of the comment.

Syntax for functionsThe Formula Editor includes the following function options.

Mathematical functions


+Addition

The plus sign can also be used to indicatemerging preference for a Discovery formulathat the value will only overwrite previouscontent if the previous content was missingor empty.

-Subtraction

The minus sign can also be used to indicatemerging preference for a Discovery formulathat the value will only overwrite theprevious content if the previous content wasmissing.



*Multiplication - you need to add a spacebefore each * (multiply star) for the formulato be correctly parsed.

The asterisk, or multiply star, can also beused to indicate merging preference for aDiscovery formula that the value will alwaysoverwrite the previous content.

/ Division

% Returns the remainder of an integer division

< Less than, the same as in the Cprogramming language

<= Less than or equal to, the same as in the Cprogramming language

> Greater than, the same as in the Cprogramming language

>= Greater than or equal to, the same as in theC programming language

== Equal to, the same as in the C programminglanguage

!= Not equal to, the same as in the Cprogramming language

Int() Returns only the integer part of theexpression

Log() Returns the logarithm (log10)

Ln() Returns the natural logarithm (loge)

Abs() Returns the absolute value

Exp() Returns the value of ex

Round() Returns number rounded to the nearestmultiple of significance

Other functions


&& Logical AND

|| Logical OR

like Performs an ASCII comparison of twoarguments. Wildcards can be used in theright-hand argument. For example, to testthe start of a sysObjectID compared to avendor, without going into the modeldetails.

Not() Negates the expression; provides theopposite.


SNMP-specific functions


delta()Calculates the difference between the valueretrieved during this polling and the valueretrieved during the previous polling for asingle SNMP variable. This difference canonly be positive because these variablesmust be counter variables. This functionmanages counter overflows and resets.

Last()Returns the value assigned to this expressionduring the previous polling.

Diff() Returns the difference between the currentvalue of this expression and its value for theprevious polling. This value can be positiveor negative.

These functions cannot be nested.

Aggregate functionsFor these functions, the expression defines an operation. The dimension specifiesthe variable used as an index for that operation.


Sum (Dimension, Expression)Returns the total of all values. For example:

Sum (*, ifInOctets.%I1)

provides all octets entered on all theinterfaces.

Max (Dimension, Expression)Returns the highest value encountered. Forexample:

Max (*, ifInOctets.%I1)

provides the number of octets entered on theinterface with the highest number ofincoming octets.

Min (Dimension, Expression)Returns the lowest value encountered. Forexample:

Min (*, ifInOctets.%I1)

provides the number of octets entered on theinterface with the lowest number ofincoming octets.

Count (Dimension, Expression) Returns a count.

Ave (Dimension, Expression) Calculates the average.


Filter functions


FirstN (Number of items, Expression) Retains only the N lines with the highestresult.

LastN (Number of items, Expression) Retains the N lines with the lowest results.

Filter (Expression)Retains only the lines with a true result. Innormal use, the expression is a Boolean thatreturns 1 (true) or 0 (false).

Distribution functionThis function specifies the distribution of results within a formula. It provides aquantified, non-linear numerical result. For example, you can assign values suchas:

5 for a load between 1% and 5%

4 for a load between 5% and 10%

1 for a load > 30%, and so on.

The syntax is:distrib (Expression, Definition)

The Definition string contains the list of tests to be performed, and the value of theresult to be used if the comparison is positive. The Definition is a series of"condition: value" fields separated by commas. These are allowed in the condition:<, <=, >, >=, ==. They are compared to a numerical value, and the result is eitherthe specified value, or * to keep the initial value.

The Definition string must be enclosed in double quotation marks. It is evaluatedfrom left to right. As soon as a condition is true, the corresponding value isreturned. If no conditions are true at the end of the string, then no value isreturned. Therefore, the distribution function can filter for specified values.

For example:Dim I1 as Integer ;

V1=OIDVAL(Distrib( (8*delta(ifInOctets.%I1))/(delta(sysUpTime.0)/100),’<100:1,<1000:2,<100000:3,<1000000:4,<5000000:5,default:6’), every);

Note: Although the width of the page forces the second line of the formula towrap onto three lines in this example, when using the Formula Editor each line ofa formula must be on one line. Long lines cannot wrap.


AddForMissing() operatorThis operator allows extending the size of a result set and adding news resultsentries by using entries and dimensions from a reference vector. The onlyprerequisite is that both the expression, and the reference vector have the samedimensions set.addForMissing ( Expression , reference Vector [, defaultreplacement ] )

The result of the operator is an extension of Expression. For each dimension entrythat is present in reference Vector only, a new dimension entry is added toExpression, using either the result in the reference vector, or the defaultreplacement submitted

ExampleExpression alone would result in the following results.

Expression [I1 = (int) 1] Æ (int) 10

[I1 = (int) 3] Æ (int) 30

[I1 = (int) 4] Æ (int) 40

The reference vector, obtained with an OIDVAL operation (in a precedent line,) hasthe same Dimension set (I1), but with more replacement values (1, 2, 3, 4, 5, 6)

Reference vector [I1 = (int) 1] Æ (int) 11

[I1 = (int) 2] Æ (int) 21

[I1 = (int) 3] Æ (int) 31

[I1 = (int) 4] Æ (int) 41

[I1 = (int) 5] Æ (int) 51

[I1 = (int) 6] Æ (int) 61

The addForMissing operator detects that the replacement values (2, 5, and 6) werenot defined in the original result set, and creates entries for them.

If no default Replacement is provided, corresponding results from Reference vectorare used. This generates the following result:

result [I1 = (int) 1] Æ (int) 10 // fromExpression

[I1 = (int) 2] Æ (int) 21 // fromreference vector

[I1 = (int) 3] Æ (int) 30 // fromExpression





If a default Replacement is provided, this default value is inserted for all newentries. This generates the following result:

result [I1 = (int) 1] Æ (int) 10 // fromExpression

[I1 = (int) 2] Æ (int) default value





Using the Formula SelectorYou can load an existing formula from the Formula Selector window.

About this task

To open the Formula Selector, follow these steps:

Procedure

Click File > Selectors > Formula Selector.

Note: You can also use the formsel command-line interface (CLI) command tolaunch the Formulas Selector from the command line.

Creating a formula groupProcedure1. Follow steps 1 in “Using the Formula Selector.”2. Right-click and select New > Group.3. Enter a unique name for the group and press the Enter. The new group is

created.

Finding a formulaAbout this task

To find a formula, follow these steps:

Procedure1. Follow step 1 in “Using the Formula Selector.”2. Select a group or sub-group from the Formula branch.3. Select Find from the menu.4. Enter the group or formula name you want to find and click OK.

To expand the search, you can use a "*" wildcard at the beginning, in themiddle, or at the end of a character string.For example:v CIS* - search for all the names beginning with CISv *SCO - search for all the names ending with SCO


v C*O - search for all the names beginning with C and ending with O.v *MIB* - search for all the names containing MIB.If more than one item is found, the Find Choices box appears.

5. Click OK to close the Find Choices box.

Copying formulasAbout this task

You can copy a single formula or a group/sub-group of formulas.

To copy formulas, follow these steps:

Procedure1. Follow step 1“Using the Formula Selector” on page 93.2. Expand a group or subgroup.3. Select a formula, group, or subgroup to copy.4. Right-click and select Copy.5. Alternatively, you can select Cut to remove the formula, group, or subgroup

from its current location and paste it to another location.6. The text for the items that you select turns blue to indicate that they are copied.7. Paste the selection to the location of your choice.

Deleting a formulaAbout this task

To delete a formula, follow these steps:

Procedure1. Follow step 1 in “Using the Formula Selector” on page 93.2. Select a formula, group, or subgroup.3. Right-click and select Delete. The items you select are deleted from view.4. Click Apply to confirm the deletion.5. Click Revert if you want to restore the deleted items.

Renaming a formulaProcedure1. Follow step 1 in “Using the Formula Selector” on page 93.2. Expand one of the directories.3. Select a formula from the tree.4. Select Rename from the menu.5. Enter the new name.

Formula examplesThis section contains three examples of formulas:v Discoveryv Collectionv Discovery merge


Discovery formula for a Redback Ethernet interfaceThe following example shows a Discovery formula that discovers all RedbackEthernet interfaces. For each interface, it reports the type, description, and speed.

To use this formula automatically with the Inventory Tool, it must have anassociated entry in the inventory_subelements.txt file.

For information about how to create the associated entry, see “Understanding theinventory_subelements.txt file” on page 108.Dim I1 AS Integer Default * NAME Interface;V1=OIDINST(ifType.%I1 == 6, once);V2=OIDVAL(ifDescr.%V1, once);V3=OIDVAL(int(ifSpeed.%V1/1000000), once);%V2 index "RedbackEthernet<%V1>||%V2 %V3mbps Inst %V1||ifSpeed<%V3mbps>ifDescr<%V2>";

Line-by-Line explanationDim I1 AS Integer Default * NAME Interface

This line declares the input variable I1. It specifies that it is an integer, that thedefault is all instances, and it is called Interface.

Further information about the Dim statement is available in “Dim declaration” onpage 80.



Not case-sensitive.

I1 The input variable."I" must be capitalized, andmust be followed by anumber.

AS A keyword to indicate thatthe data type of the inputvariable is being declared.

Not case-sensitive.

Integer The data type of the inputvariable. Not case-sensitive. The valid






* The instances to use if noother instances are specified.In this case, * specifies thatall instances must be used.

Default instances can be alist of values

Or

* to indicate that all instancesmust be used.




Interface The name to use for thisinput variable in the instancefield of the Formula Editor.

Must contain only letters andnumbers; underscores andspaces are not allowed.


V1=OIDINST(ifType.%I1 == 6, once);

This line restricts the type of row to which the formula is applied. It checkswhether the value of ifType for each row is 6, which is defined in RFC1213 tomean ethernet-csmacd. If the value is not equal to 6, the row is skipped. If thevalue is equal to 6, the value of ifIndex for this row is assigned to V1, andprocessing continues with the next line of the formula.

Further information about the OIDINST instruction is available in “OIDINSTinstruction” on page 83.


V1 A temporary variable."V" must be capitalized, andmust be followed by anumber.



OIDINST A keyword to indicate that aconditional filter is beingused/

Not case-sensitive.



ifType A MIB object to which thefilter is applied. In this case,ifType indicates the ifTypecolumn of the ifTable.

Case sensitive, must be aMIB object in a MIBcompiled in Tivoli NetcoolPerformance Manager.

See Chapter 9, “ManagingMIBs,” on page 131forinformation about how touse the MIB Browser and theMIB Compiler.

. Separates the MIB objectfrom the instance.

Spaces are not allowedbefore or after.

%I1 The instance of the MIBobject. In this case, thevalues of the previouslydefined input variable issubstituted.

Must begin with %, andmust:

v match a previouslydefined input variable

Or

v be a constant

Or

v be the * wildcard

== "equal to" the same as in theC programming language. Spaces before and after are

optional. Valid operators forfiltering are:

like, <, >, <=, >=, ==, !=

See “Syntax for functions” onpage 88 for more informationabout these operators.

6 The value to be filtered. Inthis case 6, which isdefinedin RFC1213 to meanethernet-csmacd.

Can be any value that isvalid for the MIB objectbeing used

once A keyword to indicate thatthe data must be retrievedonly once, not polledrepeatedly.

Preceded by a comma;spaces before and after thecomma are optional.


V2=OIDVAL(ifDescr.%V1, once);

This line retrieves the value of ifDescr for each value for V1 of the previous line.It assigns the value of ifDescr.%V1 to V2.

Further information about the OIDVAL instruction is available in “OIDVALexpression line” on page 82.



V2 A temporary variable."V" must be capitalized, andmust be followed by anumber.



OIDVAL A keyword that indicatesthat the value of anexpression is being assignedto a temporary variable.

Not case-sensitive, theexpression must be enclosedin parentheses.

ifDescr A MIB object, the value ofwhich is assigned to thetemporary variable. In thiscase, ifDescr indicates theifDescr column of the ifTable.

Case sensitive, must be aMIB object in a MIBcompiled in Tivoli NetcoolPerformance Manager.

See Chapter 9, “ManagingMIBs,” on page 131 forinformation about how touse the MIB Browser and theMIB Compiler.



%V1 The instance of the MIBobject. In this case, thevalues of the previouslydefined temporary variable issubstituted.

Must begin with %, andmust match a previouslydefined temporary variable.

once A keyword to indicate thatthe data must be retrievedonly once, not polledrepeatedly.



V3=OIDVAL(int(ifSpeed.%V1/1000000), once);

This line retrieves the value of ifSpeed for each value for V1 from the second lineof the formula. It divides this value by 1,000,000, to convert from bits/second tomegabits/second. It applies the int function to convert the result to an integer. Itassigns that integer to V3.

Further information about the OIDVAL instruction is available in “OIDVALexpression line” on page 82.


V3 A temporary variable."V" must be capitalized andfollowed by a number.


=Indicates that the result ofthe expression on the rightmust be assigned to thetemporary variable on theleft.


OIDVALA keyword that indicatesthat the value of anexpression is being assignedto a temporary variable.

Not case-sensitive. Theexpression must be enclosedin parentheses.

intA function that returns onlythe integer part of anexpression.

Not case-sensitive. The list ofall available functions can befound in “Syntax forfunctions” on page 88.

ifSpeedA MIB object, the value ofwhich is used in thecalculation. In this case,ifSpeed indicates the ifSpeedcolumn of the ifTable.

Case sensitive, must be aMIB object in a MIBcompiled in Tivoli NetcoolPerformance Manager. SeeChapter 9, “Managing MIBs,”on page 131for informationabout how to use the MIBBrowser and the MIBCompiler.



%V1The instance of the MIBobject. In this case, thevalues of the previouslydefined temporary variable issubstituted.


/ Division Spaces before and after areoptional. See “Syntax forfunctions” on page 88 for alist of operations.

1000000Used to calculatemegabits/second fromifSpeed, which is inbits/second.

onceA keyword to indicate thatthe data must be retrievedonly once, not polledrepeatedly.



The result of a Discovery formula contains four parts:v First part must be a variable (%Vxxx) or an expression. The number of values of

the variable or the number of returns of the expression drives how many resultscan be produced by the Discovery formula.


v Second part is the instance of the subelement.v Third part is prefaced with the host name and "_" to become the label field in

both the Subelement and Host Selector, and in the Subelement Editor.v Fourth part (ifSpeed<%V3mbps>ifDescr<%V2>) contains details about the interface.

The MIB objects returned by the last line of the formula (ifSpeed, ifDescr)become properties in the database, and can be used to create grouping ruleswith the Rule Editor.

See Chapter 4, “Creating grouping rules,” on page 47 for more information aboutthe Rule Editor.


%V2 A temporary variable thatindicates a result is beingreturned. The value of thisvariable is appended to theend of the return string. Inthis case, ifDescr for eachinstance is assigned to it inthe third line of the formula.

Must begin with %, andmust match a temporaryvariable from the left side ofa previous OIDVALinstruction. A temporaryvariable from a previousOIDINST instruction causes anerror.

indexA keyword that allows youto add text strings to theoutput.

Not case-sensitive, spacesrequired before and after.

" Indicates the beginning ofthe output.

RedbackEthernetA text string to describe theoutput. In this case, thename of the interface.

ASCII text, double quotationmarks must not be usedwithin the string.

<%V1>A temporary variable. In thiscase, ifIndex for eachinstance is assigned to it inthe second line of theformula.


||Separates the instance of thesubelement from the labelfield.

%V2A temporary variable. In thiscase, ifDescr for eachinstance is assigned to it inthe third line of the formula.


%V3A temporary variable. In thiscase, the speed of theinterface for each instance isassigned to it in the fourthline of the formula.



mbpsA text string to describe theoutput. In this case,megabits/second, the unitscalculated in the fourth lineof the formula.


Inst A text string to describe theoutput. In this case, anabbreviation for "instance."


%V1 A temporary variable. In thiscase, ifIndex for eachinstance is assigned to it inthe second line of theformula.


|| Separates the label field fromthe details about theinterface.

ifSpeedA text string to describe theoutput. In this case, thename of a MIB object.

MIB objects returned by thelast line of a discoveryformula become properties inthe database, and can beused to create grouping ruleswith the Rule Editor. SeeChapter 4, “Creatinggrouping rules,” on page 47for details about Rule Editor.


<%V3>A temporary variable. In thiscase, the speed of theinterface for each instance isassigned to it in the fourthline of the formula.


mbps> A text string to describe theoutput. In this case,megabits/second, the unitscalculated in the fourth lineof the formula.


ifDescrA text string to describe theoutput. In this case, thename of a MIB object.

MIB objects returned by thelast line of a discoveryformula become properties inthe database, and can beused to create grouping ruleswith the Rule Editor. SeeChapter 4, “Creatinggrouping rules,” on page 47for details about Rule Editor.

ASCII text, double quotationmarks mustnot be usedwithin the string.


<%V2>A temporary variable. In thiscase, ifDescr for eachinstance is assigned to it inthe third line of the formula.


" Indicates the end of theoutput.


Collection formula exampleThe following example shows a Collection formula for inbound bandwidth. To usethis formula automatically with the Inventory Tool, it must have an associatedentry in the inventory_subelements.txt file.

See “Understanding the inventory_subelements.txt file” on page 108 forinformation about how to create the associated entry.Dim I1 AS Integer Default * Name Interface;delta(ifInOctets.%If)/delta(sysUpTime.0/100);

Line-by-Line explanationDim I1 AS Integer Default * Name Interface;

This line declares the input variable I1. It specifies that it is an integer, that thedefault is all instances, and it is called "Interface."

Further information on the Dim statement is available in “Dim declaration” onpage 80.



Not case-sensitive.

I1 The input variable. "I" must be capitalized, andmust be followed by anumber.

AS A keyword to indicate thatthe datatype of the inputvariable is being declared.

Not case-sensitive.

Integer The datatype of the inputvariable. Not case-sensitive. The valid






* The instances to use if noother instances are specified.In this case, * specifies thatall instances should be used.

Default instances can be alist of values

Or

* to indicate that all instancesshould be used.




Interface The name to use for thisinput variable in the instancefield of the Formula Editor.(This name will also appearin the Request Editor.)

Can contain only letters andnumbers; spaces are notallowed.


delta(ifInOctets.%If)/delta(sysUpTime.0/100);

This line returns the final result. It calculates the number of incoming cells, as thenumber of octets divided by 53. It then divides this by the time period over whichthe collection was done.


delta A function that calculates thedifference between the valueretrieved during this pollingand the value retrievedduring the previous pollingfor a single SNMP variable.

Must be lower case. Furtherinformation is available in“SNMP-specific functions”on page 90.

ifInOctets A MIB object on which thecalculation will be done. Inthis case, ifInOctets indicatesthe ifInOctets column of theifTable.

case-sensitive, must be a MIBobject in a MIB compiled inTivoli Netcool PerformanceManager.

See Chapter 9, “ManagingMIBs,” on page 131 forinformation on how to usethe MIB Browser and theMIB Compiler.



.Separates the MIB objectfrom the instance.


%IfThe instance of the MIBobject. In this case, inboundbandwidth


/ Division Spaces before and after areoptional. The list of possibleoperations is in “Syntax forfunctions” on page 88.

53Used to calculate the numberof cells from the number ofoctets.

Spaces before and after areoptional. The list of possibleoperations is in “Syntax forfunctions” on page 88.

deltaA function that calculates thedifference between the valueretrieved during this pollingand the value retrievedduring the previous pollingfor a single SNMP variable.

Must be lower case. See“SNMP-specific functions”on page 90 for moreinformation.

sysUpTimeA MIB object on which thecalculation will be done. Inthis case, sysUpTimeindicates the time since thesystem was re-initialized.

case-sensitive, must be a MIBobject in a MIB compiled inTivoli Netcool PerformanceManager.

See Chapter 9, “ManagingMIBs,” on page 131forinformation on how to usethe MIB Browser and theMIB Compiler.

.Separates the MIB objectfrom the instance.


0The instance of the MIBobject. In this case,sysUpTime is scalar, so "0" isused as the only instance.

Spaces before and after areoptional. The list of possibleoperations is in “Syntax forfunctions” on page 88.

/ Division

100 Used to calculate the numberof seconds from the value ofsysUpTime, which is inhundredths of a second.



Merge formulas exampleThe following example implements the following on top of standard MIB IIformula (1213_IF and 2233_IF):v Octet capability detection: inbound and outbound, 64, 32, or undefined.v Packets capability detection: 64 or 32 or undefinedv Custom invariant, either from MIB II ifDescr, or RFC2233 ifNamev Customer-specific key and properties

inventory_sub-element.txt# File format:#{FAMILY} |{Elem. FAMILY}|{sysObjId Mask} |{Match Formula} |{I}|{Discovery Formula}|{I}|{cancel FAMILY};[{...};]|

1213_Device |Generic~Agent |1.3.6.1 |NULL |<*>|AP~1213_Device |<*>| |

1213_IF |Generic~Agent |1.3.6.1 |NULL |<*>|AP~1213_IF |<*>| |

2233_IF |Generic~Agent |1.3.6.1 |AP~2233_IF_match |<*>|AP~2233_IF |<*>| 1213_IF;|

2233_IF(Exp) |Generic~Agent |1.3.6.1 |AP~2233_IF_match |<*>|AP~2233_HCOctets_Support |<*>| |

2233_IF(Exp) |Generic~Agent |1.3.6.1 |AP~2233_IF_match |<*>|AP~2233_HCPackets_Support |<*>| |

1213_IF(Exp) |Generic~Agent |1.3.6.1 |NULL |<*>|AP~1213_IF_Invariant |<*>| |

2233_IF(Exp) |Generic~Agent |1.3.6.1 |AP~2233_IF_match |<*>|AP~2233_IF_Invariant |<*>| |

1213_IF(Exp)|Generic~Agent |1.3.6.1 |NULL |<*>|AP~TELUS_KEY

1213_IFDim I1 AS Integer Default * NAME If;V1 = OIDVAL(ifType.%I1 format clean, once);V2 = OIDVAL(sysLocation.0, once);V3 = OIDVAL(ifSpeed.%I1, once);V4 = OIDVAL(int(%V3/1000000), once);V5 = OIDVAL(ifAdminStatus.%I1 format clean, once);V6 = OIDVAL(ifDescr.%I1, once);%V1 index "If<%I1>||IF %I1 (%V4Mbps)||type<%V1>location<%V2>physicalCapacity<%V3>status<%V5>||";

2233_IFDim I1 AS Integer Default * NAME If;V1 = OIDVAL(ifType.%I1 format clean, once);V2 = OIDVAL(sysLocation.0, once);V3 = OIDVAL(ifSpeed.%I1, once);V4 = OIDVAL(int(%V3/1000000), once);V5 = OIDVAL(ifName.%I1 format clean, once);V6 = OIDVAL(ifAdminStatus.%I1 format clean, once);V7 = OIDVAL(ifAlias.%I1 format clean, once);V8 = OIDVAL(ifDescr.%I1, once);%V1 index "If<%I1>||IF: %I1 (%V5) (%V4Mbps)||type<%V1>location<%V2>physicalCapacity<%V3>name<%V5>status<%V6>||";


2233_HCOctets_SupportDim I1 AS Integer Default * NAME If;V1 = OIDVAL( ifIndex.%I1 );V2 = OIDVAL( filter( ifHCInOctets.%I1 >0) );V3 = OIDVAL( filter( ifInOctets.%I1 >0) );V5 = OIDVAL( filter( ifHCOutOctets.%I1 > 0 ) );V6 = OIDVAL( filter( ifOutOctets.%I1 > 0) );%V2+%V5 index"If<%I1>||-UNSPECIFIED_LABEL||Octets<in64.out64>||";%V2+%V6 index"If<%I1>||-UNSPECIFIED_LABEL||Octets<in64.out32>||";%V3+%V5 index"If<%I1>||-UNSPECIFIED_LABEL||Octets<in32.out64>||";%V3+%V6 index"If<%I1>||-UNSPECIFIED_LABEL||Octets<in32.out32>||";%V2 index"If<%I1>||-UNSPECIFIED_LABEL||Octets<in64.out0>||";%V3 index"If<%I1>||-UNSPECIFIED_LABEL||Octets<in32.out0>||";%V5 index"If<%I1>||-UNSPECIFIED_LABEL||Octets<in0.out64>||";%V6 index"If<%I1>||-UNSPECIFIED_LABEL||Octets<in0.out32>||";%V1 index"If<%I1>||-UNSPECIFIED_LABEL||Octets<in0.out0>||";

2233_HCPackets_SupportDim I1 AS Integer Default * NAME If;V1 = OIDVAL( ifSpeed.%I1 );V2 = OIDVAL( filter (( ifHCInUcastPkts.%If +ifHCInMulticastPkts.%If + ifHCInBroadcastPkts.%If ) > 0) );V3 = OIDVAL( filter (( ifInUcastPkts.%If+ ifOutUcastPkts.%If +ifInNUcastPkts.%If + ifOutNUcastPkts.%If ) > 0) );%V2 index "If<%I1>||-UNSPECIFIED_LABEL||Packets<64>||";%V3 index "If<%I1>||-UNSPECIFIED_LABEL||Packets<32>||";%V1 index "If<%I1>||-UNSPECIFIED_LABEL||Packets<no>||";

1213_IF_Invariant# provide ifDescr and ifType as default invariantDim I1 AS Integer Default * NAME If;V1 = OIDVAL(ifType.%I1 format clean, once);V2 = OIDVAL(ifDescr.%I1, once);%V1 index "If<%I1>||-UNSPECIFIED_LABEL||||%V1-%V2";

2233_IF_Invariant# provide invariant based on ifName, when non emptyDim I1 AS Integer Default * NAME If;V1 = OIDVAL( filter ( not (ifName.%I1 like "") ), once);V2 = OIDVAL( ifName.%I1 , once);%V1 index "If<%I1>||-UNSPECIFIED_LABEL||||*%V2";


<CustomerSpecific>_KEYThe following example shows the <CustomerSpecific> key titled OurCustomer.Dim I1 AS IPAddress Default * NAME I1;V01=OIDVAL( ipAdEntAddr.%I1 );V02=OIDVAL( ipAdEntIfIndex.%I1 );V09=OIDVAL(expand(V02, ifDescr.%V02) );%V09 index"If<%V02>||-UNSPECIFIED_LABEL||OurCustomerKEY<%V09>HPKEY<%V09>IP@<%V01>||";

Formula error messagesYou might encounter one or more of the following error messages when editingand testing formulas.

Error Message Description

Initialization is not properly achieved. Error in formula.

NO DATAError in formula

Or

The formula is fine; however, there isnothing to collect

Or

The device does not respond as expected

Or

The formula timed out. This can happen ifthe formula includes more than one deltafunction and is launched against a targetwith a large number of sub-elements. Trylaunching the formula against a morespecific target.

Error while casting variableIncorrect input variable. "I" (letter I) must becapitalized, and must be followed by anumber.

Object identifier was not found in any of thecompiled MIBs The MIB object used is invalid. Check that

the name is correct. Names are casesensitive.

Or

Use the MIB Browser to check that the MIBhas been compiled in Tivoli NetcoolPerformance Manager. If necessary, use theMIB Compiler to compile the MIB in TivoliNetcool Performance Manager.

See Chapter 9, “Managing MIBs,” on page131 for information on how to use the MIBBrowser and the MIB Compiler.


ClientServices open Unable to connect toserver at localhost Check that the collector is running.

See Viewing Collector Information in the IBMTivoli Netcool Performance Manager: DataMartConfiguration and Operation Guide forinformation about the collector.

Error Message Description

"DATA at" with the date & time, but nextline is "End" with no data Inappropriate target

Or

Error in formula

Understanding the inventory_subelements.txt fileThe inventory_subelements.txt file contains the list of rules the Discovery uses. Itis located in the conf directory under the PVM directory.

When you create new discovery formulas, you need to edit this file to create newrules. You must edit the file before the new Discovery formula can be used by theInventory Tool. (You do not need to edit this file before a new collection formulacan be used.)

Discovery formulas are used only against elements, not against subelements.During Discovery, the Inventory Tool uses the sysObjectID field in theinventory_subelements.txt file to determine the correct formula to use for eachelement it encounters. The file already includes generic formulas that match anysysObjectID, and numerous formulas for specific vendors and specific interfaces.The file only needs to be edited to add a new formula.

“Discovery formula for a Redback Ethernet interface” on page 95).

Field Example Purpose

SubElementFamilyName Redback_SMS_EthernetDetermines howsub-elements are grouped inthe Subelement and HostSelector.

FamilyName Router~Redback

SysObjId 1.3.6.1.4.1.2352.1.The sysObjectID, or a part ofthe sysObjectID.

For further information, see“SysObjId” on page 109.

FilterFormulaName NULLThe path to the formula thatis used to distinguishbetween different elementswith the same sysObjectID.

For further information, see“FilterFormulaName” onpage 110.


Instance <*>The instances to which theformula should be applied.This should correspond tothe input variables in theformula listed underFilterFormulaName.

If the formula contains morethan one DIM declaration,there should be more thanone Instance entry. If theformula only retrieves scalarobjects, the instance can beempty.

SubElementFormulaName PVL~Redback~EthernetThe path to the discoveryformula for this subelement.The path is a location withinthe "Alias Instance and LabelInventory" directory, and isspecified with tilde (~) as thepath separator.

Instance <*>The instances to which theformula should be applied.This should correspond tothe input variables in thefilter listed underSubElementFormulaName.

If the formula contains morethan one DIM declaration,there should be more thanone Instance entry. If theformula only retrieves scalarobjects, the instance can beempty.

SubElementFormulaName tocancel Generic_Lan_Ethernet10;

Generic_Lan_Ethernet100;

Generic_Lan_Ethernet1000

A list ofSubElementFormulaName thatshould not be used with thissysObjectID.

For more information, see“SubElementFamilyName tocancel” on page 110.

SysObjIdThis field is the sysObjectID. The Inventory Tool checks to see if the sysObjectIDof each element matches the sysObjectID listed here. If they match, it checks to seeif there is an entry for FilterFormulaName. If the element matches both entries, theInventory Tool runs the formula specified under SubElementFormulaName.

Only a partial match for the sysObjectID is required. There are generic formulasincluded with Tivoli Netcool Performance Manager DataMart that specify 1.3.6.1 asthe sysObjectID. This is not an exact match for anything, but it is a partial matchfor everything. Since only a partial match for the sysObjectID is required, thesegeneric formulas are used against every element encountered by the Inventory


Tool. Any vendor-specific formula contains a more specific sysObjectID thatmatches only that vendor's sysObjectID.

FilterFormulaNameThis field specifies the path to the formula that is used to distinguish betweendifferent elements with the same sysObjectID.

The path is a location within the "Alias Instance and Label Inventory" directory,and is specified with tilde (~) as the path separator.

For the Redback example, there is no such formula, so the entry is "NULL."

Devices such as the Cisco Catalyst 3000 and Catalyst 5000 would have an entry inthis field. They both have the same sysObjectID; however they can have differentsubelement types; therefore, they require different discovery formulas.

For example, the FilterFormulaName for the Cisco Catalyst 3000 isPVL~Cisco~Catalyst~C3000~Match. Its discovery formula isPVL~Cisco~Catalyst~C3000~Port_HalfDuplex_10Mb.

The FilterFormulaName for the Cisco Catalyst 5000 isPVL~Cisco~Catalyst~C5000~Match. Its discovery formula isPVL~Cisco~Catalyst~C5000~Port_HalfDuplex_10Mb.

If the Inventory Tool finds a match on the sysObjectID, it checks for aFilterFormulaName. If a formula is specified, the element must match both thesysObjectID and the FilterFormulaName before the inventory tool runs the formulaunder SubElementFormulaName.

SubElementFamilyName to cancelThis field contains a list of any SubElementFamilyNames that must not be used withthis sysObjectID.

For the Redback example, the SubElementFamilyNames to be ignored are:Generic_Lan_Ethernet10, Generic_Lan_Ethernet100, andGeneric_Lan_Ethernet1000.

If you leave this blank, the same subelement can appear under two differentgroups, the vendor-specific group and a generic group. If you add information, theInventory Tool ignores the canceled formulas not only for this type of subelementbut for all subelements found on the element being processed.

If you cancel a generic rule that can be applied to more than one type of interface,and the Inventory Tool finds a subelement that does not match any of yourdevice-specific rules but would have matched the canceled generic rule, thatsubelement is not discovered.

For example, if Generic_Node is included in the SubElementFamilyName to cancelfield for the Redback example, the Inventory Tool only discovers Redback ethernetinterfaces. If the element contains other types of subelements, such as ATM, noneof the other subelements are discovered.


Chapter 8. Configuring thresholds

Explains how to configure thresholds using the Resource Editor.

Thresholds are values that are compared against metrics to determine if the metricsexceed or drop below a specific limit. Using thresholds as the measure againstwhich data is evaluated lets you report on only those resources with pertinentdata.

About thresholdsA threshold is a value that is compared against metrics to determine if the metricshave violated a specific constraint. Using thresholds as the measure against whichdata is evaluated lets you report on only those resources with pertinent data.

Threshold report capabilities exist at both the resource and group levels. The CMEuses these threshold values to determine threshold violations and to generateSNMP traps. The information is stored in the database and is used by TivoliNetcool Performance Manager DataView for on-demand and scheduled reports.

Group thresholds are specified on a per formula basis within the Group SummaryTable (GST) reporter parameters. The user specifies values for the critical orwarning thresholds, the duration for which the threshold is in violation, themetrics, and statistics for which the threshold values apply, which user profile canview the thresholds in the report, and the reporter to drilldown to if the thresholdis violated.

Threshold typesYou configure most of these thresholds (group threshold is the exception) usingeither the Resource Editor GUI or the resmgr command.

Tivoli Netcool Performance Manager provides the following types of thresholds tosupply report viewers with the information they want.

burst Ignores the natural network bursts by evaluating how long in a row theviolations occurred per resource. Burst thresholds can be set and resetmultiple times.

period Involves the concept of accumulated duration for which the threshold isviolated. This duration is accumulated per resource until the end of theSLA period. The threshold is violated as soon as a data spike'saccumulated duration by period exceeds a certain duration of time. Periodthresholds, once violated are not reset until the end of the period.

risk A proactive threshold that detects resources that are at risk of violating aperiod threshold before the end of the SLA period.

baselineProvides a view into resource behavior outside the normal range. It uses aprofiled deviation function to compare the current daily behavior with thebaseline as data flows throughout the system (in real time.) What is normalis defined and what is not normal is flagged.


Unlike burst, there is not a single threshold level to consider when determiningduration. The duration determination scheme considers varying threshold levels.And unlike burst, period, and risk thresholds, you do not statically define thebaseline, it dynamically adapts to historical data.

User profiles and threshold typesYou need to decide what threshold information your report viewer needs to see, ifany. You then grant access privileges to the threshold information to report viewersbased on their user profile.

For example, you might want report viewers with the NOC profile to have accessto baseline threshold information to monitor the following:v Unusually high volumes at what is normally a "quiet" time (for example, night

time) that might indicate a security issue.v Unusually high volumes at "peak" time that might indicate that a new

application has been deployed across the network and network capacity needsresizing.

v Unusually low volume at "peak" time that might indicate a potential issue witha router's forwarding mechanism, which continuously transmits data at a lowlevel; impacting user perceived latency.

The following matrix shows the threshold information that each type of audienceprobably wants to see.

Violation Type

ReportConsumer

Burst Period Risk Baseline User Profilefor Reports

ServiceProvider'sNOC

Yes Yes No Yes NOC

Customer No Yes No No SLA

Decision-maker

No Yes Yes Yes PSLA

Basic computationThe arrival of a metric record drives threshold computations. If a metric recorddoes not arrive, no threshold computation occurs. Each incoming metric value iscompared against a deployed threshold definition as part of the overall processingof the threshold record. All threshold statistics in the RA record are then updatedappropriately.

Statistic used for processingThreshold definition specifies the actual statistic to be used in the comparison (forexample, raw or sum). As each metric value arrives, the statistic specified by thisfield is computed and this value is used for the subsequent thresholdcomputations.


Exceeding a threshold levelDetermining whether a threshold is violated involves determining whether themetric exceeds a specified level. The actual comparison order depends on the typeof metric (Over, Under, or Band).

For example, the metric is considered to have exceeded the threshold level whenthe following occurs:v Threshold level is 10v Metric value is 15v Over metric type

However, the metric would not be considered to have exceeded the threshold levelif it was an Under. Determining whether the threshold is violated also involves theduration.

InterpolationIn order to determine how much time is spent `exceeding' a level, the system`interpolates' from the current value back to the previous one. If a previous valuedoes not exist (at the very start of a metric stream) no interpolation is carried out,and a duration of zero is assumed.

The following examples illustrate the linear interpolation process.

Threshold deploymentExplains the basics of threshold deployment. To understand threshold deployment,you need a basic knowledge of how thresholds are processed. Processingthresholds involves working with a metric, group, and resource (m/g/r)combination. (This m/g/r combination directly maps to Resource Aggregations(RAs) m/g/r combination.)

Threshold deployment is the evaluation of thresholds to determine whichthreshold applies to which m/g/r combination. To make the determination, TivoliNetcool Performance Manager examines each m/g/r combination and tries to finda matching threshold definition.

Each threshold definition contains three key fields (Metric, Group, Resource) thatare used to determine deployment. The examination involves comparing them/g/r combination key values with the threshold key values.

Chapter 8. Configuring thresholds 113

Note: Only one threshold definition can apply to a specific m/g/r combination.

Tivoli Netcool Performance Manager looks for matches in the order defined in thefollowing table:

Configuration Metric Group Resource Priority

group- andsubelement-specific

Defined Defined Defined 1

subelement-specific

Defined No Defined 2

group-specific Defined Defined No 3

global Defined No No 4

Priority indicates which configuration takes precedence when multiple thresholddefinitions are available for a single resource. Also, multiple group-specificthresholds can be specified for a single branch of the subelement hierarchy. In thiscase, the definition closest to the resource (farthest from the root) takes precedence.

ExamplesThe following examples illustrate the different configurations. They use the groups,G0, G1, G2, G3, and G4 and the resources, R1, R2, R3.

The runtime context (identified by m/g/r combination) is shown below eachresource. The specific metric, `m' is considered, other metrics have their ownruntime contexts.

Group- specific and subelement-specific exampleThe threshold definition T1(m/G3/R0) means that the key fields have values formetric, group, and resource set to `m', G3 and R0 respectively. Tivoli NetcoolPerformance Manager can match the m/G3/R0 combination with T1(m/G3/R0) -Group-specific and Subelement-specific.

The threshold definition T1 is the only one in the system and it does not matcheither of the other m/g/r/ combinations.


Group-specific exampleA new threshold definition is defined, T2(m/G3/-.) This threshold differs from T1because the resource is undefined. Tivoli Netcool Performance Manager cannotmatch the group- and subelement-specific or subelement-specific configurations,but can find a match for a group-specific configuration. The system determinesthat T2 is deployed against both m/G3/R0 and m/G3/R1.


Group-specific and subelement-specific combined with group-specificThresholds T1(m, G3, R0) and T2(m, G3, -) are defined in the system. Boththresholds specify group G3; in addition T1 specifies the resource. The prioritytable is used to determine which threshold actually applies.

The system deploys T1 against the m/G3/R0 combination (based on the group-and subelement-specific rule which is examined first) and T2 against the m/G3/R1combination (based on the group-specific rule.)

Now a third threshold T3(m, G1, -) is added.

Because T1 and T2 have higher precedence, the runtime deployment state remainsthe same.

The threshold T4(m, G0, -) is also added. Again, T1 and T2 are higher priority forthe m/G3/R0 and m/G3/R1 groups respectively. The threshold deploymentsagainst those m/g/r groups remain the same. However, T4 does get deployedagainst m/G4/R2.


Resource in two groups exampleThe following example shows R1 as a member of G3 and G4. A single thresholddefinition exists, T4 (m/G0/-.) Because R1 is a member of two groups, it belongsto two combinations, m/G3/R1 and m/G4/R1. Therefore, T4 is deployed againstboth these contexts.


TRAP generation rulesProvides a brief overview of trap generation rules. If Tivoli Netcool PerformanceManager is configured to generate traps, trap generation input to a specificthreshold occur when there is a change in the violation state.v burst, period (and proactive) thresholds

Non-Violation <-> Warning Violation <-> Critical Violationv baseline thresholds

Non-Violation <-> Violation

The traps generated reflect the nature of the state transition. For example, whenthe system goes from burst non-violation to burst Warning violation for aparticular m/g/r-threshold; a provisoCMEWarningViolationBurstThr (seeproviso.mib) is generated.

The example illustrated in “Resource in two groups example” on page 117 showsresource R1 as a member of two groups. A threshold is deployed against them/g/r combinations that result from that group membership. Therefore, it ispossible for multiple traps to be generated (one for each m/g/r combination)when a single metric value is processed.

Using the threshold definition period settingProvides a brief overview of the use of the period setting in the calculation of aperiod threshold.

Threshold definitions have a period setting (different from a period threshold) thatcan have the following values:v Dayv Weekv Monthv All (which means Day and Week and Month)

In each m/g/r combination, threshold statistics can be calculated for Days, Weeksand/or Months. The period setting determines which of these time periods thethreshold statistics is calculated for, when processing the type of threshold call aperiod threshold.

Note: Statistics in these m/g/r combinations map directly to Daily, Weekly, andMonthly Aggregation records.

Processing trapsWhen processing an m/g/r combination, it is possible that a period threshold canbe violated for each of the configured periods. If that occurs, the system can sendthree traps, one corresponding to each of the configured periods (one trap for theDay, one for the Week and one for the Month).

However, when processing burst thresholds, a similar violation would lead to asingle trap.


Launching the threshold toolExplains how to launch the Threshold tool from the Tivoli Netcool PerformanceManager DataMart Resource Editor. The Threshold tool lets you configurethresholds.

Procedure1. Click Resource Editor in the Resource tab.2. In the Resource Editor, click the Threshold tab.3. Filter the listings by entering a filter value, and then clickApply Filter. The

following table lists the possible columns that can appear in the window:

Column Description

Metric Name of the metric

Group Name of the subelement group

Resource Name of the resource

Mode Threshold mode

DateDate and time the action takes effect.Actions cannot be applied to the past andtake effect on the hour.

StatStatistic the CME uses to calculate thresholdinformation:

v raw (default)

v min

v max

v avg

v sum

v count

CalcCalculation used to determine the value ofthe following:

v standard

v normalized

v scale

CalcValValue used for calculating the percentageover or under the threshold.

BCrtLLevel of the critical threshold for burstthresholds. Zero implies the threshold is notdefined. The metric must be greater thanthis level to trigger a violation.

BCrtTTime limit for the burst critical threshold.

BWrnLLevel of the warning threshold for burstthresholds. Zero implies the threshold is notdefined.

BwrnT Duration of the burst critical threshold inseconds.


Column Description

BEventIndicates whether Tivoli NetcoolPerformance Manager generates SNMP trapsfor the burst threshold.

PCrtL Level of the period critical threshold forperiod thresholds. Zero implies thethreshold is not defined.

PCrtTDuration the period critical period thresholdin seconds.

PWrnLLevel of the warning threshold for periodthresholds. Zero implies the threshold is notdefined.

PWrnTDuration of the warning period threshold inseconds. Zero (0) indicates an immediatethreshold violation.

PEventIndicates whether Tivoli NetcoolPerformance Manager generates SNMP trapsfor the period threshold.

PDefDefines the period for period and burstthresholds:

v all

v day

v week

v month

If the period is day, week, or month, theGST and RST reports for the other periodsdo not show a violation. If the field is set toall, violations are reported for all periods.

MaxNbDayNumber of days used as the maximumvalue for the computation of the uppercontrol limit. The upper control limit is thetop of what is considered the normal rangeand is used for the baseline threshold.

minNbDay Number of days used as the minimum valuefor the computation of the lower controllimit. The lower control limit is the bottomof what is considered the normal range andis used for the baseline threshold

blCalcMode Mode used in calculation of baseline data:

v 0 = previous days,

v 1= previous same day of the week

blModeBaseline mode

v 1 = under

v 2 = over

v 3 = band


Column Description

blTime Duration of baseline violation.

blTrap Indicates whether the baseline thresholdgenerates a trap.

v 0 = no

v 1 = yes

blUpper Number of standard deviations used as themaximum value for the computation of theupper control limit. The upper control limitis the top of what is considered the normalrange.

blLowerNumber of standard deviations used as themaximum value for the computation of thelower control limit. The lower control limitis the bottom of what is considered thenormal range.

Adding a thresholdAbout this task

This section explains how to add the following types of thresholds by using theAdd Threshold window:v burst (static threshold because you set the value)v period (static threshold because you set the value)v baseline

To add a threshold, follow these steps:

Procedure1. Click the Threshold tab in Resource Editor.2. Click Add from the Edit menu. The Add Threshold window appears.

Selecting metricsYou need to choose the metric to which you want to apply the threshold. Use thisfor all three types of thresholds

Procedure1. Click Browse to access the Formula Selector.2. Go to the metric (formula) you want to by expanding the folders in the left

pane and clicking the folder name to display metrics (formulas) in the rightpane.

3. Click the formula name to highlight it and while holding down the left mousebutton, drag the formula name to the Metric text box. The formula name, alongwith the entire path, appears.For more information about the Formula Selector, see “Using the FormulaSelector” on page 93.


Applying thresholds to a group of subelementsYou can choose to apply the threshold to a group of resources at differentgranularity levels.

About this task

You can apply the threshold to the top group in the grouping tree, to any of theleaves or subleaves. Or, you can choose not to apply the threshold to any group,by leaving the text box blank because you want to apply the threshold to anysubelement containing the metric you have chosen or to just a specific subelementby adding its name to the subelement text box.

If you are applying a group- and subelement-specific threshold, you need toidentify the leaf-level group that contains the resource and apply the threshold tothat group.

To choose the group using the Resource Editor, follow these steps:

Procedure1. Put the focus on the Resource Editor window, while leaving the Add Threshold

window open.2. In the Resource Editor, click the Sub-Element Group tab.3. Click the + sign next to SUB-ELEMENTS in the left pane to expand it. The list

of all subelement groups appears in the left pane.4. Go to the formula group you want to choose. For example, go to the High

Speed Interfaces (>=100 Mbps) group under the All Technologies group.5. Highlight the group name and hold down the left mouse button while

dragging the group name to the Group text box in the Add Threshold window.From here, you can add a specific subelement name from the group or you canleave the Sub-Element text box blank to apply the threshold to all subelementsbelonging to the group, that contain the specified metric.

Specifying subelementsYou can specify the subelement to which you want to apply a threshold. If you donot specify a group for that subelement, the threshold is applied to thatsubelement, in each group to which it belongs.

About this task

To choose a subelement using the Resource Editor:

Procedure1. Put the focus on the Resource Editor window, while leaving the Add

Threshold window open.2. In the Resource Editor, click the Sub-Element Group tab.3. Click the + sign next to SUB-ELEMENTS in the left pane to expand it. The

list of all subelement groups appears in the left pane.4. Go to the subelement that you want to apply the threshold. For example, go

to the list of subelements belonging to the subleaf group calledethernetCsmacd.

5. Click the subleaf group's name to display the list of subelements in the rightpane.


6. Click the subelement name in the right pane to highlight it.7. Holding down the right mouse button, drag the subelement name to the

Sub-Element text box in the Add Thresholdwindow.8. Release the right mouse button. The subelement name appears in the text box.9. Click Apply to finalize your choices.

10. Click Close to clear the message or click Details to open the Details section ofthe message box From here, you can configure the static and baselinethresholds.

Configuring burst or period thresholdsExplains how to configure burst and period thresholds. These thresholds areconsidered static thresholds because you set the value for them by using theconfiguration dialog box. You also define how you want the threshold to act.

Configuring thresholdsProcedure

From the Add Threshold Window, click Static Threshold.

Configuring modeYou need to configure the mode you want to apply to your burst and/or periodthreshold.

Procedure1. Configure the mode you want to apply to the static threshold (burst or period.)

The following table lists the configuration options:

Option Definition Values

Effective dateCurrently not used by TivoliNetcool PerformanceManager.

Threshold is effectiveimmediately after creation orupdate.

Do not edit this value.

Mode Mode of the thresholdClick the down arrow toaccess the list of values:

v Band: detect violationswhen they go outside arange (or band) betweentwo threshold values

v Over: detect violationswhen they exceedthreshold values

v Under: detect violationswhen they fall short ofthreshold values

Statistic modeIndicate which statistic youwant used to calculatethreshold information.

Click the down arrow toaccess the list of statistics.


Calculation mode Calculation method to use todetermine the maximumpercentage over burst andperiod threshold values.

Click the down arrow toaccess the list of the threedifferent ways of calculatingthis value.

v Standard

v Normalized

v Scaled

Calculation value Activated when you selectScaled for the Calculationmode. Value used forcalculating the percentageover or under the threshold.

Enter the number you wantto use for the calculation.

2. Click Apply.

Configuring maximum percent over for burst and periodthresholds

When configuring the burst and period thresholds, you need to enter a value thatrepresents the maximum percent over a threshold level. This section provides abrief overview of the maximum percent over calculation.

For both burst and period thresholds, the values of the maximum percent overfields (DBL_BRST_MAX_PCT_OVER and DBL_PRD_MAX_PCT_OVER) use the followingalgorithm:

MAX_PCT_OVER = 0For each metric, mi,If | mi - Lw | / Lw > MAX_PCT_OVER thenMAX_PCT_OVER = | mi - Lw | / LwIf | mi - Lc | / Lc > MAX_PCT_OVER thenMAX_PCT_OVER = |mi - Lc|/ Lc

The algorithm differs from taking the maximum value of a metric and dividing itby the most severe threshold violation. Depending on the relative values of metricsand threshold levels, it is possible that the maximum percent over is obtained froma metric that is not the largest metric value.

Configuring burst valuesAbout this task

To configure burst values, follow these steps:

Procedure1. In Static Threshold, click the Burst tab.2. Click Enabled Threshold to activate the configuration options.

Note: You can disable a threshold but retain the configuration values byclearing the Enabled Threshold box and clicking Apply. The threshold isdisabled immediately for all Tivoli Netcool Performance Manager modulesexcept the CME. For the CME, the action takes effect with the hourly reload.If you want to reuse this threshold with the same values, you click EnabledThreshold, check the values, and click Apply.


3. Enter the values you want for the burst threshold. The following table lists theconfiguration options:


Warning LevelLevel of the warningthreshold. The metric valuemust be greater than thisvalue to trigger a thresholdviolation.

Enter a double-precisionfloating point number withup to six digits to the rightof the decimal point.

Critical Level Level of the criticalthreshold. The metric valuemust be greater than thisvalue to trigger a thresholdviolation.


Event generationIndicates whether TivoliNetcool PerformanceManager must generate anevent when thresholdviolation occurs at warningand/or critical levels (if youentered a value in theWarning Level and CriticalLevel fields.)

Click the down arrow todisplay the values. Chooseyes if you want to generatean event when a thresholdviolation occurs.

Warning timeMaximum duration forexceeding Warning thresholdlevel. see “Configuringmaximum percent over forburst and period thresholds”on page 124.

Enter the number of secondsas an integer.

Critical time Maximum duration forexceeding Critical thresholdlevel. See “Configuringmaximum percent over forburst and period thresholds”on page 124.


4. Click Apply.

Configuring period valuesAbout this task

To configure period values, follow these steps:

Procedure1. In Static Threshold, click the Period tab.2. Click Enabled Threshold to activate the configuration options.

Note: You can disable a threshold but retain the configuration values byclearing the Enabled Threshold box and clicking Apply. The threshold isdisabled immediately for all Tivoli Netcool Performance Manager modulesexcept the CME. For the CME, the action takes effect with the hourly reload. Ifyou want to reuse this threshold with the same values, you click EnabledThreshold, check the values, and click Apply.


3. Enter the values you want for the period threshold. The following table lists theconfiguration options:


Warning Level Level of the warningthreshold. The metric valuemust be greater than thisvalue to trigger a thresholdviolation.


Critical Level Level of the warningthreshold. The metric valuemust be greater than thisvalue to trigger a thresholdviolation.


Event generation Indicates whether TivoliNetcool PerformanceManager should generate anevent when thresholdviolation occurs at warningand/or critical levels (if youhave entered a value in theWarning Level and CriticalLevel fields.)


Warning time Maximum duration forexceeding Warning thresholdlevel. Refer to “Configuringmaximum percent over forburst and period thresholds”on page 124.


Critical time Maximum duration forexceeding Critical thresholdlevel. Refer to “Configuringmaximum percent over forburst and period thresholds”on page 124.


Period Definition Defines the period for whichyou want thresholdviolations reported.

Click the down arrow todisplay the values. Choosethe period for which youwant threshold violationsreported. If you choose All,violations for all periods arereported.

4. Click Apply.

Configuring baseline thresholdsExplains how to configure baseline thresholds. Unlike burst and period thresholds,you do not statically define the baseline, it dynamically adapts to historical data.

About this task

To configure a baseline threshold, follow these steps:


Procedure1. From the Add Threshold window, click Baseline Threshold.2. Click Enabled Threshold to activate the configuration options.

Note: You can disable a threshold but retain the configuration values byclearing the Enabled Threshold box and clicking Apply. The threshold isdisabled immediately for all Tivoli Netcool Performance Manager modulesexcept the CME. For the CME, the action takes effect with the hourly reload. Ifyou want to reuse this threshold with the same values, you click EnabledThreshold, check the values, and click Apply.

3. Enter the values you want for the baseline. The following table lists theconfiguration options:


Max # of daysMaximum number of daysyou want to consider for thebaseline. This value must behigher than the value youenter for the minimumnumber of days.

Enter an integer of up tothree digits to indicate themaximum number of days.

Min # of days Minimum number of days ofdata required before thebaseline is calculated. Thisvalue must be less than orequal to the Maximumnumber of days.

Enter an integer of up tothree digits to indicate theminimum number of days.


CalculationIndicate which calculationmode you want to use forthe baseline.

Click the down arrow todisplay the values:

v PreviousDays: include theprevious N days from thespecified reporting periodin the calculation. Forexample:

If you specify 10 days for thereporting period of August29; the PreviousDayscalculation includes the 10previous days:

August 19, 20, 21, 22, 23, 24,25, 26, 27, and 28.

v PrevSameDay: include theN previous same days ofthe week from thespecified reporting periodin the calculation. Forexample:

If you specify 10 days for thereporting period of Friday,August 29; the PrevSameDaycalculation includes the sameday from the 10 previousweeks:

Friday June 20, Friday June27, Friday July 4, Friday, July11, Friday July 18, FridayJuly 25, Friday August 1,Friday August 8, FridayAugust 15, and FridayAugust 22.

4. Enter the values you want for the threshold. The following table lists theconfiguration options:


Sensitivity (upper)Number of standarddeviations added to themean to determine upperthreshold level.

Enter an integer withmaximum of four digits,with a maximum of twodigits to the right of thedecimal point.

Sensitivity (lower) Number of standarddeviations added to themean to determine lowerthreshold level.

Enter an integer withmaximum of four digits,with a maximum of twodigits to the right of thedecimal point.


Permitted time outsidebaseline Baseline equivalent of

duration for burst thresholds.Enter the time limit inminutes, hours, or days. Youcan use a combination ofunits such as 1 hour 25minutes.

Event generation Indicates whether TivoliNetcool PerformanceManager must generate anevent when thresholdviolation occurs.


ModeMode of the baselinethreshold.

Click the down arrow toaccess the list of values:

v Band: detect violationswhen they go outside arange (or band) betweentwo threshold values

v Over: detect violationswhen they exceedthreshold values

v Under: detect violationswhen they fall short ofthreshold values

5. Click Apply.

Trapping threshold violationsThe following sections explain how to enable Tivoli Netcool Performance Managerto do the following:v Trap threshold violations to a log file.v Trap threshold violations and send them to a specified host or hosts.

Trapping threshold violations to the log fileOnce you e configured thresholds, you can enable the trapping of thresholdviolations to the main log file, proviso.log.

About this task

To enable the trapping of threshold violations to the log file, follow these steps:

Procedure1. Open an existing Tivoli Netcool Performance Manager topology.2. Go to the Logical View.3. Browse to the Complex Metric Engine (CME) folder on the left pane as follows:

Netcool/Proviso Topology > DataChannels > DataChannel 1 > Collector 1.1 >Complex Metric Engine 1.1.

4. Go to the Properties tab on the right pane and select the LOG_TRAPSproperty.

5. Set the value to true (default is false) by selecting the check box. This enablesthe trapping of threshold violations to the log file.


6. Repeat step 2 - 4 for each threshold violations trapping you want to enable forthe DataChannels.

7. Save the topology.The following is an example of a threshold violation recorded in theproviso.log log file:2005.03.18-13.01.56 UTC CME.2.2-13969 I THRSHEVENT trap log : ProvisoViolationAutoThr 192.168.1.7 200002143::192.168.1.7-2::192.168.1.7-2_If<1001>::

Sending trapped threshold violations to specified hostsAbout this task

Once you configured thresholds, you can configure Tivoli Netcool PerformanceManager to send trapped threshold violations to specified hosts, as follows:v Send trapped threshold violations to up to five hosts at a specified port.v Include in the trap header the IP address of the element where the violation

occurred.

SNMP traps are easily managed and decoded by almost any fault managementsystem. Netcool/OMNIbus and Webtop, for example, allow a Webtop user toright-click on an alarm generated by Tivoli Netcool Performance Manager,launching the relevant Tivoli Netcool Performance Manager report.

For more information about integrating Tivoli Netcool Performance Manager withOMNIbus and Webtop, see the IBM Tivoli Netcool Performance Manager: OMNIbusWeb GUI/Webtop Integration.

To configure the sending of trapped threshold violations to specified hosts, followthese steps:

Procedure1. Open an existing Tivoli Netcool Performance Manager topology.2. Go to the Logical View.3. Browse to the Complex Metric Engine (CME) folder on the left pane as follows:

Netcool/Proviso Topology > DataChannels > DataChannel 1 > Collector 1.1 >Complex Metric Engine 1.1

4. Go to the Properties tab on the right pane and select the LOG_TRAPSproperty.

5. Specify the host name and port number combinations to receive trappedthreshold violations. For example,v localhost:162

Orv 1.1.1.1:162

6. Select the corresponding TRAP_IPADDRESS_FROM_ELEMENT property.7. The default value is set to true. This is to include in the trap header the IP

address of the element where the threshold violation originated. If thisparameter is set to false, the IP address of the CME system that sent the trapis included in the trap header.

8. Save the topology.


Chapter 9. Managing MIBs

Explains how to use the MIB compiler to compile MIBs and how to use the MIBbrowser to view MIB files and verify object values.

.A MIB file consists of object definitions that manage TCP/IP-based networks. Thevariables in a MIB are organized in groups, such as System, Interface, or TCP.

MIB groupsA MIB file contains object definitions, which are typically organized into thefollowing groups:v System Group (1)v Interface Group (2)v AT Group (3)v IP Group (4)v ICMP Group (5)v TCP Group (6)v UDP Group (7)v EGP Group (8)v CMOT Group (9)v Transmission Group (10)v SNMP Group (11)

Compiling a MIBTivoli Netcool Performance Manager DataMart includes pre-compiled MIB files.You can include additional MIB files by importing them and compiling them intothe required Tivoli Netcool Performance Manager DataMart format.

About this task

Compiling a MIB makes Tivoli Netcool Performance Manager aware of the MIBobject identifiers and their values. The compile process occurs in three phases, allof which are not apparent to the user:v Phase one creates an intermediary frozen MIB format.v Phase two creates the OID format required by Tivoli Netcool Performance

Manager DataMart.v Phase three compiles the MIB, as well as all dependant MIBs.

The results of the compilation are stored in the $PVMHOME/mibs directory in thefollowing subdirectories:v frozen

v oid

v src

Important: A MIB is compiled only when both the frozen and OID formats exist.


To compile a MIB, follow these steps:

Procedure1. On the server where DataMart is installed, enter the following command to

open the DataMart application:$PVMHONE/bin/pvm &

The DataMart application appears, as shown in the following figure:

2. Click Metric > Mib Compiler.3. In the display pane, click the MIB directory to select an entire tree or branch, or

drill-down to a specific MIB or MIBs that you want to compile.4. Optional: If the MIB you want to compile is not in the list displayed in the MIB

Compiler, you can copy it to the appropriate directory by selecting ImportFile... from the File menu.a. Go to where the MIB file is located.b. Highlight the MIB file name to select it and click Open. The file format for

a MIB is typically .mib, asn, or .txt.If you want to compile more that one MIB file, do the following:v Select a directory name to compile all MIB files in the directoryv Select several consecutive MIB files by clicking the file name for the first

MIB file, then clicking the additional names while holding down theShift key

v Select several non-consecutive MIB files by clicking each name whileholding down the Ctrl key

c. Click Yes to continue the import process. The file is copied to the specifieddirectory and the imported MIB appears in the navigation tree of MIB filesin the left display pane of the MIB Compiler.

5. To begin the compilation, click Compile. A progress indicator displays thestatus of the compilation and a message appear in the Traces pane.

Note: The Traces pane displays compilation warning messages in blue anderror messages in red.


Printing or saving trace informationProcedure1. Right-click in the Traces area to access a menu with the following options

v Reset - clears the Trace areav Save - lets you print the trace information or save it to a file.

2. Click Save.

Printing trace informationProcedure1. Select a printer from the drop down list.2. Edit the print command if you want to print in a specific format.3. Increase or decrease number of copies by clicking the up and down arrows.4. Click OK to print.

Saving trace informationProcedure1. Click the To file: option.2. Enter the path to where you want to store the file or click Browse.3. Click OK to save the information.

Deleting a MIBAbout this task

If for whatever reason you decide to delete a MIB, you can do so by followingthese steps:

Procedure1. Log on as pvuser to the system where DataMart is installed.2. Change your working directory to $PVMHOME/datamart/mibs.3. Using the rm command, delete whatever MIB files you no longer want from the

DataMart server file system.

Note: In some cases, the MIB file might be located in the src subdirectory.4. In order to permanently remove the MIB files, you must also delete them from

the database by resyncing the database with the files on disk.5. To resync the database with the MIB files on disk, enter the following

command:$PVMHOME/bin/dbRep checkin mibs -r $PVMHOME/mibs -m "*" -dodelete t

For example, if you removed the MIB agent-mib.mib from the$PVMHOME/datamart/mibs/src directory and then ran the $PVMHOME/bin/dbRepcommand, you would see output like the following:

Chapter 9. Managing MIBs 133

[[email protected]:/opt/datamart/mibs/src] rm agent-mib.mib

[[email protected]:/opt/datamart/mibs/src] dbRep checkin mibs -r$PVMHOME/mibs -m "*" -dodelete t

load cached catalog ’.catalog’ for ’/opt/datamart/mibs/’ ... ok[catalog has 2713 entrie(s)].

update catalog from disk ’/opt/datamart/mibs/’ ... ok, [catalog has2712 entrie(s)].

deleting ’src/agent-mib.mib’ in database ... ok.

save cached catalog ’.catalog’ for ’/opt/datamart/mibs/’ ... ok.

[[email protected]:/opt/datamart/mibs/src]

Viewing MIB file sourceProcedure1. Click the MIB filename in the navigation and selection pane.2. Choose View from the MIB menu to display the source. The contents of a

sample MIB file appears.3. Locate specific information by entering text in the Find text box and clicking

Forward or Backward to search through the file.4. Click Close to exit.

Browsing MIB filesYou can view a list of compiled MIB files by accessing the MIB Browser.

About this task

To access the MIB Browser, follow these steps:

Procedure1. Click Browse to open the MIB Browser.2. See “Viewing compiled MIB files” for detailed information.

Viewing compiled MIB filesThe MIB Browser lets you view a list of compiled MIB files in either tree format orin group/table format. You can then choose files from the list to review elementinformation or to verify object values.

Procedure1. Click MIB Browser in the Metric tab. The MIB Browser dialog box appears

listing compiled MIB files in tree format2. Select the Group/Table item from the Options menu to change the display. In

this format, all MIB files link directly to the iso root and are separated intoeither objects contained in groups or objects contained in tables.

Finding MIB filesYou can quickly locate a specific MIB object in the navigation and selection pane.

About this task

To find an item, follow these steps:


Procedure1. Place cursor in navigation and selection pane.2. Right-click. A menu appears.

3. Enter the object name of the item you want to find and click OK.4. If the search finds more than one item, the following dialog box appears.

5. Click the line containing item you want and click OK. The cursor moves to thatitem in the tree and the Find Choices dialog box closes.

Loading MIB filesYou can temporarily load MIB files into the MIB Browser to review elementinformation or to verify object values.

About this task

To load MIB files, follow these steps:

Procedure1. Select Load from the File menu. The MIB Selector dialog box appears.2. Click a folder to display subfolders.3. Click a subfolder to display a list of MIB files.


4. Click the name to select the MIB file and click OK. The selected MIB file, andall its dependencies, appears in the navigation and selection pane. When youexit the MIB Browser, the MIB file is removed from the display.

Viewing element informationYou can view specific element information about the MIB file.

About this task

To view element information, follow these steps:

Procedure1. Click the name of the MIB file you want to select.2. Click the Element Info tab in the MIB Browser dialog box. The information for

the selected object appears in the Element Info tab.v Name is the textual identifier of the object.v OID is the numeric identifier in dot-notation format.v Module name are the names of the modules that define the selected MIB

node. A MIB can include other MIBs, either directly or indirectly.v Syntax identifies the abstract data structure corresponding to the object type,

using ASN.1 constructs.v Access is one of the following:

– Read-only– Read-Write– Write-only– non-accessible

v Index is a list of MIB names that are used as a key in a conceptual table. Nonames appear if the MIB node does not correspond to a MIB table.

v Description is a textual description of the meaning of the object type.

Verifying object valuesIf you want to verify the values of MIB objects, you can test them directly in theMIB Browser.

Procedure1. Click the name to select a MIB file.2. Click the Test tab in the MIB Browser dialog box.3. select the type of resource from the following list.

v Element

v Element_Group

4. Choose the name of the resource you want to test from the list. If the list isblank, click Refresh to update it.The Instance and Community text boxes are populated if included as part ofthe resource name. The associated SNMP Collector automatically appears in theSNMP Collector list.

5. Select a MIB file by clicking the name in the navigation and selection pane. Thelocation of the MIB file in the tree affects what MIB files are included in therequest if:v The MIB file is located in the final section of the tree, the request is executed

on just that section.


v The MIB file is located elsewhere in the tree, the request is executed on thatsection and all sections below it in the tree. The sections can include anentire MIB set, the entire MIB, or a MIB sub-set.

6. Click Test. The Trace area displays the results of the test request.The results include:v Request parametersv MIB files selectedv Results of request

7. Right-click in the Trace area to access a menu with the following options:v Reset - clears the Trace areav Save - lets you print the trace information or save it to a file.

8. Click Save. the following dialog box appears.

Printing trace information:Procedure

1. Select a printer from the drop-down list.2. Edit the print command if you want to print in a specific format.3. Increase or decrease number of copies by clicking the up and down arrows.4. Click OK to print.

Saving trace information:Procedure

1. Click the To file: option.2. Enter the path to where you want to store the file or click Browse.3. Click OK to save the information.


Chapter 10. Editing resources

Describes how to use the Resource Editor to edit the resources.

You can perform the following tasks by using the Resource Editor:v View resource informationv Export resourcesv Import resourcesv Add resourcesv Delete resourcesv Deploy reports

For more information about managing resources from the command line, see theIBM Tivoli Netcool Performance Manager: Command Line Interface Guide.

Filtering elements and subelementsDisplay specific subsets of information by filtering the elements, subelements, andcomposite subelements in your network. Displaying all resources in the ResourceEditor can take a significant amount of time in large deployments. For largedeployments, always use the filter to avoid displaying all resources.

Procedure1. Click Resource Editor in the Resource tab. The Resource Editor window opens.2. Click the Element or Sub-Element tab in the Resource Editor.3. Click Apply Filter to display all resources on your network. To filter the results

to display specific resources, enter a unique value in any of the columnheadings then click Apply Filter. Use the following syntax to create your filters:

Filter Result

string Displays all results that match the value ofstring.

string* Displays all results that match the prefixvalue of string.

*string Displays all results that match the suffixvalue of string.

*string* Displays all results that contain the value ofstring.

!='string' Displays all results that have values otherthan the value of string.

is null Displays all results that have no valuedefined.

not null Displays all results that have any valuedefined.


Viewing resource informationExplains how to view information about elements, subelements, subelementgroups, and element and subelement properties.

Displaying all resources in the Resource Editor can take a significant amount oftime in large deployments. For large deployments, always use the filter to avoiddisplaying all resources.

Viewing elementsProcedure1. Click the Element tab in the Resource Editor.2. Click Apply Filter to view all elements in the database, or enter filter

information to limit the number of results. The following information isdisplayed.

Note: Both IPv4 and IPv6 address formats are supported.

Column Name Description

NameDisplays the name of the element.

ProfileDisplays the name of the inventory profileused to discover this element. For moreinformation, see the IBM Tivoli NetcoolPerformance Manager: Installation Guide.

CollectorDisplays the collector number assigned tothis element.

DescriptionDisplays a descriptive textual name for theelement.

TypeDisplays the type of the element:

snmp Defines an element for SNMPcollections.

default_snmpUsed for SnmpConf.

star_snmpUsed for SnmpConf (@IPrange).

import Defines a host with imported data.No SNMP collections are available.

OriginDisplays the method used to add theelement to the database.

StateDisplays the state of the element:

on Indicates that the element is visiblein the graphical user interface.

off Indicates that data collection on theelement is stopped and that theelement is no longer visible in thegraphical user interface.


Viewing subelementsProcedure1. Click the Sub-Element tab in the Resource Editor.2. Click Apply Filter to view all subelements or composite subelements in the

database, or enter filter information to limit the number of results. Thefollowing information is displayed:


NameDisplays the name of the subelement orcomposite subelement.

DateDisplays the date for the subelement orcomposite subelement.

Label Displays a descriptive comment for thesubelement or composite subelement.

ProfileDisplays the name of the inventory profileused to discover the subelement orcomposite subelement. For moreinformation, see the IBM Tivoli NetcoolPerformance Manager: Installation Guide.

FamilyDisplays the name of the family for thesubelement or composite subelement.

ElementDisplays the name of the element for thesubelement or composite subelement.

InstanceDisplays the name of the instance for thesubelement or composite subelement.

Viewing subelement groupsProcedure1. Click the Sub-Element Group tab in the Resource Editor.2. Click a subelement or composite subelement group folder to expand it.3. Select a subelement or composite subelement group name to display the

elements it contains in the right pane. The following information is displayed:


NameDisplays the name of the subelement orcomposite subelement.

Label Displays a descriptive comment for thesubelement or composite subelement.

FamilyDisplays the name of the family for thesubelement or composite subelement.

Element Displays the name of the element for thesubelement or composite subelement.

Chapter 10. Editing resources 141


InstanceDisplays the name of the instance for thesubelement or composite subelement.

Type The type of the group member. Possiblevalues are GROUP, SE, or CSE.

RelationThe relation of each group member.Particularly important for compositesubelements.

NameThe name of the group member.

LabelThe label of the group member.

Viewing property detailsProcedure1. Click the Element or the Sub-Element tab in the Resource Editor.2. Click Apply Filter to view all resources in the database, or enter filter

information to limit the number of results.3. Locate an element, subelement, or composite subelement by scrolling through

the list, or click the magnifying glass icon to open the Find dialog box.4. Highlight the element, subelement, or composite subelement and click Detail.

The Properties, Relation To, and Relation From tabs are displayed.5. Optional: To hide the details, click Detail again.

Property detailsThe Detail tabs provide these information:

PropertiesThe properties and values associated with the selected subelement orcomposite subelement.

Relation ToThe source subelements or composite subelements to which the selectedcomposite subelement is linked. The Relation To tab contains:

RelationThe relationship between the selected composite subelement andeach of the source subelements or composite subelements. Arelation can be any string.

ResourceThe source subelement or composite subelement.

Relation FromThe destination subelements or composite subelements for the selectedcomposite subelement and the relationship between them. The RelationFrom tab contains

RelationThe relationship between the selected composite subelement andeach of the destination subelements or composite subelements. Arelation can be any string.


ResourceThe destination subelement or composite subelement.

Viewing reportsProcedure1. Click the Report tab in the Resource Editor.2. Click Apply Filter to view all reports in the database, or enter filter information

to limit the number of results. The following information is displayed:


Name Displays the name of the report.

URL Displays the universal resource locator forthe report.

Type Displays the type of the report.

Comment Displays comments on the report.

Viewing thresholdsProcedure1. Click the Threshold tab in the Resource Editor.2. Click Apply Filter to view all thresholds in the database, or enter filter

information to limit the number of results. The following columns aredisplayed:


Metric Formula Metric

Group Group Name

Resource Resource Name

isBrst Burst Type Violation

isPrd Period Type Violation

isBl Baseline Threshold Type Violation

Mode Threshold mode (Under, Over, or band)

Date Date

Stat Statistic mode (raw, min, max, avg, sum,count)

Calc Calculation mode (Standard, Normalized,Scale)

CalcVal Threshold value (for Calculation Scale)

BCrtL Burst Critical Level

BCrtT Burst Critical Time

BWrnL Burst Warning Level

BWrnT Burst Warning Time

BEvent Burst Event Generation

PCrtL Period Critical Level

PCrtT Period Critical Time

PWrnL Period Warning Level



PWnrT Period Time

PEvent Period Event Generation

PDef Period Definition

MaxNbDay Baseline Threshold Maximum Number ofDays

MinNbDay Baseline Threshold Minimum Number ofDays

blCalcMode Baseline Calculation Mode (Previous Days,Previous Same Day of Week)

blMode Baseline Threshold Mode (Under, Over,Band)

blTime Baseline Threshold Time Limit

blTrap Baseline Threshold Event Generation (No,Yes)

blUpper Baseline Threshold Upper Limit

blLower Baseline Threshold Lower Limit

Exporting resourcesExplains how to export resources for use with another Tivoli Netcool PerformanceManager DataMart installation. You can export elements, subelements, compositesubelements, and subelement groups. Displaying all resources in the ResourceEditor can take a significant amount of time in large deployments. For largedeployments, always use the filter to avoid displaying all resources.

About this task

To export resources, follow these steps:

Procedure1. Click the Element, Sub-Element, or Sub-Element Group tab in the Resource

Editor.2. Click Apply Filter to view all resources in the database, or enter filter

information to limit the number of results.3. Select the resources to export and choose Export from the File menu. The

resources available for exporting are displayed according to their filters.4. Click Folder to specify the destination location for the export files.5. Enter a name for the export file in the File name text box. The file name

extension is .elt for elements,.se for subelements, and .segp for subelementgroups.

6. Click Save to export the file. A message box displays when the export processcompletes.

7. Click Close.


Importing resourcesExplains how to import elements, subelements, composite subelements, andsubelement groups. The file name extensions differ depending on the resource youare importing. Displaying all resources in the Resource Editor can take a significantamount of time in large deployments. For large deployments, always use the filterto avoid displaying all resources.

About this task

To import elements or subelements, follow these steps:

Procedure1. Click the Element tab or the Sub-Element tab.2. Click Apply Filter to view all elements or subelements in the database, or enter

filter information to limit the number of results.3. Select Import from the File menu. The Import dialog box displays.4. Click Folder to specify the source location for the import files. The file name

extension is.elt for elements, .se for subelements, and .segp for subelementgroups.

5. Click Open to import the file.6. Click Details to view a detailed status on the import procedure. A message box

opens when the import process completes.7. Click Close.

Adding resourcesExplains how to add elements, subelements, reports, and thresholds.


Adding elementsProcedure1. Click the Element tab.2. Click Apply Filter to view all elements in the database, or enter filter

information to limit the number of results.3. Click an element name as a base for the new element.4. Select Add from the Edit menu or right-click the element name and select Add

from the menu. The Add Element dialog box opens.5. Enter the following information for the new element:

Field Description

Name Specifies the name of the element.

Profile Select the name of the inventory profile usedto discover this element. For moreinformation, see the IBM Tivoli NetcoolPerformance Manager: Installation Guide.

Collector Select the collector number assigned to thiselement.


Field Description

sysDesc Select a descriptive textual name for theelement.

TypeSelect the type of the element:





CommentSpecifies descriptive comments about theelement.

6. Click OK to accept your changes.7. Click Close to exit the message box.

Adding subelementsProcedure1. Click the Sub-Element tab.2. Click Apply Filter to view all subelements and composite subelements in the

database, or enter filter information to limit the number of results.3. Click a subelement or composite subelement name.4. Select Add from the Edit menu or right-click the element name and select Add

from the menu. The Add Sub-Element dialog box opens.5. Enter the following information for the new subelement:

Field Description

Name Specifies the name of the subelement orcomposite subelement.

Label Specifies a descriptive comment for thesubelement or composite subelement.

Family Select the name of the family for thesubelement or composite subelement.

Element Specifies the name of the element for thesubelement or composite subelement.

Instance Specifies the name of the instance for thesubelement or composite subelement.

Invariant Specifies the invariant entity associated withthe subelement or composite subelement.



Adding composite subelement relationsProcedure1. Click the Sub-Element tab.2. Click Apply Filter to view all subelements in the database, or enter filter

information to limit the number of results.3. Click a composite subelement name.4. Click Detail to display the list of properties associated with the selected

composite subelement.5. Click Relation To or Relation From tab to display the relation information.6. Select Add from the Edit menu or right-click the element name and select Add

from the menu. The Add Sub-Element dialog box opens.7. Enter the following information for the new subelement or composite

subelement:

Field Description

RelationSpecifies the name of the subelement orcomposite subelement relation.

NameSpecifies the name of the subelement orcomposite subelement.


ElementSpecifies the name of the element for thesubelement or composite subelement.

InstanceSpecifies the name of the instance for thesubelement or composite subelement.

InvariantSpecifies the invariant entity associated withthe subelement or composite subelement.

FamilySelect the name of the family for thesubelement or composite subelement.


Adding reportsProcedure1. Click the Report tab.2. Click Apply Filter to view all reports in the database, or enter filter information

to limit the number of results.3. Click a report name.4. Select Add from the Edit menu or right-click the report name and select Add

from the menu. The Add Report dialog box opens.5. Enter the following information for the new report:

Field Description

Name Specifies the name of the report.


Field Description

URL Specifies the universal resource locator forthe report.

Type Select the type of the report.

Data Specifies the data displayed in the report.

Comment Specifies comments on the report.


Adding thresholdsExplains how to add new thresholds. A threshold is a value that is comparedagainst metrics to determine if the metrics exceed or drop below a critical limit.Results appear in Tivoli Netcool Performance Manager DataView reports. Youmust enter values in several tabs to create a valid threshold.

About this task

Before you can add a threshold, you need to set thresholds. For more information,see IBM Tivoli Netcool Performance Manager: Command Line Interface Guide .

Adding resource and metric threshold parametersProcedure1. Click the Threshold tab.2. Click Apply Filter to view all thresholds in the database, or enter filter

information to limit the number of results.3. Click a threshold name.4. Select Add from the Edit menu or right-click the threshold name and select

Add from the menu. The Add Threshold dialog box opens.5. Enter the following information for the new threshold:

Field Description

Metric Specifies the formula name associated withthe threshold.

Group Specifies the subelement group associatedwith the threshold.

Sub-ElementSpecifies the subelement name associatedwith the threshold.

6. Click OK to accept your changes.

Adding threshold mode parametersProcedure1. Click the Threshold tab.2. Click Apply Filter to view all thresholds in the database, or enter filter


Add from the menu. The Add Threshold dialog box opens.5. Click the Static Threshold tab.


6. Click the Mode tab. Enter the following information for the new threshold:

Field Description

Effective date Specifies the effective date of action for thethreshold. Setting the date in the past doesnot cause reprocessing of data but mightcause thresholds to display on reports.

ModeSelect a threshold mode for the thresholdfrom the following:

Under Violation if data value belowthreshold value (either warning orcritical).

Over Violation is data value is overthreshold value (either warning orcritical).

band Violation if data is not between thevalues.

Statistic modeSelect a statistic mode for the threshold fromthe following:

raw Raw data from collectors.

min, max, avg, sum, countData from aggregations.

Calculation mode Select a calculation mode for the thresholdfrom either Standard, Normalized, or Scaled.

Calculation value Specifies the calculation value for thethreshold if you selected Scaled as theCalculation mode.


Adding threshold burst parametersA burst threshold removes the natural network bursts by evaluating how manytimes in a row the violations occurred over a certain period of time.

Procedure1. Click the Threshold tab.2. Click Apply Filter to view all thresholds in the database, or enter filter


Add from the menu. The Add Threshold dialog box opens.5. Click the Static Threshold tab.6. Click the Burst tab.7. Select the Enable Threshold check box.8. Enter the following information for the new threshold:

Field Description

Warning level Specifies the level of the warning thresholdfor BURST thresholds. NULL indicates thatthe threshold is not defined.


Field Description

Critical level Specifies the level of the critical thresholdfor BURST thresholds. NULL indicates thatthe threshold is not defined.

Event generation Select whether to generate events for theBURST threshold.

Warning time Specifies the time limit (in seconds) forwarning BURST thresholds. NULL indicatesthat the threshold is not defined. "0s"indicates that the threshold is violated whenthe metric exceeds the threshold. Forexample, the input format: 1d 2h 3m 4sequals a duration of 1 day, 2 hours, 3minutes, and 4 seconds.

Critical time Specifies the time limit (in seconds) forcritical BURST thresholds. NULL indicatesthat the threshold is not defined. "0s"indicates that the threshold is violated whenthe metric exceeds the threshold. Forexample, the input format: 1d 2h 3m 4sequals a duration of 1 day, 2 hours, 3minutes, and 4 seconds.


Adding threshold period parametersA period threshold involved the concept of duration for which the threshold isviolated. This duration is accumulated until the end of the expected service levelperiod.



Add from the menu. The Add Threshold dialog box opens.5. Click the Static Threshold tab.6. Click the Period tab.7. Select the Enable Threshold check box.8. Enter the following information for the new threshold:

Field Description

Warning level Specifies the level of the warning thresholdfor PERIOD thresholds. NULL indicates thatthe threshold is not defined.

Critical level Specifies the level of the critical thresholdfor PERIOD thresholds. NULL indicates thatthe threshold is not defined.

Event generation Select whether to generate events for thePERIOD threshold.


Field Description

Warning time Specifies the time limit (in seconds) forwarning PERIOD thresholds. NULLindicates that the threshold is not defined."0s" indicates that the threshold is violatedwhen the metric exceeds the threshold. Forexample, the input format: 1d 2h 3m 4sequals a duration of 1 day, 2 hours, 3minutes, and 4 seconds.

Critical time Specifies the time limit (in seconds) forcritical PERIOD thresholds. NULL indicatesthat the threshold is not defined. "0s"indicates that the threshold is violated whenthe metric exceeds the threshold. Forexample, the input format: 1d 2h 3m 4sequals a duration of 1 day, 2 hours, 3minutes, and 4 seconds.

Period Definition Select a period definition for the thresholdas either Day, Week, Month, or All. Allperiod indicates that the Complex MetricsEngine (CME) uses the period of theaggregation tables.


Adding baseline threshold parametersProcedure1. Click the Threshold tab.2. Click Apply Filter to view all thresholds in the database, or enter filter


Add from the menu. The Add Threshold dialog box opens.5. Click the Baseline Threshold tab.6. Select the Enable Threshold check box.7. Enter the following information for the new threshold:

Field Description

Max # of daysSpecifies the maximum number of days usedto calculate the baseline threshold.

Min # of daysSpecifies the minimum number of days usedto calculate the baseline threshold.

Calculation Select the baseline calculation mode fromeither PreviousDays orPrevSameDayofWeek.

Sensitivity (upper)Enter the upper threshold limit (number ofstandard deviations above the baseline) thatmust be violated before generating an event.


Field Description

Sensitivity (lower)Enter the lower threshold limit (number ofstandard deviations below the baseline) thatmust be violated before generating an event.

Permitted time outside baselineEnter the time limit (in minutes, hours, ordays) that a threshold can be violated beforegenerating an event.

Event generationSelect whether to generate events forbaseline threshold violations.

ModeSelect a violation mode for the thresholdfrom the following:

Under Violation if data value belowthreshold value.

Over Violation is data value is overthreshold value.

band Violation if data is not between thevalues.


Creating a propertyAbout this task


To create a new property, follow these steps:

Procedure1. Click the Sub-Element tab.2. Click Apply Filter to view all subelements in the database, or enter filter

information to limit the number of results.3. Select a subelement from the list.4. Select Add Property from the Edit menu. The Add Property dialog box opens.5. Select a name for the property in the Name field. See “Property names” for a

description of property names.6. Enter a value for the property in the Value field.7. Click OK to accept your entries.

Property namesProperties are the attributes or characteristics of an element or subelement thatdefines its state, appearance, or value. These properties are installed by TivoliNetcool Performance Manager Technology Packs. Property names for elements,subelements and report users are listed in the following tables.

The Complex Metrics Engine (CME) uses numeric properties in calculations withraw data or other complex metrics. The CME determines which properties arerequired and loads them from the database at startup. The properties are kept in


CME memory. When a property value changes in the database, the CME obtainsthe new value from the next database load.

Table 8. Subelement Properties

Property Description

hostnameA user-defined name assigned to the hostupon which this resource resides. Providedduring network configuration.

descriptionOpen-format description text used forgrouping.

nameA user-defined name that is user-defined forthis entity during network configuration.This name is used only for grouping (it isnot supported by DM or DV as a SE label).

hostIPPhysical IP address of the host upon whichthis resource resides.

networkAreaNetwork area (for example, BackBone, CPE)of the entity.

typeOpen-format name of the specific type ofresource represented (for example, Ethernet,DS1).

physicalCapacityThe maximum speed of this resource (bps).

hosturlURL address assigned to the host uponwhich a resource resides.

parentOpen-format name or ID assigned to anentity, other than a physical host (see'hostName' Property), that can be consideredas a "parent" containing this resource.

hostTypeOpen-format "type" classification of thedevice upon which this resource resides.

parentTypeOpen-format type classification of the parentof this resource.

classOpen-format name of the general class ofresource represented (for example, device,interface, logical port, or end-to-endconnection).

subTypeIf needed, more specific type information orthe resource (NNI, UNI).

protocolTransmission protocol specific to theresource (ATM, Frame Relay, IP, IPSec, TCP,UDP, MPLS).


Table 8. Subelement Properties (continued)

protocolVersionVersion of transmission protocol being used.

modelOpen-format model name of the resource.

modelIDOpen-format model ID string of theresource.

versionOpen-format version identification of theresource.

patch levelOpen-format patch level identification of theresource.

countryThe country in which the resource resides.

cityThe city, town, or municipality in which theresource resides.

stateThe state in which the resource resides.

provinceThe province in which the resource resides.

regionOpen-format region name in which theresource resides.

regionIDOpen-format ID string assigned to theregion in which the resource resides.

locationOpen-format physical location name inwhich the resource resides.

locationIDOpen-format ID string assigned to thephysical location in which the resourceresides.

statusOperational status of the resource (active,initializing, maintenance).

priorityOpen-format priority name or code.

committedCapacityThe steady-rate bandwidth (bps) committedfor transfer over a resource.

committedBurstCapacityThe transmission rate (bps) committed forshort traffic bursts (for a pre-agreedduration) over a resource.

committedPeakCapacityThe maximum transmission rate committedfor transfer over this resource.

ownerService provider employee name/ID towhich this resource belongs.



ownerCustomTagUser-definable property for custom resourceorganization attributes.

departmentService provider department to which aresource belongs.

departmentIDID of the service provider department towhich a resource belongs.

networkThe name of the network of which aresource is a part.

networkIDThe ID of the network of which a resource isa part.

privateNetworkThe name of the private (virtual) network ofwhich this entity is a part.

privateNetworkID The ID of the private (virtual) network ofwhich this entity is a part.

customerThe name of the specific customer that aresource services.

customerIDThe ID of the specific customer that thisresource services.

customerTypeThe type of customer that a resourceservices.

customerFacingName Alternate name to be used for this resourcein customer-facing reports, and messages.

securityProfileMaskOpen-format string for definition of a textmask which can be generated for SEs by acustom user group control system and usedwithin rule conditions to organize usergroups' access to resource views.

operationFor monitor probes, such as RMON. The testoperation being executed.

timeoutFor monitor probes, such as RMON. Thetimeout duration (seconds) for targetresponse.

sourceIP For unidirectional entities (end-to-endsimplex connections, network test probes).The IP address of the originating side.

sourceURL For unidirectional entities (end-to-endsimplex connections, network test probes)the URL of the originating side.

sourcePortFor unidirectional entities (end-to-endsimplex connections, network test probes).The IP port used on the originating side.



destIPFor unidirectional entities (end-to-endsimplex connections, network test probes).The IP address of the terminating side.

destURLFor unidirectional entities (end-to-endsimplex connections, network test probes).The URL of the terminating side.

destPortFor unidirectional entities (end-to-endsimplex connections, network test probes).The IP port used on the terminating side.

corbaPortThe number identifying the CORBA portthis entity uses.

targetDirectoryFile system directory to which this entitydelivers processed data.

pathDirectory path within which this entityresides.

tablespace Name of the table space in which this tableresides.

tablespaceClass Aggregation characteristics of the table spaceof which this table is part. For raw data:NRAW. For resource aggregations"1{D,WM}RA. For group aggregations:1{D,W,M}GA.

aggregationSet Timezone applied to this entity.

channelID of the Tivoli Netcool PerformanceManager channel of which this entity is part.

channelTableSetTypeType of Channel Table Set of which thistable is part: Current-"H0"; Recent-"H1";Ancient-"H2"; Current to RecentStaging-"S0"; Recent to Ancient Staging-"S1"

measurementIntervalThe duration of time (seconds) over whichraw statistics from this resource arecomputed and possibly pre-aggregated bythat resource or by an intermediatemanagement system. This property also canbe used in network monitoring probeimplementations to represent the configuredamount of time wait between probe testexecutions.



measurementSubIntervalThe duration of time (seconds) over whichraw statistics from this resource aresubaggregated intra-period (for example, forpeak values within the overall measurementinterval). Also can be used to represent theduration that multi-sample network probeswait between each resend within a singleprobe execution.

Table 9. DataView User Properties

Property Description

DV_UserTimeZone Defines the default time zone to be used forthe user whenever a group that has not beenassigned it's own time zone is viewed in theportal.

DV_UserShowCurrentPeriodControls access to active-period reportviewing. If undefined or set to "true:", theuser is allowed to view reports for thecurrent, active, time period. If set to "false",the user cannot view reports for the currentperiod.

DV_UserProfileDefines the general user type for control ofcertain security options. Valid settingsinclude the following:

v NOC - Network Operations Center user,few restrictions.

v PSLA - Proactive Service Level Agreementpersonnel, moderate restriction.

v SLA - users, highest restrictiveness.

DV_UserResourceNameDefines which subelement name definitionsmust be used for SE labels displayed to theparticular user. Valid settings include thefollowing:

v 1 - Use the SEs' internal ALIAS fieldvalues (also dubbed "SE Labels").

v 2 - Use the SEs' internal NAME fieldvalues.

v 1771 - Use the value defined in the"customerFacingName" Property for eachSE.

DV_UserLoginNameDataView user-scope property that can beset with the login name attributed to aDataView user. This property is used forinformational display on reporter summaryheadings only.

DV_UserNameDataView user-scope property that can beset with the name attributed to a DataViewuser. This property is used for informationaldisplay on reporter summary headings only.


Table 9. DataView User Properties (continued)

DV_UserCustomLogoFileDataView user-scope property that can beset with a link to an image file staticallydefining a custom graphic to be displayedon reporter summary headings.

Modifying resourcesExplains how to modify elements, subelements, reports, and thresholds by usingResource Editor.

Note: Displaying all resources in the Resource Editor can take a significant amountof time in large deployments. For large deployments, always use the filter to avoiddisplaying all resources.

Modifying an elementProcedure1. Click the Element tab.2. Click Apply Filter to view all elements in the database, or enter filter

information to limit the number of results.3. Click an element name that you want to modify.4. Select Update from the Edit menu or right click the element name and select

Update from the popup menu. The Update Element dialog box opens.5. Change the following information for the element:

Field Description

Name Specifies the name of the element.

Profile Select the name of the inventory profile usedto discover this element. For moreinformation, see the IBM Tivoli NetcoolPerformance Manager: Installation Guide.

Collector Select the collector number assigned to thiselement.

sysDesc Select a descriptive textual name for theelement.

Type Select the type of the element:





Comment Specifies descriptive comments about theelement.


Field Description

StateSelect the state of the element:

on Indicates that the element is visiblein the graphical user interface.

off Indicates that data collection on theelement is stopped and that theelement is no longer visible in thegraphical user interface.

Origin Specifies the method used to add theelement to the database.

User Specifies the user who created the element.

Date Specifies when the element was created ormodified.

6. Click OK to accept your modifications.

Modifying a subelementAbout this task

To modify a subelement or composite subelement, follow these steps:

Procedure1. Click the subelement tab.2. Click Apply Filter to view all subelements and composite subelements in the

database, or enter filter information to limit the number of results.3. Click the name of the subelement or composite subelement that you want to

modify.4. Select Update from the Edit menu or right click the element name and select

Update. The Update subelement dialog box opens.5. Update the following information:

Field Description

Name Specifies the name of the subelement orcomposite subelement.


Element Specifies the name of the element for thesubelement or composite subelement.

Instance Specifies the name of the instance for thesubelement or composite subelement.

Invariant Specifies the invariant entity associated withthe subelement or composite subelement.

Family Displays the name of the family for thesubelement or composite subelement.


Field Description

StateSelect the state of the subelement orcomposite subelement:

on the subelement or compositesubelement is visible in thegraphical user interface.

off data collection on the subelementor composite subelement is stoppedand that the element is no longervisible in the graphical userinterface.

Origin Specifies the method used to add thesubelement or composite subelement to thedatabase.

User Specifies the user who created thesubelement or composite subelement.

Date Specifies when the subelement was createdor modified or composite subelement.


Modifying a reportProcedure1. Click the Report tab.2. Click Apply Filter to view all reports in the database, or enter filter information

to limit the number of results.3. Click a report name that you want to modify.4. Select Update from the Edit menu or right-click the element name and select

Update from the menu. The Update Report dialog box opens.5. Enter the following information for the new report:

Field Description

Name Specifies the name of the report.

URL Specifies the universal resource locator forthe report.

TypeSelect the type of the report.

DataSpecifies the data displayed in the report.

Comment Specifies comments on the report.



Modifying ThresholdsAbout this task

Resources and Metrics


information to limit the number of results.3. Click a threshold name that you want to modify.4. Select Update from the Edit menu or right-click the threshold name and select

Update from the popup menu. The Add Threshold dialog box opens. Changethe following information for the threshold:

Field Description

Metric Specifies the formula name associated withthe threshold.

Group Specifies the subelement group associatedwith the threshold.

Sub-ElementSpecifies the subelement name associatedwith the threshold.


ModeAbout this task

The following thresholds are static thresholds:v Modev Burstv Periodv Baseline



Update from the menu.5. Click the Static Threshold tab.6. Click the Mode tab.

The Add Threshold dialog box opens.Change the following information for the threshold:


Field Description

Effective dateSpecifies the effective date of action for thethreshold. Setting the date in the past willnot cause re-processing of data but maycause thresholds to display on reports.

ModeSelect a threshold mode for the thresholdfrom the following:

v Under - Violation if data value belowthreshold value (either warning orcritical).

v Over - Violation is data value is overthreshold value (either warning orcritical).

v band - Violation if data is not between thevalues.

Statistic modeSelect a statistic mode for the threshold fromthe following:

v raw - Raw data from collectors.

v min, max, avg, sum, count - Data fromaggregations.

Calculation modeSelect a calculation mode for the thresholdfrom either Standard, Normalized, or Scaled.

Calculation valueSpecifies the calculation value for thethreshold if you selected Scaled as theCalculation mode.


BurstAbout this task

A burst threshold removes the natural network bursts by evaluating how manytimes in a row the violations occurred over a certain period of time.

To modify threshold burst parameters, follow these steps:



Update from the menu.5. Click the Static Threshold tab.6. Click the Burst tab.



Field Description

Warning levelSpecifies the level of the warning thresholdfor BURST thresholds. NULL indicates thatthe threshold is not defined.

Critical levelSpecifies the level of the critical thresholdfor BURST thresholds. NULL indicates thatthe threshold is not defined.

Event generation Select whether to generate events for theBURST threshold.

Warning timeSpecifies the time limit (in seconds) forwarning BURST thresholds. NULL indicatesthat the threshold is not defined. "0s"indicates that the threshold is violated whenthe metric exceeds the threshold. Forexample, the input format: 1d 2h 3m 4sequals a duration of 1 day, 2 hours, 3minutes, and 4 seconds.

Critical timeSpecifies the time limit (in seconds) forcritical BURST thresholds. NULL indicatesthat the threshold is not defined. "0s"indicates that the threshold is violated whenthe metric exceeds the threshold. Forexample, the input format: 1d 2h 3m 4sequals a duration of 1 day, 2 hours, 3minutes, and 4 seconds.


PeriodAbout this task

A period threshold involved the concept of duration for which the threshold isviolated. This duration is accumulated until the end of the expected service levelperiod.

To modify threshold burst parameters, follow these steps:



Update from the menu.5. Click the Static Threshold tab.6. Click the Period tab.



Field Description

Warning level Specifies the level of the warning thresholdfor PERIOD thresholds. NULL indicates thatthe threshold is not defined.

Critical levelSpecifies the level of the critical thresholdfor PERIOD thresholds. NULL indicates thatthe threshold is not defined.

Event generation Select whether to generate events for thePERIOD threshold.

Warning timeSpecifies the time limit (in seconds) forwarning PERIOD thresholds. NULLindicates that the threshold is not defined."0s" indicates that the threshold is violatedwhen the metric exceeds the threshold. Forexample, the input format: 1d 2h 3m 4sequals a duration of 1 day, 2 hours, 3minutes, and 4 seconds.

Critical timeSpecifies the time limit (in seconds) forcritical PERIOD thresholds. NULL indicatesthat the threshold is not defined. "0s"indicates that the threshold is violated whenthe metric exceeds the threshold. Forexample, the input format: 1d 2h 3m 4sequals a duration of 1 day, 2 hours, 3minutes, and 4 seconds.

Period DefinitionSelect a period definition for the thresholdas either Day, Week, Month, or All. Allperiod indicates that the Complex MetricsEngine (CME) uses the period of theaggregation tables.


Baseline ThresholdAbout this task

To modify baseline threshold parameters, follow these steps:



Update from the menu.5. Click the Static Threshold tab.6. Click the Baseline Threshold tab.



Field Description

Max # of days Specifies the maximum number of days usedto calculate the baseline threshold.

Min # of daysSpecifies the minimum number of days usedto calculate the baseline threshold.

Calculation Select the baseline calculation mode fromeither PreviousDays orPrevSameDayofWeek.

Sensitivity (upper)Enter the upper threshold limit (number ofstandard deviations above the baseline) thatmust be violated before generating an event.

Sensitivity (lower)Enter the lower threshold limit (number ofstandard deviations below the baseline) thatmust be violated before generating an event.

Permitted time outside baselineEnter the time limit (in minutes, hours, ordays) that a threshold can be violated beforegenerating an event.

Event generationSelect whether to generate events forbaseline threshold violations.

ModeSelect a violation mode for the thresholdfrom the following:

v Under - Violation if data value belowthreshold value.

v Over - Violation is data value is overthreshold value.

v band - Violation if data is not between thevalues.


Deleting resourcesExplains how to delete the following resources from the database:v Elements and subelementsv Sub-element groupsv subelements within groupsv Properties associated with elements and subelements

Note: When you delete an element, you delete the associated subelements. Whenyou delete a property, you delete only the property. Displaying all resources in theResource Editor can take a significant amount of time in large deployments. Forlarge deployments, always use the filter to avoid displaying all resources.


Deleting elements or subelementsProcedure1. Click the Element or the Sub-Element tab.2. Click Apply Filter to view all resources in the database, or enter filter

information to limit the number of results.3. Click the resource names you want to delete.4. Click the Delete icon in the toolbar. A confirmation message opens.5. Click Yes to continue, or No to cancel.

Deleting subelement groupsProcedure1. Click the Sub-Element Group tab in Resource Editor.2. Click the subelement group to expand it and select the name of the group. The

subelements contained in the group appear in the right pane.3. Click the Delete icon in the toolbar. A confirmation message opens.4. Click Yes to continue, or No to cancel.

Deleting resources within groupsProcedure1. Click the Sub-Element Group tab in the Resource Editor.2. Click the Sub-Element group name to expand it.3. Click the group name in the left pane to display the subelements in the right

pane.4. Click a resource name to select it, or click the magnifying glass icon to open the

Find dialog box to search by name.5. Click the Delete icon in the toolbar. A confirmation message opens.6. Click Yes to delete the resource, or No to cancel.

Deleting propertiesProcedure1. Click the Element or Sub-Element tab in the Resource Editor.2. Click Apply Filter to view all resources in the database, or enter filter

information to limit the number of results.3. Select a resource whose properties you want to delete.4. Click Detail to display the properties table.5. Click the property name you want to delete.6. Click the Delete icon in the toolbar. A confirmation message opens.7. Click Yes to delete, or No to cancel.


Deleting composite Subelement relationsProcedure1. Click the Sub-Element tab.2. Click Apply Filter to view all subelements in the database, or enter filter

information to limit the number of results.3. Click a composite subelement name.4. Click Detail to display the list of properties associated with the selected

composite subelement.5. Click Relation To or Relation From tab to display the relation information.6. Right-click a relation in the list and select Delete.7. Click Yes to confirm your choice.

Deploying reportsExplains how to manually deploy reports using Resource Editor.

Procedure1. Click the Report tab.2. Click Apply Filter to view all reports in the database, or enter filter

information to limit the number of results.3. Click the Report SE Group tab.4. Expand a group to view a list of the rules applied to and select a rule to

display any reports currently deployed against it.5. Click the Report tab to display the list of reports again.6. Click the report name you want to deploy to highlight it.7. Copy the report by pressing Ctrl + C.8. Click the Report SE Group tab to select it again.9. Click the group name in the left pane to highlight it.

10. Press Ctrl + V to paste the report into the frame. You are prompted toconfirm your choice.

11. Click Yes to continue. The copied report displays in the right pane.12. Move the cursor to the left pane and scroll up to select SUB-ELEMENTS.13. Right-click and select AutoGrouping from the pull down menu. A

confirmation prompt opens.14. Click Yes to continue.15. Click Close to exit the message box or click Details to view a description of

any errors or warnings.


Chapter 11. Viewing collected data

Explains how to view various collected data.

Viewing graphical charts for filesExplains how to view a list of curves contained in a file, which you can thendisplay in graphical form.

About this task

To view curves, follow these steps:

Procedure1. Click Data Viewer in the Data Manager tab. The following windows appears:

The foreground window lets you select data to display. The backgroundwindow displays the data in graphical form.

2. Select a file from the upper list. A list of curves appear in the bottom list.3. Select one or more curves that you want to display in graphical form.4. Click Apply to accept your selections.


Viewing graphical charts for subelementsExplains how to view graphical charts for subelements.

About this task

To view graphical charts for subelements, follow these steps:

Procedure1. Click Data Viewer in the Data Manager tab.2. Click the Sub-elements tab.3. Click Apply Filter to view all subelement names in the left pane, or enter

filter information to limit the number of results.

Note: You can sort columns by clicking on the column titles.4. Select one or more subelements from the list in the left pane. Use the Ctrl key

to make multiple selections.5. Select one or more associated formulas from the list in the right pane.6. Select a time range in the Data Range Selection group from the following:

Current - Selects currently collected data.Recent - Select most recent collected data.History - Select historical data.

7. Select a data type in the Data Type group from the following:Raw - Provides raw collected data.Min - Provides minimum values of the raw data according to theaggregation type that you select.Max - Provides maximum values of the raw data according to theaggregation type that you select.Sum - Provides the sum of the raw data according to the aggregation typeyou select.Count - Provides the number of raw data according to the aggregationtype you select.

8. Select an aggregation type in the Aggregation type list from the following:Per day - Aggregations per dayPer week - Aggregations per weekPer month - Aggregations per month

9. Select an aggregation set in the Aggregations Set list from the following:GMT - Greenwich Mean Time, which is the mean solar time of themeridian of Greenwich used as the prime basis of standard timethroughout the world.AggSet 1 to AggSet 6 - An Aggregation Set defines an offset from GMTand is associated with groups. This feature can have a different name ifcustomized.

10. Click Apply to accept your selections.One or more graphical charts appear in the Data Viewer window.

What to do next

See the next sections to save, print, and configure graphs.


Viewing graphical charts for subelement groupsExplains how to view graphical charts for subelements groups.

Procedure1. Click Data Viewer in the Data Manager tab.2. Click the Sub-Element Groups tab.3. Select one or more subelement groups from the list in the left pane.4. Select one or more formulas from the list in the right pane.5. Select a time range in the Data Range Selection group from the following:

Current - Selects currently collected data.Recent - Selects recently collected data.History - Select historical data.

6. Select one or more data types in the Data Type group from the following:Raw - Provides raw collected data.Min - Provides minimum values of the raw data according to theaggregation type that you select.Max - Provides maximum values of the raw data according to theaggregation type that you select.Sum - Provides the sum of the raw data according to the aggregation typeyou select.Count - Provides the number of raw data according to the aggregation typeyou select.

7. Select an aggregation type in the Aggregation type list from the following:Per day - aggregations per dayPer week - aggregations per weekPer month - aggregations per month

8. Select an aggregation set in the Aggregations Set list from the following:GMT - Greenwich Mean Time, which is the mean solar time of the meridianof Greenwich used as the prime basis of standard time throughout theworld.AggSet1 to AggSet 6 - An Aggregation Set defines an offset from GMT andis associated with groups.

Saving a graphExplains how to save a graph

Procedure1. Select Save from the File menu.2. Select the timestamp from one of the following:

GMT - Saves the data in Greenwich Mean Time, which is the mean solartime of the meridian of Greenwich used as the prime basis of standard timethroughout the world.Local - Saves the graph in the local time for your location.

3. Select the file type in the Type list from one of the following:Bin format - Compacted ASCII format. Only the date and measure valueare preserved in the data lines.

Chapter 11. Viewing collected data 171

BOF format - Binary Object Format provides an extensible, space and timeefficient storage format for storing Tivoli Netcool Performance Managerobjects in flat files. This format provides a high-performance format fortransferring information between distributed Tivoli Netcool PerformanceManager subsystems in a store and forward environment.

4. Specify where to save the graph in the File box or click Browse to find thelocation.


Printing a graphExplains how to set up printing for graphical charts in the Data Viewer.

About this task

To set up printing, follow these steps:

Procedure1. Select Print from the File menu.2. Select a paper format, width, and height.3. Select an orientation (Portrait or Landscape).4. Select where to position the graph on the sheet of paper (Center or Origin).5. Click Apply or OK to accept your selections.

Configuring graphsExplains how to configure a graph.

Displaying crosshairsProcedure1. Right-click an area inside the graph and select the Configuration menu item.2. Click Display CrossHair in the General tab.3. Select a line width for the crosshairs from the Width list.4. Select a dash format for the crosshairs from the Dash list.5. Select a color for the crosshairs from the Color list menu.6. Click OK to accept your selections. Crosshairs appears in the graph. For

example:


Displaying a gridProcedure1. Right-click an area inside the graph and select the Configuration menu item.2. Click the General tab.3. Click the Display Grid in the General tab.4. Click Set Grid on minor ticks if you want the grid to display on minor axis

marks.5. Select the desired line width for the grid from the Width list.6. Select a dash format for the grid from the Dash list.7. Select a color for the grid from the Color list.8. Click Apply or OK to accept your selection. A grid appears in the graph.

Configuring a titleProcedure1. Right-click an area inside the graph and select the Configuration menu item.2. Click the General tab.3. Click Configure Title in the General tab.4. Select a font style for the title from the Font list.5. Select a weight for the title from the Weight list.6. Select a slant for the title from the Slant list.7. Select a point size for the title from the Size list.8. Select a color for the title from the Color box.9. Click OK to accept your selections. A title appears in the graph.


Configuring the X-AxisProcedure1. Right-click an area inside the graph and select the Configuration menu item.2. Click the Axis tab and select X axis.3. Enter a title for the X axis in the Title box.4. Select a line width for the X axis from the Width list.5. Select a color for the X axis from the Color list.6. Select a date format to be displayed in the X axis area of the graph from the

Scale group. The default setting is "MM/dd/nhh:mm" (minute, day, hourminute). You can enter any character you desire such as forward slash (/)colons (:), semicolons (;).The following keypad options are available:

Year = YYYYMonth = MMWeek = wwDay = ddHour = hhMinute = mmCR = \n is carriage return to next line

7. Click OK to accept your selections. The X axis in the graph is configuredaccordingly.

Customizing the Y-AxisProcedure1. Right-click an area inside the graph and select the Configuration menu item.2. Click the Axis tab and select Y axis.3. Select Y Axis in the Axis tab.4. Enter a title for the Y axis in the Title box.5. Select a line width for the Y-axis from the Width list.6. Select a color for the Y-axis from the Color list.7. Select a scale type in the Scale group from the following:

Linear - displays the graph using straight lines.Logarithmic - displays the graph in powers of ten (ten times more linesthan the Linear option).

8. Click OK to accept your selection. The Y-axis in the graph is configuredaccordingly.

Configuring curvesProcedure1. Right-click an area inside the graph and select the Configuration menu item.2. Click the Curves tab.3. Select a curve that you want to modify from the Curve list.4. Select the desired line width for the curve from the Width list.5. Select a dash format for the curve from the Dash list.6. Select a symbol format from the Symbol list.7. Select a color from the Color box to change the color of the graphical points.


8. Specify the legend by entering the appropriate label in the Legend field.9. Select the curves displayed from the Curves to Display list.

10. Click Apply or OK to accept your selections.

Configuring a graph legendProcedure1. Right-click an area inside the graph and select the Configuration menu item.2. Click the Legend tab.3. Click Yes to display the legend.4. Select the position for the legend in the Position list from the following:

Top - Top of graphBottom - Under graphRight - Right of graphLeft - Left of graphPlot Area - In the graph

5. Select a font for the legend from the Font list to choose a font style for thetitle.

6. Select a weight for the legend from the Weight list.7. Select a slant for the legend from the Slant list.8. Select a point size for the legend from the Size list.9. Select a color for the legend from the Color box

10. Click OK to accept your selections. A legend appears in the graph.


Chapter 12. Viewing the list of collectors

Explains how to view information about both active and non-active collectorsusing the Collector Information Tool.

About this task

The collectinfo command-line interface (CLI) command launches the CollectorInformation Tool from the command line. For more information, see the IBM TivoliNetcool Performance Manager: Command Line Interface Guide.

To view the collectors list, follow these steps:

Procedure1. Click Collector Information from the Monitor tab. This window lists all the

collectors loaded from the database.2. Select a collector from the list, then click the other tabs to review specific

collector information. The following collector information is available:

Column Description

Number Indicates the collector identifier number.

Status Indicates the collector status. For example,"Running" or "Not Running."

Server Indicates the host name or IP address of thesystem on which the collector is installed.

Port Indicates the communication port numberfor the collector.

Type Indicates the collector type.

Installation Directory Indicates the directory where the collector isinstalled.

Viewing collector informationExplains how to view detailed information about a collector.

Procedure1. Click Collector Information from the Monitor tab.2. Select a collector from the list.3. Click the Collector Information tab. The State group displays the following

information:

Item Description

Green traffic light Indicates that the collector is active andoperational.

Yellow traffic light Indicates that the collector is in a transitorystate between start-up and shutdown. This isa temporary state.


Item Description

Red traffic light Indicates that the collector is not active oroperational.

Refresh Interval Indicates the frequency in which theinformation displayed in the tabs isrefreshed (in seconds).

Current debug level Indicates the current debug level of thecollector. "0" indicates a minimal debug. Thelevel should be set to "0"; a level of "1" ormore is for troubleshooting purposes.

Version Displays the version date and operatingsystem for the collector.

Server Displays the name of the computer onwhich the collector is running.

Port Displays the port number that the collectoruses to communicate with Tivoli NetcoolPerformance Manager DataMart.

Connections Displays the number of clients connected tothe collector.

SysUpTime Displays the amount of time that thecollector has run without interruption (indays, hours, minutes, and seconds).

Current Time Displays the day, month, year, and time ofday as set on the server where the collectoris running (dependent on your time zone).The time shown here can be different fromlocal time. This is the time that TivoliNetcool Performance Manager DataMartuses to schedule data collection, if youdeclare a calendar from 8 am to 8 pm.

The Actions group displays the following information:

Item Description

Refresh interval Modifies the current refresh value frequency.

Start/Stop button Launches or shuts down the local collector.


Item Description

Current tabDisplays the following options:Note: Tivoli Netcool Performance ManagerDataMart does not permanently save yourselections in the Current tab.

v Debug level - Modifies the debug level ofthe collector. Contact technical support atIBM for more information aboutdebugging.

v Log Path - Saves the debug informationfile (ServReqDaemonxxxx.log) to a specificpath. You can use the Directory Selectionbutton to select the log path. The defaultlog directory is $PVMHOME/log.

v Date in file - Displays the creation date inthe log file name. Select Yes to activatethis option. For example,pvmd_9991015_16348.log.

v Channel in file - Displays the requestnumber in the log file name. Selecting thisoption creates one file per request ID.Select Yes to activate this option.

Note: The Channel in file option createsmultiple files (one for each request).

Tivoli Netcool Performance ManagerDataMart permanently saves and stores yourselections in the configuration file. Forexample, in $PVMHOME/conf/pvmd.log on theserver system.

Viewing scheduler informationThe Scheduler maintains the internal list of the requests for data. The Schedulerregularly scans the list to determine whether requests are executed placed into awaiting queue. A task placed in a waiting queue is flagged as "READY." You canview statistics compiled by the collector about the planning of requests.

Procedure1. Click Collector Information from the Monitor tab.2. Select a collector from the list.3. Click the Scheduler tab. The Scheduler window displays the following

information:

Item Description

Collections Priority Mode Indicates the number of Collections PriorityMode requests on the current collector.

Chapter 12. Viewing the list of collectors 179

Item Description

Execute requestsIndicates the number of requests beingexecuted on the collector.

v Execute external requests (Nb)[immediate] - Indicates the number ofexternal requests being executed on thecollector.

v Execute internal requests (Nb)[immediate] - Indicates the number ofinternal requests being executed on thecollector.

Items ProcessedIndicates the collector activity level. Theactivity level is measured in number ofrequests executed per second over a specifictime period.

v Items Processed Average (Nb) [last 24hours] - Indicates the number of requestsexecuted during the last 24 hours.

v Items Processed Average (Nb) [last hour]- Indicates the number of requestsexecuted during the last hour.

v Items Processing Rate (Nb/s) [last 24hours] - Indicates the request executionrate per second during the last 24 hours.You can compare this activity level withresults on comparable systems to evaluateperformance.

v Items Processing Rate (Nb/s) [last hour] -Indicates the request execution rate persecond during the last hour. This rate issimilar to the rate for the last 24 hours butis more sensitive to variations duringcollections over longer periods (longerthan one hour).

Items ScheduledRequests that need to be executed. TheScheduler scans the list to determine therequests to execute or to place in the waitingqueue.

v Items Scheduled (Nb) [immediate]indicates the number of requestsgenerated in this list.

v Max Items Scheduled (Nb) [immediate]indicates the maximum configurationvalue for the request list size.


Item Description

Queue Max SizeThird of the three waiting queues where athread searches for a request number toexecute.

v Queue Max Size (Nb) [last 24 hours]indicates the maximum size attained bythe queue during the last 24 hours.

v Queue Max Size (Nb) [last hour]indicates the maximum size attained bythe queue during the last hour.

v Queue Size (Nb) [immediate] indicatesthe current size of the queue.

ThreadsCollector activity creates threads. Thecollector verifies it can activate a thread eachtime it executes a collection or launches acommand. If it cannot activate a thread, nocollector activity occurs and reliability isdiminished.

v Threads (Nb) [immediate] - Indicates thenumber of threads created throughcollector activity. This is a realtimecounter. The value can change quicklyfrom 1 to MaxThreadedItems. You cantune this value in the registry.conf file inthe following location:$PVMHOME/conf/registry.conf

v Threads Availability (%) [last 24 hours] -Indicates collector reliability during thelast 24 hours.

v Threads Availability (%) [last hour] -Indicates collector reliability during thelast hour.

internal errors (Nb) [cumul] Indicates the number of memory errorsdetected and corrected. This counter needsto remain at zero. If it is not at zero, restartthe collector.

Viewing data manager informationThe Data Manager manages the insertion of records (measures) into the record file.It accumulates data in an internal queue, then transfers the data to the record filewhen the queue reaches a specified size. Each time the Data Manager transfersdata it stores information about the job.

Procedure1. Click Collector Information from the Monitor tab.2. Select a collector from the list.3. Click the Data Manager tab. The Data Manager window displays the following

information:


Item Description

.dat files v dat files (nb) [immediate] - Indicates thenumber of .dat files located in the$PVMHOME/data directory.

v dat files (KB) [immediate] - Indicates thesize of the .dat file.

Average Storage TimeSpecifies the average time to store a measurein a local file.

v Average Storage Time (ms) [last 24hours] - Indicates the average processingtime for a measure during the last 24hours.

v Average Storage Time (ms) [last hour] -Indicates the average processing time fora measure during the last hour.

Congestion State Indicates the Congestion State code.

FilesystemIndicates file system space information:

v Filesystem FSLL (KB) [immediate] -Indicates the size of the FSLL for the filesystem.

v Filesystem available (KB) [immediate] -Indicates the available size of the filesystem.

v Filesystem free space (KB) [immediate] -Indicates the amount of free space on thefile system.

v Filesystem quota (KB) [immediate] -Indicates the size of the quota for the filesystem.

v Filesystem used (KB) [immediate] -Indicates the amount of space used on thefile system.


Item Description

MeasuresA measure is a record inserted into therecord file. Each insertion is measured intime and the median value is posted.

v Measures Processed Average (Nb) [last24 hours] - Indicates the number ofmeasures processed during the last 24hours.

v Measures Processed Average (Nb) [lasthour] - Indicates the number of measuresprocessed during the last hour.

v Measures Lost (Nb) [cumul] - Indicatesthe number of measures that have beenlost since the start of the collector. Thesemeasures were collected but were notsaved.

v Measures Lost (Nb) [last 24 hours] -Indicates the number of measures lostduring the last 24 hours. These measureswere collected but were not saved.

v Measures Lost (Nb) [last hour] - Indicatesthe number of measures lost during thelast hour. These measures were collectedbut were not saved.

v Measures Stored (Nb) [cumul] - Indicatesthe total number of measures stored. Forexample, total number of answers frommetrics requested.

v Measures Stored (Nb) [last 24 hours]indicates the total number of measuresstored. For example, the total number ofanswers from metrics requested over thelast 24 hours.

v Measures Stored (Nb) [last hour]indicates the total number of measuresstored. For example, the total number ofanswers from metrics requested over thelast hour.

Save AvailabilityDisplays the reliability of data insertion.Reliability of 100% means that all measuresare correctly inserted. A reliability rate ofless than 100% does not necessarily indicatea loss of measures, but should beinvestigated.

v Save Availability (%) [last 24 hours] -Indicates the calculated insertionreliability during the last 24 hours.

v Save Availability (%) [last hour] -Indicates the calculated insertionreliability during the last hour.


Viewing target informationEach time the collector interacts with an SNMP agent, information about theinteraction is recorded.

Procedure1. Click Collector Information from the Monitor tab.2. Select a collector from the list.3. Click the Targets tab. The Targets window displays the following information:

Item Description

Agent SNMP Version [immediate] Indicates the SNMP Version of the agent forthe collector.

Average SNMP Response Time (ms) [lasthour]

Indicates the average elapsed time betweenthe sending of the first SNMP packet and itsreturn. Time is not calculated on theexchanged packets during the MIB browse.

CALC Errors (Nb) [last hour] Indicates the number of CALC errors thatoccurred in the last hour.

CPU Load (Nb OIDs) [last hour] Indicates the estimated CPU load needed bythe collector to handle all requests relatingto this target. This measurement integratesthe number of OIDs handled to solve therequests, the number of requests necessary,and the frequency of each interrogation.

Discovery Received PDU (Nb) [last hour] Indicates the number of PDUs received aspart of the discovery process in the lasthour.

Discovery Received PDU Max Size (bytes)[last hour]

Indicates the maximum size of PDUsreceived as part of the discovery process inthe last hour.

Discovery Received PDU Total Size (bytes)[last hour]

Indicates the total size of PDUs received aspart of the discovery process in the lasthour.

Discovery Sent PDU (Nb) [last hour] Indicates the number of PDUs sent as partof the discovery process in the last hour.

Discovery Sent PDU Max Size (bytes) [lasthour]

Indicates the maximum size of PDUs sent aspart of the discovery process in the lasthour.

Discovery Sent PDU Total Size (bytes) [lasthour]

Indicates the total size of PDUs sent as partof the discovery process in the last hour.

Expected Measures (Nb) [last hour] Indicates the number of measures expectedin the last hour.

Max SNMP Response Time (ms) [last hour] Indicates the maximum amount of time foran SNMP response that occurred in the lasthour.

OID Rate (Nb/s) [last hour] Indicates the OID rate that occurred in thelast hour.

Produced Measures (Nb) [last hour] Indicates the number of measures producedin the last hour.

Received PDU (Nb) [last hour] Indicates the number of PDUs received inthe last hour.


Item Description

Received PDU Max Size (bytes) [last hour] Indicates the maximum size of PDUsreceived in the last hour.

Received PDU Total Size (bytes) [last hour] Indicates the total size of PDUs received inthe last hour.

SNMP Availability (%) [last hour] Indicates the reliability of the interactionwith SNMP agents. A value of 0% canindicate a bad community name or that thetimeout value is insufficient. A value morethan 0% but less than 100% is often causedby timeouts during the SNMP interaction.

SNMP Errors (Nb) [last hour] Indicates the total amount of errors in theSNMP protocol encountered during theinteraction. An error cannot occur when thecommunity name is correct and the timeoutis correctly configured. An error signifieseither an agent problem in responding to apacket or an error between the collector MIBand the MIB supported by the agent. Mostoften it indicates a problem with a formula.

SNMP Requests (Nb) [cumul] Indicates the total number of executedrequests on equipment since the start of thecollector. You can identify the equipmentwith a high rate of requests.

Sent PDU (Nb) [last hour] Indicates the number of PDUs sent in thelast hour.

Sent PDU Max Size (bytes) [last hour] Indicates the maximum size of PDUs sent inthe last hour.

Sent PDU Total Size (bytes) [last hour] Indicates the total size of PDUs sent in thelast hour.

Viewing detailed technical informationYou can view detailed technical information about the collector that displays allcurrent tasks managed by the collector.

Procedure1. Click Collector Information from the Monitor tab.2. Select a collector from the list.3. Click the Detail Information tab. The tasks use the following format:

[<number>]ID <Request ID>, {CAL <calendardefinition>} (<priority>) (<state>)(<type>)

Where:

Item Description

<Request ID> The ID of the tasks in the Scheduler list oftasks.

<calendar definition> Definition (period optional calendar name)and the time of the next start


Item Description

<priority>Valid values include the following:

v Realtime

v High

v Normal

The priority chosen here is linked to thecorresponding Scheduler priority queue. See“Viewing scheduler information” on page179 for details.

<state>Valid values include the following:

v ASLEEP - indicates that the task is set forthe next execution and does not use anyresources.

v ACTIVE - indicates that the task iscurrently running. This state appears anddisappears as the task processes SNMPqueries.

v ZOMBIE - indicates that the task is aboutto disappear from view.

v READY - indicates that the task hasreached the time of the next start but iswaiting for an available thread to beexecuted. The task has been place in awaiting queue according to its currentpriority value. As soon as the task ishandled by a thread, the state changes toACTIVE.

<type>Name of the service for this task:

v ServiceSTAT - displays a list of the taskscurrently running.

v ServiceCRON - executes commands atdifferent preset times.

v ServiceFORM and ServiceGet - executeSNMP queries

v Trgt indicates that the target host that isbeing queried. A target can be one of thefollowing types:

element (Elmt)sub-element (SubElmt)group of elements (ElmtGrp)group of sub-elements (SubElmtGrp)

v Form indicates the formula used for thequery.

v Inst lists the instances impacted duringthe query process.

Note: Formulas (PVL-Tivoli Netcool Performance Manager-Statistics) areavailable that monitor collector statistics.


Stopping and restarting a local collectorYou can stop the local collector from the Collector Information Tool window.

Procedure1. Click Collector Information from the Monitor tab.2. Select a collector from the list.3. Click the Collector Information tab.4. Click the Stop button in the Actions group, then confirm your choice at the

prompt.5. Click Yes to confirm.

Note: To stop a remote collector, you need to connect to the system on whichthe collector resides and launch the pvmdmgrscript with the stop option. Forexample:pvmdmgr stop

Restarting a local collectorYou can restart the local collector from the Collector Information Tool window.

Procedure1. Click Start in the Actions group, then confirm your choice at the prompt.2. Click Yes to restart the collector.

Note: To restart a remote collector, you need to connect to the machine onwhich the collector resides and launch the pvmdmgr script with the start option.For example:pvmdmgr start

Configuring watchdog for collector memory checkingThe watchdog for Collector Memory Checking limits the amount of memory usedby a collector and restarts collectors that exceed a threshold limit.

ParametersThe Watchdog parameters reside in the registry.conf file located in the confdirectory where Tivoli Netcool Performance Manager DataMart is installed.

The Watchdog default settings are as follows:[Quallaby\PROVISO-Daemon\WatchMgr]"ActivateWatchMgr"="1""UseErrorsCount"="1""UseMemoryChecking"="0""UseWatchDog"="1"[Quallaby\PROVISO-Daemon\WatchMgr\ErrorsCount]"MaxErrorsCount"="10"

[Quallaby\PROVISO-Daemon\WatchMgr\MemoryChecking]"MinimalWorkingSet"="134217728""MaximalWorkingSet"="1073741824""WorkingSetInflation"="1000"

[Quallaby\PROVISO-Daemon\WatchMgr\WatchDog]"MaxPulseInterval"="250""PulseInterval"="80"


Activation of memory checkingAbout this task

To activate memory checking, you need to set the following value to 1:[Quallaby\PROVISO-Daemon\WatchMgr]"UseMemoryChecking"="1"

Setting lower and upper limitsThere are two settings for controlling the memory size of a collector. All values arein bytes.

About this task

The first value is the maximum upper limit."MaximalWorkingSet"="1073741824"

You need to tune this limit, which depends on the size of the physical memory onyour system and the number of processes running. For example, if your systemconfiguration is comprised of one collector with a remote database, you can set theupper limit size to 75 percent of the total physical memory. This means that thecollector process would never uses more that 75 percent of the memory."MinimalWorkingSet"="134217728"

The lower limit is the threshold under which there is no check of memory. Thislimit is important, and should not be configured to a small value because duringthe boot phase of a collector, the memory is increasing rapidly, and this increasecan confuse the Watchdog. Ideally, this limit should be set up to the normalmemory usage of a collector.

Procedure1. To set up this value, start a Tivoli Netcool Performance Manager process, let it

run for one hour, modify theregistry.conf file2. Get the process size using the ps command.3. Restart the collector.

Setting inflation limitEach time a collector reloads a new request, it calculates the amount of memoryneeded to manage those requests, and each time the Watchdog is contacted, ittransmits information.

About this task

You can control memory usage. For example:"WorkingSetInflation"="1000"

The amount of memory required is called the nominal value and the real amountof memory used is called real value.

If the value is greater than the value contained in the WorkingSetInflation= thanthe nominal amount, then the Watchdog can restart a collector.

By default, this setting is set to 1000, which means 1000 percent (that is, the realvalue greater than 10 times of the nominal value). If the minimal value is correctly


set up, then the inflation factor can be set to 130 (30 %) or 150 (50%). A small value(110) is not recommended because this limit can be reached during normaloperation.

This setting is only useful, if there are several processes on the system, and if acollector has to share memory with Oracle. In this case, the inflation is preferred tothe upper limit. If only one collector is on the system by itself, the upper limitshould be used instead, and the inflation setting should remain at 1000.


Chapter 13. Viewing status

The Tivoli Netcool Performance Manager DataMart Status tool displays whichmodules are currently in use, their host system, and displays locked instances ofrunning modules.

The pvmstat command line interface (CLI) command launches the Status Tool fromthe command line. For more information, see the IBM Tivoli Netcool PerformanceManager: Command Line Interface Guide.

Viewing DataMart statusExplains how to use the Tivoli Netcool Performance Manager DataMart Status toolto view the status of individual modules.

Procedure

Click DataMart Status in the Applications tab. The Registered Modules groupdisplays the following information:

Item Description

Name Name of the module in use.

Pid Process identification number of UNIX.

Host Name of the host machine on which theprocess is being run.

Display Name of the graphical view from whichTivoli Netcool Performance ManagerDataMart was launched.

PortPort number of the software process. Thecollector default port is 3002. 0 indicates thatno port number is used.

User Name of a Tivoli Netcool PerformanceManager DataMart user running themodule.

Date Date and time that the module waslaunched.

Status Indicates either a status or progress level.

Comment Provides information on the module beingrun.

The Locked Modules group displays the following information:

Item Description

Lock Name of the locked module.

ModeProtection level that the lock provides.

0 = Read Only

1 = Read/Write


Item Description

Locked by Name of the application that has locked themodule (usually the module is locked byitself).

Pid Process identification number of UNIX.

Host Name of the host system on which theprocess is being run.

The following modules do not use a collector:v Mibcompiler - This module processes MIB from ASNI format to IBM format

(understandable by the collector). No result testing is made; therefore, there is noneed for a collector.

v Userconf - There is no connection between a collector and the users descriptions.This part of the configuration is not loaded/reloaded by a collector.

Removing a lock from the databaseTivoli Netcool Performance Manager DataMart locks a module when it is in use bya user to prevent others from making any changes. A lock can be set on a runningmodule's instance either by another module, or by the module itself.

About this task

You can run more than one instance of a module simultaneously. The first instancesets a lock in the database to indicate to the next instance that this it is alreadyrunning. The lock causes the next instance to run in "Read-Only" mode so thatcritical operations (for example, changing resources in the database) are under thecontrol of the original instance.

If a module is abnormally terminated, and does not unregister or unlock itselffrom the database, then the instance module is still displayed by the Tivoli NetcoolPerformance Manager DataMart Status tool even following a refreshing.

To remove a lock from the database, follow these steps:

Note: You cannot remove a lock that is locked by another user using this module.Use the pvmstat command line interface to remove a lock set by another user

Procedure1. Click DataMart Status in the Applications tab. The Tivoli Netcool Performance

Manager DataMart Status Tool dialog box appears.2. Select Remove Locks from the File menu. The module changes to unlocked

and disappears from the Locked Modules group.


Chapter 14. Viewing database information

Explains how to view information on the Tivoli Netcool Performance ManagerDataMart database, instance, and status.

Before you begin

Before you view database information, ensure that libpvmextc.so is running.

Procedure1. Click Database Information in the Monitor tab. A splash screen appears

followed by the ProvisoInfo Browser.2. Click Refresh objects from the database to globally update the window with

the most recent database information.3. Click the Identification tab. The Identification tab provides the following

information:

Item Description

Database Server Name Name of the server where the database isinstalled.

Database Name Name of the database. The database is thedata on disk (set of files), stored in operatingsystem files. Tivoli Netcool PerformanceManager DataMart uses only one database.

Current Database User Current user connected to the database. Forexample, "PV_ADMIN".

Oracle Edition Release For example, Oracle 8i Enterprise Edition,Release 8.1.7.1.0 - Production.

PL/SQL Release For example, PL/SQL Release 8.1.7.1.0 -Production.

CORE For example, 8.1.7.0.0 - Production.

TNS for Operating System For example, 8.1.7.1.0 - Production.

NLSRTL Version National Language Support Run-TimeLibrary. This library is responsible forproviding algorithms forinternationalization. The information(NLSDATA) is read by the NLSRTL libraryduring run-time. For example, 3.4.1.0.0 -Production.


Item Description

Total SGASystem Global Area is the shared memoryarea used by the instance to storeinformation shared between the databaseand the user processes. The following valuesare displayed (in MB):

v Fixed Size - exact size. For example, 72K.

v Variable Size - shared spool. For example,291M.

v Database Buffers - part of the SGA thatholds copies of blocks of data read fromthe Oracle datafiles on disk. For example,125M.

v Redo Buffers - an area of memory withinthe SGA that holds information aboutrecent changes to the database. Forexample, 528K.

Last Refresh Date Displays the date when the database waslast refreshed. The format is Y-M-D H-M-S.

Last Refresh Duration Displays the amount of time (in seconds)used when you refresh all objects from thedatabase.

Viewing database free space statusThe Database Free Status is displayed at the bottom of the ProvisoInfo Browser.Free space is computed using metric data and metadata tablespaces.

About this task

The Database Free Space Status values include the following:

Value Description

NORMAL (green) Indicates that the database is functioningproperly. More than or equal to 30 percentof free space is available.

WARNING (orange) Indicates that database free space isminimal. Less than or equal to 30 percent offree space is available.

CRITICAL (red) Indicates that you need to purge part of thedatabase. Less than or equal to 10 percent offree space is available

DEADZONE (maroon) Indicates that the database might not befunctioning properly. Less than or equal to 5percent of free space is available.

Note: If a warning, critical, or deadzone status exists, the affected tab in theProvisoInfo Browser displays the appropriate color code (orange, red, or maroon).

A refresh is automatically started every day at 4 p.m. If the status is not normal, amessage is sent to Tivoli Netcool Performance Manager user via the notifyDBSpacescript (located in the bin directory of the DataMart installation path).


Viewing database parametersProcedure1. Click the Database folder. The Parameters and Statistics folders appear.2. Click the Parameters folder to view database parameter information. This

information lets you quickly identify all database level parameters and is usefulfor working with Oracle technical support or IBM in troubleshooting issues. Forexample, you can verify that a parameter changes or if the init.ora file wasmodified.

Viewing database statisticsProcedure1. Click the Database folder. The Parameters and Statistics folders appear.2. Click the Statistics folder to view database statistics. This information provides

you with a quick look at performance of Oracle memory areas, and displaysthe information in progression bars. For example, the information aboveindicates that the disk space for the SQL Area is 75 percent full.

Viewing the Tivoli Netcool Performance Manager version informationProcedure

Click the Proviso Version folder to display version information. This informationlets you quickly identify the versions of Tivoli Netcool Performance Managercomponents in your environment and is useful for working with Oracle technicalsupport or IBM in troubleshooting issues.

Viewing MetaDataThe MetaData tab displays information about Tivoli Netcool Performance Managerconfiguration elements, metrics, and properties. Metadata represents data such astablespace and table information, and is grouped by topic (for example,configuration, temporary tablespaces, system tablespaces, etc.). Tivoli NetcoolPerformance Manager describes each resource, collection and aggregationschedules, and MIBs.

About this task

To view Metadata information, follow these steps:

Procedure1. Click the MetaData tab.2. Expand the Tablespaces item.3. Expand the Metadata item.4. Click a tablespace item.5. Expand a tablespace item in the tree to display a list of files.6. Click the directory path and file name to view the total space used (in

megabytes) for this file.7. Expand the Temporary tablespace item and the items beneath it to view sizing

information in megabytes.8. Expand the System & Rollback item. The SYSTEM item appears.

Chapter 14. Viewing database information 195

9. Click the SYSTEM item to display spacing information.10. Expand the SYSTEM item to view only the total space used (in megabytes).11. Expand the Meta Tables item.12. Expand the Formulas item.13. Click the FRML_DESC item in the Formulas tree. This information lets you

quickly view table structures and provides a short description of the purposeof each column (if available).

14. Click the FRML_DESC_HIST item.15. Click the FRML_GRP_DESC item.16. Click the FRML_GRP_MEMBER item.17. Click the FRML_GRP_PATH.18. Click the FRML_MIB.19. Click the FMRL_MIB_HIST.20. Click the Resources item to expand the branch.21. Click the Grouping - Inventory item to expand the branch.22. Click the Properties - Thresholds item to expand the branch.23. Click the Dataview item to expand the branch.24. Click the Nomenclature item to expand the branch.25. Click the Schedule - Collect item to expand the branch.26. Click the Miscellaneous item to expand the branch.27. Click the Internal item to expand the branch.

Viewing MetricDataThe MetricData tab displays channel information on aggregation sets, channel lists,and loaders. MetricData is data collected and optionally transformed by formulas,imported, or summarized by an aggregation policy.

About this task

To view metric data, follow these steps:

Note: This information allows you to view current threshold database status fortables paces in current history (raw data). In the example above, the thresholds arein the critical stage, alerting you to potential problems.

Procedure1. Click the MetricData tab.2. Click the Aggregation Sets tab. This information displays aggregation sets

status. In the example above, GMT -5 (Boston) aggregation set is active and isbeing used by the Complex Metric Engine. The aggregation set’s tables andviews show a status of “OK.”

3. Click a GMT value in the tree to view the aggregation set status for that GMT.4. Click a channel item to get additional partition information.5. Click the Channels tab to display channel information.6. Click the Working item to expand the branch.7. Click an item to display file names.8. Click a file name.9. Click the Historic item to expand the branch.


10. Click a historic item. The number of rows, high date, and tablespace used isdisplayed for each partition. Partition information for recent and previous(ancient) history is also displayed.

11. Click the DataLoads tab to display a list of SNMP and Bulk collectorsinstalled in your network.

12. Click a DataLoad collector number under the DataLoads navigation tree.13. Click the Registry tab. The Registry stores parameter information. Each

application creates a registry, which allows Tivoli Netcool PerformanceManager parameters to be stored in a central location.

14. Click the Default item in the Registry navigation tree to expand the branch.15. Click the Common item in the Registry navigation tree to expand the branch.16. Click the Current folder. This information allows you to view current

threshold database status for tablespaces in current history (raw data). In theexample above, the thresholds are in the critical stage, alerting you topotential problems.

17. Click the Clients item in the Registry navigation tree to expand the branch.18. Click the Channel (C01) item in the Registry navigation tree to expand the

branch.

Viewing client informationExplains how to view Oracle client status information on the Tivoli NetcoolPerformance Manager Database, DataMart, DataLoad, DataChannel, and DataView.

About this task

To view client information, follow these steps:

Procedure1. Click the Clients tab.2. Click either Database, DataLoad, DataView, DataMart or Data Channel.

Oracle IDs must be created in the database and displayed. Only one client isconnected by PV_ADMIN.

Viewing database statusExplains how to view database status to help you troubleshoot problems.

Procedure

Click the Database Status tab.If the database is normal, the following information is displayed:


If the status of the database is in the Warning, Critical, or Deadzone state, thefollowing information is displayed:

Note: In the example above, only 7 percent of overall free space remains available,and the database is 90 percent full.


Viewing disk informationProcedure1. Click the Disk tab.2. Click the / (forward slash) to display the amount of free disk space.3. Click var to display the amount of free disk space.4. Expand /export/home to expand the branch and view mount point disk space

information.5. Click an item. The following information is displayed:


Chapter 15. Exporting or Importing Metadata

Discusses the following topics:

Exporting dataExplains how to export data between two Tivoli Netcool Performance ManagerDataMart systems. You can save metadata to files so they can be shared with otherusers in different locations. An export operation creates a set of files in a specifieddestination directory.

Procedure1. Click Import-Export Configuration in the Configuration tab. The EXPORT

operation is enabled by default. An export operation can be used even if themodule is running in read-only mode.

2. Click Browse to go to the target directory where you want to store the files.The default path (/opt/datamart) appears in the Directory list. Since an exportprocedure can generate numerous files, it might be helpful for you to create adirectory for organizational purposes.To create a directory, enter its name in the Directory Name box and click OK.The directory is automatically created in the $PVHOME/importexport directorypath.

3. Select a profile to export from the Type of Data list. These commands areconfigured in the impexp.conf file, with each data type having import andexport profile parameters specified in the configuration file. The following datatypes are available:


Option Description Operation Profile(s)

formulas Export of metrics used forcollections.

v exportFormulas (default) -Exports all formulas (listedbelow) from the database.

v exportCustomFormulas -Exports all customformulas (formulas a usercreates manually; notformulas in Tivoli NetcoolPerformance ManagerTechnology Packs) fromthe database. The customdata indices* are greaterthan 100000000.

v exportPsFormulas -Exports all formulascreated by IBMProfessional Services.

v exportPvlFormulas -Exports formulas createdby Tivoli NetcoolPerformance ManagerApplication. The indexesfor these formulas is lessthan 50000000.

*where indexes = databaseIDs.

calendars Export period of collectionconfigurations (no link withtimezones).

v exportCalendars (default) -Exports all calendars. Thisprofile includes theprofiles below.

v exportCustomCalendars -Exports all calendarscreated by the users. Thecustom data indexes aregreater than 100000000.

v exportPsCalendars -Exports all calendarscreated by IBMProfessional Services.

v exportPvlCalendars -Exports all calendarscreated by TechnologyPacks. Indexes are lessthan 50000000.

users Export of users and userpermissions.

v exportUsers - Exports allusers.

timezones Export of aggregation setsconfiguration.

v exportTimeZones - Exportsaggregation setdescriptions.

elements Export of elementsconfiguration.

v exportElements (default) -Exports all elements andgroups..



subelements Export of subelementsconfiguration.

v exportSubElements(default) - Exports allsubelements.

v

exportSubElements_Skeleton- Exports subelementgroups.

v

exportLinks_subEltGroups/aggregationSets - Exportsthe links betweensubelement groups andaggregations sets.

dashboards Export of dashboards. v exportDashboards -Exports all dashboards,

resources Export of subelements andelements.

v exportResources -Combines exportElementsand exportSubElementsprofiles.

requests Export of data requests. v exportRequests - Exportsall data collection requests.

thresholds Export of thresholds. v exportThresholds - Exportsall thresholds.

inventory_profiles Export of inventory profiles. v exportInventoryProfiles -Exports all inventoryprofiles.

reports Export of reports. v exportReports - Exports allreports.

snmp_parameters Export of SNMP parameters. v exportSnmpElements -Exports SNMP parameters.

core_configuration Export of core configuration. v exportCoreConfiguration -Exports core configuration.

all Export all of the data types. v exportAllConfig - Exportsall data types. Exports alldata that can be exportedusing this module. Thisprofile is a combination ofall the export profiles ofall the data types.

A profile can be either a basic profile (resmgr parameters) or a list of profiles.For example, “exportAllConfig” includes the following profiles:exportFormulas, exportCalendars, exportUsers, exportResources,exportDashboards, exportRequests, and exportTimeZones.The differences between formulas and calendars created within DataMartmodules and those created by a technology pack include the following:v To recognize the data created by the Tivoli Netcool Performance Manager

Technology Packs, the database indexes ranged from 0 to 50000000 isreserved

Chapter 15. Exporting or Importing Metadata 203

v The records whose indexes are included in that range comes fromTechnology Packs. The Custom and PVL profiles set a filter on the indexes.

4. Select an export profile from the Operation Profile listbox or accept the default.An export profile defines how to export data. For each data type, one or moreexport profile types are available.

5. Click Run to start the export procedure. A progress bar indicates the status ofthe export procedure. The message bar at the bottom of the box displays thenumber of items processed, and errors and warnings (if any). Click Details todisplay more information about the export procedure.

6. When the operation ends, click Close to exit the message box. Export files aregenerated in the target directory.

Export files

The datatypes.res file is used for an import procedure, as it contains a list of alldata types that are exported for the profile.

Do not rename or delete export files, or change their content. To exchange exportdata between systems, either move, copy, or rename the entire directory

Option Profile(s) Export File(s) Generated

formulas

exportFormulascustom_formula.dat

custom_mib.dat

pvl_formula.dat

pvl_mib.dat

ps_formula.dat

ps_mib.dat

exportCustomFormulascustom_formula.dat

custom_mib.dat

exportPsFormulasps_formula.dat

ps_mib.dat

exportPvlFormulaspvl_formula.dat

pvl_mib.dat

calendars



exportCalendarscustomCalGlob.dat

customCalPlan.dat

pvlCalGlob.dat

pvlCalPlan.dat

psCalGlob.dat

psCalPlan.dat

exportPsCalendarspsCalGlob.dat

psCalPlan.dat

exportCustomCalendarscustomCalGlob.dat

customCalPlan.dat

exportPvlCalendarspvlCalGlob.dat

pvlCalPlan.dat

users

exportusersusersDesc.dat

usersGrgpLink.dat

usersGroups.dat

usersRights.dat

timezones

exportTimeZones timeZones.dat

elements

exportElementseGroupsDesc.dat

elements.dat

snmpElementItems.dat

ega.dat

elementsLinks.dat

egu.dat

eltProperties.dat

exportElements_SkeletoneGroupsDesc.dat

ega.dat

egu.dat

subelements



exportSubElementsseGroupsDesc.dat

subelementLinks.dat

sega.dat

subelementgroupsCal.dat

segrpToTz.dat

subelementgroupsPlans.dat

segu.dat

subelementsProperties.dat

subElements.dat

exportSubElements_SkeletonseGroupsDesc.dat

segu.dat sega.dat


segrpToTz.dat


exportLinks_subEltGroups/aggregationSets

segrpToTz.dat

dashboards exportDashboardsdbdDesc.dat

dbdText.dat

dbdThresholds.dat

dbdViews.dat



resources exportResourceseGroupsDesc.dat

segrpToTz.dat ega.dat

segu.dat egu.dat


elements.dat

subElements.dat

elementsLinks.dat

subelementLinks.dat

eltProperties.dat


seGroupsDesc.dat


sega.dat


requests exportRequestsseRequests.dat

segpRequests.dat

thresholds exportThresholds thresholds.dat

inventory_profiles exportInventoryProfiles optinventory.dat

reports exportReportslinkReport.dat

reportStyle.dat

web_user.dat

report.dat

reportStyleGroup.dat

web_user_group.dat

reportGroup.dat

web_link_user2group.dat

web_user_properties.dat

snmp_parameters exportSnmpElements snmpElementItems.dat



core_configuration exportCoreConfigurationLinkReport.dat

Threshold.dat

segp_resource.dat

Report.dat

formula.dat

subelement.dat

ReportGroup.dat

mib_formula.dat

web_user.dat

ReportStyle.dat

profil.dat

web_user_group.dat

ReportStyleGroup.dat

propertiesE.dat


Requests.dat

propertiesSE.dat Rules.dat

se_with_seprp.dat



all exportAllConfigcustomCalGlob.dat

reportGroup.dat

customCalPlan.dat

reportStyle.dat

custom_formula.dat

reportStyleGroup.dat

custom_mib.dat

seGroupsDesc.dat

dbdDesc.dat

seRequests.dat

dbdText.dat

sega.dat

dbdThresholds.dat

segpRequests.dat

dbdViews.dat

segrpToTz.dat

eGroupsDesc.dat

segu.dat ega.dat


egu.dat

subElements.dat

elements.dat

subelementLinks.dat

elementsLinks.dat


eltProperties.dat




exportAllConfig (continued) linkReport.dat


optinventory.dat

thresholds.dat

psCalGlob.dat

timeZones.dat

psCalPlan.dat

usersDesc.dat

ps_formula.dat

usersGrgpLink.dat

ps_mib.dat

usersGroups.dat

pvlCalGlob.dat

usersRights.dat

pvlCalPlan.dat

web_link_user2group.dat

pvl_formula.dat

web_user.dat pvl_mib.dat

web_user_group.datreport.dat


Importing dataExplains how to import data between two Tivoli Netcool Performance ManagerDataMart systems. You can save metadata to files so they can be shared with otherusers in different locations. Do not rename or delete export files, or change theircontent. To exchange export data between systems, either move, copy, or renamethe entire directory

Procedure1. Click Import-Export Configuration in the Configuration tab.2. Click the Import option.3. Click Browse to go to the target directory where the files are stored.4. Select a profile to import from the Type of Data list. These commands are

configured in the impexp.conf file, with each data type having import andexport profile parameters specified in the configuration file. The following datatypes are available:



formulas Import of metrics used forcollections.

v importFormulas (default) -Imports all formulas(listed below) from thedatabase.

v importCustomFormulas -Imports all customformulas (formulas a usercreates manually; notformulas in Tivoli NetcoolPerformance ManagerTechnology Packs) fromthe database. The customdata indexes* are greaterthan 100000000.

v importPsFormulas -Imports all formulascreated by Tivoli NetcoolPerformance ManagerProfessional Services.

v importPvlFormulas -Imports formulas createdby Tivoli NetcoolPerformance ManagerApplication. The indexesfor these formulas is lessthan 50000000.

*where indices = databaseIDs.

calendars Import period of collectionconfigurations (no link withtimezones).

v importCalendars (default)- Imports all calendars.This profile includes theprofiles below.

v importCustomCalendars -Imports all calendarscreated by the users. Thecustom data indexes aregreater than 100000000.

v importPsCalendars -Imports all calendarscreated by IBMProfessional Services.

v importPvlCalendars -Imports all calendarscreated by TechnologyPacks. Indexes are lessthan 50000000.

users Import of users and userpermissions.

v importUsers - Imports allusers.

elements Import of elementsconfiguration.

v importElements (default) -Exports all elements andgroups.



subelements Import of subelementsconfiguration.

v importSubElements(default) - Exports allsubelements.

v

importSubElements_Skeleton- Exports subelementgroups.

v

importLinks_subEltGroups/aggregationSets - Exportsthe links betweensubelement groups andaggregations sets.

dashboards Import of dashboards. v importDashboards -Exports all dashboards,

resources Import of subelements andelements.

v importResources -Combines exportElementsand exportSubElementsprofiles.

requests Import of data requests. v importRequests - Exportsall data collection requests.

thresholds Import of thresholds. v importThresholds -Imports all thresholds.

inventory_profiles Import of inventory profiles. v importInventoryProfiles -Imports all inventoryprofiles.

reports Import of reports. v importReports - Importsall reports.

snmp_parameters Import of SNMP parameters. v importSnmpElements -Imports SNMPparameters.

core_configuration Import of core configuration. v importCoreConfiguration -Imports core configuration

all Import all of the data types. v importAllConfig - Exportsall data types. Exports alldata that can be exportedusing this module. Thisprofile is a combination ofall the export profiles ofall the data types.

5. Select an import profile from the Operation Profile list or accept the default.An import profile defines how to import data. For each data type, one or moreimport profile types are available.

6. Click Run to start the import procedure. A progress bar indicates the status ofthe import procedure. The message bar at the bottom of the box displays thenumber of items processed, and errors and warnings (if any). Click Details todisplay more information about the import procedure.


7. When the operation ends, click Close to exit the message box. After an importprocedure is completed, a collector reload is performed and the collector isrefreshed with the configuration changes.

8. Click Close to exit the message box. After an import procedure is completed, acollector reload is performed and the collector is refreshed with theconfiguration changes.

Note: While the format of the files generated is a resource manager (resmgr)format, individual files generated using Resource Manager cannot be importedusing the importExport tool.


Glossary

ANS.1 Abstract Syntax Notation One is OSIlanguage for describing data typesindependent of particular computerstructures and representation techniques.

ARP The Address Resolution Protocol is usedto bind an IP address to a MAC address.

ATM Asynchronous Transfer Mode

availabilityThe percentage of time during a giveninterval that a network object or interfaceis available to perform its function.Availability is measured by a poller. Thepoller tracks how long an element orsub-element is unavailable and thepercentage of time that it is available.Tivoli Netcool Performance ManagerDataMart lets you monitor end-to-endnetwork availability.

bandwidthA measure of the capacity of acommunications link.

bps Bit per Second is a measurement thatexpresses the speed at which data istransferred between computers.

bridge A device that connects one physicalsection of a network to another, oftenproviding isolation.

broadcastA packet destined for all hosts on anetwork.

burst rateA circuit data transmission rate above theCommitted Information Rate (CIR) thatcan be used to increase data throughput ifit is available.

collectorThe collector stores data for monitoringelements and sub-elements on yournetwork. Tivoli Netcool PerformanceManager DataMart enables the collection,consolidation, storage and archiving ofcritical network performance and serviceanalysis data. This data can be integratedinto Tivoli Netcool Performance ManagerDataView or the reporting tool of yourchoice.

Committed Information Rate (CIR)The specified amount of guaranteedbandwidth (measured in bits per second)on a Frame Relay service. Typically, whenpurchasing a Frame Relay service, acompany can specify the CIR level theywant. The Frame Relay network vendorguarantees that frames not exceeding thislevel will be delivered. It is possible thatadditional traffic might also be delivered,but it is not guaranteed. See also burstrate.

daemonA process that executes a programautomatically in background mode whenthe system is initially started.

DashboardA real-time graphic display of one ormore formulas or MIB objects on one ormore hosts.

Data Link Connection Identifier (DLCI)Frame relay allows users to segmentphysical ports into multiple logicalinterfaces. Each of these logical interfacesis identified by its DLCI.

defaultAn operation or value that the system orapplication assumes unless you make anexplicit choice.

delay (also known as latency)A measurement from one end of anetwork or device to another. Higherlatency indicates longer delays.

discoveryLets you analyze your network andgather information about TCP/IP networkelements and sub-elements and how theyare interconnected.

Domain Name Service (DNS)The system that translates betweeninternet IP addresses and internet hostnames.

Dynamic Host Configuration Protocol (DHCP)A protocol that provides dynamic IPaddress allocation and automatic IPconfiguration.


elementAn addressable, managed node or host.

exceptionAn exception is an event that is notconsidered normal and requires yourimmediate attention. For example, routeroutages or network response time failures.

formulaA set of mathematical instructions andSNMP queries.

frame relayA packet-oriented communication methodfor connecting computer systems onWANs. Frame Relay isdigital-data-communications protocolprovided by a carrier. Connections into aframe relay network require a router anda line from the customer site to a carrier'sframe relay port entry.

group Customized, virtual association thatcontains one or more network elements.

hop A hop represents a transmission of a datapacket through a router in a network ofinterconnected segments or subnetworks.In many networks, there are many routersconnecting many segments, thus forminga number of paths that a packet can travelto get to its destination. A measure of thispath is the hop count, or the number ofrouters the packet must pass through toget to its destination.

hub A common connection point for devicesin a network. Hubs are commonly used toconnect segments of a LAN. A hubcontains multiple ports. When a packetarrives at one port, it is copied to theother ports so that all segments of theLAN can see all packets.

HyperText Markup Language (HTML)Used for developing Web documents.

HyperText Transfer Protocol (HTTP)A protocol that allows Web clients toretrieve information from Web servers.

Internet Control Message Protocol (ICMP)Used to handle error and controlmessages sent when datagrams arediscarded or systems are congested. Partof the IP protocol.

interfaceThe network connection between twosystems or devices.

InternetA collection of autonomous systemsinterconnected by bridges, routers, orgateways.

Inventory profileLets you define your network inventory.You can create different profiles fordifferent resources in your network.

Inventory ToolProvides you with a report of networkelements and sub-elements on yournetwork.

IP Internet Protocol is a communicationsprotocol that allows computers of anymake to communicate when running IPsoftware.

IP addressAn identifier for a computer or device onan IP network. Networks using the IPprotocol route messages based on the IPaddress of the destination. The format ofan IP address is a 32-bit numeric addresswritten as four numbers separated byperiods. Each number can be zero to 255.For example, 1.160.10.240.

KB Kilobyte is a data unit of 1,024 bytes.

latencyMeasures the time it takes for a packet totravel from one point to another pointand back.

Local Area Network (LAN)A computer network that is limited to asmall geographic area. For example, anoffice building.

MAC The Media Access Control protocolgoverns the method by which a stationcan access a network.

Management Information Base (MIB)A data repository used by an SNMP agentto store management data about amanaged object. All MIB information isdefined in ASN.1 format. MIB variablesare organized in groups such as systemand interfaces. An SNMP agent managesonly the part of the MIB that the MIBreferences.

Meta-DataControl information about the collecteddata. Tivoli Netcool Performance Manager


uses meta data to describe resources,collection and aggregation schedules, andMIBs.

Metric The result of a formula applied toresources. These results are displayed inthe reports viewed through a Webbrowser.

Metric-DataData collected on resources that is(optionally) transformed by formulas,imported, or summarized by anaggregation policy.

millisecondOne thousandth of a second.

networkA system of computers, hardware, andsoftware that is connected over whichdata, files, and messages can betransmitted and end users communicate.Networks can be local or wide area.Network users can share the same dataand application files, send messagesbetween individual workstations, andprotect files with an extensive securitysystem.

network administratorThe person who installs, configures, anddeploys Tivoli Netcool PerformanceManager on an enterprise network. Thisincludes creating and managing usersprofiles and assigning rights andprivileges.

network monitoring systemAn integrated set of software thatmeasures and analyzescommunications-related parameters in anetwork.

network trafficThe data that flows on a communicationsdevice or system.

NIS Network Information Service is a protocolfor administering network-widedatabases.

node The endpoint of a network connection ora junction common to two or more linesin a network. Nodes can be processors,controllers, or workstations.

NOC Network Operations Center

Open Database Connectivity (ODBC)ODBC is a specification designed to give

users access to a variety of multipledesktop databases and file formats.

OSI The Open Systems Interconnection modelis a layered architecture plan thatstandardizes levels of service and type ofinteraction for computers exchanginginformation through a network.)

packet Also known as a frame, single unit ofdata transmitted over a packet-switchingnetwork. A packet contains source anddestination address in addition to thedata.

peak The highest level or greatest degree asrepresented in graphical reports.

Permanent Virtual Circuits (PVC)A pathway through a packet-switched orcell-switched network.

PID Protocol Identifier.

PING (Packet INternet Groper) a utility todetermine whether a specific IP address isaccessible. A source IP device sends apacket to a destination address and waitsfor a reply.

port A physical connection on a networkdevice.

probe A packet sent to the remote end of anetwork. The probe requests anacknowledgment from end nodes.

profileSee Inventory profile.

PropertiesAny attribute or characteristic that definesa resource more precisely and providesadditional information on it. Propertiescan be customer attributes and technicalattributes including:

v Customer name for which the resource isdeployed

v VPNv IP addressv Interface namev Sitev Class of service (Silver, Gold, Platinum)v Geographical properties (city, building, floor)v Customer properties (division, business

department, branch office)v Service properties (applications)

Glossary 217

v SLA value (thresholds, burst threshold,availability threshold, CIR, and SLA contracttype)

protocolA standard set of rules by which networkelements trade information tocommunicate including the format,timing, sequencing, or error checking.

Quality of Service (QOS)A guaranteed throughput level from theprovider to its customers.

Read-Only modeProvides only viewing access to TivoliNetcool Performance Manager DataMartmodules. You cannot make modificationsto any module in "read-only" mode. TheRead-Only icon is as follows:

repeaterA device that lets you extend the lengthof your network by amplifying andrepeating the information it receives.

resourceA type of physical or logical objectmanaged by the Tivoli NetcoolPerformance Manager system. Anymanaged physical interface or port is aresource, any managed logical circuit isalso resource. For example, a Frame RelayDLCI, an ATM PVC, and a CE-CEitinerary (VPN Customer Edge). Anyobject from which Tivoli NetcoolPerformance Manager can getidentification (a name and a label) andrelated metrics can be modeled in theDataMart, using the resource concept.

rights User privileges assigned by the networkadministrator for access to Tivoli NetcoolPerformance Manager.

report A formatted and organized presentationof data.

response timeThe amount of time that takes oneendpoint to respond to a request fromanother endpoint on a network.

router The equipment that receives an internetpacket and sends it to the next machine inthe destination path.

segmentA protocol data unit consisting of part ofa stream of bytes being sent between twomachines.

server A computer that runs services. Also refersto a piece of hardware or software thatprovides access to information requestedfrom it.

Service Level Agreement (SLA)is a contractual guarantee that stipulatesthe specified minimum level of networkcapacity and service support that acustomer will receive. An SLA establishesrealistic expectations for consistent servicedelivery and articulates compensatorymeasure in the case of service deliveryfailure.

You can develop an aggressive SLA, bothinternally and externally, that deliverspriority, availability, and bandwidthrequired by business applications.

Service Level Management (SLM)provides the measurement and evaluationof network performance against businessmetrics. A comprehensive flexible SLMplan that monitors performanceeffectively can result in increased usersatisfaction.

Simple Network Management Protocol (SNMP)A communications protocol used tocontrol and monitor devices on anetwork. An SNMP agent manages partsof a MIB.

SMI Structure of Management Information(RFC 1155) specifies rules used to definemanaged objects in a MIB. See also MIB.

SNMP Availabilityis the percentage of time during a giveninterval that a network object or interfaceis available to perform its function.Availability is measured by a poller. Thepoller tracks how long an element orsub-element is unavailable and thepercentage of time that it is available.Tivoli Netcool Performance ManagerDataMart helps you increase end-to-endnetwork availability.

SNMP Response Timeis the amount of time that takes oneendpoint to respond to a request fromanother endpoint on a network. Tivoli


Netcool Performance Manager DataMarthelps you improve response time.

SNMP trapAn SNMP trap lets you forward one ormore exceptions for a network object to adesignated computer on your network.The destination computer needs to have athird-party packet capturing softwareprogram installed. You use this programto view the exception message.

SNMP Utilizationis the percentage of bandwidth that anelement or sub-element is in use during agiven period of time. For example, 30% to40% signifies a low utilization and 80 to90% signifies a high utilization.

Sub-ElementA sub-component of an element, such as aport, interface, virtual circuits, user, or aDLCI.

subnetA portion of a network that shares acommon address component. On IPnetworks, subnets are defined as alldevices whose IP addresses have thesame prefix. For example, all devices withIP addresses that start with 100.100.100.would be part of the same subnet. IPnetworks are divided using a subnetmask.

subnet maskA 32-bit value that distinguishes thenetwork ID from the host ID of an IPaddress.

switch A device that filters and forwards packetsbetween LAN or WAN segments.Switches operate at the data link layer(layer 2) of the OSI Reference Model andtherefore support any packet protocol.LANs that use switches to join segmentsare called switched LANs or, in the caseof Ethernet networks, switched EthernetLANs.

target The object to which a formula applies

thresholdA value that is compared against metricsto determine if the metrics exceed or dropbelow a critical limit.

tracerouteA utility that traces a packet from sourceIP to destination IP address, showing howmany hops the packet requires to reachthe host and how long each hop takes.

traffic See network traffic.

TCP Transmission Control Protocol is a layer 4protocol that provides a level ofconnection-oriented reliability to an IPnetwork.

URL Uniform Resource Locator is theaddressing system used in the Web thatcan reference any type of file on theInternet, enabling a Web client to accessthat file.

utilizationThe percentage of time that a networkobject or interface is in use for a givenperiod of time.

VLAN A virtual LAN is a group of devices onone or more LANs that are configured sothat they can communicate as if they wereattached to the same wire, when if fact,they are located on a number of differentLAN segments.

volumeThe number of bits that flowed through anetwork interface over a period of time.

Web browserA software program that lets you viewand access HTML documents. Forexample, Internet Explorer and NetscapeNavigator.

Wide Area Network (WAN)A network of geographically dispersedcomputers.

Write modeProvides you with full access to TivoliNetcool Performance Manager DataMartmodules. You can make modification toany module in "write" mode. The writemode icon is as follows:

Glossary 219

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 223

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