tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search

RFC 4150

 
 
 

Transport Performance Metrics MIB

Part 3 of 3, p. 33 to 57
Prev RFC Part

 


prevText      Top      Up      ToC       Page 33 
   tpmAggrReportStatN OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 6 }

   tpmAggrReportOverflowStatN OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 7 }

   tpmAggrReportHCStatN OBJECT-TYPE
       SYNTAX      ZeroBasedCounter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 8 }

   tpmAggrReportStatSumX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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.

Top      Up      ToC       Page 34 
           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."
       ::= { tpmAggrReportEntry 9 }

   tpmAggrReportOverflowStatSumX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 10 }

   tpmAggrReportHCStatSumX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 11 }

   tpmAggrReportStatMaximum OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 12 }

   tpmAggrReportStatMinimum OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current

Top      Up      ToC       Page 35 
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 13 }

   tpmAggrReportStatSumSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 14 }

   tpmAggrReportOverflowStatSumSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 15 }

   tpmAggrReportHCStatSumSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The high-capacity version of tpmAggrReportStatSumSq.
           Note that this object will only be instantiated if the
           agent supports High Capacity monitoring for a particular

Top      Up      ToC       Page 36 
           dataSource."
       ::= { tpmAggrReportEntry 16 }

   tpmAggrReportStatSumIX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 17 }

   tpmAggrReportOverflowStatSumIX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 18 }

   tpmAggrReportHCStatSumIX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 19 }

   tpmAggrReportStatSumIXSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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

Top      Up      ToC       Page 37 
           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."
       ::= { tpmAggrReportEntry 20 }

   tpmAggrReportOverflowStatSumIXSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 21 }

   tpmAggrReportHCStatSumIXSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmAggrReportEntry 22 }

   --
   -- The tpmCurrentReportsGroup
   --

   tpmCurReportTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF TpmCurReportEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "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

Top      Up      ToC       Page 38 
           transaction is indicated by the value of
           the tpmCurReportCompletion object."
       ::= { tpmReports 3 }

   tpmCurReportEntry OBJECT-TYPE
       SYNTAX      TpmCurReportEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "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"
       INDEX { tpmAggrReportCntrlIndex,
               tpmCurReportAppLocalIndex,         -- Application Layer
               tpmCurReportTransMetricIndex,      -- Metric and Protocol
               protocolDirLocalIndex,             -- Network Layer
               tpmCurReportServerAddress,

Top      Up      ToC       Page 39 
               tpmCurReportApmNameClientID,
               tpmCurReportApmTransactionID
             }
       ::= { tpmCurReportTable 1 }

   TpmCurReportEntry ::= SEQUENCE {
       tpmCurReportAppLocalIndex              AppLocalIndex,
       tpmCurReportTransMetricIndex           TpmTransactionMetricIndex,
       tpmCurReportServerAddress              OCTET STRING,
       tpmCurReportApmNameClientID            RmonClientID,
       tpmCurReportApmTransactionID           Unsigned32,
       tpmCurReportMetricValue                ZeroBasedCounter32,
       tpmCurReportCompletion                 INTEGER
   }

   tpmCurReportAppLocalIndex  OBJECT-TYPE
       SYNTAX      AppLocalIndex
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "The common application of the transactions reported
           in this entry."
       ::= { tpmCurReportEntry 1 }

   tpmCurReportTransMetricIndex OBJECT-TYPE
       SYNTAX      TpmTransactionMetricIndex
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A unique index that identifies the transaction and
           metric associated with the statistics reported here."
       ::= { tpmCurReportEntry 2 }

   tpmCurReportServerAddress OBJECT-TYPE
       SYNTAX      OCTET STRING (SIZE (0..108))
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "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."

Top      Up      ToC       Page 40 
       ::= { tpmCurReportEntry 3 }

   tpmCurReportApmNameClientID OBJECT-TYPE
       SYNTAX      RmonClientID
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A unique ID assigned to the machine represented by this
           mapping.  This ID is assigned by the agent using an
           implementation-specific algorithm."
       ::= { tpmCurReportEntry 4 }

   tpmCurReportApmTransactionID OBJECT-TYPE
       SYNTAX      Unsigned32 (0..4294967295)
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmCurReportEntry 5 }

   tpmCurReportMetricValue OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmCurReportEntry 6 }

   tpmCurReportCompletion OBJECT-TYPE
       SYNTAX      INTEGER {
                       current(1),
                       completed(2)
                   }
       MAX-ACCESS  read-only

