tivoli ibm wireline component - inpm · the audience for this guide is the tivoli netcool perf...

IBMNetcool Performance Manager 1.3.1Tivoli
Wireline Component
Document Revision R2E1

DataMart Operation Guide

Note

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

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

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

The Tivoli Netcool Performance Manager Product Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tivoli Netcool Performance Manager Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1: Editing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Filtering Elements and Sub-Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Viewing Resource Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Viewing Sub-Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Exporting Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Importing Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Adding Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Modifying Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Deleting Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Deploying Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 2: Viewing Collected Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Viewing Graphical Charts for Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Viewing Graphical Charts for Sub-Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Viewing Graphical Charts for Sub-Element Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Saving a Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Printing a Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Configuring Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 3: Viewing Collector Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Viewing the List of Collectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Viewing Collector Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Viewing Scheduler Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Viewing Data Manager Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Viewing Target Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

IBM Tivoli Netcool Performanc Manager: DataMart Operation Guide v

Contents

Viewing Detailed Technical Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Stopping and Restarting a Local Collector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuring Watchdog for Collector Memory Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 4: Viewing Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Viewing Tivoli Netcool Performance Manager DataMart Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Removing a Lock from the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 5: Viewing Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Viewing Database Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Viewing MetaData. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Viewing MetricData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Viewing Client Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Viewing Database Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Viewing Disk Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 6: Exporting or Importing Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Exporting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Importing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

vi IBM Tivoli Netcool Performanc Manager: DataMart Operation Guide

Preface

IBM Tivoli Netcool Performance Manager consists of two main components. A wireline component (formerly Tivoli Netcool/Proviso), and a wireless component (formerly Tivoli Netcool Performance Manager for Wireless).

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

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.

Organization

This guide is organized as follows:

• Chapter 1, Editing Resources

Explains how to edit resources using the DataMart GUI.

• Chapter 2, Viewing Collected Data

Explains how to view the data that is collected.

• Chapter 3, Viewing Collector Information

Explains how to view various types of information about collectors.

• Chapter 4, Viewing Status

Explains how to check the status of various Tivoli Netcool Performance Manager utilities and operations.

• Chapter 5, Viewing Database Information

Explains how to view information about the database.

• Chapter 6, Exporting or Importing Metadata

Explains how to import and export data from Tivoli Netcool Performance Manager.

The Tivoli Netcool Performance Manager Product Suite

Tivoli Netcool Performance Manager is made up of the following components:

• Tivoli Netcool Performance Manager DataMart is a set of management, configuration and troubleshooting GUIs that the Tivoli Netcool Performance Manager System Administrator uses to define policies and configuration, as well as verify and troubleshoot operations.

• Tivoli Netcool Performance Manager DataLoad provides flexible, distributed data collection and data import of SNMP and non-SNMP data to a centralized database.

IBM Tivoli Netcool Performanc Manager: DataMart Operation Guide vii

Preface

• Tivoli Netcool Performance Manager 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 on-line calculations and detects real-time threshold violations.

• Tivoli Netcool Performance Manager DataView is a reliable application server for on-demand, web-based network reports.

• Tivoli Netcool Performance Manager 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.

Figure 1: Tivoli Netcool Performance Manager Modules

Tivoli Netcool Performance Manager Documentation

Tivoli Netcool Performance Manager documentation consists of the following:

• release notes

• configuration recommendations

• user guides

• technical notes

• online help

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

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

viii IBM Tivoli Netcool Performanc Manager: DataMart Operation Guide

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

Chapter 1: Editing Resources

This chapter discusses the following topics:

Overview

This chapter explains how to use the Resource Editor to do the following:

• View resource information

• Export resources

• Import resources

• Add resources

• Delete resources

• Deploy reports

Note: For information about managing resources from the command line, see the IBM Tivoli Netcool Performance Manager: Command Line Interface Guide.

Topic Page

Filtering Elements and Sub-Elements 2

Viewing Resource Information 3

Exporting Resources 7

Importing Resources 8

Adding Resources 9

Modifying Resources 21

Deleting Resources 28

Deploying Reports 30

IBM Tivoli Netcool Performanc Manager: DataMart Operation Guide 1


Filtering Elements and Sub-Elements

Display specific subsets of information by filtering the elements, sub-elements and composite sub-elements in your network.

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.

To filter elements and sub-elements, follow these steps:

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:

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.

2 IBM Tivoli Netcool Performanc Manager: DataMart Operation Guide


Viewing Resource Information

This section explains how to view information about elements, sub-elements, sub-element groups, and element and sub-element properties.


Viewing Elements

To view elements, follow these steps:

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 Description

Name Displays the name of the element.

Profile Displays the name of the inventory profile used to discover this element. For more information, see the IBM Tivoli Netcool Performance Manager: Installation Guide .

Collector Displays the collector number assigned to this element.

Description Displays a descriptive textual name for the element.

Type 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 Displays the method used to add the element to the database.

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



Viewing Sub-Elements

To view sub-elements, follow these steps:

1. Click the Sub-Element tab in the Resource Editor.

2. Click Apply Filter to view all sub-elements or composite sub-elements in the database, or enter filter information to limit the number of results. The following information is displayed:

Viewing Sub-Element Groups

To view sub-element groups, follow these steps:

1. Click the Sub-Element Group tab in the Resource Editor.

2. Click a sub-element or composite sub-element group folder to expand it.

3. Select a sub-element or composite sub-element group name to display the elements it contains in the right pane. The following information is displayed:


Name Displays the name of the sub-element or composite sub-element .

Date Displays the date for the sub-element or composite sub-element.

Label Displays a descriptive comment for the sub-element or composite sub-element.

Profile Displays the name of the inventory profile used to discover the sub-element or composite sub-element. For more information, see the IBM Tivoli Netcool Performance Manager: Installation Guide.

Family Displays the name of the family for the sub-element or composite sub-element.

Element Displays the name of the element for the sub-element or composite sub-element.

Instance Displays the name of the instance for the sub-element or composite sub-element.


Name Displays the name of the sub-element or composite sub-element.

Label Displays a descriptive comment for the sub-element or composite sub-element.


Element Displays the name of the element for the sub-element or composite sub-element.



Viewing Property Details

To view property details, follow these steps:

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, sub-element, or composite sub-element by scrolling through the list, or click the magnifying glass icon to open the Find dialog box.

4. Highlight the element, sub-element, or composite sub-element 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 sub-element or composite sub-element.

• Relation To - The source sub-elements or composite sub-elements to which the selected composite sub-element is linked. The Relation To tab contains:

* Relation - The relationship between the selected composite sub-element and each of the source sub-elements or composite sub-elements. A relation can be any string.

* Resource - The source sub-element or composite sub-element.

• Relation From - The destination sub-elements or composite sub-elements for the selected composite sub-element and the relationship between them. The Relation From tab contains:

* Relation - The relationship between the selected composite sub-element and each of the destination sub-elements or composite sub-elements. A relation can be any string.

* Resource - The destination sub-element or composite sub-element.

Instance Displays the name of the instance for the sub-element or composite sub-element.

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 sub-elements.

Name The name of the group member.

Label The label of the group member.




Viewing Reports

To view reports, follow these steps:

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:

Viewing Thresholds

To view thresholds, follow these steps:

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:


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.


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



Exporting Resources

This section explains how to export resources for use with another Tivoli Netcool Performance Manager DataMart installation. You can export elements, sub-elements, composite sub-elements, and sub-element groups.


Exporting Resources

To export resources, follow these steps:

1. Click the Element, Sub-Element, or Sub-Element Group tab in the Resource Editor.


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 the Folder button to specify the destination location for the export files.

5. Enter a name for the export file in the File name text box. The filename extension is .elt for elements, .se for sub-elements, and .segp for sub-element groups.

6. Click Save to export the file. A message box displays when the export process completes.

7. Click Close.

BEvent Burst Event Generation

PCrtL Period Critical Level

PCrtT Period Critical Time

PWrnL Period Warning Level

PWnrT Period Time

