Wednesday, 4 January 2012

TNPM (Tivoli Netcool Performance Manager - Proviso )

The following terms are used throughout the Netcool/Proviso DataChannel installation procedure.

•Collector Subchannel: A subdivision of a DataChannel, with each Collector subchannel associated with a single Collector and CME. The division into Collector subchannels helps eliminate latency or loss of data caused by delayed Collectors. If a Collector subchannel disconnects for a period of time, only that Collector is affected, and all other Collector subchannels continue processing. The number of Collector subchannels per DataChannel differs according to the needs of a particular deployment. See the Netcool/Proviso Configuration Recommendations for information related to system configuration requirements. The terms Collector and Collectors are used to refer to Collector subchannel and Collector subchannels.

•Complex Metric Engine (CME): A DataChannel program that performs on-the-fly calculations on raw metrics data for a DataChannel. These calculations include time aggregations for resources, as well as statistical calculations using raw data, thresholds, properties, and constants as inputs. If CME formulas are defined for the incoming metrics data, the values are processed by those formulas. The CME synchronizes metadata at the beginning of each hour, and only processes the metadata that exists for the hour.

•CORBA (Common Object Request Broker Architecture): An industry-standard programming architecture that enables pieces of programs, called objects, to communicate with one another regardless of the programming language that they were written in or the operating system they are running on.

•Daily Database Loader (DLDR): A DataChannel program that gathers statistical data processed by a DataChannel’s CME and inserts it into the Netcool/Proviso database. There is one Daily Loader for each DataChannel; it is part of the channel processor component of the DataChannel.

•DataChannel Remote (DCR): A DataChannel installation configuration in which the subchannel, CME and FTE components are installed and run on one host, while the Loader components are installed and run on another host. In this configuration, the subchannel hosts can continue processing data and detecting threshold violations, even while disconnected from the Channel Manager server.

•DataChannel Standard: A DataChannel installation configuration in which all component programs of each subchannel are installed and run on the same server. DataChannel Standard installation is described in this chapter.

•DataLoad Bulk Collector: A DataLoad program that processes different data formats and resource files supplied by network devices, network management platforms, network probes, and other types of resources such as BMC Patrol. The Bulk Collector translates bulk statistics provided in flat files into Netcool/Proviso metadata and data. If operating in synchronized inventory mode, the Bulk Collector passes the resources and properties to the Netcool/Proviso DataMart Inventory application.

•DataLoad SNMP Collector: A DataLoad program that collects data from network resources via SNMP polling. The SNMP Collector provides raw data files to the DataChannel for processing by the CME.

•DataLoad UBA Bulk Collector: A DataLoad program that imports data from files (referred to as Bulk input files) generated by non-SNMP devices, including Alcatel 5620 NM, Alcatel SAM, and Cisco CWM. These Bulk input files contain formats that the Bulk Collector is unable to handle.

•Discovery Server (DISC): A DataChannel program that runs as a daemon to perform an inventory of SNMP network devices from which to gather statistical data.

•Hourly Database Loader (LDR): A DataChannel program that serves as the point of data synchronization and merging, and of late data processing, for each DataChannel. The Hourly Loader gathers files generated by the CME, computes group aggregations from the individual resource aggregation records, and loads the data into the Netcool/Proviso database.

•File Transfer Engine (FTE): A DataChannel program that periodically scans the Collector output directories, examines the global execution plan to determine which computation requests require the data, then sorts the incoming data for storage.

•Next-Hour Policy: Specifies the number of seconds to wait past the hour for files to arrive before the next hourly directory is created. The default value causes the DataChannel to wait until 15 minutes after the hour before it starts processing data for the next hour. To avoid losing data, you need to set a percentage and a time-out period during the configuration of the CME.

•Plan Builder (PBL): A DataChannel program that creates the metric data routing and processing plan for the other components in the DataChannel.

No comments:

Post a Comment

Tweets by @sriramperumalla