TPM-MIB
File:
TPM-MIB.mib (75505 bytes)
Imported modules
Imported symbols
Defined Types
| TpmTransactionMetricIndex |
|
| An index used to identify an entry in the
tpmTransMetricDir table uniquely. Each such entry defines
the protocol transaction and metric instance to be
monitored for a specific application. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
1..65535 |
|
| TpmMetricDefID |
|
| An index that identifies through reference to a specific
performance metrics. The metrics are referenced
through their type (connect, delay, loss, etc.), their
directional characteristics (one-way, round trip, etc.),
their name, and their reference to a documented definition. |
| TEXTUAL-CONVENTION |
|
|
|
| |
Unsigned32 |
1..2147483647 |
|
| TpmTransMetricDirEntry |
|
| SEQUENCE |
|
|
|
| |
tpmTransMetricAppLocalIndex |
AppLocalIndex |
|
| |
tpmTransMetricIndex |
TpmTransactionMetricIndex |
|
| |
tpmTransMetricProtocolIndex |
Unsigned32 |
|
| |
tpmTransMetricMetricIndex |
Unsigned32 |
|
| |
tpmTransMetricDirConfig |
INTEGER |
|
| TpmMetricDefEntry |
|
| SEQUENCE |
|
|
|
| |
tpmMetricDefinitionID |
TpmMetricDefID |
|
| |
tpmMetricDefType |
INTEGER |
|
| |
tpmMetricDefDirType |
INTEGER |
|
| |
tpmMetricDefName |
SnmpAdminString |
|
| |
tpmMetricDefReference |
SnmpAdminString |
|
| |
tpmMetricDefGlobalID |
OBJECT IDENTIFIER |
|
| TpmAggrReportCntrlEntry |
|
| SEQUENCE |
|
|
|
| |
tpmAggrReportCntrlIndex |
Unsigned32 |
|
| |
tpmAggrReportCntrlApmCntrlIndex |
Unsigned32 |
|
| |
tpmAggrReportCntrlDataSource |
DataSourceOrZero |
|
| |
tpmAggrReportCntrlAggrType |
TransactionAggregationType |
|
| |
tpmAggrReportCntrlInterval |
Unsigned32 |
|
| |
tpmAggrReportCntrlReqSize |
Unsigned32 |
|
| |
tpmAggrReportCntrlGrantedSize |
Unsigned32 |
|
| |
tpmAggrReportCntrlReqReports |
Unsigned32 |
|
| |
tpmAggrReportCntrlGrantedReports |
Unsigned32 |
|
| |
tpmAggrReportCntrlStartTime |
TimeStamp |
|
| |
tpmAggrReportCntrlReportNumber |
Unsigned32 |
|
| |
tpmAggrReportCntrlInsertsDenied |
Counter32 |
|
| |
tpmAggrReportCntrlDroppedFrames |
Counter32 |
|
| |
tpmAggrReportCntrlOwner |
OwnerString |
|
| |
tpmAggrReportCntrlStorageType |
StorageType |
|
| |
tpmAggrReportCntrlStatus |
RowStatus |
|
| TpmAggrReportEntry |
|
| SEQUENCE |
|
|
|
| |
tpmAggrReportIndex |
Unsigned32 |
|
| |
tpmAggrReportAppLocalIndex |
AppLocalIndex |
|
| |
tpmAggrReportTransMetricIndex |
TpmTransactionMetricIndex |
|
| |
tpmAggrReportServerAddress |
OCTET STRING |
|
| |
tpmAggrReportApmNameClientID |
RmonClientID |
|
| |
tpmAggrReportStatN |
ZeroBasedCounter32 |
|
| |
tpmAggrReportOverflowStatN |
ZeroBasedCounter32 |
|
| |
tpmAggrReportHCStatN |
ZeroBasedCounter64 |
|
| |
tpmAggrReportStatSumX |
ZeroBasedCounter32 |
|
| |
tpmAggrReportOverflowStatSumX |
ZeroBasedCounter32 |
|
| |
tpmAggrReportHCStatSumX |
ZeroBasedCounter64 |
|
| |
tpmAggrReportStatMaximum |
ZeroBasedCounter32 |
|
| |
tpmAggrReportStatMinimum |
ZeroBasedCounter32 |
|
| |
tpmAggrReportStatSumSq |
ZeroBasedCounter32 |
|
| |
tpmAggrReportOverflowStatSumSq |
ZeroBasedCounter32 |
|
| |
tpmAggrReportHCStatSumSq |
ZeroBasedCounter64 |
|
| |
tpmAggrReportStatSumIX |
ZeroBasedCounter32 |
|
| |
tpmAggrReportOverflowStatSumIX |
ZeroBasedCounter32 |
|
| |
tpmAggrReportHCStatSumIX |
ZeroBasedCounter64 |
|
| |
tpmAggrReportStatSumIXSq |
ZeroBasedCounter32 |
|
| |
tpmAggrReportOverflowStatSumIXSq |
ZeroBasedCounter32 |
|
| |
tpmAggrReportHCStatSumIXSq |
ZeroBasedCounter64 |
|
| TpmCurReportEntry |
|
| SEQUENCE |
|
|
|
| |
tpmCurReportAppLocalIndex |
AppLocalIndex |
|
| |
tpmCurReportTransMetricIndex |
TpmTransactionMetricIndex |
|
| |
tpmCurReportServerAddress |
OCTET STRING |
|
| |
tpmCurReportApmNameClientID |
RmonClientID |
|
| |
tpmCurReportApmTransactionID |
Unsigned32 |
|
| |
tpmCurReportMetricValue |
ZeroBasedCounter32 |
|
| |
tpmCurReportCompletion |
INTEGER |
|
| TpmExcpReportEntry |
|
| SEQUENCE |
|
|
|
| |
tpmExcpReportTransMetricIndex |
TpmTransactionMetricIndex |
|
| |
tpmExcpReportStatN |
ZeroBasedCounter32 |
|
| |
tpmExcpReportOverflowStatN |
ZeroBasedCounter32 |
|
| |
tpmExcpReportHCStatN |
ZeroBasedCounter64 |
|
| |
tpmExcpReportStatSumX |
ZeroBasedCounter32 |
|
| |
tpmExcpReportOverflowStatSumX |
ZeroBasedCounter32 |
|
| |
tpmExcpReportHCStatSumX |
ZeroBasedCounter64 |
|
| |
tpmExcpReportStatMaximum |
ZeroBasedCounter32 |
|
| |
tpmExcpReportStatMinimum |
ZeroBasedCounter32 |
|
| |
tpmExcpReportStatSumSq |
ZeroBasedCounter32 |
|
| |
tpmExcpReportOverflowStatSumSq |
ZeroBasedCounter32 |
|
| |
tpmExcpReportHCStatSumSq |
ZeroBasedCounter64 |
|
| |
tpmExcpReportStatSumIX |
ZeroBasedCounter32 |
|
| |
tpmExcpReportOverflowStatSumIX |
ZeroBasedCounter32 |
|
| |
tpmExcpReportHCStatSumIX |
ZeroBasedCounter64 |
|
| |
tpmExcpReportStatSumIXSq |
ZeroBasedCounter32 |
|
| |
tpmExcpReportOverflowStatSumIXSq |
ZeroBasedCounter32 |
|
| |
tpmExcpReportHCStatSumIXSq |
ZeroBasedCounter64 |
|
Defined Values
| tpmMIB |
1.3.6.1.2.1.16.30 |
| This module defines extensions to the RMON2-MIB module
for the collection of Performance Metrics related to
application traffic in a network. In particular,
it describes managed objects used for monitoring
selectable performance metrics and statistics
derived from the monitoring of network packets and
sub-application level transactions.
In order to maintain the RMON 'look-and-feel', some of
the text from the RMON2 [RFC2021] and HC-RMON [RFC3273]
MIBs by Steve Waldbusser have been used in this MIB module.
Copyright (C) The Internet Society (2005). This version of
this MIB module is part of RFC 4150; see the RFC itself for
full legal notices. |
| MODULE-IDENTITY |
|
|
|
| tpmClockResolution |
1.3.6.1.2.1.16.30.1.1 |
| A read-only variable indicating the resolution
of the measurements possible by this device. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SspmMicroSeconds |
|
|
| tpmClockMaxSkew |
1.3.6.1.2.1.16.30.1.2 |
| A read-only variable indicating the maximum
offset error due to skew of the local clock
over the time interval 86400 seconds, in seconds. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SspmClockMaxSkew |
|
|
| tpmClockSource |
1.3.6.1.2.1.16.30.1.3 |
| A read-only variable indicating the source of the clock.
This is provided to allow a user to determine how accurate
the timing mechanism is compared with other devices. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SspmClockSource |
|
|
| tpmTransMetricDirLastChange |
1.3.6.1.2.1.16.30.1.4 |
| The value of sysUpTime at the time the
tpmTransMetricDirTable was last modified, through
modifications of the tpmTransMetricDirConfig object. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TimeStamp |
|
|
| tpmTransMetricDirTable |
1.3.6.1.2.1.16.30.1.5 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
TpmTransMetricDirEntry |
|
| tpmTransMetricDirEntry |
1.3.6.1.2.1.16.30.1.5.1 |
| A conceptual row in the tpmTransMetricDirTable.
An example of the indexing of this entry is
tpmTransMetricDirConfig.5.2 where 5 is the
value of a valid and visible appLocalIndex object
in the appLocalDir table. The entries describe
the transaction and metric pairs monitored for this
application. The tpmTransMetricProtocolIndex
identifies the protocol transaction and the
tpmMetricDefIndex describes the metric monitored. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
TpmTransMetricDirEntry |
|
|
| tpmTransMetricAppLocalIndex |
1.3.6.1.2.1.16.30.1.5.1.1 |
| An index used to uniquely identify the application
with which the entries in the tpmTransMetricDir
table are associated. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
AppLocalIndex |
|
|
| tpmTransMetricIndex |
1.3.6.1.2.1.16.30.1.5.1.2 |
| An index used to uniquely identify an entry in the
tpmTransMetricDir table. Each such entry defines
protocol transaction and metric instance
to be monitored for a specific application. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
TpmTransactionMetricIndex |
|
|
| tpmTransMetricProtocolIndex |
1.3.6.1.2.1.16.30.1.5.1.3 |
| The protocolDirLocalIndex of the particular transaction to
be analyzed when computing and generating the selected metric
for a specific application. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..2147483647 |
|
| tpmTransMetricMetricIndex |
1.3.6.1.2.1.16.30.1.5.1.4 |
| The tpmMetricDefinitionID of the particular metric to be
generated. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..2147483647 |
|
| tpmTransMetricDirConfig |
1.3.6.1.2.1.16.30.1.5.1.5 |
| This object describes and configures the probe's support
for this performance metric in relationship to the
specified transaction and application. The agent
creates entries in this table for all metric
and transaction combinations that it can generate. Because
the probe will only populate this table with supported
entries, and the table cannot have entries added, the
notSupported(1) setting is only used to signify that other
configuration parameters are causing the agent currently not
to support the generation and collection of this metric for
the specified protocol and application. Also, the status of
this object will not change to notSupported(1) due to a
change to supportedOff(2) in the tpmMetricDir table.
If the value of this object is notSupported(1), the probe
will not perform computations for this performance metric and
transaction combination and will not allow this object to be
changed to any other value. If the value of this object is
supportedOn(3), the probe supports computations for this
performance metric and protocol and is configured to perform
the computations for this performance metric and protocol
combination for the application for all interfaces.
If the value of this object is supportedOff(2), the
probe supports computations for this performance
metric for the specified protocol, but is configured
not to perform the computations for this performance
metric and protocol for the application for any
interfaces. Whenever this value changes from
supportedOn(3) to supportedOff(2), the probe shall
cause the deletion of all entries in the tpmReportGroup
tables, for all appropriate studies configured in the
tpmAggrReportCntrlTable.
The value of this object must persist across reboots. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
notSupported(1), supportedOff(2), supportedOn(3) |
|
| tpmMetricDefTable |
1.3.6.1.2.1.16.30.1.6 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
TpmMetricDefEntry |
|
| tpmMetricDefEntry |
1.3.6.1.2.1.16.30.1.6.1 |
| Information about a particular metric. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
TpmMetricDefEntry |
|
|
| tpmMetricDefinitionID |
1.3.6.1.2.1.16.30.1.6.1.1 |
| The index for this entry. This object identifies
the particular metric in this MIB module. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
TpmMetricDefID |
|
|
| tpmMetricDefType |
1.3.6.1.2.1.16.30.1.6.1.2 |
| The basic type of metric indicated by this entry.
The value 'other(1)' indicates that this metric cannot be
characterized by any of the remaining enumerations specified
for this object.
The value 'connectMetric(2)' indicates that this metric
measures connectivity characteristics.
The value 'delayMetric(3)' indicates that this metric
measures delay characteristics.
The value 'lossMetric(4)' indicates that this metric
measures loss characteristics. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
other(1), connectMetric(2), delayMetric(3), lossMetric(4) |
|
| tpmMetricDefDirType |
1.3.6.1.2.1.16.30.1.6.1.3 |
| The directional characteristics of the this metric.
The value 'oneWay(1)' indicates that this metric is measured
with some sort of unidirectional test.
The value 'twoWay(2)' indicates that this metric is measured
with some sort of bidirectional test.
The value 'multiWay(3)' indicates that this metric is
measured with some combination of unidirectional and/or
bidirectional tests. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
oneWay(1), twoWay(2), multiWay(3) |
|
| tpmMetricDefName |
1.3.6.1.2.1.16.30.1.6.1.4 |
| The textual name of this metric. For example, if
this tpmMetricDefEntry identified the IPPM metric for
round trip delay, then this object should contain
the value, e.g., 'Type-P-Round-Trip-Delay'. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
|
|
| tpmMetricDefReference |
1.3.6.1.2.1.16.30.1.6.1.5 |
| This object contains a reference to the document that
defines this metric. If this document is available online
via electronic download, then a de-referencable URL
should be specified in this object. The implementation
must support an HTTP URL type and may support additional
types of de-referencable URLs such as an FTP type.
For example, if this tpmMetricDefName identified the IPPM
metric 'Type-P-Round-Trip-Delay', then this object should
contain the value, e.g.,
'http://www.ietf.org/rfc/rfc2681.txt'. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
|
|
| tpmMetricDefGlobalID |
1.3.6.1.2.1.16.30.1.6.1.6 |
| This object contains a reference to the Object ID
in a metrics registration MIB being developed
in the IPPM WG at the IETF; e.g., the
IPPM-REGISTRY-MIB [RFC4148], which defines the metric.
In the event that this metric has no corresponding
object identifier (OID) or until the IPPM-REGISTRY-MIB is
defined, then the value should be set to 0.0 for none. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OBJECT IDENTIFIER |
|
|
| tpmAggrReportCntrlTable |
1.3.6.1.2.1.16.30.2.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
TpmAggrReportCntrlEntry |
|
| tpmAggrReportCntrlEntry |
1.3.6.1.2.1.16.30.2.1.1 |
| A conceptual row in the tpmAggrReportCntrlTable.
An example of the indexing of this entry is
tpmAggrReportCntrlDataSource.1 |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
TpmAggrReportCntrlEntry |
|
|
| tpmAggrReportCntrlIndex |
1.3.6.1.2.1.16.30.2.1.1.1 |
| An index that uniquely identifies an entry in the
tpmAggrReportCntrlTable. Each such entry defines a unique
report whose results are placed in the tpmAggrReportTable on
behalf of this tpmAggrReportCntrlEntry. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..65535 |
|
| tpmAggrReportCntrlApmCntrlIndex |
1.3.6.1.2.1.16.30.2.1.1.2 |
| This index associates this TpmAggrReportCntrlEntry directly
with an existing ApmReportControlEntry. This link is used
to synchronize reports in the associated tpmAggrReportTable.
A value of 0 (zero) enables an independent control table that
will report entries to tpmAggrReportTable based only on the
other objects in this table.
A non-zero value indicates that this row is defined through
the APM-MIB. In this case, all row objects are set to their
corresponding values in the APM-MIB. In the event that a
SET is issued to a row object, while the value of the
tpmAggrReportCntrlApmCntrlIndex is non-zero, the agent
MUST respond as if the object of the SET command
had MAX-ACCESS of read-only.
This object may not be modified if the associated
tpmAggrReportCntrlStatus object is equal to active(1). |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0..65535 |
|
| tpmAggrReportCntrlDataSource |
1.3.6.1.2.1.16.30.2.1.1.3 |
| The source of the data for TPM Reports generated on
behalf of this tpmAggrReportCntrlEntry.
If the measurement is being performed by a probe, this should
be set to the interface or port where data was received for
analysis. If the measurement isn't being performed by a
probe this should be set to the primary interface over which
the measurement is being performed. If the measurement isn't
being performed by a probe and there is no primary interface,
or if this information isn't known, this object should be
set to 0.0.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object is set to the corresponding
apmReportControlTable object in the APM-MIB [RFC3729].
This object may not be modified if the associated
tpmAggrReportCntrlStatus object is equal to active(1). |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
DataSourceOrZero |
|
|
| tpmAggrReportCntrlAggrType |
1.3.6.1.2.1.16.30.2.1.1.4 |
| The type of aggregation being performed for this set of
reports.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object should be set by the agent to the value
of the apmReportControlAggregationType object.
This object may not be modified if the associated
tpmAggrReportCntrlStatus object is equal to active(1). |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
TransactionAggregationType |
|
|
| tpmAggrReportCntrlInterval |
1.3.6.1.2.1.16.30.2.1.1.5 |
| The interval in seconds over which data is accumulated before
being aggregated into a report in the tpmAggrReportTable.
All reports with the same tpmAggrReportCntrlIndex will be
based on the same interval.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object should be set by the agent to the value
of the apmReportControlControlInterval object.
This object may not be modified if the associated
tpmReportAggregateCntrlStatus object is equal to active(1). |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| tpmAggrReportCntrlReqSize |
1.3.6.1.2.1.16.30.2.1.1.6 |
| The maximum number of Client and Server combination
entries requested for this report.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object should be set by the agent to the value
of the apmReportControlRequestedSize object.
When this object is created or modified, the probe
should set tpmReportCntrlGrantedSize as closely to this
object as is possible for the particular probe
implementation and available resources.
It is important to note that this value is the number of
requested entries in the tpmAggrReportTable only. Because
the probe can derive this table from the apmReportTable, the
probe must make sure that sufficient resources exist to
support the creation of the apmReportTable, plus any
additional resources required to convert or support this
table.
This object may not be modified if the associated
tpmReportAggregateCntrlStatus object is equal to active(1). |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| tpmAggrReportCntrlGrantedSize |
1.3.6.1.2.1.16.30.2.1.1.7 |
| The maximum number of performance entries in this report.
When the associated tpmAggrReportCntrlReqSize object is
created or modified, the probe should set this
object as closely to the requested value as is
possible for the particular implementation and
available resources. The probe must not lower this
value except as a result of a set to the associated
tpmAggrReportCntrlReqSize object.
It is an implementation-specific matter as to whether
zero-valued entries are available. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| tpmAggrReportCntrlReqReports |
1.3.6.1.2.1.16.30.2.1.1.8 |
| The number of saved reports requested to be allocated on
behalf of this entry.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object should be set by the agent to the value
of the apmReportControlcwRequestedReportsDataSource object.
This object may not be modified if the associated
tpmReportAggregateCntrlStatus object is equal to active(1). |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..65535 |
|
| tpmAggrReportCntrlGrantedReports |
1.3.6.1.2.1.16.30.2.1.1.9 |
| The number of saved reports the agent has allocated based
on the requested amount in tpmAggrReportCntrlReqReports.
Because each report can have many entries, the total number
of entries allocated will be this number multiplied by the
value of tpmAggrReportCntrlGrantedSize, or by 1 if that
object doesn't exist.
When the associated tpmAggrReportCntrlReqReports object is
created or modified, the agent should set this object as
closely to the requested value as is possible for the
particular implementation and available resources. When
considering available resources, the agent must consider its
ability to allocate this many reports, each with the number
of entries represented by tpmAggrReportCntrlGrantedSize, or
by 1 if that object doesn't exist.
Note that although the storage required for each report may
fluctuate due to changing conditions, the agent must continue
to have storage available to satisfy the full report size for
all reports, when necessary. Further, the agent must not
lower this value except as a result of a set to the
associated tpmAggrReportCntrlReqSize object. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0..65535 |
|
| tpmAggrReportCntrlStartTime |
1.3.6.1.2.1.16.30.2.1.1.10 |
| The value of sysUpTime when the system began processing the
report in progress. Note that the report in progress is not
available.
This object may be used by the management station to figure
out the start time for all previous reports saved for this
tpmAggrReportCntrlEntry, as reports are started at fixed
intervals.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object is set to the corresponding
apmReportControlTable object in the APM-MIB defined in
the IETF's RMONMIB WG. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TimeStamp |
|
|
| tpmAggrReportCntrlReportNumber |
1.3.6.1.2.1.16.30.2.1.1.11 |
| The number of the report in progress. When an
tpmAggrReportCntrlEntry is activated, the first report will
be numbered zero.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object should be set by the agent to the value
of the apmReportControlReportNumber object. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| tpmAggrReportCntrlInsertsDenied |
1.3.6.1.2.1.16.30.2.1.1.12 |
| The number of attempts to add an entry to reports for
this TpmAggrReportCntrlEntry that failed because the number
of entries would have exceeded tpmAggrReportCntrlGrantedSize.
This number is valuable in determining if enough entries have
been allocated for reports in light of fluctuating network
usage. Note that an entry that is denied will often be
attempted again, so this number will not predict the exact
number of additional entries needed, but it can be used to
understand the relative magnitude of the problem.
Also note that there is no ordering specified for the entries
in the report; thus, there are no rules for which entries
will be omitted when not enough entries are available. As a
consequence, the agent is not required to delete 'least
valuable' entries first. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| tpmAggrReportCntrlDroppedFrames |
1.3.6.1.2.1.16.30.2.1.1.13 |
| The total number of frames that were received by the agent
and therefore not accounted for in the *StatsDropEvents, but
for which the agent chose not to count for this entry for
whatever reason. Most often, this event occurs when the
agent is out of some resources and decides to shed load from
this collection.
This count does not include packets that were not counted
because they had MAC-layer errors.
Note that if the alMatrixTables are not implemented or are
inactive because no protocols are enabled in the protocol
directory, this value should be 0.
Note that, unlike the dropEvents counter, this number is the
exact number of frames dropped. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| tpmAggrReportCntrlOwner |
1.3.6.1.2.1.16.30.2.1.1.14 |
| The entity that configured this entry and is
therefore using the resources assigned to it.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object should be set by the agent to the value
of the apmReportControlReportNumber object.
This object may not be modified if the associated
tpmReportAggregateCntrlStatus object is equal to active(1). |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
OwnerString |
|
|
| tpmAggrReportCntrlStorageType |
1.3.6.1.2.1.16.30.2.1.1.15 |
| The storage type of this tpmAggrReportCntrlEntry. If the
value of this object is 'permanent', no objects in this row
need to be writable. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
StorageType |
|
|
| tpmAggrReportCntrlStatus |
1.3.6.1.2.1.16.30.2.1.1.16 |
| The status of this performance control entry.
An entry may not exist in the active state unless each
object in the entry has an appropriate value.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object should be set by the agent to the value
of the apmReportControlReportNumber object.
Once this object is set to active(1), no objects in the
tpmAggrReportCntrlTable can be changed.
If this object is not equal to active(1), all associated
entries in the tpmAggrReportTable shall be deleted. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
RowStatus |
|
|
| tpmAggrReportTable |
1.3.6.1.2.1.16.30.2.2 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
TpmAggrReportEntry |
|
| tpmAggrReportEntry |
1.3.6.1.2.1.16.30.2.2.1 |
| A conceptual row in the tpmAggrReportTable.
The tpmAggrReportCntrlIndex value in the index identifies the
tpmAggrReportCntrlEntry on whose behalf this entry was
created.
The tpmAggrReportIndex value in the index identifies which
report (in the series of reports) this entry is a part of.
The tpmAggrReportAppLocalIndex value in the index identifies
the application protocol that is being reported.
The tpmTransMetricIndex value in the index identifies
the transaction protocol-metric pair for the traffic flows
aggregated in this entry.
The protocolDirLocalIndex value in the index identifies the
network layer protocol of the tpmAggrReportServerAddress.
When the associated tpmAggrReportCntrlAggrType value is equal
to applications(4) or clients(2), this value will equal 0.
The tpmAggrReportServerAddress value in the index identifies
the network layer address of the server in traffic flows
aggregated in this entry.
The tpmAggrReportApmNameClientID value in the index
identifies the client in traffic flows aggregated in this
entry. If the associated tpmAggrReportCntrlAggrType is equal
to applications(4) or servers(3), then this object will be
set to 0.
An example of the indexing of this entry is
tpmAggrReportStatN.3.15.34.262.18.4.128.2.6.7.3256521 |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
TpmAggrReportEntry |
|
|
| tpmAggrReportIndex |
1.3.6.1.2.1.16.30.2.2.1.1 |
| The value of tpmAggrReportCntrlNumber for the report to
which this entry belongs. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..2147483647 |
|
| tpmAggrReportServerAddress |
1.3.6.1.2.1.16.30.2.2.1.4 |
| The network layer address of the server host in this
conversation.
This is represented as an octet string with specific
semantics and length as identified by the
protocolDirLocalIndex component of the index.
Because this object is an index variable, it is encoded in
the index according to the index encoding rules. For
example, if the protocolDirLocalIndex indicates an
encapsulation of IPv4, this object is encoded as a length
octet of 4, followed by the 4 octets of the IPv4 address,
in network byte order.
If the associated tpmAggrReportCntrlAggrType is equal to
application(4) or client(2), then this object will be a null
string and will be encoded simply as a length octet of 0. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(0..108) |
|
| tpmAggrReportApmNameClientID |
1.3.6.1.2.1.16.30.2.2.1.5 |
| A unique ID assigned to the machine represented by this
mapping. This ID is assigned by the agent using an
implementation-specific algorithm. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
RmonClientID |
|
|
| tpmAggrReportStatN |
1.3.6.1.2.1.16.30.2.2.1.6 |
| The count of the total number of data points for the
specified metric. This number always represents the
total size of the statistical datum analyzed. Each
metric specifies the exact meaning of this object.
This value represents the results for one metric and is
related directly to the specific parameters of the metric
and the Server and Client addresses involved. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportOverflowStatN |
1.3.6.1.2.1.16.30.2.2.1.7 |
| The number of times the associated
tpmAggrReportStatN counter has overflowed. Note
that this object will only be instantiated if the
associated tpmAggrReportHCStatN object is also
instantiated for a particular dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportHCStatN |
1.3.6.1.2.1.16.30.2.2.1.8 |
| The high-capacity version of tpmAggrReportStatN.
Note that this object will only be instantiated if the
agent supports high-capacity monitoring for a particular
dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter64 |
|
|
| tpmAggrReportStatSumX |
1.3.6.1.2.1.16.30.2.2.1.9 |
| The sum of all the data point values for the specified
metric. This number always represents the total values
of the statistical datum analyzed. Each metric
specifies the exact meaning of this object.
This value represents the results of one metric and is
related directly to the specific parameters of the metric
and the Server and Client addresses involved. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportOverflowStatSumX |
1.3.6.1.2.1.16.30.2.2.1.10 |
| The number of times the associated
tpmAggrReportStatSumX counter has overflowed.
Note that this object will only be instantiated if the
associated tpmAggrReportHCStatSumX object is also
instantiated for a particular dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportHCStatSumX |
1.3.6.1.2.1.16.30.2.2.1.11 |
| The high-capacity version of tpmAggrReportStatSumX.
Note that this object will only be instantiated if the
agent supports High Capacity monitoring for a particular
dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter64 |
|
|
| tpmAggrReportStatMaximum |
1.3.6.1.2.1.16.30.2.2.1.12 |
| The single maximum data point value observed during the
study period for the specified metric. This number always
represents the maximum value of any single statistical
datum analyzed. Each metric specifies the exact meaning
of this object.
This value represents the results of one metric and is
related directly to the specific parameters of the metric
and the Server and Client addresses involved. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportStatMinimum |
1.3.6.1.2.1.16.30.2.2.1.13 |
| The single minimum data point value observed during the
study period for the specified metric. This number always
represents the minimum value of any single statistical
datum analyzed. Each metric specifies the exact meaning
of this object.
This value represents the results of one metric and is
related directly to the specific parameters of the metric
and the Server and Client addresses involved. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportStatSumSq |
1.3.6.1.2.1.16.30.2.2.1.14 |
| The sum of all the squared data point values for the
specified metric. This number always represents the
total of the squared values of the statistical datum
analyzed. Each metric specifies the exact meaning of
this object.
This value represents the results of one metric and is
related directly to the specific parameters of the metric
and the Server and Client addresses involved. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportOverflowStatSumSq |
1.3.6.1.2.1.16.30.2.2.1.15 |
| The number of times the associated
tpmAggrReportStatSumSq counter has overflowed.
Note that this object will only be instantiated if
the associated tpmAggrReportHCStatSumSq object
is also instantiated for a particular dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportHCStatSumSq |
1.3.6.1.2.1.16.30.2.2.1.16 |
| The high-capacity version of tpmAggrReportStatSumSq.
Note that this object will only be instantiated if the
agent supports High Capacity monitoring for a particular
dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter64 |
|
|
| tpmAggrReportStatSumIX |
1.3.6.1.2.1.16.30.2.2.1.17 |
| For each interval, each data point is associated with a
value I, I = 1..N where N is the number of data points;
tpmAggrReportStatSumIX is the multiplication of the
data point value with the current I. This value
along with the other statistics values allow the
calculation of the slope of the least-squares line
through the data points. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportOverflowStatSumIX |
1.3.6.1.2.1.16.30.2.2.1.18 |
| The number of times the associated
tpmAggrReportStatSumIX counter has overflowed.
Note that this object will only be instantiated if the
associated tpmAggrReportHCStatSumIX object is also
instantiated for a particular dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportHCStatSumIX |
1.3.6.1.2.1.16.30.2.2.1.19 |
| The high-capacity version of tpmAggrReportStatSumIX.
Note that this object will only be instantiated if the
agent supports High Capacity monitoring for a particular
dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter64 |
|
|
| tpmAggrReportStatSumIXSq |
1.3.6.1.2.1.16.30.2.2.1.20 |
| For each interval, each data point is associated with a
value I, I = 1..N where N is the number of data points;
tpmAggrReportStatSumIXSq is the multiplication
of the data point value with the current I.
This value along with the other statistics
values allow the calculation of the slope of
the least-squares line through the data points. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportOverflowStatSumIXSq |
1.3.6.1.2.1.16.30.2.2.1.21 |
| The number of times the associated
tpmAggrReportStatSumIXSq counter has overflowed.
Note that this object will only be instantiated if the
associated tpmAggrReportHCStatSumIXSq object is also
instantiated for a particular dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmAggrReportHCStatSumIXSq |
1.3.6.1.2.1.16.30.2.2.1.22 |
| The high-capacity version of tpmAggrReportStatSumIXSq.
Note that this object will only be instantiated if the
agent supports High Capacity monitoring for a particular
dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter64 |
|
|
| tpmCurReportTable |
1.3.6.1.2.1.16.30.2.3 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
TpmCurReportEntry |
|
| tpmCurReportEntry |
1.3.6.1.2.1.16.30.2.3.1 |
| A conceptual row in the tpmCurReportTable.
The tpmAggrReportControlIndex value in the index identifies
the tpmAggrReportCntrlEntry on whose behalf this entry was
created. The tpmCurReportAppLocalIndex value in the
index identifies the application protocol that is being
reported. The protocolDirLocalIndex value in the
index identifies the network layer protocol
of the tpmAggrReportServerAddress. When the associated
tpmAggrReportCntrlAggrType value is
equal to applications(4), this value will equal 0.
The tpmCurReportServerAddress value in the
index identifies the network layer address of the
server in traffic flows aggregated in this entry.
The tpmCurReportCurrentApmNameClientID value in the
index identifies the network layer address of the
client in traffic flows aggregated in this entry.
The tpmCurReportCurrentMetricIndex value in the
index identifies the transported application protocol
of the traffic flows aggregated in this entry.
Note that the order of protocolDirLocalIndex variables is
the opposite of that in the RMON2 MIB (application.network
instead of network.application); the report entries are
sorted by application first, server second, and client third.
The tpmCurReportCntrIndex value in the index identifies
the tpmAggrReportCntrlEntry on whose behalf this entry was
created. The tpmCurReportMetricIndex value in the index
identifies the metric and protocol of the
tpmCurReportServerAddress, via the tpmTransMetricDir
table.
An example of the indexing of this table is
tpmCurReportStatisticN.3.34.262.18.4.128.2.6.6.3256521.29667 |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
TpmCurReportEntry |
|
|
| tpmCurReportServerAddress |
1.3.6.1.2.1.16.30.2.3.1.3 |
| The network server address for this tpmCurReportEntry.
This is represented as an octet string with
specific semantics and length as identified
by the protocolDirLocalIndex component of the index.
For example, if the protocolDirLocalIndex indicates an
encapsulation of IPv4, this object is encoded as a length
octet of 4, followed by the 4 octets of the IPv4 address,
in network byte order. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(0..108) |
|
| tpmCurReportApmNameClientID |
1.3.6.1.2.1.16.30.2.3.1.4 |
| A unique ID assigned to the machine represented by this
mapping. This ID is assigned by the agent using an
implementation-specific algorithm. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
RmonClientID |
|
|
| tpmCurReportApmTransactionID |
1.3.6.1.2.1.16.30.2.3.1.5 |
| A unique value for this transaction amongst other
transactions sharing the same application,
transaction-layer protocol and metric, and
server and client addresses. Implementations may choose to
use the value of the client's source port, when possible.
If the tpmAggrReportCntrlApmCntrlIndex is non-zero,
then this object is set to the corresponding
apmTransactionID object in the APM-MIB developed
in the IETF's RMONMIB WG. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0..4294967295 |
|
| tpmCurReportMetricValue |
1.3.6.1.2.1.16.30.2.3.1.6 |
| The current value of the metric being evaluated.
For some transaction types this value may be 0, e.g.,
the current round-trip time for a DNS query. For
other transaction types, this will represent the
current value of a continuously measured metric, e.g.,
the current throughput of an FTP transaction. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmCurReportCompletion |
1.3.6.1.2.1.16.30.2.3.1.7 |
| The status of this transaction. It is not always obvious
from context whether a transaction is ongoing or
completed. E.g., an ftp-GET transaction may last several
minutes or hours, and a value found in the
tpmCurReportMetricValue object lists to observed throughput
for the transaction up to this point in time. The value
of the tpmCurReportCompletion indicates whether the
transaction has been completed. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
current(1), completed(2) |
|
| tpmCurReportSize |
1.3.6.1.2.1.16.30.2.4 |
| The maximum number of completed transactions desired to be
retained in the tpmCurReportTable. If the agent doesn't have
enough resources to retain this many, it will retain as many
as possible. Regardless of this value, the agent must
attempt to keep records for all current transactions it is
monitoring.
The agent should consider this value to give a hint as to
how many transactions to save. This is not a hard limit,
just a hint to a maximum value of interest. If this value is
reduced by the management station, the agent can take note,
it may free some records, or it may do nothing.
The value of this object must persist across reboots. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| tpmExcpReportTable |
1.3.6.1.2.1.16.30.2.5 |
| This table contains all sub-flow metrics for transactions
that have been tagged by the apmExceptionTable filter
as having had poor performance. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
TpmExcpReportEntry |
|
| tpmExcpReportEntry |
1.3.6.1.2.1.16.30.2.5.1 |
| A conceptual row in the tpmExcpReportTable. This table
contains aggregated information associated with
exceptions counted in the apmExceptionTable. The
information is aggregated in a manner identical to the
aggregation in the tpmAggrReportTable, with the exception
that data only from transactions associated with a
flagged application is included.
The indexing into this table follows the indexing in the
APM-MIB but adds the tpmTransMetricIndex to identify the
sub-application transaction and metric pair. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
TpmExcpReportEntry |
|
|
| tpmExcpReportStatN |
1.3.6.1.2.1.16.30.2.5.1.2 |
| The count of the total number of data points for the
specified metric. This number always represents the
total size of the statistical datum analyzed. Each
metric specifies the exact meaning of this object.
This value represents the results of one metric and is
related directly to the specific parameters of the metric
and the Server and Client addresses involved. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportOverflowStatN |
1.3.6.1.2.1.16.30.2.5.1.3 |
| The number of times the associated tpmExcpReportStatN
counter has overflowed. Note that this object will only
be instantiated if the associated tpmExcpReportHCStatN
object is also instantiated for a particular dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportHCStatN |
1.3.6.1.2.1.16.30.2.5.1.4 |
| The high-capacity version of tpmExcpReportStatN.
Note that this object will only be instantiated if the
agent supports High Capacity monitoring for a particular
dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter64 |
|
|
| tpmExcpReportStatSumX |
1.3.6.1.2.1.16.30.2.5.1.5 |
| The sum of all the data point values for the specified
metric. This number always represents the total values
of the statistical datum analyzed. Each metric
specifies the exact meaning of this object.
This value represents the results of one metric and is
related directly to the specific parameters of the metric
and the Server and Client addresses involved. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportOverflowStatSumX |
1.3.6.1.2.1.16.30.2.5.1.6 |
| The number of times the associated
tpmExcpReportStatSumX counter has overflowed.
Note that this object will only be instantiated if
the associated tpmExcpReportHCStatSumX object is also
instantiated for a particular dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportHCStatSumX |
1.3.6.1.2.1.16.30.2.5.1.7 |
| The high-capacity version of tpmExcpReportStatSumX.
Note that this object will only be instantiated if the
agent supports High Capacity monitoring for a particular
dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter64 |
|
|
| tpmExcpReportStatMaximum |
1.3.6.1.2.1.16.30.2.5.1.8 |
| The single maximum data point value observed during the
study period for the specified metric. This number always
represents the maximum value of any single statistical
datum analyzed. Each metric specifies the exact meaning
of this object.
This value represents the results of one metric and is
related directly to the specific parameters of the metric
and the Server and Client addresses involved. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportStatMinimum |
1.3.6.1.2.1.16.30.2.5.1.9 |
| The single minimum data point value observed during the
study period for the specified metric. This number always
represents the minimum value of any single statistical
datum analyzed. Each metric specifies the exact meaning
of this object.
This value represents the results of one metric and is
related directly to the specific parameters of the metric
and the Server and Client addresses involved. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportStatSumSq |
1.3.6.1.2.1.16.30.2.5.1.10 |
| The sum of all the squared data point values for the
specified metric. This number always represents the
total of the squared values of the statistical datum
analyzed. Each metric specifies the exact meaning of
this object.
This value represents the results of one metric and is
related directly to the specific parameters of the metric
and the Server and Client addresses involved. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportOverflowStatSumSq |
1.3.6.1.2.1.16.30.2.5.1.11 |
| The number of times the associated
tpmExcpReportStatSumSq counter has overflowed.
Note that this object will only be instantiated if the
associated tpmExcpReportHCStatSumSq object is also
instantiated for a particular dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportHCStatSumSq |
1.3.6.1.2.1.16.30.2.5.1.12 |
| The high-capacity version of tpmExcpReportStatSumSq.
Note that this object will only be instantiated if the
agent supports High Capacity monitoring for a particular
dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter64 |
|
|
| tpmExcpReportStatSumIX |
1.3.6.1.2.1.16.30.2.5.1.13 |
| For each interval, each data point is associated with a
value I, I = 1..N where N is the number of data points;
tpmExcpReportStatSumIX is the multiplication of the
data point value with the current I. This value along with
the other statistics values allow the calculation of the
slope of the least-squares line through the data points. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportOverflowStatSumIX |
1.3.6.1.2.1.16.30.2.5.1.14 |
| The number of times the associated
tpmExcpReportStatSumIX counter has overflowed.
Note that this object will only be instantiated if the
associated tpmExcpReportHCStatSumIX object is also
instantiated for a particular dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportHCStatSumIX |
1.3.6.1.2.1.16.30.2.5.1.15 |
| The high-capacity version of tpmExcpReportStatSumIX.
Note that this object will only be instantiated if the
agent supports High Capacity monitoring for a particular
dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter64 |
|
|
| tpmExcpReportStatSumIXSq |
1.3.6.1.2.1.16.30.2.5.1.16 |
| For each interval, each data point is associated with a
value I, I = 1..N where N is the number of data points;
tpmExcpReportStatSumIXSq is the multiplication of the data
point value with the current I. This value along with the
other statistics values allow the calculation of the slope of
the least-squares line through the data points. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportOverflowStatSumIXSq |
1.3.6.1.2.1.16.30.2.5.1.17 |
| The number of times the associated
tpmExcpReportStatSumIXSq counter has overflowed.
Note that this object will only be instantiated if the
associated tpmExcpReportHCStatSumIXSq object is also
instantiated for a particular dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter32 |
|
|
| tpmExcpReportHCStatSumIXSq |
1.3.6.1.2.1.16.30.2.5.1.18 |
| The high-capacity version of tpmExcpReportStatSumIXSq.
Note that this object will only be instantiated if the
agent supports High Capacity monitoring for a particular
dataSource. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
ZeroBasedCounter64 |
|
|
| tpmGroups |
1.3.6.1.2.1.16.30.3.2 |
| OBJECT IDENTIFIER |
|
|
|
| tpmMIBCompliance |
1.3.6.1.2.1.16.30.3.1.1 |
| Describes the requirements for conformance to
the TPM-MIB.
This compliance statement defines the following
TPM-MIB implementation:
- tpmCapabilitiesGroup (minimum)
- tpmAggregateReportsGroup (minimum)
- tpmCurrentReportsGroup (optional)
- tpmExceptionReportsGroup (optional).
In order to implement the (optional)
tpmExceptionReportsGroup, it is necessary
to implement pieces of the APM-MIB as
described in the tpmApmMIBCompliance MODULE
below. Further, in the event that the TPM-MIB
is used to provide a drill-down capability,
which is the true value of this MIB, then the
tpmApmReportControlGroup must be implemented. |
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| tpmCurrentReportsCompliance |
1.3.6.1.2.1.16.30.3.1.2 |
| This defines the Current Reports compliance.
This is useful when information on in-progress
and historical transaction-level data is
desired. |
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| tpmExceptionReportsCompliance |
1.3.6.1.2.1.16.30.3.1.3 |
| This defines the Exception Reports compliance.
This is useful when information on
transactions whose performance is deemed
out-of-bounds. |
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| tpmCapabilitiesGroup |
1.3.6.1.2.1.16.30.3.2.1 |
| The tpmCapabilitiesGroup specifies various capabilities
associated with the monitoring agent. |
| Status: current |
Access: read-only |
| OBJECT-GROUP |
|
|
|
| tpmAggregateReportsGroup |
1.3.6.1.2.1.16.30.3.2.2 |
| The tpmAggregateReportsGroup provides control
and reporting of aggregate measurement
statistics. |
| Status: current |
Access: read-only |
| OBJECT-GROUP |
|
|
|
| tpmCurrentReportsGroup |
1.3.6.1.2.1.16.30.3.2.3 |
| The tpmCurrentReportsGroup contains metric
information relating to ongoing measurements
as well as historical values. |
| Status: current |
Access: read-only |
| OBJECT-GROUP |
|
|
|
| tpmExceptionReportsGroup |
1.3.6.1.2.1.16.30.3.2.4 |
| The tpmExceptionReportsGroup reports
sub-application level statistics associated
with errant applications. |
| Status: current |
Access: read-only |
| OBJECT-GROUP |
|
|
|