PEvent Period Event Generation

PDef Period Definition

MaxNbDay Baseline Threshold Maximum Number 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




Importing Resources

This section explains how to import elements, sub-elements, composite sub-elements, and sub-element groups. The filename extensions differ depending on the resource you are importing.


Importing Resources

To import elements or sub-elements, follow these steps:

1. Click the Element tab or the Sub-Element tab.

2. Click Apply Filter to view all elements or sub-elements 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 the Folder button to specify the source location for the import files. The filename extension is .elt for elements, .se for sub-elements, and .segp for sub-element groups.

5. Click Open to import the file. Click the Details button to view a detailed status on the import procedure. A message box opens when the import process completes.

6. Click Close.



Adding Resources

This section explains how to add elements, sub-elements, reports, and thresholds.


Adding Elements

To add elements, follow these steps:

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 popup menu. The Add Element dialog box opens.

5. Enter the following information for the new element:

6. Click OK to accept your changes.

7. Click Close to exit the message box.

Adding Sub-Elements

To add sub-elements or composite sub-elements, follow these steps:

1. Click the Sub-Element tab.

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:





Comment Specifies descriptive comments about the element.



2. Click Apply Filter to view all sub-elements and composite sub-elements in the database, or enter filter information to limit the number of results.

3. Click a sub-element or composite sub-element name.

4. Select Add from the Edit menu or right-click the element name and select Add from the popup menu. The Add Sub-Element dialog box opens.

5. Enter the following information for the new sub-element:



Adding Composite Sub-Element Relations

To add composite sub-element relationships, follow these steps:


2. Click Apply Filter to view all sub-elements in the database, or enter filter information to limit the number of results.

3. Click a composite sub-element name.

4. Click Detail to display the list of properties associated with the selected composite sub-element.

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 popup menu. The Add Sub-Element dialog box opens.

7. Enter the following information for the new sub-element or composite sub-element:

Field Description

Name Specifies the name of the sub-element or composite sub-element.

Label Specifies a descriptive comment for the sub-element or composite sub-element.

Family Select the name of the family for the sub-element or composite sub-element.

Element Specifies the name of the element for the sub-element or composite sub-element.

Instance Specifies the name of the instance for the sub-element or composite sub-element.

Invariant Specifies the invariant entity associated with the sub-element or composite sub-element.

Field Description

Relation Specifies the name of the sub-element or composite sub-element relation.






Adding Reports

To add reports, follow these steps:

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 popup menu. The Add Report dialog box opens.

5. Enter the following information for the new report:







Family Select the name of the family for the sub-element or composite sub-element.

Field Description

Field Description

Name Specifies the name of the report.

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.



Adding Thresholds

This section 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 need to enter values in several tabs to create a valid threshold.

Important: Before you can add a threshold, you need to set thresholds. For more information, see IBM Tivoli Netcool Performance Manager: Command Line Interface Guide.

Resources and Metrics

To add resource threshold parameters, follow these steps:

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 popup menu. The Add Threshold dialog box opens.

5. Enter the following information for the new threshold:


Static Threshold

Mode

To set threshold mode parameters, follow these steps:




4. Select Add from the Edit menu or right-click the threshold name and select Add from the popup menu.

5. Click the Static Threshold tab.

Field Description

Metric Specifies the formula name associated with the threshold.

Group Specifies the sub-element group associated with the threshold.

Sub-Element Specifies the sub-element name associated with the threshold.



6. Click the Mode tab. Enter the following information for the new threshold:


Burst

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 set threshold burst parameters, follow these steps:






6. Click the Burst tab.

7. Select the Enable Threshold check box.


Field Description

Effective date 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.

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.

Statistic mode 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.

Field Description

Warning level Specifies the level of the warning threshold for BURST thresholds. NULL indicates that the threshold is not defined.




Period

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 set threshold period parameters, follow these steps:






6. Click the Period tab.



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.

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.

Field Description




Baseline Threshold

To add baseline threshold parameters, follow these steps:





5. Click the Baseline Threshold tab.



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.

Field Description

Max # of days Specifies the maximum number of days used to calculate the baseline threshold.

Min # of days Specifies the minimum number of days used to calculate the baseline threshold.

Calculation Select the baseline calculation mode from either PreviousDays or PrevSameDayofWeek.

Sensitivity (upper) Enter the upper threshold limit (number of standard deviations above the baseline) that must be violated before generating an event.

Sensitivity (lower) Enter the lower threshold limit (number of standard deviations below the baseline) that must be violated before generating an event.

Permitted time outside baseline Enter the time limit (in minutes, hours, or days) that a threshold can be violated before generating an event.

Field Description




Creating a New Property

Properties are the attributes or characteristics of an element or sub-element that defines its state, appearance, or value. These properties are installed by Tivoli Netcool Performance Manager Technology Packs.

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 CME memory. When a property value changes in the database, the CME obtains the new value from the next database load.


To create a new property, follow these steps:



3. Select a sub-element 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 on page 16 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 sub-element that defines its state, appearance, or value. These properties are installed by Tivoli Netcool Performance Manager Technology Packs. Property names for elements, sub-elements and report users are listed in the following tables.

Event generation Select whether to generate events for baseline threshold violations.

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


Field Description

Table 1: Sub-Element Properties

Property Description

hostname A user-defined name assigned to the host upon which this resource resides. Provided during network configuration.



description Open-format description text used for grouping.

name 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).

hostIP Physical IP address of the host upon which this resource resides.

networkArea Network area (for example, BackBone, CPE) of the entity.

type Open-format name of the specific type of resource represented (for example, Ethernet, DS1).

physicalCapacity The maximum speed of this resource (bps).

hosturl URL address assigned to the host upon which a resource resides.

parent Open-format name or ID assigned to an entity, usually other than a physical host (see 'hostName' Property), that can be considered as a "parent" containing this resource.

hostType Open-format "type" classification of the device upon which this resource resides.

parentType Open-format type classification of the parent of this resource.

class Open-format name of the general class of resource represented (for example, device, interface, logical port, or end-to-end connection).

subType If needed, more specific type information or the resource (NNI, UNI).

protocol Transmission protocol specific to the resource (ATM, Frame Relay, IP, IPSec, TCP, UDP, MPLS).

protocolVersion Version of transmission protocol being used.

model Open-format model name of the resource.

modelID Open-format model ID string of the resource.

version Open-format version identification of the resource.

patch level Open-format patch level identification of the resource.

country The country in which the resource resides.

city The city, town, or municipality in which the resource resides.

state The state in which the resource resides.

province The province in which the resource resides.

region Open-format region name in which the resource resides.

regionID Open-format ID string assigned to the region in which the resource resides.

location Open-format physical location name in which the resource resides.

locationID Open-format ID string assigned to the physical location in which the resource resides.

status Operational status of the resource (active, initializing, maintenance).

priority Open-format priority name or code.

Table 1: Sub-Element Properties (cont.)



committedCapacity The steady-rate bandwidth (bps) committed for transfer over a resource.

committedBurstCapacity The transmission rate (bps) committed for short traffic bursts (for a pre-agreed duration) over a resource.

committedPeakCapacity The maximum transmission rate committed for transfer over this resource.

owner Service provider employee name/ID to which this resource belongs.

ownerCustomTag User-definable property for custom resource organization attributes.

department Service provider department to which a resource belongs.

departmentID ID of the service provider department to which a resource belongs.

network The name of the network of which a resource is a part.

networkID The ID of the network of which a resource is a part.

privateNetwork The name of the private (virtual) network of which this entity is a part.

privateNetworkID The ID of the private (virtual) network of which this entity is a part.

customer The name of the specific customer that a resource services.

customerID The ID of the specific customer that this resource services.

customerType The type of customer that a resource services.

customerFacingName Alternate name to be used for this resource in customer-facing reports, and messages.

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

operation For monitor probes, such as RMON. The test operation being executed.

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

