INTERNET-DRAFT C. Kalbfleisch
Verio, Inc.
C. Krupczak
Empire Technologies, Inc.
R. Presuhn
BMC Software, Inc.
J. Saperia
BGS Systems, Inc.
20 November 1997
Application Management MIB
<draft-ietf-applmib-mib-05.txt>
Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet- Drafts
Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast).
Copyright Notice
Copyright (C) The Internet Society (1997). All Rights Reserved.
Abstract
This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management protocols in
the Internet Community. In particular, it defines objects used for
the management of applications. This MIB complements the System
Application MIB, providing for the management of applications' common
attributes which could not typically be observed without the
cooperation of the software being managed.
Applmib Working Group Expires May 1998 [Page 1]
Internet Draft Application Management MIB 20 November 1997
Table of Contents
1. Introduction ................................................ 3
2. Overview .................................................... 3
3. Architecture ................................................ 5
3.1. Relationships to other MIBs ............................... 5
3.1.1. Relationship to the System Application MIB .............. 6
3.1.2. Relationship to the Host Resources MIB .................. 6
3.1.3. Relationship to NSM ..................................... 6
4. MIB Structure ............................................... 6
4.1. The service-level tables .................................. 8
4.1.1. The service name to service instance table .............. 8
4.1.2. The service instance to service name table .............. 9
4.2. The open files group ...................................... 9
4.2.1. The open files table .................................... 9
4.2.2. The open files cross-reference table .................... 10
4.3. The open connections table ................................ 10
4.4. The former connection group ............................... 11
4.4.1. The former connection control table ..................... 11
4.4.2. The former connection table ............................. 11
4.5. The transaction group ..................................... 12
4.5.1. The transaction summary table ........................... 12
4.5.2. The transaction flow statistics table ................... 12
4.5.3. The transaction kind statistics table ................... 13
4.6. The running element status and control group .............. 13
4.6.1. The running application element status table ............ 13
4.6.2. The running application element control table ........... 14
5. Definitions ................................................. 14
6. Implementation Issues ....................................... 60
7. Intellectual Property ....................................... 61
8. Acknowledgements ............................................ 62
9. Security Considerations ..................................... 62
10. References ................................................. 62
11. Editors' Addresses ......................................... 64
12. Issues and List of Things Left To Be Done .................. 65
13. Full Copyright Statement ................................... 66
Applmib Working Group Expires May 1998 [Page 2]
Internet Draft Application Management MIB 20 November 1997
1. Introduction
This draft furthers the work begun in the systems application mib
[10]. See the issues list at the end of this document for issues
that remain to be worked out.
The development of [1], [2], [3], [4], and [8] provides us with a
base of experience in making a variety of applications visible to
management; this specification abstracts out the common aspects of
applications management and provides a generic base usable for the
management of almost any application.
2. Overview
Due to the design decision to not require application
instrumentation, many important topics were not handled in system
application MIB [10]. The following topics are within the scope of
this document:
- Support for generic application throughput
measurements;
- Providing MIB definitions that allow managed entities
to report what they considered to be units of work;
- Providing support for generic application response time
monitoring capabilities;
- Provide explicit support for the management of
applications distributed within a single managed system
("local" distribution);
- Address generic resource management issues, including:
- files in use;
- I/O statistics (from the application's
perspective, not at the operating system or
device driver level);
- application-layer networking resource usage
- Providing access to dependency information, both
in the form of MIB objects to report
dependencies on "mission critical" processes, as
well as the logging of failures due to
dependencies.
Applmib Working Group Expires May 1998 [Page 3]
Internet Draft Application Management MIB 20 November 1997
- Provide a generic logging (stderr) capability:
- Identify common log entries of use with multiple
applications;
- Permit use of specialized log entries where
appropriate;
- Provide generic facility for the management of
this log;
- Provide generic facility to control notification
generation by the application;
- Facilities for the control of applications, including:
- Starting and stopping applications and their
elements;
- Suspending and resuming applications and their
elements;
- Configuration of application parameters;
- A "mission critical process" MIB to identify
processes that are of particular interest;
- Reconfiguration (e.g., SIGHUP) request
capability.
Note that these issues are addressed at least in part by other (non-
IETF) standards work, including [11] and [12].
Some topics were identified as being of interest to the applmib
working group, but outside the scope of this document.
- Providing MIB definitions that allow management to
define what is to be considered an error. This
includes mechanisms for filtering and selective
forwarding of information from notifications or log
entries.
Topics identified as specifically out of scope include:
- Providing MIB definitions to allow dynamic control of
the definition of units of work;
- Explicit support for the management of applications
Applmib Working Group Expires May 1998 [Page 4]
Internet Draft Application Management MIB 20 November 1997
distributed across multiple systems; (The indexing
structure and semantics of the system application MIB
[10] are not sufficient for this task.)
- Issues of backup and recovery;
- Issues of software request, delivery, installation,
activation, patching, version update, reversion, and
removal;
- Issues of software validation and integrity checks;
- Issues of software licensing.
3. Architecture
Object-oriented modeling techniques like subclassing and multiple
inheritance can be emulated in the SNMP information model through the
use of tables with common indexes.
The challenge for the developer of management applications is to
recognize those situations in which various aspects of a single
logical resource are represented in several different tables,
possibly defined in different MIBs.
Most of the management information defined here may pertain to any
number of applications in a managed system. The simplest way of
supporting this requirement within the SNMP information model is to
use tables. This means that the management information for a
particular resource may be found in one or more rows of one or more
tables; the fact that this information pertains to a single resource
may be deduced from the index values used, possibly with the support
of mapping tables. This also means that a single table may contain
management information relevant to a number of applications. This
has significant implementation implications; see the implementation
issues section below for more information.
3.1. Relationships to other MIBs
This section outlines the relationships of the components of this MIB
(usually in the form of common indexing structures) to:
- the systems applications MIB [10]
- the host resources MIB [1]
- the network services monitoring MIB [2]
Applmib Working Group Expires May 1998 [Page 5]
Internet Draft Application Management MIB 20 November 1997
3.1.1. Relationship to the System Application MIB
The system application MIB defines attributes for management of
applications which can be realized without instrumenting an
application. This specification extends that framework to include
additional attributes which will typically require instrumentation
within the managed resource. The sysApplRunElmtIndex is the key
connection between these two MIBs; it is essential that
implementations of this MIB and of the system applications MIB
running concurrently on a given platform employ a consistent policy
for assigning this value to running application elements.
3.1.2. Relationship to the Host Resources MIB
The Host Resources MIB [1] supplies information on the hardware,
operating system, installed and running software on a host.
The Host Resources MIB has three hardware groups ("hrSystem",
"hrStorage" and "hrDevice") and three software groups ("hrSWRun",
"hrSWRunPerf" and "hrSWInstalled"). Of these, the software groups
are of greatest significance to this MIB.
The software groups define management information on the software
used in the system. The information provided is grouped into (1) the
currently running, (2) the performance and (3) the installed
applications.
The index "hrSWRunIndex" used in the "hrSWRunTable" and other tables
to identify running software by process identifier (or equivalent)
relates information in the Host Resources MIB to information in the
System Applications MIB and this MIB.
3.1.3. Relationship to NSM
The Network Services Monitoring MIB [2] is defined as the base set of
attributes for managing network applications. The Application MIB
extends includes information normally obtainable only from the
managed resource itself, rather than the supporting system. Due to
differences in index representation, the relationship between the
Network Services Monitoring MIB and the Application MIB is not
formally defined.
4. MIB Structure
This MIB is organized into several groups, which in turn are
organized into tables to provide the monitoring and control of
information relevant to the management of applications. The groups
model:
Applmib Working Group Expires May 1998 [Page 6]
Internet Draft Application Management MIB 20 November 1997
- the service-level view of applications
- information on open files in use by applications
information on open connections in use by applications
historical information on former connections
transaction-level information
process-level status and control information
These groups are organized into various tables. Information for a
particular running managed application appears in the form of entries
in the appropriate tables. The tables are:
- the tables providing a service-level view, including:
- the service name to service instance table
- the service instance to service name table
- the service instance to running application
element table
- the running application element to service
instance table
- the tables providing information on open files,
including:
- the open files table
- the open files cross-reference table
- the open connections table
- the connection history table
- the transaction statistics tables
- the running application element status and control
group
- the running application element status table
- the running application element control table
Applmib Working Group Expires May 1998 [Page 7]
Internet Draft Application Management MIB 20 November 1997
In order to support SNMPv1, SNMPv2, and SNMPv3 environments, in cases
where counter objects may potentially advance very rapidly, both a
sixty-four bit counter and two thirty-two bit counters have been
defined.
Since rows in most of these tables will come and go with the running
application elements whose information is contained in them,
sysUpTime.0 is not appropriate as a discontinuity indicator for
counters in these tables. By defining separate discontinuity
indicators for the rows in these tables, entries can come and go as
needed without causing other objects to appear to have
discontinuities. As required by [5], the discontinuity indicators
for the various information objects in these tables are identified in
the relevant DESCRIPTION clauses.
4.1. The service-level tables
The service-level tables permit the identification of one or more
instances of named services on a system, and the association of
running application elements to these services.
Service names are represented as human-readable strings, using values
assigned by IANA where possible. The allocation of unique values for
service instance identifiers is a local administrative issue; the
values allocated must be constant for the lifetime of the service
instance, and re-use of values should be avoided.
In deciding what should or should not be considered a service, the
following factors merit consideration:
- is there an identifiable set of resources associated
with providing this service?
- is there a reasonably long-lived server or client
process?
Following this reasoning, one can see where SMTP and HTTP would be
good candidates for classification as services for purposes of
application management, where finger probably would not. Of course,
implementors of this MIB are free to define additional services. An
applicability statement may be an appropriate vehicle for
standardizing how a specific service's information is reported using
this MIB.
4.1.1. The service name to service instance table
The service name to service instance table uses service name as its
primary key, and service instance identifier as its secondary key.
Applmib Working Group Expires May 1998 [Page 8]
Internet Draft Application Management MIB 20 November 1997
It facilitates the identification and lookup of the instances a given
service in a system.
4.1.2. The service instance to service name table
The service instance to service name table uses service instance
identifier as its primary key, and service name as its secondary key.
Given a service instance identifier, it facilitates the lookup of the
name of the service being provided.
4.1.3. The service instance to running application element table
The service instance to running application element table uses the
service instance identifier as its primary key, and the running
application element index as its secondary key. This facilitates the
identification of the set of running application elements providing a
given instance of a service.
4.1.4. The running application element to service instance table
The running application element to service instance table uses the
running application element index as its primary key and the service
instance identifier as its secondary key. It identifies the set of
services provided by a given running application element.
4.2. The open files group
There are two tables in the open files group: the open files table
and the open files cross-reference table. These permit information
on open files to be retreived by running application element index
and by open file name.
4.2.1. The open files table
The open files table contains one entry for each file in use by a
manageable running application element. (See [10] for a detailed
definition of a running application element.) The purpose of this
table is to identify the files in use and to record I/O activity on
each file attributable to a particular running application element.
If multiple running application elements open the same file, there
will be an entry for each running application element opening that
file. Similarly, if a running application element opens a file
multiple times, there will be an entry in this table for the file
corresponding to each open.
The task of combining the information for file activity from this
table (organized by running application element) into per-application
Applmib Working Group Expires May 1998 [Page 9]
Internet Draft Application Management MIB 20 November 1997
statistics can be accomplished by a manager using the System
Application MIB's [10] sysApplInstallPkgTable to find the installed
application, the sysApplRunTable to find the running instances of
that application, and the sysApplElmtRunTable to find the relevant
values of sysApplElmtRunIndex. The manager, armed with a set of
values for sysApplElmtRunIndex, is now able to retrieve the relevant
portions of the applOpenFileTable and other tables in this MIB.
Entries in this table are indexed by the application run index and an
arbitrary integer, chosen so that taken together the application run
index and this integer yield a unique key for each open file. The
following information is available in this table:
- file name
- number of read requests
- number of bytes read
- time at which most recent read operation was initiated
- number of write requests
- number of bytes written
- time at which most recent write operation was initiated
- number of seek operations
- file size
- mode (read/write) in which file was opened
Special cases to consider: stdin, stdout, stderr, etc. may require
some special handling.
4.2.2. The open files cross-reference table
This table provides a way to efficiently determine which processes
are currently holding a file open. It introduces no new attributes
of its own, and merely provides an alternative indexing to the open
file table.
4.3. The open connections table
This table provides information on each open connection of an
application element. It is indexed by the application element and
the connection identifier. The following information is available
Applmib Working Group Expires May 1998 [Page 10]
Internet Draft Application Management MIB 20 November 1997
for each connection:
- time at which the connection was opened
- identification of the transport protocol in use
- near-end address and port
- far-end address and port
- identification of the application layer protocol in use
- number of read requests
- number of bytes received
- time at which the most recent read request was
initiated
- number of write requests
- number of bytes transmitted
- time at which most recent write request was initiated
4.4. The former connection group
The former connection group consists of two tables: the former
connection table and the former connection control table.
4.4.1. The former connection control table
The former connection control table provides per-process control over
the accumulation of information on former connections. For each
process, this table, indexed by the application element run index,
controls whether information on former connections is accumulated,
how many of these history records are retained, how long these are
retained (within the lifetime of the process), and a count of history
entries that were deleted before their expiration time in order to
make room for new entries.
4.4.2. The former connection table
The former connection table provides historical information on
connections that have been closed. The number and lifetime of these
entries is controlled, on a per-process basis, by the former
connection control table. Most of the information in this table
corresponds to information in the open connection table.
Applmib Working Group Expires May 1998 [Page 11]
Internet Draft Application Management MIB 20 November 1997
4.5. The transaction group
The transaction statistics group has three tables. The transaction
summary table contains per-stream summaries of transaction
statistics. The transaction flow statistics table contains
statistics broken into both transmit and receive counts for requests
and responses on each stream. The transaction kind statistics table
contains information further broken down by transaction type.
Entries in the the tables in this group have a common structure for
their indexing, with additional indexes added for increasing detail.
All of these tables are indexed by the application element run index
and an arbitrary integer, chosen so that taken together the
application run index and this integer yield a unique key for each
transaction stream associated with the running application element.
A transaction stream may be a file or a connection; a column in the
transaction summary table contains the OBJECT IDENTIFIER of the
instance of applOpenConnectionOpenTime or applOpenFileOpenTime, in
the open files table or open connections table respectively.
4.5.1. The transaction summary table
The transaction summary table contains per-stream summaries of
transaction statistics. The information represented in this table
includes:
- identification of the underlying connection or file
used for this transaction stream
- a human-readable description of this stream
- a human-readable description of this stream's notion of
what a unit of work is
- the cumulative amount of time spent (as an operation
invoker) waiting for responses
- the cumulative amount of time spent (as an operation
performer) handling requests
- a time stamp for use as a discontinuity indicator in
related rows in this group
4.5.2. The transaction flow statistics table
The transaction flow statistics table contains statistics broken into
both transmit and receive counts for requests and responses on each
stream. In addition to the running application element and
Applmib Working Group Expires May 1998 [Page 12]
Internet Draft Application Management MIB 20 November 1997
transaction stream identifier indexes, rows in this table are indexed
by flow direction (transmit or receive) and role (requests and
responses). The information in this table includes:
- the number of transactions processed
- the number of bytes processed
- the time at which the most recent transaction was
processed in this flow
4.5.3. The transaction kind statistics table
The transaction kind statistics table contains summary information
organized by direction, request/response, and transaction type for
each stream. The indexing of this table is like that of the
transaction flow table, with the addition of a transaction kind
index.
- number of transactions processed
- number of bytes processed
- the time at which the most recent transaction of this
kind in this direction in this stream was processed
4.6. The running element status and control group
The running application element status and control group has two
tables.
4.6.1. The running application element status table
This table provides information for a running application element.
Indexed by the sysApplElmtRunIndex, an entry in this table reports
useful information on that running element's resource usage. Entries
in this table contain:
- current heap usage for this running application element
- current number of open network connections for this
running application element
- the most recent error message issued by this running
application element
Note that other information, such as the current number of open files
for this running application element, is available from the
Applmib Working Group Expires May 1998 [Page 13]
Internet Draft Application Management MIB 20 November 1997
sysapplElmtRunTable in [10].
4.6.2. The running application element control table
This table provides rudimentary control over a running application
element. Indexed by the sysApplElmtRunIndex, an entry in this table
gives a manager with appropriate permissions the ability to suspend
and resume processing by this running element, the ability to request
reconfiguration, and the ability to terminate the running element.
Variables in this table include:
- a suspend/resume control
- a reconfiguration request control
- a termination request control
5. Definitions
APPLICATION-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE,
Counter64, Counter32, Gauge32,
mib-2, Unsigned32 FROM SNMPv2-SMI
DateAndTime, RowPointer,
TAddress, TestAndIncr, TDomain,
TimeStamp, TruthValue FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
LongUtf8String,
sysApplElmtRunIndex,
Utf8String FROM SYSAPPL-MIB;
applicationMib MODULE-IDENTITY
LAST-UPDATED "9711200000Z"
ORGANIZATION "Application MIB Working Group"
CONTACT-INFO
"http://www.ietf.org/html.charters/applmib-charter.html
Randy Presuhn
BMC Software, Inc.
1190 Saratoga Avenue, Suite 100
Applmib Working Group Expires May 1998 [Page 14]
Internet Draft Application Management MIB 20 November 1997
San Jose, CA 95129
USA
Telephone: +1 800 841-2031
Facsimile: +1 408 556-0735
Email: rpresuhn@bmc.com
"
DESCRIPTION
"This MIB defines objects representing generic
aspects of applications that are of interest to
management but typically require instrumentation
within the managed application element.
"
::= { mib-2 3333333333 }
--ISSUE: need to get IANA assignment for registration
--
-- Registration hierarchy for this MIB
--
applicationMibObjects OBJECT IDENTIFIER ::=
{ applicationMib 1 }
applicationMibTraps OBJECT IDENTIFIER ::=
{ applicationMib 2 }
applicationMibConformance OBJECT IDENTIFIER ::=
{ applicationMib 3 }
--
-- Groups defined in this MIB
--
applServiceGroup OBJECT IDENTIFIER ::=
{ applicationMibObjects 1 }
applFileGroup OBJECT IDENTIFIER ::=
{ applicationMibObjects 2 }
applConnectionGroup OBJECT IDENTIFIER ::=
{ applicationMibObjects 3 }
applPastConGroup OBJECT IDENTIFIER ::=
{ applicationMibObjects 4 }
applTransactionGroup OBJECT IDENTIFIER ::=
{ applicationMibObjects 5 }
applElmtRunControlGroup OBJECT IDENTIFIER ::=
Applmib Working Group Expires May 1998 [Page 15]
Internet Draft Application Management MIB 20 November 1997
{ applicationMibObjects 6 }
-- *************************************************************
--
-- applServiceGroup -
-- The service-level tables permit the
-- identification of one or more instances of named
-- services on a system, and the association of
-- running application elements to these services.
--
-- *************************************************************
--
-- The service name to service instance table
--
applSrvNameToSrvInstTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplSrvNameToSrvInstEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The service name to service instance table uses
service name as its primary key, and service
instance identifier as its secondary key.
It facilitates the identification and lookup of
the instances a given service in a system."
::= { applServiceGroup 1 }
ApplSrvNameToSrvInstEntry ::= SEQUENCE
{
applSrvInstQual Utf8String
}
applSrvNameToSrvInstEntry OBJECT-TYPE
SYNTAX ApplSrvNameToSrvInstEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applSrvNameToSrvInstEntry identifies an instance
of a given service. The allocation and reservation of
unique values for applSrvInst is an administrative issue.
An applSrvNameToSrvInstEntry exists for the lifetime
of that instance of that service; the index values may not
change during that lifetime.
"
INDEX { applSrvName, applSrvInst }
::= { applSrvNameToSrvInstTable 1 }
Applmib Working Group Expires May 1998 [Page 16]
Internet Draft Application Management MIB 20 November 1997
applSrvInstQual OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of applSrcInstQual provides additional
information about this particular instance of this
service."
"
::= { applSrvNameToSrvInstEntry 1 }
--
-- Service instance to Service Name table
--
applSrvInstToSrvNameTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplSrvInstToSrvNameEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The service instance to service name table uses
service instance identifier as its primary key,
and service name as its secondary key. Given a
service instance identifier, it facilitates the
lookup of the name of the service being provided."
::= { applServiceGroup 2 }
ApplSrvInstToSrvNameEntry ::= SEQUENCE
{
applSrvName Utf8String
}
applSrvInstToSrvNameEntry OBJECT-TYPE
SYNTAX ApplSrvInstToSrvNameEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applSrvInstToSrvNameEntry maps a service instance
identifier back to a service name."
INDEX { applSrvInst, applSrvName }
::= { applSrvInstToSrvNameTable 1 }
applSrvName OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The human-readable name of a service.
Where possible, the official protocol name as
Applmib Working Group Expires May 1998 [Page 17]
Internet Draft Application Management MIB 20 November 1997
assigned by IANA or other authority should be
used.
"
::= { applSrvInstToSrvNameEntry 1 }
--
-- The service instance to running application element table
--
applSrvInstToRunApplElmtTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplSrvInstToRunApplElmtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The service instance to running application
element table uses the service instance
identifier as its primary key, and the running
application element index as its secondary key.
This facilitates the identification of the set
of running application elements providing a
given instance of a service."
::= { applServiceGroup 3 }
ApplSrvInstToRunApplElmtEntry ::= SEQUENCE
{
applElmtRunIndex Unsigned32
}
applSrvInstToRunApplElmtEntry OBJECT-TYPE
SYNTAX ApplSrvInstToRunApplElmtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applSrvInstToRunApplElmtEntry identifies a running
application element providing an instance of a service.
Note that there may be multiple running application
elements involved in the provision of an instance of
a service."
INDEX { applSrvInst, sysapplElmtRunIndex }
::= { applSrvInstToRunApplElmtTable 1 }
applSrvInst OBJECT-TYPE
SYNTAX Unsigned32
--
-- ISSUE: should zero be excluded from the range?
--
MAX-ACCESS read-only
STATUS current
Applmib Working Group Expires May 1998 [Page 18]
Internet Draft Application Management MIB 20 November 1997
DESCRIPTION
"An applSrvInst is the system-unique identifier of
an instance of a service. The value is unique
not only across all instances of a given service,
but also across all services.
Re-use of values for this index should be avoided.
No two service instances in a given system shall
concurrently have the same value for this index.
"
::= { applSrvInstToRunApplElmtEntry 1 }
--
-- The running application element to service instance table
--
applRunApplElmtToSrvInstTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplRunApplElmtToSrvInstEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The running application element to service
instance table uses the running application
element index as its primary key and the service
instance identifier as its secondary key.
It identifies the set of services provided by
a given running application element."
::= { applServiceGroup 4 }
ApplRunApplElmtToSrvInstEntry ::= SEQUENCE
{
-- ISSUE: need to put something here
}
applRunApplElmtToSrvInstEntry OBJECT-TYPE
SYNTAX ApplRunApplElmtToSrvInstEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applRunApplElmtToSrvInstEntry serves to identify
an instance of a service being provided by a
given running application element. Note that a
particular running application element may
provide multiple services."
INDEX { sysApplElmtRunIndex, applSrvInst }
::= { applRunApplElmtToSrvInstTable 1 }
-- *************************************************************
Applmib Working Group Expires May 1998 [Page 19]
Internet Draft Application Management MIB 20 November 1997
--
-- applOpenFileTable - Table of Open Files
--
-- *************************************************************
applOpenFileTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplOpenFileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The applOpenFileTable reports information on open
files for running application elements. This table
is indexed by sysApplElmtRunIndex [10], effectively
grouping all entries for a given running application
element together, and by applOpenFileId, uniquely
identifying an open file within the context of a
particular running application element.
Some of the information in this table is
available through both sixty-four and thirty-two
bit counters. The sixty-four bit counters are
not accessible in protocols that do not support
this data type."
::= { applFileGroup 1 }
ApplOpenFileEntry ::= SEQUENCE
{
applOpenFileOpenTime TimeStamp,
applOpenFileName LongUtf8String,
applOpenFileReadRequests Counter64,
applOpenFileReadRequestsLow Counter32,
applOpenFileReadFailures Counter32,
applOpenFileBytesRead Counter64,
applOpenFileBytesReadLow Counter32,
applOpenFileLastReadTime DateAndTime,
applOpenFileWriteRequests Counter64,
applOpenFileWriteRequestsLow Counter32,
applOpenFileWriteFailures Counter32,
applOpenFileBytesWritten Counter64,
applOpenFileBytesWrittenLow Counter32,
applOpenFileLastWriteTime DateAndTime,
applOpenFileSeekRequests Counter64,
applOpenFileSeekRequestsLow Counter32,
applOpenFileSizeHigh Unsigned32,
applOpenFileSizeLow Unsigned32,
applOpenFileOpenMode INTEGER
}
Applmib Working Group Expires May 1998 [Page 20]
Internet Draft Application Management MIB 20 November 1997
applOpenFileEntry OBJECT-TYPE
SYNTAX ApplOpenFileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applOpenFileEntry indicates that a file has been
opened by this running application element and is
still open. Note that if a file has been opened
multiple times, even by the same process, it may
have multiple entries."
INDEX { sysApplElmtRunIndex, applOpenFileId }
::= { applOpenFileTable 1 }
applOpenFileOpenTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute records the value of sysUptime.0
when this file was opened and this entry was
added to this table. This attribute serves as a
discontinuity indicator for the counter attributes
in this entry."
::= { applOpenFileEntry 1 }
applOpenFileName OBJECT-TYPE
SYNTAX LongUtf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the name of this open file.
Wherever practical, a fully qualified path name
should be reported.
The values 'stdin', 'stdout', and 'stderr' are
reserved in accordance with common usage."
::= { applOpenFileEntry 2 }
applOpenFileReadRequests OBJECT-TYPE
SYNTAX Counter64
UNITS "read requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of read requests
for this file made by this running application
element. All read requests for this file by
Applmib Working Group Expires May 1998 [Page 21]
Internet Draft Application Management MIB 20 November 1997
this running application element, regardless of
completion status, are included in this count.
Read requests are counted in terms of system
calls, rather than API calls.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 3 }
applOpenFileReadRequestsLow OBJECT-TYPE
SYNTAX Counter32
UNITS "read requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the low thirty-two
bits of applOpenFileReadRequests.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 4 }
applOpenFileReadFailures OBJECT-TYPE
SYNTAX Counter32
UNITS "failed read requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of failed
read requests.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 5 }
applOpenFileBytesRead OBJECT-TYPE
SYNTAX Counter64
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of bytes read
from this file by this running application element.
Applmib Working Group Expires May 1998 [Page 22]
Internet Draft Application Management MIB 20 November 1997
Only bytes successfully read are included in
this count.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 6 }
applOpenFileBytesReadLow OBJECT-TYPE
SYNTAX Counter32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-
two bits of applOpenFileBytesRead.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 7 }
applOpenFileLastReadTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the time of the most
recent read request made by this running application
element, regardless of completion status, for this
open file.
If no read requests have been made by this running
application element, the value of this attribute
shall be '0000000000000000'H "
DEFVAL { '0000000000000000'H }
::= { applOpenFileEntry 8 }
applOpenFileWriteRequests OBJECT-TYPE
SYNTAX Counter64
UNITS "write requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of write requests
for this file made by this running application
element. All write requests for this file by
this running application element, regardless of
Applmib Working Group Expires May 1998 [Page 23]
Internet Draft Application Management MIB 20 November 1997
completion status, are included in this count.
Write requests are counted in terms of system calls,
rather than API calls.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 9 }
applOpenFileWriteRequestsLow OBJECT-TYPE
SYNTAX Counter32
UNITS "write requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-
two bits of applOpenFileWriteRequests.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 10 }
applOpenFileWriteFailures OBJECT-TYPE
SYNTAX Counter32
UNITS "failed write requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of failed
write requests.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 11 }
applOpenFileBytesWritten OBJECT-TYPE
SYNTAX Counter64
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of bytes written
to this file by this running application
element. Only bytes successfully written (without
errors reported by the API in use by the application)
Applmib Working Group Expires May 1998 [Page 24]
Internet Draft Application Management MIB 20 November 1997
are included in this count.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 12 }
applOpenFileBytesWrittenLow OBJECT-TYPE
SYNTAX Counter32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-
two bits of applOpenFileBytesWritten.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 13 }
applOpenFileLastWriteTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the time of the most
recent write request made by this running
application element, regardless of completion
status, for this open file.
If no write requests have been made by this running
application element, the value of this attribute
shall be '0000000000000000'H "
DEFVAL { '0000000000000000'H }
::= { applOpenFileEntry 14 }
applOpenFileSeekRequests OBJECT-TYPE
SYNTAX Counter64
UNITS "seek requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of seek requests
made on this open file.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
Applmib Working Group Expires May 1998 [Page 25]
Internet Draft Application Management MIB 20 November 1997
this entry."
::= { applOpenFileEntry 15 }
applOpenFileSeekRequestsLow OBJECT-TYPE
SYNTAX Counter32
UNITS "seek requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-
two bits of applOpenFileSeekRequests.
Discontinuities in this counter can be detected
by monitoring the applOpenFileOpenTime value for
this entry."
::= { applOpenFileEntry 16 }
applOpenFileSizeHigh OBJECT-TYPE
SYNTAX Unsigned32
UNITS "2^32 byte blocks"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This file's current size in 2^32 byte blocks.
For example, for a file with a total size of
4,294,967,296 bytes, this attribute would have
a value of 1; for a file with a total size of
4,294,967,295 bytes this attribute's value would
be 0."
::= { applOpenFileEntry 17 }
applOpenFileSizeLow OBJECT-TYPE
SYNTAX Unsigned32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This file's current size modulo 2^32 bytes.
For example, for a file with a total size of
4,294,967,296 bytes this attribute would have
a value of 0; for a file with a total size of
4,294,967,295 bytes this attribute's value would
be 4,294,967,295."
::= { applOpenFileEntry 18 }
applOpenFileOpenMode OBJECT-TYPE
Applmib Working Group Expires May 1998 [Page 26]
Internet Draft Application Management MIB 20 November 1997
SYNTAX INTEGER { read(1),
write(2),
readWrite(3) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the mode in which the file
was most recently opened by this running application
element.
These values correspond to the Posix/ANSI C library
function fopen() 'type' parameter, using the
following mappings:
r -> read(1)
w -> write(2)
a -> write(2)
+ -> readWrite(3)
These values have the following meanings:
read(1) - file opened for reading only
write(2) - file opened for writing only
readWrite - file opened for read and write."
::= { applOpenFileEntry 19 }
-- *************************************************************
--
-- applOpenFileXrefTable - Open File cross-reference table
--
-- *************************************************************
applOpenFileXrefTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplOpenFileXrefEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The applOpenFileXrefTable provides an alternative
indexing to the information in the
applOpenFileTable. Rather than grouping entries by
sysApplElmtRunIndex, it groups them by their names
(the value of applOpenXrefFileName is derived from
applOpenFileName). Since in many environments
multiple processes may concurrently open a file,
and a single process may open a file multiple
times, entries in this table are also indexed by
Applmib Working Group Expires May 1998 [Page 27]
Internet Draft Application Management MIB 20 November 1997
sysApplElmtRunIndex and applOpenFileId."
::= { applFileGroup 2 }
ApplOpenFileXrefEntry ::= SEQUENCE
{
applOpenFileXrefName Utf8String,
applOpenFileId Unsigned32
}
applOpenFileXrefEntry OBJECT-TYPE
SYNTAX ApplOpenFileXrefEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applOpenFileXrefEntry indicates that a file
has been opened by a running application element.
Note that if a file has been opened multiple
times, even by the same process, it may have
multiple entries.
Note that the SMI limitation on the maximum number
of components in an OBJECT IDENTIFIERS means that
the full name of an open file may be too long to
use directly as an index. Thus, a value meeting
these constraints yet readily derived from the
full name is used for purposes of indexing."
INDEX { applOpenFileXrefName,
sysApplElmtRunIndex,
applOpenFileId }
::= { applOpenFileXrefTable 1 }
applOpenFileXrefName OBJECT-TYPE
SYNTAX Utf8String (SIZE (0 .. 114 ))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This index corresponds to applOpenFileName.
This index's value is derived from that of
applOpenFileName by application of the following
algorithm (or one with equivalent results), made
necessary by by SNMP's limits on maximum object
identifier length.
1) Start with applOpenFileName's value
2) Convert to a sequence of 32-bit values
(undo the UTF-8 transform)
3) apply the UTF-8 transform to this sequence,
encoding code points completely, but not
Applmib Working Group Expires May 1998 [Page 28]
Internet Draft Application Management MIB 20 November 1997
exceeding 114 bytes. (Thus it is possible
that a truncated value may be several bytes
less than 114 bytes long.)
"
::= { applOpenFileXrefEntry 1 }
applOpenFileId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute serves to uniquely identify this
open file in the context of the running application
element. When practical, the native file descriptor
number shall be used."
::= { applOpenFileXrefEntry 2 }
-- *************************************************************
--
-- applOpenConnectionTable - Open Connection Table
--
-- *************************************************************
applOpenConnectionTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplOpenConnectionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The applOpenConnectionTable provides information
about open and listening connections from
the perspective of the running application
element. Entries in this table are indexed by
sysApplElmtRunIndex and by applOpenConnectionId,
which serves to uniquely identify each connection
in the context of a running application element."
::= { applConnectionGroup 1 }
ApplOpenConnectionEntry ::= SEQUENCE
{
applOpenConnectionId Unsigned32,
applOpenConnectionOpenTime TimeStamp,
applOpenConnectionTransport TDomain,
applOpenConnectionNearEndAddr TAddress,
applOpenConnectionNearEndFqdn Utf8String,
applOpenConnectionFarEndAddr TAddress,
Applmib Working Group Expires May 1998 [Page 29]
Internet Draft Application Management MIB 20 November 1997
applOpenConnectionFarEndFqdn Utf8String,
applOpenConnectionApplication Utf8String,
applOpenConnectionReadRequests Counter64,
applOpenConnectionReadReqsLow Counter32,
applOpenConnectionReadFailures Counter32,
applOpenConnectionBytesRead Counter64,
applOpenConnectionBytesReadLow Counter32,
applOpenConnectionLastReadTime DateAndTime,
applOpenConnectionWriteRequests Counter64,
applOpenConnectionWriteReqsLow Counter32,
applOpenConnectionWriteFailures Counter32,
applOpenConnectionBytesWritten Counter64,
applOpenConnectionBytesWritLow Counter32,
applOpenConnectionLastWriteTime DateAndTime
}
applOpenConnectionEntry OBJECT-TYPE
SYNTAX ApplOpenConnectionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applOpenConnectionEntry indicates that a
running application element has an open connection.
The entry has information describing that
connection."
INDEX { sysApplElmtRunIndex,
applOpenConnectionId }
::= { applOpenConnectionTable 1 }
applOpenConnectionId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This attribute serves to uniquely identify this open
connection in the context of the running application
element. Where suitable, the application's native
descriptor number may be used."
::= { applOpenConnectionEntry 1 }
applOpenConnectionOpenTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute records the value of sysUptime.0
when this connection was opened and this entry was
added to this table. This attribute serves as a
Applmib Working Group Expires May 1998 [Page 30]
Internet Draft Application Management MIB 20 November 1997
discontinuity indicator for the counter attributes
in this entry."
::= { applOpenConnectionEntry 2 }
applOpenConnectionTransport OBJECT-TYPE
SYNTAX TDomain
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applOpenConnectionTransport attribute
identifies the transport protocol in use for
this connection. If it is not practical
to determine the underlying transport, this
attribute's value shall have a value of {0 0}."
DEFVAL { { 0 0 } }
::= { applOpenConnectionEntry 3 }
applOpenConnectionNearEndAddr OBJECT-TYPE
SYNTAX TAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applOpenConnectionNearEndAddr attribute reports
the transport address and port information for
the near end of this connection.
If the value is not known, the value has a length
of zero."
DEFVAL { "" }
::= { applOpenConnectionEntry 4 }
applOpenConnectionNearEndFqdn OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applOpenConnectionNearEndFqdn attribute reports
the fully-qualified domain name and port information
for the near end of this connection.
If the value is not known, the value has a length
of zero."
DEFVAL { "" }
::= { applOpenConnectionEntry 5 }
applOpenConnectionFarEndAddr OBJECT-TYPE
SYNTAX TAddress
MAX-ACCESS read-only
Applmib Working Group Expires May 1998 [Page 31]
Internet Draft Application Management MIB 20 November 1997
STATUS current
DESCRIPTION
"The applOpenConnectionFarEndAddr attribute reports
the transport address and port information for
the far end of this connection.
If not known, as in the case of a connectionless
transport, the value of this attribute shall be
a zero-length string."
DEFVAL { "" }
::= { applOpenConnectionEntry 6 }
applOpenConnectionFarEndFqdn OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applOpenConnectionFarEndFqdn attribute reports
the fully-qualified domain name and port information
for the far end of this connection.
If not known, as in the case of a connectionless
transport, the value of this attribute shall be
a zero-length string."
DEFVAL { "" }
::= { applOpenConnectionEntry 7 }
applOpenConnectionApplication OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applOpenConnectionApplication attribute
identifies the application layer protocol in use.
If not known, the value of this attribute shall
be a zero-length string.
When possible, protocol names should be
those used in the 'ASSIGNED NUMBERS' [15].
For example, an SMTP mail server would use 'SMTP'."
DEFVAL { "" }
::= { applOpenConnectionEntry 8 }
applOpenConnectionReadRequests OBJECT-TYPE
SYNTAX Counter64
UNITS "read requests"
MAX-ACCESS read-only
STATUS current
Applmib Working Group Expires May 1998 [Page 32]
Internet Draft Application Management MIB 20 November 1997
DESCRIPTION
"This attribute reports the number of read requests
for this connection made by this running application
element. All read requests for this connection
by this running application element, regardless
of completion status, are included in this count.
Read requests are counted in terms of system calls,
rather than API calls.
Discontinuities in this counter can be detected by
monitoring the applOpenConnectionOpenTime attribute
for this entry."
::= { applOpenConnectionEntry 9 }
applOpenConnectionReadReqsLow OBJECT-TYPE
SYNTAX Counter32
UNITS "read requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-two
bits of applOpenConnectionReadReqs.
Discontinuities in this counter can be detected by
monitoring the applOpenConnectionOpenTime attribute
for this entry."
::= { applOpenConnectionEntry 10 }
applOpenConnectionReadFailures OBJECT-TYPE
SYNTAX Counter32
UNITS "failed read requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of failed
read requests.
Discontinuities in this counter can be detected by
monitoring the applOpenConnectionOpenTime attribute
for this entry."
::= { applOpenConnectionEntry 11 }
applOpenConnectionBytesRead OBJECT-TYPE
SYNTAX Counter64
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
Applmib Working Group Expires May 1998 [Page 33]
Internet Draft Application Management MIB 20 November 1997
DESCRIPTION
"This attribute reports the number of bytes read
from this connection by this running application
element. Only bytes successfully read are included
in this count.
Discontinuities in this counter can be detected by
monitoring the applOpenConnectionOpenTime attribute
for this entry."
::= { applOpenConnectionEntry 12 }
applOpenConnectionBytesReadLow OBJECT-TYPE
SYNTAX Counter32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-two
bits of applOpenConnectionBytesRead.
Discontinuities in this counter can be detected by
monitoring the applOpenConnectionOpenTime attribute
for this entry."
::= { applOpenConnectionEntry 13 }
applOpenConnectionLastReadTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the time of the most
recent read request made by this running application
element, regardless of completion status, for this
open connection.
If no read requests have been made by this running
application element for this connection, the value
of this attribute shall be '0000000000000000'H "
DEFVAL { '0000000000000000'H }
::= { applOpenConnectionEntry 14 }
applOpenConnectionWriteRequests OBJECT-TYPE
SYNTAX Counter64
UNITS "write requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applOpenConnectionWriteRequests attribute
Applmib Working Group Expires May 1998 [Page 34]
Internet Draft Application Management MIB 20 November 1997
reports the number of write requests, regardless of
completion status, made by this running application
element for this open connection.
Write requests are counted in terms of system calls,
rather than API calls.
Discontinuities in this counter can be detected by
monitoring the applOpenConnectionOpenTime attribute
for this entry."
::= { applOpenConnectionEntry 15 }
applOpenConnectionWriteReqsLow OBJECT-TYPE
SYNTAX Counter32
UNITS "write requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-two
bits of applOpenConnectionWriteRequests.
Discontinuities in this counter can be detected by
monitoring the applOpenConnectionOpenTime attribute
for this entry."
::= { applOpenConnectionEntry 16 }
applOpenConnectionWriteFailures OBJECT-TYPE
SYNTAX Counter32
UNITS "failed write requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of failed
write requests.
Discontinuities in this counter can be detected by
monitoring the applOpenConnectionOpenTime attribute
for this entry."
::= { applOpenConnectionEntry 17 }
applOpenConnectionBytesWritten OBJECT-TYPE
SYNTAX Counter64
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of bytes written
to this connection by this running application
Applmib Working Group Expires May 1998 [Page 35]
Internet Draft Application Management MIB 20 November 1997
element. Only bytes successfully written (no errors
reported by the API in use by the application)
are included in this count.
Discontinuities in this counter can be detected by
monitoring the applOpenConnectionOpenTime attribute
for this entry."
::= { applOpenConnectionEntry 18 }
applOpenConnectionBytesWritLow OBJECT-TYPE
SYNTAX Counter32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-two
bits of applOpenConnectionBytesWritten.
Discontinuities in this counter can be detected by
monitoring the applOpenConnectionOpenTime attribute
for this entry."
::= { applOpenConnectionEntry 19 }
applOpenConnectionLastWriteTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applOpenConnectionLastWriteTime attribute
reports the time of the most recent write request
made by this running application element, regardless
of completion status, for this open connection.
If no write requests have been made by this running
application element for this connection, the value
of this attribute shall be '0000000000000000'H "
DEFVAL { '0000000000000000'H }
::= { applOpenConnectionEntry 20 }
-- *************************************************************
--
-- applPastConGroup - history information for former
-- connections. These tables control the collection of
-- of connection history information and represent the
-- accumlated historical data.
--
-- *************************************************************
Applmib Working Group Expires May 1998 [Page 36]
Internet Draft Application Management MIB 20 November 1997
applPastConControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplPastConControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The applPastConControlTable controls the
accumulation of history information about
connections from the perspective of the running
application element. Entries in this table are
indexed by sysApplElmtRunIndex, giving control
of connection history accumulation at the
level of each running application element."
::= { applPastConGroup 1 }
ApplPastConControlEntry ::= SEQUENCE
{
applPastConControlCollect INTEGER,
applPastConControlMaxRows Unsigned32,
applPastConControlTimeLimit Unsigned32,
applPastConControlRemItems Counter32
}
applPastConControlEntry OBJECT-TYPE
SYNTAX ApplPastConControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applPastConControlEntry provides the
ability to control the retention of connection
history information by a running application."
INDEX { sysApplElmtRunIndex }
::= { applPastConControlTable 1 }
applPastConControlCollect OBJECT-TYPE
SYNTAX INTEGER { enabled (1),
frozen (2),
disabled (3) }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When the value of applPastConControlCollect is
'enabled', each time the corresponding running
application element closes an open connection a new
entry will be added to the applPastConTable.
When the value of applPastConControlCollect
is 'frozen', no new entries are added to the
applPastConTable for this running application
Applmib Working Group Expires May 1998 [Page 37]
Internet Draft Application Management MIB 20 November 1997
element, and old entries are not aged out.
When the value of applPastConControlCollect
is 'disabled', all entries are removed from
applPastConTable for this running application,
and no new entries are added."
::= { applPastConControlEntry 1 }
applPastConControlMaxRows OBJECT-TYPE
SYNTAX Unsigned32
UNITS "connection history entries"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum number of entries allowed in the
applPastConTable for this running application
element. Once the number of rows for this running
application element in the applPastConTable
reaches this value, the management subsystem will
remove the oldest entry to make room for the new
entry to be added. Entries will be removed on
the basis of oldest applExconnectionCloseTime
value first."
DEFVAL { 500 }
::= { applPastConControlEntry 2 }
applPastConControlTimeLimit OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The maximum time in seconds which an entry for this
running application element may exist in the
applExconnectionTable before it is removed.
Any entry that is older than this value will be
removed (aged out) from the table, unless the
applPastConControlCollect is set to 'frozen'.
Note that an entry may be aged out prior to
reaching this time limit if it is the oldest
entry in the table and must be removed to
make space for a new entry so as to not
exceed applExconnectionControlMaxRows, or if
the applPastConControlCollect is set to
'disabled'."
DEFVAL { 7200 }
::= { applPastConControlEntry 3 }
Applmib Working Group Expires May 1998 [Page 38]
Internet Draft Application Management MIB 20 November 1997
applPastConControlRemItems OBJECT-TYPE
SYNTAX Counter32
UNITS "connection history entries"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applPastConControlRemItems attribute
reports the number of applPastConControlTable
entries for this running application element
that were deleted in order to make room for a new
history entry.
This count does NOT include entries deleted for the
following reasons:
- the corresponding
applPastConControlCollect attribute
has been set to 'disabled'
- the entry has been in the table longer
that the time limit indicated
by the corresponding
applPastConControlTimeLimit.
"
::= { applPastConControlEntry 4 }
-- *************************************************************
--
-- applPastConTable - Table of former connections
--
-- *************************************************************
applPastConTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplPastConEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The applPastConTable provides history
information about connections from the perspective
of the running application element. Entries in
this table are indexed by sysApplElmtRunIndex and
by applPastConId, which serves to uniquely
identify each former connection in the context of
a running application element.
Note that the value of applPastConId is
independent of the value applConnectionId
had when this connection was active.
Applmib Working Group Expires May 1998 [Page 39]
Internet Draft Application Management MIB 20 November 1997
Entries for closed connections for a given running
application element can be added to this table only
if the running application element's entry in the
applPastConControlTable has the value 'enabled'
for the attribute applPastConControlCollect.
Entries for closed connections are removed under
the following circumstances:
- the running application element no longer
exists
- the corresponding
applPastConControlCollect attribute
has been set to 'disabled'
- the entry has been in the table longer
that the time limit
indicated by the corresponding
applPastConControlTimeLimit and the
value of applPastConControlCollect is
not 'frozen'
- this is the oldest entry for the running
application element in question and the
addition of a new element would otherwise
cause applPastConControlMaxRows to
be exceeded for this running application
element.
- a value of applPastConId has been re-
used. Note that under normal circumstances,
this is unlikely.
Removal/replacement of an entry under the
two conditions causes the corresponding
applPastConControlRemItems to be
incremented."
::= { applPastConGroup 2 }
ApplPastConEntry ::= SEQUENCE
{
applPastConId Unsigned32,
applPastConOpenTime DateAndTime,
applPastConCloseTime DateAndTime,
applPastConTransport TDomain,
applPastConNearEndAddr TAddress,
Applmib Working Group Expires May 1998 [Page 40]
Internet Draft Application Management MIB 20 November 1997
applPastConNearEndFqdn Utf8String,
applPastConFarEndAddr TAddress,
applPastConFarEndFqdn Utf8String,
applPastConApplication Utf8String,
applPastConReadRequests Counter64,
applPastConReadReqsLow Counter32,
applPastConReadFailures Counter32,
applPastConBytesRead Counter64,
applPastConBytesReadLow Counter32,
applPastConLastReadTime DateAndTime,
applPastConWriteRequests Counter64,
applPastConWriteReqsLow Counter32,
applPastConWriteFailures Counter32,
applPastConBytesWritten Counter64,
applPastConBytesWritLow Counter32,
applPastConLastWriteTime DateAndTime
}
applPastConEntry OBJECT-TYPE
SYNTAX ApplPastConEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applPastConEntry indicates that a running
application element once had an open connection,
which is now closed. The entry has information
describing that connection."
INDEX { sysApplElmtRunIndex,
applPastConId }
::= { applPastConTable 1 }
applPastConId OBJECT-TYPE
SYNTAX Unsigned32
--
-- ISSUE: should zero be excluded from the range?
--
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute serves to uniquely identify this
closed connection in the context of the running
application element. This attribute has no other
semantics.
Note that the value of applPastConId is
independent of the value applConnectionId
had when this connection was active.
Applmib Working Group Expires May 1998 [Page 41]
Internet Draft Application Management MIB 20 November 1997
In issuing this index value, the implementation
must avoid re-issuing an index value which has
already been assigned to an entry which has not yet
been deleted due to age or space considerations."
::= { applPastConEntry 1 }
applPastConOpenTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute records the time when this
connection was originally opened. Note that
this information is quite different from
applOpenConnectionOpenTime, which is used
for the detection of counter discontinuities."
::= { applPastConEntry 2 }
applPastConCloseTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute records the time when this
connection was closed."
::= { applPastConEntry 3 }
applPastConTransport OBJECT-TYPE
SYNTAX TDomain
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applPastConTransport attribute identifies
the transport protocol that was in use for this
former connection. If the trasport protocol could
not be determined, the value { 0 0 } is used."
DEFVAL { { 0 0 } }
::= { applPastConEntry 4 }
applPastConNearEndAddr OBJECT-TYPE
SYNTAX TAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applPastConNearEndAddr attribute reports
the transport address and port information for
the near end of this former connection.
Applmib Working Group Expires May 1998 [Page 42]
Internet Draft Application Management MIB 20 November 1997
If the information could not be determined, the
value shall be a zero-length string."
DEFVAL { "" }
::= { applPastConEntry 5 }
applPastConNearEndFqdn OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applPastConNearEndFqdn attribute reports
the fully-qualified domain name and port information
for the near end of this former connection.
If the information could not be determined, the
value shall be a zero-length string."
DEFVAL { "" }
::= { applPastConEntry 6 }
applPastConFarEndAddr OBJECT-TYPE
SYNTAX TAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applPastConFarEnd attribute reports
the transport address and port information for
the far end of this former connection.
If not known, as in the case of a connectionless
transport, the value of this attribute shall be
a zero-length string."
DEFVAL { "" }
::= { applPastConEntry 7 }
applPastConFarEndFqdn OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applPastConFarEnd attribute reports
the transport address and port information for
the far end of this former connection.
If not known, as in the case of a connectionless
transport, the value of this attribute shall be
a zero-length string."
DEFVAL { "" }
::= { applPastConEntry 8 }
Applmib Working Group Expires May 1998 [Page 43]
Internet Draft Application Management MIB 20 November 1997
applPastConApplication OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applPastConApplication attribute
identifies the application layer protocol that was
in use. Where possible, the values defined in [15]
shall be used. If not known, the value of this
attribute shall be a zero-length string."
DEFVAL { "" }
::= { applPastConEntry 9 }
applPastConReadRequests OBJECT-TYPE
SYNTAX Counter64
UNITS "read requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of read requests
for this connection made by this running application
element. All read requests for this connection
by this running application element, regardless
of completion status, are included in this count.
Read requests are counted in terms of system calls,
rather than API calls."
::= { applPastConEntry 10 }
applPastConReadReqsLow OBJECT-TYPE
SYNTAX Counter32
UNITS "read requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-two
bits of applPastConReadRequests."
::= { applPastConEntry 11 }
applPastConReadFailures OBJECT-TYPE
SYNTAX Counter32
UNITS "failed read requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of failed
read requests."
::= { applPastConEntry 12 }
Applmib Working Group Expires May 1998 [Page 44]
Internet Draft Application Management MIB 20 November 1997
applPastConBytesRead OBJECT-TYPE
SYNTAX Counter64
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of bytes read
from this connection by this running application
element. Only bytes successfully read are included
in this count. "
::= { applPastConEntry 13 }
applPastConBytesReadLow OBJECT-TYPE
SYNTAX Counter32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-two
bits of applPastConBytesRead."
::= { applPastConEntry 14 }
applPastConLastReadTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the time of the most
recent read request made by this running application
element, regardless of completion status, for this
former connection.
If no read requests have been made by this running
application element for this connection, the value
of this attribute shall be '0000000000000000'H "
DEFVAL { '0000000000000000'H }
::= { applPastConEntry 15 }
applPastConWriteRequests OBJECT-TYPE
SYNTAX Counter64
UNITS "write requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applExconnectionWriteRequests attribute
reports the number of write requests, regardless of
completion status, made by this running application
element for this former connection.
Applmib Working Group Expires May 1998 [Page 45]
Internet Draft Application Management MIB 20 November 1997
Write requests are counted in terms of system calls,
rather than API calls."
::= { applPastConEntry 16 }
applPastConWriteReqsLow OBJECT-TYPE
SYNTAX Counter32
UNITS "write requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-two
bits of applExconnectionWriteRequests."
::= { applPastConEntry 17 }
applPastConWriteFailures OBJECT-TYPE
SYNTAX Counter32
UNITS "failed write requests"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of
failed write requests."
::= { applPastConEntry 18 }
applPastConBytesWritten OBJECT-TYPE
SYNTAX Counter64
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the number of bytes written
to this former connection by this running
application element. Only bytes successfully
written (no errors reported by the API in use by
the application) are included in this count."
::= { applPastConEntry 19 }
applPastConBytesWritLow OBJECT-TYPE
SYNTAX Counter32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-two
bits of applExconnectionBytesWritten."
::= { applPastConEntry 20 }
applPastConLastWriteTime OBJECT-TYPE
Applmib Working Group Expires May 1998 [Page 46]
Internet Draft Application Management MIB 20 November 1997
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applPastConLastWriteTime attribute reports
the time of the most recent write request made by
this running application element, regardless of
completion status, for this former connection.
If no write requests have been made by this running
application element for this connection, the value
of this attribute shall be '0000000000000000'H "
DEFVAL { '0000000000000000'H }
::= { applPastConEntry 21 }
-- *************************************************************
--
-- applTransactionControlTable - common and control
-- information for transaction stream monitoring
--
-- *************************************************************
applTransactionControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplTransactionControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The applTransactionControlTable contains common
information for the control of transaction
statistic accumulation."
::= { applTransactionGroup 1 }
ApplTransactionControlEntry ::= SEQUENCE {
applTransactStreamId Unsigned32,
applTransactStreamPointer RowPointer,
applTransactStreamDescr Utf8String,
applTransactStreamUnitOfWork Utf8String,
applTransactStreamInvCumTime Counter32,
applTransactStreamPrfCumTime Counter32,
applTransactStreamUpTime TimeStamp
}
applTransactionControlEntry OBJECT-TYPE
SYNTAX ApplTransactionControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
Applmib Working Group Expires May 1998 [Page 47]
Internet Draft Application Management MIB 20 November 1997
"An applTransactionControlEntry contains control
information for a single transaction stream. A
transaction stream can be a network connection,
file, or other source of transactions."
INDEX { sysApplElmtRunIndex,
applTransactStreamId }
::= { applTransactionControlTable 1 }
applTransactStreamId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applTransactStreamId serves to uniquely
identify a transaction stream in the context of
a given running application element."
::= { applTransactionControlEntry 1 }
applTransactStreamPointer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactStreamPointer attribute
identifies the network connection or file
I/O stream over which these transactions are
carried. This will normally point to an entry
in the applOpenFilesTable or to an entry in the
applOpenConnectionsTable. If this transaction
stream is not associated with a specific file or
connection, this attribute's value shall be
{ 0 0 }."
::= { applTransactionControlEntry 2 }
applTransactStreamDescr OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactStreamDescr attribute provides
a human-readable description of this transaction
stream.
If no descriptive information is available, this
attribute's value shall be a zero-length string."
DEFVAL { "" }
::= { applTransactionControlEntry 3 }
Applmib Working Group Expires May 1998 [Page 48]
Internet Draft Application Management MIB 20 November 1997
applTransactStreamUnitOfWork OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactStreamUnitOfWork attribute
provides a human-readable definition of what the
unit of work is for this transaction stream.
If no descriptive information is available, this
attribute's value shall be a zero-length string."
DEFVAL { "" }
::= { applTransactionControlEntry 4 }
applTransactStreamInvCumTime OBJECT-TYPE
SYNTAX Counter32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactStreamInvCumTime attribute
reports the cumulative sum of the times measured
between the transmission of requests and the
receipt of the corresponding responses.
Discontinuities in this counter can be detected
by monitoring the applTransactStreamUpTime for
this row."
::= { applTransactionControlEntry 5 }
applTransactStreamPrfCumTime OBJECT-TYPE
SYNTAX Counter32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactStreamPrfCumTime attribute
reports the cumulative sum of the times measured
between receipt of requests and the transmission
of the corresponding responses.
Discontinuities in this counter can be detected
by monitoring the applTransactStreamUpTime for
this row."
::= { applTransactionControlEntry 6 }
applTransactStreamUpTime OBJECT-TYPE
SYNTAX TimeStamp
Applmib Working Group Expires May 1998 [Page 49]
Internet Draft Application Management MIB 20 November 1997
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactStreamUpTime attribute records
the value of sysUpTime.0 when this transaction
stream entry was created and serves as a
discontinuity indicator for all of the counters
in this row."
::= { applTransactionControlEntry 7 }
-- *************************************************************
--
-- applTransactFlowTable
--
-- *************************************************************
applTransactFlowTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplTransactFlowEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The applTransactFlowTable contains entries,
organized by running application element, direction
of flow, and type (request/response) for each
open transaction stream.
The simple model of a transaction used here looks
like this:
invoker | Request | performer
| - - - - - - > |
| |
| Response |
| < - - - - - - |
| |
Since in some protocols it is possible for an entity
to take on both the invoker and performer roles,
information here is accumulated for transmitted
and received requests, as well as for transmitted
and received responses. Counts are maintained
for both transactions and bytes transferred."
::= { applTransactionGroup 2 }
ApplTransactFlowEntry ::= SEQUENCE {
applTransactFlowDirection INTEGER,
applTransactFlowReqRsp INTEGER,
Applmib Working Group Expires May 1998 [Page 50]
Internet Draft Application Management MIB 20 November 1997
applTransactFlowTrans Counter64,
applTransactFlowTransLow Counter32,
applTransactFlowBytes Counter64,
applTransactFlowBytesLow Counter32,
applTransactFlowTime DateAndTime }
applTransactFlowEntry OBJECT-TYPE
SYNTAX ApplTransactFlowEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applTransactFlowEntry reports transaction
throughput information for requests or response
in a particular direction (transmit / receive)
for a transaction stream.
Entries in this table correspond to those in the
applTransactionControlTable with identical values
for the sysApplElmtRunIndex and applTransactStreamId.
For all counter objects in one of these entries, the
corresponding (same value for sysApplElmtRunIndex and
applTransactStreamId) applTransactStreamUpTime object
serves as a discontinuity indicator. "
INDEX { sysApplElmtRunIndex,
applTransactStreamId,
applTransactFlowDirection,
applTransactFlowReqRsp }
::= { applTransactFlowTable 1 }
applTransactFlowDirection OBJECT-TYPE
SYNTAX INTEGER { transmit(1),
receive(2) }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The applTransactFlowDirection index serves to
identify an entry as containing information
pertaining to the transmit (1) or receive (2)
flow of a transaction stream. "
::= { applTransactFlowEntry 1 }
applTransactFlowReqRsp OBJECT-TYPE
SYNTAX INTEGER { request(1),
response(2) }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
Applmib Working Group Expires May 1998 [Page 51]
Internet Draft Application Management MIB 20 November 1997
"The value of the applTransactFlowReqRsp index
indicates whether this entry contains information
on requests (1), or responses (2)."
::= { applTransactFlowEntry 2 }
applTransactFlowTrans OBJECT-TYPE
SYNTAX Counter64
UNITS "transactions"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactFlowTrans attribute reports
the number of request/response (as indicated
by the applTransactFlowReqRsp index) transactions
received/generated (as indicated by the
applTransactFlowDirection index) handled by this
application element on this transaction stream.
Discontinuities in this counter can be detected
by monitoring the corresponding instance of
applTransactStreamUpTime."
::= { applTransactFlowEntry 3 }
applTransactFlowTransLow OBJECT-TYPE
SYNTAX Counter32
UNITS "transactions"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-two
bits of applTransactFlowTrans.
Discontinuities in this counter can be detected
by monitoring the applTransactStreamUpTime for
this row."
::= { applTransactFlowEntry 4 }
applTransactFlowBytes OBJECT-TYPE
SYNTAX Counter64
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactFlowBytes attribute reports
the number of request/response (as indicated
by the applTransactFlowReqRsp index) bytes
received/generated (as indicated by the
applTransactFlowDirection index) handled by this
Applmib Working Group Expires May 1998 [Page 52]
Internet Draft Application Management MIB 20 November 1997
application element on this transaction stream.
All application layer bytes are included in this
count, including any application layer wrappers,
headers, or other overhead.
Discontinuities in this counter can be detected
by monitoring the instance of applTransactStreamUpTime
corresponding to this row."
::= { applTransactFlowEntry 5 }
applTransactFlowBytesLow OBJECT-TYPE
SYNTAX Counter32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute corresponds to the low thirty-two
bits of applTransactFlowBytes.
Discontinuities in this counter can be detected
by monitoring the instance of applTransactStreamUpTime
corresponding to this row."
::= { applTransactFlowEntry 6 }
applTransactFlowTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactFlowTime attribute records the
time of the processing (receipt or transmission
as indicated by the applTransactFlowDirection
index) by this running application element of
the most recent request/response (as indicated
by the applTransactFlowReqRsp index) on this
transaction stream.
If no requests/reponses been received/transmitted
by this running application element over this
transaction stream, the value of this attribute
shall be '0000000000000000'H "
DEFVAL { '0000000000000000'H }
::= { applTransactFlowEntry 7 }
--
-- applTransactKindTable - transaction statistics broken down
-- by individual transaction types
Applmib Working Group Expires May 1998 [Page 53]
Internet Draft Application Management MIB 20 November 1997
--
applTransactKindTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplTransactKindEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The applTransactKindTable provides transaction
statistics broken down by individual transaction
types. The definition of the transaction types
is specific to the application protocol in use,
and may be documented in the form of an applicability
statement. "
::= { applTransactionGroup 3 }
ApplTransactKindEntry ::= SEQUENCE
{
applTransactKind Utf8String,
applTransactKindTrans Counter64,
applTransactKindTransLow Counter32,
applTransactKindBytes Counter64,
applTransactKindBytesLow Counter32,
applTransactKindTime DateAndTime
}
applTransactKindEntry OBJECT-TYPE
SYNTAX ApplTransactKindEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applTransactKindEntry reports information for
a specific running application element's use of
a specific transaction stream in a particular
direction in requests or responses (as indicated
by the applTransactFlowReqRsp index) broken down by
transaction kind, as indicated by the applTransact
Kind index. Discontinuities in any of the counters
in an entry can be detected by monitoring the
instance of applTransactStreamUpTime corresponding
to this row."
INDEX { sysApplElmtRunIndex,
applTransactStreamId,
applTransactFlowDirection,
applTransactFlowReqRsp,
applTransactKind }
::= { applTransactKindTable 1 }
applTransactKind OBJECT-TYPE
SYNTAX Utf8String
Applmib Working Group Expires May 1998 [Page 54]
Internet Draft Application Management MIB 20 November 1997
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The applTransactKind index is the human-readable
identifier for a particular transaction type
within the context of an application protocol.
The values to be used for a particular protocol
may be identified in an applicability statement."
::= { applTransactKindEntry 1 }
applTransactKindTrans OBJECT-TYPE
SYNTAX Counter64
UNITS "transactions"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactKindTrans attribute reports
the number of request/response (as indicated
by the applTransactFlowReqRsp index) transactions
received/generated (as indicated by the
applTransactFlowDirection index) handled by this
application element on this transaction stream
for this transaction kind.
Discontinuities in this counter can be detected
by monitoring the corresponding instance of
applTransactStreamUpTime."
::= { applTransactKindEntry 2 }
applTransactKindTransLow OBJECT-TYPE
SYNTAX Counter32
UNITS "transactions"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactKindTransLow attribute reports
the low thrity-two bits of applTransactKindTrans.
Discontinuities in this counter can be detected
by monitoring the instance of applTransactStreamUpTime
corresponding to this row."
::= { applTransactKindEntry 3 }
applTransactKindBytes OBJECT-TYPE
SYNTAX Counter64
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
Applmib Working Group Expires May 1998 [Page 55]
Internet Draft Application Management MIB 20 November 1997
DESCRIPTION
"The applTransactKindBytes attribute reports
the number of request/response (as indicated
by the applTransactFlowReqRsp index) bytes
received/generated (as indicated by the
applTransactFlowDirection index) handled by this
application element on this transaction stream
for this transaction kind.
All application layer bytes are included in this
count, including any application layer wrappers,
headers, or other overhead.
Discontinuities in this counter can be detected
by monitoring the instance of applTransactStreamUpTime
corresponding to this row."
::= { applTransactKindEntry 4 }
applTransactKindBytesLow OBJECT-TYPE
SYNTAX Counter32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactKindBytesLow attribute corresponds
to the low thirty-two bits of applTransactKindBytes.
Discontinuities in this counter can be detected
by monitoring the instance of applTransactStreamUpTime
corresponding to this row."
::= { applTransactKindEntry 5 }
applTransactKindTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applTransactKindTime attribute records the
time of the processing (receipt or transmission
as indicated by the applTransactFlowDirection
index) by this running application element of
the most recent request/response (as indicated
by the applTransactFlowReqRsp index) of this
kind of transaction on this transaction stream.
If no requests/reponses of this kind been
received/transmitted by this running application
element over this transaction stream, the value
Applmib Working Group Expires May 1998 [Page 56]
Internet Draft Application Management MIB 20 November 1997
of this attribute shall be '0000000000000000'H "
DEFVAL { '0000000000000000'H }
::= { applTransactKindEntry 6 }
-- *************************************************************
--
-- applElmtRunControlGroup - monitor and control running
-- application elements
--
-- *************************************************************
applElmtRunStatusTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplElmtRunStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provies information on running
application elements, complementing information
available in the correspondingly indexed
sysApplElmtRunTable [10]."
::= { applElmtRunControlGroup 1 }
ApplElmtRunStatusEntry ::= SEQUENCE {
applElmtRunStatusSuspended TruthValue,
applElmtRunStatusHeapUsage Gauge32,
applElmtRunStatusOpenConnections Gauge32,
applElmtRunStatusLastErrorMsg Utf8String,
applElmtRunStatusLastErrorTime DateAndTime }
applElmtRunStatusEntry OBJECT-TYPE
SYNTAX ApplElmtRunStatusEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applElmtRunStatusEntry contains information
to support the control and monitoring of a single
running application element."
INDEX { sysApplElmtRunIndex }
::= { applElmtRunStatusTable 1 }
applElmtRunStatusSuspended OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Applmib Working Group Expires May 1998 [Page 57]
Internet Draft Application Management MIB 20 November 1997
"The applElmtRunStatusSuspended attribute reports
whether processing by this running application
element has been suspended, whether by management
request or by other means."
::= { applElmtRunStatusEntry 1 }
applElmtRunStatusHeapUsage OBJECT-TYPE
SYNTAX Gauge32
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applElmtRunStatusHeapUsage reports the
current approximate heap usage by this running
application element."
::= { applElmtRunStatusEntry 2 }
applElmtRunStatusOpenConnections OBJECT-TYPE
SYNTAX Gauge32
UNITS "connections"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applElmtRunStatusOpenConnections reports
the current number of open connections in use
by this running application element."
::= { applElmtRunStatusEntry 3 }
applElmtRunStatusLastErrorMsg OBJECT-TYPE
SYNTAX Utf8String
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applElmtRunStatusLastErrorMessage attribute
reports the most recent error message (typically
written to stderr or a system error logging
facility) from this running application element.
If no such message has yet been generated, the value
of this attribute shall be a zero-length string."
DEFVAL { "" }
::= { applElmtRunStatusEntry 4 }
applElmtRunStatusLastErrorTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The applElmtRunStatusLastErrorTime attribute
Applmib Working Group Expires May 1998 [Page 58]
Internet Draft Application Management MIB 20 November 1997
reports the time of the most recent error message
in applElmtRunStatusLastErrorMsg.
If no such message has yet been generated, the value
of this attribute shall be '0000000000000000'H "
DEFVAL { '0000000000000000'H }
::= { applElmtRunStatusEntry 5 }
-- *************************************************************
--
-- applElmtRunControlTable - control running application
-- elements
--
-- *************************************************************
applElmtRunControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplElmtRunControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table provides the ability to control
application elements, complementing information
available in the correspondingly indexed
sysApplElmtRunTable [10]."
::= { applElmtRunControlGroup 2 }
ApplElmtRunControlEntry ::= SEQUENCE {
applElmtRunControlSuspend TruthValue,
applElmtRunControlReconfigure TestAndIncr,
applElmtRunControlTerminate TruthValue }
applElmtRunControlEntry OBJECT-TYPE
SYNTAX ApplElmtRunControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An applElmtRunControlEntry contains information
to support the control of a single running
application element."
INDEX { sysApplElmtRunIndex }
::= { applElmtRunControlTable 1 }
applElmtRunControlSuspend OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
Applmib Working Group Expires May 1998 [Page 59]
Internet Draft Application Management MIB 20 November 1997
DESCRIPTION
"Setting this variable to 'true' requests the
suspension of processing by this running application
element. Setting this variable to 'false' requests
that processing be resumed. The effect, if any,
will be reported by the applElmtRunStatusSuspended
attribute."
DEFVAL { false }
::= { applElmtRunControlEntry 1 }
applElmtRunControlReconfigure OBJECT-TYPE
SYNTAX TestAndIncr
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Changing the value of this variable requests
that the running application element re-load
its configuration (like SIGHUP for many
UNIX-based daemons)."
::= { applElmtRunControlEntry 2 }
applElmtRunControlTerminate OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting the value of applElmtRunControlTerminate
to 'true' requests that the running application
element terminate processing and exit in an
orderly manner. This is a 'polite' shutdown
request."
DEFVAL { false }
::= { applElmtRunControlEntry 3 }
--
-- ISSUE: CONFORMANCE STATEMENTS NEEDED
--
END
6. Implementation Issues
Unlike the system application MIB [10], in many environments support
for much of this MIB requires instrumentation built into the managed
resource. Some tables may be implemented by a single monitor
process; for others, the implementation may be distributed within the
Applmib Working Group Expires May 1998 [Page 60]
Internet Draft Application Management MIB 20 November 1997
managed system with the resources being managed.
As a practical matter, this means that the management infrastructure
of the managed system must support different subagents taking
responsibility for different rows of a single table. This can be
supported by Agentx [13], as well as some other subagent protocols
[14].
The sysApplRunElmtIndex is the key connection between this MIB and
the systems application MIB. Implementations of these two MIBs
intended to run concurrently on a given platform must employ a
consistent policy for assigning this value to running application
elements.
Some of the objects defined in this MIB may carry a high run-time
cost in some environments. For example, tracking transaction elapsed
time could be expensive if it required two kernel calls (start and
finish) per transaction. Similarly, maintaining tables of per-
transaction information, rather than aggregating information by
transaction type or transaction stream, could have significant
storage and performance impacts.
Unless a collision-free mechanism for allocating service instance
indexes is in place, the structure of the service-level tables makes
an index-reservation mechanism necessary.
7. Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Applmib Working Group Expires May 1998 [Page 61]
Internet Draft Application Management MIB 20 November 1997
8. Acknowledgements
This document was produced by the Application MIB working group.
The author gratefully acknowledges the comments and contributions of
the following individuals:
Harrie Hazewinkel
Carl Kalbfleisch
Cheryl Krupczak
John Saperia
Juergen Schoenwaelder
9. Security Considerations
By making potentially sensitive information externally accessible,
the capabilities supported by the MIB have the potential of becoming
security problems.
The tables in this MIB are organized to separate sensitive control
capabilities from less sensitive usage information. For example, the
objects to control application suspend/resume are separated from
those to handle reconfiguration, which in turn are distinct from
those for termination. This recognizes the need to support
configurations where the level of authorization needed by a manager
to do a "reconfigure" might be substantially less than the level
needed to terminate an application element. By keeping these in
separate columns, we make it possible to set up access control that
allows, for example, "reconfigure" but not "kill".
The MIB is structured to be useful for managers with read-only access
rights.
The capabilities supported by this MIB include several that may be of
value to a security administrator. These include the ability to
monitor the level of usage of a given application, and to check the
integrity of application components.
10. References
[1] Grillo, P., and S. Waldbusser, "Host Resources MIB", RFC 1514,
September 1993.
[2] Freed, N., and S. Kille, "Network Services Monitoring MIB", RFC
1565, January 1994.
[3] Freed, N., and S. Kille, "Mail Monitoring MIB", RFC 1566, January
1994.
Applmib Working Group Expires May 1998 [Page 62]
Internet Draft Application Management MIB 20 November 1997
[4] Brower, D., Purvy, R., Daniel, A., Sinykin, M., and J. Smith,
"Relational Database Management System (RDBMS) Management
Information Base (MIB) using SMIv2", RFC 1697, August 1994.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
of Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1902, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1903, January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Conformance Statements for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1904, January 1996.
[8] C. Kalbfleisch, "Applicability of Standards Track MIBs to
Management of World Wide Web Servers", RFC 2039, November 1996.
[9] Yergeau, F., "UTF-8, a transformation format of Unicode and ISO
10646", RFC 2044, October 1996.
[10] Krupczak, C., and J. Saperia, "Definitions of System-Level
Managed Objects for Applications", <draft-ietf-applmib-
sysapplmib-09.txt>, October 1997.
[11] ITU-T Recommendation X.744 | ISO/IEC IS 10164-18:1996,
Information Technology - Open Systems Interconnection - Systems
Management: Software Management Function, 1996.
[12] IEEE P1387.2, POSIX System Administration - Part 2: Software
Administration. (Draft)
[13] Daniele, M., Francisco, D., and B. Wijnen, "Agent Extensibility
(AgentX) Protocol", <draft-ietf-agentx-pro-04.txt>, June, 1997.
[14] Rose, M., "SNMP MUX Protocol and MIB", RFC 1227, May 1991.
[15] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", RFC 1700, STD 2,
October, 1994.
[16] Hovey, R., and S. Bradner, "The Organizations Involved in the
IETF Standards Process", BCP 11, RFC 2028, October 1996.
[17] ARM Working Group, "Application Response Measurement (ARM) API
Guide, Version 2", September, 1997.
Applmib Working Group Expires May 1998 [Page 63]
Internet Draft Application Management MIB 20 November 1997
11. Editors' Addresses
Carl Kalbfleisch
Verio, Inc.
1950 Stemmons Frwy
2026 INFOMART
Dallas, TX 75207
USA
Phone: +1 972-238-8303
Fax: +1 214-672-7275
EMail: cwk@verio.net
Cheryl Krupczak
Empire Technologies, Inc.
541 Tenth Street, NW Suite 169
Atlanta, GA 30318
USA
Phone: +1 770-384-0184
EMail: cheryl@empiretech.com
Randy Presuhn
BMC Software, Inc.
Silicon Valley Division
(formerly PEER Networks)
1190 Saratoga Avenue
San Jose, CA 95129
USA
Phone: +1 408-556-0720
Fax: +1 408-556-0735
EMail: rpresuhn@bmc.com
Jon Saperia
BGS Systems, Inc.
One First Avenue
Waltham, MA 02254
USA
Phone: +1 617-663-4682
Fax: +1 617-890-0000
EMail: saperia@networks.bgs.com
Applmib Working Group Expires May 1998 [Page 64]
Internet Draft Application Management MIB 20 November 1997
12. Issues and List of Things Left To Be Done
The following issues remain to be resolved.
- At Munich there was general agreement that it would be
desirable to be able to access (aggregated) transaction
statistics organized by service instance. Can this
somehow be collapsed with the current tables?
- Need further discussion of order of indexes on
transaction flow and transaction kind tables. Has
implications for both access control and for bulk
retrieval.
- Should applOpenConnectionApplication be a human-
readable thing or something like an RMON protocol
identifier?
- Decide which object definitions should be borrowed or
reference from the ARM work.
- Do we need to report current mode in addition to open
mode? For example, fcntl() can change append mode.
(With this revision of the draft, we've reduced the
alternatives to read and write, but the issue remains.)
- The syntax for the identifiers for transport and
application protocol identifiers should be narrowed
down a bit.
- MIB definitions to support the following capabilities
are still needed:
- system calls?
Strawman: close this issue, no one has argued
that we need these.
- stack penetration?
Strawman: close this issue, no one has argued
that we really need this.
- other networking resources?
Strawman: close this issue, what is in the MIB
appears to be enough.
- dependency information
- logging capability
Applmib Working Group Expires May 1998 [Page 65]
Internet Draft Application Management MIB 20 November 1997
- align with stdguide requirements
- add conformance clauses
- Should applOpenconnectionNearEnd (and similar
attributes) be Taddress or fqdn?
- should control capabilities be defined at an
application, service, or process level in this MIB?
The following items were removed from the document's scope section:
- other resources are open to discussion, possibilities
include:
- various system calls;
- stack penetration;
- networking resources.
13. Full Copyright Statement
Copyright (C) The Internet Society (1997). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
Applmib Working Group Expires May 1998 [Page 66]
Internet Draft Application Management MIB 20 November 1997
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Applmib Working Group Expires May 1998 [Page 67]
