Tivoli Netcool Performance Manager 1.3
Wireline Component (Netcool/Proviso 5.2) Document Revision R2E1
Bulk Collector User’s Guide
IBM
Note Before using this information and the product it supports, read the information in Notices on page 39.
Copyright IBM Corp. 1997, 2010 US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Netcool/Proviso Collector Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Purpose of the Netcool/Proviso Bulk Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Netcool/Proviso Architecture with Bulk Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 2: Using the Bulk Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Bulk Collector Custom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 FORMULAPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 PROFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 PROPERTY_TO_STRING_METRIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Operation of the Bulk Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Starting and Stopping the Bulk Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Processing of PvLine Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Discovery and Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Synchronized Inventory Discovery Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 No Inventory Discovery Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Advanced Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Multi-Hour Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Dual Collection and Collector Aliasing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 3: Troubleshooting the Bulk Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Troubleshooting Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Verify Basic Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Verify the Bulk Collector is Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Verify the Bulk Collector Is Not Flow Controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Verify the Bulk Collector Is Not Producing Walkback Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
iii
Contents
Monitoring Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Log File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Working with the Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Common Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Problems With Bulk Collector Operation - Starting, Stopping, Frequent Crashes . . . . . . . . . . . . 24 No Data in Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Unable to Generate Output or Acquire Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Bulk Collector is Stuck in Synchronized Inventory State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Unable to Transfer Inventory Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 File Detection and File Processing Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Input Files Not Detected/Wrong Input Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Unable to Access the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 4: PvLine File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 PvLine File Format Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Rules for Specifying Formats in PvLine Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 PvLine File Header Line Option Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 PvLine File Data Line Field Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 PvLine File Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Examples of Specifying Special Property Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Examples of Specifying Property Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Examples of Specifying Metric Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Sample PvLine File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Additional Copyright Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK 8.3.3 . . . . . . . . . . . . . . . . . . . . 43 SCOTTY Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 BLT 2.4u . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 CMU-SNMP 1.14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Scotty 2.8, incrTCL 3.0, [incr TCL] 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 UCD SNMP 4.2.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 JDOM 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Regex 1.1a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
iv
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Preface
IBM® Tivoli® Netcool® Performance Manager 1.3 is a bundled product consisting of a wireline component (formerly Tivoli Netcool/Proviso) and a wireless component (formerly Tivoli Netcool Performance Manager for Wireless). This guide explains the Netcool/Proviso Bulk Collector and includes information about the Bulk Collector’s architecture, installation, configuration, operation, and troubleshooting. It also includes a discussion of the Netcool/Proviso PvLine file format that is processed by the Bulk Collector.
Audience The audience for this guide is anyone who wants to use the Bulk Collector to collect and process BULK data. To make use of the Bulk Collector, you must install the Netcool/Proviso product suite on an enterprise network. To install Netcool/Proviso successfully, you should have a thorough understanding of the following subjects: •
Basic principles of TCP/IP networks and network management
•
SNMP concepts
•
Administration of the Solaris or AIX operating environment
•
Administration of the Oracle database management system
•
Netcool/Proviso
Organization This guide is organized as follows: •
Chapter 1, Introduction Provides an overview of the Netcool/Proviso Bulk Collector and its architecture.
•
Chapter 2, Using the Bulk Collector Explains how to use the Netcool/Proviso Bulk Collector.
•
Chapter 3, Troubleshooting the Bulk Collector Explains how to troubleshoot the Netcool/Proviso Bulk Collector.
•
Chapter 4, PvLine File Format Explains the PvLine format.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
v
Preface
The Netcool/Proviso Product Suite Netcool/Proviso is made up of the following components: •
Netcool/Proviso DataMart is a set of management, configuration and troubleshooting GUIs that the Netcool/Proviso System Administrator uses to define policies and configuration, as well as verify and troubleshoot operations.
•
Netcool/Proviso DataLoad provides flexible, distributed data collection and data import of SNMP and non-SNMP data to a centralized database.
•
Netcool/Proviso DataChannel aggregates the data collected through Netcool/Proviso DataLoad for use by the Netcool/Proviso DataView reporting functions. It also processes on-line calculations and detects realtime threshold violations.
•
Netcool/Proviso DataView is a reliable application server for on-demand, web-based network reports.
•
Netcool/Proviso Technology Packs extend the Netcool/Proviso system with service-ready reports for network operations, business development, and customer viewing.
The following figure shows the different Netcool/Proviso modules. Figure 1: Netcool/Proviso Modules DataLoad collects network data.
DataChannel computes aggregations and stores data in DataMart.
DataMart provides data management and applications.
DataView produces and manages reports.
Netcool/Proviso 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.htm
vi
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 1: Introduction
This chapter provides an overview of the Netcool/Proviso Bulk Collector and its architecture. The topics are as follows:
Topic
Page
Overview
1
Netcool/Proviso Collector Types
1
Netcool/Proviso Architecture with Bulk Collector
3
Overview The Netcool/Proviso Bulk Collector imports pre-collected network performance statistics into Netcool/Proviso. This chapter begins with a brief discussion of the Netcool/Proviso Bulk collector types and concludes with an architectural overview of Netcool/Proviso modules that includes a discussion of where the Bulk Collector fits into the architecture.
Netcool/Proviso Collector Types Netcool/Proviso provides the following collector types: •
SNMP Collector — Specifies an SNMP Collector that polls network devices using SNMP protocols. Specify this collector type if you plan to install a Netcool/Proviso SNMP technology pack. These technology packs operate in networking environments where the associated devices on which they operate use an SNMP protocol. You would also specify this collector type if you plan to use the Bulk Collector to import files generated by SNMP Collectors on remote networks.
•
Bulk Collector — This type of collector imports data from files (referred to as Bulk input files). The files can have multiple origins, including log files generated by network devices, files generated by SNMP Collectors on remote networks, or files generated by a non-Netcool/Proviso network management database. You configure this collector type if you need to write custom adaptors for new Bulk input file formats. The Bulk Collector does not import data directly from these files. Instead, it imports and processes intermediate files called PvLine files that transform the fields contained in vendor-specific Bulk input files to the Netcool/Proviso model.
•
UBA Bulk Collector — This type of collector imports data from files (referred to as Bulk input files) generated by non-SNMP devices, including the following: — Alcatel 5620 NM — Alcatel 5620 SAM — Cisco CWM
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
1
Chapter 1: Introduction
The Bulk input files that these and other non-SNMP devices generate contain formats that the Bulk Collector is unable to handle. You must configure a UBA Bulk Collector for Netcool/Proviso UBA technology packs. This guide discusses how to use the Bulk Collector.
Purpose of the Netcool/Proviso Bulk Collector You can use the Netcool/Proviso Bulk Collector to process statistics from the following sources: •
Network devices that provide bulk data files.
•
Management stations that collect statistics from the devices using SNMP or some other mechanism.
•
Repositories such as a provisioning database or a trouble-ticket database.
In addition to importing bulk statistics into Netcool/Proviso, the Bulk Collector also includes the following features:
2
•
Coordinates with inventory so that inventory changes are seen close to data time, not wall clock time.
•
Maps bulk entities into their corresponding Netcool/Proviso representation.
•
Manages the allocation of disk space so that the process has sufficient resources to function.
•
Supports an intermediate file format called the Netcool/Proviso PvLine file format that allows customers to write custom adaptors for new Bulk formats. More specifically, the Bulk Collector imports and processes PvLine files that transform the fields contained in vendor-specific Bulk input files to the Netcool/Proviso model.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 1: Introduction
Netcool/Proviso Architecture with Bulk Collector The architecture of Netcool/Proviso consists of a set of pipelines (subchannels) that collect data and use parallelism to optimize performance. Each subchannel takes a time-ordered stream of data for the network resources that are assigned to that subchannel. The Complex Metric Engine (CME) for each subchannel uses formulas to transform this data into meaningful statistics, both raw and aggregate, and to perform threshold processing. Subchannels are fed data from an SNMP Collector, a Bulk Collector, or a UBA Bulk Collector. Figure 2 shows a Netcool/Proviso deployment that uses a Bulk Collector. Figure 2: Netcool/Proviso Deployment with highlighted Bulk Collector DataChannel System
DataBase System LDR.1 DLDR.1
DataLoad Bulk Collector Router 2.1
CME.1.2 sql loader
BCOL.1.2 FTE.1.2
PV_METRIC READ ONLY
Router 2.2 ./import
./datachannel
PV_METRIC R/W
./datachannel
Router n2.
PV_ADMIN
DataMart System inventory
./DMHOME
The Bulk Collector is deployed at the head of a subchannel pipeline. The Bulk Collector processes a stream of PvLine input files that contain data specified in the supported PvLine format, and outputs BOF metric files for the pipeline components downstream. The metric records in a BOF file have already been bound to the appropriate Netcool/Proviso IDs for their associated formulas and sub-elements. If the Bulk Collector is configured to perform resource discovery using the sync_inventory setting for the DISCOVERY_MODE parameter, it outputs inventory files containing resource information for the inventory server. You need to model network resources in the Netcool/Proviso system before statistics can be processed and stored. Part of the Bulk Collector’s responsibility includes discovery of these resources as they are processed. If new resources arrive in the Bulk Collector’s input stream, or if the properties of existing resources change, the Netcool/Proviso model is updated with this new discovery information.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
3
Chapter 1: Introduction
NOTES
4
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 2: Using the Bulk Collector
This chapter explains how to use the Netcool/Proviso Bulk Collector. The topics are as follows:
Topic
Page
Installation and Configuration
5
Bulk Collector Custom Parameters
10
Operation of the Bulk Collector
15
Installation and Configuration The Netcool/Proviso Installation Guide explains how to install the Netcool/Proviso product suite on an enterprise network. The installation guide also describes how to install and configure a Bulk Collector. Table 1 lists typical Bulk Collector configuration parameters specified when installing the Bulk Collector. The table uses Netcool/Proviso pre-4.4.3 and Netcool/Proviso 4.4.3 naming conventions and example parameter values, along with a description of the parameter. See the Netcool/Proviso Installation Guide for more information. On Netcool/Proviso pre-4.4.3, these Bulk Collector configuration parameters are written to the dc.cfg file by the installer. You can add Bulk Collector custom parameters not configured by the installer by manually adding them to the dc.cfg file, which is located in /opt/datachannel/conf, by default. See Bulk Collector Custom Parameters on page 10 for more information. On Netcool/Proviso 4.4.3 systems, these parameters are written to the database by the Topology Editor. You can configure these parameters through the DataChannel component in the Topology Editor. The Topology Editor does not support adding custom parameters to the Bulk Collector. Table 1: Bulk Collector Configuration Parameters (Pre-4.4.3) Parameter Name
4.4.3 Parameter Name
Example Value
Description
GLOBAL.DB_ENVIRONMEN T
DB_ENVIRONMENT
PV
Specifies the SID (system identifier) associated with the DataChannel database. The value entered here must match the SID in the tnsnames.ora file for the database supporting the desired DataChannel installation.
GLOBAL.LOG_PORT
LOG_PORT
25000
Specifies the port number of the server on which the log server will listen for UDP messages. The default port number is 25000.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
5
Chapter 2: Using the Bulk Collector
(Pre-4.4.3) Parameter Name
4.4.3 Parameter Name
Example Value
Description
GLOBAL.LOG_SERVER
LOG_SERVER
CME5
Specifies the host name of the server on which the log server will run.
GLOBAL.ORB _NAMESERVICE_HOST
ORB_NAMESERVICE _HOST
CME5
Specifies the host name for the CORBA name server.
GLOBAL.ORB _NAMESERVICE_PORT
ORB_NAMESERVICE _PORT
45107
Specifies the port number for the CORBA name server. The default port number is 45107.
BCOL.2.3.3002_SERVIC E_PORT
SERVICE_PORT
0
Specifies the port to carry the 3002 protocol for this Bulk collector. This port number is used for internal communication between the Bulk Collector’s programs. A value of 0 allows this port to be dynamically assigned.
6
BCOL.2.3.COLLECTOR _ALIAS
COLLECTOR_ALIAS
3
Allows DataChannel applications that handle inventory and metrics operations to process inventory and/or metrics for Netcool/Proviso elements owned by other collectors. Typically, this parameter is used in dual collection with an SNMP Collector. Specify the SNMP Collector number or other Bulk Collector number that was configured.
BCOL.2.3.DB _PASSWORD
DB_PASSWORD
AAAC
Specifies the database password for the related DB_USERNAME. This password is stored encrypted.
BCOL.2.3.DB _USERNAME
DB_USERNAME
PV_COLL
Specifies the database user name for the related DB_PASSWORD. This is the database user name used when the Bulk Collector connects to the database. Ensure that the specified user has the appropriate permissions.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 2: Using the Bulk Collector
(Pre-4.4.3) Parameter Name
4.4.3 Parameter Name
Example Value
Description
BCOL.2.3.DISCOVERY _MODE
DISCOVERY_MODE
sync_inventory
Specifies whether Bulk inventory is enabled: •
no_inventory — The Bulk Collector processes hourly data in time order but inventory discovery and synchronization do not occur.
•
sync_inventory — The Bulk Collector processes hourly data in time order while discovering resources. For each set of hour data processed, the Bulk Collector generates inventory files and sends them to the DataMart Inventory directory.
BCOL.2.3.DISCOVERY _PERIOD_IN_HOURS
DISCOVERY_PERIOD _IN_HOURS
4
Specifies the number of hours (the discovery period) the Bulk Collector will collect new resources to process for inventory. The appropriate value depends on how long inventory takes to run. All metric processing in the Bulk Collector is halted from the time inventory is triggered until inventory completes.
BCOL.2.3.DUAL _LOGGING
DUAL_LOGGING
true
By default (false), DataChannel components send log entries only to a log file (proviso.log) on the local file system. You can enable dual logging by specifying the value true. Dual logging instructs the DataChannel component to send messages to the local log file and to a standard log server on the network.
BCOL.2.3.FC_FSLL
FC_FSLL
150000000
Specifies the number of bytes representing the lowest amount of available disk space to keep available for the Bulk Collector. When the file system that the Bulk Collector is running on reaches this number or less of available disk space, flow control is initiated on this Bulk Collector.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
7
Chapter 2: Using the Bulk Collector
(Pre-4.4.3) Parameter Name
4.4.3 Parameter Name
Example Value
Description
BCOL.2.3.FC_QUOTA
FC_QUOTA
1000000000
Specifies the largest amount of space, in bytes, that the Bulk Collector should consume before becoming flow controlled.
BCOL.2.3.INPUT _DIRECTORIES
INPUT_DIRECTORIES
/opt/bulk/input
Full path to the directory or directories on the Collector server where you want to store the bulk input files that the Collector gathers from the device or management stations. This directory is also where the PvLine intermediate files are stored. The PvLine files transform the fields contained in the collected bulk input file to the Netcool/Proviso model. See Chapter 4, PvLine File Format for more information.
/routera, /opt/bulk/input /routerb
The Bulk Collector looks in these directories for the PvLine files to process. Keep the input directory structure separate from the directory structure created by the Bulk Collector installation. For example, do not place the input files in the Bulk Collector’s do subdirectory. You can create separate directories to store different types of bulk-loaded files. For example, you can create one directory to store the bulk files from router A and another directory to store the bulk files from router B. Each of these directories would contain the associated PvLine files. Separate more than one directory path by commas. You must specify a directory location that has read/write permissions for the currently logged in user, pvuser.
8
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 2: Using the Bulk Collector
(Pre-4.4.3) Parameter Name
4.4.3 Parameter Name
Example Value
Description
BCOL.2.3.INVENTORY_F TP_DIRECTORY
INVENTORY_FTP_DIRE CTORY
/opt/datamart /importExportBulk
Directory on the DataMart server where the generated inventory files are to be placed. An inventory file is automatically generated and appears in DataView’s Inventory Tool window. A directory in the following format is created when you install DataMart: /DataMart_Home /importExportBulk Using the default installation directory, this is: /opt/datamart/import ExportBulk You must specify a directory location that has read/write permissions for the currently logged in user, pvuser.
BCOL.2.3.INVENTORY_F TP_HOSTNAME
INVENTORY_FTP_HOST NAME
CME3
Specifies the host computer or server where the inventory bulk process will run. The Bulk Collector pushes the inventory files to this computer or server.
BCOL.2.3.INVENTORY_F TP_PASSWORD
INVENTORY_FTP_PASS WORD
DDDJCHCGCCCN
Specifies the ftp password for the host computer or server from which the inventory files will be retrieved. This password is encrypted.
BCOL.2.3.INVENTORY_F TP_PORT
INVENTORY_FTP_PORT
21
Specifies the ftp port number for the host computer or server from which the inventory files will be retrieved.
BCOL.2.3.INVENTORY_F TP_USERNAME
INVENTORY_FTP_USER NAME
cmedev
Specifies the ftp username for the host computer or server from which the inventory files will be retrieved.
BCOL.2.3.MAX_LOGS
MAX_LOGS
3
Specifies the maximum number of days to retain historical logs. Normally, logs are rolled every 24 hours. Specify a positive non-zero integer. The default is 3 days.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
9
Chapter 2: Using the Bulk Collector
(Pre-4.4.3) Parameter Name
4.4.3 Parameter Name
Example Value
Description
BCOL.2.3.OUTPUT_FORM AT
OUTPUT_FORMAT
BOF
Specifies the format of the files to be generated by this Bulk Collector. You should specify BOF as the output format.
BCOL.2.3.POLL_INTERV AL
POLL_INTERVAL
60
Specifies the time interval, in seconds, between successive polls of the different directories (input, do, and done). These polls are performed by the different DataChannel applications (including the Bulk Collector). Decreasing the value increases the frequency of the polling. More frequent polling introduces overhead to execute the poll, but more timely data is provided.
BCOL.2.3.ROOT _DIRECTORY
ROOT_DIRECTORY
/opt/datachannel/
Directory under which the Bulk Collector subsystem directory will be created.
BCOL.2.3.SSH_COMMAND
SSH_COMMAND
ssh
Specifies the location (full path) of the ssh executable (for sftp) on this host computer or server. An example of a full directory path is /usr/local/bin/ssh. The location of the ssh executable must be specified when Secure File Transfer is used during installation or file transfer.
BCOL.2.3.USE_SECURE _FILE_TRANSFER
USE_SECURE_FILE _TRANSFER
false
Specifies whether FTP (File Transfer Protocol) or SFTP (secure FTP) is used. To use FTP, specify the value false. Otherwise, to use SFTP, specify the value true.
Bulk Collector Custom Parameters You can manually add Bulk Collector custom parameters that are not configured by the installer as follows:
10
•
Pre-4.4.3 — You add these custom parameters to the dc.cfg file (located in /opt/datachannel/bin, by default) after you have installed your Netcool/Proviso environment, then copy the file to all machines in the DataChannel. Make a backup of these customized files when reinstalling or modifying the installation as the installer overwrites the settings, and you will need to reinsert these settings for redistribution.
•
4.4.3 — The Topology Editor does not support adding custom parameters to the Bulk Collector.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 2: Using the Bulk Collector
Table 2 provides the list of Bulk Collector custom parameters you can manually add to the dc.cfg file (Netcool/Proviso pre-4.4.3 only). Table 2: Bulk Collector Custom Parameters Parameter Name
Reference Page
FORMULAPATH
FORMULAPATH on page 12
PROFILE
PROFILE on page 13
PROPERTY_TO_STRING_METRIC
PROPERTY_TO_STRING_METRIC on page 14
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
11
Chapter 2: Using the Bulk Collector
FORMULAPATH dc.cfg File Syntax (Pre-4.4.3 only) BCOL...PVLINE.FORMULAPATH=
Arguments (Pre-4.4.3 only) Replace with the channel number that was configured for this Bulk Collector. This channel number appears in the dc.cfg file. (Pre-443 only) Replace with the Bulk Collector number that was specified during installation. This collector number appears in the dc.cfg file.
Specifies the formula path to use for sub-elements discovered from the specified file type.
Description The FORMULAPATH parameter tells the DataChannel Bulk Collector application the formula path to use for subelements discovered from the specified file type. This works for all file type formats except for PvLine. The PvLine file format uses a header line option to set the formula path. See PvLine File Header Line Option Syntax on page 28 for more information.
Notes This custom parameter should never be used with the PvLine file format. It is documented for historical reasons, specifically for users who used a file format other than PvLine. The only file format supported by the Bulk Collector is PvLine. The Topology Editor does not support adding custom parameters to the Bulk Collector.
12
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 2: Using the Bulk Collector
PROFILE dc.cfg File Syntax (Pre-4.4.3 only) BCOL...PVLINE.PROFILE=
Arguments (Pre-4.4.3 only) Replace with the channel number that was configured for this Bulk Collector. This channel number appears in the dc.cfg file. (Pre-443 only) Replace with the Bulk Collector number that was specified during installation. This collector number appears in the dc.cfg file.
Specifies the name of the profile to use for elements discovered from the specified file type.
Description The PROFILE parameter tells the DataChannel Bulk Collector application the name of the profile to use for elements discovered from the specified file type. The PvLine file format uses a default profile as described in PvLine File Format Values on page 27.
Notes This custom parameter should never be used with the PvLine file format. It is documented for historical reasons, specifically for users who used a file format other than PvLine. The only file format supported by the Bulk Collector is PvLine. The Topology Editor does not support adding custom parameters to the Bulk Collector.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
13
Chapter 2: Using the Bulk Collector
PROPERTY_TO_STRING_METRIC dc.cfg File Syntax (Pre-4.4.3 only) BCOL...PROPERTY_TO_STRING_METRIC.=
Arguments (Pre-4.4.3 only) Replace with the channel number that was configured for this Bulk Collector. This channel number appears in the dc.cfg file. (Pre-443 only) Replace with the Bulk Collector number that was specified during installation. This collector number appears in the dc.cfg file.
Specifies the name of the Netcool/Proviso property to map to an associated string metric specified in .
Specifies the name of the string metric to which the Netcool/Proviso property specified in is mapped.
Description The PROPERTY_TO_STRING_METRIC parameter maps the specified Netcool/Proviso property to an associated string metric. Use this custom parameter to route property values as input metrics to the CME. Typically, you specify one or more instances of the PROPERTY_TO_STRING_METRIC parameter for those situations where real-time value changes in property values (for example, the ifSpeed property) are needed.
Notes This custom parameter should never be used with the PvLine file format. It is documented for historical reasons, specifically for users who used a file format other than PvLine. The only file format supported by the Bulk Collector is PvLine. The Topology Editor does not support adding custom parameters to the Bulk Collector.
14
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 2: Using the Bulk Collector
Operation of the Bulk Collector After you install and configure the Bulk Collector, the collector needs to be started, and you need to ensure that the expected Bulk input files arrive at the configured input directories. The following sections describe topics related to the operation of the Bulk Collector, including: •
Starting and Stopping the Bulk Collector
•
Processing of PvLine files
•
Discovery and inventory
•
Advanced Bulk Collector Operation
Starting and Stopping the Bulk Collector You can use the dccmd command for basic component management and to find the Bulk Collector’s current status. To use the dccmd command: 1.
On the DataChannel host, log in as the component user, such as pvuser.
2.
Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default) using the following command: $ cd /opt/datachannel/bin
3.
Do one of the following: 3-a. To start the Bulk Collector, use the following dccmd command: $ ./dccmd -action start -pattern BCOL..
where: — — Replace with the channel number that was configured for this Bulk Collector. This channel number appears in the dc.cfg file. — — Replace with the Bulk Collector number that was specified during installation. This collector number appears in the dc.cfg file. 3-b. To stop the Bulk Collector, use the following dccmd command: $ ./dccmd -action stop -pattern BCOL..
3-c. To view Bulk Collector status, use the following dccmd command: $ ./dccmd -action status -pattern BCOL..
Processing of PvLine Files After the Bulk Collector starts, it detects and processes any PvLine files placed into its configured input directory. A PvLine file is an intermediate file format that transforms the fields contained in vendor-specific Bulk input files to the Netcool/Proviso model. An administrator must enable the external transfer of the PvLine and vendorspecific Bulk input files into the input directory to begin this file processing. See Chapter 4, PvLine File Format for details on PvLine file formats. In order to output useful metrics, you must define the resources and formulas in the Netcool/Proviso model by specifying PvLine files.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
15
Chapter 2: Using the Bulk Collector
Resources are either discovered and processed by inventory as described in the next section, or need to be imported using resmgr.
Discovery and Inventory The Bulk Collector supports two different discovery modes: synchronized inventory or no inventory. The configuration setting for the DISCOVERY_MODE Bulk Collector parameter determines the discovery mode: •
sync_inventory for synchronized discovery mode
•
no_inventory for no inventory discovery mode.
Each of these modes is discussed in the following sections.
Synchronized Inventory Discovery Mode The Bulk Collector processes the input files in time order, hour by hour, while discovering resources. The Bulk Collector generates inventory files and delivers them to the inventory server, as configured during installation. At the end of a specified period of time, known as the discovery window, the Bulk Collector stops processing input data and signals the inventory server to launch inventory. The configuration setting for the DISCOVERY_PERIOD_IN_HOURS Bulk Collector parameter determines the length of the discovery window. At the end of the each discovery window, inventory processing is activated and the Bulk Collector blocks further resource processing. Inventory processing consists of resource synchronization and auto-grouping. The Bulk Collector blocks processing until the inventory completes, whether inventory is successful or not. The discovery window defines a discovery delay period. For new resources that appear in a particular discovery window, none of the metrics for this new resource will be processed until inventory is successfully run at the end of the discovery window. Once the inventory of this new resource occurs then metrics will be able to be processed. It is important to understand that this delay exists and that data will not appear immediately. To minimize any potential delays, ensure the crontab entry for the pollinv program is set to run every 1 to 5 minutes to increase the responsiveness of the throughput of your system. Inventory processing only occurs if the Bulk Collector has signalled inventory to start. If the crontab entries are left on an hourly schedule, then there will be increased latency in the subchannel as the collector waits up to an hour before running inventory. See the Netcool/Proviso Installation Guide for information about adding watchdog scripts to crontab.
No Inventory Discovery Mode The Bulk Collector processes the input files in time order, without resource discovery and without synchronization of the inventory that occurs. The Bulk Collector responds to 3002 events for reload configuration commands in order to resynchronize external resource changes. The delivery of data files to the CME does is not interrupted.
Advanced Operation This section describes the following advanced operation features:
16
•
Multi-hour files
•
Dual collection and collector aliasing
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 2: Using the Bulk Collector
Multi-Hour Files A Bulk Collector can process PvLine files that contain multiple hours of data. The Bulk Collector processes each hour across all pending PvLine files before advancing to the next hour. It processes PvLine files hour-by-hour in order to maintain correct discovery and to deliver timely metrics for each hour. To support hour-by-hour processing, the Bulk Collector supports partial processing of each PvLine file. A Bulk Collector that processes multiple PvLine files, each of which has multiple hours of data, processes the first hour for each file, then the second hour for each file, and so on. This processing generates the BOF metric files and the inventory files for each PvLine file hourly chunk. When running in synchronized inventory mode, the end of the discovery window can occur while in the middle of a multi-hour PvLine file. The Bulk Collector causes inventory to run and blocks processing until finished. When inventory completes, the Bulk Collector advances to process the following hour.
Dual Collection and Collector Aliasing You can set a collector alias in both the Bulk Collector and the CME to enable metric collection from two different subchannels. When a subchannel (Bulk Collector and CME) has an aliased collector number, the components load the meta-data for the alias collector number, rather than the management collector number. The Bulk Collector can process metrics for resources assigned to this alias collector. Collector aliasing can be for dual collection between an SNMP subchannel and a Bulk subchannel, where the Bulk Collector is aliased to the SNMP Collector number. You also need to configure the Bulk Collector to no inventory discovery mode and all discovery needs to occur through the SNMP collector.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
17
Chapter 2: Using the Bulk Collector
NOTES
18
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 3: Troubleshooting the Bulk Collector
This chapter explains how to troubleshoot the Netcool/Proviso Bulk Collector. The topics are as follows:
Topic
Page
Overview
19
Troubleshooting Tools
19
Verify Basic Operation
19
Monitoring Log Messages
21
Common Problems
24
Overview When beginning to troubleshoot a problem with Netcool/Proviso, it is often best to begin the investigation with the Bulk Collector because it is the most upstream component in the data pipeline. For example, the time required to investigate the type of generic report that reads Unable to see statistics for these subelements, can often be reduced by troubleshooting the Bulk Collector first. The following sections provide a methodology and best practices for troubleshooting the Bulk Collector.
Troubleshooting Tools To troubleshoot the Bulk Collector, you can use the following items as diagnostic tools: •
dccmd commands
•
proviso.log file
•
BCOL subsystem directory
•
DataMart inventory directory
•
resmgr commands
Verify Basic Operation The first step in troubleshooting the Bulk Collector is to perform some basic operations to verify if the problem resides within the Bulk Collector:
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
19
Chapter 3: Troubleshooting the Bulk Collector
•
Verify that the Bulk Collector is running.
•
Verify that the Bulk Collector is not flow controlled.
•
Verify that the Bulk Collector is not producing walkback files.
Verify the Bulk Collector is Running To verify that the Bulk Collector is running: 1.
On the DataChannel host where the Channel Manager and Log Server are running, log in as the component user, such as pvuser.
2.
Change your working directory to the DataChannel bin directory (/opt/datachannel/bin by default) using the following command: $ cd /opt/datachannel/bin
3.
To view Bulk Collector status, use the following dccmd command: $ ./dccmd -action status -pattern BCOL..
where: — — Replace with the channel number that was configured for this Bulk Collector. This channel number appears in the dc.cfg file. — — Replace with the Bulk Collector number that was specified during installation. This collector number appears in the dc.cfg file. The return information should indicate that the Bulk Collector is running. If the Bulk collector is not running, start the collector using the following dccmd command: $ ./dccmd -action start -pattern BCOL..
Verify the Bulk Collector Is Not Flow Controlled To verify that the Bulk Collector is not flow controlled: 1.
On the DataChannel host where the Channel Manager and Log Server are running, log in as the component user, such as pvuser.
2.
Change your working directory to the DataChannel log directory (/opt/datachannel/log by default) using the following command: $ cd /opt/datachannel/log
3.
Use the grep command to determine if the Bulk collector is in a flow controlled state:
grep BCOL.. proviso.log | grep FLOW_CTRL_STATE
where: — — Replace with the channel number that was configured for this Bulk Collector. This channel number appears in the dc.cfg file. — — Replace with the Bulk Collector number that was specified during installation. This collector number appears in the dc.cfg file. The return information will display the changes in flow control for the day. The Bulk Collector goes through flow control full states that should clear themselves as processing continues (for example, you should see the FLOW_CTRL_STATE go through periods of full state, then release to an uncongested state).
20
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 3: Troubleshooting the Bulk Collector
If the Bulk Collector is in a flow control state, monitor the rest of that particular channel and wait for the LDR to complete work, which will open up resources for the sub-channel to continue processing.
Verify the Bulk Collector Is Not Producing Walkback Files Typically, walkback files have names that start with walkback and with a .log extension. To verify that the Bulk collector is not producing walkback files: 1. 2.
On the DataChannel host where the Bulk Collector is running, log in as the component user, such as
pvuser.
Change your working directory to the DataChannel log directory (/opt/datachannel/log by default) using the following command: $ cd /opt/datachannel/log
3.
If there are walkback files present in the state directory, something is causing the Bulk Collector to crash. The best course of action is to send the logs and walkback files to IBM support.
Monitoring Log Messages This section contains information concerning how to work with the proviso.log file.
Log File Format []
where: •
is a formatted date string YYYY.MM.DD-hh.mm.ss.
•
indicates the program that made the log file entry (for example, CMGR for Channel Manager).
•
can be one of the following:
• I – Informational. • W – Warning. • F – Failure. • 1 – Debug level 1. • 2 – Debug level 2. • 3 – Debug level 3. •
is a registered msg code for fatal and warning log messages.
•
indicates the basic type of the message.
•
is an additional text message.
Working with the Log File The proviso.log file is a text file that can be searched using the grep command.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
21
Chapter 3: Troubleshooting the Bulk Collector
1.
On the DataChannel host where the Channel Manager and Log Server are running, log in as the component user, such as pvuser.
2.
Change your working directory to the DataChannel log directory (/opt/datachannel/log by default) using the following command: $ cd /opt/datachannel/log
3.
Use the grep command to search the DataChannel log file. For example: 3-a. To check for fatal errors, use a grep command similar to the following: grep BCOL.. proviso.log | grep –w F
This action will return any messages for the specified Bulk Collector that have an F (failure) severity. 3-b. To check for warnings, use a grep command similar to the following: grep BCOL.. proviso.log | grep –w W
This action will return any messages for the specified Bulk Collector that have a W (warning) severity. 3-c. To check for a specific log message, use a grep command similar to the following: grep BCOL.. proviso.log | grep
This action will return any instances of the log message for the specified Bulk Collector.
Log Messages Note: For more information concerning log files, see the Netcool/Proviso Technical Note: Netcool/Proviso Logs.
22
Severity
Message
Description
I
APPSTARTING
Application is starting.
I
APPSTARTED
Application is started – finished initializing.
I
APPSTOPPING
Application is stopping.
I
DETECTED_FILE
A new input file has been detected. Prints the filename.
I
INVENTORY_EXIT_CODE
Synchronized Inventory finished with a return code.
I
FLOW_CTRL_SKIP
80% of the quota is filled. Stop accepting input files.
I
CURRENT_HOUR
What is the current data hour.
I
DISCOVERY_WINDOW
What is the current discovery window. At the end of the window, run inventory.
I
3002EVENT
3002 event received.
I
RESYNC
Domain model is being resynced.
I
GC
GC statistics.
W
FILE_ERROR
A file read error occurred.
W
BAD_UOW_PROCESS
Unit Of Work processing failed.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 3: Troubleshooting the Bulk Collector
Severity
Message
Description
W
BAD_DESCRIPTOR
Descriptor for the input bulk file is corrupted.
W
BAD_DATAFILE
Entire file is in the wrong format or a severe corruption/error in the format is found.
W
METADATA_ERROR
A metadata failure occurred. There is a problem with the meta-model, in memory, or a sql error occurred.
W
BAD_TYPE
Field type was indeterminate.
W
EMPTY_FILE
File had no data.
W
MISSING_ELEMENT_NAME
No element name was extracted.
W
NO_TIMESTAMP
Timestamp is missing.
W
FAILINVENTORYSEND
An FTP operation failed.
W
FAILINVENTORYINIT
When establishing the FTP connection, for inventory.
W
BAD_DATALINE
A single dataline is invalid for some reason.
W
BAD_FILE
Entire file is in the wrong format or a severe corruption/error in the format is found.
W
BAD_ELEMENT
Initial element name extraction failed.
W
BAD_TIMESTAMP
Initial timestamp extraction failed.
W
BAD_DETECTION
Auto-detection failed.
W
BAD_SCHEMA
Schema is not valid.
W
BAD_TOKEN
When extracting data fields, based on a schema, a bad token was found.
1
EXSTATUSCHANGE
Extended status changed. This reports the bulk processor state in sync_inventory mode.
1
STATUSCHANGE
Normal status change.
1
PROCESS_UOW_BEGIN
Processing next hourly file chunk of type bulkfiletype (Unit Of Work).
1
PROCESS_UOW_COMMIT
Flushing metrics and metadata.
1
PROCESS_UOW_END
nnnn metrics in ssss s (tttt metrics/minute)
1
MEM_STATS
Statistics about memory usage.
1
REALTIME_HOUR_PERF
Statistics averaged over a wall clock hour ''
1
DATACLOCK_HOUR_PERF
Statistics averaged over a data hour ‘’
1
DISCOVERY_WINDOW_PERF_SUMMA RY
Statistics averaged over the discovery window ‘’
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
23
Chapter 3: Troubleshooting the Bulk Collector
Severity
Message
Description
1
FLOW_CTRL_STATE
Periodic reporting of the Flow control state.
1
FLOW_CTRL_ERROR
A flow control error situation occurred. Report the error.
1
METADATA_LOAD
Metadata is being loaded.
1
METADATA_SUMMARY
Load statistics summary.
1
MEM_POLICY
Report the installed Memory Policy.
1
FORK
Fork an internal Process.
1
SHUTDOWN
Shutting down the component.
2
DELETING_UOW
Occurs in a severe error situation, when parsing.
2
ROLLBACK_TRANSACTION
Also occurs in a severe error situation, while parsing.
3
FM_BEGIN_DISK_USAGE
Start calculating disk usage.
3
FM_END_DISK_USAGE
Stop calculating disk usage – output stats.
Common Problems This section contains information concerning problems that can commonly affect the Bulk Collector.
Problems With Bulk Collector Operation - Starting, Stopping, Frequent Crashes The proviso.log file contains messages about problems that occur. You can use the grep command to search the log for fatal log messages, as described in Working with the Log File on page 21, and you can check for walkback files as described in Verify the Bulk Collector Is Not Producing Walkback Files on page 21. If you experience a problem and cannot find a resolution, contact IBM support.
No Data in Reports There can be many reasons why data may not be appearing in reports. The cause of the problem can be anywhere in the processing pipeline and can occur for one or more of many different reasons. The potential sources of Bulk Collector-related problems include: •
The Bulk Collector is blocked by inventory.
•
The Bulk Collector input is undetected, corrupted, or not available in the configured input directory.
•
The subchannel is delayed or is flow controlled.
•
The resources are undefined in the database.
•
The resources are defined in the future.
•
The formulas are undefined in the database.
•
The formulas are defined in the future.
To troubleshoot this type of issue, you must first locate where the problem is occurring. For example:
24
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 3: Troubleshooting the Bulk Collector
•
Is the problem with the Bulk Collector, or is the problem further downstream?
•
Do the log messages for the Bulk Collector show that metrics are being output? To check for metric output, use the grep command on the log file to search for PROCESS_UOW_END. If metric output is occurring, check whether the issue is downstream or if specific metrics are missing. You can check for the contents of the BOF output files with the bofdump tool and search for appropriate resource IDS and metric IDs.
•
The subchannel might be blocked by inventory. Ensure that the Bulk Collector is not in synchronized inventory mode (see Synchronized Inventory Discovery Mode on page 16 for more information). If it is, check how well pollprofile is running and examine the inventory logs. For metadata verification, use resmgr to verify that a candidate sub-element and a formula from the report are defined in the DataMart. Verify that their historical dates are not in the subchannel’s future.
Unable to Generate Output or Acquire Files This issue is most frequently the result of bad directory permissions or ownership within the BCOL subsystem directory. Also, a problem could exist with the permissions or ownership of the input directories. Examine each of these directories and make the appropriate changes. The Bulk Collector examines the /proc directories and examines open file descriptors to determine if an existing process is manipulating the file in question. Both the processes putting files into the input directory as well as the Bulk Collector process must be owned by the same user. Otherwise, the Bulk Collector process doesn't have permission to examine the open file descriptors.
Bulk Collector is Stuck in Synchronized Inventory State Synchronized inventory processing can take significant time if a large number of resources are assigned to a particular Bulk Collector. A processing time of two or more hours is not unusual with large deployments; however, it is still possible that inventory could get stuck or fail to notify the Bulk Collector to unblock. The possible causes and solutions for this type of issue include: •
A stale database lock exists. To solve this issue, use the DataMart Status tool to remove stale locks. See the Netcool/Proviso DataMart Operation Guide for information on how to use the DataMart Status tool.
•
Bad directory permissions exist in the DataMart importExportBulk directory. To solve this issue, verify that the permissions for this directory are correct.
•
Inventory processing issue. To determine if this is the source of the problem, examine the DataMart logs, and review the datamart implementation to find out why the inventory files are not being processed. Note: A running pollprofile might crash and leave an application lock in the database. Use the DataMart Status tool to remove the locks.
Unable to Transfer Inventory Files If the Bulk Collector cannot transfer inventory files, then the file transfer configuration is incorrect. Investigate the file transfer configuration as well as the target DataMart machine for the correct configuration.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
25
Chapter 3: Troubleshooting the Bulk Collector
File Detection and File Processing Errors This type of issue might be caused by corrupted files being submitted to the Bulk Collector, or the files might be in an unsupported format. Analyze the Bulk input files to ensure that they adhere to the correct format.
Input Files Not Detected/Wrong Input Directories If input files are not being detected, examine the Bulk Collector configuration and use the grep command to search the proviso.log file for detection issues. For example, use the grep command to search for each of the warnings listed in Log Messages on page 22.
Unable to Access the Database If there are problems connecting to the database, the possible reasons include: •
The configuration settings for the database username and password are incorrect.
•
The Oracle client is not configured correctly.
•
The network is disconnected (in some deployments, this is expected).
To determine the source of the problem, you must examine the system connectivity to the database and verify the Netcool/Proviso configuration.
26
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 4: PvLine File Format
This chapter explains the PvLine file format. The topics are as follows:
Topic
Page
Overview
27
PvLine File Format Values
27
Rules for Specifying Formats in PvLine Files
28
PvLine File Header Line Option Syntax
28
PvLine File Data Line Field Syntax
30
PvLine File Examples
31
Overview The Netcool/Proviso Bulk Collector supports an intermediate file format, called PvLine, that transforms the fields contained in vendor-specific Bulk input files to the Netcool/Proviso model. The PvLine file format allows for the passing of information to the Bulk Collector so that other downstream processes (such as the CME) can handle the data manipulation and interaction with other Netcool/Proviso components. The PvLine file requires you to define, using specific option and field syntax, header lines and a series of data lines. This chapter describes the PvLine file format.
PvLine File Format Values Table 3 identifies values for specific characteristics associated with the PvLine file format. Table 3: PvLine File Format Values Format
Default Value
Format name
Netcool/Proviso PV-Line
Format abbreviation
PVLINE
File name
Typically, specified as .pvline
File version
3.0
Vendor
IBM
Format parser type
Resource block parser
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
27
Chapter 4: PvLine File Format
Format
Default Value
Default formula path
empty string
Default family
‘bulk’
Default profile
‘bulk_’ where: is the Bulk Collector number
Rules for Specifying Formats in PvLine Files Table 4 summarizes the rules for specifying header and data lines in PvLine files. Table 4: PvLine File Format Rules Rule
Description
Example
First line
The first line of a PvLine file must begin with the string Type Both.
Type Both . . . Header lines . . . Data lines
Comments
Specify comments in PvLine files by starting the line with a # (pound sign) character. The Bulk Collector ignores any line that begin with a # character.
# Setting header options
Fields in the PvLine file data line
For each data line in the PvLine file, you must specify all seven fields. Separate each field with the | character. Spaces before and after the separation character are optional. The Bulk Collector removes any leading or trailing spaces from each field after analyzing the PvLine file. Typically, you would implement a script to populate PvLine files with the appropriate syntax and contents.
field 1|field2|field3|field4||field6|field7
Note: The Instance field (field 5) is not used, but must be specified with a blank entry.
PvLine File Header Line Option Syntax The PvLine file header line option syntax is as follows: # PvLine file header line format specification syntax
28
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 4: PvLine File Format
# TYPE Both # OPTION:TYPE=Line # OPTION:PVMVersion=3.0 # OPTION:Element= # OPTION:FormulaPath= # OPTION:FormulaPath= # OPTION:TimeOffset=
Table 5 describes each PvLine file header line option syntax. Table 5: Descriptions for PvLine File Header Line Option Syntax Option Syntax
Description
OPTION:TYPE=Line
Specifies the file format associated with PvLine. The value Line indicates that this file format is the complete ASCII format.
OPTION:PVMVersion=3.0
Specifies the import file version to be recognized by the Bulk Collector. Version 3.0 is the only version that works with the Bulk Collector.
OPTION:Element=
Sets the name of the element to associate with the data records specified in subsequent data lines in the PvLine file. The Bulk Collector assigns the data metrics to the resource specified in the targetname field in the data line. See Table 6 on page 30 for more information on the targetname field. Note: The element name can be changed within a single PvLine file depending on the resources being reported. See Sample PvLine File on page 36 for examples.
OPTION:FormulaPath=
Sets the default formula path. This option provides a space saving mechanism for setting the default formula path. The Bulk Collector prepends the specified path to all metric names, for metric type data lines. If you do not specify this option, the default formula path is the empty string.
OPTION:TimeOffset=
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Sets the local timezone in which PvLine files are generated. By default, the offset is 0 (zero), which means timestamps are in Coordinated Universal Time (UTC).
29
Chapter 4: PvLine File Format
PvLine File Data Line Field Syntax The PvLine file consists of multiple data lines, where each line consists of seven fields. Each line uses the following field syntax: date|metric/propertyname|targettype|targetname|Instance|valuetype|value
Table 6 describes the syntax for each field in the PvLine file data line. See PvLine File Examples on page 31 for a sample PvLine file. Table 6: Descriptions for PvLine File Data Line Field Syntax Field Position
Field Item
Description
Field 1
date
Specifies the date in Greenwich Mean Time (GMT). The letter G must precede the date. The date format must be specified as follows: Gyyy/mm/dd hh:mm:ss The following example shows a valid date: G2009/06/02 23:30:00 The Bulk Collector outputs timestamps in GMT. More specifically, the Bulk Collector converts the timestamp to GMT by adding the time offset.
Field 2
metric/propertyname
Specifies the metric or property name to use when the import routine processes the value supplied in the value field (field 7). If a metric name is supplied: •
The metric name maps to the fully qualified bulk collection formula name, which includes its parent group name. A leading ~ does not work. Example: AP~Specific~Bulk~(device)~Inbound Errors.
You can use the OPTION:FormulaPath PvLine file header option to set a PvLine file-based default for this formula path. See PvLine File Header Line Option Syntax on page 28 for more information. •
The valuetype field (field 6) must be set to type float or type string.
If a property name is supplied: •
The valuetype field (field 6) must be set to type property or type inventory.
If the valuetype field (field 6) is set to type inventory, then field 2 must be set to one of the following strings:
30
•
Invariant
•
Instance
•
Label
•
State
•
Family
•
NodeType
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 4: PvLine File Format
Field Position
Field Item
Description
Field 3
targettype
Specifies one of the following strings: •
alias — Indicates that the target type is a sub-element. If targettype is a sub-element, then targetname (field 4) specifies the name of this sub-element.
•
host — Indicates that the target type is an element. If targettype is an element, then targetname (field 4) specifies the name of this element.
Note: The element name can also be set using the OPTION:Element PvLine file header line option. Field 4
targetname
Specifies the name used to uniquely identify the resource. The import program will use this name as the sub-element name and will associate it with the element identified in the OPTION:Element PvLine file header line option. See PvLine File Header Line Option Syntax on page 28 for more information.
Field 5
Instance
This field is not used, but must be specified with a blank entry. field 1|field2|field3|field4||field6|field7
Field 6
valuetype
Specifies one of the following ASCII strings: •
float — Used to specify a numeric value: floating point, short integer, long integer, exponents, and rolling counters. Specifying float in this field tells the import program to use the name specified in the metric/propertyname field (field 2) as the metric name.
Note: Specific formulas can be used in the CME to identify metrics that need to be treated as rolling counters. The CME will handle all processing required to accurately calculate delta values for these metrics. •
string — Used to specify a string metric that is passed to the CME. The string metric can be used in CME formulas as part of a calculation to output either a metric or a property.
•
property — Used to specify a character string that tells the import program to use the name specified in the metric/propertyname field (field 2) as the property name. Properties are typically used to group
resources into logical groups for reporting purposes. Examples of properties include linkSpeed, location, customer, and so forth.
•
Field 7
value
inventory — Used to identify special properties that must be handled differently from other properties by the inventory process. If this field is set to inventory, then the metric/propertyname field (field 2) must be set to one of these values: Invariant, Instance, Label, State, Family, or NodeType.
Specifies a numeric or string value that is associated with the metric or property name specified in the metric/propertyname field (field 2) and the valuetype field (field 6).
PvLine File Examples The following sections provides examples of PvLine header and data line entries:
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
31
Chapter 4: PvLine File Format
•
Examples of Specifying Special Property Names
•
Examples of Specifying Property Names
•
Examples of Specifying Metric Names
•
Sample PvLine File
Examples of Specifying Special Property Names The following example shows how to specify special property names. The example also includes PvLine header line options. The numbers in this font [1] at the end of specific lines in the example point to a numbered list of explanations that follow the example. TYPE Both [1] # # #
Setting Options [2]
OPTION:Type=Line [3] OPTION:PVMVersion=3.0 [4] #
Collection Interval for the following resources = 15 minutes
OPTION:Element=BigRouter [5] G1998/08/12 23:30:00 | Family | alias | Abcd |
| inventory | {device} [6]
. . . G1998/08/12 23:30:00 | Family | alias | Wxyz |
| inventory | {device} [6]
. . . OPTION:Element=EdgeRouter [5] G1998/08/12 23:30:00 | Family | alias | Mnop |
| inventory | {device} [6]
. . . G1998/08/12 23:30:00 | Family | alias | Qrst |
| inventory | {device} [6]
. . .
32
1.
Specifies Type Both, which must be the first line of a PvLine file.
2.
Specifies the # (pound sign) character at the beginning of lines to identify comments. The Bulk Collector ignores any lines that begin with a # character.
3.
Specifies the OPTION:Type=Line header line option to identify the file format associated with PvLine.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 4: PvLine File Format
4.
Specifies the OPTION:PVMVersion=3.0 header line option to identify the import PvLine file version. Version 3.0 is the only version that works with the Bulk Collector.
5.
Specify OPTION:Element header line options to identify two element names: BigRouter and EdgeRouter.
6.
Defines the required fields as follows: • Field 1 — Each of these data lines specifies the date in GMT. The letter G, by rule, precedes each date specification. • Field 2 — Each of these data lines specify the special property name called Family. Note that when a special property name is specified in field 2, the value type specified in field 6 must be inventory. • Field 3 — Each of these data lines specify a target type of alias. • Field 4 — These data lines specify target names of Abcd, Wxyz, and Mnop, respectively. More specifically, these target names are the sub-element names associated with the elements BigRouter and EdgeRouter identified in the OPTION:Element header lines. • Field 5 — Although this field is not currently used, by rule, it must still be specified. Each of these data lines specify this field by leaving it blank and following it with a separator character (|). • Field 6 — Each of these data lines specify a value type of inventory. This means that the value specified in field 2 must be a special property (in these data lines, Family). • Field 7 — Each of these data lines specify the value of Family for each of the specified sub-elements. Depending on the previous fields, the value could be a string or a number. For example:
Element
Sub-Elements
Family Values
BigRouter
Abcd
device
Wxyz EdgeRouter
Mnop
device
Qrst
Examples of Specifying Property Names The following example shows how to specify property names. The example also includes PvLine header line options. The numbers in this font [1] at the end of specific lines in the example point to a numbered list of explanations that follow the example. TYPE Both [1] # # # Setting Options [2] OPTION:Type=Line [3] OPTION:PVMVersion=3.0 [4] #
Collection Interval for the following resources = 15 minutes
OPTION:Element=BigRouter [5] . .
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
33
Chapter 4: PvLine File Format
. G1998/08/12 23:30:00 | Customer | alias | Abcd |
| property | Acme [6]
G1998/08/12 23:30:00 | Continent | alias | Abcd | G1998/08/12 23:30:00 | Country | alias | Abcd | G1998/08/12 23:30:00 | City | alias | Abcd | G1998/08/12 23:30:00 | CIR | alias | Abcd |
| property | Europe [6]
| property | France [6]
| property | Paris [6] | property | 128 [6]
. . . OPTION:Element=EdgeRouter [5] . . . G1998/08/12 23:30:00 | Customer | alias | Mnop |
| property | Customer3 [6]
G1998/08/12 23:30:00 | Continent | alias | Mnop | G1998/08/12 23:30:00 | Country | alias | Mnop | G1998/08/12 23:30:00 | City | alias | Mnop | G1998/08/12 23:30:00 | CIR | alias | Mnop |
| property | Europe [6]
| property | Italy [6]
| property | Rome [6] | property | 128 [6]
. . .
1.
Specifies Type Both, which must be the first line of a PvLine file.
2.
Specifies the # (pound sign) character at the beginning of lines to identify comments. The Bulk Collector ignores any lines that begin with a # character.
3.
Specifies the OPTION:Type=Line header line option to identify the file format associated with PvLine.
4.
Specifies the OPTION:PVMVersion=3.0 header line option to identify the import PvLine file version. Version 3.0 is the only version that works with the Bulk Collector.
5.
Specify OPTION:Element header line options to identify two element names: BigRouter and EdgeRouter.
6.
Defines the required fields as follows: • Field 1 — Each of these data lines specifies the date in GMT. The letter G, by rule, precedes each date specification. • Field 2 — Each of these data lines specify the specific property name. Note that when a property name is specified in field 2, the value type specified in field 6 must be property. In these data lines, the property names are Customer, Continent, Country, City, and CIR. • Field 3 — Each of these data lines specify a target type of alias. • Field 4 — These data lines specify target names of Abcd and Mnop, respectively. More specifically, these target names are the sub-element names associated with the elements BigRouter and EdgeRouter identified in the OPTION:Element header lines. • Field 5 — Although this field is not currently used, by rule, it must still be specified. Each of these data lines specify this field by leaving it blank and following it with a separator character (|).
34
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 4: PvLine File Format
• Field 6 — Each of these data lines specify a value type of property. This means that the value specified in field 2 must be a property name. • Field 7 — Each of these data lines specify a value for its associated property name. For example, the Customer properties have values of Acme and Customer3, respectively. The Country properties have values of France and Italy, respectively. The CIR properties have a numeric value of 128.
Examples of Specifying Metric Names The following example shows how to specify metric names. The example also includes PvLine header line options. The numbers in this font [1] at the end of specific lines in the example point to a numbered list of explanations that follow the example. TYPE Both [1] # # # Setting Options [2] OPTION:Type=Line [3] OPTION:PVMVersion=3.0 [4] #
Collection Interval for the following resources = 15 minutes
OPTION:Element=BigRouter [5] . . . G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~IP Traffic Percentage | alias | Abcd | | float | 95.448312749999999 [6] G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Power Level | alias | Abcd | | float | 1.672e-23 [6] . . . OPTION:Element=EdgeRouter [5] . . . G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~IP Traffic Percentage | alias | Mnop | | float | 95.448312749999999 [6] G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Power Level | alias | Mnop | | float | 1.672e-23 [6] . . .
1.
Specifies Type Both, which must be the first line of a PvLine file.
2.
Specifies the # (pound sign) character at the beginning of lines to identify comments. The Bulk Collector ignores any lines that begin with a # character.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
35
Chapter 4: PvLine File Format
3.
Specifies the OPTION:Type=Line header line option to identify the file format associated with PvLine.
4.
Specifies the OPTION:PVMVersion=3.0 header line option to identify the import PvLine file version. Version 3.0 is the only version that works with the Bulk Collector.
5.
Specify OPTION:Element header line options to identify two element names: BigRouter and EdgeRouter.
6.
Defines the required fields as follows: • Field 1 — Each of these data lines specifies the date in GMT. The letter G, by rule, precedes each date specification. • Field 2 — Each of these data lines specify the specific metric name. Note that when a metric name is specified in field 2, the value type specified in field 6 must be one of the ASCII strings float or string. In these data lines, the metric names are the actual bulk collection formula names: — AP~Specific~Bulk~{device}~IP Traffic Percentage — AP~Specific~Bulk~{device}~Power Level — AP~Specific~Bulk~{device}~IP Traffic Percentage — AP~Specific~Bulk~{device}~Power Level • Field 3 — Each of these data lines specify a target type of alias. • Field 4 — These data lines specify target names of Abcd and Mnop, respectively. More specifically, these target names are the sub-element names associated with the elements BigRouter and EdgeRouter identified in the OPTION:Element header lines. • Field 5 — Although this field is not currently used, by rule, it must still be specified. Each of these data lines specify this field by leaving it blank and following it with a separator character (|). • Field 6 — Each of these data lines specify a value type of float. This means that the value specified in field 2 must be a metric name. • Field 7 — Each of these data lines specify a value for its associated metric name. In these data lines, the values associated with the metric names (the actual bulk collection formula names) are as follows: — AP~Specific~Bulk~{device}~IP Traffic Percentage — 95.448312749999999 — AP~Specific~Bulk~{device}~Power Level — 1.672e-23 — AP~Specific~Bulk~{device}~IP Traffic Percentage — 95.448312749999999 — AP~Specific~Bulk~{device}~Power Level — 1.672e-23
Sample PvLine File The following is the complete sample PvLine file. Specific lines from this sample were discussed in previous sections. TYPE Both # # # Setting Options OPTION:Type=Line OPTION:PVMVersion=3.0 #
Collection Interval for the following resources = 15 minutes
OPTION:Element=BigRouter
36
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Chapter 4: PvLine File Format
G1998/08/12 23:30:00 | Family | alias | Abcd |
| inventory | {device}
G1998/08/12 23:30:00 | Customer | alias | Abcd |
| property | Acme
G1998/08/12 23:30:00 | Continent | alias | Abcd | G1998/08/12 23:30:00 | Country | alias | Abcd | G1998/08/12 23:30:00 | City | alias | Abcd | G1998/08/12 23:30:00 | CIR | alias | Abcd |
| property | Europe
| property | France
| property | Paris | property | 128
G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~IP Traffic Percentage | alias | Abcd | | float | 95.448312749999999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Power Level | alias | Abcd | | float | 1.672e-23 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Inbound Packets | alias | Abcd | | float | 749999999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Inbound Errors | alias | Abcd | | float | 456789 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Outbound Packets | alias | Abcd | | float | 8457499999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Interval | alias | Abcd | float | 15 G1998/08/12 23:30:00 | Family | alias | Wxyz |
| inventory | {device}
G1998/08/12 23:30:00 | Customer | alias | Wxyz |
| property | Customer2
G1998/08/12 23:30:00 | Continent | alias | Wxyz |
| property | Europe
G1998/08/12 23:30:00 | Country | alias | Wxyz | G1998/08/12 23:30:00 | City | alias | Wxyz | G1998/08/12 23:30:00 | CIR | alias | Wxyz |
|
| property | France
| property | Paris | property | 128
G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~IP Traffic Percentage | alias | Wxyz | | float | 95.448312749999999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Power Level | alias | Wxyz | | float | 1.672e-23 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Inbound Packets | alias | Wxyz | | float | 749999999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Inbound Errors | alias | Wxyz | | float | 456789 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Outbound Packets | alias | Wxyz | | float | 8457499999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Interval | alias | Wxyz | float | 15
|
OPTION:Element=EdgeRouter G1998/08/12 23:30:00 | Family | alias | Mnop |
| inventory | {device}
G1998/08/12 23:30:00 | Customer | alias | Mnop |
| property | Customer3
G1998/08/12 23:30:00 | Continent | alias | Mnop |
| property | Europe
G1998/08/12 23:30:00 | Country | alias | Mnop | G1998/08/12 23:30:00 | City | alias | Mnop | G1998/08/12 23:30:00 | CIR | alias | Mnop |
| property | Italy
| property | Rome | property | 128
G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~IP Traffic Percentage | alias | Mnop | | float | 95.448312749999999
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
37
Chapter 4: PvLine File Format
G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Power Level | alias | Mnop | | float | 1.672e-23 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Inbound Packets | alias | Mnop | | float | 749999999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Inbound Errors | alias | Mnop | | float | 456789 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Outbound Packets | alias | Mnop | | float | 8457499999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Interval | alias | Mnop | float | 15 G1998/08/12 23:30:00 | Family | alias | Qrst |
| inventory | {device}
G1998/08/12 23:30:00 | Customer | alias | Qrst |
| property | Customer4
G1998/08/12 23:30:00 | Continent | alias | Qrst |
| property | Europe
G1998/08/12 23:30:00 | Country | alias | Qrst | G1998/08/12 23:30:00 | City | alias | Qrst | G1998/08/12 23:30:00 | CIR | alias | Qrst |
|
| property | Germany
| property | Munich | property | 128
G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~IP Traffic Percentage | alias | Qrst | | float | 95.448312749999999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Power Level | alias | Qrst | | float | 1.672e-23 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Inbound Packets | alias | Qrst | | float | 749999999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Inbound Errors | alias | Qrst | | float | 456789 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Outbound Packets | alias | Qrst | | float | 8457499999 G1998/08/12 23:30:00 | AP~Specific~Bulk~{device}~Interval | alias | Qrst | float | 15
38
|
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
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:
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
39
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 developmentlevel 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.
40
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both.
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. 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.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
41
42
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Additional Copyright Information The following copyright information is for software used by Netcool/Proviso.
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 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.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
43
Additional Copyright information
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. 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.
•
The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission.
44
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Additional Copyright information
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 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.
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.
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
45
Additional Copyright information
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. 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.22719. 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, 19982000 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. Portions Copyright: (c) 2001-2003, Networks Associates Technology, Inc, (c) 2001-2003, Cambridge Broadband Ltd, (c) 20032005, 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. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 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
46
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
Additional Copyright information
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. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 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 . 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 . 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 and Brett McLaughlin . For more information on the JDOM Project, please see .
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
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
47
Additional Copyright information
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.
48
Netcool/Proviso Bulk Collector User’s Guide, Version 5.2
49
Netcool/Proviso DataMart Configuration Guide, Version 5.2
IBM
®
Printed in the USA.