Top      Up      ToC       Page 41 
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmCurReportEntry 7 }

   tpmCurReportSize OBJECT-TYPE
       SYNTAX      Unsigned32
       MAX-ACCESS  read-write
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmReports 4 }

   --
   -- The tpmExceptionReportsGroup
   --

   tpmExcpReportTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF TpmExcpReportEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "This table contains all sub-flow metrics for transactions
           that have been tagged by the apmExceptionTable filter
           as having had poor performance."
       ::= { tpmReports 5 }

   tpmExcpReportEntry OBJECT-TYPE

Top      Up      ToC       Page 42 
       SYNTAX      TpmExcpReportEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "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."
       INDEX { apmAppDirAppLocalIndex,       -- Application
               apmAppDirResponsivenessType,  -- Responsiveness Type
               apmExceptionIndex,            -- Linkage to ApmExceptions
               tpmExcpReportTransMetricIndex -- Metric and Protocol
             }
       ::= { tpmExcpReportTable 1 }

   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
   }

   tpmExcpReportTransMetricIndex OBJECT-TYPE
       SYNTAX      TpmTransactionMetricIndex
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION

Top      Up      ToC       Page 43 
            "A unique index that identifies the transaction and
            metric associated with the data reported here."
       ::= { tpmExcpReportEntry 1 }

   tpmExcpReportStatN OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 2 }

   tpmExcpReportOverflowStatN OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 3 }

   tpmExcpReportHCStatN OBJECT-TYPE
       SYNTAX      ZeroBasedCounter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 4 }

   tpmExcpReportStatSumX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The sum of all the data point values for the specified
           metric.  This number always represents the total values

Top      Up      ToC       Page 44 
           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."
       ::= { tpmExcpReportEntry 5 }

   tpmExcpReportOverflowStatSumX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 6 }

   tpmExcpReportHCStatSumX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 7 }

   tpmExcpReportStatMaximum OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 8 }

   tpmExcpReportStatMinimum OBJECT-TYPE

Top      Up      ToC       Page 45 
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 9 }

   tpmExcpReportStatSumSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 10 }

   tpmExcpReportOverflowStatSumSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 11 }

   tpmExcpReportHCStatSumSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION

Top      Up      ToC       Page 46 
           "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."
       ::= { tpmExcpReportEntry 12 }

   tpmExcpReportStatSumIX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 13 }

   tpmExcpReportOverflowStatSumIX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 14 }

   tpmExcpReportHCStatSumIX OBJECT-TYPE
       SYNTAX      ZeroBasedCounter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 15 }

   tpmExcpReportStatSumIXSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "For each interval, each data point is associated with a

Top      Up      ToC       Page 47 
           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."
       ::= { tpmExcpReportEntry 16 }

   tpmExcpReportOverflowStatSumIXSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 17 }

   tpmExcpReportHCStatSumIXSq OBJECT-TYPE
       SYNTAX      ZeroBasedCounter64
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "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."
       ::= { tpmExcpReportEntry 18 }

   --
   -- TPM Conformance
   --

   tpmMIBCompliances  OBJECT IDENTIFIER ::= { tpmConformance 1 }
   tpmGroups          OBJECT IDENTIFIER ::= { tpmConformance 2 }

   --
   -- TPM Compliance Statement
   --

   tpmMIBCompliance MODULE-COMPLIANCE
       STATUS  current
       DESCRIPTION
           "Describes the requirements for conformance to
           the TPM-MIB.

           This compliance statement defines the following