destIP For unidirectional entities (end-to-end simplex connections, network test probes). The IP address of the terminating side.

destURL For unidirectional entities (end-to-end simplex connections, network test probes). The URL of the terminating side.

destPort For unidirectional entities (end-to-end simplex connections, network test probes). The IP port used on the terminating side.

corbaPort The number identifying the CORBA port this entity uses.

targetDirectory File system directory to which this entity delivers processed data.




path Directory path within which this entity resides.

tablespace Name of the tablespace in which this table resides.

tablespaceClass Aggregation characteristics of the tablespace 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 ID of the Tivoli Netcool Performance Manager channel of which this entity is part.

channelTableSetType 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”

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

measurementSubInterval The duration of time (seconds) over which raw statistics from this resource are sub-aggregated 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 2: 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 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.

DV_UserProfile Defines the general user type for control of certain security options. Valid settings include the following:

• NOC - Network Operations Center user, few restrictions.

• PSLA - Proactive Service Level Agreement personnel, moderate restriction.

• SLA - End users, highest restrictiveness.




DV_UserResourceName Defines which sub-element name definitions should be used for SE labels displayed to the particular user. Valid settings include the following:

• 1 - Use the SEs' internal ALIAS field values (also dubbed "SE Labels").

• 2 - Use the SEs' internal NAME field values.

• 1771 - Use the value defined in the "customerFacingName" Property for each SE.

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

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

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.

Table 2: DataView User Properties



Modifying Resources

This section explains how to modify elements, sub-elements, reports, and thresholds using Resource Editor.


Modifying an Element

To modify an element, follow these steps:

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:





Comment Specifies descriptive comments about the element.

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



6. Click OK to accept your modifications.

Modifying a Sub-Element

To modify a sub-element or composite sub-element, follow these steps:


2. Click Apply Filter to view all sub-elements and composite sub-elements in the database, or enter filter information to limit the number of results.

3. Click the name of the sub-element or composite sub-element that you want to modify.

4. Select Update from the Edit menu or right click the element name and select Update. The Update Sub-Element dialog box opens.

5. Update the following information:

Date Specifies when the element was created or modified.

Field Description

Field Description







State Select the state of the sub-element or composite sub-element:

• on - the sub-element or composite sub-element is visible in the graphical user interface.

• off - data collection on the sub-element or composite sub-element is stopped and that the element is no longer visible in the graphical user interface.

Origin Specifies the method used to add the sub-element or composite sub-element to the database.

User Specifies the user who created the sub-element or composite sub-element.

Date Specifies when the sub-element was created or modified or composite sub-element.




Modifying a Report

To modify a report, follow these steps:



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 popup menu. The Update Report dialog box opens.

5. Enter the following information for the new report:


Modifying Thresholds

Resources and Metrics

To modify resource threshold parameters, follow these steps:



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.

5. Change the following information for the threshold:

Field Description

Name Specifies the name of the report.

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.

Field Description

Metric Specifies the formula name associated with the threshold.

Group Specifies the sub-element group associated with the threshold.




Static Threshold

Mode

To modify threshold mode parameters, follow these steps:




4. Select Update from the Edit menu or right-click the threshold name and select Update from the popup menu.


6. Click the Mode tab. The Add Threshold dialog box opens.



Sub-Element Specifies the sub-element name associated with the threshold.

Field Description

Effective date 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.

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


Statistic mode 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.

Field Description



Burst

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:






6. Click the Burst tab. The Add Threshold dialog box opens.




Period

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 period parameters, follow these steps:




Field Description

Warning level Specifies the level of the warning threshold for BURST thresholds. NULL indicates that the threshold is not defined.

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.





6. Click the Period tab. The Add Threshold dialog box opens.




Baseline Threshold

To modify baseline threshold parameters, follow these steps:





5. Click the Baseline Threshold tab. The Add Threshold dialog box opens.


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.

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.





Field Description

Max # of days Specifies the maximum number of days used to calculate the baseline threshold.

Min # of days Specifies the minimum number of days used to calculate the baseline threshold.

Calculation Select the baseline calculation mode from either PreviousDays or PrevSameDayofWeek.

Sensitivity (upper) Enter the upper threshold limit (number of standard deviations above the baseline) that must be violated before generating an event.

Sensitivity (lower) Enter the lower threshold limit (number of standard deviations below the baseline) that must be violated before generating an event.

Permitted time outside baseline Enter the time limit (in minutes, hours, or days) that a threshold can be violated before generating an event.

Event generation Select whether to generate events for baseline threshold violations.

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




Deleting Resources

This section explains how to delete the following resources from the database:

• Elements and sub-elements

• Sub-element groups

• Sub-elements within groups

• Properties associated with elements and sub-elements

When you delete an element, you delete the associated sub-elements. When you delete a property, you delete only the property.


Deleting Elements or Sub-Elements

To delete elements, sub-elements or composite sub-elements, follow these steps:

1. Click the Element or the Sub-Element tab.


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 Sub-Element Groups

To delete sub-element groups, follow these steps:

1. Click the Sub-Element Group tab in Resource Editor.

2. Click the sub-element group to expand it and select the name of the group. The sub-elements contained in the group appear in the right pane.


4. Click Yes to continue, or No to cancel.

Deleting Resources Within Groups

To delete resources within groups, follow these steps:

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 sub-elements 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.


6. Click Yes to delete the resource, or No to cancel.

Deleting Properties

To delete properties:

1. Click the Element or Sub-Element tab in the Resource Editor.


3. Select a resource whose properties you want to delete.

4. Click Detail to display the properties table.

5. Click the property name you want to delete.


7. Click Yes to delete, or No to cancel.

Deleting Composite Sub-Element Relations

To delete composite sub-element relationships, follow these steps:



3. Click a composite sub-element name.

4. Click Detail to display the list of properties associated with the selected composite sub-element.

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

This section explains how to manually deploy reports using Resource Editor.

To deploy reports, follow these steps:



3. Click the Report SEGroup tab.

4. Expand a group to view a list of the rules applied to and select a rule to display any reports currently deployed against it.

5. Click the Report tab to display the list of reports again.

6. Click the report name you want to deploy to highlight it.

7. Copy the report by pressing Ctrl + C.

8. Click the Report SEGroup tab to select it again.

9. Click the group name in the left pane to highlight it.

10. Press Ctrl + V to paste the report into the frame. You are prompted to confirm your choice.

11. Click Yes to continue. The copied report displays in the right pane.

12. Move the cursor to the left pane and scroll up to select SUB-ELEMENTS.

13. Right-click and select AutoGrouping from the pull down menu. A confirmation prompt opens.

14. Click Yes to continue. Click Close to exit the message box or click Details to view a description of any errors or warnings.


Chapter 2: Viewing Collected Data


Topic Page

Viewing Graphical Charts for Files 32

Viewing Graphical Charts for Sub-Elements 33

Viewing Graphical Charts for Sub-Element Groups 35

Saving a Graph 36

Printing a Graph 37

Configuring Graphs 38



Viewing Graphical Charts for Files

This section explains how to view a list of curves contained in a file, which you can then display in graphical form.

To view curves, follow these steps:

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 listbox. A list of curves appear in the bottom listbox.

3. Select one or more curves that you want to display in graphical form.

4. Click Apply to accept your selections.



Viewing Graphical Charts for Sub-Elements

This section explains how to view graphical charts for sub-elements.

To view graphical charts for sub-elements, follow these steps:

1. Click Data Viewer in the Data Manager tab.

2. Click the Sub-elements tab. The following windows appears:

3. Click Apply Filter to view all sub-element names in the left pane, or enter filter information to limit the number of results.

Tip: You can sort columns by clicking on the column titles.

4. Select one or more sub-elements 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. For example:



Tip: You can display multiple graphs simultaneously in the Data Viewer window.

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

One sub-element and four formulas are selected in this example:



Four sub-elements and four formulas are selected in this example:

11. See the next sections to save, print, and configure graphs.

