IBM Tivoli Netcool Performance Manager 1.3.2
Wirelines Component
Document Revision R2E1
DataMart Configuration and Operation
Guide
Note
Before 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 Contract
with IBM Corp.
Contents
Preface . . . . . . . . . . . . . . vii
Intended audience . . . . . . . . . . .
Tivoli Netcool Performance Manager - Wireline
Component . . . . . . . . . . . . .
. vii
. vii
Chapter 1. Introduction . . . . . . . . 1
Configuring DataMart GUI .
Opening DataMart GUI. . .
The Tivoli Netcool Performance
tabs and utilities . . . . .
Configuration . . . . .
Data Manager . . . . .
Metric . . . . . . .
Monitor . . . . . . .
Resource. . . . . . .
Where to go from here . . .
. . . . . . .
. . . . . . .
Manager DataMart
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. 1
. 4
.
.
.
.
.
.
.
4
5
5
5
5
6
6
Chapter 2. Configuring users and
groups . . . . . . . . . . . . . . . 7
Creating a user . . . . .
Deleting a user . . . .
Creating a group of users . .
Deleting a group . . . .
Granting rights to groups . .
Understanding the DataMart
. . . . . . . . 7
. . . . . . . . 8
. . . . . . . . 8
. . . . . . . . 9
. . . . . . . . 9
modules . . . . 10
Chapter 3. Configuring inventory . . . 13
Before you begin . . . . . . . . . . .
Configuring your network inventory . . . . .
Using the Inventory Tool . . . . . . . .
Creating an inventory profile . . . . . . .
Configuring your discovery . . . . . . . .
Selecting your network discovery method . .
Specifying IP addresses . . . . . . . .
Defining an SNMP configuration . . . . .
Specifying SNMP community names . . . .
Specifying an ICMP configuration . . . . .
Configuring labels for subelements . . . .
Specifying synchronization . . . . . . .
Inserting resources . . . . . . . . . .
Specifying automatic grouping . . . . . .
Specifying repository group rules . . . . .
Selecting modules . . . . . . . . . .
Running an inventory profile . . . . . . .
Viewing the log file. . . . . . . . . .
Reloading collectors . . . . . . . . .
Deleting a profile . . . . . . . . . .
SNMP bandwidth control and collection smoothing
Bandwidth control . . . . . . . . . .
Collection smoothing . . . . . . . . .
Understanding file formats . . . . . . . .
Element file . . . . . . . . . . . .
Subelement file . . . . . . . . . . .
Managing dynamic changes . . . . . . . .
Guidelines . . . . . . . . . . . . .
© Copyright IBM Corp. 2012
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13
13
14
15
16
17
18
19
21
23
24
25
25
26
27
27
28
29
29
29
29
30
30
33
34
34
35
36
CME formula command template . . . . .
Example based on process illustration . . .
Example for 2233_IF family . . . . . . .
CME processing . . . . . . . . . . .
Discovery server responsibilities . . . . .
Logging policy . . . . . . . . . . .
Configuring a bulk collector inventory . . . .
Understanding a bulk collector inventory . . .
Importing bulk files . . . . . . . . .
Bulk collector inventory file sets . . . . .
pollinv and pollprofile commands . . . . .
Inventory polling and the cron table . . . .
Directories and files (location, naming, and format)
Bulk file format examples . . . . . . . .
Element resources . . . . . . . . . .
Subelement resources . . . . . . . . .
Inventory arguments . . . . . . . . .
Chapter 4. Creating grouping rules
Before you begin . . . . . . . . .
Creating grouping rules . . . . . . .
Using operators and functions . . . .
Using conditions . . . . . . . .
Using grouping rules . . . . . . . .
Testing grouping rules . . . . . . . .
Saving test results . . . . . . . .
Copying grouping rules . . . . . .
Moving grouping rules . . . . . .
Deleting Grouping Rules . . . . . .
Understanding the file format . . . .
Viewing rule database information . . .
Viewing properties . . . . . . . . .
Using syntax for grouping rules . . . .
Using static text . . . . . . . . .
Creating variables . . . . . . . .
Using a text editor to create grouping rules.
Exporting grouping rules . . . . . .
Importing grouping rules . . . . . .
Understanding the file format . . . . .
Grouping rule example . . . . . . .
Name with static text . . . . . . .
Name with a variable . . . . . . .
Nested variable . . . . . . . . .
Condition . . . . . . . . . . .
Example of nested conditions . . . . .
Condition . . . . . . . . . . .
Nested condition . . . . . . . .
Second nested condition . . . . . .
Variable . . . . . . . . . . .
Example of combining text, a variable, and a
condition . . . . . . . . . . . .
.
.
.
.
.
.
.
.
37
37
38
39
40
40
41
42
42
43
44
44
45
46
46
46
46
. . 47
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 64
Chapter 5. Collection and aggregation
Before you begin . . . . . . .
Configuring data collection requests .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
47
47
48
52
53
53
55
55
55
56
56
56
57
58
58
58
58
58
59
59
59
60
60
61
61
62
62
62
63
63
65
. 65
. 65
iii
Setting the collection period .
Configuring aggregation requests
Configuring a percentile value
Filtering requests . . . . .
Sorting columns . . . . .
Validating the requests . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
66
66
66
67
67
67
Chapter 6. Configuring calendars . . . 69
Using the Calendar Configuration Tool
Creating customized calendars . . .
Creating a one-time calendar . .
Creating a daily calendar . . . .
Creating a weekly calendar . . .
Creating a monthly calendar. . .
Deleting a calendar . . . . . . .
Using the Calendar Selector . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
69
69
71
71
72
72
73
73
Chapter 7. Writing custom formulas . . 75
Before you begin . . . . . . . . . .
What is a formula? . . . . . . . . . .
Merging discovery results . . . . . .
Creating formulas . . . . . . . . . .
Editing the inventory_subelement.txt file .
Testing formulas. . . . . . . . . .
Saving formulas . . . . . . . . . .
Modifying a custom formula . . . . .
Standard rules for writing formulas . . . .
Dim declaration . . . . . . . . . .
OIDVAL expression line . . . . . . .
OIDINST instruction . . . . . . . . .
Example . . . . . . . . . . . .
Types of variables . . . . . . . . . .
Instance variables . . . . . . . . .
Temporary variables . . . . . . . .
Host variable . . . . . . . . . . .
Returning a result . . . . . . . . . .
Comments in formulas . . . . . . . .
Syntax for functions . . . . . . . . .
Mathematical functions . . . . . . .
Other functions . . . . . . . . . .
SNMP-specific functions . . . . . . .
Aggregate functions . . . . . . . .
Filter functions . . . . . . . . . .
Distribution function . . . . . . . .
AddForMissing() operator . . . . . . .
Example . . . . . . . . . . . .
Using the Formula Selector . . . . . . .
Creating a formula group. . . . . . .
Finding a formula . . . . . . . . .
Copying formulas . . . . . . . . .
Deleting a formula . . . . . . . . .
Renaming a formula . . . . . . . .
Discovery formula for a Redback Ethernet
interface . . . . . . . . . . . .
Collection formula example . . . . .
Merge formulas example . . . . . .
inventory_sub-element.txt . . . . . .
1213_IF . . . . . . . . . . . .
2233_IF . . . . . . . . . . . .
2233_HCOctets_Support . . . . . . .
iv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
75
75
76
77
77
78
79
80
80
80
82
83
85
86
86
87
88
88
88
88
88
89
90
90
91
91
92
92
93
93
93
94
94
94
. 95
102
105
105
105
105
106
2233_HCPackets_Support . . . . . . .
1213_IF_Invariant . . . . . . . . . .
2233_IF_Invariant . . . . . . . . . .
<CustomerSpecific>_KEY . . . . . . .
Formula error messages . . . . . . . . .
Understanding the inventory_subelements.txt file
SysObjId . . . . . . . . . . . . .
FilterFormulaName . . . . . . . . .
SubElementFamilyName to cancel . . . .
.
.
.
.
.
106
106
106
107
107
108
. 109
. 110
. 110
Chapter 8. Configuring thresholds . . 111
About thresholds . . . . . . . . . . .
Threshold types . . . . . . . . . . .
User profiles and threshold types. . . . .
Basic computation . . . . . . . . . .
Statistic used for processing . . . . . .
Exceeding a threshold level. . . . . . .
Interpolation. . . . . . . . . . . .
Threshold deployment . . . . . . . . .
Examples . . . . . . . . . . . . .
TRAP generation rules . . . . . . . . .
Using the threshold definition period setting . .
Processing traps . . . . . . . . . .
Launching the threshold tool . . . . . . .
Adding a threshold . . . . . . . . . .
Selecting metrics . . . . . . . . . .
Applying thresholds to a group of subelements
Specifying subelements . . . . . . . .
Configuring burst or period thresholds . . . .
Configuring thresholds . . . . . . . .
Configuring mode . . . . . . . . . .
Configuring maximum percent over for burst
and period thresholds . . . . . . . .
Configuring burst values . . . . . . .
Configuring period values . . . . . . .
Configuring baseline thresholds . . . . . .
Trapping threshold violations . . . . . . .
Trapping threshold violations to the log file .
Sending trapped threshold violations to
specified hosts . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
111
111
112
112
112
113
113
113
114
118
118
118
119
121
121
122
122
123
123
123
.
.
.
.
.
.
124
124
125
126
129
129
. 130
Chapter 9. Managing MIBs . . . . . . 131
MIB groups . . . . . . . . . .
Compiling a MIB . . . . . . . .
Printing or saving trace information .
Deleting a MIB . . . . . . . .
Viewing MIB file source . . . . .
Browsing MIB files . . . . . .
Viewing compiled MIB files . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
131
131
133
133
134
134
134
Chapter 10. Editing resources . . . . 139
Filtering elements and subelements
Viewing resource information . .
Viewing elements . . . . .
Viewing subelements . . . .
Viewing subelement groups .
Viewing property details . .
Viewing reports . . . . .
Viewing thresholds . . . .
Exporting resources . . . . .
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
139
140
140
141
141
142
143
143
144
Importing resources . . . . . . . .
Adding resources . . . . . . . . .
Adding elements . . . . . . . .
Adding subelements . . . . . . .
Adding composite subelement relations
Adding reports . . . . . . . . .
Adding thresholds. . . . . . . .
Creating a property . . . . . . .
Modifying resources . . . . . . . .
Modifying an element . . . . . .
Modifying a subelement . . . . . .
Modifying a report . . . . . . .
Modifying Thresholds . . . . . .
Deleting resources . . . . . . . . .
Deleting elements or subelements . .
Deleting subelement groups . . . .
Deleting resources within groups . . .
Deleting properties . . . . . . .
Deleting composite Subelement relations
Deploying reports . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
145
145
145
146
147
147
148
152
158
158
159
160
161
165
166
166
166
166
167
167
Chapter 11. Viewing collected data
169
Viewing graphical charts for files . . . . . .
Viewing graphical charts for subelements . . .
Viewing graphical charts for subelement groups
Saving a graph . . . . . . . . . . . .
Printing a graph . . . . . . . . . . .
Configuring graphs . . . . . . . . . .
Displaying crosshairs . . . . . . . . .
Displaying a grid . . . . . . . . . .
Configuring a title. . . . . . . . . .
Configuring the X-Axis . . . . . . . .
Customizing the Y-Axis . . . . . . . .
Configuring curves . . . . . . . . .
Configuring a graph legend . . . . . .
. 169
. 170
171
. 171
. 172
. 172
. 172
. 173
. 173
. 174
. 174
. 174
. 175
Viewing target information . . . . . .
Viewing detailed technical information . .
Stopping and restarting a local collector .
Restarting a local collector . . . . .
Configuring watchdog for collector memory
checking . . . . . . . . . . . .
Parameters . . . . . . . . . .
Activation of memory checking . . .
Setting lower and upper limits . . .
Setting inflation limit . . . . . . .
Chapter 13. Viewing status
.
.
.
.
.
.
.
.
.
.
.
.
184
185
187
187
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
187
187
188
188
188
. . . . . 191
Viewing DataMart status . . . .
Removing a lock from the database .
.
.
.
.
.
.
.
.
. 191
. 192
Chapter 14. Viewing database
information . . . . . . . . . . . . 193
Viewing database free space status . . . . . . 194
Viewing database parameters . . . . . . . . 195
Viewing database statistics . . . . . . . . . 195
Viewing the Tivoli Netcool Performance Manager
version information . . . . . . . . . . . 195
Viewing MetaData. . . . . . . . . . . . 195
Viewing MetricData . . . . . . . . . . . 196
Viewing client information . . . . . . . . . 197
Viewing database status . . . . . . . . . . 197
Viewing disk information . . . . . . . . . 199
Chapter 15. Exporting or Importing
Metadata . . . . . . . . . . . . . 201
Exporting data .
Export files .
Importing data .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 201
. 204
. 210
Glossary . . . . . . . . . . . . . 215
Chapter 12. Viewing the list of
collectors . . . . . . . . . . . . . 177
Viewing collector information . . .
Viewing scheduler information . .
Viewing data manager information .
.
.
.
.
.
.
.
.
.
.
.
.
. 177
. 179
. 181
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 of
a wireline component and a wireless component. .
The purpose of this guide is to help you work with Tivoli Netcool Performance
Manager DataMart.
Intended audience
The audience for this guide is the Tivoli Netcool Performance Manager
administrators who assign permissions, create groups, associate users with reports,
and manages Tivoli Netcool Performanc Manager DataMart.
Tivoli Netcool Performance Manager - Wireline Component
IBM® 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 the
following subcomponents:
v DataMart is a set of management, configuration, and troubleshooting GUIs. The
Tivoli Netcool Performance Manager System Administrator uses the GUIs to
define policies and configuration, and to verify and troubleshoot operations.
v DataLoad provides flexible, distributed data collection and data import of SNMP
and non-SNMP data to a centralized database.
v DataChannel aggregates the data collected through Tivoli Netcool Performance
Manager DataLoad for use by the Tivoli Netcool Performance Manager
DataView reporting functions. It also processes online calculations and detects
real-time threshold violations.
v DataView is a reliable application server for on-demand, web-based network
reports.
v Technology Packs extend the Tivoli Netcool Performance Manager system with
service-ready reports for network operations, business development, and
customer viewing.
The following figure shows the different Tivoli Netcool Performance Manager
modules.
© Copyright IBM Corp. 2012
vii
Tivoli Netcool Performance Manager documentation consists of the following:
v Release notes
v
v
v
v
Configuration recommendations
User guides
Technical notes
Online help
The documentation is available for viewing and downloading on the information
center 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
Chapter 1. Introduction
Tivoli Netcool Performance Manager DataMart supports a graphical user interface
that lets you perform various administrative tasks. You can also manage, and
review information about the resources and metrics being collected and stored in
the Oracle database.
The initial startup steps vary depending on whether you installed a minimal
deployment or a distributed environment deployment. For a distributed
environment deployment, the $PVHOME variable is defined as /opt/datamart by
default. For a minimal deployment, the default is /opt/proviso/datamart.
Configuring DataMart GUI
Explains how to configure DataMart GUI after a Tivoli Netcool Performance
Manager installation.
About this task
The $PVMHOME variable is defined as /opt/datamart by default. For minimal
deployment, the default is /opt/proviso/datamart.
To configure DataMart GUI, follow these steps:
Procedure
1.
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 first
time, you must log in as pvuser.
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. Execute the following command:
pvm
The following information and prompt is displayed:
-----------------------------------------------------Tivoli Netcool/Proviso - Wed Apr 7 09:34:34 IST 2010
Licensed Materials - Property of IBM
5724-P55, 5724-P57, 5724-P58, 5724-P59
Copyright IBM Corporation 2007. All Rights Reserved.
US Government Users Restricted Rights- Use,
duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
Script revision 30.20
DataMart configuration
- Default Association
------------------------------------------------------
Enter password for PV_ADMIN:
© Copyright IBM Corp. 2012
1
Note: The DB_USER_ROOT password is required to connect to the database
using SQL*Plus.
5. Enter the password for DB_USER_ROOT (in this example, PV_ADMIN) and press
Enter.
6. Confirm the password. The setup prompt for the Time Zone in the Database
appears.
==> Press <Enter> to continue ....
_____________
The following Time Zones are defined into the Database :
_________________________________________________________________________________________
id | Date (in GMT)
| offset in | Name
| Aggset status
|
| seconds
|
|
_________________________________________________________________________________________
0 | 1970/01/01 00:00:00 |
0 |
Greenwich Mean Time |
Aggset created
==> Press <Enter> to continue ....
7. Press Enter to continue. The list of available Time Zones appears.
_________________________________________________________________________________________
Num | OffSet | Time zone Name
| Short
| Long
| Hours
|
| Description | Description
_________________________________________________________________________________________
[ 1] : 0:00 |
Europe/London |
BST |Greenwich Mean Time
[ 2] : -10:00 |
America/Adak |
HADT |Hawaii-Aleutian Standard Time
[ 3] : -10:00 |
Pacific/Rarotonga |
CKT |Cook Is. Time
[ 4] : -9:00 |
AST |
AKDT |Alaska Standard Time
[ 5] : -9:00 |
America/Anchorage |
AKDT |Alaska Standard Time
[ 6] : -8:00 |
PST8PDT |
PDT |Pacific Standard Time
[ 7] : -7:00 |
MST7MDT |
MDT |Mountain Standard Time
[ 8] : -6:00 |
America/Mexico_City |
CDT |Central Standard Time
[ 9] : -6:00 |
CST6CDT |
CDT |Central Standard Time
[10] : -5:00 |
EST5EDT |
EDT |Eastern Standard Time
[11] : -4:00 |
America/Santiago |
CLST |Chile Time
[12] : -3:00 |
America/Sao_Paulo |
BRST |Brasilia Time
[13] : -1:00 |
Atlantic/Azores |
AZOST |Azores Time
[14] : 1:00 |
ECT |
CEST |Central European Time
[15] : 1:00 |
Europe/Paris |
CEST |Central European Time
[16] : 2:00 |
Africa/Cairo |
EEST |Eastern European Time
[17] : 2:00 |
Europe/Bucharest |
EEST |Eastern European Time
[18] : 2:00 |
Europe/Helsinki |
EEST |Eastern European Time
[19] : 3:00 |
Asia/Baghdad |
ADT |Arabia Standard Time
[20] : 3:00 |
Europe/Moscow |
MSD |Moscow Standard Time
[21] : 4:00 |
Asia/Baku |
AZST |Azerbaijan Time
[22] : 5:00 |
Asia/Yekaterinburg |
YEKST |Yekaterinburg Time
[23] : 6:00 |
Asia/Novosibirsk |
NOVST |Novosibirsk Time
[24] : 7:00 |
Asia/Krasnoyarsk |
KRAST |Krasnoyarsk Time
[25] : 8:00 |
Asia/Irkutsk |
IRKST |Irkutsk Time
[26] : 9:00 |
Asia/Yakutsk |
YAKST |Yakutsk Time
[27] : 10:00 |
Australia/Sydney |
EST |Eastern Standard Time (New South Wales)
[28] : 11:00 |
Pacific/Noumea |
NCT |New Caledonia Time
[29] : 12:00 |
Asia/Anadyr |
ANAST |Anadyr Time
[30] : 12:00 |
Pacific/Auckland |
NZDT |New Zealand Standard Time
==> Select Time Zone number [1-30 ] (E : Exit) : 1
==> Select an Aggset ID to add/modify (E: Exit) : 1
==> Does your Time Zone manage DST [Y/N] : Y
8. Select and enter your Time Zone number. For example, 1, for Greenwich Mean
Time (GMT).
9. Select and enter your Time Zone number 1 again to confirm the Aggregation
set (the offset hours in your GMT timezone) is associated with GMT 0:00.
10. Enter Y if the Time Zone you selected manages Daylight Saving.
2
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
11. The following output shows that the process to start the DataMart is
completed successfully.
Complete with Success ...
_______________________________________________________________________________________________
The following Time Zone has been modified :
_________________________________________________________________________________________
id | Date (in GMT)
| offset in | Name
|Aggset status
|
| seconds
|
|
_________________________________________________________________________________________
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010/04/07
2010/10/31
2011/03/27
2011/10/30
2012/03/25
2012/10/28
2013/03/31
2013/10/27
2014/03/30
2014/10/26
2015/03/29
2015/10/25
2016/03/27
2016/10/30
2017/03/26
2017/10/29
2018/03/25
2018/10/28
2019/03/31
2019/10/27
2020/03/29
2020/10/25
2021/03/28
2021/10/31
2022/03/27
2022/10/30
2023/03/26
2023/10/29
2024/03/31
2024/10/27
2025/03/30
2025/10/26
2026/03/29
2026/10/25
2027/03/28
2027/10/31
2028/03/26
2028/10/29
2029/03/25
2029/10/28
2030/03/31
2030/10/27
08:42:06
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
01:00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
3600
0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Greenwich Mean Time_2010_DST
Greenwich Mean Time_2010
Greenwich Mean Time_2011_DST
Greenwich Mean Time_2011
Greenwich Mean Time_2012_DST
Greenwich Mean Time_2012
Greenwich Mean Time_2013_DST
Greenwich Mean Time_2013
Greenwich Mean Time_2014_DST
Greenwich Mean Time_2014
Greenwich Mean Time_2015_DST
Greenwich Mean Time_2015
Greenwich Mean Time_2016_DST
Greenwich Mean Time_2016
Greenwich Mean Time_2017_DST
Greenwich Mean Time_2017
Greenwich Mean Time_2018_DST
Greenwich Mean Time_2018
Greenwich Mean Time_2019_DST
Greenwich Mean Time_2019
Greenwich Mean Time_2020_DST
Greenwich Mean Time_2020
Greenwich Mean Time_2021_DST
Greenwich Mean Time_2021
Greenwich Mean Time_2022_DST
Greenwich Mean Time_2022
Greenwich Mean Time_2023_DST
Greenwich Mean Time_2023
Greenwich Mean Time_2024_DST
Greenwich Mean Time_2024
Greenwich Mean Time_2025_DST
Greenwich Mean Time_2025
Greenwich Mean Time_2026_DST
Greenwich Mean Time_2026
Greenwich Mean Time_2027_DST
Greenwich Mean Time_2027
Greenwich Mean Time_2028_DST
Greenwich Mean Time_2028
Greenwich Mean Time_2029_DST
Greenwich Mean Time_2029
Greenwich Mean Time_2030_DST
Greenwich Mean Time_2030
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
|Aggset
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
not
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
created
==> Press <Enter> to continue ....
12. Press Enter. The DataMart GUI appears.
Chapter 1. Introduction
3
Opening DataMart GUI
Explains 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. For
minimal deployment, the default is /opt/proviso/datamart .
If the main toolbar appears gray, the database is not running.
Procedure
1. 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 utilities
The Tivoli Netcool Performance Manager DataMart GUI supports the following
tabs:
v
v
v
v
v
Configuration
Metric
Resource
Monitor
Data Manager
Note: Each tab contains various graphical utilities that allow you to perform
administrative tasks.
4
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Note: Tivoli Netcool Performance Manager DataMart supports an Adobe Acrobat
PDF help system. You can access the online help system by selecting Tivoli
Netcool Performance Manager DataMart Help... from the Help menu.
Configuration
The 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 two
Tivoli Netcool Performance Manager DataMart systems. For example, you can
share information with other Tivoli Netcool Performance Manager DataMart
users in different locations.
v Users Configuration - lets you create, modify, or delete user and group accounts
and 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 Manager
The Data Manager tab supports the following utility:
v Data Viewer - lets you view and verify collected data in the database in
graphical charts.
Metric
The 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 another
application where you want it to be used (such as Formula Editor, Request
Editor, or Dashboard Editor).
v MIB Compiler - lets you convert a management information base (MIB) file in
Structure of Management Information (SMI) format to the Tivoli Netcool
Performance Manager DataMart internal format. You can also add new MIBs in
addition to the MIBs provided with Tivoli Netcool Performance Manager
DataMart.
Monitor
The 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 the
modules that are locked. Lets you unlock modules when necessary.
v Database Information - provides detailed statistical and graphical information
about the Tivoli Netcool Performance Manager DataMart database.
Chapter 1. Introduction
5
Resource
The 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, port
number, 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 here
The following chapters explain how to use the various DataMart utilities to
administer Tivoli Netcool Performance Manager.
6
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 2. Configuring users and groups
Explains how to create users and groups so that customers can access Tivoli
Netcool Performance Manager DataMart. It also explains how to grant access
rights.
Creating a user
Explains how to create one or more user accounts for end-users that need access to
Tivoli Netcool Performance Manager DataMart. You can specify whether a user
account has read-only or full access rights to the Tivoli Netcool Performance
Manager DataMart modules.
About this task
To create a user, follow these steps:
Procedure
1. 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. By
default, the pvuser user account belongs to the admin group and has read
and write access rights to all modules. You can modify the pvuser user
account.
Note: You can choose the name for this user account during installation. For
example, instead of pvuser, you can choose Jerry or operations. See the IBM
Tivoli Netcool Performance Manager: Installation Guide for more details.
v root - the user account for the person(s) responsible for managing the Tivoli
Netcool Performance Manager DataMart system on a network. By default,
the root user account belongs to the admingroup and has read and write
access rights to all modules. You cannot modify the root user account.
Note: The daemon user is a special account used by Oracle. You cannot
modify 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 instructions
on granting user access rights to Tivoli Netcool Performance Manager DataMart
modules.
© Copyright IBM Corp. 2012
7
Deleting a user
Procedure
1. 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 users
Explains how to create a group for users that need access to Tivoli Netcool
Performance Manager DataMart. When you add users to a group, the users
belonging to that group automatically inherit the rights from the group.
About this task
To create a group, follow these steps:
Procedure
1. 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 must
be 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 (by
default), which can be used to view data that is collected for verification
purposes.
v pvUsers - this group has read-only access to all Tivoli Netcool Performance
Manager 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 instructions
on granting access rights to Tivoli Netcool Performance Manager DataMart
modules.
8
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Deleting a group
About 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 Manager
DataMart Administrators.
pvUsers
Tivoli Netcool Performance Manager
DataMart users.
To delete a group, follow these steps:
Procedure
1. 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 groups
About this task
After you create groups as detailed in “Creating a group of users” on page 8, you
can assign rights to specific Tivoli Netcool Performance Manager DataMart
modules for that group.
To grant rights to groups, follow these steps:
Procedure
1. Create a group as detailed in the section “Creating a group of users” on page 8
Or
2. 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 for
a module, Read access is automatically included.
For example, you might want to give full access rights for all modules to
network operators and read-only rights to corporate executives.
See the next section entitled " “Understanding the DataMart modules” on page
10" 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 modules
About this task
The following tables list the Tivoli Netcool Performance Manager DataMart
modules for which you can grant access rights.
Table 1. Configuration tools
Module
Import/Export Configuration
Description
Lets you transfer hosts, subelements,
dashboards, requests, formulas, calendars,
and thresholds between two Tivoli Netcool
Performance Manager DataMart systems.
Users Configuration
Lets you create user and group accounts and
assign access privileges.
Calendar Configuration
Lets you define and modify time ranges for
data collection.
Request Editor
Lets you manage data collection parameters
such as frequency and storage.
Table 2. Metric tools
Module
Description
Formula Editor
Lets you create formulas, which are a series
of operations applied to one or more MIB
objects.
MIB Browser
Lets you browse a MIB tree structure.
MIB Compiler
Lets you convert a management information
base (MIB) file in Structure of Management
Information (SMI) format to the Tivoli
Netcool Performance Manager DataMart
internal format.
Table 3. Resource tools
Module
Description
Inventory Tool
Lets you search for all SNMP hosts on a
network and discover elements and
subelements.
Rule Editor
Lets you create and edit grouping rules.
SNMP Configuration
Lets you define and maintain Simple
Network Management Protocol (SNMP)
community names.
Resource Editor
Lets view resource information, import
resources, export resources, and to delete
resources.
Table 4. Monitor tools
10
Module
Description
Collector Information
Provides information about collector activity.
Tivoli Netcool Performance Manager
DataMart Status Tool
Lists all modules that are currently active.
Lets you unlock modules when necessary.
Dashboard Manager
Lets you launch dashboards requests.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Table 4. Monitor tools (continued)
Dashboard Editor
Lets you create dashboard requests in realtime.
Table 5. Data Manager tools
Module
Description
Data Viewer
Lets you use view and verify collected data
in the database.
Table 6. Selector tools
Module
Description
Formula Selector
Lets you select a formula from the formula
library.
Dashboard Selector
Displays a list of configured dashboards
requests.
Calendar Selector
Lets you designate a time to automatically
launch one or more requests.
Table 7. Command Line Interfaces
Module
Description
Resource Manager (resmgr)
Lets you import, export, modify, and delete
objects in the database. These objects include
elements, subelements, element and
subelement groups, properties, thresholds,
inventory profiles, Tivoli Netcool
Performance Manager DataMart users and
groups, web users, web reports, and web
access.
Database Manager (dbMgr)
A utility that lets you create a database
channel.
Chapter 2. Configuring users and groups
11
12
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 3. Configuring inventory
Explains how to import, analyze, and discover elements and subelements in your
network 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: DataMart
Configuration and Operation Guide.
v You have installed Tivoli Netcool Performance Manager Technology Packs if you
want to use default grouping rules. For instructions on installing Tivoli Netcool
Performance Manager Technology Packs, see the IBM Tivoli Netcool Performance
Manager: Installation Guide.
Note: The Discovery Server uses the dig command from your operating system to
interact with a DNS server. If the system is not configured correctly and the
command does not work, then Tivoli Netcool Performance Manager fails in
discovery from DNS. Consult your operating system configuration guide for
troubleshooting information. The dig command with the axfr option uses an
insecure method of retrieving the entire contents of a DNS server. For safety
reasons, many DNS servers are now configured to reject such a command. For a
secure DNS server, the dig command does not return anything. For such DNS
servers, the Discovery Server with DNS import does not work. Either reconfigure
the DNS to allow the axfr option, or try another import mechanism, such as files
or /etc/hosts.
Configuring your network inventory
Explains how to gather information about elements and subelements in your
network using the Inventory Tool.
When you execute an inventory, the discovery phase searches for SNMP and
non-SNMP elements and subelements (known as resources). As these resources
respond, 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: Command
Line Interface Guide.
Note: The Inventory Tool can find only operational elements. If an element is
down, it is not detected.
© Copyright IBM Corp. 2012
13
Using the Inventory Tool
Procedure
Click Inventory Tool in the Resource tab. The Inventory Tool window appears. A
list of defined profiles appears. An example profile called default also appears, but
it is not functional.
Important: The Tivoli Netcool Performance Manager default inventory profile
settings are used as examples. You must supply settings that are valid for your
network.
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 an
inventory profile” on page 15 for
instructions on selecting a discovery mode.
Collector ID
The collector identifier. Elements and
subelements discovered while running the
profile are assigned to this collector.
To view the status on collectors, see Viewing
Collector Information in the IBM Tivoli Netcool
Performance Manager: DataMart Configuration
and Operation Guide.
Information
Status
Additional information about the profile,
such as the IP addresses you are including
or excluding. If you are importing data from
a file, the file name is displayed.
Provides the following information:
v Ready appears after you create or edit a
profile.
v EndDiscovery appears after you complete
a discovery.
v SynchroReady appears after
pre-synchronization when you run the
profile from the command line (see note).
v EndSynchro appears after
synchronization.
v GroupingReady appears after
pre-grouping when you run the profile
from the command line (see note).
v EndGrouping appears after grouping.
Module to Run
Indicates the modules that are enabled
within the selected profile. A module can be
enabled or disabled by clicking its name.
Note: The inventory command-line interface (CLI) command launches the
Inventory Tool from the command line. See the IBM Tivoli Netcool Performance
Manager: Command Line Interface Guide for instructions on using this CLI.
14
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Creating an inventory profile
The Inventory Tool Wizard lets you create and modify one or more profiles. A
profile lets you define your network inventory. You can create different profiles for
different 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 by
providing collectors with multiple community names that limit the number of
timeouts.
v Separate resources with invariants that require editing during synchronization
from 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 second
profile overwrites the results of the first profile.
To use the Inventory Tool Wizard, follow these steps:
Procedure
1. Select New profile from the Edit menu.
Note: Select Edit profile from the Edit menu if you want to edit an existing
profile.
2. Enter a name for the profile in the Profile name field. If you are editing an
existing profile, this field is automatically populated with the name of the
profile.
Important: You must not use any of the following reserved terms in the name
of your profile:
elt
inventory
slowwan
exclude
ipaddress
snmpconf
fastlan
lan
subelt
filestoinsert
mode
subeltinv
grouping
objectfilter
synchro
icmp
objectfilter
wan
rulefilter
||ROOTROOT||
include
3. If you are managing multiple networks where there is a possibility of
duplicate IP addresses, select the Use duplicate IP addresses option. This
option indexes a subelement name with a collector number so that identical IP
addresses can be differentiated.
4. If you want to check invariants assigned to new resources against only other
sub-elements that belong to the same element, select the Enforce Sub-element
invariant 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 address
is dynamic, select Target devices use dynamic DNS. Typically, residential
cable modems use the dynamic IP address assignment.
6. Select an identifier for the collector in the Collector number and Discovery
SNMP collector number lists. All elements and subelements discovered while
running this profile are assigned to this collector.
If you are importing a bulk file for a Bulk Collector inventory, ensure that you
select a valid Bulk Collector number. For more information, see the IBM Tivoli
Netcool Performance Manager: Installation Guide.
A network discovery is performed using the default collector that can later be
assigned to a secondary collector. Ensure that the default collector can reach
all nodes in the inventory.
7. In the Directory Configuration field, click Browse to g to the directory where
you want to write the files generated by the inventory process. The default is
the importexport directory where you installed Tivoli Netcool Performance
Manager 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 you
do 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 network
to include in the profile.
Synchronization
Lets you synchronize new data for your
profile with existing data.
Automatic Grouping
Lets you specify grouping rules for this
profile (default or custom).
See Chapter 4, “Creating grouping rules,” on
page 47 for step-by-step instructions on
creating 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 disable
one or more of the modules, the window sequence might differ.
Configuring your discovery
Explains how to use the Discovery Tool Wizard to specify what resources are
included in your network inventory profile.
To fully configure your profile, you must complete the tasks detailed in the
following sections.
Note: The window sequences displayed in the Discovery Tool Wizard might differ
according to the selections you made.
16
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Selecting your network discovery method
Explains how to specify the discovery method for your network. You can choose to
either discover network elements using SNMP requests, or import network
elements from a Domain Name Server (DNS), Network Information Service (NIS),
or host file.
Note: Ensure that a running collector is available in your environment before
selecting either the Discover elements & Analyze or Import elements & Analyze
options. No running collector is required for the import from ASCII file option as
the element and subelement files are produced by the bulk collector or an external
provisioning system.
Discovering network resources
About this task
To discover network resources, follow these steps:
Procedure
1. 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 a
large network.
This network discovery method uses SNMP Get commands to retrieve MIB
OIDs from target devices that are used to identify device types and their
characteristics.
2. Click Next. See “Specifying IP addresses” on page 18 to continue.
Importing network resources
About this task
To import network resources, follow these steps:
Procedure
1. 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 is
recommended for large networks.
If you import network resources and also list specific IP addresses (as
explained in “Specifying IP addresses” on page 18), Tivoli Netcool Performance
Manager discovers only elements that appear in both the imported list and the
list of specific IP addresses.
Note: The “Import elements & Analyze” mode must be used if you plan to
run the inventory profile using the subprofile option.
2. To import resources from a domain-based source, select one of the following
options:
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 Tool
displays the DNS in /etc/resolv.conf.
Chapter 3. Configuring inventory
17
v From NIS: lets you import elements by specifying a valid Network
Information Service (NIS) domain name. Specify the NIS domain name in the
box to the right. The Inventory Tool displays the result of the UNIX
command domainname if it is valid.
3. To import resources from a file-based source, select one of the following
options:
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 file
name of the input file.
v From elements list: lets you import elements by specifying a file. The file
contains a list of IP addresses with one address on each line. This file can be
a .txt file.
Note: The From elements list option must be used if you plan to run the
inventory 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 addresses
Explains how to include or exclude IP addresses from your network inventory
profile. The IP address options are displayed.
Procedure
1. 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 address
formats.
2. Click <<Add to add it to the list of IP addresses to include in the discovery, or
click 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 the
IP address entry box. Modify the entry in the IP address entry box, then click
Modify.
4. To delete an IP address: highlight it and click Delete. To delete all the entries in
the IP address include area, click <<Clear. To delete all the entries in the IP
address exclude area, click Clear>>.
5. Click the ARP Query (Address Resolution Protocol) option if you want to use
ARP 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.
18
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Defining an SNMP configuration
Explains how to use the SNMP Configuration Tool to define general parameters for
SNMP requests. The SNMP Configuration Tool is launched.
Procedure
1. Click Open for the SNMP Configuration Tool.
Note: You can also launch the SNMP Configuration tool from the command
line using the snmpconf command-line interface (CLI) command. See the IBM
Tivoli Netcool Performance Manager: Command Line Interface Guide for
instructions on using this CLI.
2. Click Apply Filter to list all of the elements currently in the SNMP
configuration database. The following information is displayed for each entry:
Item
Description
Name
Specifies the name of the device associated
with this SNMP configuration.
IP Address
Specifies the IP address, mask, subnets, or
address list for the device. Both IPv4 or IPv6
address formats are acceptable.
Type
Specifies the type of the device.
Read community
Specifies the name of the SNMP read
community.
Collector ID
Identifies the collector associated with this
SNMP configuration. A setting of 0 applies
the SNMP configuration to all collectors.
Write Community
Specifies the name of the SNMP write
community.
Timeout
Specifies the length of time (in seconds) to
wait for a response from a request.
Retries
Specifies the number of times that a request
is tried again in the event of a request
failure.
Port
Specifies the number of the port associated
with this SNMP configuration.
Bandwidth
Specifies the maximum amount of traffic (in
Kbps) permitted for the corresponding IP
address. For more information, see “SNMP
bandwidth control and collection
smoothing” on page 29.
Version
Specifies the SNMP version associated with
this 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 SNMP
Configuration: Add/Update Configuration window.
v Click Resolve to attempt to resolve the name in the Element field, and if
possible, update the IP Address fields accordingly.
Chapter 3. Configuring inventory
19
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 on
Profile 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)
Or
abcd:ef01:2345:6789:ABCD:EF01:2345:6789 (IPv6 address format)
v To specify a mask of IP addresses, enter the mask information in the IP
address 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 to
192.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:: to
2620:0:860:2:FFFF:FFFF:FFFF:FFFF
– To specify several IP entries for the same SNMP configuration, enter the
address information in the IP Address field with each entry separated by
semi-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 the
beginning of the Read Community field, while selecting Auto omits the
version prefix.
Note: The ReadCommunity field is automatically populated for the following
Version options and does not need updating:
SnmpV3-No-Auth
SnmpV3-Auth-MD5
SnmpV3-Auth-SHA
SnmpV3-Auth-MD5-Priv-DES
SnmpV3-Auth-SHA-Priv-DES
SnmpV3-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, the
corresponding version prefix must be used in the SNMP read community
name. The Read Community field takes the parameters from the following
controls and uses them to build the Read Community string:
v Security Name: Specifies the user name to be used for this SNMP V3
element
v Auth. Password: Specifies the password to be used for authentication
(MD5) for this SNMP V3 element.
20
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
v Priv. Password: Specifies the private password to be used with the
following Version options:
SnmpV3-Auth-MD5-Priv-DES
SnmpV3-Auth-SHA-Priv-DES
SnmpV3-Auth-MD5-Priv-AES
SnmpV3-Auth-SHA-Priv-AES
v Context Name: Specifies the context name to be used for this SNMP V3
element.
8. Specify the name of the SNMP write community in the Write Community
field.
9. Specify the length of time (in seconds) to wait for a response from a request in
the TimeOut field.
10. Specify the number of times that a request must be tried again in the event of
a request failure in the Retries field.
11. Specify the number of the port associated with this SNMP configuration in the
Port field. A setting of 0 indicates that this SNMP configuration applies to all
ports.
12. Specify the bandwidth limit for traffic (in Kbps) permitted for this SNMP
configuration 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 the
Collector ID list. A setting of 0 indicates that this SNMP configuration is
applicable to all collectors.
14. After specifying the SNMP configuration, click OK.
Specifying SNMP community names
Explains how to specify alternative community names, and determine if the SNMP
configuration 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:
Procedure
1. 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 to
specify 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 separator
character must be used to separate all of the options specified in the
community name. Typically, you use a ,(comma) character as the separator.
However, if the , (comma) character is used in any of the passwords, you
can substitute the comma with any other separator character (for example, /,
@, -, and so on).
Chapter 3. Configuring inventory
21
v option - Specifies one or more option keywords that define an SNMP V3
community string. Each option keyword is followed by an = (equals sign).
v value - Specifies a valid value for the specified option. The following table
lists the option keywords along with their associated valid values:
Option
Values
SecurityName
Specifies the user name to be used for this
SNMP V3 community name.
ContextName
Specifies the context name to be used for
this SNMP V3 community name.
AuthPasswd
Specifies the password to be used for
authentication (MD5) for this SNMP V3
community name.
EngineId
Specifies the value for the engine ID for this
SNMP V3 community name. This option
keyword is optional.
AccessMode
Specifies the level of security required for
this SNMP V3 community name. The
following are the valid values for this
option:
v
No-Auth - Indicates that this SNMP V3
community name is no more secure than
the community string provided in SNMP
V1 or SNMP V2c.
v
Auth-MD5 - Indicates that this SNMP V3
community name security level
corresponds to an unencrypted traffic,
authenticated with MD5 hash. Specifying
this value means that you must also
specify the SecurityName, ContextName,
and AuthPasswd options.
The following example specifies an SNMP V3 community name that uses an
MD5 authentication:
&V3,AccessMode=Auth-MD5
SecurityName=user2
ContextName=context2
AuthPasswd=1234567890abcdef
2. To modify an existing entry, highlight the entry so that it appears in the
Alternative community names box. Modify the entry in the Alternative
community 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 name
to update the community names in the SNMP configuration database with the
alternative community name for elements queried.
5. Click Next to proceed. You can specify which types of elements to include in
the discovery. The left pane displays all the known element types. The right
pane 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 Manager
Technology Packs; otherwise the Groups folder does not display any element
22
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
type subfolder. See the IBM Tivoli Netcool Performance Manager: Installation Guide
and IBM Tivoli Netcool Performance Manager: Pack Installation and Configuration
Guide for instructions on installing Tivoli Netcool Performance Manager
Technology 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 run
discovery against and not the entire tree.
c. Clear the Insert unknown elements option so that unknown element types
are excluded from the inventory. If you select this option, unknown
elements are included in the discovery and are added to a folder called
NONE.
6. Click Next to proceed. See “Specifying SNMP community names” on page 21
to continue.
Specifying an ICMP configuration
Explains how to specify Internet Control Message Protocol (ICMP) parameters for
your inventory profile.
Procedure
1. 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 can
be 1 - 64,000 bytes.
Tries
Number of times to ping specific IP
addresses if no response is received from the
ping. Your entry can be 1 - 10.
Time out
Length of time (in seconds) to wait for a
response to a ping before sending another
ping. The length doubles for each additional
ping.
For example, if the Timeout value is 5
seconds:
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) between
pings.
Chapter 3. Configuring inventory
23
Option
Description
Ping Window Configuration
Allows you to configure a pause when
sending pings to avoid congestion on the
network. If you do not select this option,
pings are sent equally spaced, without
pause, as specified by the Ping Interval.
v Window interval: Length of time (in
seconds) to pause in sending pings. Your
entry can be from 0.1 to 100 seconds.
v Window size: Number of pings to send
before pausing. Your entry can be from 2
to 65,000 pings. It can also be 0, which
disables the window. Using 0 is the same
as clearing Ping Window Configuration
option.
3. Click Next to proceed. See “Configuring labels for subelements” to continue.
Configuring labels for subelements
Explains how to configure labels (naming conventions) for subelements in your
inventory profile.
Procedure
1. Choose the type of element name you want to use. The following options are
available
Option
Description
Example
Subelement file and formulas Specifies which discovery file /opt/datamart/conf/
configuration
and formulas are used to
inventory_subelements.txt
perform the inventory
process.
Do not use element names
Name of the subelement is
used alone.
Dlci 10 (Cir 0 b/s)
Use element names
Name of the element is
concatenated with the name
of the subelement. This
option is enabled by default.
bost_Dlci 10 (Cir 0 b/s)
Use DNS element names
bost.forxh001.sample.fr_Dlci
Full DNS name of the
element is concatenated with 10 (Cir 0 b/s)
the name of the subelement.
If a DNS name is not found
then the IP address is used.
2. Click Next to proceed. See “Specifying synchronization” on page 25 to
continue.
24
Option
Description
Sub-element file and
formulas configuration
Specifies which discovery file /opt/datamart/conf/
and formulas are used to
.inventory_subelements.txt
perform the inventory
process.
Do not use element names
Name of the sub-element is
used alone.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Example
Dlci 10 (Cir 0 b/s)
Use element names
Name of the element is
concatenated with the name
of the sub-element. This
option is enabled by default.
bost_Dlci 10 (Cir 0 b/s)
Use DNS element names
Full DNS name of the
bost.forxh001.sample.fr_Dlci
element is concatenated with 10 .(Cir 0 b/s)
the name of the sub-element.
If a DNS name is not found
then the IP address is used.
3. Click the Next button to proceed. See See Specifying Synchronization to
continue.
Specifying synchronization
Explains how to specify the data source for the synchronization of your inventory
profile.
Procedure
1. 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 the
database.
v From file - Tivoli Netcool Performance Manager DataMart synchronizes the
results of this discovery with the data in the files you specify. Click Browse
to 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 resources
Explains how to add, remove, or update resources in your network inventory that
you created or changed since the last network discovery operation.
Procedure
1. 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 the
appropriate columns. The following actions are supported:
Selection
Description
New
Add resources found during the discovery
that do not exist in the current data.
Update
Update the existing resource data with data
found during the discovery.
Delete
Delete the existing resource data that is not
found 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 of
times previously existing resources that are not discovered are retried before
they are deleted from the network inventory.
Chapter 3. Configuring inventory
25
3. In the Specify the age for resources... area of the window, specify how long
previously existing resources that are not discovered are retained before they
are deleted from the network inventory.
Note: If the creation date or date of the last update for this resource is older
than the date specified, the resource is deleted. If the creation date or date of
the last update for this resource is more recent than the date specified, the
resource is not deleted.
4. Click Next to proceed.
Specifying automatic grouping
Explains how to group resources together automatically. When you use automatic
grouping, a link is created in the database for each resource that is included in a
group.
About this task
Regrouping the resources modifies these links; however, database changes for the
resources are not made. Default grouping rules are only provided if you installed
Tivoli Netcool Performance Manager Technology Packs. See the IBM Tivoli Netcool
Performance Manager: Installation Guide for instructions on installing Tivoli Netcool
Performance Manager Technology Packs.
You need to create custom grouping rules by using the Rule Editor in Tivoli
Netcool 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:
Procedure
1. 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 the
appropriate 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 and
groups. Does not add or delete any links,
but only updates existing links.
Delete
Deletes links between resources and groups,
which removes the resources from the
groups.
The grouping files for your profile are created in the $PVMHOME/importexport/
profilename/grouping directory.
2. Click Next to proceed.
26
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Specifying repository group rules
Explains 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 rules
that can be applied during the grouping operation. The Rules to be used for this
profile side of the window displays the grouping rules selected for the specified
profile. By default, Tivoli Netcool Performance Manager DataMart executes all of
the grouping rules during the grouping operation.
To specify repository group rules, follow these steps:
Procedure
1. Under the Repository group rules side of the window, click Unselect All.
Tivoli Netcool Performance Manager DataMart removes all of the grouping
rules 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 grouping
rules you want to apply from the Repository group rules side of the window
to the Rules to be used for this profile side of the window. Tivoli Netcool
Performance Manager DataMart refreshes the window to display the grouping
rules you selected.
3. To apply all grouping rules to your inventory profile, under the Repository
group rules side of the window, click Select All. Tivoli Netcool Performance
Manager DataMart refreshes the window to display all of the grouping rules
for the specified profile.
4. Click Next to proceed.
Selecting modules
Explains how to specify the modules that are run with your inventory profile.
Procedure
1. Select one or all of the following:
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 their
status to "active." See Chapter 4, “Creating grouping rules,” on page 47 for
details.
2. Click Next to proceed. This window displays a summary of the profile that you
created. Ensure that the profile contains the correct values. If you want to
change any of the values, click Previous to return to the appropriate window.
3. Click Finish to complete your profile. See “Running an inventory profile” on
page 28 for instructions on running your profile, or you can also run a profile
from the command line.
Chapter 3. Configuring inventory
27
Running an inventory profile
After you configure an inventory profile, you need to run it to perform a
discovery.
About this task
To run an inventory profile, follow these steps:
Procedure
1. 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 options
include the following:
Note: You can select or clear these check boxes to make immediate and
permanent changes to the database. For example, you might want to run just a
discovery for a bulk inventory. These options are also available when you
create 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 their
status to active. See Chapter 4, “Creating grouping rules,” on page 47 for
details.
Note: If you plan to use custom grouping rules, they must be created before
running the profile.
v subProfile option - Gathers information about listed network resources that
are imported from a file. The subProfile option is typically used to run a
discovery on a subset of the entire profile. This option can be used with
inventory profiles configured as described in “Importing network resources”
on page 17.
v Reload collectors - Reloads the collectors at the same time that the inventory
profile is run.
Important: The Tivoli Netcool Performance Manager default inventory
profile settings are used as examples. You must supply settings that are valid
for your network.
4. Select Run profile from the Actions menu.
The Live information tab displays messages about the status of the profile. The
messages are color coded as follows:
v Red - Error messages
v Blue - Warning messages
v Black - Informational messages
28
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Viewing the log file
The last line in the Live Information tab provides the path to the
TraceInventory.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 collectors
Each profile is assigned to a collector. If the resources included in the profile
change, you need to reload the collector, which updates the collector with the
changes. For optimal performance, you must always reload the collector after you
modify a profile.
About this task
To reload a collector, follow these steps:
Procedure
1. 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 but
profile is not run.
Deleting a profile
To 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 smoothing
The Bandwidth Control and Collection Smoothing features are used to optimize
the performance of SNMP collectors in your environment.
Before using Bandwidth Control and Collection Smoothing, you must consider
how these features function and how that might impact the operation of your
network.
Chapter 3. Configuring inventory
29
Bandwidth control
SNMP Bandwidth Control is used to prevent SNMP collectors from consuming
excessive bandwidth during periods of heavy network activity. The SNMP
bandwidth control feature defines a bandwidth limitation that allows you to
maximize the performance of the collectors without requiring an overly cautious
approach to collection management.
Bandwidth Control is configured by defining an SNMP configuration in Tivoli
Netcool Performance Manager DataMart. An SNMP configuration primarily
consists of a bandwidth limitation that is imposed on the specified collector for the
target IP addresses listed within the definition. Once defined, SNMP configurations
are propagated to the collectors during the Tivoli Netcool Performance Manager
processing cycle.
After the SNMP configurations are loaded, Bandwidth Control monitors outbound
traffic originating from the specified target IP addresses. Any collection request
destined for these target IP addresses is queried to determine if there is sufficient
bandwidth available to allow the collection to take place without exceeding the
defined bandwidth limit. If sufficient bandwidth is available, the collection request,
along with any similarly grouped requests, is permitted to take place. While
permitting grouped collection activity can cause a spike that exceeds the
bandwidth limitation for a short time (for example, 5 - 30 seconds), the bandwidth
limitation is enforced based on the average traffic monitored at the collector. Once
the bandwidth limit is reached, no collections are permitted to take place on that
portion of the network until the bandwidth utilization falls below the defined
threshold. If collection activity is suspended on any portion of the network due to
excessive bandwidth consumption, Bandwidth Control attempts to begin collection
on the next portion of the network.
Note: If several SNMP configurations and bandwidth limits apply to a set of IP
addresses, the lowest defined limit is used to control collection activity for the
collector. For example, if a bandwidth limit of 256 Kbps applies to the IP address
range 10.64.*.*, but another limit of 64 Kbps is defined for 10.64.1.*, then collection
activity on the collector is suspended if the network bandwidth exceeds 64 Kbps.
Configuring SNMP bandwidth control in DataMart
You can configure bandwidth control in DataMart using the SNMP Configuration
Tool as described in “Defining an SNMP configuration” on page 19.
Note: You can also configure SNMP Bandwidth Control using the CLI Utility. See
the IBM Tivoli Netcool Performance Manager: Command Line Interface Guide for
instructions on using this CLI.
Collection smoothing
Collection smoothing is used to prevent spikes in collector activity that occur at the
beginning of the polling period. Typically, the collector attempts to execute as
many collection requests as it can in the shortest time possible, which leads to a
pattern of a brief period of intense activity followed by an extended period of
sparse collection activity.
When enabled, collection smoothing imposes a bandwidth limit on the collector
that is based on monitored network activity. This bandwidth limit is dynamically
adjusted and serves to constrain the collector so that collection activity is
performed throughout the polling interval.
30
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Defining a collection smoothing period directs the collector to distribute collection
activity across a percentage of the polling period, which leaves the remaining time
available for other network tasks such as discovery activity. Care must be exercised
in defining this value as specifying too long of a collection smoothing period might
leave insufficient time to recover from unexpected issues and ultimately result in
lost collections. Similarly, as collection smoothing essentially delays collector
activity, you must consider that any network issues such as unexpected latency,
high traffic volume, or heavy processor bandwidth utilization might result in slips
in the collection schedule.
Note: If you intend on using collection smoothing with bandwidth control, the
lowest bandwidth limitation is used to control collection activity for the collector.
For example, if the bandwidth control limit is 64 Kbps and the dynamically
calculated collection smoothing limit is 100 Kbps, then collection activity on the
collector is suspended if network bandwidth exceeds 64 Kbps. To avoid collection
loss, ensure that bandwidth collection limits are not lower than the range of
bandwidth limits that are expected for collection smoothing activity.
Configuring collection smoothing in DataLoad
About this task
To configure collection smoothing in DataLoad, follow these steps:
Procedure
1. 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 Open
Topology 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 is
localhost.
v Port - The port number used for communication with the database. The
default value is 1521.
v Database user - The user name used to access the database. The default
value is pv_admin.
v Database Password - The password for the database user account. For
example, 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
Chapter 3. Configuring inventory
31
Where:
Parameter/Value
Description
AUTOSMOOTHING=false
The AUTOSMOOTHING
true
parameter enables Collection
Smoothing on SNMP
collectors. The parameter
must be set to true to activate
the feature.
SMOOTHINGSAFETYRATIO=75
The SMOOTHINGSAFETYRATIO
parameter determines how
collection activity is
distributed (in percentage of
time) throughout the polling
interval.
Recommended Value
75
The default, and
recommended, value of 75
specifies that collection
activity occurs over 75% of
the polling interval, leaving
25% of the time available for
other network tasks,
unexpected network
problems, and so on.
Using too high a setting (for
example, 95), might not leave
sufficient time for other
network events and might
result in lost collections.
SMOOTHINGCHECKFREQUENCY=60
The
SMOOTHINGCHECKFREQUENCY
parameter determines how
often (in seconds) dynamic
collection smoothing
requirements are
recalculated.
The default, and
recommended, value of 60
specifies that the dynamic
collection smoothing
requirements are recalculated
every 60 seconds. This value
is used to achieve the
greatest precision in the
calculation.
If less precision in dynamic
bandwidth control values is
required or processor usage
is too high, adjust the value
to a higher setting (for
example, 90 seconds).
32
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
60
Parameter/Value
Description
Recommended Value
DISCINITIALQUOTA=512
The DISCINITIALQUOTA
parameter determines the
initial value (in Kbps) for the
dynamic bandwidth control
limitation (in Kbps) for
discovery activity.
512
The default, and
recommended, value of 512
specifies that the initial
bandwidth limitation for
discovery is 512 Kbps. If
collections proceed smoothly
and there is a high level of
discovery activity, the
discovery limit is
automatically increased. If
collections are blocked, the
discovery limit is
automatically decreased or
put on hold until collection
activity is improved.
11. When you are satisfied with your settings, select Topology > Save topology to
save 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 dccmd
from a command line. See IBM Tivoli Netcool Performance Manager: Command
Line Interface Guide for more information.
Understanding file formats
Explains the formats required for the discovery files and the synchronization files.
See “Specifying synchronization” on page 25 for details about the synchronization
files.
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 only
subelements that have invariants. An invariant is a constant; it does not change.
v sub-element file without invariants - contains information about the
subelements that are synchronized with the results of the current discovery. It
contains only subelements that do not have invariants. An invariant is a
constant; it does not change.
Chapter 3. Configuring inventory
33
Element file
The fields for each element are separated by |_|. If a field has no value it must be
left empty: |_||_|.
An example of the correct format:
Note: The width of this page forces this example to wrap onto several lines. The
information 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 the
element.
127.0.0.1
Resolution of the largest IP address of any
interface 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 seconds
since 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 file
The fields for each subelement are separated by |_|. If a field has no value it must
be left empty: |_| |_|.
An example of the correct format:
Note: The width of this page forces this example to wrap onto several lines. The
information 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:
34
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Field
Value in Example
Invariant of the subelement. If the
subelement does not have an invariant, this
field 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 seconds
since 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 the
subelement 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 the
form "name|_|value".
Name of the property of the subelement.
State
Value of the property with the name in the
previous field.
active
Name of the property of the subelement.
Interface
Value of the property with the name in the
previous field.
1
Name of the property of the subelement.
DLCI
Value of the property with the name in the
previous field.
0
Name of the property of the subelement.
CIR
Value of the property with the name in the
previous field.
0
Managing dynamic changes
Explains how to ensure that Tivoli Netcool Performance Manager detects dynamic
changes, such as index shifting, and updates its state in real time. Doing so
prevents unreliable and incorrect information from being stored and minimizes
data loss.
Tivoli Netcool Performance Manager provides a method to automatically detect
and reconcile processing when resource invariants change in near real time. This
method, implemented in the CME, includes triggering inventory for the element
and updating a running system after information about that element is refreshed.
You can enable/disable collection on a subelement using a CME formula. You can
also start the Inventory for the element, to which the subelement belongs, when
that subelement becomes disabled. You do so by starting a CME formula designed
as an invariant check formula. This formula is based on the SNMP-collected
invariant for the subelement. When the invariant formula determines that a
property is changed (the index for example,) it disables the subelement. The CME
then determines to which element the subelement belongs and passes the element
to the appropriate Discovery server. This Discover server is co-located with the
Chapter 3. Configuring inventory
35
Inventory process running the element Inventory profile. The Discovery server
requests the Inventory to do a full reinventory for the specified element.
After the reinventory of the element is complete and the database is updated, the
SNMP Collector is reloaded and the subsequent flow of data to the CME corrects
itself. From this point on, invariant properties stop triggering reinventory requests.
Guidelines
You can associate a CME formula with an invariant property to create a formula
with two inputs:
v SNMP-collected invariant metric
v Invariant property
The formula needs to compare its two input arguments.
About the process
The following example illustrates the process by which the invariant management
occurs:
v As a result of Inventory, the subelement is assigned instance IF<1> and invariant
property 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.
36
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
v InventoryCheck formula compares collectedInventory metric and Inventory
property. 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 template
The following template:
^self
checkInvariant: (collectedInvariant ~= invariant)
old: <anOldValue>
new: <aNewValue>
Example based on process illustration
The following example includes a formula called InvariantCheck that takes the
following 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. The
formula returns a number (0 or 1). If output is 1, the invariant is valid, otherwise it
is 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 was
foo. Until this value is updated in the database, the value of the Invariant
argument for the formula for this subelement remains foo. At the same time, the
SNMP Collector keeps collecting collectedInvariant metric for this resource and
gets foo every time. When the CME processes this string record, the Invariant
formula compares its first and second arguments and uses the result of this
comparison to call checkInvariant. Until the collected invariant changes, this
argument remains true.
When an index shift occurs, the SNMP Collector (still using the old index) collects
a different value for the invariant (for example, bar.) When this string metric
record 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 is
false.
A sequence of corrective actions occurs. First, the CME marks this subelement
internal state as DISABLED. While disabled, no deployed CME formulas for this
subelement are evaluated and the metrics are dropped. The subelement locks out
all 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 to
ENABLED and to unlock the formulas, checkInvariant: with true must be called;
Chapter 3. Configuring inventory
37
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 performed
immediately (only when the subelement internal state changes from ENABLED to
DISABLED.) The CME locates the appropriate Discovery server and requests a
reinventory 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, the
SNMP Collector is reloaded. It now uses the correct instance to collect data from
the device, and the value of collected invariant metric becomes foo again. When
invariantCheck is evaluated, both collectedInvariant and Invariant arguments
are foo, so checkInvariant: is started with true. This switches the internal
subelement state to ENABLED, thus unlocking all the subelement formulas. This also
switches the internal state of the element to ENABLED. From that point on, if a
subelement of this element is disabled, it triggers another reinventory request.
Example for 2233_IF family
The following example is based on a profile called invTest, a property named
ifAlias, an SNMP Collection formula ifAlias, and a change in the value of the
ifAlias property.
Discovery formula
The 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 Formula
SNMP formula:
Name: ifAlias
Source:
ifAlias.%I1
SNMP collection requests:
Formula
ifAlias
ifAlias
38
Group
Interval in Minutes
Storage
Sub-Element
Collect~RFC2233~Frequent
5
No
Sub-Element
Collect~RFC2233~Normal
15
No
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
CME Formula
Use the CME invariant metric as the CME invariant formula input argument. The
formula must be associated with subelement invariant property and return either 0
or 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, the
subelement invariant is changed and it must be reinventoried. If the value is true,
the subelement is not changed.
CME formula for invariant check:
Name: invCheck
Input bindings:
collectedInvariant - String bound to ifAlias formula
invariantProperty - Property bound to ifAlias property
Source:
^self
checkInvariant: (collectedInvariant = invariantProperty)
old: invariantProperty
new: collectedInvariant
XML Source:
<formula genericId="100010591"><inputBinding
localName="collectedInvariant" metricId="100010506"
type="String"></inputBinding><inputBinding
localName="invariantProperty" metricId="100004697"
type="Property"></inputBinding><source>&#13;&#9;^self
checkInvariant: (collectedInvariant = invariantProperty) old:
invariantProperty new:
collectedInvariant</source></formula>
Requests for invariant check:
Formula
Group
Interval in Minutes
Storage
invCheck
Sub-Element
Collect~RFC2233~Frequent
5
No
invCheck
Sub-Element
Collect~RFC2233~Normal
15
No
CME processing
The results of starting checkInvariant include:
v Disables subelement if enabled
v Obtains subelement element
v Acts according to the following table
The following table lists the supported arguments:
Argument Value
Internal Element State
Action
Chapter 3. Configuring inventory
39
false
ENABLED
Obtain remote reference to
associated discovery server
Request reinventory of
specified element
Set element internal state to
DISABLED
false
DISABLED
No action
true
DISABLED
Set element internal state to
ENABLED
true
ENABLED
No action
In addition, the CME uses a timeout to periodically send reinventory requests to
the Discovery Server. This allows the Discovery Server to be relatively lax with the
requests. If a request was missed for any reason and reinventory did not happen
(for example, Discovery Server restarted), the request is repeated a few minutes
later.
Discovery server responsibilities
When the Discovery server receives reinventory request, it must run inventory
processing 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 policy
The 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 outcome
of every attempt. Change in the element internal state (between ENABLED and
DISABLED) are also logged. Target element is listed with each of these messages.
v Sends a log message for each element reinventory with the following
information:
– 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
40
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Configuring a bulk collector inventory
Explains how to configure a bulk collector inventory. Bulk collector inventory
profiles 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 on
importing files to a bulk collector, inventory file sets, polling commands, and
directories and file locations.
Important: IBM does not recommend changing the profile name or file names and
locations.
To configure a bulk collector inventory, follow these steps:
Procedure
1. Click Inventory Tool in the Resource tab.
Note: The Tivoli Netcool Performance Manager default inventory profile
settings are used as examples. You must supply settings that are valid for
your 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 discover
files only and insert new subelement from the bulk files into the Tivoli
Netcool 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 elements
from the database during the inventory by clearing all the “X” symbols from
the Delete column.
7. Click Next to proceed
Modify as needed. For example, you can choose not to update any existing
grouping links by clearing all the “X” symbols from the Update column.
8. Click Next to proceed
9. Click Next to proceed
10. Click Finish. See “Running an inventory profile” on page 28 for instructions
on running an inventory profile.
Chapter 3. Configuring inventory
41
Understanding a bulk collector inventory
This section explains the following:
v Importing files to a bulk collector
v Bulk collector inventory file sets
v pollinv and pollprofile commands
v Inventory polling and the cron table
v Directories and files
Importing bulk files
When bulk files are imported to the bulk collector, the collector creates resource
files that are sent to the $PVMHOME/importExportBulk/bulk_N/Do directory on the
DataMart machine, where N indicates the bulk collector number. Once the resource
files arrive in the directory, DataMart starts an inventory based on the gathered
data 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:
Procedure
1. 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 Tivoli
Netcool 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 Collector
installation, and $DC_HOME is equal to the path where you installed Data
Channel.
Resource files related to a Bulk Collector profile are stored into the same profile
directory on the DataMart machine. The name of the directory is the name of
the profile, for example, bulk_65.
Discovered resources are assigned to a profile of bulk_N and FTP to a
subdirectory of the same name. The pollinv command automatically creates a
profile with the same name.
42
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Bulk collector inventory file sets
For each inventory session, a Bulk collector creates one or multiple resource file
sets. 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 the
options 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 day
v 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 Do
and Done. During transfer staging, a bulk collector first copies the files into the do
directory. When the transfer is complete, the files are then moved from the Do
directory into the Done directory.
The following diagram illustrates the directory structure and data flow:
Chapter 3. Configuring inventory
43
pollinv and pollprofile commands
The inventory polling process uses the pollinv command, which is configured in
the machine cron and runs once an hour on the DataMart machine. The pollinv
command browses the importExportBulk directory for profiles, and launches the
pollprofile command, one per profile. The inventory command then inserts the
resources (metadata) from the file set into the Tivoli Netcool Performance Manager
database.
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 directory
v 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 the
number of file sets, all file sets that have the same arguments string are merged
together. This makes the pollprofile run faster. The files that do not have
special arguments files are assumed to have default arguments and are merged
together.
Log files for the pollinv command are located in $PVMHOME/log/
logFile.POLLINVENTORY.
Inventory polling and the cron table
The Tivoli Netcool Performance Manager DataMart setup program inserts the
following 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 Manager
DataMart is installed.
< 0 * * * * > is where you can change the frequency.
At every period configured, the system cron launches the pollinv command to
implement the inventory polling. The default period string is "0 * * * * " (this
specifies 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 modified
pollinv 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 "
44
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
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 Manager
DataMart. It is the location where the Bulk Collector pushes its profile
directories (and file sets inside the profile directories). This is also the source
profile 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 = the
bulk collector number (ID) that you specified during Bulk Collector installation).
All subelements created into the database using the current inventory profile are
assigned to this collector.
v Do - temporary directory used by the Bulk Collector when transferring files to
Tivoli Netcool Performance Manager DataMart. When the transfer is complete,
the Bulk Collector moves the files from this directory to the done directory. This
directory is created by the Bulk Collector.
v Done - source file sets directory for the inventory polling process (pollprofile
command). Each resources file set is composed of two types of files (element
and subelement). An optional file containing the inventory command arguments
(args) can be appended to the file set. After each successful inventory command
is run by the pollprofile command, the associated file set is deleted from this
directory. This directory and its file sets are created by the Bulk Collector.
v Dm - source file set directory for the inventory process (launched by the
pollprofile command). Each inventory launched using this profile get its source
files from this directory, and uses this directory as its working space. This is the
case whether the inventory is launched automatically (pollprofile) or manually
(by using the Inventory Tool or CLI). After each inventory (manual or
automatic), the last file set used is not deleted. Since this directory working
directory for the inventory command, it creates its working files and working
directories at <profilename>/grouping, <profilename>/ groupingWait,
<profilename>/inventory, <profilename>/synchro, profilename>/synchroWait.
These directories are created by the pollinv command.
Chapter 3. Configuring inventory
45
Bulk file format examples
Some bulk file format examples:
Element resources
The following is an example of an element.<suffix>.dat file:
# col = eprp.ipAddressMin:value eprp.ipName:value
eprp.sysName:value name date state encl.oid eprp.ipAddress:value
scf.rcommunity eprp.sysDescr:value collector profile
# filter =
# type = elt
10.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 resources
The following is an example of a subelement.<suffix>.dat file:
# col = invariant elt.name name date instance label state fam.name
seprp.name:name seprp.value:name#
filter =
# type = se
LPort<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 arguments
The following is an example of an args.<suffix>.dat. This file contains a single
line (no comments allowed). The content of the line is the options string to append
in the inventory command.
Example:
-reload 1 -action synchro
This means that the inventory reloads the collectors and perform only the
synchronization (no discovery or grouping).
46
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 4. Creating grouping rules
Explains how to create custom grouping rules to group and edit resources on your
network to use with your network inventory, data collection, and reporting.
Note: You can also import resources from the command line. For more
information, see the IBM Tivoli Netcool Performance Manager: Command Line Interface
Guide.
Note: For instructions on creating grouping rules for composite subelements
(CSEs), see the IBM Tivoli Netcool Performance Manager: Composite Subelement
Configuration Guide.
Before you begin
Before creating and testing grouping rules, you need to configure a network
inventory to add elements and subelements to the database, as detailed in
Chapter 3, “Configuring inventory,” on page 13.
Grouping acts like a taxonomy. The intent of grouping is to identify objects that
have a common set of attribute and property values, and to organize the objects in
a common place (by creating a group membership relation) expressing the
circumstance of satisfying the criteria for selection.
Grouping rules are organized hierarchically. Each level in the hierarchy is intended
to represent an incremental refinement in categorization. The first rule in a
grouping 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 a
branch intended to organize technologically would perhaps have rules to
discriminate by type of device. For example, router or switch. And the next level
might further classify in terms of device capacity, or capability.
A grouping rule is evaluated by the conjunction of all rule conditions defined
along a branch in the grouping hierarchy. Group membership is granted at the leaf
level, the most precise taxonomic location, when the complete condition of a
grouping rule (the aggregate of all conditions from root to leaf) is met.
Creating grouping rules
The "ruleconf" command-line interface (CLI) command launches the Rule Editor
from the command line.
About this task
For more information, see the IBM Tivoli Netcool Performance Manager: Command
Line Interface Guide.
To create rules, follow these steps:
Procedure
1. 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.
© Copyright IBM Corp. 2012
47
Note: For instructions on creating grouping rules for composite subelements
(CSEs), see the IBM Tivoli Netcool Performance Manager: Composite Subelement
Configuration Guide.
3. Expand the tree in the left pane and click the name of a rule to select it. This
rule must be at the level of the tree just above where you want to insert the
new rule.
4. Right-click and select New. Tivoli Netcool Performance Manager DataMart
inserts 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 name
can be either static text or a variable. You can drag the properties from the
Properties listbox to the Name box.
Note: Conditions are not allowed in the Name box. See “Using syntax for
grouping rules” on page 58 for more information.
6. Optional: In the Label text box, assign a label to the group. Labels are used as
an alias for group names, providing another level of abstraction. When
creating reports, Tivoli Netcool Performance Manager DataView first looks for
a 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 the
Operator listbox to the Condition box.
See “Using operators and functions” for details on operators and function
available 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. This
rule (and each rule below it within the tree) is ignored by the Inventory
Tool 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 the
properties you selected. Values for Type, Updated On, and Origin are filled
automatically 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
AND
Description
Joins two conditions. Resources are included
in the results if they match both conditions.
This operator has the same effect as creating
nested conditions.
For example:
%(Element.PROFIL) = `public’ AND
%(ifType) = `ethernetCsmacd’
Resources are included in the results if the
profile name is public and the ifType is
ethernetCsmacd.
48
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
OR
Joins two conditions. Resources are included
in the results if they match either condition.
For example:
%(Element.PROFIL) = `public’ OR
%(ifType) = `ethernetCsmacd’
Resources are included in the results if
either the profile name is "public" or the
ifType is ethernetCsmacd.
=
Tests if the variable is equal to a value. Use
this operator to test against only one value.
For example:
%(VENDOR) = `Cisco’
Resources with the vendor "Cisco" are
included in the results.
Use IN to test against a list of values. Use
LIKE 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 one
value.
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 a
wildcard (%).
<
Tests if the variable is less than the value.
Use this operator to test against only one
value. It does a comparison based on an
ASCII sort, if the value is enclosed in double
quotation marks. It does a comparison based
on a numeric sort, if the value is not
enclosed in double quotation marks. For
example:
%(Element.COLLECTOR) < 3
Resources with a collector number less than
"3" are included in the results.
Note: Do not use double quotation marks
for the collector number. The collector
number is an Int column in the database and
must 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 one
value. It does a comparison based on an
ASCII sort, if the value is enclosed in double
quotation marks. It does a comparison based
on a numeric sort, if the value is not
enclosed in double quotation marks. For
example:
%(Element.COLLECTOR) > 3
Resources with a collector number greater
than "3" are included in the results.
Note: Do not use double quotation marks
for the collector number. The collector
number is an Int column in the database and
must use a numeric comparison.
It is also possible to use >=.
IS NULL
Tests if the variable is NULL. For example:
%(FAMILY) IS NULL
Resources with the FAMILY property
"NULL" are included in the results.
IS NOT NULL
Tests if the variable is not NULL. For
example:
%(FAMILY) IS NOT NULL
Resources with the FAMILY property "not
NULL" are included in the results.
LIKE
Tests if the variable is equal to a value
containing a wildcard (%). For example:
%(ipAddress) LIKE `182.168.%’
Resources with IP address that begin with
182.168 are included in the result.
Use IN to test against a list of values.
NOT LIKE
Tests if the variable is equal to a value
containing a wildcard (%). For example:
%(ipAddress) NOT LIKE `182.168.%’
Resources with IP address that begin with
anything other than 182.168 are included in
the result.
Use NOT IN to test against a list of values.
50
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
IN
Tests 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 are
included in the result.
Use LIKE to test against a value with a
wildcard (%).
NOT IN
Tests 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 or
SLIP are included in the result.
Use NOT LIKE to test against a value with a
wildcard (%).
pub.PVM_TO_NUMBER
Casts a string to a number. Use this function
with operators such as < and > to perform a
numeric comparison rather than a string
comparison. Place the function before the
variable.
For example:
pub.PVM_TO_NUMBER(%(ifSpeed)) >
= 100000000
pub.FormatIP
Reformats an IP address so that each set of
numbers in the address contains three digits.
This is necessary to do an accurate
comparison. 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 includes
both the IP addresses 182.168.78.4 and
182.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 address
182.168.78.4, but not 182.168.78.48.
Chapter 4. Creating grouping rules
51
Using conditions
You can use any property in the database as a variable in a condition. A condition
can test against any value that is valid for the property.
To test against multiple values use the OR, IN, and LIKE operators. See “Using
operators and functions” on page 48 for more information.
The syntax for conditions is similar to SQL syntax. A condition has the following
format:
%(property) operator`value’
Part of Condition
Description
Syntax Requirements
%
Creates a variable from a
property.
No space between % and the
property.
property
Specifies the property to be
tested.
Parenthesis are required.
operator
Defines the relationship
Spaces before and after the
between the variable and the operator are recommended,
value. See “Using operators
but not always required.
and functions” on page 48
for more information.
value
Specifies the test.
v Single Quotation marks
are required around each
value for a string
comparison.
v Double quotation marks
around the values are not
allowed for a numeric
comparison.
Note: Do not use double
quotation marks for the
collector number. The
collector number is an Int
column in the database and
must use a numeric
comparison.
v If the condition tests
against a list of values,
parentheses are required
around the list.
v If the condition tests
against a list of values,
each value needs to be
separated by a comma.
Spaces before and after the
comma are optional.
v The value in the condition
needs to match the value
in the database.
Capitalization and
punctuation must be the
same.
You can nest conditions. For example:
52
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
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 the
lowest level of the tree is used by the Inventory Tool to create groups.
Using grouping rules
Explains how to use custom grouping rules after you create them.
About this task
To use grouping rules, follow these steps:
Procedure
1. 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: Command
Line Interface Guide for information about importing resources.
2. If you want to use properties that are not included with Tivoli Netcool
Performance Manager DataMart, create properties and add them to the
database. See Managing Resources in the IBM Tivoli Netcool Performance Manager:
Command Line Interface Guide for more information about adding properties to
the database.
Note: After you create properties, you must exit the Rule Editor and reopen it
for the new properties to appear.
3. Create grouping rules. See Chapter 4, “Creating grouping rules,” on page 47 for
details.
4. Run the Autogrouping option in the Inventory Tool Wizard to execute the
grouping rules. See “Configuring your network inventory” on page 13 for
instructions. Profiles created with the Inventory Tool Wizard use the grouping
rules that you create with the Rule Editor.
5. Use the groups to create collection requests. See “Configuring data collection
requests” on page 65 for information about using the Request Editor to create
requests.
Testing grouping rules
After you create custom grouping rules, you can test them using database
information.
About this task
To obtain database information configure an inventory to add elements and
subelements to the database, as detailed in “Configuring your network inventory”
on page 13. You can also import resources. See Managing Resources in the IBM Tivoli
Netcool Performance Manager: Command Line Interface Guide for details.
When you test a grouping rule, the results are displayed in a tree structure in the
Test Result tab.
Chapter 4. Creating grouping rules
53
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 resources
are included in the result and are grouped according to the different ifSpeeds of
the resources.
You can also nest variables. The results of nested variables are sorted according to
each variable. See “Creating variables” on page 58 for details. Only the result of
the 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 the
resources that match the condition are grouped together.
If you use a condition to filter according to :ifSpeed, only the resources that
match the condition are included in the result. Unlike with variables, all the
resources that match the condition are grouped together. They are not sorted
according to the different ifSpeeds.
Conditions can also be nested. A nested condition filters the results again. Only
resources that match all the conditions are included in the result. Only the result
of 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:
Procedure
1. 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. If
the 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.
Or
Display only the number of resources included in the group by clicking the
name 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 for
grouping rules” on page 58 for details.
Each property must have a default value. If an element has no value for a
property, and there is no default value for the property, then the element is not
included in the results for grouping rules that use that property.
54
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Saving test results
This saves the test results in a file. It does not save the results in the database. To
modify the groups in the database, run Automatic Grouping in the Inventory Tool.
Procedure
1.
2.
3.
4.
Test the rule as explained in “Testing grouping rules” on page 53.
Click the Save result in file button.
Specify a path and file name.
Click Save.
Copying grouping rules
Procedure
1. 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 rules
About this task
To move grouping rules, follow these steps:
Procedure
1. 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 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.
Chapter 4. Creating grouping rules
55
Deleting Grouping Rules
Procedure
1. 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 format
About this task
A file with the test results contains fields for the following:
v Path and name for the rule
v Identifier for the resource
v Database index for the rule
Each line of the file represents one resource. The fields are separated by |_|.
For example:
Viewing rule database information
Procedure
1. 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:
56
Parameter
Description
Heading
Path and name for the rule. The path
separator is a tilde (~).
dbIndex
Database index for the rule.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Name
Name of the rule.
type
Type of rule (static or rule).
cond
Condition for the rule. This is blank if the
rule does not have a condition.
state
Indicates whether the rule is used by the
Inventory Tool during grouping.
v on - indicates that the rule is used. This
corresponds to the Status: active in the
graphical user interface.
v off - indicates that the rule is not be used.
This corresponds to the Status: idle in the
graphical user interface.
date
Modification date as the number of seconds
since 1 January 1970.
origin
How the rule was created.
Viewing properties
Grouping 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 property
ifSpeed becomes the variable %(ifSpeed).You can use any property in the database
as a variable.
To view properties, follow these steps:
Procedure
1. Open the Rule Editor as explained in Chapter 4, “Creating grouping rules,” on
page 47.
2. Click the Rule Element tab if you want to view a description of a property for
an element.
Or
Click the Rule Sub-Element tab if you want to view a description of a property
for 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 you
can use them in a grouping rule. See Managing Tivoli Netcool Performance
Chapter 4. Creating grouping rules
57
Manager Objects in the IBM Tivoli Netcool Performance Manager: Command Line
Interface Guide for details on adding properties to the database.
Using syntax for grouping rules
Explains 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 page
64 for examples.
Using static text
Do not use the percent sign (%) in static text. It is reserved for creating variables.
You can use operators, which are treated as text.
Creating variables
You 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 and
dropping it in the Name box or the Condition box.
Note: Parenthesis around the name of the property are recommended, but not
required.
You can use variables without conditions in the Name box, but not in the
Condition box.
You can nest variables. The results of nested variables are sorted according to each
variable. See Chapter 4, “Creating grouping rules,” on page 47 for details. Only the
result 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 rules
You can use a text editor to create grouping rules. Using a text editor lets you
create grouping rules quickly because you can export the existing rules from the
Rule 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 rules
Procedure
1. 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.
58
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Importing grouping rules
Procedure
1. 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 format
The file format for a grouping rule file is the same for an import file and an export
file. You can export the rules from the Rule Editor, edit the file in a text editor, then
import 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 |_|. For
example:
Grouping rule example
This example illustrates grouping rules containing:
v
v
v
v
Name with static text
Name with a variable
Nested variable
Condition
Chapter 4. Creating grouping rules
59
Name with static text
To 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. The
results for this example are the ROOT.
Name with a variable
To 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.
60
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Nested variable
To 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 according
to 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 to
create groups. See “Specifying automatic grouping” on page 26 for more
information.
Condition
To 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, the
greater 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 numeric
comparison rather than an ASCII comparison.
The test results are sorted according to a collector and are then filtered according
to interface speed. Resources are only included in the test results if the interface
speed is more than 100 Mbps. Resources with a slower interface speed are ignored.
Chapter 4. Creating grouping rules
61
Example of nested conditions
This example illustrates nested conditions.
Condition
To 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. Subelements
are only included in the test results if they are active. Inactive subelements are
ignored.
Nested condition
To 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 numeric
comparison rather than an ASCII comparison.
62
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
The test results are filtered according to the state, and are then filtered according to
interface 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 condition
To 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 to
interface speed, and then filtered according to interface type. Resources are only
included in the test results if they are active, and the interface speed is less than
100 Mbps, and the interface is either PPP or Frame Relay. Inactive resources are
ignored. Resources with faster interface speeds are ignored. Resources with other
types of interfaces are ignored.
The results include resources that are either PPP or Frame Relay. The results do not
specify the interface for each resource.
Variable
To 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 to
interface speed, then filtered according to interface type, and finally sorted
according to interface type.
The list of resources is the same as before, but are sorted according to interface
type.
Chapter 4. Creating grouping rules
63
Only the result of this lowest level of the tree is used by the Inventory Tool to
create groups. See “Specifying automatic grouping” on page 26 for more
information.
Example of combining text, a variable, and a condition
This 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 to
interface type. The text is included in the display of the results.
64
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 5. Collection and aggregation
Explains how to collect and store network performance and service analysis data
for monitoring subelements on your network using SNMP, Bulk, and Complex
Metric formulas. It also explains how to configure aggregation requests and
percentile information for presentation in reports.
After collection, and possibly aggregation, this data can be integrated into Tivoli
Netcool Performance Manager DataView or the reporting tool of your choice.
Before you begin
Before 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 requests
Explains how to configure data collection requests for the subelements in your
network. Results of the data collection are stored in the Tivoli Netcool Performance
Manager database for use in reporting.
About this task
In addition to the Request Editor, you use the following Tivoli Netcool
Performance 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.
Procedure
1. 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 have
timezones attached to them.
3. Go to the collection group you want by expanding the top-level folders to
locate the group.
4. Click the + sign next to AP in the Formulas pane to expand it and display the
formula 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 7
before clicking Save.
© Copyright IBM Corp. 2012
65
Setting the collection period
You can set the time you want data collection to run in the Details area of the
Collection tab.
Procedure
1. 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, repeat
steps 1 through 3 before clicking Save.
Configuring aggregation requests
Explains how to configure aggregation requests and percentile values.
Procedure
1. 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 timezones
associated with them.
3. Go to the report group you want by expanding the top-level folders to locate
the group.
4. Click the + sign next to AP in the Formulas pane to expand it and display the
formula groups.
5. Go to the formulas you want to apply to the data collection. Aggregation is
usually against generic formulas.
6. Select the formulas pressing Ctrl or Shift while clicking to select
non-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 clicking
Save.
Configuring a percentile value
You can use a percentile value instead of the average or max statistics to better
represent a metric that includes the occasional burst or spike. Occasional bursts or
spikes render a min or max value meaningless, and throw off average and mean
calculations. In these cases, using a percentile calculation allows you to see more
accurately how the metric is performing over time. Percentile values are applied to
raw data.
Procedure
1. 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 request
table.
66
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
3. 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 clicking
Save.
Filtering requests
Explains how to filter the requests displayed in both the Collection and
Aggregation tabs. The Request Editor displays a filtering toolbar that's the same on
both tabs.
The filter expressions are applied to the requests displayed in the table. The
column heads effected by the expressions change to reflect the filter applied.
Sorting columns
You can click column headings to sort the contents. A single click to a column head
changes the order which the line items in the request table are displayed. A second
click reverses the order.
Validating the requests
Explains how to validate all the Collection and Aggregation requests. Click Save
after creating or modifying a request to make the system validate all requests, even
those populated by other tools.
Chapter 5. Collection and aggregation
67
68
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
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 SNMP
collection time period.
IBM recommends that you collect data on a 24 x 7 basis, which is the default
collection period in the Request Editor. For more information, see “Configuring
data collection requests” on page 65.
You use a calendar to define periods for SNMP data collection. For example, you
can stop SNMP data collection times for a customer site that is closed for business
and the network is not being used (no data collection before 8:00 a.m. or after 8
p.m.). This is known as planned outage for Service Level Agreement purposes. The
Service Provider has no obligation to the customer during a planned outage.
Using the Calendar Configuration Tool
About this task
The Calendar Configuration Tool provides calendars to use with Tivoli Netcool
Performance Manager DataMart data collection requests.
Note: The calsel command-line interface (CLI) command launches the Calendar
Selector from the command line. The calconf CLI command launches the
Calendar Selector from the command line. For more information, see the IBM Tivoli
Netcool Performance Manager: Command Line Interface Guide.
To start the Calendar Configuration Tool, follow these steps:
Procedure
1. Click Calendar Configuration in the Configuration tab. The Calendar
Configuration Tool dialog box appears
2. TheCalendar Configuration Tool lets you create your own calendar from
scratch. For more information, see “Creating customized calendars.”
Creating customized calendars
Explains how to create customized calendars for scheduling data collection.
About this task
When creating a custom calendar for an SNMP data collection request, be aware
that if you apply to a CME formula data collection request using Resource
Manager, it has the opposite affect.
For example, if you create a calendar for a planned outage that collects data from 8
a.m. to 8 p.m. on Tuesday, if applied to the CME, it doesl not collect data from 8
a.m. to 8 p.m. on Tuesday. The CME expresses outages in this way.
© Copyright IBM Corp. 2012
69
IBM recommends that you use the CME Permanent calendar for all Bulk file/CME
formula data requests. The CME Permanent calendar is a 24 x 7 calendar that
collects data every hour on a daily basis from 0:00 to 23:59 (12:00 a.m. to 11:59
p.m.)
To create a custom calendar, follow these steps:
Procedure
1. 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 a
guide.
70
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
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
+11
Magadan, Solomon Island, New Caledonia
+12
Auckland, Wellington, Fiji, Kamchatka,
Marshall Island
Creating a one-time calendar
Explains how to configure a calendar to run once within your local time zone. For
example, 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:
Procedure
1. 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 collection
from 6 a.m. to 5 p.m.
3. Click a date list to specify dates for the collection (day-month-year format). A
calendar pop-up window appears.
4. Double-click a specific day.
Note: The time and date are based on the date and time properties of your
computer.
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 calendar
You can schedule daily data collection.
Procedure
1. 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 data
collection from 6 a.m. to 5 p.m.
5. Click OK to accept your selections.
Chapter 6. Configuring calendars
71
Creating a weekly calendar
Explains how to create a weekly calendar to use for SNMP and bulk file data
collection. A calendar for a data request that uses a bulk file works inversely from
a calendar for an SNMP data request.
About this task
To schedule weekly data collection, follow these steps:
Procedure
1. 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 a
weekly 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 this
button disables the default setting, which is to collect data every hour (12:00
a.m. to 11:59 a.m.) For example, you can choose to collect data from 8:00 a.m. to
8 p.m. (08:00 to 20:00).
Or
v 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 data
every hour on Monday, Wednesday, and Friday (includes - ON).
If you apply it to a bulk file/CME formula data collection request, it collects
data on Tuesday, Thursday, Saturday, and Sunday. It does NOT collect data on
Monday, Wednesday, and Friday (excludes - OFF).
Creating a monthly calendar
You can schedule monthly data collection.
About this task
To schedule monthly data collection, follow these steps:
Procedure
1. 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 in
which you want to end data collection. For example, from the first day of the
month 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.
72
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
7. Click OK to accept your selections.
Deleting a calendar
Procedure
1. 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 Selector
You can load a calendar that already exists in the database from the Calendar
Selector.
About this task
To select a calendar, follow these steps:
Procedure
1. 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
74
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 7. Writing custom formulas
Explains how to create and modify custom formulas.
You use the following Tivoli Netcool Performance Manager DataMart modules to
create 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 begin
Ensure 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 language
developed by IBM Corporation. A formula is a collection of object identifiers
(OIDs,) functions, and standard mathematical operations applied to a subelement
to perform a computation. A formula lets you customize the information gathered
by 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 against
hosts only (not against subelements) and are designed to return a list of results.
Discovery formulas collect information using OIDVAL()functions and store the
values into Vxx vectors. The last lines in the Discovery formula are the ones that
send results to the Inventory.
Discovery formulas for most interfaces are already included with Tivoli Netcool
Performance Manager DataMart. You can write a new discovery formula to
include a device that is new to the market.
v Collection formulas are used by the Request Editor to collect information about
the status of various devices in the network. Collection formulas are applied
against a subelement to produce a result (string or numeric) that is saved in the
database. There are numerous collection formulas included with Tivoli Netcool
Performance Manager DataMart; however, you can write additional formulas for
a customized collection process.
© Copyright IBM Corp. 2012
75
Merging discovery results
You can create Discovery formulas that merge results to create a unique
subelement. Instead of creating one large Discovery formula, you can create
multiple smaller Discovery formulas that can run sequentially with the results
being merged if a common key (formed by the pair of element name and
subelement instance field) is detected.
About this task
The process of creating multiple Discovery formulas that can be used for the merge
process includes creating one base formula and multiple expansion formulas to use
with the base.
v base formula: the main formula that discovers the subelement along with basic
properties
v expansion formula: additional formulas that define and populate additional
properties for the subelement
The merge process applies to the following three fields:
v SubElement Label
v Properties
v Invariant
The merge occurs between the version of a subelement produced by a Discovery
formula (the base formula) and already stored in memory and the more current
version of that subelement returned by a subsequent Discovery formula (expansion
formula.).
You add the merge capability to Discovery formulas by including one of the
following characters as the initial character in the SubElement Label, Property, and
Invariant fields.
v * (asterisk) value of current version of the subelement always overwrites
previous value
v + (plus sign) value of the current version of the subelement overwrites previous
value if the previous value was empty or missing
v - 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 using
these characters when creating formulas.
Note: Do not use any of these characters as the initial character when naming a
SubElement label, Property, or Invariant.
The character is removed by the Discovery server before the production of the file
for the Inventory process.
76
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Creating formulas
You can create custom formulas to use for discovery and data collection in
addition to the formula library included with Tivoli Netcool Performance Manager
DataMart.
For example, if you want to know the number of IP packets discarded on a host
from MIB-II, you would use this formula:
ipInDiscards.0 + ipOutDiscards.0
where ipInDiscards.0 is the number of incoming discarded IP packets and
iPOutDiscards.0 is the number of outgoing discarded IP packets.
A valid formula needs to have a MIB that is compiled in Tivoli Netcool
Performance Manager DataMart. Without a valid MIB, the formula returns an error
message to the request.
Editing the inventory_subelement.txt file
When you create a Discovery formula, you need to edit the
Inventory_sublement.txt file to include the formula so it can be used by the
Inventory tool. The Inventory_sublement.txt file lists the rules that Discovery uses
and you need to create rules for any Discovery formulas you create.
About this task
To create a formula, follow these steps:
Procedure
1. 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 management
protocol that is used to monitor routers and attached networks. SNMP is an
application layer protocol. Information about devices managed is defined
and 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 or
an object.
MOD
Takes the modulus of an expression
(remainder from the full division) or of an
object. This function is typically used with
the INT function.
LN
Takes the Naperian logarithm of an
expression or an object.
LOG
Takes the decimal logarithm of an
expression or an object.
e*
Takes the exponential of an expression or an
object.
10*
Takes 10 to the power of an expression or an
object.
Chapter 7. Writing custom formulas
77
Function
Description
INT
Converts the value of an expression or an
object into an integer value.
LAST
Displays the previous measurement value.
∆ (delta)
Displays the difference between the last
measurement and the previous one (x last(x)). Results are always positive. This
function is used for data whose value
increases after reaching a maximum peak.
This function is typically used for "counter"
type MIB data.
DIFF
Displays the difference between the last
measurement and the previous one (x - last
(x)). Results can be negative. This function is
typically 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 Data
of Formula box to create a formula. Many of these functions are also available
as 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 is
4000.
6. Select File > Save to save your formula in the database.
Testing formulas
You can test a formula after you create it. This step is important to ensure that the
formula is valid.
About this task
Note: The Resource field accepts both IPv4 and IPv6 IP address formats.
To test a formula, follow these steps:
Procedure
1. 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 Ethernet
formula requires a target with an ethernet interface. A token ring formula
requires a target with a token ring interface.
4. Click the refresh button to update this listbox with available resources.
78
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
5. Specify an instance from the Instance box. For example, a single instance such
as 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 the
Instance 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 Manager
DataMart uses the default instances specified in the formula, and inserts them
into 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 associated
collector appears by default.
8. Click Test to test the validity of the formula. The selected target and
community 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 is
active. The numerical results of the test are displayed.
If the test failed, an error message is displayed. For example, the message
might tell you that no data was found.
9. Right-click the Trace > Reset to clear the Trace box or select Save to print the
results or save them to a file.
Saving formulas
When you save a formula, Tivoli Netcool Performance Manager DataMart searches
all the MIBs that have been compiled. It creates a link from the formula to the
compiled 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 must
specify which MIB should be used. Tivoli Netcool Performance Manager DataMart
automatically displays a list of MIBs in the MIB Selection window. Click on the
desired MIB, then click OK.
You can view the details of any of the MIBs by using the MIB Browser. For more
information 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 Instance
and Label Inventory" branch of the formula tree. Before the formula can be used
automatically by the Inventory Tool, the path to the formula must be specified in
theinventory_subelements.txt file. This file can only recognize a location within
the "Alias Instance and Label Inventory" branch of the formula tree.
Chapter 7. Writing custom formulas
79
Modifying a custom formula
You can modify an existing formula by using the Formula Selector.
Procedure
1. Select File > Load. The Formula Selector dialog box appears.
2. Expand the branches and select the formula you want to modify and click OK.
Or
3. 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 formulas
Describes 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 must
be on one line. Long lines cannot wrap. The lines of a formula are processed
sequentially. There are no statements such as loops, switches, or cases.
Dim declaration
The Dim declaration defines the format of an input variable. If the formula
requires more than one input variable, there must be a separate Dim declaration
for each input variable.
The syntax is:
Dim <Var> As <Type> [Default <val>] [Name <label>];
80
Part of Formula
Purpose
Syntax Requirements
Dim
A keyword to indicate that
an input variable is being
declared.
Not case-sensitive.
Var
The input variable.
As
A keyword to indicate that
the data type of the input
variable is being declared.
Type
The data type of the input
variable.
Default
A keyword to indicate that
default instances are being
declared.
Part of Formula
Purpose
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Must be of the form "I1", "I"
must be capitalized, and
must be followed by a
number.
Not case-sensitive.
Not case-sensitive. The valid
types are listed in “Instance
variables” on page 86.
Optional, not case-sensitive.
If both the Default and
Name parameters are used,
the Default parameter must
come before the Name
parameter.
Syntax Requirements
val
The instances to use if no
other instances are specified.
Default instances can be a
list of values
- or * to indicate that all instances
must be used.
See “Instance variables” on
page 86 for more information
about the format for default
instances.
Name
A keyword to indicate that a
name for the input variable
is being declared.
label
The name to use for this
Can contain only letters and
input variable in the instance numbers; spaces are not
field of the Formula Editor.
allowed.
;
Indicates the end of the line.
Optional, not case-sensitive.
If both the Default and
Name parameters are used,
the Default parameter must
come before the Name
parameter.
Required for every line of
the formula, including
comments.
Every formula must begin with a Dim declaration. This allows the formula be used
with 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 recommends
that you use the first method.
There is only one type of formula that does not require a Dim declaration. If the
formula is applied to a scalar object (which therefore has only one instance), the
Dim declaration can be omitted. In this case, the instance is specified as "0".
For example:
sysName.0
Chapter 7. Writing custom formulas
81
OIDVAL expression line
The OIDVAL expression line executes an expression based on OIDs or statistics
variables 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 OIDs
required for the execution of the <Expression.> It retrieves the list by replacing all
variables contained in the <Expression> with their substitution values. All
substitutions must be resolved in order for the <Expression> to be obtained.
Depending on the Validity settings, the different OIDs and stats variables are either
restored from preceding executions or are queried from target devices.
The following table lists the syntax requirements:
Part of Formula
Purpose
Syntax Requirements
Vn
A temporary variable.
=
Indicates that the result of
the expression on the right
must be assigned to the
temporary variable on the
left.
Spaces before and after are
optional.
OIDVAL
A keyword that indicates
that the value of an
expression is being assigned
to a temporary variable.
Not case-sensitive.
Expression
The expression; the
calculation to be done.
Must be of the form "V1",
"V" must be capitalized, and
must be followed by a
number.
Contains at least one OID
(MIB object with a fixed
instance or MIB object with a
variable instance) stat
variable, or mathematical
operation.
The expression can be simple
or complex, and can include
more than one OID. The
expression must be enclosed
in parentheses.
Part of Formula
82
Purpose
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Syntax Requirements
Validity
Specifies how often to
re-evaluate the expression.
The choices include:
v Once, evaluate the
expression only at the first
polling.
v Every, evaluate the
expression at each polling.
This is the default.
v xxP, evaluate the
expression at a specified
number of pollings. For
example, 10P means
re-evaluate the expression
on each 10th polling.
v ssss, a specific period, in
seconds. For example, 3600
means re-evaluate the
expression once each hour.
;
Indicates the end of the line.
Required for every line of
the formula, including
comments.
Example
Dim 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
Æ
(int) 195.31
This produces the following result:
result
[I1 = (int) 2]
Stored in V1, for future use.
OIDINST instruction
The OIDINST expression line stores the values of a key for which the expression is
true (different from zero.) The instruction is primarily used for Discovery formulas
to filter a subset of indexes from a large set, based on properties. If the filter is
unsuccessful, the row is skipped. If the filter is successful, the value of the index
for the row is assigned to the temporary variable, and processing continues with
the next line of the formula.
The syntax is:
Vn = OIDINST(<Boolean Expression> [, Validity]);
Chapter 7. Writing custom formulas
83
Part of Formula
Purpose
Vn
A temporary variable.
=
Indicates that the result of
the expression on the right
must be assigned to the
temporary variable on the
left.
OIDINST
A keyword to indicate that a
conditional filter is being
used.
Expression
The expression to be filtered.
Syntax Requirements
Must be of the form "V1",
"V" must be capitalized, and
must be followed by a
number.
Spaces before and after are
optional.
Not case-sensitive.
OID, stat variable, or
mathematical operations
with a Boolean result.
Valid operators for filtering
are:
like, <, >, <=, >=, ==, !=
More information about
these operators can be found
in “Syntax for functions” on
page 88.
Part of Formula
Purpose
Syntax Requirements
Validity
specifies how often to
re-evaluate the expression
The choices include:
v Once, evaluate the
expression only at the first
polling.
v Every, evaluate the
expression at each polling.
This is the default.
v P, evaluate the expression
at a specified number of
pollings. For example, 10P
means re-evaluate the
expression on each10th
polling.
v A specific period, in
seconds. For example, 3600
means re-evaluate the
expression once each hour.
;
84
Indicates the end of the line.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Required for every line of
the formula, including
comments.
Example
V1=OIDINST (ifStatus.%1 like `up’)
Based on substitutions of I1 and SNMP query, the SNMP stack returns the
following:
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 produces
following 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 V1
vector, 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 way
as an Ix variable, because it has no dimension and that supports multiple possible
substitutions.
This OIDINST operator only works when the index is composed of only one
dimension. If the index comprises more than one dimension, all substitutions
values are concatenated and separated by character dot. Types of each dimension
are 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 than
benefits. 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 way
as an Ix variable, because it has no dimension and that supports multiple possible
substitutions.
This OIDINST operator only works when the index is composed of only one
dimension. If the index comprises more than one dimension, all substitutions
values are concatenated and separated by character dot. Types of each dimension
are lost and the resulting type of V1 variables is string (this is default type, when
Chapter 7. Writing custom formulas
85
no explicit type is declared). Not using explicit types has more side effects than
benefits. 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 one
dimension 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 variables
Formulas can include the following three classes of variables:
v instance
v temporary
v host
In most cases, these variables are actually vectors.
Instance variables
Instance variables represent the input values for a formula.
They are declared as a capital I, followed by a number (single digit) between 1 and
9. 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 Editor
v Assigning a subelement to a request using the Request Editor
The instance field is an ASCII string, which must be constructed as the following
sequence:
[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 for
replacement of
To use the value of the instance variable in a formula, add %:
86
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
%I1, %I2, %I3, and so on.
Only values whose responses do not return errors are retained for interpreting the
remaining lines of the formula.
The valid types for an instance variable correspond to SNMP types. They are:
v
v
v
v
v
v
v
Integer
IP address
Gauge
Counter
MacAddress
OctetString
DisplayString
v 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 must
be used. Spaces are not allowed within a list of values for an instance variable.
These are valid:
v integer, for example: 3
v list of integers, for example: 1,3,6,9,8,109
v interval, for example: 4-59
v list of integers and intervals, for example: 1,3,6,9,8-96,109,200-250
v character string, enclosed in double quotation marks, for example: "this is a
STRING"
v pointer to a string, for example: 128.3.56.7
v wildcard: *
Temporary variables
Temporary variables hold an intermediate SNMP result or a partial result. You do
not need to use temporary variables in a formula. Only use temporary variables in
a collection formula when strictly required, because of the possible performance
impact.
These temporary variables can be used as parameters for subsequent queries. They
are 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 assigned
automatically as the type of the variable. The previous contents of the variable are
overwritten 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.
Chapter 7. Writing custom formulas
87
Host variable
The host variable (Hx) represents the current host name.
Because multihost formulas are not supported, the only instance of this variable is
H1. You can set the value by using the Formula Editor, by setting a target element
or subelement for test, or by defining a target in the Request Editor table.
Returning a result
Only the result of the last line of a formula is returned. This was illustrated in the
example formulas. Prior lines made calculations, and manipulated variables, but
only the last line returned a result.
The MIB objects returned by the last line of a discovery formula become properties
in 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 grouping
rules,” on page 47.
Comments in formulas
To add comments to a formula:
v put each comment on a line by itself
v 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 functions
The Formula Editor includes the following function options.
Mathematical functions
Function
+
Description
Addition
The plus sign can also be used to indicate
merging preference for a Discovery formula
that the value will only overwrite previous
content if the previous content was missing
or empty.
-
Subtraction
The minus sign can also be used to indicate
merging preference for a Discovery formula
that the value will only overwrite the
previous content if the previous content was
missing.
88
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Function
*
Description
Multiplication - you need to add a space
before each * (multiply star) for the formula
to be correctly parsed.
The asterisk, or multiply star, can also be
used to indicate merging preference for a
Discovery formula that the value will always
overwrite the previous content.
/
Division
%
Returns the remainder of an integer division
<
Less than, the same as in the C
programming language
<=
Less than or equal to, the same as in the C
programming language
>
Greater than, the same as in the C
programming language
>=
Greater than or equal to, the same as in the
C programming language
==
Equal to, the same as in the C programming
language
!=
Not equal to, the same as in the C
programming language
Int()
Returns only the integer part of the
expression
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 nearest
multiple of significance
Other functions
Function
Description
&&
Logical AND
||
Logical OR
like
Performs an ASCII comparison of two
arguments. Wildcards can be used in the
right-hand argument. For example, to test
the start of a sysObjectID compared to a
vendor, without going into the model
details.
Not()
Negates the expression; provides the
opposite.
Chapter 7. Writing custom formulas
89
SNMP-specific functions
Function
delta()
Last()
Diff()
Description
Calculates the difference between the value
retrieved during this polling and the value
retrieved during the previous polling for a
single SNMP variable. This difference can
only be positive because these variables
must be counter variables. This function
manages counter overflows and resets.
Returns the value assigned to this expression
during the previous polling.
Returns the difference between the current
value of this expression and its value for the
previous polling. This value can be positive
or negative.
These functions cannot be nested.
Aggregate functions
For these functions, the expression defines an operation. The dimension specifies
the variable used as an index for that operation.
Function
Sum (Dimension, Expression)
Description
Returns the total of all values. For example:
Sum (*, ifInOctets.%I1)
provides all octets entered on all the
interfaces.
Max (Dimension, Expression)
Returns the highest value encountered. For
example:
Max (*, ifInOctets.%I1)
provides the number of octets entered on the
interface with the highest number of
incoming octets.
Min (Dimension, Expression)
Returns the lowest value encountered. For
example:
Min (*, ifInOctets.%I1)
provides the number of octets entered on the
interface with the lowest number of
incoming octets.
90
Count (Dimension, Expression)
Returns a count.
Ave (Dimension, Expression)
Calculates the average.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Filter functions
Function
Description
FirstN (Number of items, Expression)
Retains only the N lines with the highest
result.
LastN (Number of items, Expression)
Retains the N lines with the lowest results.
Filter (Expression)
Retains only the lines with a true result. In
normal use, the expression is a Boolean that
returns 1 (true) or 0 (false).
Distribution function
This function specifies the distribution of results within a formula. It provides a
quantified, non-linear numerical result. For example, you can assign values such
as:
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 the
result 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 either
the specified value, or * to keep the initial value.
The Definition string must be enclosed in double quotation marks. It is evaluated
from left to right. As soon as a condition is true, the corresponding value is
returned. If no conditions are true at the end of the string, then no value is
returned. 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 to
wrap onto three lines in this example, when using the Formula Editor each line of
a formula must be on one line. Long lines cannot wrap.
Chapter 7. Writing custom formulas
91
AddForMissing() operator
This operator allows extending the size of a result set and adding news results
entries by using entries and dimensions from a reference vector. The only
prerequisite is that both the expression, and the reference vector have the same
dimensions set.
addForMissing ( Expression , reference Vector [, default
replacement ] )
The result of the operator is an extension of Expression. For each dimension entry
that is present in reference Vector only, a new dimension entry is added to
Expression, using either the result in the reference vector, or the default
replacement submitted
Example
Expression 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,) has
the 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) were
not defined in the original result set, and creates entries for them.
If no default Replacement is provided, corresponding results from Reference vector
are used. This generates the following result:
result
92
[I1 = (int) 1]
Æ
(int) 10 // from
Expression
[I1 = (int) 2]
Æ
(int) 21 // from
reference vector
[I1 = (int) 3]
Æ
(int) 30 // from
Expression
[I1 = (int) 4]
Æ
(int) 40 // from
Expression
[I1 = (int) 5]
Æ
(int) 51 // from
reference vector
[I1 = (int) 6]
Æ
(int) 61 // from
reference vector
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
If a default Replacement is provided, this default value is inserted for all new
entries. This generates the following result:
result
[I1 = (int) 1]
Æ
(int) 10 // from
Expression
[I1 = (int) 2]
Æ
(int) default value
[I1 = (int) 3]
Æ
(int) 30 // from
Expression
[I1 = (int) 4]
Æ
(int) 40 // from
Expression
[I1 = (int) 5]
Æ
(int) default value
[I1 = (int) 6]
Æ
(int) default value
Using the Formula Selector
You 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 to
launch the Formulas Selector from the command line.
Creating a formula group
Procedure
1. 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 formula
About this task
To find a formula, follow these steps:
Procedure
1. 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 the
middle, or at the end of a character string.
For example:
v CIS* - search for all the names beginning with CIS
v *SCO - search for all the names ending with SCO
Chapter 7. Writing custom formulas
93
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 formulas
About this task
You can copy a single formula or a group/sub-group of formulas.
To copy formulas, follow these steps:
Procedure
1. 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 formula
About this task
To delete a formula, follow these steps:
Procedure
1.
2.
3.
4.
Follow step 1 in “Using the Formula Selector” on page 93.
Select a formula, group, or subgroup.
Right-click and select Delete. The items you select are deleted from view.
Click Apply to confirm the deletion.
5. Click Revert if you want to restore the deleted items.
Renaming a formula
Procedure
1. 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 examples
This section contains three examples of formulas:
v Discovery
v Collection
v Discovery merge
94
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Discovery formula for a Redback Ethernet interface
The following example shows a Discovery formula that discovers all Redback
Ethernet interfaces. For each interface, it reports the type, description, and speed.
To use this formula automatically with the Inventory Tool, it must have an
associated entry in the inventory_subelements.txt file.
For information about how to create the associated entry, see “Understanding the
inventory_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 explanation
Dim I1 AS Integer Default * NAME Interface
This line declares the input variable I1. It specifies that it is an integer, that the
default is all instances, and it is called Interface.
Further information about the Dim statement is available in “Dim declaration” on
page 80.
Part of Formula
Purpose
Syntax Requirements
Dim
A keyword to indicate that
an input variable is being
declared.
Not case-sensitive.
I1
The input variable.
AS
A keyword to indicate that
the data type of the input
variable is being declared.
Integer
The data type of the input
variable.
Default
A keyword to indicate that
default instances are being
declared.
"I" must be capitalized, and
must be followed by a
number.
Not case-sensitive.
Not case-sensitive. The valid
types are listed in “Instance
variables” on page 86.
Optional, not case-sensitive.
If both the Default and
Name parameters are used,
the Default parameter must
come before the Name
parameter.
Chapter 7. Writing custom formulas
95
Part of Formula
Purpose
Syntax Requirements
*
The instances to use if no
other instances are specified.
In this case, * specifies that
all instances must be used.
Default instances can be a
list of values
Or
* to indicate that all instances
must be used.
See “Instance variables” on
page 86 for more information
about the format for default
instances.
Name
A keyword to indicate that a
name for the input variable
is being declared.
Interface
The name to use for this
input variable in the instance Must contain only letters and
numbers; underscores and
field of the Formula Editor.
spaces are not allowed.
;
Indicates the end of the line.
Optional, not case-sensitive.
If both the Default and
Name parameters are used,
the Default parameter must
come before the Name
parameter.
Required for every line of
the formula, including
comments.
V1=OIDINST(ifType.%I1 == 6, once);
This line restricts the type of row to which the formula is applied. It checks
whether the value of ifType for each row is 6, which is defined in RFC1213 to
mean ethernet-csmacd. If the value is not equal to 6, the row is skipped. If the
value is equal to 6, the value of ifIndex for this row is assigned to V1, and
processing continues with the next line of the formula.
Further information about the OIDINST instruction is available in “OIDINST
instruction” on page 83.
96
Part of Formula
Purpose
V1
A temporary variable.
=
Indicates that the result of
the expression on the right
must be assigned to the
temporary variable on the
left.
Spaces before and after are
optional.
OIDINST
A keyword to indicate that a
conditional filter is being
used/
Not case-sensitive.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Syntax Requirements
"V" must be capitalized, and
must be followed by a
number.
Part of Formula
Purpose
Syntax Requirements
ifType
A MIB object to which the
filter is applied. In this case,
ifType indicates the ifType
column of the ifTable.
Case sensitive, must be a
MIB object in a MIB
compiled in Tivoli Netcool
Performance Manager.
See Chapter 9, “Managing
MIBs,” on page 131for
information about how to
use the MIB Browser and the
MIB Compiler.
.
Separates the MIB object
from the instance.
%I1
The instance of the MIB
object. In this case, the
values of the previously
defined input variable is
substituted.
Spaces are not allowed
before or after.
Must begin with %, and
must:
v match a previously
defined input variable
Or
v be a constant
Or
v be the * wildcard
==
"equal to" the same as in the
C programming language.
Spaces before and after are
optional. Valid operators for
filtering are:
like, <, >, <=, >=, ==, !=
See “Syntax for functions” on
page 88 for more information
about these operators.
6
The value to be filtered. In
this case 6, which isdefined
in RFC1213 to mean
ethernet-csmacd.
Can be any value that is
valid for the MIB object
being used
once
A keyword to indicate that
the data must be retrieved
only once, not polled
repeatedly.
Preceded by a comma;
spaces before and after the
comma are optional.
;
Indicates the end of the line.
Required for every line of
the formula, including
comments.
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 “OIDVAL
expression line” on page 82.
Chapter 7. Writing custom formulas
97
Part of Formula
Purpose
Syntax Requirements
V2
A temporary variable.
=
Indicates that the result of
the expression on the right
must be assigned to the
temporary variable on the
left.
OIDVAL
A keyword that indicates
that the value of an
expression is being assigned
to a temporary variable.
Not case-sensitive, the
expression must be enclosed
in parentheses.
ifDescr
A MIB object, the value of
which is assigned to the
temporary variable. In this
case, ifDescr indicates the
ifDescr column of the ifTable.
Case sensitive, must be a
MIB object in a MIB
compiled in Tivoli Netcool
Performance Manager.
"V" must be capitalized, and
must be followed by a
number.
Spaces before and after are
optional.
See Chapter 9, “Managing
MIBs,” on page 131 for
information about how to
use the MIB Browser and the
MIB Compiler.
.
Separates the MIB object
from the instance.
Spaces are not allowed
before or after.
%V1
The instance of the MIB
Must begin with %, and
object. In this case, the
must match a previously
values of the previously
defined temporary variable is defined temporary variable.
substituted.
once
A keyword to indicate that
the data must be retrieved
only once, not polled
repeatedly.
;
Indicates the end of the line.
Preceded by a comma;
spaces before and after the
comma are optional.
Required for every line of
the formula, including
comments.
V3=OIDVAL(int(ifSpeed.%V1/1000000), once);
This line retrieves the value of ifSpeed for each value for V1 from the second line
of the formula. It divides this value by 1,000,000, to convert from bits/second to
megabits/second. It applies the int function to convert the result to an integer. It
assigns that integer to V3.
Further information about the OIDVAL instruction is available in “OIDVAL
expression line” on page 82.
98
Part of Formula
Purpose
V3
A temporary variable.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Syntax Requirements
"V" must be capitalized and
followed by a number.
=
OIDVAL
int
ifSpeed
.
%V1
/
1000000
once
;
Indicates that the result of
the expression on the right
must be assigned to the
temporary variable on the
left.
A keyword that indicates
that the value of an
expression is being assigned
to a temporary variable.
A function that returns only
the integer part of an
expression.
Spaces before and after are
optional.
Not case-sensitive. The
expression must be enclosed
in parentheses.
Not case-sensitive. The list of
all available functions can be
found in “Syntax for
functions” on page 88.
A MIB object, the value of
which is used in the
calculation. In this case,
ifSpeed indicates the ifSpeed
column of the ifTable.
Case sensitive, must be a
MIB object in a MIB
compiled in Tivoli Netcool
Performance Manager. See
Chapter 9, “Managing MIBs,”
on page 131for information
about how to use the MIB
Browser and the MIB
Compiler.
Separates the MIB object
from the instance.
Spaces are not allowed
before or after.
Must begin with %, and
The instance of the MIB
must match a previously
object. In this case, the
defined temporary variable.
values of the previously
defined temporary variable is
substituted.
Division
Spaces before and after are
optional. See “Syntax for
functions” on page 88 for a
list of operations.
Used to calculate
megabits/second from
ifSpeed, which is in
bits/second.
A keyword to indicate that
the data must be retrieved
only once, not polled
repeatedly.
Indicates the end of the line.
Preceded by a comma;
spaces before and after the
comma are optional.
Required for every line of
the formula, including
comments.
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 results
can be produced by the Discovery formula.
Chapter 7. Writing custom formulas
99
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 rules
with the Rule Editor.
See Chapter 4, “Creating grouping rules,” on page 47 for more information about
the Rule Editor.
Part of Formula
Purpose
%V2
A temporary variable that
indicates a result is being
returned. The value of this
variable is appended to the
end of the return string. In
this case, ifDescr for each
instance is assigned to it in
the third line of the formula.
index
"
RedbackEthernet
<%V1>
||
%V2
%V3
100
A keyword that allows you
to add text strings to the
output.
Syntax Requirements
Must begin with %, and
must match a temporary
variable from the left side of
a previous OIDVAL
instruction. A temporary
variable from a previous
OIDINST instruction causes an
error.
Not case-sensitive, spaces
required before and after.
Indicates the beginning of
the output.
A text string to describe the
output. In this case, the
name of the interface.
ASCII text, double quotation
marks must not be used
within the string.
A temporary variable. In this Must begin with %, and
must match a previously
case, ifIndex for each
instance is assigned to it in
defined temporary variable.
the second line of the
formula.
Separates the instance of the
subelement from the label
field.
A temporary variable. In this Must begin with %, and
case, ifDescr for each
must match a previously
defined temporary variable.
instance is assigned to it in
the third line of the formula.
A temporary variable. In this Must begin with %, and
case, the speed of the
must match a previously
interface for each instance is defined temporary variable.
assigned to it in the fourth
line of the formula.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
mbps
A text string to describe the
output. In this case,
megabits/second, the units
calculated in the fourth line
of the formula.
ASCII text, double quotation
marks must not be used
within the string.
Inst
A text string to describe the
output. In this case, an
abbreviation for "instance."
ASCII text, double quotation
marks must not be used
within the string.
%V1
A temporary variable. In this
Must begin with %, and
case, ifIndex for each
must match a previously
instance is assigned to it in
defined temporary variable.
the second line of the
formula.
||
Separates the label field from
the details about the
interface.
ifSpeed
A text string to describe the
output. In this case, the
name of a MIB object.
ASCII text, double quotation
marks must not be used
within the string.
MIB objects returned by the
last line of a discovery
formula become properties in
the database, and can be
used to create grouping rules
with the Rule Editor. See
Chapter 4, “Creating
grouping rules,” on page 47
for details about Rule Editor.
<%V3>
mbps>
ifDescr
A temporary variable. In this Must begin with %, and
must match a previously
case, the speed of the
interface for each instance is defined temporary variable.
assigned to it in the fourth
line of the formula.
A text string to describe the
output. In this case,
megabits/second, the units
calculated in the fourth line
of the formula.
ASCII text, double quotation
marks must not be used
within the string.
A text string to describe the
output. In this case, the
name of a MIB object.
ASCII text, double quotation
marks mustnot be used
within the string.
MIB objects returned by the
last line of a discovery
formula become properties in
the database, and can be
used to create grouping rules
with the Rule Editor. See
Chapter 4, “Creating
grouping rules,” on page 47
for details about Rule Editor.
Chapter 7. Writing custom formulas
101
<%V2>
A temporary variable. In this Must begin with %, and
case, ifDescr for each
must match a previously
defined temporary variable.
instance is assigned to it in
the third line of the formula.
"
Indicates the end of the
output.
;
Indicates the end of the line.
Required for every line of
the formula, including
comments.
Collection formula example
The following example shows a Collection formula for inbound bandwidth. To use
this formula automatically with the Inventory Tool, it must have an associated
entry in the inventory_subelements.txt file.
See “Understanding the inventory_subelements.txt file” on page 108 for
information about how to create the associated entry.
Dim I1 AS Integer Default * Name Interface;
delta(ifInOctets.%If)/delta(sysUpTime.0/100);
Line-by-Line explanation
Dim I1 AS Integer Default * Name Interface;
This line declares the input variable I1. It specifies that it is an integer, that the
default is all instances, and it is called "Interface."
Further information on the Dim statement is available in “Dim declaration” on
page 80.
102
Part of Formula
Purpose
Syntax Requirements
Dim
A keyword to indicate that
an input variable is being
declared.
Not case-sensitive.
I1
The input variable.
"I" must be capitalized, and
must be followed by a
number.
AS
A keyword to indicate that
the datatype of the input
variable is being declared.
Not case-sensitive.
Integer
The datatype of the input
variable.
Default
A keyword to indicate that
default instances are being
declared.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Not case-sensitive. The valid
types are listed in “Instance
variables” on page 86.
Optional, not case-sensitive.
If both the Default and
Name parameters are used,
the Default parameter must
come before the Name
parameter.
Part of Formula
Purpose
Syntax Requirements
*
The instances to use if no
other instances are specified.
In this case, * specifies that
all instances should be used.
Default instances can be a
list of values
Or
* to indicate that all instances
should be used.
See “Instance variables” on
page 86 for more information
about the format for default
instances.
Name
A keyword to indicate that a
name for the input variable
is being declared.
Interface
The name to use for this
input variable in the instance Can contain only letters and
numbers; spaces are not
field of the Formula Editor.
(This name will also appear allowed.
in the Request Editor.)
;
Indicates the end of the line.
Optional, not case-sensitive.
If both the Default and
Name parameters are used,
the Default parameter must
come before the Name
parameter.
Required for every line of
the formula, including
comments.
delta(ifInOctets.%If)/delta(sysUpTime.0/100);
This line returns the final result. It calculates the number of incoming cells, as the
number of octets divided by 53. It then divides this by the time period over which
the collection was done.
Part of Formula
Purpose
Syntax Requirements
delta
A function that calculates the
difference between the value
retrieved during this polling
and the value retrieved
during the previous polling
for a single SNMP variable.
Must be lower case. Further
information is available in
“SNMP-specific functions”
on page 90.
ifInOctets
A MIB object on which the
calculation will be done. In
this case, ifInOctets indicates
the ifInOctets column of the
ifTable.
case-sensitive, must be a MIB
object in a MIB compiled in
Tivoli Netcool Performance
Manager.
See Chapter 9, “Managing
MIBs,” on page 131 for
information on how to use
the MIB Browser and the
MIB Compiler.
Chapter 7. Writing custom formulas
103
Part of Formula
.
%If
Separates the MIB object
from the instance.
The instance of the MIB
object. In this case, inbound
bandwidth
Syntax Requirements
Spaces are not allowed
before or after.
Must begin with %, and
must match a previously
defined temporary variable.
/
Division
53
Spaces before and after are
Used to calculate the number optional. The list of possible
of cells from the number of
operations is in “Syntax for
octets.
functions” on page 88.
delta
Must be lower case. See
A function that calculates the “SNMP-specific functions”
difference between the value on page 90 for more
retrieved during this polling information.
and the value retrieved
during the previous polling
for a single SNMP variable.
sysUpTime
.
0
104
Purpose
A MIB object on which the
calculation will be done. In
this case, sysUpTime
indicates the time since the
system was re-initialized.
Separates the MIB object
from the instance.
The instance of the MIB
object. In this case,
sysUpTime is scalar, so "0" is
used as the only instance.
/
Division
100
Used to calculate the number
of seconds from the value of
sysUpTime, which is in
hundredths of a second.
;
Indicates the end of the line.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Spaces before and after are
optional. The list of possible
operations is in “Syntax for
functions” on page 88.
case-sensitive, must be a MIB
object in a MIB compiled in
Tivoli Netcool Performance
Manager.
See Chapter 9, “Managing
MIBs,” on page 131for
information on how to use
the MIB Browser and the
MIB Compiler.
Spaces are not allowed
before or after.
Spaces before and after are
optional. The list of possible
operations is in “Syntax for
functions” on page 88.
Required for every line of
the formula, including
comments.
Merge formulas example
The following example implements the following on top of standard MIB II
formula (1213_IF and 2233_IF):
v Octet capability detection: inbound and outbound, 64, 32, or undefined.
v Packets capability detection: 64 or 32 or undefined
v Custom invariant, either from MIB II ifDescr, or RFC2233 ifName
v Customer-specific key and properties
inventory_sub-element.txt
# File format:
#{FAMILY}
|{Elem. FAMILY}|{sysObjId Mask}
{I}|{Discovery Formula}|{I}|{cancel FAMILY};[{...};]|
|{Match Formula}
|
1213_Device
<*>|AP~1213_Device
|Generic~Agent |1.3.6.1
|<*>|
|
|NULL
|
1213_IF
<*>|AP~1213_IF
|Generic~Agent |1.3.6.1
|<*>|
|
|NULL
|
2233_IF
<*>|AP~2233_IF
|Generic~Agent |1.3.6.1
|<*>| 1213_IF;|
|AP~2233_IF_match
|
2233_IF(Exp) |Generic~Agent |1.3.6.1
<*>|AP~2233_HCOctets_Support
|<*>|
|AP~2233_IF_match
|
|
2233_IF(Exp) |Generic~Agent |1.3.6.1
<*>|AP~2233_HCPackets_Support
|<*>|
|AP~2233_IF_match
|
|
1213_IF(Exp) |Generic~Agent |1.3.6.1
<*>|AP~1213_IF_Invariant
|<*>|
|NULL
|
|
2233_IF(Exp) |Generic~Agent |1.3.6.1
<*>|AP~2233_IF_Invariant
|<*>|
|AP~2233_IF_match
|
|
1213_IF(Exp)|Generic~Agent |1.3.6.1
<*>|AP~TELUS_KEY
|NULL
|
1213_IF
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(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_IF
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);
V8 = OIDVAL(ifDescr.%I1, once);
%V1 index "If<%I1>||IF: %I1 (%V5) (%V4Mbps)||type<%V1>
location<%V2>physicalCapacity<%V3>name<%V5>status<%V6>||";
Chapter 7. Writing custom formulas
105
2233_HCOctets_Support
Dim 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_Support
Dim 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 invariant
Dim 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 empty
Dim 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";
106
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
<CustomerSpecific>_KEY
The 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 messages
You might encounter one or more of the following error messages when editing
and testing formulas.
Error Message
Description
Initialization is not properly achieved.
Error in formula.
NO DATA
Error in formula
Or
The formula is fine; however, there is
nothing to collect
Or
The device does not respond as expected
Or
The formula timed out. This can happen if
the formula includes more than one delta
function and is launched against a target
with a large number of sub-elements. Try
launching the formula against a more
specific target.
Error while casting variable
Incorrect input variable. "I" (letter I) must be
capitalized, and must be followed by a
number.
Object identifier was not found in any of the
The MIB object used is invalid. Check that
compiled MIBs
the name is correct. Names are case
sensitive.
Or
Use the MIB Browser to check that the MIB
has been compiled in Tivoli Netcool
Performance Manager. If necessary, use the
MIB Compiler to compile the MIB in Tivoli
Netcool Performance Manager.
See Chapter 9, “Managing MIBs,” on page
131 for information on how to use the MIB
Browser and the MIB Compiler.
Chapter 7. Writing custom formulas
107
ClientServices open Unable to connect to
server at localhost
Check that the collector is running.
See Viewing Collector Information in the IBM
Tivoli Netcool Performance Manager: DataMart
Configuration and Operation Guide for
information about the collector.
Error Message
Description
"DATA at" with the date & time, but next
line is "End" with no data
Inappropriate target
Or
Error in formula
Understanding the inventory_subelements.txt file
The inventory_subelements.txt file contains the list of rules the Discovery uses. It
is located in the conf directory under the PVM directory.
When you create new discovery formulas, you need to edit this file to create new
rules. You must edit the file before the new Discovery formula can be used by the
Inventory Tool. (You do not need to edit this file before a new collection formula
can be used.)
Discovery formulas are used only against elements, not against subelements.
During Discovery, the Inventory Tool uses the sysObjectID field in the
inventory_subelements.txt file to determine the correct formula to use for each
element it encounters. The file already includes generic formulas that match any
sysObjectID, 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
SubElementFamilyName
Redback_SMS_Ethernet
FamilyName
Router~Redback
SysObjId
1.3.6.1.4.1.2352.1.
Purpose
Determines how
sub-elements are grouped in
the Subelement and Host
Selector.
The sysObjectID, or a part of
the sysObjectID.
For further information, see
“SysObjId” on page 109.
FilterFormulaName
NULL
The path to the formula that
is used to distinguish
between different elements
with the same sysObjectID.
For further information, see
“FilterFormulaName” on
page 110.
108
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Instance
<*>
The instances to which the
formula should be applied.
This should correspond to
the input variables in the
formula listed under
FilterFormulaName.
If the formula contains more
than one DIM declaration,
there should be more than
one Instance entry. If the
formula only retrieves scalar
objects, the instance can be
empty.
SubElementFormulaName
PVL~Redback~Ethernet
Instance
<*>
The path to the discovery
formula for this subelement.
The path is a location within
the "Alias Instance and Label
Inventory" directory, and is
specified with tilde (~) as the
path separator.
The instances to which the
formula should be applied.
This should correspond to
the input variables in the
filter listed under
SubElementFormulaName.
If the formula contains more
than one DIM declaration,
there should be more than
one Instance entry. If the
formula only retrieves scalar
objects, the instance can be
empty.
SubElementFormulaName to
cancel
Generic_Lan_Ethernet10;
Generic_Lan_Ethernet100;
Generic_Lan_Ethernet1000
A list of
SubElementFormulaName that
should not be used with this
sysObjectID.
For more information, see
“SubElementFamilyName to
cancel” on page 110.
SysObjId
This field is the sysObjectID. The Inventory Tool checks to see if the sysObjectID
of each element matches the sysObjectID listed here. If they match, it checks to see
if there is an entry for FilterFormulaName. If the element matches both entries, the
Inventory Tool runs the formula specified under SubElementFormulaName.
Only a partial match for the sysObjectID is required. There are generic formulas
included with Tivoli Netcool Performance Manager DataMart that specify 1.3.6.1 as
the sysObjectID. This is not an exact match for anything, but it is a partial match
for everything. Since only a partial match for the sysObjectID is required, these
generic formulas are used against every element encountered by the Inventory
Chapter 7. Writing custom formulas
109
Tool. Any vendor-specific formula contains a more specific sysObjectID that
matches only that vendor's sysObjectID.
FilterFormulaName
This field specifies the path to the formula that is used to distinguish between
different 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 in
this field. They both have the same sysObjectID; however they can have different
subelement types; therefore, they require different discovery formulas.
For example, the FilterFormulaName for the Cisco Catalyst 3000 is
PVL~Cisco~Catalyst~C3000~Match. Its discovery formula is
PVL~Cisco~Catalyst~C3000~Port_HalfDuplex_10Mb.
The FilterFormulaName for the Cisco Catalyst 5000 is
PVL~Cisco~Catalyst~C5000~Match. Its discovery formula is
PVL~Cisco~Catalyst~C5000~Port_HalfDuplex_10Mb.
If the Inventory Tool finds a match on the sysObjectID, it checks for a
FilterFormulaName. If a formula is specified, the element must match both the
sysObjectID and the FilterFormulaName before the inventory tool runs the formula
under SubElementFormulaName.
SubElementFamilyName to cancel
This field contains a list of any SubElementFamilyNames that must not be used with
this sysObjectID.
For the Redback example, the SubElementFamilyNames to be ignored are:
Generic_Lan_Ethernet10, Generic_Lan_Ethernet100, and
Generic_Lan_Ethernet1000.
If you leave this blank, the same subelement can appear under two different
groups, the vendor-specific group and a generic group. If you add information, the
Inventory Tool ignores the canceled formulas not only for this type of subelement
but 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 your
device-specific rules but would have matched the canceled generic rule, that
subelement is not discovered.
For example, if Generic_Node is included in the SubElementFamilyName to cancel
field for the Redback example, the Inventory Tool only discovers Redback ethernet
interfaces. If the element contains other types of subelements, such as ATM, none
of the other subelements are discovered.
110
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
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 metrics
exceed or drop below a specific limit. Using thresholds as the measure against
which data is evaluated lets you report on only those resources with pertinent
data.
About thresholds
A threshold is a value that is compared against metrics to determine if the metrics
have violated a specific constraint. Using thresholds as the measure against which
data is evaluated lets you report on only those resources with pertinent data.
Threshold report capabilities exist at both the resource and group levels. The CME
uses these threshold values to determine threshold violations and to generate
SNMP traps. The information is stored in the database and is used by Tivoli
Netcool Performance Manager DataView for on-demand and scheduled reports.
Group thresholds are specified on a per formula basis within the Group Summary
Table (GST) reporter parameters. The user specifies values for the critical or
warning thresholds, the duration for which the threshold is in violation, the
metrics, and statistics for which the threshold values apply, which user profile can
view the thresholds in the report, and the reporter to drilldown to if the threshold
is violated.
Threshold types
You configure most of these thresholds (group threshold is the exception) using
either the Resource Editor GUI or the resmgr command.
Tivoli Netcool Performance Manager provides the following types of thresholds to
supply report viewers with the information they want.
burst
Ignores the natural network bursts by evaluating how long in a row the
violations occurred per resource. Burst thresholds can be set and reset
multiple times.
period Involves the concept of accumulated duration for which the threshold is
violated. This duration is accumulated per resource until the end of the
SLA period. The threshold is violated as soon as a data spike's
accumulated duration by period exceeds a certain duration of time. Period
thresholds, once violated are not reset until the end of the period.
risk
A proactive threshold that detects resources that are at risk of violating a
period threshold before the end of the SLA period.
baseline
Provides a view into resource behavior outside the normal range. It uses a
profiled deviation function to compare the current daily behavior with the
baseline as data flows throughout the system (in real time.) What is normal
is defined and what is not normal is flagged.
© Copyright IBM Corp. 2012
111
Unlike burst, there is not a single threshold level to consider when determining
duration. The duration determination scheme considers varying threshold levels.
And unlike burst, period, and risk thresholds, you do not statically define the
baseline, it dynamically adapts to historical data.
User profiles and threshold types
You need to decide what threshold information your report viewer needs to see, if
any. You then grant access privileges to the threshold information to report viewers
based on their user profile.
For example, you might want report viewers with the NOC profile to have access
to 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 needs
resizing.
v Unusually low volume at "peak" time that might indicate a potential issue with
a router's forwarding mechanism, which continuously transmits data at a low
level; impacting user perceived latency.
The following matrix shows the threshold information that each type of audience
probably wants to see.
Violation Type
Report
Consumer
Burst
Period
Risk
Baseline
User Profile
for Reports
Service
Provider's
NOC
Yes
Yes
No
Yes
NOC
Customer
No
Yes
No
No
SLA
Decisionmaker
No
Yes
Yes
Yes
PSLA
Basic computation
The arrival of a metric record drives threshold computations. If a metric record
does not arrive, no threshold computation occurs. Each incoming metric value is
compared against a deployed threshold definition as part of the overall processing
of the threshold record. All threshold statistics in the RA record are then updated
appropriately.
Statistic used for processing
Threshold definition specifies the actual statistic to be used in the comparison (for
example, raw or sum). As each metric value arrives, the statistic specified by this
field is computed and this value is used for the subsequent threshold
computations.
112
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Exceeding a threshold level
Determining whether a threshold is violated involves determining whether the
metric exceeds a specified level. The actual comparison order depends on the type
of metric (Over, Under, or Band).
For example, the metric is considered to have exceeded the threshold level when
the following occurs:
v Threshold level is 10
v Metric value is 15
v Over metric type
However, the metric would not be considered to have exceeded the threshold level
if it was an Under. Determining whether the threshold is violated also involves the
duration.
Interpolation
In 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 value
does 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 deployment
Explains the basics of threshold deployment. To understand threshold deployment,
you need a basic knowledge of how thresholds are processed. Processing
thresholds 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 which
threshold applies to which m/g/r combination. To make the determination, Tivoli
Netcool Performance Manager examines each m/g/r combination and tries to find
a matching threshold definition.
Each threshold definition contains three key fields (Metric, Group, Resource) that
are used to determine deployment. The examination involves comparing the
m/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 the
following table:
Configuration
Metric
Group
Resource
Priority
group- and
subelementspecific
Defined
Defined
Defined
1
subelementspecific
Defined
No
Defined
2
group-specific
Defined
Defined
No
3
global
Defined
No
No
4
Priority indicates which configuration takes precedence when multiple threshold
definitions are available for a single resource. Also, multiple group-specific
thresholds can be specified for a single branch of the subelement hierarchy. In this
case, the definition closest to the resource (farthest from the root) takes precedence.
Examples
The 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 each
resource. The specific metric, `m' is considered, other metrics have their own
runtime contexts.
Group- specific and subelement-specific example
The threshold definition T1(m/G3/R0) means that the key fields have values for
metric, group, and resource set to `m', G3 and R0 respectively. Tivoli Netcool
Performance 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 match
either of the other m/g/r/ combinations.
114
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Group-specific example
A new threshold definition is defined, T2(m/G3/-.) This threshold differs from T1
because the resource is undefined. Tivoli Netcool Performance Manager cannot
match the group- and subelement-specific or subelement-specific configurations,
but can find a match for a group-specific configuration. The system determines
that T2 is deployed against both m/G3/R0 and m/G3/R1.
Chapter 8. Configuring thresholds
115
Group-specific and subelement-specific combined with groupspecific
Thresholds T1(m, G3, R0) and T2(m, G3, -) are defined in the system. Both
thresholds specify group G3; in addition T1 specifies the resource. The priority
table is used to determine which threshold actually applies.
The system deploys T1 against the m/G3/R0 combination (based on the groupand subelement-specific rule which is examined first) and T2 against the m/G3/R1
combination (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 remains
the same.
The threshold T4(m, G0, -) is also added. Again, T1 and T2 are higher priority for
the m/G3/R0 and m/G3/R1 groups respectively. The threshold deployments
against those m/g/r groups remain the same. However, T4 does get deployed
against m/G4/R2.
116
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Resource in two groups example
The following example shows R1 as a member of G3 and G4. A single threshold
definition exists, T4 (m/G0/-.) Because R1 is a member of two groups, it belongs
to two combinations, m/G3/R1 and m/G4/R1. Therefore, T4 is deployed against
both these contexts.
Chapter 8. Configuring thresholds
117
TRAP generation rules
Provides a brief overview of trap generation rules. If Tivoli Netcool Performance
Manager is configured to generate traps, trap generation input to a specific
threshold occur when there is a change in the violation state.
v burst, period (and proactive) thresholds
Non-Violation <-> Warning Violation <-> Critical Violation
v baseline thresholds
Non-Violation <-> Violation
The traps generated reflect the nature of the state transition. For example, when
the system goes from burst non-violation to burst Warning violation for a
particular m/g/r-threshold; a provisoCMEWarningViolationBurstThr (see
proviso.mib) is generated.
The example illustrated in “Resource in two groups example” on page 117 shows
resource R1 as a member of two groups. A threshold is deployed against the
m/g/r combinations that result from that group membership. Therefore, it is
possible 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 setting
Provides a brief overview of the use of the period setting in the calculation of a
period threshold.
Threshold definitions have a period setting (different from a period threshold) that
can have the following values:
v Day
v Week
v Month
v All (which means Day and Week and Month)
In each m/g/r combination, threshold statistics can be calculated for Days, Weeks
and/or Months. The period setting determines which of these time periods the
threshold statistics is calculated for, when processing the type of threshold call a
period threshold.
Note: Statistics in these m/g/r combinations map directly to Daily, Weekly, and
Monthly Aggregation records.
Processing traps
When processing an m/g/r combination, it is possible that a period threshold can
be violated for each of the configured periods. If that occurs, the system can send
three traps, one corresponding to each of the configured periods (one trap for the
Day, one for the Week and one for the Month).
However, when processing burst thresholds, a similar violation would lead to a
single trap.
118
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Launching the threshold tool
Explains how to launch the Threshold tool from the Tivoli Netcool Performance
Manager DataMart Resource Editor. The Threshold tool lets you configure
thresholds.
Procedure
1. 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
Date
Stat
Date and time the action takes effect.
Actions cannot be applied to the past and
take effect on the hour.
Statistic the CME uses to calculate threshold
information:
v raw (default)
v min
v max
v avg
v sum
v count
Calc
Calculation used to determine the value of
the following:
v standard
v normalized
v scale
CalcVal
BCrtL
BCrtT
BWrnL
BwrnT
Value used for calculating the percentage
over or under the threshold.
Level of the critical threshold for burst
thresholds. Zero implies the threshold is not
defined. The metric must be greater than
this level to trigger a violation.
Time limit for the burst critical threshold.
Level of the warning threshold for burst
thresholds. Zero implies the threshold is not
defined.
Duration of the burst critical threshold in
seconds.
Chapter 8. Configuring thresholds
119
Column
BEvent
PCrtL
PCrtT
PWrnL
PWrnT
PEvent
PDef
Description
Indicates whether Tivoli Netcool
Performance Manager generates SNMP traps
for the burst threshold.
Level of the period critical threshold for
period thresholds. Zero implies the
threshold is not defined.
Duration the period critical period threshold
in seconds.
Level of the warning threshold for period
thresholds. Zero implies the threshold is not
defined.
Duration of the warning period threshold in
seconds. Zero (0) indicates an immediate
threshold violation.
Indicates whether Tivoli Netcool
Performance Manager generates SNMP traps
for the period threshold.
Defines the period for period and burst
thresholds:
v all
v day
v week
v month
If the period is day, week, or month, the
GST and RST reports for the other periods
do not show a violation. If the field is set to
all, violations are reported for all periods.
MaxNbDay
Number of days used as the maximum
value for the computation of the upper
control limit. The upper control limit is the
top of what is considered the normal range
and is used for the baseline threshold.
minNbDay
Number of days used as the minimum value
for the computation of the lower control
limit. The lower control limit is the bottom
of what is considered the normal range and
is 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
blMode
Baseline mode
v 1 = under
v 2 = over
v 3 = band
120
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Column
Description
blTime
Duration of baseline violation.
blTrap
Indicates whether the baseline threshold
generates a trap.
v 0 = no
v 1 = yes
blUpper
blLower
Number of standard deviations used as the
maximum value for the computation of the
upper control limit. The upper control limit
is the top of what is considered the normal
range.
Number of standard deviations used as the
maximum value for the computation of the
lower control limit. The lower control limit
is the bottom of what is considered the
normal range.
Adding a threshold
About this task
This section explains how to add the following types of thresholds by using the
Add 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:
Procedure
1. Click the Threshold tab in Resource Editor.
2. Click Add from the Edit menu. The Add Threshold window appears.
Selecting metrics
You need to choose the metric to which you want to apply the threshold. Use this
for all three types of thresholds
Procedure
1. 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 right
pane.
3. Click the formula name to highlight it and while holding down the left mouse
button, drag the formula name to the Metric text box. The formula name, along
with the entire path, appears.
For more information about the Formula Selector, see “Using the Formula
Selector” on page 93.
Chapter 8. Configuring thresholds
121
Applying thresholds to a group of subelements
You can choose to apply the threshold to a group of resources at different
granularity levels.
About this task
You can apply the threshold to the top group in the grouping tree, to any of the
leaves 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 any
subelement containing the metric you have chosen or to just a specific subelement
by adding its name to the subelement text box.
If you are applying a group- and subelement-specific threshold, you need to
identify the leaf-level group that contains the resource and apply the threshold to
that group.
To choose the group using the Resource Editor, follow these steps:
Procedure
1. 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 can
leave the Sub-Element text box blank to apply the threshold to all subelements
belonging to the group, that contain the specified metric.
Specifying subelements
You can specify the subelement to which you want to apply a threshold. If you do
not specify a group for that subelement, the threshold is applied to that
subelement, in each group to which it belongs.
About this task
To choose a subelement using the Resource Editor:
Procedure
1. 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 called
ethernetCsmacd.
5. Click the subleaf group's name to display the list of subelements in the right
pane.
122
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
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 of
the message box From here, you can configure the static and baseline
thresholds.
Configuring burst or period thresholds
Explains how to configure burst and period thresholds. These thresholds are
considered static thresholds because you set the value for them by using the
configuration dialog box. You also define how you want the threshold to act.
Configuring thresholds
Procedure
From the Add Threshold Window, click Static Threshold.
Configuring mode
You need to configure the mode you want to apply to your burst and/or period
threshold.
Procedure
1. Configure the mode you want to apply to the static threshold (burst or period.)
The following table lists the configuration options:
Option
Effective date
Definition
Values
Currently not used by Tivoli
Netcool Performance
Manager.
Do not edit this value.
Threshold is effective
immediately after creation or
update.
Mode
Mode of the threshold
Click the down arrow to
access the list of values:
v Band: detect violations
when they go outside a
range (or band) between
two threshold values
v Over: detect violations
when they exceed
threshold values
v Under: detect violations
when they fall short of
threshold values
Statistic mode
Indicate which statistic you
want used to calculate
threshold information.
Click the down arrow to
access the list of statistics.
Chapter 8. Configuring thresholds
123
Calculation mode
Calculation method to use to
Click the down arrow to
determine the maximum
access the list of the three
percentage over burst and
different ways of calculating
period threshold values.
this value.
v Standard
v Normalized
v Scaled
Calculation value
Activated when you select
Scaled for the Calculation
mode. Value used for
calculating the percentage
over or under the threshold.
Enter the number you want
to use for the calculation.
2. Click Apply.
Configuring maximum percent over for burst and period
thresholds
When configuring the burst and period thresholds, you need to enter a value that
represents the maximum percent over a threshold level. This section provides a
brief overview of the maximum percent over calculation.
For both burst and period thresholds, the values of the maximum percent over
fields (DBL_BRST_MAX_PCT_OVER and DBL_PRD_MAX_PCT_OVER) use the following
algorithm:
MAX_PCT_OVER = 0
For each metric, mi,
If | mi - Lw | / Lw > MAX_PCT_OVER then
MAX_PCT_OVER = | mi - Lw | / Lw
If | mi - Lc | / Lc > MAX_PCT_OVER then
MAX_PCT_OVER = |mi - Lc|/ Lc
The algorithm differs from taking the maximum value of a metric and dividing it
by the most severe threshold violation. Depending on the relative values of metrics
and threshold levels, it is possible that the maximum percent over is obtained from
a metric that is not the largest metric value.
Configuring burst values
About this task
To configure burst values, follow these steps:
Procedure
1. 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 by
clearing the Enabled Threshold box and clicking Apply. The threshold is
disabled immediately for all Tivoli Netcool Performance Manager modules
except 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 Enabled
Threshold, check the values, and click Apply.
124
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
3. Enter the values you want for the burst threshold. The following table lists the
configuration options:
Option
Warning Level
Critical Level
Event generation
Definition
Values
Level of the warning
threshold. The metric value
must be greater than this
value to trigger a threshold
violation.
Enter a double-precision
floating point number with
up to six digits to the right
of the decimal point.
Level of the critical
threshold. The metric value
must be greater than this
value to trigger a threshold
violation.
Enter a double-precision
floating point number with
up to six digits to the right
of the decimal point.
Indicates whether Tivoli
Netcool Performance
Manager must generate an
event when threshold
violation occurs at warning
and/or critical levels (if you
entered a value in the
Warning Level and Critical
Level fields.)
Click the down arrow to
display the values. Choose
yes if you want to generate
an event when a threshold
violation occurs.
Warning time
Enter the number of seconds
Maximum duration for
as an integer.
exceeding Warning threshold
level. see “Configuring
maximum percent over for
burst and period thresholds”
on page 124.
Critical time
Enter the number of seconds
Maximum duration for
exceeding Critical threshold as an integer.
level. See “Configuring
maximum percent over for
burst and period thresholds”
on page 124.
4. Click Apply.
Configuring period values
About this task
To configure period values, follow these steps:
Procedure
1. 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 by
clearing the Enabled Threshold box and clicking Apply. The threshold is
disabled immediately for all Tivoli Netcool Performance Manager modules
except 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 Enabled
Threshold, check the values, and click Apply.
Chapter 8. Configuring thresholds
125
3. Enter the values you want for the period threshold. The following table lists the
configuration options:
Option
Definition
Values
Warning Level
Level of the warning
threshold. The metric value
must be greater than this
value to trigger a threshold
violation.
Enter a double-precision
floating point number with
up to six digits to the right
of the decimal point.
Critical Level
Level of the warning
threshold. The metric value
must be greater than this
value to trigger a threshold
violation.
Enter a double-precision
floating point number with
up to six digits to the right
of the decimal point.
Event generation
Indicates whether Tivoli
Netcool Performance
Manager should generate an
event when threshold
violation occurs at warning
and/or critical levels (if you
have entered a value in the
Warning Level and Critical
Level fields.)
Click the down arrow to
display the values. Choose
yes if you want to generate
an event when a threshold
violation occurs.
Warning time
Enter the number of seconds
Maximum duration for
exceeding Warning threshold as an integer.
level. Refer to “Configuring
maximum percent over for
burst and period thresholds”
on page 124.
Critical time
Enter the number of seconds
Maximum duration for
exceeding Critical threshold as an integer.
level. Refer to “Configuring
maximum percent over for
burst and period thresholds”
on page 124.
Period Definition
Defines the period for which
you want threshold
violations reported.
Click the down arrow to
display the values. Choose
the period for which you
want threshold violations
reported. If you choose All,
violations for all periods are
reported.
4. Click Apply.
Configuring baseline thresholds
Explains 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:
126
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Procedure
1. 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 by
clearing the Enabled Threshold box and clicking Apply. The threshold is
disabled immediately for all Tivoli Netcool Performance Manager modules
except 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 Enabled
Threshold, check the values, and click Apply.
3. Enter the values you want for the baseline. The following table lists the
configuration options:
Option
Max # of days
Min # of days
Definition
Values
Maximum number of days
you want to consider for the
baseline. This value must be
higher than the value you
enter for the minimum
number of days.
Enter an integer of up to
three digits to indicate the
maximum number of days.
Minimum number of days of
Enter an integer of up to
data required before the
three digits to indicate the
baseline is calculated. This
minimum number of days.
value must be less than or
equal to the Maximum
number of days.
Chapter 8. Configuring thresholds
127
Calculation
Indicate which calculation
mode you want to use for
the baseline.
Click the down arrow to
display the values:
v PreviousDays: include the
previous N days from the
specified reporting period
in the calculation. For
example:
If you specify 10 days for the
reporting period of August
29; the PreviousDays
calculation includes the 10
previous days:
August 19, 20, 21, 22, 23, 24,
25, 26, 27, and 28.
v PrevSameDay: include the
N previous same days of
the week from the
specified reporting period
in the calculation. For
example:
If you specify 10 days for the
reporting period of Friday,
August 29; the PrevSameDay
calculation includes the same
day from the 10 previous
weeks:
Friday June 20, Friday June
27, Friday July 4, Friday, July
11, Friday July 18, Friday
July 25, Friday August 1,
Friday August 8, Friday
August 15, and Friday
August 22.
4. Enter the values you want for the threshold. The following table lists the
configuration options:
Option
Sensitivity (upper)
Sensitivity (lower)
128
Definition
Values
Number of standard
deviations added to the
mean to determine upper
threshold level.
Enter an integer with
maximum of four digits,
with a maximum of two
digits to the right of the
decimal point.
Number of standard
deviations added to the
mean to determine lower
threshold level.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Enter an integer with
maximum of four digits,
with a maximum of two
digits to the right of the
decimal point.
Permitted time outside
baseline
Event generation
Mode
Baseline equivalent of
Enter the time limit in
duration for burst thresholds. minutes, hours, or days. You
can use a combination of
units such as 1 hour 25
minutes.
Indicates whether Tivoli
Netcool Performance
Manager must generate an
event when threshold
violation occurs.
Mode of the baseline
threshold.
Click the down arrow to
display the values. Choose
yes if you want to generate
an event when a threshold
violation occurs.
Click the down arrow to
access the list of values:
v Band: detect violations
when they go outside a
range (or band) between
two threshold values
v Over: detect violations
when they exceed
threshold values
v Under: detect violations
when they fall short of
threshold values
5. Click Apply.
Trapping threshold violations
The following sections explain how to enable Tivoli Netcool Performance Manager
to 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 file
Once you e configured thresholds, you can enable the trapping of threshold
violations to the main log file, proviso.log.
About this task
To enable the trapping of threshold violations to the log file, follow these steps:
Procedure
1. 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_TRAPS
property.
5. Set the value to true (default is false) by selecting the check box. This enables
the trapping of threshold violations to the log file.
Chapter 8. Configuring thresholds
129
6. Repeat step 2 - 4 for each threshold violations trapping you want to enable for
the DataChannels.
7. Save the topology.
The following is an example of a threshold violation recorded in the
proviso.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 hosts
About this task
Once you configured thresholds, you can configure Tivoli Netcool Performance
Manager 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 management
system. Netcool/OMNIbus and Webtop, for example, allow a Webtop user to
right-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 with
OMNIbus and Webtop, see the IBM Tivoli Netcool Performance Manager: OMNIbus
Web GUI/Webtop Integration.
To configure the sending of trapped threshold violations to specified hosts, follow
these steps:
Procedure
1. 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_TRAPS
property.
5. Specify the host name and port number combinations to receive trapped
threshold violations. For example,
v localhost:162
Or
v 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 this
parameter is set to false, the IP address of the CME system that sent the trap
is included in the trap header.
8. Save the topology.
130
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 9. Managing MIBs
Explains how to use the MIB compiler to compile MIBs and how to use the MIB
browser to view MIB files and verify object values.
.A MIB file consists of object definitions that manage TCP/IP-based networks. The
variables in a MIB are organized in groups, such as System, Interface, or TCP.
MIB groups
A MIB file contains object definitions, which are typically organized into the
following 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
v
v
v
EGP Group (8)
CMOT Group (9)
Transmission Group (10)
SNMP Group (11)
Compiling a MIB
Tivoli Netcool Performance Manager DataMart includes pre-compiled MIB files.
You can include additional MIB files by importing them and compiling them into
the required Tivoli Netcool Performance Manager DataMart format.
About this task
Compiling a MIB makes Tivoli Netcool Performance Manager aware of the MIB
object identifiers and their values. The compile process occurs in three phases, all
of 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 the
following subdirectories:
v frozen
v
v
oid
src
Important: A MIB is compiled only when both the frozen and OID formats exist.
© Copyright IBM Corp. 2012
131
To compile a MIB, follow these steps:
Procedure
1. 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 Import
File... 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 directory
v Select several consecutive MIB files by clicking the file name for the first
MIB file, then clicking the additional names while holding down the
Shift key
v Select several non-consecutive MIB files by clicking each name while
holding down the Ctrl key
c. Click Yes to continue the import process. The file is copied to the specified
directory and the imported MIB appears in the navigation tree of MIB files
in the left display pane of the MIB Compiler.
5. To begin the compilation, click Compile. A progress indicator displays the
status of the compilation and a message appear in the Traces pane.
Note: The Traces pane displays compilation warning messages in blue and
error messages in red.
132
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Printing or saving trace information
Procedure
1. Right-click in the Traces area to access a menu with the following options
v Reset - clears the Trace area
v Save - lets you print the trace information or save it to a file.
2. Click Save.
Printing trace information
Procedure
1.
2.
3.
4.
Select a printer from the drop down list.
Edit the print command if you want to print in a specific format.
Increase or decrease number of copies by clicking the up and down arrows.
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.
Deleting a MIB
About this task
If for whatever reason you decide to delete a MIB, you can do so by following
these steps:
Procedure
1. 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/dbRep
command, 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 has
2712 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 source
Procedure
1. 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 files
You can view a list of compiled MIB files by accessing the MIB Browser.
About this task
To access the MIB Browser, follow these steps:
Procedure
1. Click Browse to open the MIB Browser.
2. See “Viewing compiled MIB files” for detailed information.
Viewing compiled MIB files
The MIB Browser lets you view a list of compiled MIB files in either tree format or
in group/table format. You can then choose files from the list to review element
information or to verify object values.
Procedure
1. Click MIB Browser in the Metric tab. The MIB Browser dialog box appears
listing compiled MIB files in tree format
2. 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 into
either objects contained in groups or objects contained in tables.
Finding MIB files
You can quickly locate a specific MIB object in the navigation and selection pane.
About this task
To find an item, follow these steps:
134
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Procedure
1. 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 that
item in the tree and the Find Choices dialog box closes.
Loading MIB files
You can temporarily load MIB files into the MIB Browser to review element
information or to verify object values.
About this task
To load MIB files, follow these steps:
Procedure
1. 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.
Chapter 9. Managing MIBs
135
4. Click the name to select the MIB file and click OK. The selected MIB file, and
all its dependencies, appears in the navigation and selection pane. When you
exit the MIB Browser, the MIB file is removed from the display.
Viewing element information
You can view specific element information about the MIB file.
About this task
To view element information, follow these steps:
Procedure
1. 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. No
names 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 values
If you want to verify the values of MIB objects, you can test them directly in the
MIB Browser.
Procedure
1. 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 is
blank, click Refresh to update it.
The Instance and Community text boxes are populated if included as part of
the resource name. The associated SNMP Collector automatically appears in the
SNMP Collector list.
5. Select a MIB file by clicking the name in the navigation and selection pane. The
location of the MIB file in the tree affects what MIB files are included in the
request if:
v The MIB file is located in the final section of the tree, the request is executed
on just that section.
136
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
v The MIB file is located elsewhere in the tree, the request is executed on that
section and all sections below it in the tree. The sections can include an
entire 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 parameters
v MIB files selected
v Results of request
7. Right-click in the Trace area to access a menu with the following options:
v Reset - clears the Trace area
v 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 9. Managing MIBs
137
138
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
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
v
v
v
v
v
View resource information
Export resources
Import resources
Add resources
Delete resources
Deploy reports
For more information about managing resources from the command line, see the
IBM Tivoli Netcool Performance Manager: Command Line Interface Guide.
Filtering elements and subelements
Display specific subsets of information by filtering the elements, subelements, and
composite subelements in your network. Displaying all resources in the Resource
Editor can take a significant amount of time in large deployments. For large
deployments, always use the filter to avoid displaying all resources.
Procedure
1. 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 column
headings then click Apply Filter. Use the following syntax to create your filters:
© Copyright IBM Corp. 2012
Filter
Result
string
Displays all results that match the value of
string.
string*
Displays all results that match the prefix
value of string.
*string
Displays all results that match the suffix
value of string.
*string*
Displays all results that contain the value of
string.
!='string'
Displays all results that have values other
than the value of string.
is null
Displays all results that have no value
defined.
not null
Displays all results that have any value
defined.
139
Viewing resource information
Explains how to view information about elements, subelements, subelement
groups, and element and subelement properties.
Displaying all resources in the Resource Editor can take a significant amount of
time in large deployments. For large deployments, always use the filter to avoid
displaying all resources.
Viewing elements
Procedure
1. 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 is
displayed.
Note: Both IPv4 and IPv6 address formats are supported.
Column Name
Name
Profile
Collector
Description
Type
Description
Displays the name of the element.
Displays the name of the inventory profile
used to discover this element. For more
information, see the IBM Tivoli Netcool
Performance Manager: Installation Guide.
Displays the collector number assigned to
this element.
Displays a descriptive textual name for the
element.
Displays the type of the element:
snmp
Defines an element for SNMP
collections.
default_snmp
Used for SnmpConf.
star_snmp
Used for SnmpConf (@IPrange).
import Defines a host with imported data.
No SNMP collections are available.
Origin
State
140
Displays the method used to add the
element to the database.
Displays the state of the element:
on
Indicates that the element is visible
in the graphical user interface.
off
Indicates that data collection on the
element is stopped and that the
element is no longer visible in the
graphical user interface.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Viewing subelements
Procedure
1. 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. The
following information is displayed:
Column Name
Name
Date
Label
Profile
Family
Element
Instance
Description
Displays the name of the subelement or
composite subelement.
Displays the date for the subelement or
composite subelement.
Displays a descriptive comment for the
subelement or composite subelement.
Displays the name of the inventory profile
used to discover the subelement or
composite subelement. For more
information, see the IBM Tivoli Netcool
Performance Manager: Installation Guide.
Displays the name of the family for the
subelement or composite subelement.
Displays the name of the element for the
subelement or composite subelement.
Displays the name of the instance for the
subelement or composite subelement.
Viewing subelement groups
Procedure
1. 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:
Column Name
Name
Label
Family
Element
Description
Displays the name of the subelement or
composite subelement.
Displays a descriptive comment for the
subelement or composite subelement.
Displays the name of the family for the
subelement or composite subelement.
Displays the name of the element for the
subelement or composite subelement.
Chapter 10. Editing resources
141
Column Name
Instance
Description
Displays the name of the instance for the
subelement or composite subelement.
Type
The type of the group member. Possible
values are GROUP, SE, or CSE.
Relation
The relation of each group member.
Particularly important for composite
subelements.
Name
The name of the group member.
Label
The label of the group member.
Viewing property details
Procedure
1. 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 details
The Detail tabs provide these information:
Properties
The properties and values associated with the selected subelement or
composite subelement.
Relation To
The source subelements or composite subelements to which the selected
composite subelement is linked. The Relation To tab contains:
Relation
The relationship between the selected composite subelement and
each of the source subelements or composite subelements. A
relation can be any string.
Resource
The source subelement or composite subelement.
Relation From
The destination subelements or composite subelements for the selected
composite subelement and the relationship between them. The Relation
From tab contains
Relation
The relationship between the selected composite subelement and
each of the destination subelements or composite subelements. A
relation can be any string.
142
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Resource
The destination subelement or composite subelement.
Viewing reports
Procedure
1. 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:
Column Name
Description
Name
Displays the name of the report.
URL
Displays the universal resource locator for
the report.
Type
Displays the type of the report.
Comment
Displays comments on the report.
Viewing thresholds
Procedure
1. 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 are
displayed:
Column Name
Description
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
Chapter 10. Editing resources
143
Column Name
Description
PWnrT
Period Time
PEvent
Period Event Generation
PDef
Period Definition
MaxNbDay
Baseline Threshold Maximum Number of
Days
MinNbDay
Baseline Threshold Minimum Number of
Days
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 resources
Explains how to export resources for use with another Tivoli Netcool Performance
Manager DataMart installation. You can export elements, subelements, composite
subelements, and subelement groups. Displaying all resources in the Resource
Editor can take a significant amount of time in large deployments. For large
deployments, always use the filter to avoid displaying all resources.
About this task
To export resources, follow these steps:
Procedure
1. 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 subelement
groups.
6. Click Save to export the file. A message box displays when the export process
completes.
7. Click Close.
144
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Importing resources
Explains how to import elements, subelements, composite subelements, and
subelement groups. The file name extensions differ depending on the resource you
are importing. Displaying all resources in the Resource Editor can take a significant
amount of time in large deployments. For large deployments, always use the filter
to avoid displaying all resources.
About this task
To import elements or subelements, follow these steps:
Procedure
1. 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 subelement
groups.
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 resources
Explains how to add elements, subelements, reports, and thresholds.
Displaying all resources in the Resource Editor can take a significant amount of
time in large deployments. For large deployments, always use the filter to avoid
displaying all resources.
Adding elements
Procedure
1. 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 used
to discover this element. For more
information, see the IBM Tivoli Netcool
Performance Manager: Installation Guide.
Collector
Select the collector number assigned to this
element.
Chapter 10. Editing resources
145
Field
Description
sysDesc
Select a descriptive textual name for the
element.
Type
Select the type of the element:
snmp
Defines an element for SNMP
collections.
default_snmp
Used for SnmpConf.
star_snmp
Used for SnmpConf (@IPrange).
import Defines a host with imported data.
No SNMP collections are available.
Comment
Specifies descriptive comments about the
element.
6. Click OK to accept your changes.
7. Click Close to exit the message box.
Adding subelements
Procedure
1. 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 or
composite subelement.
Label
Specifies a descriptive comment for the
subelement or composite subelement.
Family
Select the name of the family for the
subelement or composite subelement.
Element
Specifies the name of the element for the
subelement or composite subelement.
Instance
Specifies the name of the instance for the
subelement or composite subelement.
Invariant
Specifies the invariant entity associated with
the subelement or composite subelement.
6. Click OK to accept your changes.
7. Click Close to exit the message box.
146
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Adding composite subelement relations
Procedure
1. 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
Relation
Name
Label
Element
Instance
Invariant
Family
Description
Specifies the name of the subelement or
composite subelement relation.
Specifies the name of the subelement or
composite subelement.
Specifies a descriptive comment for the
subelement or composite subelement.
Specifies the name of the element for the
subelement or composite subelement.
Specifies the name of the instance for the
subelement or composite subelement.
Specifies the invariant entity associated with
the subelement or composite subelement.
Select the name of the family for the
subelement or composite subelement.
8. Click OK to accept your changes.
9. Click Close to exit the message box.
Adding reports
Procedure
1. 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.
Chapter 10. Editing resources
147
Field
Description
URL
Specifies the universal resource locator for
the report.
Type
Select the type of the report.
Data
Specifies the data displayed in the report.
Comment
Specifies comments on the report.
6. Click OK to accept your changes.
7. Click Close to exit the message box.
Adding thresholds
Explains how to add new thresholds. A threshold is a value that is compared
against metrics to determine if the metrics exceed or drop below a critical limit.
Results appear in Tivoli Netcool Performance Manager DataView reports. You
must 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 parameters
Procedure
1. 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 with
the threshold.
Group
Specifies the subelement group associated
with the threshold.
Sub-Element
Specifies the subelement name associated
with the threshold.
6. Click OK to accept your changes.
Adding threshold mode parameters
Procedure
1. 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. Click the Static Threshold tab.
148
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
6. Click the Mode tab. Enter the following information for the new threshold:
Field
Description
Effective date
Specifies the effective date of action for the
threshold. Setting the date in the past does
not cause reprocessing of data but might
cause thresholds to display on reports.
Mode
Statistic mode
Select a threshold mode for the threshold
from the following:
Under
Violation if data value below
threshold value (either warning or
critical).
Over
Violation is data value is over
threshold value (either warning or
critical).
band
Violation if data is not between the
values.
Select a statistic mode for the threshold from
the following:
raw
Raw data from collectors.
min, max, avg, sum, count
Data from aggregations.
Calculation mode
Select a calculation mode for the threshold
from either Standard, Normalized, or Scaled.
Calculation value
Specifies the calculation value for the
threshold if you selected Scaled as the
Calculation mode.
7. Click OK to accept your changes.
Adding threshold burst parameters
A burst threshold removes the natural network bursts by evaluating how many
times in a row the violations occurred over a certain period of time.
Procedure
1. 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. 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 threshold
for BURST thresholds. NULL indicates that
the threshold is not defined.
Chapter 10. Editing resources
149
Field
Description
Critical level
Specifies the level of the critical threshold
for BURST thresholds. NULL indicates that
the threshold is not defined.
Event generation
Select whether to generate events for the
BURST threshold.
Warning time
Specifies the time limit (in seconds) for
warning BURST thresholds. NULL indicates
that the threshold is not defined. "0s"
indicates that the threshold is violated when
the metric exceeds the threshold. For
example, the input format: 1d 2h 3m 4s
equals a duration of 1 day, 2 hours, 3
minutes, and 4 seconds.
Critical time
Specifies the time limit (in seconds) for
critical BURST thresholds. NULL indicates
that the threshold is not defined. "0s"
indicates that the threshold is violated when
the metric exceeds the threshold. For
example, the input format: 1d 2h 3m 4s
equals a duration of 1 day, 2 hours, 3
minutes, and 4 seconds.
9. Click OK to accept your changes.
Adding threshold period parameters
A period threshold involved the concept of duration for which the threshold is
violated. This duration is accumulated until the end of the expected service level
period.
Procedure
1. 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. 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:
150
Field
Description
Warning level
Specifies the level of the warning threshold
for PERIOD thresholds. NULL indicates that
the threshold is not defined.
Critical level
Specifies the level of the critical threshold
for PERIOD thresholds. NULL indicates that
the threshold is not defined.
Event generation
Select whether to generate events for the
PERIOD threshold.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Field
Description
Warning time
Specifies the time limit (in seconds) for
warning PERIOD thresholds. NULL
indicates that the threshold is not defined.
"0s" indicates that the threshold is violated
when the metric exceeds the threshold. For
example, the input format: 1d 2h 3m 4s
equals a duration of 1 day, 2 hours, 3
minutes, and 4 seconds.
Critical time
Specifies the time limit (in seconds) for
critical PERIOD thresholds. NULL indicates
that the threshold is not defined. "0s"
indicates that the threshold is violated when
the metric exceeds the threshold. For
example, the input format: 1d 2h 3m 4s
equals a duration of 1 day, 2 hours, 3
minutes, and 4 seconds.
Period Definition
Select a period definition for the threshold
as either Day, Week, Month, or All. All
period indicates that the Complex Metrics
Engine (CME) uses the period of the
aggregation tables.
9. Click OK to accept your changes.
Adding baseline threshold parameters
Procedure
1. 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. Click the Baseline Threshold tab.
6. Select the Enable Threshold check box.
7. Enter the following information for the new threshold:
Field
Max # of days
Min # of days
Calculation
Sensitivity (upper)
Description
Specifies the maximum number of days used
to calculate the baseline threshold.
Specifies the minimum number of days used
to calculate the baseline threshold.
Select the baseline calculation mode from
either PreviousDays or
PrevSameDayofWeek.
Enter the upper threshold limit (number of
standard deviations above the baseline) that
must be violated before generating an event.
Chapter 10. Editing resources
151
Field
Sensitivity (lower)
Permitted time outside baseline
Event generation
Mode
Description
Enter the lower threshold limit (number of
standard deviations below the baseline) that
must be violated before generating an event.
Enter the time limit (in minutes, hours, or
days) that a threshold can be violated before
generating an event.
Select whether to generate events for
baseline threshold violations.
Select a violation mode for the threshold
from the following:
Under
Violation if data value below
threshold value.
Over
Violation is data value is over
threshold value.
band
Violation if data is not between the
values.
8. Click OK to accept your changes.
Creating a property
About this task
Displaying all resources in the Resource Editor can take a significant amount of
time in large deployments. For large deployments, always use the filter to avoid
displaying all resources.
To create a new property, follow these steps:
Procedure
1. 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 names
Properties are the attributes or characteristics of an element or subelement that
defines its state, appearance, or value. These properties are installed by Tivoli
Netcool 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 with
raw data or other complex metrics. The CME determines which properties are
required and loads them from the database at startup. The properties are kept in
152
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
CME memory. When a property value changes in the database, the CME obtains
the new value from the next database load.
Table 8. Subelement Properties
Property
hostname
description
name
hostIP
networkArea
type
physicalCapacity
hosturl
parent
hostType
parentType
class
subType
protocol
Description
A user-defined name assigned to the host
upon which this resource resides. Provided
during network configuration.
Open-format description text used for
grouping.
A user-defined name that is user-defined for
this entity during network configuration.
This name is used only for grouping (it is
not supported by DM or DV as a SE label).
Physical IP address of the host upon which
this resource resides.
Network area (for example, BackBone, CPE)
of the entity.
Open-format name of the specific type of
resource represented (for example, Ethernet,
DS1).
The maximum speed of this resource (bps).
URL address assigned to the host upon
which a resource resides.
Open-format name or ID assigned to an
entity, other than a physical host (see
'hostName' Property), that can be considered
as a "parent" containing this resource.
Open-format "type" classification of the
device upon which this resource resides.
Open-format type classification of the parent
of this resource.
Open-format name of the general class of
resource represented (for example, device,
interface, logical port, or end-to-end
connection).
If needed, more specific type information or
the resource (NNI, UNI).
Transmission protocol specific to the
resource (ATM, Frame Relay, IP, IPSec, TCP,
UDP, MPLS).
Chapter 10. Editing resources
153
Table 8. Subelement Properties (continued)
protocolVersion
model
modelID
version
patch level
country
city
state
province
region
regionID
location
locationID
status
priority
committedCapacity
committedBurstCapacity
committedPeakCapacity
owner
154
Version of transmission protocol being used.
Open-format model name of the resource.
Open-format model ID string of the
resource.
Open-format version identification of the
resource.
Open-format patch level identification of the
resource.
The country in which the resource resides.
The city, town, or municipality in which the
resource resides.
The state in which the resource resides.
The province in which the resource resides.
Open-format region name in which the
resource resides.
Open-format ID string assigned to the
region in which the resource resides.
Open-format physical location name in
which the resource resides.
Open-format ID string assigned to the
physical location in which the resource
resides.
Operational status of the resource (active,
initializing, maintenance).
Open-format priority name or code.
The steady-rate bandwidth (bps) committed
for transfer over a resource.
The transmission rate (bps) committed for
short traffic bursts (for a pre-agreed
duration) over a resource.
The maximum transmission rate committed
for transfer over this resource.
Service provider employee name/ID to
which this resource belongs.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Table 8. Subelement Properties (continued)
ownerCustomTag
department
departmentID
network
networkID
privateNetwork
privateNetworkID
customer
customerID
customerType
customerFacingName
securityProfileMask
operation
timeout
User-definable property for custom resource
organization attributes.
Service provider department to which a
resource belongs.
ID of the service provider department to
which a resource belongs.
The name of the network of which a
resource is a part.
The ID of the network of which a resource is
a part.
The name of the private (virtual) network of
which this entity is a part.
The ID of the private (virtual) network of
which this entity is a part.
The name of the specific customer that a
resource services.
The ID of the specific customer that this
resource services.
The type of customer that a resource
services.
Alternate name to be used for this resource
in customer-facing reports, and messages.
Open-format string for definition of a text
mask which can be generated for SEs by a
custom user group control system and used
within rule conditions to organize user
groups' access to resource views.
For monitor probes, such as RMON. The test
operation being executed.
For monitor probes, such as RMON. The
timeout duration (seconds) for target
response.
sourceIP
For unidirectional entities (end-to-end
simplex connections, network test probes).
The IP address of the originating side.
sourceURL
For unidirectional entities (end-to-end
simplex connections, network test probes)
the URL of the originating side.
sourcePort
For unidirectional entities (end-to-end
simplex connections, network test probes).
The IP port used on the originating side.
Chapter 10. Editing resources
155
Table 8. Subelement Properties (continued)
destIP
destURL
destPort
corbaPort
targetDirectory
path
For unidirectional entities (end-to-end
simplex connections, network test probes).
The URL of the terminating side.
For unidirectional entities (end-to-end
simplex connections, network test probes).
The IP port used on the terminating side.
The number identifying the CORBA port
this entity uses.
File system directory to which this entity
delivers processed data.
Directory path within which this entity
resides.
tablespace
Name of the table space in which this table
resides.
tablespaceClass
Aggregation characteristics of the table space
of 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.
channel
channelTableSetType
measurementInterval
156
For unidirectional entities (end-to-end
simplex connections, network test probes).
The IP address of the terminating side.
ID of the Tivoli Netcool Performance
Manager channel of which this entity is part.
Type of Channel Table Set of which this
table is part: Current-"H0"; Recent-"H1";
Ancient-"H2"; Current to Recent
Staging-"S0"; Recent to Ancient Staging-"S1"
The duration of time (seconds) over which
raw statistics from this resource are
computed and possibly pre-aggregated by
that resource or by an intermediate
management system. This property also can
be used in network monitoring probe
implementations to represent the configured
amount of time wait between probe test
executions.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Table 8. Subelement Properties (continued)
measurementSubInterval
The duration of time (seconds) over which
raw statistics from this resource are
subaggregated intra-period (for example, for
peak values within the overall measurement
interval). Also can be used to represent the
duration that multi-sample network probes
wait between each resend within a single
probe execution.
Table 9. DataView User Properties
Property
Description
DV_UserTimeZone
Defines the default time zone to be used for
the user whenever a group that has not been
assigned it's own time zone is viewed in the
portal.
DV_UserShowCurrentPeriod
DV_UserProfile
Controls access to active-period report
viewing. If undefined or set to "true:", the
user is allowed to view reports for the
current, active, time period. If set to "false",
the user cannot view reports for the current
period.
Defines the general user type for control of
certain security options. Valid settings
include the following:
v NOC - Network Operations Center user,
few restrictions.
v PSLA - Proactive Service Level Agreement
personnel, moderate restriction.
v SLA - users, highest restrictiveness.
DV_UserResourceName
Defines which subelement name definitions
must be used for SE labels displayed to the
particular user. Valid settings include the
following:
v 1 - Use the SEs' internal ALIAS field
values (also dubbed "SE Labels").
v 2 - Use the SEs' internal NAME field
values.
v 1771 - Use the value defined in the
"customerFacingName" Property for each
SE.
DV_UserLoginName
DV_UserName
DataView user-scope property that can be
set with the login name attributed to a
DataView user. This property is used for
informational display on reporter summary
headings only.
DataView user-scope property that can be
set with the name attributed to a DataView
user. This property is used for informational
display on reporter summary headings only.
Chapter 10. Editing resources
157
Table 9. DataView User Properties (continued)
DV_UserCustomLogoFile
DataView user-scope property that can be
set with a link to an image file statically
defining a custom graphic to be displayed
on reporter summary headings.
Modifying resources
Explains how to modify elements, subelements, reports, and thresholds by using
Resource Editor.
Note: Displaying all resources in the Resource Editor can take a significant amount
of time in large deployments. For large deployments, always use the filter to avoid
displaying all resources.
Modifying an element
Procedure
1. 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 used
to discover this element. For more
information, see the IBM Tivoli Netcool
Performance Manager: Installation Guide.
Collector
Select the collector number assigned to this
element.
sysDesc
Select a descriptive textual name for the
element.
Type
Select the type of the element:
snmp
Defines an element for SNMP
collections.
default_snmp
Used for SnmpConf.
star_snmp
Used for SnmpConf (@IPrange).
import Defines a host with imported data.
No SNMP collections are available.
Comment
158
Specifies descriptive comments about the
element.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Field
State
Description
Select the state of the element:
on
Indicates that the element is visible
in the graphical user interface.
off
Indicates that data collection on the
element is stopped and that the
element is no longer visible in the
graphical user interface.
Origin
Specifies the method used to add the
element to the database.
User
Specifies the user who created the element.
Date
Specifies when the element was created or
modified.
6. Click OK to accept your modifications.
Modifying a subelement
About this task
To modify a subelement or composite subelement, follow these steps:
Procedure
1. 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 or
composite subelement.
Label
Specifies a descriptive comment for the
subelement or composite subelement.
Element
Specifies the name of the element for the
subelement or composite subelement.
Instance
Specifies the name of the instance for the
subelement or composite subelement.
Invariant
Specifies the invariant entity associated with
the subelement or composite subelement.
Family
Displays the name of the family for the
subelement or composite subelement.
Chapter 10. Editing resources
159
Field
State
Description
Select the state of the subelement or
composite subelement:
on
the subelement or composite
subelement is visible in the
graphical user interface.
off
data collection on the subelement
or composite subelement is stopped
and that the element is no longer
visible in the graphical user
interface.
Origin
Specifies the method used to add the
subelement or composite subelement to the
database.
User
Specifies the user who created the
subelement or composite subelement.
Date
Specifies when the subelement was created
or modified or composite subelement.
6. Click OK to accept your modifications.
Modifying a report
Procedure
1. 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 for
the report.
Type
Data
Comment
Select the type of the report.
Specifies the data displayed in the report.
Specifies comments on the report.
6. Click OK to accept your modifications.
160
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Modifying Thresholds
About this task
Resources and Metrics
Procedure
1. 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 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. Change
the following information for the threshold:
Field
Description
Metric
Specifies the formula name associated with
the threshold.
Group
Specifies the subelement group associated
with the threshold.
Sub-Element
Specifies the subelement name associated
with the threshold.
5. Click OK to accept your changes.
Mode
About this task
The following thresholds are static thresholds:
v Mode
v Burst
v Period
v Baseline
Procedure
1. 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 that you want to modify.
4. Select Update from the Edit menu or right-click the threshold name and select
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:
Chapter 10. Editing resources
161
Field
Effective date
Mode
Description
Specifies the effective date of action for the
threshold. Setting the date in the past will
not cause re-processing of data but may
cause thresholds to display on reports.
Select a threshold mode for the threshold
from the following:
v Under - Violation if data value below
threshold value (either warning or
critical).
v Over - Violation is data value is over
threshold value (either warning or
critical).
v band - Violation if data is not between the
values.
Statistic mode
Select a statistic mode for the threshold from
the following:
v raw - Raw data from collectors.
v min, max, avg, sum, count - Data from
aggregations.
Calculation mode
Calculation value
Select a calculation mode for the threshold
from either Standard, Normalized, or Scaled.
Specifies the calculation value for the
threshold if you selected Scaled as the
Calculation mode.
7. Click OK to accept your changes.
Burst
About this task
A burst threshold removes the natural network bursts by evaluating how many
times in a row the violations occurred over a certain period of time.
To modify threshold burst parameters, follow these steps:
Procedure
1. 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 that you want to modify.
4. Select Update from the Edit menu or right-click the threshold name and select
Update from the menu.
5. Click the Static Threshold tab.
6. Click the Burst tab.
The Add Threshold dialog box opens.
Change the following information for the threshold:
162
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Field
Warning level
Critical level
Event generation
Warning time
Critical time
Description
Specifies the level of the warning threshold
for BURST thresholds. NULL indicates that
the threshold is not defined.
Specifies the level of the critical threshold
for BURST thresholds. NULL indicates that
the threshold is not defined.
Select whether to generate events for the
BURST threshold.
Specifies the time limit (in seconds) for
warning BURST thresholds. NULL indicates
that the threshold is not defined. "0s"
indicates that the threshold is violated when
the metric exceeds the threshold. For
example, the input format: 1d 2h 3m 4s
equals a duration of 1 day, 2 hours, 3
minutes, and 4 seconds.
Specifies the time limit (in seconds) for
critical BURST thresholds. NULL indicates
that the threshold is not defined. "0s"
indicates that the threshold is violated when
the metric exceeds the threshold. For
example, the input format: 1d 2h 3m 4s
equals a duration of 1 day, 2 hours, 3
minutes, and 4 seconds.
7. Click OK to accept your changes.
Period
About this task
A period threshold involved the concept of duration for which the threshold is
violated. This duration is accumulated until the end of the expected service level
period.
To modify threshold burst parameters, follow these steps:
Procedure
1. 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 that you want to modify.
4. Select Update from the Edit menu or right-click the threshold name and select
Update from the menu.
5. Click the Static Threshold tab.
6. Click the Period tab.
The Add Threshold dialog box opens.
Change the following information for the threshold:
Chapter 10. Editing resources
163
Field
Description
Warning level
Specifies the level of the warning threshold
for PERIOD thresholds. NULL indicates that
the threshold is not defined.
Critical level
Event generation
Warning time
Critical time
Period Definition
Specifies the level of the critical threshold
for PERIOD thresholds. NULL indicates that
the threshold is not defined.
Select whether to generate events for the
PERIOD threshold.
Specifies the time limit (in seconds) for
warning PERIOD thresholds. NULL
indicates that the threshold is not defined.
"0s" indicates that the threshold is violated
when the metric exceeds the threshold. For
example, the input format: 1d 2h 3m 4s
equals a duration of 1 day, 2 hours, 3
minutes, and 4 seconds.
Specifies the time limit (in seconds) for
critical PERIOD thresholds. NULL indicates
that the threshold is not defined. "0s"
indicates that the threshold is violated when
the metric exceeds the threshold. For
example, the input format: 1d 2h 3m 4s
equals a duration of 1 day, 2 hours, 3
minutes, and 4 seconds.
Select a period definition for the threshold
as either Day, Week, Month, or All. All
period indicates that the Complex Metrics
Engine (CME) uses the period of the
aggregation tables.
7. Click OK to accept your changes.
Baseline Threshold
About this task
To modify baseline threshold parameters, follow these steps:
Procedure
1. 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 that you want to modify.
4. Select Update from the Edit menu or right-click the threshold name and select
Update from the menu.
5. Click the Static Threshold tab.
6. Click the Baseline Threshold tab.
The Add Threshold dialog box opens.
Change the following information for the threshold:
164
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Field
Description
Max # of days
Specifies the maximum number of days used
to calculate the baseline threshold.
Min # of days
Calculation
Sensitivity (upper)
Sensitivity (lower)
Permitted time outside baseline
Event generation
Mode
Specifies the minimum number of days used
to calculate the baseline threshold.
Select the baseline calculation mode from
either PreviousDays or
PrevSameDayofWeek.
Enter the upper threshold limit (number of
standard deviations above the baseline) that
must be violated before generating an event.
Enter the lower threshold limit (number of
standard deviations below the baseline) that
must be violated before generating an event.
Enter the time limit (in minutes, hours, or
days) that a threshold can be violated before
generating an event.
Select whether to generate events for
baseline threshold violations.
Select a violation mode for the threshold
from the following:
v Under - Violation if data value below
threshold value.
v Over - Violation is data value is over
threshold value.
v band - Violation if data is not between the
values.
7. Click OK to accept your changes.
Deleting resources
Explains how to delete the following resources from the database:
v Elements and subelements
v Sub-element groups
v subelements within groups
v Properties associated with elements and subelements
Note: When you delete an element, you delete the associated subelements. When
you delete a property, you delete only the property. Displaying all resources in the
Resource Editor can take a significant amount of time in large deployments. For
large deployments, always use the filter to avoid displaying all resources.
Chapter 10. Editing resources
165
Deleting elements or subelements
Procedure
1. 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 groups
Procedure
1. 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 groups
Procedure
1. 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 properties
Procedure
1. 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.
5.
6.
7.
166
Click
Click
Click
Click
Detail to display the properties table.
the property name you want to delete.
the Delete icon in the toolbar. A confirmation message opens.
Yes to delete, or No to cancel.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Deleting composite Subelement relations
Procedure
1. 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 reports
Explains how to manually deploy reports using Resource Editor.
Procedure
1. 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.
8.
9.
10.
11.
12.
13.
14.
15.
Copy the report by pressing Ctrl + C.
Click the Report SE Group tab to select it again.
Click the group name in the left pane to highlight it.
Press Ctrl + V to paste the report into the frame. You are prompted to
confirm your choice.
Click Yes to continue. The copied report displays in the right pane.
Move the cursor to the left pane and scroll up to select SUB-ELEMENTS.
Right-click and select AutoGrouping from the pull down menu. A
confirmation prompt opens.
Click Yes to continue.
Click Close to exit the message box or click Details to view a description of
any errors or warnings.
Chapter 10. Editing resources
167
168
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 11. Viewing collected data
Explains how to view various collected data.
Viewing graphical charts for files
Explains how to view a list of curves contained in a file, which you can then
display in graphical form.
About this task
To view curves, follow these steps:
Procedure
1. Click Data Viewer in the Data Manager tab. The following windows appears:
The foreground window lets you select data to display. The background
window 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.
© Copyright IBM Corp. 2012
169
Viewing graphical charts for subelements
Explains how to view graphical charts for subelements.
About this task
To view graphical charts for subelements, follow these steps:
Procedure
1. 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 the
aggregation type that you select.
Max - Provides maximum values of the raw data according to the
aggregation type that you select.
Sum - Provides the sum of the raw data according to the aggregation type
you select.
Count - Provides the number of raw data according to the aggregation
type you select.
8. Select an aggregation type in the Aggregation type list from the following:
Per day - Aggregations per day
Per week - Aggregations per week
Per 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 the
meridian of Greenwich used as the prime basis of standard time
throughout the world.
AggSet 1 to AggSet 6 - An Aggregation Set defines an offset from GMT
and is associated with groups. This feature can have a different name if
customized.
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.
170
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Viewing graphical charts for subelement groups
Explains how to view graphical charts for subelements groups.
Procedure
1.
2.
3.
4.
Click Data Viewer in the Data Manager tab.
Click the Sub-Element Groups tab.
Select one or more subelement groups from the list in the left pane.
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 the
aggregation type that you select.
Max - Provides maximum values of the raw data according to the
aggregation type that you select.
Sum - Provides the sum of the raw data according to the aggregation type
you select.
Count - Provides the number of raw data according to the aggregation type
you select.
7. Select an aggregation type in the Aggregation type list from the following:
Per day - aggregations per day
Per week - aggregations per week
Per 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 meridian
of Greenwich used as the prime basis of standard time throughout the
world.
AggSet1 to AggSet 6 - An Aggregation Set defines an offset from GMT and
is associated with groups.
Saving a graph
Explains how to save a graph
Procedure
1. 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 solar
time of the meridian of Greenwich used as the prime basis of standard time
throughout 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 value
are preserved in the data lines.
Chapter 11. Viewing collected data
171
BOF format - Binary Object Format provides an extensible, space and time
efficient storage format for storing Tivoli Netcool Performance Manager
objects in flat files. This format provides a high-performance format for
transferring information between distributed Tivoli Netcool Performance
Manager subsystems in a store and forward environment.
4. Specify where to save the graph in the File box or click Browse to find the
location.
5. Click OK to accept your selections.
Printing a graph
Explains how to set up printing for graphical charts in the Data Viewer.
About this task
To set up printing, follow these steps:
Procedure
1. 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 graphs
Explains how to configure a graph.
Displaying crosshairs
Procedure
1. Right-click an area inside the graph and select the Configuration menu item.
2. Click Display CrossHair in the General tab.
3.
4.
5.
6.
172
Select a line width for the crosshairs from the Width list.
Select a dash format for the crosshairs from the Dash list.
Select a color for the crosshairs from the Color list menu.
Click OK to accept your selections. Crosshairs appears in the graph. For
example:
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Displaying a grid
Procedure
1. 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 title
Procedure
1.
2.
3.
4.
Right-click an area inside the graph and select the Configuration menu item.
Click the General tab.
Click Configure Title in the General tab.
Select a font style for the title from the Font list.
5.
6.
7.
8.
9.
Select a weight for the title from the Weight list.
Select a slant for the title from the Slant list.
Select a point size for the title from the Size list.
Select a color for the title from the Color box.
Click OK to accept your selections. A title appears in the graph.
Chapter 11. Viewing collected data
173
Configuring the X-Axis
Procedure
1.
2.
3.
4.
Right-click an area inside the graph and select the Configuration menu item.
Click the Axis tab and select X axis.
Enter a title for the X axis in the Title box.
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, hour
minute). You can enter any character you desire such as forward slash (/)
colons (:), semicolons (;).
The following keypad options are available:
Year = YYYY
Month = MM
Week = ww
Day = dd
Hour = hh
Minute = mm
CR = \n is carriage return to next line
7. Click OK to accept your selections. The X axis in the graph is configured
accordingly.
Customizing the Y-Axis
Procedure
1. Right-click an area inside the graph and select the Configuration menu item.
2. Click the Axis tab and select Y axis.
3.
4.
5.
6.
7.
Select Y Axis in the Axis tab.
Enter a title for the Y axis in the Title box.
Select a line width for the Y-axis from the Width list.
Select a color for the Y-axis from the Color list.
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 lines
than the Linear option).
8. Click OK to accept your selection. The Y-axis in the graph is configured
accordingly.
Configuring curves
Procedure
1.
2.
3.
4.
Right-click an area inside the graph and select the Configuration menu item.
Click the Curves tab.
Select a curve that you want to modify from the Curve list.
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.
174
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
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 legend
Procedure
1.
2.
3.
4.
Right-click an area inside the graph and select the Configuration menu item.
Click the Legend tab.
Click Yes to display the legend.
Select the position for the legend in the Position list from the following:
5.
Top - Top of graph
Bottom - Under graph
Right - Right of graph
Left - Left of graph
Plot Area - In the graph
Select a font for the legend from the Font list to choose a font style for the
title.
Select a weight for the legend from the Weight list.
Select a slant for the legend from the Slant list.
Select a point size for the legend from the Size list.
Select a color for the legend from the Color box
6.
7.
8.
9.
10. Click OK to accept your selections. A legend appears in the graph.
Chapter 11. Viewing collected data
175
176
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 12. Viewing the list of collectors
Explains how to view information about both active and non-active collectors
using the Collector Information Tool.
About this task
The collectinfo command-line interface (CLI) command launches the Collector
Information Tool from the command line. For more information, see the IBM Tivoli
Netcool Performance Manager: Command Line Interface Guide.
To view the collectors list, follow these steps:
Procedure
1. 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 the
system on which the collector is installed.
Port
Indicates the communication port number
for the collector.
Type
Indicates the collector type.
Installation Directory
Indicates the directory where the collector is
installed.
Viewing collector information
Explains how to view detailed information about a collector.
Procedure
1. 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:
© Copyright IBM Corp. 2012
Item
Description
Green traffic light
Indicates that the collector is active and
operational.
Yellow traffic light
Indicates that the collector is in a transitory
state between start-up and shutdown. This is
a temporary state.
177
Item
Description
Red traffic light
Indicates that the collector is not active or
operational.
Refresh Interval
Indicates the frequency in which the
information displayed in the tabs is
refreshed (in seconds).
Current debug level
Indicates the current debug level of the
collector. "0" indicates a minimal debug. The
level should be set to "0"; a level of "1" or
more is for troubleshooting purposes.
Version
Displays the version date and operating
system for the collector.
Server
Displays the name of the computer on
which the collector is running.
Port
Displays the port number that the collector
uses to communicate with Tivoli Netcool
Performance Manager DataMart.
Connections
Displays the number of clients connected to
the collector.
SysUpTime
Displays the amount of time that the
collector has run without interruption (in
days, hours, minutes, and seconds).
Current Time
Displays the day, month, year, and time of
day as set on the server where the collector
is running (dependent on your time zone).
The time shown here can be different from
local time. This is the time that Tivoli
Netcool Performance Manager DataMart
uses to schedule data collection, if you
declare a calendar from 8 am to 8 pm.
The Actions group displays the following information:
178
Item
Description
Refresh interval
Modifies the current refresh value frequency.
Start/Stop button
Launches or shuts down the local collector.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Item
Current tab
Description
Displays the following options:
Note: Tivoli Netcool Performance Manager
DataMart does not permanently save your
selections in the Current tab.
v Debug level - Modifies the debug level of
the collector. Contact technical support at
IBM for more information about
debugging.
v Log Path - Saves the debug information
file (ServReqDaemonxxxx.log) to a specific
path. You can use the Directory Selection
button to select the log path. The default
log directory is $PVMHOME/log.
v Date in file - Displays the creation date in
the log file name. Select Yes to activate
this option. For example,
pvmd_9991015_16348.log.
v Channel in file - Displays the request
number in the log file name. Selecting this
option creates one file per request ID.
Select Yes to activate this option.
Note: The Channel in file option creates
multiple files (one for each request).
Tivoli Netcool Performance Manager
DataMart permanently saves and stores your
selections in the configuration file. For
example, in $PVMHOME/conf/pvmd.log on the
server system.
Viewing scheduler information
The Scheduler maintains the internal list of the requests for data. The Scheduler
regularly scans the list to determine whether requests are executed placed into a
waiting queue. A task placed in a waiting queue is flagged as "READY." You can
view statistics compiled by the collector about the planning of requests.
Procedure
1. 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 Priority
Mode requests on the current collector.
Chapter 12. Viewing the list of collectors
179
Item
Execute requests
Description
Indicates the number of requests being
executed on the collector.
v Execute external requests (Nb)
[immediate] - Indicates the number of
external requests being executed on the
collector.
v Execute internal requests (Nb)
[immediate] - Indicates the number of
internal requests being executed on the
collector.
Items Processed
Indicates the collector activity level. The
activity level is measured in number of
requests executed per second over a specific
time period.
v Items Processed Average (Nb) [last 24
hours] - Indicates the number of requests
executed during the last 24 hours.
v Items Processed Average (Nb) [last hour]
- Indicates the number of requests
executed during the last hour.
v Items Processing Rate (Nb/s) [last 24
hours] - Indicates the request execution
rate per second during the last 24 hours.
You can compare this activity level with
results on comparable systems to evaluate
performance.
v Items Processing Rate (Nb/s) [last hour] Indicates the request execution rate per
second during the last hour. This rate is
similar to the rate for the last 24 hours but
is more sensitive to variations during
collections over longer periods (longer
than one hour).
Items Scheduled
Requests that need to be executed. The
Scheduler scans the list to determine the
requests to execute or to place in the waiting
queue.
v Items Scheduled (Nb) [immediate]
indicates the number of requests
generated in this list.
v Max Items Scheduled (Nb) [immediate]
indicates the maximum configuration
value for the request list size.
180
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Item
Queue Max Size
Description
Third of the three waiting queues where a
thread searches for a request number to
execute.
v Queue Max Size (Nb) [last 24 hours]
indicates the maximum size attained by
the queue during the last 24 hours.
v Queue Max Size (Nb) [last hour]
indicates the maximum size attained by
the queue during the last hour.
v Queue Size (Nb) [immediate] indicates
the current size of the queue.
Threads
Collector activity creates threads. The
collector verifies it can activate a thread each
time it executes a collection or launches a
command. If it cannot activate a thread, no
collector activity occurs and reliability is
diminished.
v Threads (Nb) [immediate] - Indicates the
number of threads created through
collector activity. This is a realtime
counter. The value can change quickly
from 1 to MaxThreadedItems. You can
tune this value in the registry.conf file in
the following location:
$PVMHOME/conf/registry.conf
v Threads Availability (%) [last 24 hours] Indicates collector reliability during the
last 24 hours.
v Threads Availability (%) [last hour] Indicates collector reliability during the
last hour.
internal errors (Nb) [cumul]
Indicates the number of memory errors
detected and corrected. This counter needs
to remain at zero. If it is not at zero, restart
the collector.
Viewing data manager information
The 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 file
when the queue reaches a specified size. Each time the Data Manager transfers
data it stores information about the job.
Procedure
1. 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:
Chapter 12. Viewing the list of collectors
181
Item
Description
.dat files
v dat files (nb) [immediate] - Indicates the
number of .dat files located in the
$PVMHOME/data directory.
v dat files (KB) [immediate] - Indicates the
size of the .dat file.
Average Storage Time
Specifies the average time to store a measure
in a local file.
v Average Storage Time (ms) [last 24
hours] - Indicates the average processing
time for a measure during the last 24
hours.
v Average Storage Time (ms) [last hour] Indicates the average processing time for
a measure during the last hour.
Congestion State
Filesystem
Indicates the Congestion State code.
Indicates file system space information:
v Filesystem FSLL (KB) [immediate] Indicates the size of the FSLL for the file
system.
v Filesystem available (KB) [immediate] Indicates the available size of the file
system.
v Filesystem free space (KB) [immediate] Indicates the amount of free space on the
file system.
v Filesystem quota (KB) [immediate] Indicates the size of the quota for the file
system.
v Filesystem used (KB) [immediate] Indicates the amount of space used on the
file system.
182
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Item
Measures
Description
A measure is a record inserted into the
record file. Each insertion is measured in
time and the median value is posted.
v Measures Processed Average (Nb) [last
24 hours] - Indicates the number of
measures processed during the last 24
hours.
v Measures Processed Average (Nb) [last
hour] - Indicates the number of measures
processed during the last hour.
v Measures Lost (Nb) [cumul] - Indicates
the number of measures that have been
lost since the start of the collector. These
measures were collected but were not
saved.
v Measures Lost (Nb) [last 24 hours] Indicates the number of measures lost
during the last 24 hours. These measures
were collected but were not saved.
v Measures Lost (Nb) [last hour] - Indicates
the number of measures lost during the
last hour. These measures were collected
but were not saved.
v Measures Stored (Nb) [cumul] - Indicates
the total number of measures stored. For
example, total number of answers from
metrics requested.
v Measures Stored (Nb) [last 24 hours]
indicates the total number of measures
stored. For example, the total number of
answers from metrics requested over the
last 24 hours.
v Measures Stored (Nb) [last hour]
indicates the total number of measures
stored. For example, the total number of
answers from metrics requested over the
last hour.
Save Availability
Displays the reliability of data insertion.
Reliability of 100% means that all measures
are correctly inserted. A reliability rate of
less than 100% does not necessarily indicate
a loss of measures, but should be
investigated.
v Save Availability (%) [last 24 hours] Indicates the calculated insertion
reliability during the last 24 hours.
v Save Availability (%) [last hour] Indicates the calculated insertion
reliability during the last hour.
Chapter 12. Viewing the list of collectors
183
Viewing target information
Each time the collector interacts with an SNMP agent, information about the
interaction is recorded.
Procedure
1. 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:
184
Item
Description
Agent SNMP Version [immediate]
Indicates the SNMP Version of the agent for
the collector.
Average SNMP Response Time (ms) [last
hour]
Indicates the average elapsed time between
the sending of the first SNMP packet and its
return. Time is not calculated on the
exchanged packets during the MIB browse.
CALC Errors (Nb) [last hour]
Indicates the number of CALC errors that
occurred in the last hour.
CPU Load (Nb OIDs) [last hour]
Indicates the estimated CPU load needed by
the collector to handle all requests relating
to this target. This measurement integrates
the number of OIDs handled to solve the
requests, the number of requests necessary,
and the frequency of each interrogation.
Discovery Received PDU (Nb) [last hour]
Indicates the number of PDUs received as
part of the discovery process in the last
hour.
Discovery Received PDU Max Size (bytes)
[last hour]
Indicates the maximum size of PDUs
received as part of the discovery process in
the last hour.
Discovery Received PDU Total Size (bytes)
[last hour]
Indicates the total size of PDUs received as
part of the discovery process in the last
hour.
Discovery Sent PDU (Nb) [last hour]
Indicates the number of PDUs sent as part
of the discovery process in the last hour.
Discovery Sent PDU Max Size (bytes) [last
hour]
Indicates the maximum size of PDUs sent as
part of the discovery process in the last
hour.
Discovery Sent PDU Total Size (bytes) [last
hour]
Indicates the total size of PDUs sent as part
of the discovery process in the last hour.
Expected Measures (Nb) [last hour]
Indicates the number of measures expected
in the last hour.
Max SNMP Response Time (ms) [last hour]
Indicates the maximum amount of time for
an SNMP response that occurred in the last
hour.
OID Rate (Nb/s) [last hour]
Indicates the OID rate that occurred in the
last hour.
Produced Measures (Nb) [last hour]
Indicates the number of measures produced
in the last hour.
Received PDU (Nb) [last hour]
Indicates the number of PDUs received in
the last hour.
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Item
Description
Received PDU Max Size (bytes) [last hour]
Indicates the maximum size of PDUs
received in the last hour.
Received PDU Total Size (bytes) [last hour]
Indicates the total size of PDUs received in
the last hour.
SNMP Availability (%) [last hour]
Indicates the reliability of the interaction
with SNMP agents. A value of 0% can
indicate a bad community name or that the
timeout value is insufficient. A value more
than 0% but less than 100% is often caused
by timeouts during the SNMP interaction.
SNMP Errors (Nb) [last hour]
Indicates the total amount of errors in the
SNMP protocol encountered during the
interaction. An error cannot occur when the
community name is correct and the timeout
is correctly configured. An error signifies
either an agent problem in responding to a
packet or an error between the collector MIB
and the MIB supported by the agent. Most
often it indicates a problem with a formula.
SNMP Requests (Nb) [cumul]
Indicates the total number of executed
requests on equipment since the start of the
collector. You can identify the equipment
with a high rate of requests.
Sent PDU (Nb) [last hour]
Indicates the number of PDUs sent in the
last hour.
Sent PDU Max Size (bytes) [last hour]
Indicates the maximum size of PDUs sent in
the last hour.
Sent PDU Total Size (bytes) [last hour]
Indicates the total size of PDUs sent in the
last hour.
Viewing detailed technical information
You can view detailed technical information about the collector that displays all
current tasks managed by the collector.
Procedure
1. 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 <calendar
definition>} (<priority>) (<state>)(<type>)
Where:
Item
Description
<Request ID>
The ID of the tasks in the Scheduler list of
tasks.
<calendar definition>
Definition (period optional calendar name)
and the time of the next start
Chapter 12. Viewing the list of collectors
185
Item
<priority>
Description
Valid values include the following:
v Realtime
v High
v Normal
The priority chosen here is linked to the
corresponding Scheduler priority queue. See
“Viewing scheduler information” on page
179 for details.
<state>
Valid values include the following:
v ASLEEP - indicates that the task is set for
the next execution and does not use any
resources.
v ACTIVE - indicates that the task is
currently running. This state appears and
disappears as the task processes SNMP
queries.
v ZOMBIE - indicates that the task is about
to disappear from view.
v READY - indicates that the task has
reached the time of the next start but is
waiting for an available thread to be
executed. The task has been place in a
waiting queue according to its current
priority value. As soon as the task is
handled by a thread, the state changes to
ACTIVE.
<type>
Name of the service for this task:
v ServiceSTAT - displays a list of the tasks
currently running.
v ServiceCRON - executes commands at
different preset times.
v ServiceFORM and ServiceGet - execute
SNMP queries
v Trgt indicates that the target host that is
being queried. A target can be one of the
following types:
element (Elmt)
sub-element (SubElmt)
group of elements (ElmtGrp)
group of sub-elements (SubElmtGrp)
v Form indicates the formula used for the
query.
v Inst lists the instances impacted during
the query process.
Note: Formulas (PVL-Tivoli Netcool Performance Manager-Statistics) are
available that monitor collector statistics.
186
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Stopping and restarting a local collector
You can stop the local collector from the Collector Information Tool window.
Procedure
Click Collector Information from the Monitor tab.
Select a collector from the list.
Click the Collector Information tab.
Click the Stop button in the Actions group, then confirm your choice at the
prompt.
5. Click Yes to confirm.
1.
2.
3.
4.
Note: To stop a remote collector, you need to connect to the system on which
the collector resides and launch the pvmdmgrscript with the stop option. For
example:
pvmdmgr stop
Restarting a local collector
You can restart the local collector from the Collector Information Tool window.
Procedure
1. 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 on
which the collector resides and launch the pvmdmgr script with the start option.
For example:
pvmdmgr start
Configuring watchdog for collector memory checking
The watchdog for Collector Memory Checking limits the amount of memory used
by a collector and restarts collectors that exceed a threshold limit.
Parameters
The Watchdog parameters reside in the registry.conf file located in the conf
directory 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"
Chapter 12. Viewing the list of collectors
187
Activation of memory checking
About 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 limits
There are two settings for controlling the memory size of a collector. All values are
in 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 on
your system and the number of processes running. For example, if your system
configuration is comprised of one collector with a remote database, you can set the
upper limit size to 75 percent of the total physical memory. This means that the
collector 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. This
limit is important, and should not be configured to a small value because during
the boot phase of a collector, the memory is increasing rapidly, and this increase
can confuse the Watchdog. Ideally, this limit should be set up to the normal
memory usage of a collector.
Procedure
1. To set up this value, start a Tivoli Netcool Performance Manager process, let it
run for one hour, modify theregistry.conf file
2. Get the process size using the ps command.
3. Restart the collector.
Setting inflation limit
Each time a collector reloads a new request, it calculates the amount of memory
needed to manage those requests, and each time the Watchdog is contacted, it
transmits 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 amount
of memory used is called real value.
If the value is greater than the value contained in the WorkingSetInflation= than
the nominal amount, then the Watchdog can restart a collector.
By default, this setting is set to 1000, which means 1000 percent (that is, the real
value greater than 10 times of the nominal value). If the minimal value is correctly
188
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
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 normal
operation.
This setting is only useful, if there are several processes on the system, and if a
collector has to share memory with Oracle. In this case, the inflation is preferred to
the upper limit. If only one collector is on the system by itself, the upper limit
should be used instead, and the inflation setting should remain at 1000.
Chapter 12. Viewing the list of collectors
189
190
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 13. Viewing status
The Tivoli Netcool Performance Manager DataMart Status tool displays which
modules are currently in use, their host system, and displays locked instances of
running modules.
The pvmstat command line interface (CLI) command launches the Status Tool from
the command line. For more information, see the IBM Tivoli Netcool Performance
Manager: Command Line Interface Guide.
Viewing DataMart status
Explains how to use the Tivoli Netcool Performance Manager DataMart Status tool
to view the status of individual modules.
Procedure
Click DataMart Status in the Applications tab. The Registered Modules group
displays 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 the
process is being run.
Display
Name of the graphical view from which
Tivoli Netcool Performance Manager
DataMart was launched.
Port
Port number of the software process. The
collector default port is 3002. 0 indicates that
no port number is used.
User
Name of a Tivoli Netcool Performance
Manager DataMart user running the
module.
Date
Date and time that the module was
launched.
Status
Indicates either a status or progress level.
Comment
Provides information on the module being
run.
The Locked Modules group displays the following information:
Item
Description
Lock
Name of the locked module.
Mode
Protection level that the lock provides.
0 = Read Only
1 = Read/Write
© Copyright IBM Corp. 2012
191
Item
Description
Locked by
Name of the application that has locked the
module (usually the module is locked by
itself).
Pid
Process identification number of UNIX.
Host
Name of the host system on which the
process 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 no
need 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 database
Tivoli Netcool Performance Manager DataMart locks a module when it is in use by
a user to prevent others from making any changes. A lock can be set on a running
module'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 instance
sets a lock in the database to indicate to the next instance that this it is already
running. The lock causes the next instance to run in "Read-Only" mode so that
critical operations (for example, changing resources in the database) are under the
control of the original instance.
If a module is abnormally terminated, and does not unregister or unlock itself
from the database, then the instance module is still displayed by the Tivoli Netcool
Performance 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
Procedure
1. 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.
192
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 14. Viewing database information
Explains how to view information on the Tivoli Netcool Performance Manager
DataMart database, instance, and status.
Before you begin
Before you view database information, ensure that libpvmextc.so is running.
Procedure
1. 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:
© Copyright IBM Corp. 2012
Item
Description
Database Server Name
Name of the server where the database is
installed.
Database Name
Name of the database. The database is the
data on disk (set of files), stored in operating
system files. Tivoli Netcool Performance
Manager DataMart uses only one database.
Current Database User
Current user connected to the database. For
example, "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-Time
Library. This library is responsible for
providing algorithms for
internationalization. The information
(NLSDATA) is read by the NLSRTL library
during run-time. For example, 3.4.1.0.0 Production.
193
Item
Total SGA
Description
System Global Area is the shared memory
area used by the instance to store
information shared between the database
and the user processes. The following values
are 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 that
holds copies of blocks of data read from
the Oracle datafiles on disk. For example,
125M.
v Redo Buffers - an area of memory within
the SGA that holds information about
recent changes to the database. For
example, 528K.
Last Refresh Date
Displays the date when the database was
last 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 the
database.
Viewing database free space status
The 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 functioning
properly. More than or equal to 30 percent
of free space is available.
WARNING (orange)
Indicates that database free space is
minimal. Less than or equal to 30 percent of
free space is available.
CRITICAL (red)
Indicates that you need to purge part of the
database. Less than or equal to 10 percent of
free space is available
DEADZONE (maroon)
Indicates that the database might not be
functioning properly. Less than or equal to 5
percent of free space is available.
Note: If a warning, critical, or deadzone status exists, the affected tab in the
ProvisoInfo 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, a
message is sent to Tivoli Netcool Performance Manager user via the notifyDBSpace
script (located in the bin directory of the DataMart installation path).
194
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Viewing database parameters
Procedure
1. 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 useful
for working with Oracle technical support or IBM in troubleshooting issues. For
example, you can verify that a parameter changes or if the init.ora file was
modified.
Viewing database statistics
Procedure
1. 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 displays
the information in progression bars. For example, the information above
indicates that the disk space for the SQL Area is 75 percent full.
Viewing the Tivoli Netcool Performance Manager version information
Procedure
Click the Proviso Version folder to display version information. This information
lets you quickly identify the versions of Tivoli Netcool Performance Manager
components in your environment and is useful for working with Oracle technical
support or IBM in troubleshooting issues.
Viewing MetaData
The MetaData tab displays information about Tivoli Netcool Performance Manager
configuration elements, metrics, and properties. Metadata represents data such as
tablespace and table information, and is grouped by topic (for example,
configuration, temporary tablespaces, system tablespaces, etc.). Tivoli Netcool
Performance Manager describes each resource, collection and aggregation
schedules, and MIBs.
About this task
To view Metadata information, follow these steps:
Procedure
1. 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.
10.
11.
12.
13.
14.
15.
16.
17.
Click the SYSTEM item to display spacing information.
Expand the SYSTEM item to view only the total space used (in megabytes).
Expand the Meta Tables item.
Expand the Formulas item.
Click the FRML_DESC item in the Formulas tree. This information lets you
quickly view table structures and provides a short description of the purpose
of each column (if available).
Click the FRML_DESC_HIST item.
Click the FRML_GRP_DESC item.
Click the FRML_GRP_MEMBER item.
Click the FRML_GRP_PATH.
18. Click the FRML_MIB.
19. Click the FMRL_MIB_HIST.
20.
21.
22.
23.
24.
Click
Click
Click
Click
Click
the
the
the
the
the
Resources item to expand the branch.
Grouping - Inventory item to expand the branch.
Properties - Thresholds item to expand the branch.
Dataview item to expand the branch.
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 MetricData
The 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 for
tables paces in current history (raw data). In the example above, the thresholds are
in the critical stage, alerting you to potential problems.
Procedure
1. 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 is
being used by the Complex Metric Engine. The aggregation set’s tables and
views show a status of “OK.”
3.
4.
5.
6.
7.
Click
Click
Click
Click
Click
a GMT value in the tree to view the aggregation set status for that GMT.
a channel item to get additional partition information.
the Channels tab to display channel information.
the Working item to expand the branch.
an item to display file names.
8. Click a file name.
9. Click the Historic item to expand the branch.
196
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
10. Click a historic item. The number of rows, high date, and tablespace used is
displayed 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 collectors
installed 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 Performance
Manager 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 the
example above, the thresholds are in the critical stage, alerting you to
potential 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 information
Explains how to view Oracle client status information on the Tivoli Netcool
Performance Manager Database, DataMart, DataLoad, DataChannel, and DataView.
About this task
To view client information, follow these steps:
Procedure
1. 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 is
connected by PV_ADMIN.
Viewing database status
Explains 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:
Chapter 14. Viewing database information
197
If the status of the database is in the Warning, Critical, or Deadzone state, the
following information is displayed:
Note: In the example above, only 7 percent of overall free space remains available,
and the database is 90 percent full.
198
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Viewing disk information
Procedure
Click the Disk tab.
Click the / (forward slash) to display the amount of free disk space.
Click var to display the amount of free disk space.
Expand /export/home to expand the branch and view mount point disk space
information.
5. Click an item. The following information is displayed:
1.
2.
3.
4.
Chapter 14. Viewing database information
199
200
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Chapter 15. Exporting or Importing Metadata
Discusses the following topics:
Exporting data
Explains how to export data between two Tivoli Netcool Performance Manager
DataMart systems. You can save metadata to files so they can be shared with other
users in different locations. An export operation creates a set of files in a specified
destination directory.
Procedure
1. Click Import-Export Configuration in the Configuration tab. The EXPORT
operation is enabled by default. An export operation can be used even if the
module 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 export
procedure can generate numerous files, it might be helpful for you to create a
directory 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 directory
path.
3. Select a profile to export from the Type of Data list. These commands are
configured in the impexp.conf file, with each data type having import and
export profile parameters specified in the configuration file. The following data
types are available:
© Copyright IBM Corp. 2012
201
Option
Description
Operation Profile(s)
formulas
Export of metrics used for
collections.
v exportFormulas (default) Exports all formulas (listed
below) from the database.
v exportCustomFormulas Exports all custom
formulas (formulas a user
creates manually; not
formulas in Tivoli Netcool
Performance Manager
Technology Packs) from
the database. The custom
data indices* are greater
than 100000000.
v exportPsFormulas Exports all formulas
created by IBM
Professional Services.
v exportPvlFormulas Exports formulas created
by Tivoli Netcool
Performance Manager
Application. The indexes
for these formulas is less
than 50000000.
*where indexes = database
IDs.
calendars
Export period of collection
configurations (no link with
timezones).
v exportCalendars (default) Exports all calendars. This
profile includes the
profiles below.
v exportCustomCalendars Exports all calendars
created by the users. The
custom data indexes are
greater than 100000000.
v exportPsCalendars Exports all calendars
created by IBM
Professional Services.
v exportPvlCalendars Exports all calendars
created by Technology
Packs. Indexes are less
than 50000000.
202
users
Export of users and user
permissions.
v exportUsers - Exports all
users.
timezones
Export of aggregation sets
configuration.
v exportTimeZones - Exports
aggregation set
descriptions.
elements
Export of elements
configuration.
v exportElements (default) Exports all elements and
groups..
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Option
Description
Operation Profile(s)
subelements
Export of subelements
configuration.
v exportSubElements
(default) - Exports all
subelements.
v
exportSubElements_Skeleton
- Exports subelement
groups.
v
exportLinks_subEltGroups/
aggregationSets - Exports
the links between
subelement groups and
aggregations sets.
dashboards
Export of dashboards.
v exportDashboards Exports all dashboards,
resources
Export of subelements and
elements.
v exportResources Combines exportElements
and exportSubElements
profiles.
requests
Export of data requests.
v exportRequests - Exports
all data collection requests.
thresholds
Export of thresholds.
v exportThresholds - Exports
all thresholds.
inventory_profiles
Export of inventory profiles.
v exportInventoryProfiles Exports all inventory
profiles.
reports
Export of reports.
v exportReports - Exports all
reports.
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 - Exports
all data types. Exports all
data that can be exported
using this module. This
profile is a combination of
all the export profiles of
all 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 DataMart
modules 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 is
reserved
Chapter 15. Exporting or Importing Metadata
203
v The records whose indexes are included in that range comes from
Technology 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 more
export profile types are available.
5. Click Run to start the export procedure. A progress bar indicates the status of
the export procedure. The message bar at the bottom of the box displays the
number of items processed, and errors and warnings (if any). Click Details to
display more information about the export procedure.
6. When the operation ends, click Close to exit the message box. Export files are
generated in the target directory.
Export files
The datatypes.res file is used for an import procedure, as it contains a list of all
data types that are exported for the profile.
Do not rename or delete export files, or change their content. To exchange export
data between systems, either move, copy, or rename the entire directory
Option
Profile(s)
Export File(s) Generated
formulas
exportFormulas
custom_formula.dat
custom_mib.dat
pvl_formula.dat
pvl_mib.dat
ps_formula.dat
ps_mib.dat
exportCustomFormulas
custom_formula.dat
custom_mib.dat
exportPsFormulas
ps_formula.dat
ps_mib.dat
exportPvlFormulas
pvl_formula.dat
pvl_mib.dat
calendars
204
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Option
Profile(s)
Export File(s) Generated
exportCalendars
customCalGlob.dat
customCalPlan.dat
pvlCalGlob.dat
pvlCalPlan.dat
psCalGlob.dat
psCalPlan.dat
exportPsCalendars
psCalGlob.dat
psCalPlan.dat
exportCustomCalendars
customCalGlob.dat
customCalPlan.dat
exportPvlCalendars
pvlCalGlob.dat
pvlCalPlan.dat
users
exportusers
usersDesc.dat
usersGrgpLink.dat
usersGroups.dat
usersRights.dat
timezones
exportTimeZones
timeZones.dat
elements
exportElements
eGroupsDesc.dat
elements.dat
snmpElementItems.dat
ega.dat
elementsLinks.dat
egu.dat
eltProperties.dat
exportElements_Skeleton
eGroupsDesc.dat
ega.dat
egu.dat
subelements
Chapter 15. Exporting or Importing Metadata
205
Option
Profile(s)
exportSubElements
Export File(s) Generated
seGroupsDesc.dat
subelementLinks.dat
sega.dat
subelementgroupsCal.dat
segrpToTz.dat
subelementgroupsPlans.dat
segu.dat
subelementsProperties.dat
subElements.dat
exportSubElements_Skeleton
seGroupsDesc.dat
segu.dat sega.dat
subelementgroupsCal.dat
segrpToTz.dat
subelementgroupsPlans.dat
exportLinks_subEltGroups/
aggregationSets
dashboards
exportDashboards
segrpToTz.dat
dbdDesc.dat
dbdText.dat
dbdThresholds.dat
dbdViews.dat
206
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Option
Profile(s)
Export File(s) Generated
resources
exportResources
eGroupsDesc.dat
segrpToTz.dat ega.dat
segu.dat egu.dat
snmpElementItems.dat
elements.dat
subElements.dat
elementsLinks.dat
subelementLinks.dat
eltProperties.dat
subelementgroupsCal.dat
seGroupsDesc.dat
subelementgroupsPlans.dat
sega.dat
subelementsProperties.dat
requests
exportRequests
seRequests.dat
segpRequests.dat
thresholds
exportThresholds
thresholds.dat
inventory_profiles
exportInventoryProfiles
optinventory.dat
reports
exportReports
linkReport.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
Chapter 15. Exporting or Importing Metadata
207
Option
Profile(s)
core_configuration
exportCoreConfiguration
Export File(s) Generated
LinkReport.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
web_user_properties.dat
Requests.dat
propertiesSE.dat Rules.dat
se_with_seprp.dat
208
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Option
Profile(s)
Export File(s) Generated
all
exportAllConfig
customCalGlob.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
snmpElementItems.dat
egu.dat
subElements.dat
elements.dat
subelementLinks.dat
elementsLinks.dat
subelementgroupsCal.dat
eltProperties.dat
subelementgroupsPlans.dat
Chapter 15. Exporting or Importing Metadata
209
Option
Profile(s)
Export File(s) Generated
exportAllConfig (continued)
linkReport.dat
subelementsProperties.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.dat
report.dat
web_user_properties.dat
Importing data
Explains how to import data between two Tivoli Netcool Performance Manager
DataMart systems. You can save metadata to files so they can be shared with other
users in different locations. Do not rename or delete export files, or change their
content. To exchange export data between systems, either move, copy, or rename
the entire directory
Procedure
1.
2.
3.
4.
210
Click Import-Export Configuration in the Configuration tab.
Click the Import option.
Click Browse to go to the target directory where the files are stored.
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 and
export profile parameters specified in the configuration file. The following data
types are available:
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Option
Description
Operation Profile(s)
formulas
Import of metrics used for
collections.
v importFormulas (default) Imports all formulas
(listed below) from the
database.
v importCustomFormulas Imports all custom
formulas (formulas a user
creates manually; not
formulas in Tivoli Netcool
Performance Manager
Technology Packs) from
the database. The custom
data indexes* are greater
than 100000000.
v importPsFormulas Imports all formulas
created by Tivoli Netcool
Performance Manager
Professional Services.
v importPvlFormulas Imports formulas created
by Tivoli Netcool
Performance Manager
Application. The indexes
for these formulas is less
than 50000000.
*where indices = database
IDs.
calendars
Import period of collection
configurations (no link with
timezones).
v importCalendars (default)
- Imports all calendars.
This profile includes the
profiles below.
v importCustomCalendars Imports all calendars
created by the users. The
custom data indexes are
greater than 100000000.
v importPsCalendars Imports all calendars
created by IBM
Professional Services.
v importPvlCalendars Imports all calendars
created by Technology
Packs. Indexes are less
than 50000000.
users
Import of users and user
permissions.
v importUsers - Imports all
users.
elements
Import of elements
configuration.
v importElements (default) Exports all elements and
groups.
Chapter 15. Exporting or Importing Metadata
211
Option
Description
Operation Profile(s)
subelements
Import of subelements
configuration.
v importSubElements
(default) - Exports all
subelements.
v
importSubElements_Skeleton
- Exports subelement
groups.
v
importLinks_subEltGroups/
aggregationSets - Exports
the links between
subelement groups and
aggregations sets.
dashboards
Import of dashboards.
v importDashboards Exports all dashboards,
resources
Import of subelements and
elements.
v importResources Combines exportElements
and exportSubElements
profiles.
requests
Import of data requests.
v importRequests - Exports
all data collection requests.
thresholds
Import of thresholds.
v importThresholds Imports all thresholds.
inventory_profiles
Import of inventory profiles.
v importInventoryProfiles Imports all inventory
profiles.
reports
Import of reports.
v importReports - Imports
all reports.
snmp_parameters
Import of SNMP parameters. v importSnmpElements Imports SNMP
parameters.
core_configuration
Import of core configuration. v importCoreConfiguration Imports core configuration
all
Import all of the data types.
v importAllConfig - Exports
all data types. Exports all
data that can be exported
using this module. This
profile is a combination of
all the export profiles of
all 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 more
import profile types are available.
6. Click Run to start the import procedure. A progress bar indicates the status of
the import procedure. The message bar at the bottom of the box displays the
number of items processed, and errors and warnings (if any). Click Details to
display more information about the import procedure.
212
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
7. When the operation ends, click Close to exit the message box. After an import
procedure is completed, a collector reload is performed and the collector is
refreshed with the configuration changes.
8. Click Close to exit the message box. After an import procedure is completed, a
collector reload is performed and the collector is refreshed with the
configuration changes.
Note: While the format of the files generated is a resource manager (resmgr)
format, individual files generated using Resource Manager cannot be imported
using the importExport tool.
Chapter 15. Exporting or Importing Metadata
213
214
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Glossary
ANS.1 Abstract Syntax Notation One is OSI
language for describing data types
independent of particular computer
structures and representation techniques.
ARP
The Address Resolution Protocol is used
to bind an IP address to a MAC address.
ATM
Asynchronous Transfer Mode
availability
The percentage of time during a given
interval that a network object or interface
is available to perform its function.
Availability is measured by a poller. The
poller tracks how long an element or
sub-element is unavailable and the
percentage of time that it is available.
Tivoli Netcool Performance Manager
DataMart lets you monitor end-to-end
network availability.
bandwidth
A measure of the capacity of a
communications link.
bps
Bit per Second is a measurement that
expresses the speed at which data is
transferred between computers.
bridge A device that connects one physical
section of a network to another, often
providing isolation.
broadcast
A packet destined for all hosts on a
network.
burst rate
A circuit data transmission rate above the
Committed Information Rate (CIR) that
can be used to increase data throughput if
it is available.
collector
The collector stores data for monitoring
elements and sub-elements on your
network. Tivoli Netcool Performance
Manager DataMart enables the collection,
consolidation, storage and archiving of
critical network performance and service
analysis data. This data can be integrated
into Tivoli Netcool Performance Manager
DataView or the reporting tool of your
choice.
© Copyright IBM Corp. 2012
Committed Information Rate (CIR)
The specified amount of guaranteed
bandwidth (measured in bits per second)
on a Frame Relay service. Typically, when
purchasing a Frame Relay service, a
company can specify the CIR level they
want. The Frame Relay network vendor
guarantees that frames not exceeding this
level will be delivered. It is possible that
additional traffic might also be delivered,
but it is not guaranteed. See also burst
rate.
daemon
A process that executes a program
automatically in background mode when
the system is initially started.
Dashboard
A real-time graphic display of one or
more formulas or MIB objects on one or
more hosts.
Data Link Connection Identifier (DLCI)
Frame relay allows users to segment
physical ports into multiple logical
interfaces. Each of these logical interfaces
is identified by its DLCI.
default
An operation or value that the system or
application assumes unless you make an
explicit choice.
delay (also known as latency)
A measurement from one end of a
network or device to another. Higher
latency indicates longer delays.
discovery
Lets you analyze your network and
gather information about TCP/IP network
elements and sub-elements and how they
are interconnected.
Domain Name Service (DNS)
The system that translates between
internet IP addresses and internet host
names.
Dynamic Host Configuration Protocol (DHCP)
A protocol that provides dynamic IP
address allocation and automatic IP
configuration.
215
element
An addressable, managed node or host.
exception
An exception is an event that is not
considered normal and requires your
immediate attention. For example, router
outages or network response time failures.
formula
A set of mathematical instructions and
SNMP queries.
frame relay
A packet-oriented communication method
for connecting computer systems on
WANs. Frame Relay is
digital-data-communications protocol
provided by a carrier. Connections into a
frame relay network require a router and
a line from the customer site to a carrier's
frame relay port entry.
group Customized, virtual association that
contains one or more network elements.
hop
hub
A hop represents a transmission of a data
packet through a router in a network of
interconnected segments or subnetworks.
In many networks, there are many routers
connecting many segments, thus forming
a number of paths that a packet can travel
to get to its destination. A measure of this
path is the hop count, or the number of
routers the packet must pass through to
get to its destination.
A common connection point for devices
in a network. Hubs are commonly used to
connect segments of a LAN. A hub
contains multiple ports. When a packet
arrives at one port, it is copied to the
other ports so that all segments of the
LAN can see all packets.
HyperText Markup Language (HTML)
Used for developing Web documents.
HyperText Transfer Protocol (HTTP)
A protocol that allows Web clients to
retrieve information from Web servers.
Internet Control Message Protocol (ICMP)
Used to handle error and control
messages sent when datagrams are
discarded or systems are congested. Part
of the IP protocol.
interface
The network connection between two
systems or devices.
216
Internet
A collection of autonomous systems
interconnected by bridges, routers, or
gateways.
Inventory profile
Lets you define your network inventory.
You can create different profiles for
different resources in your network.
Inventory Tool
Provides you with a report of network
elements and sub-elements on your
network.
IP
Internet Protocol is a communications
protocol that allows computers of any
make to communicate when running IP
software.
IP address
An identifier for a computer or device on
an IP network. Networks using the IP
protocol route messages based on the IP
address of the destination. The format of
an IP address is a 32-bit numeric address
written as four numbers separated by
periods. Each number can be zero to 255.
For example, 1.160.10.240.
KB
Kilobyte is a data unit of 1,024 bytes.
latency
Measures the time it takes for a packet to
travel from one point to another point
and back.
Local Area Network (LAN)
A computer network that is limited to a
small geographic area. For example, an
office building.
MAC
The Media Access Control protocol
governs the method by which a station
can access a network.
Management Information Base (MIB)
A data repository used by an SNMP agent
to store management data about a
managed object. All MIB information is
defined in ASN.1 format. MIB variables
are organized in groups such as system
and interfaces. An SNMP agent manages
only the part of the MIB that the MIB
references.
Meta-Data
Control information about the collected
data. Tivoli Netcool Performance Manager
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
uses meta data to describe resources,
collection and aggregation schedules, and
MIBs.
users access to a variety of multiple
desktop databases and file formats.
OSI
Metric The result of a formula applied to
resources. These results are displayed in
the reports viewed through a Web
browser.
The Open Systems Interconnection model
is a layered architecture plan that
standardizes levels of service and type of
interaction for computers exchanging
information through a network.)
Metric-Data
Data collected on resources that is
(optionally) transformed by formulas,
imported, or summarized by an
aggregation policy.
packet Also known as a frame, single unit of
data transmitted over a packet-switching
network. A packet contains source and
destination address in addition to the
data.
millisecond
One thousandth of a second.
peak
network
A system of computers, hardware, and
software that is connected over which
data, files, and messages can be
transmitted and end users communicate.
Networks can be local or wide area.
Network users can share the same data
and application files, send messages
between individual workstations, and
protect files with an extensive security
system.
Permanent Virtual Circuits (PVC)
A pathway through a packet-switched or
cell-switched network.
network administrator
The person who installs, configures, and
deploys Tivoli Netcool Performance
Manager on an enterprise network. This
includes creating and managing users
profiles and assigning rights and
privileges.
network monitoring system
An integrated set of software that
measures and analyzes
communications-related parameters in a
network.
PID
The highest level or greatest degree as
represented in graphical reports.
Protocol Identifier.
PING (Packet INternet Groper) a utility to
determine whether a specific IP address is
accessible. A source IP device sends a
packet to a destination address and waits
for a reply.
port
A physical connection on a network
device.
probe A packet sent to the remote end of a
network. The probe requests an
acknowledgment from end nodes.
profile
See Inventory profile.
NIS
Network Information Service is a protocol
for administering network-wide
databases.
Properties
Any attribute or characteristic that defines
a resource more precisely and provides
additional information on it. Properties
can be customer attributes and technical
attributes including:
v Customer name for which the resource is
deployed
v VPN
v IP address
v Interface name
node
The endpoint of a network connection or
a junction common to two or more lines
in a network. Nodes can be processors,
controllers, or workstations.
v
v
v
v
NOC
Network Operations Center
network traffic
The data that flows on a communications
device or system.
Open Database Connectivity (ODBC)
ODBC is a specification designed to give
Site
Class of service (Silver, Gold, Platinum)
Geographical properties (city, building, floor)
Customer properties (division, business
department, branch office)
v Service properties (applications)
Glossary
217
v SLA value (thresholds, burst threshold,
availability threshold, CIR, and SLA contract
type)
protocol
A standard set of rules by which network
elements trade information to
communicate including the format,
timing, sequencing, or error checking.
Quality of Service (QOS)
A guaranteed throughput level from the
provider to its customers.
Read-Only mode
Provides only viewing access to Tivoli
Netcool Performance Manager DataMart
modules. You cannot make modifications
to any module in "read-only" mode. The
Read-Only icon is as follows:
repeater
A device that lets you extend the length
of your network by amplifying and
repeating the information it receives.
resource
A type of physical or logical object
managed by the Tivoli Netcool
Performance Manager system. Any
managed physical interface or port is a
resource, any managed logical circuit is
also resource. For example, a Frame Relay
DLCI, an ATM PVC, and a CE-CE
itinerary (VPN Customer Edge). Any
object from which Tivoli Netcool
Performance Manager can get
identification (a name and a label) and
related metrics can be modeled in the
DataMart, using the resource concept.
rights User privileges assigned by the network
administrator for access to Tivoli Netcool
Performance Manager.
report A formatted and organized presentation
of data.
response time
The amount of time that takes one
endpoint to respond to a request from
another endpoint on a network.
router The equipment that receives an internet
packet and sends it to the next machine in
the destination path.
218
segment
A protocol data unit consisting of part of
a stream of bytes being sent between two
machines.
server A computer that runs services. Also refers
to a piece of hardware or software that
provides access to information requested
from it.
Service Level Agreement (SLA)
is a contractual guarantee that stipulates
the specified minimum level of network
capacity and service support that a
customer will receive. An SLA establishes
realistic expectations for consistent service
delivery and articulates compensatory
measure in the case of service delivery
failure.
You can develop an aggressive SLA, both
internally and externally, that delivers
priority, availability, and bandwidth
required by business applications.
Service Level Management (SLM)
provides the measurement and evaluation
of network performance against business
metrics. A comprehensive flexible SLM
plan that monitors performance
effectively can result in increased user
satisfaction.
Simple Network Management Protocol (SNMP)
A communications protocol used to
control and monitor devices on a
network. An SNMP agent manages parts
of a MIB.
SMI
Structure of Management Information
(RFC 1155) specifies rules used to define
managed objects in a MIB. See also MIB.
SNMP Availability
is the percentage of time during a given
interval that a network object or interface
is available to perform its function.
Availability is measured by a poller. The
poller tracks how long an element or
sub-element is unavailable and the
percentage of time that it is available.
Tivoli Netcool Performance Manager
DataMart helps you increase end-to-end
network availability.
SNMP Response Time
is the amount of time that takes one
endpoint to respond to a request from
another endpoint on a network. Tivoli
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Netcool Performance Manager DataMart
helps you improve response time.
SNMP trap
An SNMP trap lets you forward one or
more exceptions for a network object to a
designated computer on your network.
The destination computer needs to have a
third-party packet capturing software
program installed. You use this program
to view the exception message.
SNMP Utilization
is the percentage of bandwidth that an
element or sub-element is in use during a
given period of time. For example, 30% to
40% signifies a low utilization and 80 to
90% signifies a high utilization.
Sub-Element
A sub-component of an element, such as a
port, interface, virtual circuits, user, or a
DLCI.
subnet
A portion of a network that shares a
common address component. On IP
networks, subnets are defined as all
devices whose IP addresses have the
same prefix. For example, all devices with
IP addresses that start with 100.100.100.
would be part of the same subnet. IP
networks are divided using a subnet
mask.
subnet mask
A 32-bit value that distinguishes the
network ID from the host ID of an IP
address.
switch A device that filters and forwards packets
between LAN or WAN segments.
Switches operate at the data link layer
(layer 2) of the OSI Reference Model and
therefore support any packet protocol.
LANs that use switches to join segments
are called switched LANs or, in the case
of Ethernet networks, switched Ethernet
LANs.
traceroute
A utility that traces a packet from source
IP to destination IP address, showing how
many hops the packet requires to reach
the host and how long each hop takes.
traffic See network traffic.
TCP
Transmission Control Protocol is a layer 4
protocol that provides a level of
connection-oriented reliability to an IP
network.
URL
Uniform Resource Locator is the
addressing system used in the Web that
can reference any type of file on the
Internet, enabling a Web client to access
that file.
utilization
The percentage of time that a network
object or interface is in use for a given
period of time.
VLAN A virtual LAN is a group of devices on
one or more LANs that are configured so
that they can communicate as if they were
attached to the same wire, when if fact,
they are located on a number of different
LAN segments.
volume
The number of bits that flowed through a
network interface over a period of time.
Web browser
A software program that lets you view
and access HTML documents. For
example, Internet Explorer and Netscape
Navigator.
Wide Area Network (WAN)
A network of geographically dispersed
computers.
Write mode
Provides you with full access to Tivoli
Netcool Performance Manager DataMart
modules. You can make modification to
any module in "write" mode. The write
mode icon is as follows:
target The object to which a formula applies
threshold
A value that is compared against metrics
to determine if the metrics exceed or drop
below a critical limit.
Glossary
219
220
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement 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 be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
© Copyright IBM Corp. 2012
221
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM for the purposes of developing, using, marketing, or distributing application
programs conforming to IBM‘s application programming interfaces.
222
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
If you are viewing this information in softcopy form, the photographs and color
illustrations might not be displayed.
Notices
223
224
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at http://www.ibm.com/legal/copytrade.shtml.
Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
other countries, or both.
Cell Broadband Engine and Cell/B.E. are trademarks of Sony Computer
Entertainment, Inc., in the United States, other countries, or both and is used under
license therefrom.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.
IT Infrastructure Library is a registered trademark of the Central Computer and
Telecommunications Agency which is now part of the Office of Government
Commerce.
ITIL is a registered trademark, and a registered community trademark of the Office
of Government Commerce, and is registered in the U.S. Patent and Trademark
Office.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks 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, or
both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, and service names may be trademarks or service marks
of others.
For trademark attribution, visit the IBM Terms of Use Web site:
http://www.ibm.com/legal/us/.
© Copyright IBM Corp. 2012
225
226
IBM Tivoli Netcool Performance Manager: DataMart Configuration and Operation Guide
Printed in USA