Top      Up      ToC       Page 48 
           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."
       MODULE -- this module

       MANDATORY-GROUPS
           { tpmCapabilitiesGroup,
             tpmAggregateReportsGroup }

       GROUP tpmCurrentReportsGroup
       DESCRIPTION
           "The implementation of this group is optional."

       GROUP tpmExceptionReportsGroup
       DESCRIPTION
           "The implementation of this group is optional.
           However, because the control for this reporting group
           resides with the APM-MIB module, the apmReportGroup
           and the apmExceptionGroup must also be implemented."

       ::= { tpmMIBCompliances 1 }

   --
   -- tpmCurrentReportsGroup Compliance
   --
   tpmCurrentReportsCompliance MODULE-COMPLIANCE
           STATUS  current
           DESCRIPTION
               "This defines the Current Reports compliance.
                This is useful when information on in-progress
                and historical transaction-level data is
                desired."
           MODULE -- this module

           MANDATORY-GROUPS
               { tpmCapabilitiesGroup,

Top      Up      ToC       Page 49 
                 tpmAggregateReportsGroup,
                 tpmCurrentReportsGroup }

       ::= { tpmMIBCompliances 2 }

   --
   -- tpmExceptionReportsGroup Compliance
   --
   tpmExceptionReportsCompliance MODULE-COMPLIANCE
           STATUS  current
           DESCRIPTION
               "This defines the Exception Reports compliance.
                This is useful when information on
                transactions whose performance is deemed
                out-of-bounds."

           MODULE -- this module

           MANDATORY-GROUPS
               { tpmCapabilitiesGroup,
                 tpmAggregateReportsGroup,
                 tpmExceptionReportsGroup }

           MODULE APM-MIB

           MANDATORY-GROUPS
               { apmReportGroup,
                 apmExceptionGroup }

       ::= { tpmMIBCompliances 3 }

   --
   --  TPM-MIB Groups
   --

   tpmCapabilitiesGroup    OBJECT-GROUP
       OBJECTS { tpmClockResolution,
                 tpmClockMaxSkew,
                 tpmClockSource,
                 tpmTransMetricDirLastChange,
                 tpmTransMetricProtocolIndex,
                 tpmTransMetricMetricIndex,
                 tpmTransMetricDirConfig,
                 tpmMetricDefType,
                 tpmMetricDefDirType,
                 tpmMetricDefName,
                 tpmMetricDefReference,
                 tpmMetricDefGlobalID }

Top      Up      ToC       Page 50 
       STATUS  current
       DESCRIPTION
           "The tpmCapabilitiesGroup specifies various capabilities
           associated with the monitoring agent."
       ::= { tpmGroups 1 }

   tpmAggregateReportsGroup    OBJECT-GROUP
       OBJECTS { tpmAggrReportCntrlApmCntrlIndex,
                 tpmAggrReportCntrlDataSource,
                 tpmAggrReportCntrlAggrType,
                 tpmAggrReportCntrlInterval,
                 tpmAggrReportCntrlReqSize,
                 tpmAggrReportCntrlGrantedSize,
                 tpmAggrReportCntrlReqReports,
                 tpmAggrReportCntrlGrantedReports,
                 tpmAggrReportCntrlStartTime,
                 tpmAggrReportCntrlReportNumber,
                 tpmAggrReportCntrlInsertsDenied,
                 tpmAggrReportCntrlDroppedFrames,
                 tpmAggrReportCntrlOwner,
                 tpmAggrReportCntrlStorageType,
                 tpmAggrReportCntrlStatus,
                 tpmAggrReportStatN,
                 tpmAggrReportOverflowStatN,
                 tpmAggrReportHCStatN,
                 tpmAggrReportStatSumX,
                 tpmAggrReportOverflowStatSumX,
                 tpmAggrReportHCStatSumX,
                 tpmAggrReportStatMaximum,
                 tpmAggrReportStatMinimum,
                 tpmAggrReportStatSumSq,
                 tpmAggrReportOverflowStatSumSq,
                 tpmAggrReportHCStatSumSq,
                 tpmAggrReportStatSumIX,
                 tpmAggrReportOverflowStatSumIX,
                 tpmAggrReportHCStatSumIX,
                 tpmAggrReportStatSumIXSq,
                 tpmAggrReportOverflowStatSumIXSq,
                 tpmAggrReportHCStatSumIXSq }
       STATUS  current
       DESCRIPTION
           "The tpmAggregateReportsGroup provides control
           and reporting of aggregate measurement
           statistics."
       ::= { tpmGroups 2 }

   tpmCurrentReportsGroup  OBJECT-GROUP
       OBJECTS { tpmCurReportMetricValue,

Top      Up      ToC       Page 51 
                 tpmCurReportCompletion,
                 tpmCurReportSize }
       STATUS  current
       DESCRIPTION
           "The tpmCurrentReportsGroup contains metric
           information relating to ongoing measurements
           as well as historical values."
       ::= { tpmGroups 3 }

   tpmExceptionReportsGroup  OBJECT-GROUP
       OBJECTS { tpmExcpReportStatN,
                 tpmExcpReportOverflowStatN,
                 tpmExcpReportHCStatN,
                 tpmExcpReportStatSumX,
                 tpmExcpReportOverflowStatSumX,
                 tpmExcpReportHCStatSumX,
                 tpmExcpReportStatMaximum,
                 tpmExcpReportStatMinimum,
                 tpmExcpReportStatSumSq,
                 tpmExcpReportOverflowStatSumSq,
                 tpmExcpReportHCStatSumSq,
                 tpmExcpReportStatSumIX,
                 tpmExcpReportOverflowStatSumIX,
                 tpmExcpReportHCStatSumIX,
                 tpmExcpReportStatSumIXSq,
                 tpmExcpReportOverflowStatSumIXSq,
                 tpmExcpReportHCStatSumIXSq }
       STATUS  current
       DESCRIPTION
           "The tpmExceptionReportsGroup reports
           sub-application level statistics associated
           with errant applications."
       ::= { tpmGroups 4 }

   END