Viewing Graphical Charts for Sub-Element Groups

This section explains how to view graphical charts for sub-elements groups.

To view graphical charts for sub-elements groups, follow these steps:

1. Click Data Viewer in the Data Manager tab.

2. Click the Sub-Element Groups tab. The following window appears:



3. Select one or more sub-element groups from the list in the left pane.

4. Select one or more formulas from the list in the right pane.

5. Select a time range in the Data Range Selection group from the following:

— Current - Selects currently collected data.

— Recent - Selects recently collected data.

— History - Select historical data.

6. Select one or more data types in the Data Type group from the following:

— Raw - Provides raw collected data.

— Min - Provides minimum values of the raw data according to 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 listbox 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 listbox 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

This section explains how to save a graph.

To save a graph, follow these steps:

1. Select Save from the File menu. The following window appears.

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 listbox from one of the following:

— Bin format - Compacted ASCII format. Only the date and measure value are preserved in the data lines.



— 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

This section explains how to set up printing for graphical charts in the Data Viewer.

To set up printing, follow these steps:

1. Select Print from the File menu. The Page Setup window appears:

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

This section explains how to configure a graph.

Displaying Crosshairs

To display crosshairs, follow these steps:

1. Right-click an area inside the graph and select the Configuration menu item. The following window appears:

2. Click Display CrossHair in the General tab.

3. Select a line width for the crosshairs from the Width drop down menu.

4. Select a dash format for the crosshairs from the Dash drop down menu.

5. Select a color for the crosshairs from the Color drop down menu.

6. Click OK to accept your selections. Crosshairs appears in the graph. For example:



Displaying a Grid

To display a grid, follow these steps:

1. Right-click an area inside the graph and select the Configuration menu item.

2. Click the General tab. The following window appears:

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 pulldown box.

6. Select a dash format for the grid from the Dash drop down menu.

7. Select a color for the grid from the Color drop down menu.

8. Click Apply or OK to accept your selection. A grid appears in the graph:



Example of a grid with the ticks option selected:

Configuring a Title

To configure a title, follow these steps:


2. Click the General tab. The following window appears:

3. Click Configure Title in the General tab.

4. Select a font style for the title from the Font listbox.

5. Select a weight for the title from the Weight listbox.

6. Select a slant for the title from the Slant listbox.



7. Select a point size for the title from the Size listbox.

8. Select a color for the title from the Color box.

9. Click OK to accept your selections. A title appears in the graph. For example:

Configuring the X Axis

To configure the X axis, follow these steps:


2. Click the Axis tab and select X axis. The following window appears:

Title



3. Enter a title for the X axis in the Title box.

4. Select a line width for the X axis from the Width drop down box.

5. Select a color for the X axis from the Color drop down box.

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. For example:



Customizing the Y Axis

To customize the Y axis, follow these steps:


2. Click the Axis tab and select Y axis. The following window appears:

3. Select Y Axis in the Axis tab.

4. Enter a title for the Y axis in the Title box.

5. Select a line width for the Y axis from the Width drop down box.

6. Select a color for the Y axis from the Color drop down box.

7. Select a scale type in the Scale group from the following:

— Linear - displays the graph using straight lines.

— Logarithmic - displays the graph in powers of ten (ten times more lines than the Linear option).

8. Click OK to accept your selection. The Y axis in the graph is configured accordingly. For example:



Configuring Curves

To configure curves, follow these steps:


2. Click the Curves tab. The following window appears:

3. Select a curve that you want to modify from the Curve listbox.

4. Select the desired line width for the curve from the Width pulldown box.

5. Select a dash format for the curve from the Dash drop down menu.

6. Select a symbol format from the Symbol drop down menu.

7. Select a color from the Color box to change the color of the graphical points.

8. Specify the legend by entering the appropriate label in the Legend field.

9. Select the curves displayed from the Curves to Display scroll-down list.

10. Click Apply or OK to accept your selections. The curve is modified accordingly. For example:



Configuring a Graph Legend

To configure a graph legend, follow these steps:


2. Click the Legend tab. The following window appears:

3. Click Yes to display the legend.

4. Select the position for the legend in the Position listbox from the following:

— Top - Top of graph

— Bottom - Under graph

— Right - Right of graph

— Left - Left of graph

— Plot Area - In the graph

5. Select a font for the legend from the Font listbox to choose a font style for the title.

6. Select a weight for the legend from the Weight listbox.

7. Select a slant for the legend from the Slant listbox.

8. Select a point size for the legend from the Size listbox.

9. Select a color for the legend from the Color box.



10. Click OK to accept your selections. A legend appears in the graph. For example:



NOTES


Chapter 3: Viewing Collector Information


Note: 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.

Topic Page

Viewing the List of Collectors 50

Viewing Collector Information 51

Viewing Scheduler Information 52

Viewing Data Manager Information 55

Viewing Target Information 56

Viewing Detailed Technical Information 58

Stopping and Restarting a Local Collector 60

Configuring Watchdog for Collector Memory Checking 61



led.

Viewing the List of Collectors

This section explains how to view information about both active and non-active collectors using the Collector Information Tool.

To view the collectors list, follow these steps:

1. Click Collector Information from the Monitor tab. The following window appears:

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 instal

Port Indicates the communication port number for the collector.

Type Indicates the collector type.

Installation Directory

Indicates the directory where the collector is installed.



own. This

reshed (in

bug. The oses.

Viewing Collector Information

This section explains how to view detailed information about a collector.

To view collector information, follow these steps:

1. Click Collector Information from the Monitor tab.

2. Select a collector from the list.

3. Click the Collector Information tab. The following window appears:

The State group displays the following information:

Traffic light (collector state)Exit Refresh Apply

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 shutdis a temporary state.

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 refseconds).

Current debug level Indicates the current debug level of the collector. “0” indicates a minimal delevel should be set to “0”; a level of “1” or more is for troubleshooting purp

Version Displays the version date and operating system for the collector.

Server Displays the name of the computer on which the collector is running.



i Netcool

(in days,

collector rent from art uses

ntly save

ical

) to a log path.

o activate

cting this .

.

s your d.log on

The Actions group displays the following information:

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.

To view Scheduler information, follow these steps:



Port Displays the port number that the collector uses to communicate with TivolPerformance 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 hours, minutes, and seconds).

Current Time Displays the day, month, year, and time of day as set on the server where theis running (dependent on your time zone). The time shown here can be diffelocal time. This is the time that Tivoli Netcool Performance Manager DataMto schedule data collection, if you declare a calendar from 8 am to 8 pm.

Item Description

Item Description

Refresh interval Modifies the current refresh value frequency.

Start/Stop button Launches or shuts down the local collector.

Current tab Displays the following options:

Note: Tivoli Netcool Performance Manager DataMart does not permaneyour selections in the Current tab.

• Debug level - Modifies the debug level of the collector. Contact technsupport at IBM for more information about debugging.

