TPM-MIB Table View

This table is used to describe and link sets of
performance metrics and protocols to an entry in
the application directory.  This table, with the
tpmMetricDefTable, describes the capability of
the agent to collection sub-application level
data related to each entry in the
apmAppDirectoryTable.
          
This table lists the protocol transactions and their
corresponding performance metrics that this agent
has the capability to compute and collect, for the specified
application.  There is one entry in this table for each such
application, protocol transaction, and metric combination
supported by this agent.  The entries in this
table represent the metrics that are collected for each
protocol transaction that comprise the application.
The agent should boot up with this table pre-configured
with those combinations of applications, protocol
transactions, and metrics that it knows about and wishes to
          
monitor.  Implementations must populate the table with all
possible application, protocol transaction, and metric
combinations and have the default configuration objects
set to supportedOff(2).  This table does not support the
creation of new combinations by the management application.
          
The deletion of an entry in the apmAppDirectoryTable will
cause the removal of entries from this table.  These entries
must be removed because the appLocalIndex value will no
longer be visible in the apmAppDirectoryTable.  When an entry
is created in the apmAppDirectoryTable and the agent has the
ability to support metrics for these protocol transactions,
the appropriate entries must be made in the
tpmTransMetricDefTable.

The tpmMetricDefTable describes the metrics
available to the TPM-MIB.  The tpmMetricDefTable
can define metrics by referencing existing IETF,
ITU, and other standards organizations' documents,
including enterprise-specific documents.
          
Examples of appropriate references include the
ITU-T Recommendation Y.1540 [Y.1540] on IP
packet transfer performance metrics and the
IETF documents from the IPPM WG; e.g., RFC2681
on the round trip delay metric [RFC2681] or
RFC3393 on the delay variation metric [RFC3393].
Other examples include RFC2679 [RFC2679], RFC2680
[RFC2680], and RFC3432 [RFC3432].  Although no
specific metric is mandatory, implementations
should, at a minimum, support a round-trip delay
and a round-trip loss metric.
          
This table contains one row per metric supported by this
agent, and it should be populated during system
initialization.

The tpmAggrReportCntrlTable is the controlling entry
that manages the population of studies in the Transport
Aggregate Report for selected interfaces, metrics, and
transaction protocols and applications.
          
Note that this is not like the typical RMON
controlTable and dataTable in which each entry creates
its own data table.  Each entry in this table enables the
creation of multiple data tables on a study basis.  For each
interval, the study is updated in place, and the current
data content of the table becomes invalid.
          
The control table entries are persistent across
system reboots.

This table contains transport performance metric
studies for each of the control table entries in
tpmAggrReportCntrlTable.  These studies are
          
provided based on the selections and parameters
found for the entry in the
tpmAggregateReportCntrlTable.
          
The performance statistics are specified in the
tpmTransMetricDirTable associated with the
application in question and indexed by
appLocalIndex and tpmTransMetricIndex.

This table will contain entries associated with an
apmReportControlEntry that consitute a current 'snapshot'
of the metrics being collected in association with
a set of TPM-related application transactions.
This table contains all sub-flow metrics for transactions
that have been started but have not yet finished (i.e.,
current) and a history of those that have finished (i.e.,
completed).  It may not always be obvious from the context
whether a transaction is currently in-progress or has
been completed.  Therefore, the completion status of a
          
transaction is indicated by the value of
the tpmCurReportCompletion object.

This table contains all sub-flow metrics for transactions
that have been tagged by the apmExceptionTable filter
as having had poor performance.