5.  Acknowledgements

   This memo has been produced with a great deal of assistance from
   David Craver, Joseph Maixner, and John Metzger of Hifn, Inc.  The
   authors also gratefully acknowledge the beneficial discussions they
   have had with Carter Bullard of QoSient, LLC.  The tpmMetricDefTable
   was taken from Andy Bierman's performance management capabilities
   document, which was proposed early on in the RMON WG during the
   formation of the TPM and APM MIB work.  Finally, this MIB module
   draws heavily from the work of Steve Waldbusser and his APM-MIB
   [RFC3729].

Top      Up      ToC       Page 52 
6.  Security Considerations

   This MIB relates to a system that provides a passive monitoring
   capability of a broadcast subnet, a switched subnet, or point-to-
   point subnets.  As such, it collects information relating to network
   layer addresses and traffic statistics relating to conversations and
   to application-level activities.  These statistics could be deemed
   sensitive in certain networking environments.

   There are a number of management objects defined in this MIB module
   with a MAX-ACCESS clause of read-write and/or read-create.  Such
   objects may be considered sensitive or vulnerable in some network
   environments.  The support for SET operations in a non-secure
   environment without proper protection can have a negative effect on
   network operations.  These are the tables and objects and their
   sensitivity/vulnerability:

      + The tpmTransMetricDirConfig object describes and configures the
        probe's support for a given performance metric in relation to a
        specified transaction and application.  The agent creates
        entries in this table for all metric and transaction
        combinations that it can generate, and this object controls the
        on/off switch for this capability.  If certain statistics for a
        supported transaction are deemed sensitive, then access to SET
        operations on this object should be protected.

      + The tpmAggrReportCntrlDataSource sets the interface on which the
        network addresses and conversational and application-level
        statistics will be collected.

      + The tpmAggrReportCntrlAggrType object controls the level of data
        aggregation implemented in the report tables.  For example, this
        object could be set to allow client-level information to be
        exposed.

   In order to implement this MIB module, an agent must make certain
   management information available about protocols and network
   addresses used within a managed system, which may be considered
   sensitive in some network environments.  Therefore some of the
   readable objects in this MIB module (i.e., objects with a MAX-ACCESS
   other than not-accessible) may be considered sensitive or vulnerable
   in some network environments.  It is thus important to control even
   GET and/or NOTIFY access to these objects and possibly to even
   encrypt the values of these objects when sending them over the
   network via SNMP.  These are the tables and objects and their
   sensitivity/vulnerability:

Top      Up      ToC       Page 53 
      + The tpmAggrReportTable contains the statistical studies which
        the probe was configured to generate.  These tables contain the
        historical, aggregated data providing information on the network
        address and traffic statistics related to their conversations.

      + The tpmCurReportTable contains information on current
        transaction flows.  This table provides a view of the current
        activity on a subnet or a client machine.

   SNMP versions prior to SNMPv3 did not include adequate security.
   Even if the network itself is secure (for example by using IPSec),
   even then, there is no control as to who on the secure network is
   allowed to access and GET/SET (read/change/create/delete) the objects
   in this MIB module.

   It is RECOMMENDED that implementers consider the security features as
   provided by the SNMPv3 framework (see [RFC3410], section 8),
   including full support for the SNMPv3 cryptographic mechanisms (for
   authentication and privacy).

   Further, deployment of SNMP versions prior to SNMPv3 is NOT
   RECOMMENDED.  Instead, it is RECOMMENDED to deploy SNMPv3 and to
   enable cryptographic security.  It is then a customer/operator
   responsibility to ensure that the SNMP entity giving access to an
   instance of this MIB module is properly configured to give access to
   the objects only to those principals (users) that have legitimate
   rights to indeed GET or SET (change/create/delete) them.