• Log Path - Saves the debug information file (ServReqDaemonxxxx.logspecific path. You can use the Directory Selection button to select theThe default log directory is $PVMHOME/log.

• Date in file - Displays the creation date in the log file name. Select Yes tthis option. For example, pvmd_9991015_16348.log.

• Channel in file - Displays the request number in the log file name. Seleoption 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 storeselections in the configuration file. For example, in $PVMHOME/conf/pvmthe server system.



llector.

of external

of internal

of requests

r of requests

requests

execution rate ith results on

ution rate per hours but is er than one

he requests to

generated in

figuration

3. Click the Scheduler tab. The following window appears:

The Scheduler window displays the following information:

Item Description

Collections Priority Mode

Indicates the number of Collections Priority Mode requests on the current co

Execute requests Indicates the number of requests being executed on the collector.

• Execute external requests (Nb) [immediate] - Indicates the numberrequests being executed on the collector.

• Execute internal requests (Nb) [immediate] - Indicates the numberrequests being executed on the collector.

Items Processed Indicates the collector activity level. The activity level is measured in number executed per second over a specific time period.

• Items Processed Average (Nb) [last 24 hours] - Indicates the numbeexecuted during the last 24 hours.

• Items Processed Average (Nb) [last hour] - Indicates the number ofexecuted during the last hour.

• Items Processing Rate (Nb/s) [last 24 hours] - Indicates the request per second during the last 24 hours. You can compare this activity level wcomparable systems to evaluate performance.

• Items Processing Rate (Nb/s) [last hour] - Indicates the request execsecond during the last hour. This rate is similar to the rate for the last 24more sensitive to variations during collections over longer periods (longhour).

Items Scheduled Requests that need to be executed. The Scheduler scans the list to determine texecute or to place in the waiting queue.

• Items Scheduled (Nb) [immediate] indicates the number of requeststhis list.

• Max Items Scheduled (Nb) [immediate] indicates the maximum convalue for the request list size.



er to execute.

ained by the

by the queue

each time it collector

through y from 1 to e following

during the last

ring the last

needs to

Queue Max Size Third of the three waiting queues where a thread searches for a request numb

• Queue Max Size (Nb) [last 24 hours] indicates the maximum size attqueue during the last 24 hours.

• Queue Max Size (Nb) [last hour] indicates the maximum size attainedduring the last hour.

• Queue Size (Nb) [immediate] indicates the current size of the queue.

Threads Collector activity creates threads. The collector verifies it can activate a threadexecutes a collection or launches a command. If it cannot activate a thread, noactivity occurs and reliability is diminished.

• Threads (Nb) [immediate] - Indicates the number of threads created collector activity. This is a realtime counter. The value can change quicklMaxThreadedItems. You can tune this value in the registry.conf file in thlocation:

$PVMHOME/conf/registry.conf• Threads Availability (%) [last 24 hours] - Indicates collector reliability

24 hours.

• Threads Availability (%) [last hour] - Indicates collector reliability duhour.

internal errors (Nb) [cumul]

Indicates the number of memory errors detected and corrected. This counterremain at zero. If it is not at zero, restart the collector.

Item Description



he

sing time for

g time for a

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.

To view data manager information, follow these steps:



3. Click the Data Manager tab. The following window appears:

The Data Manager window displays the following information:

Item Description

.dat files • dat files (nb) [immediate] - Indicates the number of .dat files located in t$PVMHOME/data directory.

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

• Average Storage Time (ms) [last 24 hours] - Indicates the average procesa measure during the last 24 hours.

• Average Storage Time (ms) [last hour] - Indicates the average processinmeasure during the last hour.

Congestion State Indicates the Congestion State code.



he file system.

e file system.

pace on the

he file system.

on the file

time and the

r of measures

f measures

ve been lost saved.

st during the

uring the last

stored. For

ures stored. last 24 hours.

stored. For our.

res are te a loss of

ability during

ity during the

Viewing Target Information

Each time the collector interacts with an SNMP agent, information about the interaction is recorded.

To view target information, follow these steps:



Filesystem Indicates file system space information:

• Filesystem FSLL (KB) [immediate] - Indicates the size of the FSLL for t

• Filesystem available (KB) [immediate] - Indicates the available size of th

• Filesystem free space (KB) [immediate] - Indicates the amount of free sfile system.

• Filesystem quota (KB) [immediate] - Indicates the size of the quota for t

• Filesystem used (KB) [immediate] - Indicates the amount of space usedsystem.

Measures A measure is a record inserted into the record file. Each insertion is measured inmedian value is posted.

• Measures Processed Average (Nb) [last 24 hours] - Indicates the numbeprocessed during the last 24 hours.

• Measures Processed Average (Nb) [last hour] - Indicates the number oprocessed during the last hour.

• Measures Lost (Nb) [cumul] - Indicates the number of measures that hasince the start of the collector. These measures were collected but were not

• Measures Lost (Nb) [last 24 hours] - Indicates the number of measures lolast 24 hours. These measures were collected but were not saved.

• Measures Lost (Nb) [last hour] - Indicates the number of measures lost dhour. These measures were collected but were not saved.

• Measures Stored (Nb) [cumul] - Indicates the total number of measuresexample, total number of answers from metrics requested.

• Measures Stored (Nb) [last 24 hours] indicates the total number of measFor example, the total number of answers from metrics requested over the

• Measures Stored (Nb) [last hour] indicates the total number of measuresexample, the total number of answers from metrics requested over the last h

Save Availability Displays the reliability of data insertion. Reliability of 100% means that all measucorrectly inserted. A reliability rate of less than 100% does not necessarily indicameasures, but should be investigated.

• Save Availability (%) [last 24 hours] - Indicates the calculated insertion relithe last 24 hours.

• Save Availability (%) [last hour] - Indicates the calculated insertion reliabillast hour.

Item Description



SNMP packet ring the MIB

r.

e all requests OIDs handled equency of

rocess in the

ery process in

rocess in the

ss in the last

process in the

ess in the last

3. Click the Targets tab. The following window appears:

The Targets window displays the following information:

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 and its return. Time is not calculated on the exchanged packets dubrowse.

CALC Errors (Nb) [last hour] Indicates the number of CALC errors that occurred in the last hou

CPU Load (Nb OIDs) [last hour] Indicates the estimated CPU load needed by the collector to handlrelating to this target. This measurement integrates the number of to solve the requests, the number of requests necessary, and the freach interrogation.

Discovery Received PDU (Nb) [last hour]

Indicates the number of PDUs received as part of the discovery plast hour.

Discovery Received PDU Max Size (bytes) [last hour]

Indicates the maximum size of PDUs received as part of the discovthe last hour.

Discovery Received PDU Total Size (bytes) [last hour]

Indicates the total size of PDUs received as part of the discovery plast hour.

Discovery Sent PDU (Nb) [last hour]

Indicates the number of PDUs sent as part of the discovery procehour.

Discovery Sent PDU Max Size (bytes) [last hour]

Indicates the maximum size of PDUs sent as part of the discoverylast hour.

Discovery Sent PDU Total Size (bytes) [last hour]

Indicates the total size of PDUs sent as part of the discovery prochour.

Expected Measures (Nb) [last hour] Indicates the number of measures expected in the last hour.



at occurred in

lue of 0% can icient. A value ing the SNMP

tered during is correct and nt problem in the MIB ormula.

e the start of quests.

Viewing Detailed Technical Information

You can view detailed technical information about the collector that displays all current tasks managed by the collector.

To view detailed technical information, follow these steps:



Max SNMP Response Time (ms) [last hour]

Indicates the maximum amount of time for an SNMP response ththe 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.

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 vaindicate a bad community name or that the timeout value is insuffmore than 0% but less than 100% is often caused by timeouts durinteraction.

SNMP Errors (Nb) [last hour] Indicates the total amount of errors in the SNMP protocol encounthe interaction. An error cannot occur when the community namethe timeout is correctly configured. An error signifies either an ageresponding to a packet or an error between the collector MIB andsupported by the agent. Most often it indicates a problem with a f

SNMP Requests (Nb) [cumul] Indicates the total number of executed requests on equipment sincthe collector. You can identify the equipment with a high rate of re

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.

Item Description



. See Viewing

t use any

disappears as

waiting for an ccording to its hanges to

3. Click the Detail Information tab. The following window appears:

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

<priority> Valid values include the following:

• Realtime

• High

• Normal

The priority chosen here is linked to the corresponding Scheduler priority queueScheduler Information on page 52 for details.

<state> Valid values include the following:

• ASLEEP - indicates that the task is set for the next execution and does noresources.

• ACTIVE - indicates that the task is currently running. This state appears andthe task processes SNMP queries.

• ZOMBIE - indicates that the task is about to disappear from view.

• READY - indicates that the task has reached the time of the next start but isavailable thread to be executed. The task has been place in a waiting queue acurrent priority value. As soon as the task is handled by a thread, the state cACTIVE.



f the following

Note: Formulas (PVL-Tivoli Netcool Performance Manager-Statistics) are available that monitor collector statistics. See the IBM Tivoli Netcool Performance Manager Technology Packs User’s Guide for details.

Stopping and Restarting a Local Collector

You can stop the local collector from the Collector Information Tool window.

To stop a local collector, follow these steps:



3. Click the Collector Information tab.

4. Click the Stop button in the Actions group, then confirm your choice at the prompt.

5. Click Yes to confirm.

Note: To stop a remote collector, you need to connect to the system on which the collector resides and launch the pvmdmgr script with the stop option. For example: pvmdmgr stop

Restarting a Local Collector

You can restart the local collector from the Collector Information Tool window.

To restart a local collector, follow these steps:

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

<type> Name of the service for this task:

• ServiceSTAT - displays a list of the tasks currently running.

• ServiceCRON - executes commands at different preset times.

• ServiceFORM and ServiceGet - execute SNMP queries

- Trgt indicates that the target host that is being queried. A target can be one otypes:

element (Elmt)sub-element (SubElmt)group of elements (ElmtGrp)group of sub-elements (SubElmtGrp)

- Form indicates the formula used for the query.

- Inst lists the instances impacted during the query process.

Item Description



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 include the following:

[Quallaby\PROVISO-Daemon\WatchMgr] "ActivateWatchMgr"="1" "UseErrorsCount"="1" "UseMemoryChecking"="0" "UseWatchDog"="1" [Quallaby\PROVISO-Daemon\WatchMgr\ErrorsCount] "MaxErrorsCount"="10"[Quallaby\PROVISO-Daemon\WatchMgr\MemoryChecking] "MinimalWorkingSet"="134217728" "MaximalWorkingSet"="1073741824" "WorkingSetInflation"="1000"[Quallaby\PROVISO-Daemon\WatchMgr\WatchDog] "MaxPulseInterval"="250" "PulseInterval"="80"

Activation of Memory Checking

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.

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.



To set up this value, start a Tivoli Netcool Performance Manager process, let it run for one hour, get the process size using the “ps” command, modify the registry.conf file, and restart the collector.

Setting Inflation Limit

You can control memory usage. For example:

"WorkingSetInflation"="1000"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.

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



NOTES


Chapter 4: Viewing Status


Overview

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.

Note: 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 Tivoli Netcool Performance Manager DataMart Status

This section explains how to use the Tivoli Netcool Performance Manager DataMart Status tool to view the status of individual modules.

To view Tivoli Netcool Performance Manager DataMart status, follow these steps:

1. Click DataMart Status in the Applications tab. The following window appears:

Topic Page

Overview 65

Viewing Tivoli Netcool Performance Manager DataMart Status 65

Removing a Lock from the Database 67

ExitRemove Locks

Refresh



The Registered Modules group displays the following information:

The Locked Modules group displays the following information:

The following modules do not use a collector:

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

— Userconf - There is no connection between a collector and the users descriptions. This part of the configuration is not loaded/reloaded by a collector.

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.

Item Description

Lock Name of the locked module.

Mode Protection level that the lock provides. 0 = Read Only1 = Read/Write

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.



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.

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.

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.

ExitRemove Lock

Refresh



NOTES


Chapter 5: Viewing Database Information


Note: Before you view database information, ensure that libpvmextc.so is running.

Topic Page

Viewing Database Information 70

Viewing MetaData 74

Viewing MetricData 84

Viewing Client Information 90

Viewing Database Status 91

Viewing Disk Information 92



Viewing Database Information

This section explains how to view information on the Tivoli Netcool Performance Manager DataMart database, instance, and status.

To view database information, follow these steps:

1. Click Database Information in the Monitor tab. A splash screen appears followed by the ProvisoInfo Browser. The following window is displayed:

2. Click the Refresh objects from the database button to globally update the window with the most recent database information.

3. Click the Identification tab. The Identification tab provides the following information:

Item Description

Database Server Name Name of the server where the database 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.

Exit Refresh objects from provisoinfo daemon

Refresh objects from the database.

Server status Database free space status

Green means connected (provisoinfo daemon is running). Red means disconnected (daemon is not running).



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.

The Database Free Space Status values include the following:

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

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.

Total SGA 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):

