idnits 2.17.1 draft-ietf-rmonmib-tpm-mib-14.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2652. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2663. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2670. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2676. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 39), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 39. ** Found boilerplate matching RFC 3979, Section 5, paragraph 3 (on line 2676), which is fine, but *also* found old RFC 2026, Section 10.4B text on line 2452. ** The document claims conformance with section 10 of RFC 2026, but uses some RFC 3978/3979 boilerplate. As RFC 3978/3979 replaces section 10 of RFC 2026, you should not claim conformance with it if you have changed to using RFC 3978/3979 boilerplate. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 1087: '... MUST respond as if the object ...' RFC 2119 keyword, line 2608: '... It is RECOMMENDED that implementers...' RFC 2119 keyword, line 2614: '... RECOMMENDED. Instead, it is RECOMM...' Miscellaneous warnings: ---------------------------------------------------------------------------- == In addition to RFC 3979, Section 5, paragraph 1 boilerplate, a section with a similar start was also found: The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF Secretariat." == In addition to RFC 3979, Section 5, paragraph 3 boilerplate, a section with a similar start was also found: The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 446 has weird spacing: '...t value for t...' == Line 1662 has weird spacing: '...ll only be in...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 28, 2004) is 7240 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2819' is defined on line 2488, but no explicit reference was found in the text == Unused Reference: 'RFC2856' is defined on line 2491, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 2506, but no explicit reference was found in the text == Unused Reference: 'RFCXXX2' is defined on line 2513, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2021 (Obsoleted by RFC 4502) -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCXXX2' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCXXX3' -- Obsolete informational reference (is this intentional?): RFC 2679 (Obsoleted by RFC 7679) -- Obsolete informational reference (is this intentional?): RFC 2680 (Obsoleted by RFC 7680) Summary: 12 errors (**), 0 flaws (~~), 10 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Russell Dietz 2 Hifn, Inc. 3 Robert Cole 4 JHU/APL 5 June 28, 2004 7 Transport Performance Metrics MIB 9 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026 [RFC2026]. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 This document is an Internet-Draft. Internet-Drafts are working 30 documents of the Internet Engineering Task Force (IETF), its areas, 31 and its working groups. Note that other groups may also distribute 32 working documents as Internet-Drafts. 34 Distribution of this document is unlimited. Please send comments to 35 the authors, and . 37 Copyright Notice 39 Copyright (C) The Internet Society (2004). All Rights Reserved. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it describes managed objects used for monitoring 46 selectable performance metrics and statistics derived from the 47 monitoring of network packets and sub-application level transactions. 48 The metrics can be defined through reference to existing IETF, ITU 49 and other standards organizations' documents. The monitoring covers 50 both passive and active traffic generation sources. 52 1. Table of Contents 54 Copyright Notice . . . . . . . . . . . . . . . . . . . . . . . . . . 1 55 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 56 1. Table of Contents . . . . . . . . . . . . . . . . . . . . . . 3 57 2. The SNMP Management Framework . . . . . . . . . . . . . . . . 4 58 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 3.1. Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 60 3.2. Report Aggregations . . . . . . . . . . . . . . . . . . . . . 6 61 3.3. Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 6 62 3.4. Statistics for Aggregation of Data - Conventions . . . . . . . 7 63 3.5. Relationship to the Remote Monitoring MIB . . . . . . . . . . 8 64 3.6. Relationship to RMON2-MIB Protocol Identifier Reference . . . 8 65 3.7. Relationship to Standards-Based Performance Metrics . . . . . 8 66 3.8. Relationship to Application Performance Measurement MIB . . . 8 67 4. Statistics Perspective . . . . . . . . . . . . . . . . . . . . 9 68 4.1. Statistics Structure . . . . . . . . . . . . . . . . . . . . . 10 69 4.2. Statistics Analysis . . . . . . . . . . . . . . . . . . . . . 11 70 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 12 71 6. Intellectual Property . . . . . . . . . . . . . . . . . . . . 53 72 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 53 73 8. Normative References . . . . . . . . . . . . . . . . . . . . . 54 74 9. Informative References . . . . . . . . . . . . . . . . . . . . 55 75 10. Security Considerations . . . . . . . . . . . . . . . . . . . 56 76 11. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 58 77 12. Full Copyright Statement . . . . . . . . . . . . . . . . . . 59 78 2. The Internet-Standard Management Framework 80 For a detailed overview of the documents that describe the current 81 Internet-Standard Management Framework, please refer to section 7 of 82 RFC 3410 [RFC3410]. 84 Managed objects are accessed via a virtual information store, termed 85 the Management Information Base or MIB. MIB objects are generally 86 accessed through the Simple Network Management Protocol (SNMP). 87 Objects in the MIB are defined using the mechanisms defined in the 88 Structure of Management Information (SMI). This memo specifies a MIB 89 module that is compliant to the SMIv2, which is described in STD 58, 90 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 91 [RFC2580]. 93 3. Overview 95 This document continues the architecture created in the RMON2-MIB 96 [RFC2021] by providing a major feature upgrade, primarily by 97 providing new metrics and studies to assist in the analysis of 98 performance for sub-application transaction flows in the network, in 99 direct relationship to the transporting of application layer 100 protocols. 102 Performance monitoring agents have been widely used to analyze the 103 parameters and metrics related to the perceived performance of 104 distributed applications and services in networks. The metrics 105 collected by these agents have ranged from basic response time to a 106 combination of metrics related to the loss and re-transmission of 107 datagrams and PDUs. While the metrics are becoming more useful in the 108 implementation of service level monitoring and troubleshooting tools, 109 the lack of a standard method to report these has limited the 110 deployment to very specific customer needs and areas. 112 This document is intended to create a general framework for the 113 collection and reporting of performance related metrics on sub- 114 application level transaction flows in a network. The MIB in this 115 document in directly linked to the current RMON2-MIB [RFC2021] and 116 uses the Protocol Directory as a key component in reporting the 117 layering involved in the sub-application level transaction flows. 119 The specific objectives of this document are to: 121 + Provide a drill-down capability to compliment the user-perceived 122 monitoring defined within the APM-MIB [RFC3729]. This capability 123 is intended to support trouble resolution, further 124 characterization of performance, and a finer granularity of 125 monitoring capabilities. The APM-MIB provides a method for 126 retrieving aggregated measurement data of the end-user's 127 perception of application-level performance. APM additionally 128 provides thresholding and associated alarms in the event the end- 129 user perceived performance degrades below defined thresholds. The 130 TPM-MIB compliments the APM-MIB capabilities by monitoring sub- 131 application level transaction aspects not typically perceived by 132 the end-user. As an example, APM-MIB provides response time 133 statistics of a typical web-browser application. This application 134 typically consists of DNS transactions, TCP connection 135 establishment (or multiple establishments), HTTP download of the 136 base page and multiple downloads of the various embedded objects. 137 Ideally TPM-MIB would provide statistics on the performance 138 aspects of these multiple sub-application level transactions. 140 + Provide additional performance metrics and related statistics. 141 For trouble shooting and a finer granularity of performance 142 monitoring, it is useful to provide measurements of additional 143 metrics beyond those supported by the APM-MIB. 145 + Support standards based metrics and associated statistical 146 aggregation by defining methods to reference those standards. The 147 TPM-MIB provides a capability to describe metrics by reference to 148 appropriate IETF, ITU or other, including enterprise specific, 149 standards bodies defining metrics. This capability is provided 150 through the tpmMetricsDefTable. 152 Specifically, this MIB itself does not make references to such 153 IETF, ITU and other organization's metric specifications. What it 154 does do is to allow for the setup of the tpmMetricDefTable that 155 does reference such IETF, ITU and other metric specifications, and 156 it allows to (dynamically) list pointers to such specifications in 157 this table. The following objects do allow for that, and the 158 DESCRIPTION clauses (of the below objects) explain how such is 159 done: 161 tpmMetricDefName OBJECT-TYPE 162 tpmMetricDefReference OBJECT-TYPE 163 tpmMetricDefGlobalID OBJECT-TYPE 165 The tpmMetricDefGlobalID object contains a reference to the Object 166 ID in a metrics registration MIB being developed in the IPPM 167 Working Group at the IETF, e.g., the IPPM-REGISTRY-MIB [RFCXXX3], 168 which defines the metric. For metrics defined within the IPPM 169 Working Group, which are included in the IPPM-REGISTRY-MIB, this 170 object is used to reference those metrics directly. For metrics 171 not included within the IPPM-REGISTRY-MIB, the value of this 172 object is set to 0.0 for none. 174 Examples of appropriate references include the ITU-T 175 Recommendation Y.1540 [Y.1540] on IP packet transfer performance 176 metrics or the IETF documents from the IPPM WG, e.g., RFC2681 on 177 the round trip delay metric [RFC2681] or RFC3393 on the delay 178 variation metric [RFC3393] or others, including RFC2679 [RFC2679], 179 RFC2680 [RFC2680], and RFC3432 [RFC3432]. While no specific 180 metric is mandatory, implementations should, at a minimum, support 181 a round trip delay and a round trip loss metric. 183 + Provide (as an option) a table storing the measurements of the 184 metrics on a transaction by transaction basis. There are times 185 when it is useful to have access to the raw measurements. The 186 tpmCurReportTable optionally provides access to this capability. 188 While this document outlines the basic measurements of performance in 189 regard to the transporting of application flows, it does not attempt 190 to measure or provide a means to measure the actual perceived 191 performance of the application transactions or quality. The detailed 192 measurements of end-user perceived performance is directly related to 193 this document and may be found in the APM-MIB [RFC3729]. 195 The objects defined in this document are intended as an interface 196 between an RMON agent and an RMON management application and are not 197 intended for direct manipulation by humans. While some users may 198 tolerate the direct display of some of these objects, few will 199 tolerate the complexity of manually manipulating objects to 200 accomplish row creation. These functions should be handled by the 201 management application. 203 3.1. Terms 205 This document uses some terms that need introduction: 207 DataSource 208 A source of data for monitoring purposes. This term is used 209 exactly as defined in the RMON2-MIB [RFC2021]. 211 protocol 212 A specific protocol encapsulation, as identified for monitoring 213 purposes. This term is used exactly as defined in the RMON 214 Protocol Identifiers document [RFC2895]. 216 performance metric 217 A specific, measured reporting metric, as identified for 218 monitoring purposes. There can be several metrics reported by 219 an agent in the same implementation. The metrics are 220 extensible based on the agent implementation. 222 application 223 A network-based, high-level protocol performing useful work 224 to an end-user of end-system. Typically the application 225 performs multiple request/response transactions to complete 226 its work. E.g., a web-application downloading a web page 227 completes DNS, TCP-connect and multiple HTTP GET transactions 228 prior to completing its task. 230 transactions 231 Elemental request/response transactions comprising more 232 complex network-based applications. E.g., a transaction 233 may include an ftp get request and the file download in 234 response. 236 3.2. Report Aggregation 238 This MIB module provides functions to aggregate measurements into 239 higher level summaries identical to the aggregation defined in the 240 APM-MIB [RFC3729]. In addition to temporal aggregation of data, the 241 Textual Convention, TransactionAggregationType, is imported from the 242 APM-MIB, which specifies the nature of the spatial aggregation 243 employed. 245 3.3. Structure of the MIB 247 The objects are arranged in the following groups: 249 -- tpmCapabilitiesGroup 251 -- tpmAggregateReportsGroup 253 -- tpmCurrentReportsGroup 255 -- tpmExceptionReportsGroup 257 These groups are the basic unit of conformance. If an agent 258 implements a group, then it must implement all objects in that group. 259 While this section provides an overview of grouping and conformance 260 information for this MIB module, the authoritative reference for such 261 information is contained in the MODULE-COMPLIANCE and OBJECT-GROUP 262 macros later in this MIB module. 264 These groups are defined to provide a means of assigning object 265 identifiers, and to provide a method for implementers of managed 266 agents to know which objects they must implement. 268 3.3.1. The tpmCapabilitiesGroup 270 The tpmCapabilitiesGroup contains objects and tables which show the 271 measurement protocol and metric capabilities of the agent. This group 272 primarily consists of the tpmTransMetricDirTable and the 273 tpmMetricDefTable. 275 3.3.2. The tpmAggregateReportsGroup 277 The tpmAggregateReportsGroup is used to provide the collection of 278 aggregated statistical measurements for the configured report 279 intervals. The tpmAggregateReportsGroup consists of the 280 tpmAggrReportCntrlTable and the tpmAggrReportTable. 282 3.3.3. The tpmCurrentReportsGroup 284 The tpmCurrentReportsGroup is used to provide the collection of 285 uncompleted measurements for the current configured report for those 286 transactions caught in progress. A history of these transactions is 287 also maintained once the current transaction has completed. The 288 tpmCurrentReportsGroup consists of the tpmCurReportTable and the 289 tpmCurReportSize object. 291 3.3.4. The tpmExceptionReportsGroup 293 The tpmExceptionReportsGroup is used to link immediate notifications 294 of transactions that exceed certain thresholds defined in the 295 apmExceptionGroup [RFC3729]. This group reports the aggregated sub- 296 application measurements for those applications exceeding thresholds. 297 The tpmExceptionReportsGroup consists of the tpmExcpReportTable. 299 3.4. Statistics for Aggregation of Data - Conventions 301 In order to measure the performance of traffic flows in a network, 302 the proper analysis of a set of statistics is required. Since a 303 large majority of the statistics have a basis of time, the use of a 304 simple statistical model is feasible. Therefore, the MIB definitions 305 within this document all use a basic set of statistical computed 306 values to assist in further analysis by a management application. 308 The remaining subsections in this section detail the common 309 structured features the are applied to the performance metrics in the 310 statistical format described above. The tpmMetricsDefTable 311 (discussed below) describes the set of metrics supported in this MIB 312 module. 314 3.5. Relationship to the Remote Monitoring MIB 315 This document describes the implementation of an additional MIB for 316 the support of performance related metrics within the framework of 317 the RMON2-MIB [RFC2021]. The objects and table defined in this MIB 318 module are an extension to the existing framework for the support of 319 both Client/Server and Server push related applications and services. 321 3.6. Relationship to RMON2-MIB Protocol Identifier Reference 323 This document uses the Protocol Identifiers outlined in the current 324 Protocol Identifier Reference document, RFC 2895 [RFC2895]. The 325 protocol index values throughout the document are a direct reference 326 to the same relationship that exists between the RMON2-MIB [RFC2021] 327 and the Protocol Identifier Reference document, RFC 2895 [RFC2895]. 328 An important extension of the Protocol Identification to application- 329 level verbs is found in RFC 3395 [RFC3395]. 331 3.7. Relationship to Standards-Based Performance Metrics 333 This document uses the tpmMetricsDefTable to describe the metrics 334 supported by an instance of the TPM-MIB. The performance metric 335 index values throughout the document are a direct reference to the 336 metrics defined in that table. The table defines metrics by directly 337 referencing other standards that provide definitive descriptions of 338 the metric. 340 3.8. Relationship to Application Performance Measurement MIB 342 This document uses the apmReportControlIndex, appLocalIndex and 343 apmReportIndex as outlined in the current Application Performance 344 Measurement MIB [RFC3729]. These objects are used to create a 345 reference link for the purpose of reporting transaction flow details 346 on application level measurements. As such, the TPM-MIB is designed 347 to provide a drill-down extension to the APM-MIB. Further, it draws 348 heavily on the ideas and designs laid out in the APM-MIB. 350 4. Statistics Perspective 352 When dealing with time based measurements on application data packets 353 it would be ideal if all the timestamps and related data could be 354 stored and forwarded for later analysis. However when faced with 355 thousands of conversations per second on ever faster networks, 356 storing all the data, even if compressed, would take too much 357 processing, memory, and manager download time to be practical. 359 It is important to note that in dealing with network data we will be 360 dealing with statistical populations and not samples. Statistics 361 books deal with both because the math is similar. In collecting 362 agent data a population, i.e., all the data, must be processed. 364 Because of the nature of application protocols just sampling some of 365 the packets will not give good results. Missing just one critical 366 packet, such as one that specified an ephemeral port on which data 367 will be transmitted, or what application will be run, can cause much 368 valid data to be lost. 370 The time-based measurements the agent collects will come from 371 examining the entire group of data, i.e., the population. The 372 population will be finite. The agent will seek only to provide 373 information that will describe the actual data. Analysis of that data 374 will be left to the management station. 376 The simplest form of representing a group of data is by frequency 377 distributions, i.e., buckets. Statistics provides a great many ways 378 of analyzing this type of data and there are some rules in creating 379 the buckets. First the range needs to be known. Second a bucket size 380 needs to be determined. Fixed bucket sizes are best, while variable 381 may be used if needed. However the statistics texts tend to only 382 refer to operations of fixed size buckets. This method of describing 383 data is expensive for a agent to implement. First the agent must 384 process a great amount of data at a time. In storing the data, 385 determine the range, then locating the buckets and then fill in the 386 data after the fact, takes a fair amount of storage and time. Fixing 387 the range and bucket sizes in the beginning can be problematical as 388 the agent may have to adjust the values for each of the applications 389 it collects data on. Such numbers can be in the thousands. 390 Additional complexity arises in adding new protocols and even in 391 describing the buckets themselves to the management application. This 392 is the approach taken in the APM-MIB. 394 A complimentary approach is to provide frequency distribution 395 statistics. Frequency distribution statistics describes aggregation 396 such as mean and standard deviation that can be obtained by summation 397 functions on the individual data elements in a population. Analysis 398 of the data described by these functions has been greatly studied and 399 interpretation of these values is available to anyone with an 400 introduction to statistics. In fact, frequency distributions are 401 routinely analyzed to generate these varied numbers which are then 402 used for further analysis. Also note that frequency distributions by 403 their very nature provide an exact characterization of the data. 404 Whereas buckets, will introduce error factors that are not present 405 with direct analysis by a summation type formulas. Because the TPM- 406 MIB provides a drill-down capability to the APM MIB it has to measure 407 and store much more information than the APM-MIB. For this reason, 408 and to compliment the APM-MIB, the TPM-MIB relies on statistical 409 descriptions rather than a bucket description of the measurement 410 data. 412 The agent will provide data that can be used to calculate the most 413 basic and useful statistical aggregates. The agent will not perform 414 the calculations and provide the statistical measurement directly. 415 There are several reason why this is not desired. The first is that 416 to find the final measurement can be expensive in terms of 417 computation and representation. There are divisions and square roots 418 and the measurements are expressed as floating point values. The 419 second is that by providing the variables to the statistical 420 functions, those variables are scalable. It is possible to combine 421 smaller intervals into larger ones. 423 An example is the arithmetic mean or average. This is the sum of the 424 data divided by the number of data elements. The agent will provide 425 the sum of the x and the number of elements N. The management station 426 can perform the division to obtain the average. Given two samples, 427 they can be combined by adding the sum of the x's and by adding the 428 number of elements to get a combined sum and number of elements. The 429 average formula then works just the same. Also the sum of the x and 430 the number of element variables are used in calculating other 431 statistical measurement values as well. 433 4.1. Statistics Structure 435 The data statistical elements, datum, of the metric have been chosen 436 to maximize the amount of data available while minimizing the amount 437 of memory needed to store the statistic and minimizing the CPU 438 processing requirement needed to generate the statistic. 440 The statistic data structure contains five unsigned integer datum. 442 N count of the number of data points for the metric 443 S(X) sum of all the data point values for the metric 444 S(X2) sum of all the data point values squared for the metric 445 Xmax maximum data point value for the metric 446 Xmin minimum data point value for the metric 447 S(I*X) sum of the data points multiplied by their order, i.e., 448 = SUM from i=1 to N { i*X sub i} 450 A performance metric is used to describe events over a time interval. 451 The measurement points can be processed immediately into the 452 statistic and do not have to be stored for later processing. For 453 example, to count the number of events in a time interval it is 454 sufficient to increment a counter for each event. It is not 455 necessary to cache all the events and then count them at the end of 456 the interval. The statistic is also designed to be easily scalable in 457 terms of combining adjacent intervals. For example if an agent 458 created a specific statistic every 30 seconds and a user table 459 interval was set to 60 seconds, the 60 second statistic could be 460 obtained by combining the two 30 second statistics. The following 461 rules will be applied when combining adjacent statistics. 463 N S(N) 464 S(X) S(S(X)) 465 S(X2) S(S(X2)) 466 Xmax MAX(Xmax) 467 Xmin MIN(Xmin) 468 S(I*X) S(I*X) + N*S(X) +S(I*X) 469 where the last two terms refer to the 470 statistics from the later 30 second period 471 and N is the count from the former 30 second 472 period. 474 This structure gives a generic framework upon which the actual 475 performance statistics will be defined. Each specific statistical 476 definition must address the specific significance, if any, given to 477 each of the metric datum. While a specific metric definition should 478 try to conform to the generic framework, it is acceptable for a 479 metric datum to not be used, and to have no meaning, for a specific 480 metric. In such cases the datum will default to a 0 value. 482 4.2. Statistics Analysis 484 The actual meaning of a specific statistical datum is determined by 485 the definition of the specific statistic. The following is a 486 discussion of the operations and observations that can be performed 487 on a generic metric. This means that the following may or may not 488 apply and/or have meaning when applied to any specific metric. 490 The following observations and analysis techniques are not all 491 inclusive. Rather these are the ones we have come up with at the 492 time of writing this document. 494 + Number. 496 + Frequency. 498 + The time interval is the time interval specified in the control 499 table. It is not a metric datum, but it is associated with the 500 metric sample. 502 + Maximum 504 + Minimum 506 + Range 507 + Arithmetic Mean 509 + Root Mean Square 511 + Variance 513 + Standard Deviation 515 + Slope of a least-squares line 517 These are accessible from the statistical datum provided by this MIB 518 module. 520 5. Definitions 522 -- 523 -- RMON2-MIB Extensions for the Monitoring metrics related to the 524 -- performance of transporting traffic in networks. 525 -- 526 -- TPM Metric Collection 527 -- * Application-to-Protocol transaction linkage 528 -- * Metric-to-Protocol linkage 529 -- * Metric study control 530 -- * Metrics for Client/Server Conversations 531 -- 533 TPM-MIB DEFINITIONS ::= BEGIN 535 IMPORTS 536 MODULE-IDENTITY, OBJECT-TYPE, 537 Counter32, Unsigned32 FROM SNMPv2-SMI --[RFC2578] 539 MODULE-COMPLIANCE, 540 OBJECT-GROUP FROM SNMPv2-CONF --[RFC2580] 542 SnmpAdminString FROM SNMP-FRAMEWORK-MIB --[RFC3411] 544 RowStatus, TEXTUAL-CONVENTION, TimeStamp, 545 StorageType FROM SNMPv2-TC --[RFC2579] 547 rmon, OwnerString FROM RMON-MIB --[RFC2819] 549 protocolDirLocalIndex, 550 ZeroBasedCounter32 FROM RMON2-MIB --[RFC2021] 552 ZeroBasedCounter64 FROM HCNUM-TC --[RFC2856] 553 AppLocalIndex, TransactionAggregationType, 554 RmonClientID, DataSourceOrZero, 555 apmAppDirAppLocalIndex, apmExceptionIndex, 556 apmReportGroup, apmExceptionGroup, 557 apmAppDirResponsivenessType FROM APM-MIB --[RFC3729] 559 SspmClockSource, SspmClockMaxSkew, 560 SspmMicroSeconds FROM SSPM-MIB; --[RFCXXX2] 562 -- Transaction Performance Monitoring MIB 564 tpmMIB MODULE-IDENTITY 565 LAST-UPDATED "200406281500Z" -- 28 June 2004 566 ORGANIZATION "IETF RMON MIB Working Group" 567 CONTACT-INFO 568 "E-mail: rmonmib@ietf.org 569 Subscribe: rmonmib-request@ietf.org 570 w/ msg body: subscribe rmonmib 572 Russell Dietz 573 Hifn, Inc. 574 Postal: 750 University Ave 575 Los Gatos, CA 95032-7695 576 USA 577 Tel: +1 408 399-3623 578 Fax: +1 408 399-3501 579 E-mail: rdietz@hifn.com 581 Robert G. Cole 582 Johns Hopkins University Applied Physics Laboratory 583 Postal: MP2-170 584 11100 Johns Hopkins Road 585 Laurel, MD 20723-6099 586 USA 587 Tel: +1 443 778-6951 588 E-mail: robert.cole@jhuapl.edu" 589 DESCRIPTION 590 "This module defines extensions to the RMON2-MIB module 591 for the collection of Performance Metrics related to 592 application traffic in a network. In particular, 593 it describes managed objects used for monitoring 594 selectable performance metrics and statistics 595 derived from the monitoring of network packets and 596 sub-application level transactions. 598 In order to maintain the RMON 'look-and-feel', some of 599 the text from the RMON2 [RFC2021] and HC-RMON [RFC3273] 600 MIBs by Steve Waldbusser have been used in this MIB module. 602 Copyright (C) The Internet Society (year). This version of 603 this MIB module is part of RFC xxxx; see the RFC itself for 604 full legal notices." 606 REVISION "200406281500Z" -- 28 June 2004 607 DESCRIPTION 608 "The original version of this MIB module, 609 published as RFCXXXX." 610 -- RFC-Editor assigns XXXX 611 ::= { rmon nn } -- To be assigned by IANA 612 -- We suggest a value of 30 for nn 614 -- 615 -- Object Identifier Assignments 616 -- 618 tpmCapabilities OBJECT IDENTIFIER ::= { tpmMIB 1 } 619 tpmReports OBJECT IDENTIFIER ::= { tpmMIB 2 } 620 tpmConformance OBJECT IDENTIFIER ::= { tpmMIB 3 } 622 -- tpmAggrReportCntrlTable OBJECT IDENTIFIER ::= { tpmReports 1 } 623 -- tpmAggrReportTable OBJECT IDENTIFIER ::= { tpmReports 2 } 624 -- tpmCurReportTable OBJECT IDENTIFIER ::= { tpmReports 3 } 625 -- tpmCurReportSize OBJECT IDENTIFIER ::= { tpmReports 4 } 626 -- tpmExcpReportTable OBJECT IDENTIFIER ::= { tpmReports 5 } 628 -- 629 -- Textual Conventions 630 -- 632 TpmTransactionMetricIndex ::= TEXTUAL-CONVENTION 633 DISPLAY-HINT "d" 634 STATUS current 635 DESCRIPTION 636 "An index used to uniquely identify an entry in the 637 tpmTransMetricDir table. Each such entry defines 638 the protocol transaction and metric instance to be 639 monitored for a specific application." 640 SYNTAX Unsigned32 (1..65535) 642 TpmMetricDefID ::= TEXTUAL-CONVENTION 643 DISPLAY-HINT "d" 644 STATUS current 645 DESCRIPTION 646 "An index that identifies through reference to a specific 647 performance metric. The metrics are referenced 648 through their type (connect, delay, loss, etc.), their 649 directional characteristics (one-way, round trip, etc.), 650 their name, their reference to a documented definition." 651 SYNTAX Unsigned32 (1..2147483647) 653 -- 654 -- The tpmCapabilitiesGroup 655 -- 657 tpmClockResolution OBJECT-TYPE 658 SYNTAX SspmMicroSeconds 659 MAX-ACCESS read-only 660 STATUS current 661 -- UNITS Microseconds 662 DESCRIPTION 663 "A read only variable indicating the resolution 664 of the measurements possible by this device." 665 ::= { tpmCapabilities 1 } 667 tpmClockMaxSkew OBJECT-TYPE 668 SYNTAX SspmClockMaxSkew 669 MAX-ACCESS read-only 670 STATUS current 671 -- UNITS Seconds 672 DESCRIPTION 673 "A read only variable indicating the maximum 674 offset error due to skew of the local clock 675 over the time interval 86400 seconds, in seconds." 676 ::= { tpmCapabilities 2 } 678 tpmClockSource OBJECT-TYPE 679 SYNTAX SspmClockSource 680 MAX-ACCESS read-only 681 STATUS current 682 DESCRIPTION 683 "A read only variable indicating the source of the clock. 684 This is provided to allow a user to determine how accurate 685 the timing mechanism is compared with other devices." 686 ::= { tpmCapabilities 3 } 688 tpmTransMetricDirLastChange OBJECT-TYPE 689 SYNTAX TimeStamp 690 MAX-ACCESS read-only 691 STATUS current 692 DESCRIPTION 693 "The value of sysUpTime at the time the 694 tpmTransMetricDirTable was last modified, through 695 modifications of the tpmTransMetricDirConfig object." 696 ::= { tpmCapabilities 4 } 698 tpmTransMetricDirTable OBJECT-TYPE 699 SYNTAX SEQUENCE OF TpmTransMetricDirEntry 700 MAX-ACCESS not-accessible 701 STATUS current 702 DESCRIPTION 703 "This table is used to describe and link sets of 704 performance metrics and protocols to an entry in 705 the application directory. This table, with the 706 tpmMetricDefTable, describes the capability of 707 the agent to collection sub-application level 708 data related to each entry in the 709 apmAppDirectoryTable. 711 This table lists the protocol transactions and their 712 corresponding performance metrics that this agent 713 has the capability to compute and collect, for the specified 714 application. There is one entry in this table for each such 715 application, protocol transaction and metric combination 716 supported by this agent. The entries in this 717 table represent the metrics that are collected for each 718 protocol transaction that comprise the application. 719 The agent should boot up with this table pre-configured 720 with those combinations of applications, protocol 721 transactions and metrics that it knows about and wishes to 722 monitor. Implementations must populate the table with all 723 possible application, protocol transaction and metric 724 combinations and have the default configuration 725 objects set to supportedOff(2). This table 726 does not support the creation of new 727 combinations by the management application. 729 The deletion of an entry in the apmAppDirectoryTable will cause 730 the removal of entries from this table. These entries must 731 be removed because the appLocalIndex value will no 732 longer be visible in the apmAppDirectoryTable. When an entry 733 is created in the apmAppDirectoryTable and the agent has the 734 ability to support metrics for these protocol transactions, 735 the appropriate entries must be made in the 736 tpmTransMetricDefTable." 737 ::= { tpmCapabilities 5 } 739 tpmTransMetricDirEntry OBJECT-TYPE 740 SYNTAX TpmTransMetricDirEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "A conceptual row in the tpmTransMetricDirTable. 746 An example of the indexing of this entry is 747 tpmTransMetricDirConfig.5.2 where 5 is the 748 value of a valid and visible appLocalIndex object in 749 in the appLocalDir table. The entries describe the 750 the transaction and metric pairs monitored for this 751 application. The tpmTransMetricProtocolIndex 752 identifies the protocol transaction and the 753 tpmMetricDefIndex describes the metric monitored." 754 INDEX { tpmTransMetricAppLocalIndex, -- Application Index 755 tpmTransMetricIndex -- (Protocol,Metric) Index 756 } 757 ::= { tpmTransMetricDirTable 1 } 759 TpmTransMetricDirEntry ::= SEQUENCE { 760 tpmTransMetricAppLocalIndex AppLocalIndex, 761 tpmTransMetricIndex TpmTransactionMetricIndex, 762 tpmTransMetricProtocolIndex Unsigned32, 763 tpmTransMetricMetricIndex Unsigned32, 764 tpmTransMetricDirConfig INTEGER 765 } 767 tpmTransMetricAppLocalIndex OBJECT-TYPE 768 SYNTAX AppLocalIndex 769 MAX-ACCESS not-accessible 770 STATUS current 771 DESCRIPTION 772 "An index used to uniquely identify the application 773 which the entries in the tpmTransMetricDir 774 table are associated." 775 ::= { tpmTransMetricDirEntry 1 } 777 tpmTransMetricIndex OBJECT-TYPE 778 SYNTAX TpmTransactionMetricIndex 779 MAX-ACCESS not-accessible 780 STATUS current 781 DESCRIPTION 782 "An index used to uniquely identify an entry in the 783 tpmTransMetricDir table. Each such entry defines 784 protocol transaction and metric instance 785 to be monitored for a specific application." 786 ::= { tpmTransMetricDirEntry 2 } 788 tpmTransMetricProtocolIndex OBJECT-TYPE 789 SYNTAX Unsigned32 (1..2147483647) 790 MAX-ACCESS read-only 791 STATUS current 792 DESCRIPTION 793 "The protocolDirLocalIndex of the particular transaction to 794 be analyzed when computing and generating the selected metric 795 for a specific application." 796 ::= { tpmTransMetricDirEntry 3 } 798 tpmTransMetricMetricIndex OBJECT-TYPE 799 SYNTAX Unsigned32 (1..2147483647) 800 MAX-ACCESS read-only 801 STATUS current 802 DESCRIPTION 803 "The tpmMetricDefinitionID of the particular metric to be 804 generated." 805 ::= { tpmTransMetricDirEntry 4 } 807 tpmTransMetricDirConfig OBJECT-TYPE 808 SYNTAX INTEGER { 809 notSupported(1), 810 supportedOff(2), 811 supportedOn(3) 812 } 813 MAX-ACCESS read-write 814 STATUS current 815 DESCRIPTION 816 "This object describes and configures the probe's support 817 for this performance metric in relationship to the 818 specified transaction and application. The agent 819 creates entries in this table for all metric 820 and transaction combinations that it can generate. 821 Because the probe will only populate this table with supported 822 entries, and the table cannot have entries added, the 823 notSupported(1) setting is only used to signify that other 824 configuration parameters are causing the agent to currently not 825 support the generation and collection of this metric for the 826 specified protocol and application. Also, the status of 827 this object will not change to notSupported(1) due to a 828 change to supportedOff(2) in the tpmMetricDir table. 830 If the value of this object is notSupported(1), the probe 831 will not perform computations for this performance metric and 832 transaction combination and shall not allow this object to be 833 changed to any other value. If the value of this object is 834 supportedOn(3), the probe supports computations for this 835 performance metric and protocol and is configured to perform 836 the computations for this performance metric and protocol 837 combination for the application for all interfaces. 838 If the value of this object is supportedOff(2), the 839 probe supports computations for this performance 840 metric for the specified protocol, but is configured 841 to not perform the computations for this performance 842 metric and protocol for the application for any 843 interfaces. Whenever this value changes from 844 supportedOn(3) to supportedOff(2), the probe shall 845 cause the deletion of all entries in the tpmReportGroup 846 tables, for all appropriate studies configured in the 847 tpmAggrReportCntrlTable. 849 The value of this object must persist across reboots." 850 ::= { tpmTransMetricDirEntry 5 } 852 -- 853 -- TPM Metric Definitions Table 854 -- 856 tpmMetricDefTable OBJECT-TYPE 857 SYNTAX SEQUENCE OF TpmMetricDefEntry 858 MAX-ACCESS not-accessible 859 STATUS current 860 DESCRIPTION 861 "The tpmMetricDefTable describes the metrics 862 available to the TPM-MIB. The tpmMetricDefTable 863 can define metrics by referencing existing IETF, 864 ITU and other standards organizations' documents, 865 including enterprise specific documents. 867 Examples of appropriate references include the 868 ITU-T Recommendation Y.1540 [Y.1540] on IP 869 packet transfer performance metrics or the 870 IETF documents from the IPPM WG, e.g., RFC2681 871 on the round trip delay metric [RFC2681] or 872 RFC3393 on the delay variation metric [RFC3393] 873 or others, including RFC2679 [RFC2679], RFC2680 874 [RFC2680], and RFC3432 [RFC3432]. While no 875 specific metric is mandatory, implementations 876 should, at a minimum, support a round trip delay 877 and a round trip loss metric. 879 This table contains one row per metric supported by this 880 agent, and should be populated during system 881 initialization." 882 ::= { tpmCapabilities 6 } 884 tpmMetricDefEntry OBJECT-TYPE 885 SYNTAX TpmMetricDefEntry 886 MAX-ACCESS not-accessible 887 STATUS current 888 DESCRIPTION 889 "Information about a particular metric." 890 INDEX { tpmMetricDefinitionID } 891 ::= { tpmMetricDefTable 1 } 893 TpmMetricDefEntry ::= SEQUENCE { 894 tpmMetricDefinitionID TpmMetricDefID, 895 tpmMetricDefType INTEGER, 896 tpmMetricDefDirType INTEGER, 897 tpmMetricDefName SnmpAdminString, 898 tpmMetricDefReference SnmpAdminString, 899 tpmMetricDefGlobalID OBJECT IDENTIFIER 900 } 902 tpmMetricDefinitionID OBJECT-TYPE 903 SYNTAX TpmMetricDefID 904 MAX-ACCESS not-accessible 905 STATUS current 906 DESCRIPTION 907 "The index for this entry. This object identifies the 908 the particular metric in this MIB module." 909 ::= { tpmMetricDefEntry 1 } 911 tpmMetricDefType OBJECT-TYPE 912 SYNTAX INTEGER { 913 other(1), 914 connectMetric(2), 915 delayMetric(3), 916 lossMetric(4) 917 } 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "The basic type of metric indicated by this entry. 923 The value 'other(1)' indicates that this metric cannot be 924 characterized by any of the remaining enumerations specified 925 for this object. 927 The value 'connectMetric(2)' indicates that this metric 928 measures connectivity characteristics. 930 The value 'delayMetric(3)' indicates that this metric 931 measures delay characteristics. 933 The value 'lossMetric(4)' indicates that this metric 934 measures loss characteristics." 935 ::= { tpmMetricDefEntry 2 } 937 tpmMetricDefDirType OBJECT-TYPE 938 SYNTAX INTEGER { 939 oneWay(1), 940 twoWay(2), 941 multiWay(3) 942 } 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "The directional characteristics of the this metric. 948 The value 'oneWay(1)' indicates that this metric is measured 949 with some sort of unidirectional test. 951 The value 'twoWay(2)' indicates that this metric is measured 952 with some sort of bidirectional test. 954 The value 'multiWay(3)' indicates that this metric is 955 measured with some combination of unidirectional and/or 956 bidirectional tests." 957 ::= { tpmMetricDefEntry 3 } 959 tpmMetricDefName OBJECT-TYPE 960 SYNTAX SnmpAdminString 961 MAX-ACCESS read-only 962 STATUS current 963 DESCRIPTION 964 "The textual name of this metric. For example, if 965 this tpmMetricDefEntry identified the IPPM metric for 966 round trip delay, then this object should contain 967 the value, e.g., 'Type-P-Round-Trip-Delay'." 968 ::= { tpmMetricDefEntry 4 } 970 tpmMetricDefReference OBJECT-TYPE 971 SYNTAX SnmpAdminString 972 MAX-ACCESS read-only 973 STATUS current 974 DESCRIPTION 975 "This object contains a reference to the document which 976 defines this metric. If this document is available online 977 via electronic download, then a dereferencable URL 978 should be specified in this object. The implementation 979 must support an HTTP URL type and may support additional 980 types of dereferencable URLs such as an FTP type. 982 For example, if this tpmMetricDefName identified the IPPM 983 metric 'Type-P-Round-Trip-Delay', then this object should 984 contain the value, e.g., 985 'http://www.ietf.org/rfc/rfc2681.txt'." 986 ::= { tpmMetricDefEntry 5 } 988 tpmMetricDefGlobalID OBJECT-TYPE 989 SYNTAX OBJECT IDENTIFIER 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "This object contains a reference to the Object ID 994 in a metrics registration MIB being developed 995 in the IPPM WG at the IETF, e.g., the 996 IPPM-REGISTRY-MIB [RFCXXX3], which defines the metric. 997 In the event that this metric has no corresponding 998 OID or until the IPPM-REGISTRY-MIB is defined, then 999 the value should be set to 0.0 for none." 1000 ::= { tpmMetricDefEntry 6 } 1002 -- 1003 -- The tpmAggregateReportsGroup 1004 -- 1006 tpmAggrReportCntrlTable OBJECT-TYPE 1007 SYNTAX SEQUENCE OF TpmAggrReportCntrlEntry 1008 MAX-ACCESS not-accessible 1009 STATUS current 1010 DESCRIPTION 1011 "The tpmAggrReportCntrlTable is the controlling entry 1012 to manage the population of studies in the Transport 1013 Aggregate Report for selected interfaces, metrics and 1014 transaction protocols and applications. 1016 Note that this is not like the typical RMON 1017 controlTable and dataTable in which each entry creates 1018 its own data table. Each entry in this table enables the 1019 creation of multiple data tables on a study basis. For each 1020 interval, the study is updated in place and the current 1021 data content of the table becomes invalid. 1023 The control table entries are persistent across 1024 system reboots." 1025 ::= { tpmReports 1 } 1027 tpmAggrReportCntrlEntry OBJECT-TYPE 1028 SYNTAX TpmAggrReportCntrlEntry 1029 MAX-ACCESS not-accessible 1030 STATUS current 1031 DESCRIPTION 1032 "A conceptual row in the tpmAggrReportCntrlTable. 1034 An example of the indexing of this entry is 1035 tpmAggrReportCntrlDataSource.1" 1036 INDEX { tpmAggrReportCntrlIndex } 1037 ::= { tpmAggrReportCntrlTable 1 } 1039 TpmAggrReportCntrlEntry ::= SEQUENCE { 1040 tpmAggrReportCntrlIndex Unsigned32, 1041 tpmAggrReportCntrlApmCntrlIndex Unsigned32, 1042 tpmAggrReportCntrlDataSource DataSourceOrZero, 1043 tpmAggrReportCntrlAggrType TransactionAggregationType, 1044 tpmAggrReportCntrlInterval Unsigned32, 1045 tpmAggrReportCntrlReqSize Unsigned32, 1046 tpmAggrReportCntrlGrantedSize Unsigned32, 1047 tpmAggrReportCntrlReqReports Unsigned32, 1048 tpmAggrReportCntrlGrantedReports Unsigned32, 1049 tpmAggrReportCntrlStartTime TimeStamp, 1050 tpmAggrReportCntrlReportNumber Unsigned32, 1051 tpmAggrReportCntrlInsertsDenied Counter32, 1052 tpmAggrReportCntrlDroppedFrames Counter32, 1053 tpmAggrReportCntrlOwner OwnerString, 1054 tpmAggrReportCntrlStorageType StorageType, 1055 tpmAggrReportCntrlStatus RowStatus 1056 } 1058 tpmAggrReportCntrlIndex OBJECT-TYPE 1059 SYNTAX Unsigned32 (1..65535) 1060 MAX-ACCESS not-accessible 1061 STATUS current 1062 DESCRIPTION 1063 "An index that uniquely identifies an entry in the 1064 tpmAggrReportCntrlTable. Each such entry defines a unique 1065 report whose results are placed in the tpmAggrReportTable on 1066 behalf of this tpmAggrReportCntrlEntry." 1067 ::= { tpmAggrReportCntrlEntry 1 } 1069 tpmAggrReportCntrlApmCntrlIndex OBJECT-TYPE 1070 SYNTAX Unsigned32 (0..65535) 1071 MAX-ACCESS read-create 1072 STATUS current 1073 DESCRIPTION 1074 "This index associates this TpmAggrReportCntrlEntry directly 1075 with an existing ApmReportControlEntry. This link is used 1076 to synchronize reports in the associated tpmAggrReportTable. 1078 A value of 0 (zero) enables an independent control table that 1079 will report entries to tpmAggrReportTable based only on the 1080 other objects in this table. 1082 A non-zero value indicates that this row is defined through 1083 the APM-MIB. In this case, all row objects are set to their 1084 corresponding values in the APM-MIB. In the event that a 1085 SET is issued to a row object, while the value of the 1086 tpmAggrReportCntrlApmCntrlIndex is non-zero, the agent 1087 MUST respond as if the object of the SET command 1088 had MAX-ACCESS of read-only. 1090 This object may not be modified if the associated 1091 tpmAggrReportCntrlStatus object is equal to active(1)." 1092 DEFVAL { 0 } 1093 ::= { tpmAggrReportCntrlEntry 2 } 1095 tpmAggrReportCntrlDataSource OBJECT-TYPE 1096 SYNTAX DataSourceOrZero 1097 MAX-ACCESS read-create 1098 STATUS current 1099 DESCRIPTION 1100 "The source of the data for TPM Reports generated on 1101 behalf of this tpmAggrReportCntrlEntry. 1103 If the measurement is being performed by a probe, this should 1104 be set to interface or port where data was received for 1105 analysis. If the measurement isn't being performed by a probe, 1106 this should be set to the primary interface over which the 1107 measurement is being performed. If the measurement isn't being 1108 performed by a probe and there is no primary interface or this 1109 information isn't known, this object should be set to 0.0. 1111 If the tpmAggrReportCntrlApmCntrlIndex is non-zero, 1112 then this object is set to the corresponding 1113 apmReportControlTable object in the APM-MIB [RFC3729]. 1115 This object may not be modified if the associated 1116 tpmAggrReportCntrlStatus object is equal to active(1)." 1117 ::= { tpmAggrReportCntrlEntry 3 } 1119 tpmAggrReportCntrlAggrType OBJECT-TYPE 1120 SYNTAX TransactionAggregationType 1121 -- INTEGER { 1122 -- flows(1), 1123 -- clients(2), 1124 -- servers(3), 1125 -- applications(4) 1126 -- } 1127 MAX-ACCESS read-create 1128 STATUS current 1129 DESCRIPTION 1130 "The type of aggregation being performed for this set of 1131 reports. 1133 If the tpmAggrReportCntrlApmCntrlIndex is non-zero, 1134 then this object should be set by the agent to the value 1135 of the apmReportControlAggregationType object. 1137 This object may not be modified if the associated 1138 tpmAggrReportCntrlStatus object is equal to active(1)." 1139 ::= { tpmAggrReportCntrlEntry 4 } 1141 tpmAggrReportCntrlInterval OBJECT-TYPE 1142 SYNTAX Unsigned32 1143 UNITS "Seconds" 1144 MAX-ACCESS read-create 1145 STATUS current 1146 DESCRIPTION 1147 "The interval in seconds over which data is accumulated before 1148 being aggregated into a report in the tpmAggrReportTable. All 1149 reports with the same tpmAggrReportCntrlIndex will be based on 1150 the same interval. 1152 If the tpmAggrReportCntrlApmCntrlIndex is non-zero, 1153 then this object should be set by the agent to the value 1154 of the apmReportControlControlInterval object. 1156 This object may not be modified if the associated 1157 tpmReportAggregateCntrlStatus object is equal to active(1)." 1158 DEFVAL { 3600 } 1159 ::= { tpmAggrReportCntrlEntry 5 } 1161 tpmAggrReportCntrlReqSize OBJECT-TYPE 1162 SYNTAX Unsigned32 1163 MAX-ACCESS read-create 1164 STATUS current 1165 DESCRIPTION 1166 "The maximum number of Client and Server combination 1167 entries requested for this report. 1169 If the tpmAggrReportCntrlApmCntrlIndex is non-zero, 1170 then this object should be set by the agent to the value 1171 of the apmReportControlRequestedSize object. 1173 When this object is created or modified, the probe 1174 should set tpmReportCntrlGrantedSize as closely to this 1175 object as is possible for the particular probe 1176 implementation and available resources. 1178 It is important to note that this value is the number of 1179 requested entries in the tpmAggrReportTable only. Since the 1180 probe can derive this table from the apmReportTable, the probe 1181 must make sure that sufficient resources exist to support the 1182 creation of the apmReportTable plus any additional resources 1183 required to convert or support this table. 1185 This object may not be modified if the associated 1186 tpmReportAggregateCntrlStatus object is equal to active(1)." 1187 ::= { tpmAggrReportCntrlEntry 6 } 1189 tpmAggrReportCntrlGrantedSize OBJECT-TYPE 1190 SYNTAX Unsigned32 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "The maximum number of performance entries in this report. 1196 When the associated tpmAggrReportCntrlReqSize object is 1197 created or modified, the probe should set this 1198 object as closely to the requested value as is 1199 possible for the particular implementation and 1200 available resources. The probe must not lower this 1201 value except as a result of a set to the associated 1202 tpmAggrReportCntrlReqSize object. 1204 It is an implementation-specific matter as to whether or not 1205 zero-valued entries are available." 1206 ::= { tpmAggrReportCntrlEntry 7 } 1208 tpmAggrReportCntrlReqReports OBJECT-TYPE 1209 SYNTAX Unsigned32 (1..65535) 1210 MAX-ACCESS read-create 1211 STATUS current 1212 DESCRIPTION 1213 "The number of saved reports requested to be allocated on 1214 behalf of this entry. 1216 If the tpmAggrReportCntrlApmCntrlIndex is non-zero, 1217 then this object should be set by the agent to the value 1218 of the apmReportControlcwRequestedReportsDataSource object. 1220 This object may not be modified if the associated 1221 tpmReportAggregateCntrlStatus object is equal to active(1)." 1222 ::= { tpmAggrReportCntrlEntry 8 } 1224 tpmAggrReportCntrlGrantedReports OBJECT-TYPE 1225 SYNTAX Unsigned32 (0..65535) 1226 MAX-ACCESS read-only 1227 STATUS current 1228 DESCRIPTION 1229 "The number of saved reports the agent has allocated based 1230 on the requested amount in tpmAggrReportCntrlReqReports. 1231 Since each report can have many entries, the total number of 1232 entries allocated will be this number multiplied by the 1233 value of tpmAggrReportCntrlGrantedSize, or 1 if that 1234 object doesn't exist. 1236 When the associated tpmAggrReportCntrlReqReports object is 1237 created or modified, the agent should set this object as 1238 closely to the requested value as is possible for the 1239 particular implementation and available resources. When 1240 considering resources available, the agent must consider its 1241 ability to allocate this many reports each with the number of 1242 entries represented by tpmAggrReportCntrlGrantedSize, or 1 if 1243 that object doesn't exist. 1245 Note that while the storage required for each report may 1246 fluctuate due to changing conditions, the agent must continue 1247 to have storage available to satisfy the full report size for 1248 all reports when necessary. Further, the agent must not lower 1249 this value except as a result of a set to the associated 1250 tpmAggrReportCntrlReqSize object." 1251 ::= { tpmAggrReportCntrlEntry 9 } 1253 tpmAggrReportCntrlStartTime OBJECT-TYPE 1254 SYNTAX TimeStamp 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "The value of sysUpTime when the system began processing the 1259 report in progress. Note that the report in progress is not 1260 available. 1262 This object may be used by the management station to figure 1263 out the start time for all previous reports saved for this 1264 tpmAggrReportCntrlEntry, as reports are started at fixed 1265 intervals. 1267 If the tpmAggrReportCntrlApmCntrlIndex is non-zero, 1268 then this object is set to the corresponding 1269 apmReportControlTable object in the APM-MIB defined in 1270 the IETF's RMONMIB WG." 1271 ::= { tpmAggrReportCntrlEntry 10 } 1273 tpmAggrReportCntrlReportNumber OBJECT-TYPE 1274 SYNTAX Unsigned32 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "The number of the report in progress. When an 1279 tpmAggrReportCntrlEntry is activated, the first report will be 1280 numbered zero. 1282 If the tpmAggrReportCntrlApmCntrlIndex is non-zero, 1283 then this object should be set by the agent to the value 1284 of the apmReportControlReportNumber object." 1285 ::= { tpmAggrReportCntrlEntry 11 } 1287 tpmAggrReportCntrlInsertsDenied OBJECT-TYPE 1288 SYNTAX Counter32 1289 MAX-ACCESS read-only 1290 STATUS current 1291 DESCRIPTION 1292 "The number of failed attempts to add an entry to reports for 1293 this TpmAggrReportCntrlEntry because the number of entries 1294 would have exceeded tpmAggrReportCntrlGrantedSize. 1296 This number is valuable in determining if enough entries have 1297 been allocated for reports in light of fluctuating network 1298 usage. Note that an entry that is denied will often be 1299 attempted again, this number will not predict the exact number 1300 of additional entries needed, but can be used to understand 1301 the relative magnitude of the problem. 1303 Also note that there is no ordering specified for the entries 1304 in the report, thus there are no rules for which entries will 1305 be omitted when not enough entries are available. As a 1306 consequence, the agent is not required to delete 'least 1307 valuable' entries first." 1308 ::= { tpmAggrReportCntrlEntry 12 } 1310 tpmAggrReportCntrlDroppedFrames OBJECT-TYPE 1311 SYNTAX Counter32 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "The total number of frames which were received by the agent 1316 and therefore not accounted for in the *StatsDropEvents, but 1317 for which the agent chose not to count for this entry for 1318 whatever reason. Most often, this event occurs when the agent 1319 is out of some resources and decides to shed load from this 1320 collection. 1322 This count does not include packets that were not counted 1323 because they had MAC-layer errors. 1325 Note that if the alMatrixTables are not implemented or are 1326 inactive because no protocols are enabled in the protocol 1327 directory, this value should be 0. 1329 Note that, unlike the dropEvents counter, this number is the 1330 exact number of frames dropped." 1331 ::= { tpmAggrReportCntrlEntry 13 } 1333 tpmAggrReportCntrlOwner OBJECT-TYPE 1334 SYNTAX OwnerString 1335 MAX-ACCESS read-create 1336 STATUS current 1337 DESCRIPTION 1338 "The entity that configured this entry and is 1339 therefore using the resources assigned to it. 1341 If the tpmAggrReportCntrlApmCntrlIndex is non-zero, 1342 then this object should be set by the agent to the value 1343 of the apmReportControlReportNumber object. 1345 This object may not be modified if the associated 1346 tpmReportAggregateCntrlStatus object is equal to active(1)." 1347 ::= { tpmAggrReportCntrlEntry 14 } 1349 tpmAggrReportCntrlStorageType OBJECT-TYPE 1350 SYNTAX StorageType 1351 MAX-ACCESS read-create 1352 STATUS current 1353 DESCRIPTION 1354 "The storage type of this tpmAggrReportCntrlEntry. If the 1355 value of this object is 'permanent', no objects in this row 1356 need to be writable." 1358 ::= { tpmAggrReportCntrlEntry 15 } 1360 tpmAggrReportCntrlStatus OBJECT-TYPE 1361 SYNTAX RowStatus 1362 MAX-ACCESS read-create 1363 STATUS current 1364 DESCRIPTION 1365 "The status of this performance control entry. 1367 An entry may not exist in the active state unless all 1368 objects in the entry have an appropriate value. 1370 If the tpmAggrReportCntrlApmCntrlIndex is non-zero, 1371 then this object should be set by the agent to the value 1372 of the apmReportControlReportNumber object. 1374 Once this object is set to active(1), no objects in the 1375 tpmAggrReportCntrlTable can be changed. 1377 If this object is not equal to active(1), all associated 1378 entries in the tpmAggrReportTable shall be deleted." 1379 ::= { tpmAggrReportCntrlEntry 16 } 1381 -- 1382 -- Transport Aggregate Report Table 1383 -- 1385 tpmAggrReportTable OBJECT-TYPE 1386 SYNTAX SEQUENCE OF TpmAggrReportEntry 1387 MAX-ACCESS not-accessible 1388 STATUS current 1389 DESCRIPTION 1390 "This table contains transport performance metric 1391 studies for each of the control table entries in 1392 tpmAggrReportCntrlTable. These studies are 1393 provided based on the selections and parameters 1394 found for the entry in the 1395 tpmAggregateReportCntrlTable. 1397 The performance statistics are specified in the 1398 tpmTransMetricDirTable associated with the 1399 application in question and indexed by 1400 appLocalIndex and tpmTransMetricIndex." 1401 ::= { tpmReports 2 } 1403 tpmAggrReportEntry OBJECT-TYPE 1404 SYNTAX TpmAggrReportEntry 1405 MAX-ACCESS not-accessible 1406 STATUS current 1407 DESCRIPTION 1408 "A conceptual row in the tpmAggrReportTable. 1410 The tpmAggrReportCntrlIndex value in the index identifies the 1411 tpmAggrReportCntrlEntry on whose behalf this entry was created. 1413 The tpmAggrReportIndex value in the index identifies which 1414 report (in the series of reports) this entry is a part of. 1415 The tpmAggrReportAppLocalIndex value in the index identifies 1416 the application protocol that is being reported. 1417 The tpmTransMetricIndex value in the index identifies 1418 the transaction protocol-metric pair for the traffic flows 1419 aggregated in this entry. 1420 The protocolDirLocalIndex value in the index identifies the 1421 network layer protocol of the tpmAggrReportServerAddress. When 1422 the associated tpmAggrReportCntrlAggrType value is equal 1423 to applications(4) or clients(2), this value will equal 0. 1424 The tpmAggrReportServerAddress value in the index identifies 1425 the network layer address of the server in traffic flows 1426 aggregated in this entry. 1427 The tpmAggrReportApmNameClientID value in the index identifies 1428 the client in traffic flows aggregated in this entry. If the 1429 associated tpmAggrReportCntrlAggrType is equal to 1430 applications(4) or servers(3), then this object will be set to 1431 0. 1433 An example of the indexing of this entry is 1434 tpmAggrReportStatN.3.15.34.262.18.4.128.2.6.7.3256521" 1435 INDEX { tpmAggrReportCntrlIndex, 1436 tpmAggrReportIndex, 1437 tpmAggrReportAppLocalIndex, -- Application Layer 1438 tpmAggrReportTransMetricIndex, -- Metric and Protocol 1439 protocolDirLocalIndex, -- Network Layer 1440 tpmAggrReportServerAddress, 1441 tpmAggrReportApmNameClientID 1442 } 1443 ::= { tpmAggrReportTable 1 } 1445 TpmAggrReportEntry ::= SEQUENCE { 1446 tpmAggrReportIndex Unsigned32, 1447 tpmAggrReportAppLocalIndex AppLocalIndex, 1448 tpmAggrReportTransMetricIndex TpmTransactionMetricIndex, 1449 tpmAggrReportServerAddress OCTET STRING, 1450 tpmAggrReportApmNameClientID RmonClientID, 1451 tpmAggrReportStatN ZeroBasedCounter32, 1452 tpmAggrReportOverflowStatN ZeroBasedCounter32, 1453 tpmAggrReportHCStatN ZeroBasedCounter64, 1454 tpmAggrReportStatSumX ZeroBasedCounter32, 1455 tpmAggrReportOverflowStatSumX ZeroBasedCounter32, 1456 tpmAggrReportHCStatSumX ZeroBasedCounter64, 1457 tpmAggrReportStatMaximum ZeroBasedCounter32, 1458 tpmAggrReportStatMinimum ZeroBasedCounter32, 1459 tpmAggrReportStatSumSq ZeroBasedCounter32, 1460 tpmAggrReportOverflowStatSumSq ZeroBasedCounter32, 1461 tpmAggrReportHCStatSumSq ZeroBasedCounter64, 1462 tpmAggrReportStatSumIX ZeroBasedCounter32, 1463 tpmAggrReportOverflowStatSumIX ZeroBasedCounter32, 1464 tpmAggrReportHCStatSumIX ZeroBasedCounter64, 1465 tpmAggrReportStatSumIXSq ZeroBasedCounter32, 1466 tpmAggrReportOverflowStatSumIXSq ZeroBasedCounter32, 1467 tpmAggrReportHCStatSumIXSq ZeroBasedCounter64 1468 } 1470 tpmAggrReportIndex OBJECT-TYPE 1471 SYNTAX Unsigned32 (1..2147483647) 1472 MAX-ACCESS not-accessible 1473 STATUS current 1474 DESCRIPTION 1475 "The value of tpmAggrReportCntrlNumber for the report to 1476 which this entry belongs." 1477 ::= { tpmAggrReportEntry 1 } 1479 tpmAggrReportAppLocalIndex OBJECT-TYPE 1480 SYNTAX AppLocalIndex 1481 MAX-ACCESS not-accessible 1482 STATUS current 1483 DESCRIPTION 1484 "The common application of the transactions aggregated 1485 in this entry." 1486 ::= { tpmAggrReportEntry 2 } 1488 tpmAggrReportTransMetricIndex OBJECT-TYPE 1489 SYNTAX TpmTransactionMetricIndex 1490 MAX-ACCESS not-accessible 1491 STATUS current 1492 DESCRIPTION 1493 "A unique index that identifies the transaction and 1494 metric associated with the statistics reported here." 1495 ::= { tpmAggrReportEntry 3 } 1497 tpmAggrReportServerAddress OBJECT-TYPE 1498 SYNTAX OCTET STRING (SIZE (0..108)) 1499 MAX-ACCESS not-accessible 1500 STATUS current 1501 DESCRIPTION 1502 "The network layer address of the server host in this 1503 conversation. 1505 This is represented as an octet string with 1506 specific semantics and length as identified 1507 by the protocolDirLocalIndex component of the index. 1509 Since this object is an index variable, it is encoded in 1510 the index according to the index encoding rules. For 1511 example, if the protocolDirLocalIndex indicates an 1512 encapsulation of IPv4, this object is encoded as a length 1513 octet of 4, followed by the 4 octets of the IPv4 address, 1514 in network byte order. 1516 If the associated tpmAggrReportCntrlAggrType is equal to 1517 application(4) or client(2), then this object will be a null 1518 string and will be encoded simply as a length octet of 0." 1519 ::= { tpmAggrReportEntry 4 } 1521 tpmAggrReportApmNameClientID OBJECT-TYPE 1522 SYNTAX RmonClientID 1523 MAX-ACCESS not-accessible 1524 STATUS current 1525 DESCRIPTION 1526 "A unique ID assigned to the machine represented by this 1527 mapping. This ID is assigned by the agent using an 1528 implementation-specific algorithm." 1529 ::= { tpmAggrReportEntry 5 } 1531 tpmAggrReportStatN OBJECT-TYPE 1532 SYNTAX ZeroBasedCounter32 1533 MAX-ACCESS read-only 1534 STATUS current 1535 DESCRIPTION 1536 "The count of the total number of data points for the 1537 specified metric. This number always represents the 1538 total size of the statistical datum analyzed. Each 1539 metric specifies the exact meaning of this object. 1541 This value represents the results for one metric and is 1542 related directly to the specific parameters of the metric 1543 and the Server and Client addresses involved." 1544 ::= { tpmAggrReportEntry 6 } 1546 tpmAggrReportOverflowStatN OBJECT-TYPE 1547 SYNTAX ZeroBasedCounter32 1548 MAX-ACCESS read-only 1549 STATUS current 1550 DESCRIPTION 1551 "The number of times the associated 1552 tpmAggrReportStatN counter has overflowed. Note 1553 that this object will only be instantiated if the 1554 associated tpmAggrReportHCStatN object is also 1555 instantiated for a particular dataSource." 1556 ::= { tpmAggrReportEntry 7 } 1558 tpmAggrReportHCStatN OBJECT-TYPE 1559 SYNTAX ZeroBasedCounter64 1560 MAX-ACCESS read-only 1561 STATUS current 1562 DESCRIPTION 1563 "The high-capacity version of tpmAggrReportStatN. 1564 Note that this object will only be instantiated if the 1565 agent supports High Capacity monitoring for a particular 1566 dataSource." 1567 ::= { tpmAggrReportEntry 8 } 1569 tpmAggrReportStatSumX OBJECT-TYPE 1570 SYNTAX ZeroBasedCounter32 1571 MAX-ACCESS read-only 1572 STATUS current 1573 DESCRIPTION 1574 "The sum of all the data point values for the specified 1575 metric. This number always represents the total values 1576 of the statistical datum analyzed. Each metric 1577 specifies the exact meaning of this object. 1579 This value represents the results of one metric and is 1580 related directly to the specific parameters of the metric 1581 and the Server and Client addresses involved." 1582 ::= { tpmAggrReportEntry 9 } 1584 tpmAggrReportOverflowStatSumX OBJECT-TYPE 1585 SYNTAX ZeroBasedCounter32 1586 MAX-ACCESS read-only 1587 STATUS current 1588 DESCRIPTION 1589 "The number of times the associated 1590 tpmAggrReportStatSumX counter has overflowed. 1591 Note that this object will only be instantiated if the 1592 associated tpmAggrReportHCStatSumX object is also 1593 instantiated for a particular dataSource." 1594 ::= { tpmAggrReportEntry 10 } 1596 tpmAggrReportHCStatSumX OBJECT-TYPE 1597 SYNTAX ZeroBasedCounter64 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "The high-capacity version of tpmAggrReportStatSumX. 1602 Note that this object will only be instantiated if the 1603 agent supports High Capacity monitoring for a particular 1604 dataSource." 1605 ::= { tpmAggrReportEntry 11 } 1607 tpmAggrReportStatMaximum OBJECT-TYPE 1608 SYNTAX ZeroBasedCounter32 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "The single maximum data point value observed during the 1613 study period for the specified metric. This number always 1614 represents the maximum value of any single statistical 1615 datum analyzed. Each metric specifies the exact meaning 1616 of this object. 1618 This value represents the results of one metric and is 1619 related directly to the specific parameters of the metric 1620 and the Server and Client addresses involved." 1621 ::= { tpmAggrReportEntry 12 } 1623 tpmAggrReportStatMinimum OBJECT-TYPE 1624 SYNTAX ZeroBasedCounter32 1625 MAX-ACCESS read-only 1626 STATUS current 1627 DESCRIPTION 1628 "The single minimum data point value observed during the 1629 study period for the specified metric. This number always 1630 represents the minimum value of any single statistical 1631 datum analyzed. Each metric specifies the exact meaning 1632 of this object. 1634 This value represents the results of one metric and is 1635 related directly to the specific parameters of the metric 1636 and the Server and Client addresses involved." 1637 ::= { tpmAggrReportEntry 13 } 1639 tpmAggrReportStatSumSq OBJECT-TYPE 1640 SYNTAX ZeroBasedCounter32 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "The sum of all the squared data point values for the 1645 specified metric. This number always represents the 1646 total of the squared values of the statistical datum 1647 analyzed. Each metric specifies the exact meaning of 1648 this object. 1650 This value represents the results of one metric and is 1651 related directly to the specific parameters of the metric 1652 and the Server and Client addresses involved." 1653 ::= { tpmAggrReportEntry 14 } 1655 tpmAggrReportOverflowStatSumSq OBJECT-TYPE 1656 SYNTAX ZeroBasedCounter32 1657 MAX-ACCESS read-only 1658 STATUS current 1659 DESCRIPTION 1660 "The number of times the associated 1661 tpmAggrReportStatSumSq counter has overflowed. 1662 Note that this object will only be instantiated if 1663 the associated tpmAggrReportHCStatSumSq object 1664 is also instantiated for a particular dataSource." 1665 ::= { tpmAggrReportEntry 15 } 1667 tpmAggrReportHCStatSumSq OBJECT-TYPE 1668 SYNTAX ZeroBasedCounter64 1669 MAX-ACCESS read-only 1670 STATUS current 1671 DESCRIPTION 1672 "The high-capacity version of tpmAggrReportStatSumSq. 1673 Note that this object will only be instantiated if the 1674 agent supports High Capacity monitoring for a particular 1675 dataSource." 1676 ::= { tpmAggrReportEntry 16 } 1678 tpmAggrReportStatSumIX OBJECT-TYPE 1679 SYNTAX ZeroBasedCounter32 1680 MAX-ACCESS read-only 1681 STATUS current 1682 DESCRIPTION 1683 "For each interval, each data point is associated with a 1684 value I, I = 1..N where N is the number of data points, 1685 tpmAggrReportStatN. IX is the multiplication of the 1686 data point value with the current I. This value 1687 along with the other statistics values allow the 1688 calculation of the slope of the least-squares line 1689 through the data points." 1690 ::= { tpmAggrReportEntry 17 } 1692 tpmAggrReportOverflowStatSumIX OBJECT-TYPE 1693 SYNTAX ZeroBasedCounter32 1694 MAX-ACCESS read-only 1695 STATUS current 1696 DESCRIPTION 1697 "The number of times the associated 1698 tpmAggrReportStatSumIX counter has overflowed. 1699 Note that this object will only be instantiated if the 1700 associated tpmAggrReportHCStatSumIX object is also 1701 instantiated for a particular dataSource." 1702 ::= { tpmAggrReportEntry 18 } 1704 tpmAggrReportHCStatSumIX OBJECT-TYPE 1705 SYNTAX ZeroBasedCounter64 1706 MAX-ACCESS read-only 1707 STATUS current 1708 DESCRIPTION 1709 "The high-capacity version of tpmAggrReportStatSumIX. 1710 Note that this object will only be instantiated if the 1711 agent supports High Capacity monitoring for a particular 1712 dataSource." 1713 ::= { tpmAggrReportEntry 19 } 1715 tpmAggrReportStatSumIXSq OBJECT-TYPE 1716 SYNTAX ZeroBasedCounter32 1717 MAX-ACCESS read-only 1718 STATUS current 1719 DESCRIPTION 1720 "For each interval, each data point is associated with a 1721 value I, I = 1..N where N is the number of data points, 1722 tpmAggrReportStatN. IX is the multiplication 1723 of the data point value with the current I. 1724 This value along with the other statistics 1725 values allow the calculation of the slope of 1726 the least-squares line through the data points." 1727 ::= { tpmAggrReportEntry 20 } 1729 tpmAggrReportOverflowStatSumIXSq OBJECT-TYPE 1730 SYNTAX ZeroBasedCounter32 1731 MAX-ACCESS read-only 1732 STATUS current 1733 DESCRIPTION 1734 "The number of times the associated 1735 tpmAggrReportStatSumIXSq counter has overflowed. 1736 Note that this object will only be instantiated if the 1737 associated tpmAggrReportHCStatSumIXSq object is also 1738 instantiated for a particular dataSource." 1739 ::= { tpmAggrReportEntry 21 } 1741 tpmAggrReportHCStatSumIXSq OBJECT-TYPE 1742 SYNTAX ZeroBasedCounter64 1743 MAX-ACCESS read-only 1744 STATUS current 1745 DESCRIPTION 1746 "The high-capacity version of 1747 tpmAggrReportStatSumIXSq. 1748 Note that this object will only be instantiated if the 1749 agent supports High Capacity monitoring for a particular 1750 dataSource." 1751 ::= { tpmAggrReportEntry 22 } 1753 -- 1754 -- The tpmCurrentReportsGroup 1755 -- 1757 tpmCurReportTable OBJECT-TYPE 1758 SYNTAX SEQUENCE OF TpmCurReportEntry 1759 MAX-ACCESS not-accessible 1760 STATUS current 1761 DESCRIPTION 1762 "This table will contain entries associated with an 1763 apmReportControlEntry which are a current 'snapshot' 1764 of the metrics being collected in association with 1765 a set of TPM related application transactions. 1766 This table contains all sub-flow metrics for transactions 1767 that have been started but have not yet finished, i.e., 1768 current, and a history of those that have finished, i.e., 1769 completed. It may not always be obvious from the context 1770 whether a transaction is currently in-progress or has 1771 completed. Therefore, the completion status of a 1772 transaction is indicated by the value of 1773 the tpmCurReportCompletion object." 1774 ::= { tpmReports 3 } 1776 tpmCurReportEntry OBJECT-TYPE 1777 SYNTAX TpmCurReportEntry 1778 MAX-ACCESS not-accessible 1779 STATUS current 1780 DESCRIPTION 1781 "A conceptual row in the tpmCurReportTable. 1783 The tpmAggrReportControlIndex value in the index identifies 1784 the tpmAggrReportCntrlEntry on whose behalf this entry was 1785 created. The tpmCurReportAppLocalIndex value in the 1786 index identifies the application protocol that is begin 1787 reported. The protocolDirLocalIndex value in the 1788 index identifies the network layer protocol 1789 of the tpmAggrReportServerAddress. When the associated 1790 tpmAggrReportCntrlAggrType value is 1791 equal to applications(4), this value will equal 0. 1792 The tpmCurReportServerAddress value in the 1793 index identifies the network layer address of the 1794 server in traffic flows aggregated in this entry. 1795 The tpmCurReportCurrentApmNameClientID value in the 1796 index identifies the network layer address of the 1797 client in traffic flows aggregated in this entry. 1798 The tpmCurReportCurrentMetricIndex value in the 1799 index identifies the transported application protocol 1800 of the traffic flows aggregated in this entry. 1802 Note that the order of protocolDirLocalIndex variables is 1803 the opposite of that in the RMON2 MIB (application.network 1804 instead of network.application) so that the report entries are 1805 sorted by application first, server second and client third. 1806 The tpmCurReportCntrIndex value in the index identifies 1807 the tpmAggrReportCntrlEntry on whose behalf this entry was 1808 created. The tpmCurReportMetricIndex value in the index 1809 identifies the metric and protocol of the 1810 tpmCurReportServerAddress, via the tpmTransMetricDir 1811 table. 1813 An example of the indexing of this table is 1814 tpmCurReportStatisticN.3.34.262.18.4.128.2.6.6.3256521.29667" 1815 INDEX { tpmAggrReportCntrlIndex, 1816 tpmCurReportAppLocalIndex, -- Application Layer 1817 tpmCurReportTransMetricIndex, -- Metric and Protocol 1818 protocolDirLocalIndex, -- Network Layer 1819 tpmCurReportServerAddress, 1820 tpmCurReportApmNameClientID, 1821 tpmCurReportApmTransactionID 1822 } 1823 ::= { tpmCurReportTable 1 } 1825 TpmCurReportEntry ::= SEQUENCE { 1826 tpmCurReportAppLocalIndex AppLocalIndex, 1827 tpmCurReportTransMetricIndex TpmTransactionMetricIndex, 1828 tpmCurReportServerAddress OCTET STRING, 1829 tpmCurReportApmNameClientID RmonClientID, 1830 tpmCurReportApmTransactionID Unsigned32, 1831 tpmCurReportMetricValue ZeroBasedCounter32, 1832 tpmCurReportCompletion INTEGER 1833 } 1835 tpmCurReportAppLocalIndex OBJECT-TYPE 1836 SYNTAX AppLocalIndex 1837 MAX-ACCESS not-accessible 1838 STATUS current 1839 DESCRIPTION 1840 "The common application of the transactions reported 1841 in this entry." 1842 ::= { tpmCurReportEntry 1 } 1844 tpmCurReportTransMetricIndex OBJECT-TYPE 1845 SYNTAX TpmTransactionMetricIndex 1846 MAX-ACCESS not-accessible 1847 STATUS current 1848 DESCRIPTION 1849 "A unique index that identifies the transaction and 1850 metric associated with the statistics reported here." 1851 ::= { tpmCurReportEntry 2 } 1853 tpmCurReportServerAddress OBJECT-TYPE 1854 SYNTAX OCTET STRING (SIZE (0..108)) 1855 MAX-ACCESS not-accessible 1856 STATUS current 1857 DESCRIPTION 1858 "The network server address for this tpmCurReportEntry. 1860 This is represented as an octet string with 1861 specific semantics and length as identified 1862 by the protocolDirLocalIndex component of the index. 1864 For example, if the protocolDirLocalIndex indicates an 1865 encapsulation of IPv4, this object is encoded as a length 1866 octet of 4, followed by the 4 octets of the IPv4 address, 1867 in network byte order." 1868 ::= { tpmCurReportEntry 3 } 1870 tpmCurReportApmNameClientID OBJECT-TYPE 1871 SYNTAX RmonClientID 1872 MAX-ACCESS not-accessible 1873 STATUS current 1874 DESCRIPTION 1875 "A unique ID assigned to the machine represented by this 1876 mapping. This ID is assigned by the agent using an 1877 implementation-specific algorithm." 1878 ::= { tpmCurReportEntry 4 } 1880 tpmCurReportApmTransactionID OBJECT-TYPE 1881 SYNTAX Unsigned32 (0..4294967295) 1882 MAX-ACCESS not-accessible 1883 STATUS current 1884 DESCRIPTION 1885 "A unique value for this transaction amongst other 1886 transactions sharing the same application, 1887 transaction-layer protocol and metric and 1888 server and client addresses. Implementations may choose to use 1889 the value of the client's source port, when possible. 1891 If the tpmAggrReportCntrlApmCntrlIndex is non-zero, 1892 then this object is set to the corresponding 1893 apmTransactionID object in the APM-MIB developed 1894 in the IETF's RMONMIB WG." 1895 ::= { tpmCurReportEntry 5 } 1897 tpmCurReportMetricValue OBJECT-TYPE 1898 SYNTAX ZeroBasedCounter32 1899 MAX-ACCESS read-only 1900 STATUS current 1901 DESCRIPTION 1902 "The current value of the metric being evaluated. 1903 For some transaction types this value may be 0, e.g., 1904 the current round trip time for a DNS query. For 1905 other transaction types this will represent the 1906 current value of a continuously measured metric, e.g., 1907 the current throughput of an FTP transaction." 1908 ::= { tpmCurReportEntry 6 } 1910 tpmCurReportCompletion OBJECT-TYPE 1911 SYNTAX INTEGER { 1912 current(1), 1913 completed(2) 1914 } 1915 MAX-ACCESS read-only 1916 STATUS current 1917 DESCRIPTION 1918 "The status of this transaction. It is not always obvious 1919 from context whether a transaction is on-going or 1920 completed. E.g., an ftp-GET transaction may last several 1921 minutes or hours and a value found in the 1922 tpmCurReportMetricValue object lists to observed throughput 1923 for the transaction up to this point in time. The value 1924 of the tpmCurReportCompletion indicates whether the 1925 transaction has completed." 1926 ::= { tpmCurReportEntry 7 } 1928 tpmCurReportSize OBJECT-TYPE 1929 SYNTAX Unsigned32 1930 MAX-ACCESS read-write 1931 STATUS current 1932 DESCRIPTION 1933 "The maximum number of completed transactions desired to be 1934 retained in the tpmCurReportTable. If the agent doesn't have 1935 enough resources to retain this many, it will retain as many as 1936 possible. Regardless of this value, the agent must attempt to 1937 keep records for all current transactions it is monitoring. 1939 The agent should consider this value to give a hint as to 1940 how many transactions to save. This is not a hard limit, 1941 just a hint to a maximum value of interest. If this value is 1942 reduced by the management station, the agent can take note, 1943 it may free some records, or it may do nothing. 1945 The value of this object must persist across reboots." 1946 ::= { tpmReports 4 } 1948 -- 1949 -- The tpmExceptionReportsGroup 1950 -- 1952 tpmExcpReportTable OBJECT-TYPE 1953 SYNTAX SEQUENCE OF TpmExcpReportEntry 1954 MAX-ACCESS not-accessible 1955 STATUS current 1956 DESCRIPTION 1957 "This table contains all sub-flow metrics for transactions 1958 that have been tagged by the apmExceptionTable filter 1959 as having had poor performance." 1960 ::= { tpmReports 5 } 1962 tpmExcpReportEntry OBJECT-TYPE 1963 SYNTAX TpmExcpReportEntry 1964 MAX-ACCESS not-accessible 1965 STATUS current 1966 DESCRIPTION 1967 "A conceptual row in the tpmExcpReportTable. This table 1968 contains aggregated information associated with 1969 exceptions counted in the apmExceptionTable. The 1970 information is aggregated in a manner identical to the 1971 aggregation in the tpmAggrReportTable, with the exception 1972 that data only from transactions associated with a 1973 flagged application is included. 1975 The indexing into this table follows the indexing in the 1976 APM-MIB but adds the tpmTransMetricIndex to identify the 1977 sub-application transaction and metric pair." 1978 INDEX { apmAppDirAppLocalIndex, -- Application 1979 apmAppDirResponsivenessType, -- Responsiveness Type 1980 apmExceptionIndex, -- Linkage to ApmExceptions 1981 tpmExcpReportTransMetricIndex -- Metric and Protocol 1982 } 1983 ::= { tpmExcpReportTable 1 } 1985 TpmExcpReportEntry ::= SEQUENCE { 1986 tpmExcpReportTransMetricIndex TpmTransactionMetricIndex, 1987 tpmExcpReportStatN ZeroBasedCounter32, 1988 tpmExcpReportOverflowStatN ZeroBasedCounter32, 1989 tpmExcpReportHCStatN ZeroBasedCounter64, 1990 tpmExcpReportStatSumX ZeroBasedCounter32, 1991 tpmExcpReportOverflowStatSumX ZeroBasedCounter32, 1992 tpmExcpReportHCStatSumX ZeroBasedCounter64, 1993 tpmExcpReportStatMaximum ZeroBasedCounter32, 1994 tpmExcpReportStatMinimum ZeroBasedCounter32, 1995 tpmExcpReportStatSumSq ZeroBasedCounter32, 1996 tpmExcpReportOverflowStatSumSq ZeroBasedCounter32, 1997 tpmExcpReportHCStatSumSq ZeroBasedCounter64, 1998 tpmExcpReportStatSumIX ZeroBasedCounter32, 1999 tpmExcpReportOverflowStatSumIX ZeroBasedCounter32, 2000 tpmExcpReportHCStatSumIX ZeroBasedCounter64, 2001 tpmExcpReportStatSumIXSq ZeroBasedCounter32, 2002 tpmExcpReportOverflowStatSumIXSq ZeroBasedCounter32, 2003 tpmExcpReportHCStatSumIXSq ZeroBasedCounter64 2004 } 2006 tpmExcpReportTransMetricIndex OBJECT-TYPE 2007 SYNTAX TpmTransactionMetricIndex 2008 MAX-ACCESS not-accessible 2009 STATUS current 2010 DESCRIPTION 2011 "A unique index that identifies the transaction and 2012 metric associated with the data reported here." 2013 ::= { tpmExcpReportEntry 1 } 2015 tpmExcpReportStatN OBJECT-TYPE 2016 SYNTAX ZeroBasedCounter32 2017 MAX-ACCESS read-only 2018 STATUS current 2019 DESCRIPTION 2020 "The count of the total number of data points for the 2021 specified metric. This number always represents the 2022 total size of the statistical datum analyzed. Each 2023 metric specifies the exact meaning of this object. 2025 This value represents the results of one metric and is 2026 related directly to the specific parameters of the metric 2027 and the Server and Client addresses involved." 2028 ::= { tpmExcpReportEntry 2 } 2030 tpmExcpReportOverflowStatN OBJECT-TYPE 2031 SYNTAX ZeroBasedCounter32 2032 MAX-ACCESS read-only 2033 STATUS current 2034 DESCRIPTION 2035 "The number of times the associated tpmExcpReportStatN 2036 counter has overflowed. Note that this object will only 2037 be instantiated if the associated tpmExcpReportHCStatN 2038 object is also instantiated for a particular dataSource." 2039 ::= { tpmExcpReportEntry 3 } 2041 tpmExcpReportHCStatN OBJECT-TYPE 2042 SYNTAX ZeroBasedCounter64 2043 MAX-ACCESS read-only 2044 STATUS current 2045 DESCRIPTION 2046 "The high-capacity version of tpmExcpReportStatN. 2047 Note that this object will only be instantiated if the 2048 agent supports High Capacity monitoring for a particular 2049 dataSource." 2050 ::= { tpmExcpReportEntry 4 } 2052 tpmExcpReportStatSumX OBJECT-TYPE 2053 SYNTAX ZeroBasedCounter32 2054 MAX-ACCESS read-only 2055 STATUS current 2056 DESCRIPTION 2057 "The sum of all the data point values for the specified 2058 metric. This number always represents the total values 2059 of the statistical datum analyzed. Each metric 2060 specifies the exact meaning of this object. 2062 This value represents the results of one metric and is 2063 related directly to the specific parameters of the metric 2064 and the Server and Client addresses involved." 2065 ::= { tpmExcpReportEntry 5 } 2067 tpmExcpReportOverflowStatSumX OBJECT-TYPE 2068 SYNTAX ZeroBasedCounter32 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "The number of times the associated 2073 tpmExcpReportStatSumX counter has overflowed. 2074 Note that this object will only be instantiated if 2075 the associated tpmExcpReportHCStatSumX object is also 2076 instantiated for a particular dataSource." 2077 ::= { tpmExcpReportEntry 6 } 2079 tpmExcpReportHCStatSumX OBJECT-TYPE 2080 SYNTAX ZeroBasedCounter64 2081 MAX-ACCESS read-only 2082 STATUS current 2083 DESCRIPTION 2084 "The high-capacity version of tpmExcpReportStatSumX. 2085 Note that this object will only be instantiated if the 2086 agent supports High Capacity monitoring for a particular 2087 dataSource." 2088 ::= { tpmExcpReportEntry 7 } 2090 tpmExcpReportStatMaximum OBJECT-TYPE 2091 SYNTAX ZeroBasedCounter32 2092 MAX-ACCESS read-only 2093 STATUS current 2094 DESCRIPTION 2095 "The single maximum data point value observed during the 2096 study period for the specified metric. This number always 2097 represents the maximum value of any single statistical 2098 datum analyzed. Each metric specifies the exact meaning 2099 of this object. 2101 This value represents the results of one metric and is 2102 related directly to the specific parameters of the metric 2103 and the Server and Client addresses involved." 2104 ::= { tpmExcpReportEntry 8 } 2106 tpmExcpReportStatMinimum OBJECT-TYPE 2107 SYNTAX ZeroBasedCounter32 2108 MAX-ACCESS read-only 2109 STATUS current 2110 DESCRIPTION 2111 "The single minimum data point value observed during the 2112 study period for the specified metric. This number always 2113 represents the minimum value of any single statistical 2114 datum analyzed. Each metric specifies the exact meaning 2115 of this object. 2117 This value represents the results of one metric and is 2118 related directly to the specific parameters of the metric 2119 and the Server and Client addresses involved." 2120 ::= { tpmExcpReportEntry 9 } 2122 tpmExcpReportStatSumSq OBJECT-TYPE 2123 SYNTAX ZeroBasedCounter32 2124 MAX-ACCESS read-only 2125 STATUS current 2126 DESCRIPTION 2127 "The sum of all the squared data point values for the 2128 specified metric. This number always represents the 2129 total of the squared values of the statistical datum 2130 analyzed. Each metric specifies the exact meaning of 2131 this object. 2133 This value represents the results of one metric and is 2134 related directly to the specific parameters of the metric 2135 and the Server and Client addresses involved." 2136 ::= { tpmExcpReportEntry 10 } 2138 tpmExcpReportOverflowStatSumSq OBJECT-TYPE 2139 SYNTAX ZeroBasedCounter32 2140 MAX-ACCESS read-only 2141 STATUS current 2142 DESCRIPTION 2143 "The number of times the associated 2144 tpmExcpReportStatSumSq counter has overflowed. 2145 Note that this object will only be instantiated if the 2146 associated tpmExcpReportHCStatSumSq object is also 2147 instantiated for a particular dataSource." 2148 ::= { tpmExcpReportEntry 11 } 2150 tpmExcpReportHCStatSumSq OBJECT-TYPE 2151 SYNTAX ZeroBasedCounter64 2152 MAX-ACCESS read-only 2153 STATUS current 2154 DESCRIPTION 2155 "The high-capacity version of 2156 tpmExcpReportStatSumSq. 2157 Note that this object will only be instantiated if the 2158 agent supports High Capacity monitoring for a particular 2159 dataSource." 2160 ::= { tpmExcpReportEntry 12 } 2162 tpmExcpReportStatSumIX OBJECT-TYPE 2163 SYNTAX ZeroBasedCounter32 2164 MAX-ACCESS read-only 2165 STATUS current 2166 DESCRIPTION 2167 "For each interval, each data point is associated with a 2168 value I, I = 1..N where N is the number of data points, 2169 tpmExcpReportStatSumIX is the multiplication of the 2170 data point value with the current I. This value along with 2171 the other statistics values allow the calculation of the slope 2172 of the least-squares line through the data points." 2173 ::= { tpmExcpReportEntry 13 } 2175 tpmExcpReportOverflowStatSumIX OBJECT-TYPE 2176 SYNTAX ZeroBasedCounter32 2177 MAX-ACCESS read-only 2178 STATUS current 2179 DESCRIPTION 2180 "The number of times the associated 2181 tpmExcpReportStatSumIX counter has overflowed. 2182 Note that this object will only be instantiated if the 2183 associated tpmExcpReportHCStatSumIX object is also 2184 instantiated for a particular dataSource." 2185 ::= { tpmExcpReportEntry 14 } 2187 tpmExcpReportHCStatSumIX OBJECT-TYPE 2188 SYNTAX ZeroBasedCounter64 2189 MAX-ACCESS read-only 2190 STATUS current 2191 DESCRIPTION 2192 "The high-capacity version of tpmExcpReportStatSumIX. 2193 Note that this object will only be instantiated if the 2194 agent supports High Capacity monitoring for a particular 2195 dataSource." 2196 ::= { tpmExcpReportEntry 15 } 2198 tpmExcpReportStatSumIXSq OBJECT-TYPE 2199 SYNTAX ZeroBasedCounter32 2200 MAX-ACCESS read-only 2201 STATUS current 2202 DESCRIPTION 2203 "For each interval, each data point is associated with a 2204 value I, I = 1..N where N is the number of data points, 2205 tpmExcpReportStatN. IX is the multiplication of the data 2206 point value with the current I. This value along with the 2207 other statistics values allow the calculation of the slope of 2208 the least-squares line through the data points." 2209 ::= { tpmExcpReportEntry 16 } 2211 tpmExcpReportOverflowStatSumIXSq OBJECT-TYPE 2212 SYNTAX ZeroBasedCounter32 2213 MAX-ACCESS read-only 2214 STATUS current 2215 DESCRIPTION 2216 "The number of times the associated 2217 tpmExcpReportStatSumIXSq counter has overflowed. 2218 Note that this object will only be instantiated if the 2219 associated tpmExcpReportHCStatSumIXSq object is also 2220 instantiated for a particular dataSource." 2221 ::= { tpmExcpReportEntry 17 } 2223 tpmExcpReportHCStatSumIXSq OBJECT-TYPE 2224 SYNTAX ZeroBasedCounter64 2225 MAX-ACCESS read-only 2226 STATUS current 2227 DESCRIPTION 2228 "The high-capacity version of 2229 tpmExcpReportStatSumIXSq. 2230 Note that this object will only be instantiated if the 2231 agent supports High Capacity monitoring for a particular 2232 dataSource." 2233 ::= { tpmExcpReportEntry 18 } 2235 -- 2236 -- TPM Conformance 2237 -- 2239 tpmMIBCompliances OBJECT IDENTIFIER ::= { tpmConformance 1 } 2240 tpmGroups OBJECT IDENTIFIER ::= { tpmConformance 2 } 2242 -- 2243 -- TPM Compliance Statement 2244 -- 2246 tpmMIBCompliance MODULE-COMPLIANCE 2247 STATUS current 2248 DESCRIPTION 2249 "Describes the requirements for conformance to 2250 the TPM-MIB. 2252 This compliance statement defines the following 2253 TPM-MIB implementation: 2255 - tpmCapabilitiesGroup (minimum) 2256 - tpmAggregateReportsGroup (minimum) 2257 - tpmCurrentReportsGroup (optional) 2258 - tpmExceptionReportsGroup (optional). 2260 In order to implement the (optional) 2261 tpmExceptionReportsGroup, it is necessary 2262 to implement pieces of the APM-MIB as 2263 described in the tpmApmMIBCompliance MODULE 2264 below. Further, in the event that the TPM-MIB 2265 be used to provide a drill-down capability, 2266 which is the true value of this MIB, then the 2267 tpmApmReportControlGroup must be implemented." 2268 MODULE -- this module 2270 MANDATORY-GROUPS 2271 { tpmCapabilitiesGroup, 2272 tpmAggregateReportsGroup } 2274 GROUP tpmCurrentReportsGroup 2275 DESCRIPTION 2276 "The implementation of this group is optional." 2278 GROUP tpmExceptionReportsGroup 2279 DESCRIPTION 2280 "The implementation of this group is optional. 2281 However, because the control for this reporting group 2282 resides with the APM-MIB module, the apmReportGroup 2283 and the apmExceptionGroup must also be implemented." 2285 ::= { tpmMIBCompliances 1 } 2287 -- 2288 -- tpmCurrentReportsGroup Compliance 2289 -- 2290 tpmCurrentReportsCompliance MODULE-COMPLIANCE 2291 STATUS current 2292 DESCRIPTION 2293 "This defines the Current Reports compliance. 2294 This is useful when information on in-progress 2295 and historical transaction-level data is 2296 desired." 2297 MODULE -- this module 2299 MANDATORY-GROUPS 2300 { tpmCapabilitiesGroup, 2301 tpmAggregateReportsGroup, 2302 tpmCurrentReportsGroup } 2304 ::= { tpmMIBCompliances 2 } 2306 -- 2307 -- tpmExceptionReportsGroup Compliance 2308 -- 2309 tpmExceptionReportsCompliance MODULE-COMPLIANCE 2310 STATUS current 2311 DESCRIPTION 2312 "This defines the Exception Reports compliance. 2313 This is useful when information on 2314 transactions whose performance is deemed 2315 out-of-bounds." 2317 MODULE -- this module 2319 MANDATORY-GROUPS 2320 { tpmCapabilitiesGroup, 2321 tpmAggregateReportsGroup, 2322 tpmExceptionReportsGroup } 2324 MODULE APM-MIB 2326 MANDATORY-GROUPS 2327 { apmReportGroup, 2328 apmExceptionGroup } 2330 ::= { tpmMIBCompliances 3 } 2332 -- 2333 -- TPM-MIB Groups 2334 -- 2336 tpmCapabilitiesGroup OBJECT-GROUP 2337 OBJECTS { tpmClockResolution, 2338 tpmClockMaxSkew, 2339 tpmClockSource, 2340 tpmTransMetricDirLastChange, 2341 tpmTransMetricProtocolIndex, 2342 tpmTransMetricMetricIndex, 2343 tpmTransMetricDirConfig, 2344 tpmMetricDefType, 2345 tpmMetricDefDirType, 2346 tpmMetricDefName, 2347 tpmMetricDefReference, 2348 tpmMetricDefGlobalID } 2349 STATUS current 2350 DESCRIPTION 2351 "The tpmCapabilitiesGroup specify various capabilities 2352 associated with the monitoring agent." 2353 ::= { tpmGroups 1 } 2355 tpmAggregateReportsGroup OBJECT-GROUP 2356 OBJECTS { tpmAggrReportCntrlApmCntrlIndex, 2357 tpmAggrReportCntrlDataSource, 2358 tpmAggrReportCntrlAggrType, 2359 tpmAggrReportCntrlInterval, 2360 tpmAggrReportCntrlReqSize, 2361 tpmAggrReportCntrlGrantedSize, 2362 tpmAggrReportCntrlReqReports, 2363 tpmAggrReportCntrlGrantedReports, 2364 tpmAggrReportCntrlStartTime, 2365 tpmAggrReportCntrlReportNumber, 2366 tpmAggrReportCntrlInsertsDenied, 2367 tpmAggrReportCntrlDroppedFrames, 2368 tpmAggrReportCntrlOwner, 2369 tpmAggrReportCntrlStorageType, 2370 tpmAggrReportCntrlStatus, 2371 tpmAggrReportStatN, 2372 tpmAggrReportOverflowStatN, 2373 tpmAggrReportHCStatN, 2374 tpmAggrReportStatSumX, 2375 tpmAggrReportOverflowStatSumX, 2376 tpmAggrReportHCStatSumX, 2377 tpmAggrReportStatMaximum, 2378 tpmAggrReportStatMinimum, 2379 tpmAggrReportStatSumSq, 2380 tpmAggrReportOverflowStatSumSq, 2381 tpmAggrReportHCStatSumSq, 2382 tpmAggrReportStatSumIX, 2383 tpmAggrReportOverflowStatSumIX, 2384 tpmAggrReportHCStatSumIX, 2385 tpmAggrReportStatSumIXSq, 2386 tpmAggrReportOverflowStatSumIXSq, 2387 tpmAggrReportHCStatSumIXSq } 2388 STATUS current 2389 DESCRIPTION 2390 "The tpmAggregateReportsGroup provides control 2391 and reporting of aggregate measurement 2392 statistics." 2393 ::= { tpmGroups 2 } 2395 tpmCurrentReportsGroup OBJECT-GROUP 2396 OBJECTS { tpmCurReportMetricValue, 2397 tpmCurReportCompletion, 2398 tpmCurReportSize } 2399 STATUS current 2400 DESCRIPTION 2401 "The tpmCurrentReportsGroup contains metric 2402 information relating to on-going measurements 2403 as well as historical values." 2404 ::= { tpmGroups 3 } 2406 tpmExceptionReportsGroup OBJECT-GROUP 2407 OBJECTS { tpmExcpReportStatN, 2408 tpmExcpReportOverflowStatN, 2409 tpmExcpReportHCStatN, 2410 tpmExcpReportStatSumX, 2411 tpmExcpReportOverflowStatSumX, 2412 tpmExcpReportHCStatSumX, 2413 tpmExcpReportStatMaximum, 2414 tpmExcpReportStatMinimum, 2415 tpmExcpReportStatSumSq, 2416 tpmExcpReportOverflowStatSumSq, 2417 tpmExcpReportHCStatSumSq, 2418 tpmExcpReportStatSumIX, 2419 tpmExcpReportOverflowStatSumIX, 2420 tpmExcpReportHCStatSumIX, 2421 tpmExcpReportStatSumIXSq, 2422 tpmExcpReportOverflowStatSumIXSq, 2423 tpmExcpReportHCStatSumIXSq } 2424 STATUS current 2425 DESCRIPTION 2426 "The tpmExceptionReportsGroup reports 2427 sub-application level statistics associated 2428 with errant applications." 2429 ::= { tpmGroups 4 } 2431 END 2432 6. Intellectual Property 2434 The IETF takes no position regarding the validity or scope of any 2435 intellectual property or other rights that might be claimed to 2436 pertain to the implementation or use of the technology described in 2437 this document or the extent to which any license under such rights 2438 might or might not be available; neither does it represent that it 2439 has made any effort to identify any such rights. Information on the 2440 IETF's procedures with respect to rights in standards-track and 2441 standards-related documentation can be found in BCP-11. Copies of 2442 claims of rights made available for publication and any assurances of 2443 licenses to be made available, or the result of an attempt made to 2444 obtain a general license or permission for the use of such 2445 proprietary rights by implementers or users of this specification can 2446 be obtained from the IETF Secretariat." 2448 The IETF invites any interested party to bring to its attention any 2449 copyrights, patents or patent applications, or other proprietary 2450 rights which may cover technology that may be required to practice 2451 this standard. Please address the information to the IETF Executive 2452 Director. 2454 7. Acknowledgements 2456 This memo has been produced with a great deal of assistance from 2457 David Craver, Joseph Maixner and John Metzger of Hifn, Inc. The 2458 authors also gratefully acknowledge the beneficial discussions they 2459 have had with Carter Bullard of QoSient, LLC. The tpmMetricDefTable 2460 was taken from Andy Bierman's performance management capabilities 2461 draft, which was a draft proposed early on in the RMON WG during the 2462 formation of the TPM and APM MIB work. Finally, this MIB module 2463 draws heavily from the work of Steve Waldbusser and his APM-MIB 2464 [RFC3729]. 2466 8. Normative References 2468 [RFC2021] Waldbusser, S., "Remote Network Monitoring Management 2469 Information Base Version 2 using SMIv2", RFC 2021, January 2470 1997. 2472 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", 2473 RFC 2026, October 1996. 2475 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2476 Rose, M. and S. Waldbusser, "Structure of Management 2477 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2478 1999. 2480 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2481 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", 2482 STD 58, RFC 2579, April 1999. 2484 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2485 Rose, M. and S. Waldbusser, "Conformance Statements for 2486 SMIv2", STD 58, RFC 2580, April 1999. 2488 [RFC2819] Waldbusser, S., "Remote Network Monitoring MIB", STD 59, RFC 2489 2819, May 2000. 2491 [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual 2492 Conventions for Additional High Capacity Data Types", RFC 2493 2856, June 2000. 2495 [RFC2895] Bierman, A., Bucci, C. and R. Iddon, "Remote Network 2496 Monitoring MIB Protocol Identifiers", RFC 2895, August 2000. 2498 [RFC3273] Waldbusser, S., "Remote Network Monitoring Management 2499 Information Base for High Capacity Networks", RFC 3273, July 2500 2002. 2502 [RFC3395] Bierman, A., Bucci, C., Dietz, R. and A. Warth "Remote 2503 Network Monitoring MIB Protocol Identifiers Reference 2504 Extensions", RFC 3395, September 2002. 2506 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 2507 for Describing Simple Network Management Protocol (SNMP) 2508 Management Frameworks", RFC 3411, December 2002. 2510 [RFC3729] Waldbusser, S., "Application Performance Measurement MIB", 2511 RFC 3729, March 2004. 2513 [RFCXXX2] Kalbfleisch, K., Cole, R.G. and D. Romascanu, "Definition of 2514 Managed Objects for Synthetic Sources for performance 2515 Monitoring Algorithms", RFC XXX2, January 2004. 2517 [RFCXXX3] Stephan, E., "IPPM metrics registry", RFC XXX3, May 2004. 2519 9. Informative References 2521 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2522 "Introduction and Applicability Statements for Internet- 2523 Standard Management Framework", RFC 3410, December 2002. 2525 [Y.1540] The ITU-T Recommendation Y.1540, "IP Data Transport Service 2526 - IP packet transfer performance metrics", ITU-T Rec. 2527 Y.1540, December 2002. 2529 [RFC2679] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-way Delay 2530 Metric for IPPM", RFC 2679, September 1999. 2532 [RFC2680] Almes, G., Kalidindi, S. and M. Zekauskas, "A One-Way Packet 2533 Loss Metric for IPPM" RFC 2680, September 1999. 2535 [RFC2681] Almes, G., Kalidindi, S. and M. Zekauskas, "A Round-Trip 2536 Delay Metric for IPPM", RFC 2681, September 1999. 2538 [RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation 2539 Metric for IP Performance Metrics (IPPM)", RFC 3393, 2540 November 2002. 2542 [RFC3432] Raisanen, V., Grotefeld, G. and A. Morton, "Network 2543 Performance Measurement with Periodic Streams", RFC 3432, 2544 November 2002. 2546 10. Security Considerations 2548 This MIB relates to a system which provides a passive monitoring 2549 capability of a broadcast subnet, a switched subnet or point-to-point 2550 subnets. As such, it collects information relating to network layer 2551 addresses, traffic statistics relating to conversations and to 2552 application-level activities. These statistics could be deemed 2553 sensitive in certain networking environments. 2555 There are a number of management objects defined in this MIB module 2556 with a MAX-ACCESS clause of read-write and/or read-create. Such 2557 objects may be considered sensitive or vulnerable in some network 2558 environments. The support for SET operations in a non-secure 2559 environment without proper protection can have a negative effect on 2560 network operations. These are the tables and objects and their 2561 sensitivity/vulnerability: 2563 + The tpmTransMetricDirConfig object describes and configures the 2564 probe's support for a given performance metric in relationship to 2565 a specified transaction and application. The agent creates 2566 entries in this table for all metric and transaction combinations 2567 that it can generate and this object controls the on/off switch 2568 for this capability. If certain statistics for a supported 2569 transaction are deemed sensitive, then access to SET operations on 2570 this object should be protected. 2572 + The tpmAggrReportCntrlDataSource sets the interface on which the 2573 network addresses, conversational and application-level statistics 2574 will be collected. 2576 + The tpmAggrReportCntrlAggrType object controls the level of data 2577 aggregation implemented in the report tables. For example, this 2578 object could to set to allow client-level information to be 2579 exposed. 2581 In order to implement this MIB module, an agent must make certain 2582 management information available about protocols and network 2583 addresses used within a managed system, which may be considered 2584 sensitive in some network environments. Therefore some of the 2585 readable objects in this MIB module (i.e., objects with a MAX-ACCESS 2586 other than not-accessible) may be considered sensitive or vulnerable 2587 in some network environments. It is thus important to control even 2588 GET and/or NOTIFY access to these objects and possibly to even 2589 encrypt the values of these objects when sending them over the 2590 network via SNMP. These are the tables and objects and their 2591 sensitivity/vulnerability: 2593 + The tpmAggrReportTable contains the statistical studies which 2594 the probe was configured to generate. These tables contain the 2595 historical, aggregated data providing information on the network 2596 address and traffic statistics related to their conversations. 2598 + The tpmCurReportTable contains information on current 2599 transaction flows. This table provides a view of the current 2600 activity on a subnet or a client machine. 2602 SNMP versions prior to SNMPv3 did not include adequate security. 2603 Even if the network itself is secure (for example by using IPSec), 2604 even then, there is no control as to who on the secure network is 2605 allowed to access and GET/SET (read/change/create/delete) the objects 2606 in this MIB module. 2608 It is RECOMMENDED that implementers consider the security features as 2609 provided by the SNMPv3 framework (see [RFC3410], section 8), 2610 including full support for the SNMPv3 cryptographic mechanisms (for 2611 authentication and privacy). 2613 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2614 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2615 enable cryptographic security. It is then a customer/operator 2616 responsibility to ensure that the SNMP entity giving access to an 2617 instance of this MIB module is properly configured to give access to 2618 the objects only to those principals (users) that have legitimate 2619 rights to indeed GET or SET (change/create/delete) them. 2621 11. Author's Address 2623 Russell Dietz 2624 Hifn, Inc. 2625 750 University Ave 2626 Los Gatos, CA, USA 95032-7695 2627 Tel: +1 408 399-3623 2628 Fax: +1 408 399-3501 2629 E-mail: rdietz@hifn.com 2631 Robert Cole 2632 Johns Hopkins University Applied Physics Laboratory 2633 MP2-170 2634 11100 Johns Hopkins Road 2635 Laurel, MD 20723-6099 2636 USA 2637 Tel: +1 443-778-6951 2638 Email: robert.cole@jhuapl.edu 2640 12. Full Copyright Statement 2642 Copyright (C) The Internet Society (2004). This document is subject 2643 to the rights, licenses and restrictions contained in BCP 78 and 2644 except as set forth therein, the authors retain all their rights. 2646 This document and the information contained herein are provided on an 2647 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2648 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2649 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2650 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2651 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2652 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2654 Intellectual Property 2656 The IETF takes no position regarding the validity or scope of any 2657 Intellectual Property Rights or other rights that might be claimed to 2658 pertain to the implementation or use of the technology described in 2659 this document or the extent to which any license under such rights 2660 might or might not be available; nor does it represent that it has 2661 made any independent effort to identify any such rights. Information 2662 on the procedures with respect to rights in RFC documents can be 2663 found in BCP 78 and BCP 79. 2665 Copies of IPR disclosures made to the IETF Secretariat and any 2666 assurances of licenses to be made available, or the result of an 2667 attempt made to obtain a general license or permission for the use of 2668 such proprietary rights by implementers or users of this 2669 specification can be obtained from the IETF on-line IPR repository at 2670 http://www.ietf.org/ipr. 2672 The IETF invites any interested party to bring to its attention any 2673 copyrights, patents or patent applications, or other proprietary 2674 rights that may cover technology that may be required to implement 2675 this standard. Please address the information to the IETF at ietf- 2676 ipr@ietf.org. 2678 *************************************************************** 2679 * Note to the RFC Editor (to be removed prior to publication) * 2680 * * 2681 * 1) The reference to RFCXXXX within the DESCRIPTION clauses * 2682 * of the MIB module point to this draft and are to be * 2683 * assigned by the RFC Editor. * 2684 * * 2685 * 2) The reference to RFCXXX2 throughout this document point * 2686 * to the current . This * 2687 * MIB module imports TCs from this draft. Once the SSPM MIB * 2688 * draft is published as an RFC, then the RFCXXX2 references * 2689 * need to be replaced with the SSPM MIB RFC number. * 2690 * * 2691 * 3) The reference to RFCXXX3 throughout this document point * 2692 * to the current . * 2693 * This MIB module can reference OIDs from this draft. Once * 2694 * published as an RFC, then the RFCXXX3 references * 2695 * need to be replaced with the IPPM Metric Registry RFC * 2696 * number. * 2697 * * 2698 ***************************************************************