7.  Normative References

   [RFC2021]   Waldbusser, S., "Remote Network Monitoring Management
               Information Base Version 2 using SMIv2", RFC 2021,
               January 1997.

   [RFC2026]   Bradner, S., "The Internet Standards Process -- Revision
               3", BCP 9, RFC 2026, October 1996.

   [RFC2578]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
               Rose, M., and S. Waldbusser, "Structure of Management
               Information Version 2 (SMIv2)", STD 58, RFC 2578, April
               1999.

   [RFC2579]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
               Rose, M., and S. Waldbusser, "Textual Conventions for
               SMIv2", STD 58, RFC 2579, April 1999.

Top      Up      ToC       Page 54 
   [RFC2580]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
               Rose, M., and S. Waldbusser, "Conformance Statements for
               SMIv2", STD 58, RFC 2580, April 1999.

   [RFC2819]   Waldbusser, S., "Remote Network Monitoring MIB", STD 59,
               RFC 2819, May 2000.

   [RFC2856]   Bierman, A., McCloghrie, K., and R. Presuhn, "Textual
               Conventions for Additional High Capacity Data Types", RFC
               2856, June 2000.

   [RFC2895]   Bierman, A., Bucci, C., and R. Iddon, "Remote Network
               Monitoring MIB Protocol Identifiers", RFC 2895, August
               2000.

   [RFC3273]   Waldbusser, S., "Remote Network Monitoring Management
               Information Base for High Capacity Networks", RFC 3273,
               July 2002.

   [RFC3395]   Bierman, A., Bucci, C., Dietz, R., and A. Warth "Remote
               Network Monitoring MIB Protocol Identifiers Reference
               Extensions", RFC 3395, September 2002.

   [RFC3411]   Harrington, D., Presuhn, R., and B. Wijnen, "An
               Architecture for Describing Simple Network Management
               Protocol (SNMP) Management Frameworks", RFC 3411,
               December 2002.

   [RFC3729]   Waldbusser, S., "Application Performance Measurement
               MIB", RFC 3729, March 2004.

   [RFC4149]   Kalbfleisch, K., Cole, R., and D. Romascanu, "Definition
               of Managed Objects for Synthetic Sources for Performance
               Monitoring Algorithms", RFC 4149, August 2005.

   [RFC4148]   Stephan, E., "IP Performance Metrics (IPPM) Metrics
               Registry", RFC 4148, August 2005.

8.  Informative References

   [RFC3410]   Case, J., Mundy, R., Partain, D., and B. Stewart,
               "Introduction and Applicability Statements for Internet-
               Standard Management Framework", RFC 3410, December 2002.

   [Y.1540]    The ITU-T Recommendation Y.1540, "IP Data Transport
               Service - IP packet transfer performance metrics", ITU-T
               Rec.  Y.1540, December 2002.

Top      Up      ToC       Page 55 
   [RFC2679]   Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way
               Delay Metric for IPPM", RFC 2679, September 1999.

   [RFC2680]   Almes, G., Kalidindi, S., and M. Zekauskas, "A One-Way
               Packet Loss Metric for IPPM" RFC 2680, September 1999.

   [RFC2681]   Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-Trip
               Delay Metric for IPPM", RFC 2681, September 1999.

   [RFC3393]   Demichelis, C. and P. Chimento, "IP Packet Delay
               Variation Metric for IP Performance Metrics (IPPM)", RFC
               3393, November 2002.

   [RFC3432]   Raisanen, V., Grotefeld, G., and A. Morton, "Network
               Performance Measurement with Periodic Streams", RFC 3432,
               November 2002.

Top      Up      ToC       Page 56 
Authors' Addresses

   Russell Dietz
   Hifn, Inc.
   750 University Ave
   Los Gatos, CA, USA 95032-7695

   Tel: +1 408 399-3623
   Fax: +1 408 399-3501
   EMail: rdietz@hifn.com


   Robert Cole
   Johns Hopkins University Applied Physics Laboratory
   MP2-170
   11100 Johns Hopkins Road
   Laurel, MD 20723-6099
   USA

   Tel: +1 443-778-6951
   EMail: robert.cole@jhuapl.edu

Top      Up      ToC       Page 57 
Full Copyright Statement

   Copyright (C) The Internet Society (2005).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM 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 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights 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; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at ietf-
   ipr@ietf.org.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.