• Fixed Size - exact size. For example, 72K.

• Variable Size - shared spool. For example, 291M.

• Database Buffers - part of the SGA that holds copies of blocks of data read from the Oracle datafiles on disk. For example, 125M.

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

Item Description

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.



Viewing Database Parameters

To view database parameter information, follow these steps:

1. Click the Database folder. The Parameters and Statistics folders appear.

2. Click the Parameters folder to view database parameter information. The following information appears:

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

To view database statistics information, follow these steps:

1. Click the Database folder. The Parameters and Statistics folders appear.



2. Click the Statistics folder to view database statistics. The following information appears:

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

To view version information, follow these steps:

1. Click the Proviso Version folder to display version information. The following information appears:

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.

To view Metadata information, follow these steps:

1. Click the MetaData tab. The following window appears:

2. Expand the Tablespaces item. The following items appear:

3. Expand the Metadata item. The following tablespace items appear:



4. Click a tablespace item. The following information is displayed:

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. The following information is displayed:



7. Expand the Temporary tablespace item and the items beneath it to view sizing information in megabytes. For example:

8. Expand the System & Rollback item. The SYSTEM item appears.

9. Click the SYSTEM item to display spacing information. The following information is displayed:



10. Expand the SYSTEM item to view only the total space used (in megabytes). The following information is displayed:

11. Expand the Meta Tables item. The following items appear:

12. Expand the Formulas item. The following items appear:



13. Click the FRML_DESC item in the Formulas tree. The following information appears:

This information lets you quickly view table structures and provides a short description of the purpose of each column (if available).

14. Click the FRML_DESC_HIST item. The following information is displayed:



15. Click the FRML_GRP_DESC item. The following information is displayed:

16. Click the FRML_GRP_MEMBER item. The following information is displayed:



17. Click the FRML_GRP_PATH. The following information is displayed:

18. Click the FRML_MIB. The following information is displayed:



19. Click the FMRL_MIB_HIST. The following information is displayed:

20. Click the Resources item to expand the branch. The following items appear:

21. Click the Grouping - Inventory item to expand the branch. The following items appear:



22. Click the Properties - Thresholds item to expand the branch. The following items appear:

23. Click the Dataview item to expand the branch. The following items appear:

24. Click the Nomenclature item to expand the branch, The following items appear:

25. Click the Schedule - Collect item to expand the branch. The following items appear:

26. Click the Miscellaneous item to expand the branch. The following items appear:



27. Click the Internal item to expand the branch. The following items appear:



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.

To view metric data, follow these steps:

1. Click the MetricData tab.

2. Click the Aggregation Sets tab. The following information is displayed:

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. Click a GMT value in the tree to view the aggregation set status for that GMT. The following information is displayed:



4. Click a channel item to get additional partition information. The following information is displayed:

5. Click the Channels tab to display channel information. The following information is displayed:

6. Click the Working item to expand the branch. The following items appear:



7. Click an item to display file names. The following items appear:

8. Click a file name. The following information is displayed:

9. Click the Historic item to expand the branch. The following items appear:

10. Click a historic item. The following information is displayed:

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. The following information is displayed:.

12. Click a DataLoad collector number under the DataLoads tree. The following information is displayed for an SNMP collector:



The following information is displayed for a Bulk Collector:

13. Click the Registry tab. The following window appears:

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 tree to expand the branch. The following items appear:



15. Click the Common item in the Registry tree to expand the branch. The following items appear:

16. Click the Current folder. The following information appears:

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 tree to expand the branch. The following items appear:

18. Click the Channel (C01) item in the Registry tree to expand the branch. The following items appear:



Viewing Client Information

This section explains how to view Oracle client status information on the Tivoli Netcool Performance Manager Database, DataMart, DataLoad, DataChannel, and DataView.

