Browse Prior Art Database

Handling Tivoli Sentry Events

IP.com Disclosure Number: IPCOM000014040D
Original Publication Date: 1999-Dec-01
Included in the Prior Art Database: 2003-Jun-19
Document File: 2 page(s) / 47K

Publishing Venue

IBM

Related People

Woodrow Arkeketa: AUTHOR [+3]

Abstract

With the addition of *Tivoli Management Environment 10 Plus support for DCE which includes support for DCE/**DFS Monitors, it was apparent that some mechanism was needed to help administer the events that could come from monitors enabled for use with Tivoli Management Environment. The information also needed to be presented in a user friendly and convenient manner.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Handling Tivoli Sentry Events

With the addition of *Tivoli Management Environment 10 Plus support for DCE which includes support for DCE/**DFS Monitors, it was apparent that some mechanism was needed to help administer the events that could come from monitors enabled for use with Tivoli Management Environment. The information also needed to be presented in a user friendly and convenient manner.

The following is the list of Distributed File System (DFS) Monitors (1st column) made available and the output from the monitor (2nd column and is the event's value slot):

Aggregate Percentage Percentage Aggregate Used Count (1K blocks) Authorization Checking String (enabled/disabled) Cache Percentage Percentage Cache Used Count (1K blocks) Cells Contacted Count Current Principals Count File Server Status String (up/down) Fileset Replicas Count Fileset Server Activity String (idle/busy) Fileset Status String (locked/unlocked) Locked Entries in Fileset Location Database (FLDB) Count (locked FLDB entries) Not Available Server String (all running/not all running) Number of Filesets on Server Count Number of Replicas on Server Count
Process Core File String (exists/do not exist) Processes Running String (up/down) Process Status String (status string) Quota Percentage Percentage
Quota Used Count (1K blocks) Reads to Fileset Count (bytes)

Total Calls Count Total Clients Count Total Fetches Count Total Fetched Bytes Count (megabytes) Total Lookups Count Total Stored Bytes Count (megabytes) Total Stores Count Writes to Fileset Count (bytes)

There is an equally impressive list of monitors available for the DCE Tivoli monitors .

It would have been appropriate for a "default" rule to exists for these monitors to suggest an appropriate approach to handling Tivoli Sentry Monitors in a consistent manner. It would have been equally nice to have a set of default profiles be generated by defining the monitors by value slot type; however, this disclosure does not attempt to describe how that could have been done. This disclosure only addresses a single rule that was applied twice in two different rulesets that could have been used as a default rule for all Tivoli Sentry Monitor events. The ramifications of actually implementing this are not addressed here. Only the single rule has been described.

Handling events of these types falls into two categories: handling duplicates and handling non-duplicates. If an event is a duplicate, the event class must be the same as well as the following event slots:
hostname,
origin (IP address),
monitor, probe_arg, and
response_level.

Handling duplicates

1

Page 2 of 2

If the event is a duplicate of an existing event, then the old value slot is appended to the prev_value slot. This is illustrated below. This allows a kind of audit trail for the prior value slots. This can be especially useful to see how the monitor values change over time. Up to 255 bytes of data can be maintained in the prev_value slot. The duplicate's value s...