To view client information, follow these steps:

1. Click the Clients tab. The following window appears:

2. Click either Database, DataLoad, DataView, DataMart or Data Channel. the following information is displayed:

In the example above, the Oracle IDs that have been created in the database are displayed and only one client is connected by PV_ADMIN.



Viewing Database Status

This section explains how to view database status to help you troubleshoot problems.

To view database status, follow these steps:

1. Click the Database Status tab. If the database is normal, the following information is displayed:

If the status of the database is in the Warning, Critical, or Deadzone state, the following information is displayed:

In the example above, only 7 percent of overall free space remains available, and the database is 90 percent full.



Viewing Disk Information

This section explains how to view disk information.

To view disk information, follow these steps:

1. Click the Disk tab. The following window appears:

2. Click the / (forward slash) to display the amount of free disk space. The following information is displayed:



3. Click var to display the amount of free disk space. The following information is displayed:

4. Expand /export/home to expand the branch and view mount point disk space information. The following items appear:



5. Click an item. The following information is displayed:



NOTES


Chapter 6: Exporting or Importing Metadata


Exporting Data

This section 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.

To export data, follow these steps:

1. Click Import-Export Configuration in the Configuration tab. The following window appears:

The EXPORT operation is enabled by default. An Export operation can be used even if the module is running in read-only mode.

Topic Page

Exporting Data 97

Importing Data 104

Exit Run



2. Click the Browse button to navigate to the target directory where you want to store the files. The following window appears:

The default path (/opt/datamart) appears in the Directory listbox. Since an export procedure can generate numerous files, it may be helpful for you to create a new directory for organizational purposes.

To create a new directory, enter its name in the Directory Name box and click OK. The directory will be automatically created in the $PVHOME/importexport directory path.

3. Select a profile to export from the Type of Data pulldown listbox. The following data types are available:

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:

Option Description Operation Profile(s)

formulas Export of metrics used for collections.

• exportFormulas (default) - Exports all formulas (listed below) from the database.

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

• exportPsFormulas - Exports all formulas created by IBM Professional Services.

• exportPvlFormulas - Exports formulas created by Tivoli Netcool Performance Manager Application. The indices for these formulas is less than 50000000.

*where indices = database IDs.



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.

calendars Export period of collection configurations (no link with timezones).

• exportCalendars (default) - Exports all calendars. This profile includes the profiles below.

• exportCustomCalendars - Exports all calendars created by the users. The custom data indices are greater than 100000000.

• exportPsCalendars - Exports all calendars created by IBM Professional Services.

• exportPvlCalendars - Exports all calendars created by Technology Packs. Indices are less than 50000000.

users Export of users and user permissions.

• exportUsers - Exports all users.

timezones Export of aggregation sets configuration.

• exportTimeZones - Exports aggregation set descriptions.

elements Export of elements configuration. • exportElements (default) - Exports all elements and groups..

subelements Export of sub-elements configuration.

• exportSubElements (default) - Exports all sub-elements.

• exportSubElements_Skeleton - Exports sub-element groups.

• exportLinks_subEltGroups/ aggregationSets - Exports the links between sub-element groups and aggregations sets.

dashboards Export of dashboards. • exportDashboards - Exports all dashboards,

resources Export of sub-elements and elements.

• exportResources - Combines exportElements and exportSubElements profiles.

requests Export of data requests. • exportRequests - Exports all data collection requests.

thresholds Export of thresholds. • exportThresholds - Exports all thresholds.

inventory_profiles Export of inventory profiles. • exportInventoryProfiles - Exports all inventory profiles.

reports Export of reports. • exportReports - Exports all reports.

snmp_parameters Export of SNMP parameters. • exportSnmpElements - Exports SNMP parameters.

core_configuration Export of core configuration. • exportCoreConfiguration - Exports core configuration.

all Export all of the data types. • 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.




The differences between formulas and calendars created within DataMart modules and those created by an Technology Pack include the following:

— To recognize the data created by the Tivoli Netcool Performance Manager Technology Packs, the database indexes ranged from 0 to 50000000 is reserved.

— 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. For example:

5. Click the Run button 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 the Details button to display more information on 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

An export procedure creates files and places them in the target directory you specified in Exporting Data on page 97. These files are used when you perform an import procedure.

The datatypes.res file is used for an import procedure, as it contains a list of all data types that have been 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.datcustom_mib.datpvl_formula.datpvl_mib.datps_formula.datps_mib.dat

exportCustomFormulas custom_formula.datcustom_mib.dat

exportPsFormulas ps_formula.datps_mib.dat

exportPvlFormulas pvl_formula.datpvl_mib.dat

calendars

exportCalendars customCalGlob.datcustomCalPlan.datpvlCalGlob.datpvlCalPlan.datpsCalGlob.datpsCalPlan.dat

exportPsCalendars psCalGlob.dat psCalPlan.dat

exportCustomCalendars customCalGlob.datcustomCalPlan.dat

exportPvlCalendars pvlCalGlob.datpvlCalPlan.dat

users

exportusers usersDesc.datusersGrgpLink.datusersGroups.datusersRights.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

exportSubElements 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

segrpToTz.dat

dashboards exportDashboards dbdDesc.dat dbdText.dat dbdThresholds.dat dbdViews.dat

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

core_configuration exportCoreConfiguration 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




Importing Data

This section 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.

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




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

Importing is disabled if the module is read-only.

To import data, follow these steps:

1. Click Import-Export Configuration in the Configuration tab. The following window appears:

2. Click the Import option.

3. Click the Browse button to navigate to the target directory where the files are stored. The following window appears:

4. Select a profile to import from the Type of Data pulldown listbox. The following data types are available:

Exit Run



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:


formulas Import of metrics used for collections.

• importFormulas (default) - Imports all formulas (listed below) from the database.

• 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 indices* are greater than 100000000.

• importPsFormulas - Imports all formulas created by Tivoli Netcool Performance Manager Professional Services.

• importPvlFormulas - Imports formulas created by Tivoli Netcool Performance Manager Application. The indices for these formulas is less than 50000000.

*where indices = database IDs.

calendars Import period of collection configurations (no link with timezones).

• importCalendars (default) - Imports all calendars. This profile includes the profiles below.

• importCustomCalendars - Imports all calendars created by the users. The custom data indices are greater than 100000000.

• importPsCalendars - Imports all calendars created by IBM Professional Services.

• importPvlCalendars - Imports all calendars created by Technology Packs. Indices are less than 50000000.

users Import of users and user permissions.

• importUsers - Imports all users.

elements Import of elements configuration. • importElements (default) - Exports all elements and groups.

subelements Import of sub-elements configuration.

• importSubElements (default) - Exports all sub-elements.

• importSubElements_Skeleton - Exports sub-element groups.

• importLinks_subEltGroups/ aggregationSets - Exports the links between sub-element groups and aggregations sets.

dashboards Import of dashboards. • importDashboards - Exports all dashboards,

resources Import of sub-elements and elements.

• importResources - Combines exportElements and exportSubElements profiles.

requests Import of data requests. • importRequests - Exports all data collection requests.

thresholds Import of thresholds. • importThresholds - Imports all thresholds.



5. Select an import profile from the Operation Profile listbox or accept the default. An import profile defines how to import data. For each data type, one or more import profile types are available. For example:

6. Click the Run button 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 the Details button to display more information on the import procedure.

7. When the operation ends, click Close to exit the message box. After an import procedures 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 procedures 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 can not be imported using the importExport tool.

inventory_profiles Import of inventory profiles. • importInventoryProfiles - Imports all inventory profiles.

reports Import of reports. • importReports - Imports all reports.

snmp_parameters Import of SNMP parameters. • importSnmpElements - Imports SNMP parameters.

core_configuration Import of core configuration. • importCoreConfiguration - Imports core configuration

all Import all of the data types. • 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.




NOTES


Index

A

addingresources 9thresholds 12

B

Bin format 36BOF format 36

C

collected datacustomizing 41viewing 32

collectorconfiguring Watchdog 61installation directory 50number 50port 50restarting 60server 50status 50stopping 60target information 56type 50viewing

Scheduler information 52viewing Data Manager information 55viewing detailed technical information 58viewing information 51viewing lists 50

crosshairs 38

D

Data Viewerbin and BOF formats 36crosshairs 38customizing the X axis 41GMT and local timestamps 36printing a graph 37setting up printing 37viewing graphical charts 32

database

name 70, 71removing locks 67server name 70, 71viewing free space status 71viewing information 70viewing parameters 72viewing statistics 72viewing status 91

DataMartcopyright information for tools 117

deletingresources 28

deploying reports 30disk information 92

E

elementsexporting 7importing 8, 9, 10, 12, 21, 22, 23, 29viewing 3

exportingdata 97, 104resources 7

F

filteringelements and sub-elements 2

G

GMT 36graphical charts

setting up printing 37viewing for collected data 32

I

importingelements 8, 9, 10, 12, 21, 22, 23, 29sub-elements 8, 9, 10, 12, 21, 22, 23, 29


Index

L

locks 67

M

metadata 74metric data 84modifying

elements 21multiple collectors

viewing 50

O

Oracle client information 90

P

portfor collector 50

propertiescreating 16viewing 5

property names 16provisoinfo daemon 70

R

removing locks from the database 67reports

deploying 30Resource Editor

exporting 7importing 8, 9, 21viewing elements 3viewing property details 5viewing sub-element groups 4viewing sub-elements 4, 6viewing thresholds 6

Resource Managerproperty names 16

resourcesdeleting 28exporting 7importing 8, 9, 21viewing 3

restarting a collector 60

S

SCOTTY Stackcopyright information 117

statusviewing 65

stopping a local collector 60sub-elements

importing 8, 9, 10, 12, 21, 22, 23, 29viewing 4, 6

T

tablespaces 74target information 56temporary tablespaces 76thresholds 12

burst 13, 15, 25, 26period 14, 25

U

unlocking a module 67

V

viewingcollected data 32collector information 51Data Manager information 55disk information 92metadata 74metric data 84multiple collectors 50Oracle client information 90Scheduler information 52target information 56

W

Watchdogconfiguring 61

X

Xwpick


INDEX

copyright information 119


Index


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

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.

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

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

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to 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 systems. 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 system 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.

If you are viewing this information in softcopy form, the photographs and color illustrations might not appear.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States, other countries, or both.

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

Microsoft and Windows are registered 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 product, and service names may be trademarks or service marks of others.

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.


Additional Copyright Information

The following copyright information is for software used by Tivoli Netcool Performance Manager.

Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK 8.3.3

This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.

The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing copyright notices are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee is required for any of the authorized uses. Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply.

IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only "Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authors grant the U.S. Government and others acting in its behalf permission to use and distribute the software in accordance with the terms specified in this license.

SCOTTY Stack

This software is copyrighted by Juergen Schoenwaelder, the Technical University of Braunschweig, the University of Twente, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.



THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN “AS IS” BASIS, AND THE AUTHORS AND


DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

Various copyrights apply to this package, listed in 3 separate parts below. Please make sure that you include all the parts. Up until 2001, the project was based at UC Davis, and the first part covers all code written during this time. From 2001 onwards, the project has been based at SourceForge, and Networks Associates Technology, Inc hold the copyright on behalf of the wider Net-SNMP community, covering all derivative work done since then. An additional copyright section has been added as Part 3 below also under a BSD license for the work contributed by Cambridge Broadband Ltd. to the project since 2001.

Part 1: CMU/UCD copyright notice: (BSD like)

Copyright © 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000

Copyright © 1996, 1998-2000 The Regents of the University of California

All Rights Reserved

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.

CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Part 2: Networks Associates Technology, Inc copyright notice (BSD)

Copyright © 2001, Networks Associates Technology, Inc

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer

in the documentation and/or other materials provided with the distribution.• Neither the name of the NAI Labs nor the names of its contributors may be used to endorse or promote products derived

from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Part 3: Cambridge Broadband Ltd. copyright notice (BSD)

Portions of this code are copyright © 2001, Cambridge Broadband Ltd.

All rights reserved.


• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.


• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

• The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

BLT 2.4u

Portions (c) 1993 AT&T, (c) 1993 - 1998 Lucent Technologies, (c) 1994-1998 Sun Microsystems, Inc., and (c) 1987-1993 The Regents of the University of California.

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the names of AT&T, Lucent Technologies Inc., Sun Microsystems, Inc. and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.

THE COPYRIGHT HOLDERS AND OTHER CONTRIBUTORS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR OTHER CONTRIBUTORS BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

CMU-SNMP 1.14

CMU/UCD copyright notice: (BSD like) Copyright 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of California

All Rights Reserved



Scotty 2.8, incrTCL 3.0, [incr TCL] 3.2

Portions Copyright (c) 1987-1994 The Regents of the University of California. Copyright (c) 1994-1995 Sun Microsystems, Inc.


This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.



THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

RESTRICTED RIGHTS: Use, duplication or disclosure by the government is subject to the restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software Clause as DFARS 252.227-7013 and FAR 52.227-19.

Portions Copyright (c) 1993-1998 Lucent Technologies, Inc.

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that the copyright notice and warranty disclaimer appear in supporting documentation, and that the names of Lucent Technologies any of their entities not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

Lucent disclaims all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no event shall Lucent be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortuous action, arising out of or in connection with the use or performance of this software.

UCD SNMP 4.2.5

Portions Copyright 1989, 1991, 1992 by Carnegie Mellon University. Derivative Work - 1996, 1998-2000, Copyright 1996, 1998-2000 The Regents of the University of California All Rights Reserved



Portions Copyright: (c) 2001-2003, Networks Associates Technology, Inc, (c) 2001-2003, Cambridge Broadband Ltd, (c) 2003-2005, Sparta, Inc., (c) 2004, Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications, (c) Fabasoft R&D Software GmbH & Co KG, 2003 [email protected]. All rights reserved.


1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.


3. Neither the names of Networks Associates Technology, Inc, Cambridge Broadband Ltd., Sparta, Inc., Cisco, Inc, Beijing University of Posts and Telecommunications, Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product names, nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

JDOM 1.0

Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved.


1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution.

3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact <request_AT_jdom_DOT_org>.

4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the JDOM Project Management <request_AT_jdom_DOT_org>.

In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or in the software itself an acknowledgement equivalent to the following:

"This product includes software developed by the JDOM Project (http://www.jdom.org/)." Alternatively, the acknowledgment may be graphical using the logos available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Jason Hunter <jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>. For more information on the JDOM Project, please see <http://www.jdom.org/>.

Regex 1.1a

Copyright (C) 1996, 1999 Vassili Bykov. It is provided to the Smalltalk community in hope it will be useful.

1. This license applies to the package as a whole, as well as to any component of it. By performing any of the activities described below, you accept the terms of this agreement.


2. The software is provided free of charge, and ``as is'', in hope that it will be useful, with ABSOLUTELY NO WARRANTY. The entire risk and all responsibility for the use of the software is with you. Under no circumstances the author may be held responsible for loss of data, loss of profit, or any other damage resulting directly or indirectly from the use of the software, even if the damage is caused by defects in the software.

3. You may use this software in any applications you build.

4. You may distribute this software provided that the software documentation and copyright notices are included and intact.

5. You may create and distribute modified versions of the software, such as ports to other Smalltalk dialects or derived work, provided that:

a. any modified version is expressly marked as such and is not misrepresented as the original software;

b. credit is given to the original software in the source code and documentation of the derived work;

c. the copyright notice at the top of this document accompanies copyright notices of any modified version.


Printed in the USA.

IBM®

tivoli ibm wireline component - inpm · the audience for this guide is the tivoli netcool perf...

Documents