idnits 2.17.1 draft-ietf-applmib-mib-11.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** 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 separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (17 November 1998) is 9289 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) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '5') ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '7') ** Downref: Normative reference to an Historic RFC: RFC 1227 (ref. '8') ** Obsolete normative reference: RFC 1228 (ref. '9') (Obsoleted by RFC 1592) ** Obsolete normative reference: RFC 1514 (ref. '10') (Obsoleted by RFC 2790) ** Downref: Normative reference to an Experimental RFC: RFC 1592 (ref. '11') ** Obsolete normative reference: RFC 1700 (ref. '13') (Obsoleted by RFC 3232) ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '14') ** Obsolete normative reference: RFC 1902 (ref. '15') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '16') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '17') (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 1905 (ref. '18') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (ref. '19') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2037 (ref. '20') (Obsoleted by RFC 2737) ** Downref: Normative reference to an Informational RFC: RFC 2039 (ref. '21') ** Obsolete normative reference: RFC 2248 (ref. '23') (Obsoleted by RFC 2788) ** Obsolete normative reference: RFC 2249 (ref. '24') (Obsoleted by RFC 2789) ** Obsolete normative reference: RFC 2257 (ref. '25') (Obsoleted by RFC 2741) ** Obsolete normative reference: RFC 2271 (ref. '26') (Obsoleted by RFC 2571) ** Obsolete normative reference: RFC 2272 (ref. '27') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2273 (ref. '28') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2274 (ref. '29') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (ref. '30') (Obsoleted by RFC 2575) Summary: 32 errors (**), 0 flaws (~~), 3 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT C. Kalbfleisch 3 Verio, Inc. 4 C. Krupczak 5 Empire Technologies, Inc. 6 R. Presuhn 7 BMC Software, Inc. 8 J. Saperia 9 IronBridge Networks 10 17 November 1998 12 Application Management MIB 13 15 Status of this Memo 17 This document is an Internet-Draft. Internet-Drafts are working 18 documents of the Internet Engineering Task Force (IETF), its areas, 19 and its working groups. Note that other groups may also distribute 20 working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as ``work in progress.'' 27 To view the entire list of current Internet-Drafts, please check the 28 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 29 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 30 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 31 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 33 Copyright Notice 35 Copyright (C) The Internet Society (1998). All Rights Reserved. 37 Abstract 39 This memo defines an experimental portion of the Management 40 Information Base (MIB) for use with network management protocols in 41 the Internet Community. In particular, it defines objects used for 42 the management of applications. This MIB complements the System 43 Application MIB, providing for the management of applications' common 44 attributes which could not typically be observed without the 45 cooperation of the software being managed. 47 Table of Contents 49 1. Introduction and Overview ................................... 3 50 2. The SNMP Management Framework ............................... 4 51 3. Architecture ................................................ 5 52 3.1. Relationships to other MIBs ............................... 5 53 3.1.1. Relationship to the System Application MIB .............. 6 54 3.1.2. Relationship to the Host Resources MIB .................. 6 55 3.1.3. Relationship to NSM ..................................... 6 56 4. MIB Structure ............................................... 6 57 4.1. The service-level tables .................................. 8 58 4.1.1. The service name to service instance table .............. 9 59 4.1.2. The service instance to service name table .............. 9 60 4.2. The I/O channel group ..................................... 9 61 4.2.1. The open channels table ................................. 10 62 4.2.2. The open files table .................................... 11 63 4.2.3. The open connections table .............................. 12 64 4.2.4. The transaction stream summary table .................... 12 65 4.2.5. The transaction flow statistics table ................... 13 66 4.2.6. The transaction kind statistics table ................... 13 67 4.3. The former channel group .................................. 14 68 4.3.1. The former channel control table ........................ 14 69 4.3.2. The former channel table ................................ 14 70 4.3.3. The former connection table ............................. 14 71 4.3.4. The former file table ................................... 14 72 4.3.5. The transaction history tables .......................... 15 73 4.4. The running element status and control group .............. 15 74 4.4.1. The running application element status table ............ 15 75 4.4.2. The running application element control table ........... 15 76 5. Definitions ................................................. 16 77 6. Implementation Issues ....................................... 80 78 7. Intellectual Property ....................................... 80 79 8. Acknowledgements ............................................ 81 80 9. Security Considerations ..................................... 81 81 10. References ................................................. 82 82 11. Authors' Addresses ......................................... 84 83 12. Full Copyright Statement ................................... 85 85 1. Introduction and Overview 87 This document furthers the work begun in the systems application MIB 88 [31]. 90 The development of the "Host Resources MIB" [10], "Network Services 91 Monitoring MIB" [23], "Mail Monitoring MIB" [24], "Relational 92 Database Management System (RDBMS) Management Information Base (MIB) 93 using SMIv2" [12], "Entity MIB using SMIv2" [20], and "Applicability 94 of Standards Track MIBs to Management of World Wide Web Servers" [21] 95 provides us with a base of experience in making a variety of 96 applications visible to management; this specification abstracts out 97 the common aspects of applications management and provides a generic 98 base usable for the management of almost any application. 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in RFC 2119 [22]. 104 Due to the design decision to not require application 105 instrumentation, many important topics were not handled in system 106 application MIB [31]. The following topics are within the scope of 107 this document: 109 - Support for generic application throughput 110 measurements; 112 - Providing MIB definitions that allow managed entities 113 to report what they considered to be units of work; 115 - Providing support for generic application response time 116 monitoring capabilities; (Note that APIs for this 117 purpose have already been developed, an example of such 118 an API is to be found in the "Application Response 119 Measurement (ARM) API Guide, Version 2" [1].) 121 - Provide explicit support for the management of 122 applications distributed within a single managed system 123 ("local" distribution); 125 - Address generic resource management issues, including: 127 - files in use; 129 - I/O statistics (from the application's 130 perspective, not at the operating system or 131 device driver level); 133 - application-layer networking resource usage 135 - Facilities for the control of applications, including: 137 - Stopping application elements 139 - Suspending and resuming application elements; 141 - Requesting reconfiguration (e.g., SIGHUP). 143 Note that these issues are addressed at least in part by other (non- 144 IETF) standards work, including "ITU-T Recommendation X.744 | ISO/IEC 145 IS 10164-18:1996" [3] and "IEEE P1387.2, POSIX System Administration 146 - Part 2: Software Administration" [2]. 148 2. The SNMP Management Framework 150 The SNMP Management Framework presently consists of five major 151 components: 153 An overall architecture, described in RFC 2271 [26]. 155 Mechanisms for describing and naming objects and events for 156 the purpose of management. The first version of this 157 Structure of Management Information (SMI) is called SMIv1 and 158 described in RFC 1155 [4], RFC 1212 [6] and RFC 1215 [7]. The 159 second version, called SMIv2, is described in RFC 1902 [15], 160 RFC 1903 [16] and RFC 1904 [17]. 162 Message protocols for transferring management information. 163 The first version of the SNMP message protocol is called 164 SNMPv1 and described in RFC 1157 [5]. A second version of the 165 SNMP message protocol, which is not an Internet standards 166 track protocol, is called SNMPv2c and described in RFC 1901 167 [14] and RFC 1906 [19]. The third version of the message 168 protocol is called SNMPv3 and described in RFC 1906 [19], RFC 169 2272 [27] and RFC 2274 [29]. 171 Protocol operations for accessing management information. The 172 first set of protocol operations and associated PDU formats is 173 described in RFC 1157 [5]. A second set of protocol 174 operations and associated PDU formats is described in RFC 1905 175 [18]. 177 A set of fundamental applications described in RFC 2273 [28] 178 and the view-based access control mechanism described in RFC 179 2275 [30]. 181 Managed objects are accessed via a virtual information store, termed 182 the Management Information Base or MIB. Objects in the MIB are 183 defined using the mechanisms defined in the SMI. 185 This memo specifies a MIB module that is compliant to the SMIv2. A 186 MIB conforming to the SMIv1 can be produced through the appropriate 187 translations. The resulting translated MIB must be semantically 188 equivalent, except where objects or events are omitted because no 189 translation is possible (use of Counter64). Some machine readable 190 information in SMIv2 will be converted into textual descriptions in 191 SMIv1 during the translation process. However, this loss of machine 192 readable information is not considered to change the semantics of the 193 MIB. 195 3. Architecture 197 Object-oriented modeling techniques like subclassing and multiple 198 inheritance can be emulated in the SNMP information model through the 199 use of tables with common indexes. 201 The challenge for the developer of management applications is to 202 recognize those situations in which various aspects of a single 203 logical resource are represented in several different tables, 204 possibly defined in different MIBs. 206 Most of the management information defined here may pertain to any 207 number of applications in a managed system. The simplest way of 208 supporting this requirement within the SNMP information model is to 209 use tables. This means that the management information for a 210 particular resource may be found in one or more rows of one or more 211 tables; the fact that this information pertains to a single resource 212 may be inferred from the index values used, possibly with the support 213 of mapping tables. This also means that a single table may contain 214 management information relevant to a number of applications. This 215 has significant implementation implications; see the implementation 216 issues section below for more information. 218 3.1. Relationships to other MIBs 220 This section outlines the relationships of the components of this MIB 221 (usually in the form of common indexing structures) to: 223 - the systems applications MIB [31] 225 - the host resources MIB [10] 227 - the network services monitoring MIB [23] 229 3.1.1. Relationship to the System Application MIB 231 The system application MIB defines attributes for management of 232 applications which can be realized without instrumenting the 233 application itself. This specification extends that framework to 234 include additional attributes which will typically require 235 instrumentation within the managed resource. The sysApplRunElmtIndex 236 is the key connection between these two MIBs; it is essential that 237 implementations of this MIB and of the system applications MIB 238 running concurrently on a given platform employ a consistent policy 239 for assigning this value to identify running application elements. 241 3.1.2. Relationship to the Host Resources MIB 243 The Host Resources MIB [10] supplies information on the hardware, 244 operating system, installed and running software on a host. 246 The Host Resources MIB has three hardware groups ("hrSystem", 247 "hrStorage" and "hrDevice") and three software groups ("hrSWRun", 248 "hrSWRunPerf" and "hrSWInstalled"). Of these, the software groups 249 are of greatest significance to this MIB. 251 The software groups define management information on the software 252 used in the system. The information provided is grouped into (1) the 253 currently running, (2) the performance and (3) the installed 254 applications. 256 The index "hrSWRunIndex" used in the "hrSWRunTable" and other tables 257 to identify running software by process identifier (or equivalent) 258 relates information in the Host Resources MIB to information in the 259 System Applications MIB and this MIB. It is essential that the 260 values assigned to hrSWRunIndex from the Host Resources MIB be 261 consistent with the values used for sysApplRunElmtIndex. 263 3.1.3. Relationship to NSM 265 The Network Services Monitoring MIB [23] is defined as the base set 266 of attributes for managing network applications. The Application MIB 267 includes information normally obtainable only from the managed 268 resource itself, rather than the supporting system. Due to 269 differences in index representation, the relationship between the 270 Network Services Monitoring MIB and the Application MIB is not 271 formally defined. 273 4. MIB Structure 275 This MIB is organized into several groups, which in turn are 276 organized into tables to provide the monitoring and control of 277 information relevant to the management of applications. The groups 278 model: 280 - the service-level view of applications 282 - information on open channels (files, connections, 283 transaction streams) in use by applications 285 - historical information on former channels 287 - process-level status and control information 289 These groups are organized into various tables. Information for a 290 particular running managed application appears in the form of entries 291 in the appropriate tables. The tables are: 293 - the tables providing a service-level view, including: 295 - the service name to service instance table 297 - the service instance to service name table 299 - the service instance to running application 300 element table 302 - the running application element to service 303 instance table 305 - the tables providing information on I/O channels, 306 including: 308 - the table of open channels 310 - the table of open files 312 - the open connections table 314 - the transaction statistics tables 316 - historical information on I/O channels 318 - the running application element status and control 319 group 321 - the running application element status table 323 - the running application element control table 325 In order to support SNMPv1, SNMPv2, and SNMPv3 environments, in cases 326 where counter objects may potentially advance very rapidly, where 327 sixty-four bit counters have been used thirty-two bit counters 328 reporting the low-order thirty-two bits of the value have also been 329 defined. 331 Since rows in most of these tables will come and go with the running 332 application elements whose information is contained in them, 333 sysUpTime.0 is not appropriate as a discontinuity indicator for 334 counters in these tables. By defining separate discontinuity 335 indicators for the rows in these tables, entries can come and go as 336 needed without causing other objects to appear to have 337 discontinuities. As required by [15], the discontinuity indicators 338 for the various information objects in these tables are identified in 339 the relevant DESCRIPTION clauses. Note that a discontinuity in one 340 of these counters does not imply a sysUpTime.0 discontinuity, nor 341 does a sysUpTime.0 discontinuity imply a discontinuity in any of 342 these counters. 344 4.1. The service-level tables 346 The service-level tables permit the identification of one or more 347 instances of named services on a system, and the association of 348 running application elements to these services. 350 Service names are represented as human-readable strings, using values 351 assigned by IANA where possible. The allocation of unique values for 352 service instance identifiers is a local administrative issue; the 353 values allocated must be constant for the lifetime of the service 354 instance, and re-use of values should be avoided. 356 It is important to understand that a service is not the same thing as 357 a protocol. Rather, some services may be at least partially 358 described by the protocol(s) used to provide that service. 360 In deciding what should or should not be considered a service, the 361 following factors merit consideration: 363 - is there an identifiable set of resources associated 364 with providing this service? 366 - is there a reasonably long-lived server or client 367 process? 369 Following this reasoning, one can see where SMTP and HTTP service 370 providers would be good candidates for classification as services for 371 purposes of application management, where finger probably would not. 372 Of course, implementors of this MIB are free to define additional 373 services. An applicability statement may be an appropriate vehicle 374 for standardizing how a specific service's information is reported 375 using this MIB. 377 4.1.1. The service name to service instance table 379 The service name to service instance table uses the service name as 380 its primary key, and the service instance identifier as its secondary 381 key. It facilitates the identification and lookup of the instances 382 of a given service in a system. 384 4.1.2. The service instance to service name table 386 The service instance to service name table uses the service instance 387 identifier as its primary key, and the service name as its secondary 388 key. Given a service instance identifier, it facilitates the lookup 389 of the name of the service being provided. 391 4.1.3. The service instance to running application element table 393 The service instance to running application element table uses the 394 service instance identifier as its primary key, and the running 395 application element index as its secondary key. This facilitates the 396 identification of the set of running application elements providing a 397 given instance of a service. 399 4.1.4. The running application element to service instance table 401 The running application element to service instance table uses the 402 running application element index as its primary key and the service 403 instance identifier as its secondary key. It identifies the set of 404 services provided by a given running application element. 406 4.2. The I/O channel group 408 Information processed by an application can be modeled using the 409 concept of a channel. Two kinds of channels, for example, are files 410 and network connections. 412 +-------+ 413 | File | 414 +---------+ /+-------+ 415 +-------------+ | Generic | / 416 | transaction |----| I/O |-------< 417 | stream | | Channel | \ +------------+ 418 +-------------+ +---------+ \ | open or | 419 \| listening | 420 | connection | 421 +------------+ 423 For each entry in the open channel table, there will be a 424 corresponding entry in either the open file table or the open 425 connection table. 427 The information flowing on a channel may be structured as 428 transactions. When the information flow on a channel is being 429 monitored as a transaction stream, an entry in the transaction stream 430 table will represent this fact and the associated information about 431 that stream. 433 To facilitate traversal of these tables and retrieval of information 434 relevant to a specific running application element or service 435 instances, the initial indexes of these tables are the same. In each 436 case, the first index determines whether the second index is 437 interpreted as a running application element identifier or as a 438 service instance identifier. The third index serves to uniquely 439 identify a channel (and consequently, an open connection or file) in 440 the context of a running application element or service instance. 442 The transaction stream summary table contains per-stream summaries of 443 transaction statistics. The transaction flow statistics table 444 contains statistics broken into both transmit and receive counts for 445 requests and responses on each stream. The transaction kind 446 statistics table contains information further broken down by 447 transaction kind. 449 The transaction tables have a common structure for their indexing, 450 with additional indexes added for increasing detail. The initial 451 three indexes are the same as all the other tables in this group, 452 serving to uniquely identify each transaction stream. 454 4.2.1. The open channels table 456 The following information is available in this table: 458 - time at which the channel was opened 460 - number of read requests 462 - number of bytes read 464 - time at which most recent read operation was initiated 466 - number of write requests 468 - number of bytes written 470 - time at which most recent write operation was initiated 472 4.2.2. The open files table 474 The open files table contains one entry for each file in use by a 475 manageable running application element. (See "Definitions of System- 476 Level Managed Objects for Applications" [31] for a detailed 477 definition of a running application element.) The purpose of this 478 table is to identify the files in use and to record information 479 peculiar to files not already covered in the open channel table. 481 If multiple running application elements open the same file, there 482 will be an entry for each running application element opening that 483 file. Similarly, if a running application element opens a file 484 multiple times, there will be an entry in this table for the file 485 corresponding to each open. 487 The task of combining the information for file activity from this 488 table (organized by running application element) into per-application 489 statistics can be accomplished by a manager using the System 490 Application MIB's [31] sysApplInstallPkgTable to find the installed 491 application, the sysApplRunTable to find the running instances of 492 that application, and the sysApplElmtRunTable to find the relevant 493 values of sysApplElmtRunIndex. The manager, armed with a set of 494 values for sysApplElmtRunIndex, is now able to retrieve the relevant 495 portions of the applOpenFileTable and other tables in this MIB. 497 The following information is available in this table: 499 - file name 501 - file size 503 - current mode (read/write) of this file 505 By convention, the names "stdin", "stdout" and "stderr" are used when 506 these streams cannot be resolved to actual file names. 508 4.2.3. The open connections table 510 This table provides information on channels that are open connections 511 or listeners. 513 The following information is available for each connection: 515 - identification of the transport protocol in use 517 - near-end address and port 519 - far-end address and port 521 - identification of the application layer protocol in use 523 4.2.4. The transaction stream summary table 525 The transaction stream summary table contains per-stream summaries of 526 transaction statistics. The simple model of a transaction used here 527 looks like this: 529 invoker | Request | performer 530 | - - - - - - > | 531 | | 532 | Response | 533 | < - - - - - - | 534 | | 536 Since in some protocols it is possible for an entity to take on both 537 the invoker and performer roles, information here is accumulated for 538 transmitted and received requests, as well as for transmitted and 539 received responses. Counts are maintained for both transactions and 540 bytes transferred. The information represented in this table 541 includes: 543 - identification of the underlying connection or file 544 used for this transaction stream 546 - a human-readable description of this stream 548 - a human-readable description of this stream's notion of 549 what a unit of work is 551 - the cumulative amount of time spent (as an operation 552 invoker) waiting for responses (from queueing of 553 request to arrival of first response) 555 - the cumulative amount of time spent (as an operation 556 invoker) receiving responses (time from the arrival of 557 the first response to the arrival of the last response 558 in a series of responses to a particular request) 560 - the cumulative amount of time spent (as an operation 561 performer) handling requests (time from receipt of 562 request to queueing of first outgoing response) 564 - the cumulative amount of time spent (as an operation 565 performer) sending responses (time from queuing of 566 first response to the last response in a series of 567 responses to a particular request) 569 - the cumulative number of transactions initiated (as an 570 invoker) 572 - the cumulative number of transactions processed (as a 573 performer) 575 4.2.5. The transaction flow statistics table 577 The transaction flow statistics table contains statistics broken into 578 both transmit and receive counts for requests and responses on each 579 stream. In addition to the service instance / running application 580 element and transaction stream identifier indexes, rows in this table 581 are indexed by flow direction (transmit or receive) and role 582 (requests and responses). The information in this table includes: 584 - the number of transactions processed 586 - the number of bytes processed 588 - the time at which the most recent transaction was 589 processed in this flow 591 4.2.6. The transaction kind statistics table 593 The transaction kind statistics table contains summary information 594 organized by direction, request/response, and transaction kind for 595 each stream. The indexing of this table is like that of the 596 transaction flow table, with the addition of a transaction kind 597 index. 599 - number of transactions processed 600 - number of bytes processed 602 - the time at which the most recent transaction of this 603 kind in this direction in this stream was processed 605 4.3. The former channel group 607 The former channel group has several tables. The former channel 608 control table controls the retention of history information by a 609 running application element or service instance. The remaining 610 tables parallel the structure of the channel group, with one 611 significant difference in indexing structure. The closed channel 612 index is independent from the open channel index. 614 4.3.1. The former channel control table 616 The former channel control table provides control over the 617 accumulation of information on former connections for running 618 application elements and service instances. For each one, this 619 table, indexed by the running application element or service instance 620 index, controls whether information on former channels is 621 accumulated, how many of these history records are retained, how long 622 these are retained (within the lifetime of the process), and a count 623 of history entries that were deleted before their expiration time in 624 order to make room for new entries. 626 4.3.2. The former channel table 628 The former channel table provides historical information on channels 629 that have been closed. The number and lifetime of these entries is 630 controlled, for each running application element or service instance, 631 by the former channel control table. Most of the information in this 632 table corresponds to information in the open channel table. 634 For the connection or file-specific aspects of a given former 635 channel, an entry will exist in the former connection table or in the 636 former file table. 638 4.3.3. The former connection table 640 For formerly open channels that were connections, connection-specific 641 historical information is kept in the former connection table. For 642 each entry in the former connection table, there will be an 643 identically indexed entry in the former channel table. 645 4.3.4. The former file table 647 For formerly open channels that were files, file-specific historical 648 information is kept in the former file table. For each entry in the 649 former file table, there will be an identically indexed entry in the 650 former channel table. 652 4.3.5. The transaction history tables 654 Two tables provide per-transaction-kind breakdowns for channels 655 carrying transaction-structured flows. These tables are analogous to 656 the transaction flow and kind statistics tables, with similar index 657 structures. 659 4.4. The running element status and control group 661 The running application element status and control group has two 662 tables. 664 4.4.1. The running application element status table 666 This table provides information for a running application element. 667 Indexed by the sysApplElmtRunIndex, an entry in this table reports 668 useful information on that running element's resource usage. Entries 669 in this table contain: 671 - current heap usage for this running application element 673 - current number of open network connections for this 674 running application element 676 - the most recent error status message issued by this 677 running application element 679 Note that other information, such as the current number of open files 680 for this running application element, is available from the 681 sysapplElmtRunTable in [31]. 683 4.4.2. The running application element control table 685 This table provides rudimentary control over a running application 686 element. Indexed by the sysApplElmtRunIndex, an entry in this table 687 gives a manager with appropriate permissions the ability to suspend 688 and resume processing by this running element, the ability to request 689 reconfiguration, and the ability to terminate the running element. 691 Variables in this table include: 693 - a suspend/resume control 695 - a reconfiguration request control 696 - a termination request control 698 5. Definitions 700 APPLICATION-MIB DEFINITIONS ::= BEGIN 702 IMPORTS 703 MODULE-IDENTITY, OBJECT-TYPE, 704 Counter64, Counter32, Gauge32, 705 mib-2, Unsigned32, zeroDotZero FROM SNMPv2-SMI 707 DateAndTime, TEXTUAL-CONVENTION, 708 TestAndIncr, TDomain, 709 TimeStamp, TruthValue FROM SNMPv2-TC 711 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 713 MODULE-COMPLIANCE, OBJECT-GROUP 714 FROM SNMPv2-CONF 716 LongUtf8String, sysApplElmtRunIndex FROM SYSAPPL-MIB; 718 applicationMib MODULE-IDENTITY 719 LAST-UPDATED "9811171815Z" 720 ORGANIZATION "Application MIB Working Group" 721 CONTACT-INFO 722 "http://www.ietf.org/html.charters/applmib-charter.html 724 Randy Presuhn 725 BMC Software, Inc. 726 965 Stewart Drive 727 Sunnyvale, CA 94086 728 USA 730 Telephone: +1 408 616-3100 731 Facsimile: +1 408 616-3101 732 EMail: randy_presuhn@bmc.com 733 " 734 DESCRIPTION 735 "This MIB defines objects representing generic aspects of 736 applications that are of interest to management but typically 737 require instrumentation within managed application elements. 738 " 739 ::= { mib-2 ??? } -- IANA will make official assignment 741 -- 742 -- Registration hierarchy for this MIB 743 -- 744 applicationMibObjects OBJECT IDENTIFIER ::= 745 { applicationMib 1 } 747 applicationMibConformance OBJECT IDENTIFIER ::= 748 { applicationMib 2 } 750 -- 751 -- Groups defined in this MIB 752 -- 753 applServiceGroup OBJECT IDENTIFIER ::= 754 { applicationMibObjects 1 } 756 applChannelGroup OBJECT IDENTIFIER ::= 757 { applicationMibObjects 2 } 759 applPastChannelGroup OBJECT IDENTIFIER ::= 760 { applicationMibObjects 3 } 762 applElmtRunControlGroup OBJECT IDENTIFIER ::= 763 { applicationMibObjects 4 } 765 Unsigned64TC ::= TEXTUAL-CONVENTION 766 STATUS current 767 DESCRIPTION 768 "A non-negative 64-bit bit integer, without counter 769 semantics." 770 SYNTAX Counter64 772 ApplTAddress ::= TEXTUAL-CONVENTION 773 STATUS current 774 DESCRIPTION 775 "Denotes a transport service address. 777 For snmpUDPDomain, an ApplTAddress is 6 octets long, 778 the initial 4 octets containing the IP-address in 779 network-byte order and the last 2 containing the UDP 780 port in network-byte order. Consult 'Transport Mappings 781 for Version 2 of the Simple Network Management Protocol 782 (SNMPv2)' for further information on snmpUDPDomain." 783 SYNTAX OCTET STRING (SIZE (0..255)) 785 -- **************************************************************** 786 -- 787 -- applServiceGroup - 788 -- 789 -- The service-level tables permit the identification of one 790 -- or more instances of named services on a system, and the 791 -- association of running application elements to services. 792 -- 793 -- **************************************************************** 795 -- **************************************************************** 796 -- 797 -- The service name to service instance table 798 -- 799 -- **************************************************************** 801 applSrvNameToSrvInstTable OBJECT-TYPE 802 SYNTAX SEQUENCE OF ApplSrvNameToSrvInstEntry 803 MAX-ACCESS not-accessible 804 STATUS current 805 DESCRIPTION 806 "The service name to service instance table uses 807 service name as its primary key, and service instance 808 identifier as its secondary key. It facilitates the 809 identification and lookup of the instances of a given 810 service in a system." 811 ::= { applServiceGroup 1 } 813 applSrvNameToSrvInstEntry OBJECT-TYPE 814 SYNTAX ApplSrvNameToSrvInstEntry 815 MAX-ACCESS not-accessible 816 STATUS current 817 DESCRIPTION 818 "An applSrvNameToSrvInstEntry identifies an instance of 819 a given service. The allocation and reservation 820 of unique values for applSrvIndex is an administrative 821 issue. 823 An applSrvNameToSrvInstEntry exists for the lifetime of 824 that instance of that service; the index values may not 825 change during that lifetime. " 826 INDEX { applSrvName, applSrvIndex } 827 ::= { applSrvNameToSrvInstTable 1 } 829 ApplSrvNameToSrvInstEntry ::= SEQUENCE 830 { 831 applSrvInstQual SnmpAdminString 832 } 834 applSrvInstQual OBJECT-TYPE 835 SYNTAX SnmpAdminString 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The value of applSrcInstQual provides additional 840 information about this particular instance of this 841 service. 843 Although not used for indexing purposes, the value of 844 this attribute should be sufficiently unique to be 845 helpful to an administrator in distinguishing among 846 service instances. " 847 ::= { applSrvNameToSrvInstEntry 1 } 849 -- **************************************************************** 850 -- 851 -- Service instance to Service Name table 852 -- 853 -- **************************************************************** 855 applSrvInstToSrvNameTable OBJECT-TYPE 856 SYNTAX SEQUENCE OF ApplSrvInstToSrvNameEntry 857 MAX-ACCESS not-accessible 858 STATUS current 859 DESCRIPTION 860 "The service instance to service name table uses 861 service instance identifier as its primary key, and 862 service name as its secondary key. Given a service 863 instance identifier, it facilitates the lookup of the 864 name of the service being provided." 865 ::= { applServiceGroup 2 } 867 applSrvInstToSrvNameEntry OBJECT-TYPE 868 SYNTAX ApplSrvInstToSrvNameEntry 869 MAX-ACCESS not-accessible 870 STATUS current 871 DESCRIPTION 872 "An applSrvInstToSrvNameEntry maps a service instance 873 identifier back to a service name." 874 INDEX { applSrvIndex, applSrvName } 875 ::= { applSrvInstToSrvNameTable 1 } 877 ApplSrvInstToSrvNameEntry ::= SEQUENCE 878 { 879 applSrvName SnmpAdminString 880 } 882 applSrvName OBJECT-TYPE 883 SYNTAX SnmpAdminString 884 MAX-ACCESS read-only 885 STATUS current 886 DESCRIPTION 887 "The human-readable name of a service. Where 888 appropriate, as in the case where a service can be 889 identified in terms of a single protocol, the strings 890 should be established names such as those assigned by 891 IANA and found in STD 2 [13], or defined by some other 892 authority. In some cases private conventions apply 893 and the string should in these cases be consistent 894 with these non-standard conventions. An applicability 895 statement may specify the service name(s) to be used. 896 " 897 ::= { applSrvInstToSrvNameEntry 1 } 899 -- **************************************************************** 900 -- 901 -- The service instance to running application element table 902 -- 903 -- **************************************************************** 905 applSrvInstToRunApplElmtTable OBJECT-TYPE 906 SYNTAX SEQUENCE OF ApplSrvInstToRunApplElmtEntry 907 MAX-ACCESS not-accessible 908 STATUS current 909 DESCRIPTION 910 "The service instance to running application element 911 table uses the service instance identifier as its primary 912 key, and the running application element index as its 913 secondary key. This facilitates the identification 914 of the set of running application elements providing a 915 given instance of a service." 916 ::= { applServiceGroup 3 } 918 applSrvInstToRunApplElmtEntry OBJECT-TYPE 919 SYNTAX ApplSrvInstToRunApplElmtEntry 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "An applSrvInstToRunApplElmtEntry identifies a running 924 application element providing an instance of a service. 925 Note that there may be multiple running application 926 elements involved in the provision of an instance of 927 a service." 928 INDEX { applSrvIndex, sysApplElmtRunIndex } 929 ::= { applSrvInstToRunApplElmtTable 1 } 931 ApplSrvInstToRunApplElmtEntry ::= SEQUENCE 932 { 933 applSrvIndex Unsigned32 934 } 936 applSrvIndex OBJECT-TYPE 937 SYNTAX Unsigned32 (1..'ffffffff'h) 938 MAX-ACCESS read-only 939 STATUS current 940 DESCRIPTION 941 "An applSrvIndex is the system-unique identifier of 942 an instance of a service. The value is unique not only 943 across all instances of a given service, but also across 944 all services in a system. 946 Re-use of values for this index should be avoided. 947 No two service instances in a given system shall 948 concurrently have the same value for this index. 950 The value zero is excluded from the set of permitted 951 values for this index. This allows other tables to 952 potentially represent things which cannot be associated 953 with a specific service instance. 954 " 955 ::= { applSrvInstToRunApplElmtEntry 1 } 957 -- **************************************************************** 958 -- 959 -- The running application element to service instance table 960 -- 961 -- **************************************************************** 962 applRunApplElmtToSrvInstTable OBJECT-TYPE 963 SYNTAX SEQUENCE OF ApplRunApplElmtToSrvInstEntry 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "The running application element to service instance 968 table uses the running application element index as 969 its primary key and the service instance identifier as 970 its secondary key. It identifies the set of services 971 provided by a given running application element." 972 ::= { applServiceGroup 4 } 974 applRunApplElmtToSrvInstEntry OBJECT-TYPE 975 SYNTAX ApplRunApplElmtToSrvInstEntry 976 MAX-ACCESS not-accessible 977 STATUS current 978 DESCRIPTION 979 "An applRunApplElmtToSrvInstEntry serves to identify an 980 instance of a service being provided by a given running 981 application element. Note that a particular running 982 application element may provide multiple services." 983 INDEX { sysApplElmtRunIndex, applSrvInstance } 984 ::= { applRunApplElmtToSrvInstTable 1 } 986 ApplRunApplElmtToSrvInstEntry ::= SEQUENCE 987 { 988 applSrvInstance Unsigned32 989 } 991 applSrvInstance OBJECT-TYPE 992 SYNTAX Unsigned32 (1..'ffffffff'h) 993 MAX-ACCESS read-only 994 STATUS current 995 DESCRIPTION 996 "An applSrvInstance is the system-unique identifier of an 997 instance of a service. The value is unique not only 998 across all instances of a given service, but also across 999 all services. 1001 Re-use of values for this index should be avoided. 1002 No two service instances in a given system shall 1003 concurrently have the same value for this index. 1005 The value zero is excluded from the set of permitted 1006 values for this index. This allows other tables to 1007 potentially represent things which cannot be associated 1008 with a specific service instance. 1010 This attribute is semantically identical to 1011 applSrvIndex." 1012 ::= { applRunApplElmtToSrvInstEntry 1 } 1014 -- **************************************************************** 1015 -- 1016 -- applChannelGroup - group with tables for I/O 1017 -- 1018 -- In this group, the common abstraction is the Channel. 1019 -- Channels are realized as files or connections. 1020 -- The information flowing on a channel can always be 1021 -- measured in terms of a byte stream. Furthermore, for many 1022 -- channels, this information may also be measured in terms 1023 -- of transactions. 1024 -- 1025 -- For all of these tables, the first two indexes determines 1026 -- whether what is being measured is for a single running 1027 -- application element or for an instance of a service. 1028 -- 1029 -- The second index identifies the running application element 1030 -- or service instance. 1031 -- 1032 -- The third index is the channel id, which uniquely identifies 1033 -- a channel within the context of a running application element 1034 -- or service instance. 1035 -- 1036 -- Any remaining indexes are table-specific. 1037 -- 1038 -- **************************************************************** 1040 -- **************************************************************** 1041 -- 1042 -- applOpenChannelTable - Table of Open Channels 1043 -- 1044 -- **************************************************************** 1046 applOpenChannelTable OBJECT-TYPE 1047 SYNTAX SEQUENCE OF ApplOpenChannelEntry 1048 MAX-ACCESS not-accessible 1049 STATUS current 1050 DESCRIPTION 1051 "The applOpenChannelTable reports information on open 1052 channels for running application elements 1053 and for service instances. This table is 1054 indexed by applElmtOrSvc, applElmtOrSvcId, and 1055 applOpenChannelIndex. This effectively groups all 1056 entries for a given running application element 1057 or service instance together. ApplChannelIndex uniquely 1058 identifies an open channel (and, consequently, a file 1059 or connection) within the context of a particular 1060 running application element or service instance. 1062 Some of the information in this table is available 1063 through both sixty-four and thirty-two bit counters. 1064 The sixty-four bit counters are not accessible in 1065 protocols that do not support this data type." 1066 ::= { applChannelGroup 1 } 1068 applOpenChannelEntry OBJECT-TYPE 1069 SYNTAX ApplOpenChannelEntry 1070 MAX-ACCESS not-accessible 1071 STATUS current 1072 DESCRIPTION 1073 "An applOpenChannelEntry indicates that a channel has been 1074 opened by this running application element or service 1075 instance and is still open. Note that if a file has been 1076 opened multiple times, even by the same process, it will 1077 have multiple channel entries." 1078 INDEX { applElmtOrSvc, applElmtOrSvcId, 1079 applOpenChannelIndex } 1080 ::= { applOpenChannelTable 1 } 1082 ApplOpenChannelEntry ::= SEQUENCE 1083 { 1084 applElmtOrSvc INTEGER, 1085 applElmtOrSvcId Unsigned32, 1086 applOpenChannelIndex Unsigned32, 1087 applOpenChannelOpenTime TimeStamp, 1088 applOpenChannelReadRequests Counter64, 1089 applOpenChannelReadRequestsLow Counter32, 1090 applOpenChannelReadFailures Counter32, 1091 applOpenChannelBytesRead Counter64, 1092 applOpenChannelBytesReadLow Counter32, 1093 applOpenChannelLastReadTime DateAndTime, 1094 applOpenChannelWriteRequests Counter64, 1095 applOpenChannelWriteRequestsLow Counter32, 1096 applOpenChannelWriteFailures Counter32, 1097 applOpenChannelBytesWritten Counter64, 1098 applOpenChannelBytesWrittenLow Counter32, 1099 applOpenChannelLastWriteTime DateAndTime 1100 } 1102 applElmtOrSvc OBJECT-TYPE 1103 SYNTAX INTEGER { service(1), 1104 element(2) } 1105 MAX-ACCESS not-accessible 1106 STATUS current 1107 DESCRIPTION 1108 "The applElmtOrSvc attribute serves as an index for tables 1109 that can hold information both for individual running 1110 application elements as well as for service instances. 1112 If the value is service(1), the row contains information 1113 gathered at the level of a service. 1115 If the value is element(2), the row contains information 1116 for an individual running application element." 1117 ::= { applOpenChannelEntry 1 } 1119 applElmtOrSvcId OBJECT-TYPE 1120 SYNTAX Unsigned32 (1..'ffffffff'h) 1121 MAX-ACCESS not-accessible 1122 STATUS current 1123 DESCRIPTION 1124 "The applElmtOrSvcId attribute is used as an index in 1125 conjunction with the applElmtOrSvc attribute. 1127 When the value of applElmtOrSvc is service(1), this 1128 attribute's value corresponds to that of applSrvIndex, 1129 when the value of applElmtOrSvc is element(2), this 1130 attribute's value corresponds to sysApplElmtRunIndex." 1131 ::= { applOpenChannelEntry 2 } 1133 applOpenChannelIndex OBJECT-TYPE 1134 SYNTAX Unsigned32 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 "This attribute serves to uniquely identify this open 1139 connection in the context of the running application 1140 element or service instance. Where suitable, the 1141 application's native descriptor number should be used." 1142 ::= { applOpenChannelEntry 3 } 1144 applOpenChannelOpenTime OBJECT-TYPE 1145 SYNTAX TimeStamp 1146 MAX-ACCESS read-only 1147 STATUS current 1148 DESCRIPTION 1149 "This attribute records the value of sysUpTime.0 1150 when this channel was opened and this entry was added to 1151 this table. This attribute serves as a discontinuity 1152 indicator for the counter attributes in this entry 1153 and for any corresponding entries in the 1154 applOpenConnectionTable, applOpenFileTable, and the 1155 applTransactionStreamTable." 1156 ::= { applOpenChannelEntry 4 } 1158 applOpenChannelReadRequests OBJECT-TYPE 1159 SYNTAX Counter64 1160 UNITS "read requests" 1161 MAX-ACCESS read-only 1162 STATUS current 1163 DESCRIPTION 1164 "This attribute reports the number of read requests 1165 for this channel. All read requests for this channel 1166 by this entity, regardless of completion status, are 1167 included in this count. 1169 Read requests are counted in terms of system calls, 1170 rather than API calls. 1172 Discontinuities in this counter can be detected by 1173 monitoring the applOpenChannelOpenTime value for this 1174 entry." 1175 ::= { applOpenChannelEntry 5 } 1177 applOpenChannelReadRequestsLow OBJECT-TYPE 1178 SYNTAX Counter32 1179 UNITS "read requests" 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION 1183 "This attribute reports the low thirty-two bits of 1184 applOpenChannelReadRequests. 1186 Discontinuities in this counter can be detected by 1187 monitoring the applOpenChannelOpenTime value for this 1188 entry." 1189 ::= { applOpenChannelEntry 6 } 1191 applOpenChannelReadFailures OBJECT-TYPE 1192 SYNTAX Counter32 1193 UNITS "failed read requests" 1194 MAX-ACCESS read-only 1195 STATUS current 1196 DESCRIPTION 1197 "This attribute reports the number of failed read 1198 requests. 1200 Discontinuities in this counter can be detected by 1201 monitoring the applOpenChannelOpenTime value for this 1202 entry." 1203 ::= { applOpenChannelEntry 7 } 1205 applOpenChannelBytesRead OBJECT-TYPE 1206 SYNTAX Counter64 1207 UNITS "bytes" 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "This attribute reports the number of bytes read from 1212 this channel. Only bytes successfully read are included 1213 in this count. 1215 Discontinuities in this counter can be detected by 1216 monitoring the applOpenChannelOpenTime value for this 1217 entry." 1218 ::= { applOpenChannelEntry 8 } 1220 applOpenChannelBytesReadLow OBJECT-TYPE 1221 SYNTAX Counter32 1222 UNITS "bytes" 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1226 "This attribute corresponds to the low thirty-two bits 1227 of applOpenChannelBytesRead. 1229 Discontinuities in this counter can be detected by 1230 monitoring the applOpenChannelOpenTime value for this 1231 entry." 1232 ::= { applOpenChannelEntry 9 } 1234 applOpenChannelLastReadTime OBJECT-TYPE 1235 SYNTAX DateAndTime 1236 MAX-ACCESS read-only 1237 STATUS current 1238 DESCRIPTION 1239 "This attribute reports the time of the most recent read 1240 request made by this entity, regardless of completion 1241 status, for this open channel. 1243 If no read requests have been made the value of this 1244 attribute shall be '0000000000000000'H " 1245 DEFVAL { '0000000000000000'H } 1246 ::= { applOpenChannelEntry 10 } 1248 applOpenChannelWriteRequests OBJECT-TYPE 1249 SYNTAX Counter64 1250 UNITS "write requests" 1251 MAX-ACCESS read-only 1252 STATUS current 1253 DESCRIPTION 1254 "This attribute reports the number of write requests for 1255 this channel made by this entity. All write requests 1256 for this channel, regardless of completion status, are 1257 included in this count. 1259 Write requests are counted in terms of system calls, 1260 rather than API calls. 1262 Discontinuities in this counter can be detected by 1263 monitoring the applOpenChannelOpenTime value for this 1264 entry." 1265 ::= { applOpenChannelEntry 11 } 1267 applOpenChannelWriteRequestsLow OBJECT-TYPE 1268 SYNTAX Counter32 1269 UNITS "write requests" 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "This attribute corresponds to the low thirty-two bits 1274 of applOpenChannelWriteRequests. 1276 Discontinuities in this counter can be detected 1277 by monitoring the applOpenChannelOpenTime value for 1278 this entry." 1279 ::= { applOpenChannelEntry 12 } 1281 applOpenChannelWriteFailures OBJECT-TYPE 1282 SYNTAX Counter32 1283 UNITS "failed write requests" 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "This attribute reports the number of failed write 1288 requests. 1290 Discontinuities in this counter can be detected 1291 by monitoring the applOpenChannelOpenTime value for 1292 this entry." 1293 ::= { applOpenChannelEntry 13 } 1295 applOpenChannelBytesWritten OBJECT-TYPE 1296 SYNTAX Counter64 1297 UNITS "bytes" 1298 MAX-ACCESS read-only 1299 STATUS current 1300 DESCRIPTION 1301 "This attribute reports the number of bytes written to 1302 this channel. Only bytes successfully written (without 1303 errors reported by the system to the API in use by the 1304 application) are included in this count. 1306 Discontinuities in this counter can be detected by 1307 monitoring the applOpenChannelOpenTime value for this 1308 entry." 1309 ::= { applOpenChannelEntry 14 } 1311 applOpenChannelBytesWrittenLow OBJECT-TYPE 1312 SYNTAX Counter32 1313 UNITS "bytes" 1314 MAX-ACCESS read-only 1315 STATUS current 1316 DESCRIPTION 1317 "This attribute corresponds to the low thirty-two bits 1318 of applOpenChannelBytesWritten. 1320 Discontinuities in this counter can be detected by 1321 monitoring the applOpenChannelOpenTime value for this 1322 entry." 1323 ::= { applOpenChannelEntry 15 } 1325 applOpenChannelLastWriteTime OBJECT-TYPE 1326 SYNTAX DateAndTime 1327 MAX-ACCESS read-only 1328 STATUS current 1329 DESCRIPTION 1330 "This attribute reports the time of the most recent write 1331 request made by this running application element or 1332 service instance, regardless of completion status, for 1333 this open channel. 1335 If no write requests have been made, the value 1336 of this attribute shall be '0000000000000000'H " 1337 DEFVAL { '0000000000000000'H } 1338 ::= { applOpenChannelEntry 16 } 1340 -- **************************************************************** 1341 -- 1342 -- applOpenFileTable - Table of Open Files 1343 -- 1344 -- **************************************************************** 1346 applOpenFileTable OBJECT-TYPE 1347 SYNTAX SEQUENCE OF ApplOpenFileEntry 1348 MAX-ACCESS not-accessible 1349 STATUS current 1350 DESCRIPTION 1351 "The applOpenFileTable reports information on open files 1352 for service instances or application elements. This 1353 table is indexed by applElmtOrSvc and applElmtOrSvcId, 1354 effectively grouping all entries for a given running 1355 service instance or application element together, and 1356 by applOpenChannelIndex, uniquely identifying an open 1357 channel (and, consequently, a file) within the context 1358 of a particular service instance or application element. 1360 Elements in this table correspond to elements in the 1361 applOpenChannelTable that represent files. For rows in 1362 the applOpenChannelTable that do not represent files, 1363 corresponding rows in this table will not exist." 1364 ::= { applChannelGroup 2 } 1366 applOpenFileEntry OBJECT-TYPE 1367 SYNTAX ApplOpenFileEntry 1368 MAX-ACCESS not-accessible 1369 STATUS current 1370 DESCRIPTION 1371 "An applOpenFileEntry indicates that a file has been 1372 opened by this running application element and is 1373 still open. Note that if a file has been opened 1374 multiple times, even by the same process, it will have 1375 multiple entries." 1376 INDEX { applElmtOrSvc, applElmtOrSvcId, 1377 applOpenChannelIndex } 1378 ::= { applOpenFileTable 1 } 1380 ApplOpenFileEntry ::= SEQUENCE 1381 { 1382 applOpenFileName LongUtf8String, 1383 applOpenFileSizeHigh Unsigned32, 1384 applOpenFileSizeLow Unsigned32, 1385 applOpenFileMode INTEGER 1386 } 1388 applOpenFileName OBJECT-TYPE 1389 SYNTAX LongUtf8String 1390 MAX-ACCESS read-only 1391 STATUS current 1392 DESCRIPTION 1393 "This attribute reports the name of this open file. 1394 Wherever practical, a fully qualified path name should 1395 be reported. 1397 The values 'stdin', 'stdout', and 'stderr' are reserved 1398 in accordance with common usage when the fully qualified 1399 path name cannot be determined." 1400 ::= { applOpenFileEntry 1 } 1402 applOpenFileSizeHigh OBJECT-TYPE 1403 SYNTAX Unsigned32 1404 UNITS "2^32 byte blocks" 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "This file's current size in 2^32 byte blocks. 1410 For example, for a file with a total size of 4,294,967,296 1411 bytes, this attribute would have a value of 1; for a file 1412 with a total size of 4,294,967,295 bytes this attribute's 1413 value would be 0." 1414 ::= { applOpenFileEntry 2 } 1416 applOpenFileSizeLow OBJECT-TYPE 1417 SYNTAX Unsigned32 1418 UNITS "bytes" 1419 MAX-ACCESS read-only 1420 STATUS current 1421 DESCRIPTION 1422 "This file's current size modulo 2^32 bytes. 1424 For example, for a file with a total size of 1425 4,294,967,296 bytes this attribute would have a value 1426 of 0; for a file with a total size of 4,294,967,295 1427 bytes this attribute's value would be 4,294,967,295." 1429 ::= { applOpenFileEntry 3 } 1431 applOpenFileMode OBJECT-TYPE 1432 SYNTAX INTEGER { read(1), 1433 write(2), 1434 readWrite(3) } 1435 MAX-ACCESS read-only 1436 STATUS current 1437 DESCRIPTION 1438 "This attribute reports the current mode of this file from 1439 the perspective of this running application element. 1441 These values have the following meanings: 1443 read(1) - file opened for reading only 1444 write(2) - file opened for writing only 1445 readWrite(3) - file opened for read and write. 1447 These values correspond to the POSIX/ANSI C library 1448 function fopen() 'type' parameter, using the following 1449 mappings: 1451 r -> read(1) 1452 w -> write(2) 1453 a -> write(2) 1454 + -> readWrite(3) 1455 " 1456 ::= { applOpenFileEntry 4 } 1458 -- **************************************************************** 1459 -- 1460 -- applOpenConnectionTable - Open Connection Table 1461 -- 1462 -- **************************************************************** 1464 applOpenConnectionTable OBJECT-TYPE 1465 SYNTAX SEQUENCE OF ApplOpenConnectionEntry 1466 MAX-ACCESS not-accessible 1467 STATUS current 1468 DESCRIPTION 1469 "The applOpenConnectionTable provides information about 1470 open and listening connections from the perspective 1471 of a running application element or service instance. 1472 Entries in this table are indexed by applElmtOrSvc, 1473 applElmtOrSvcID, and by applOpenChannelIndex, which 1474 serves to uniquely identify each connection in the 1475 context of a service instance or running application 1476 element. 1478 For each row in this table, a corresponding row will 1479 exist in the applOpenChannel table. For rows in the 1480 applOpenChannelTable which do not represent open or 1481 listening connections, no corresponding rows will exist 1482 in this table." 1483 ::= { applChannelGroup 3 } 1485 applOpenConnectionEntry OBJECT-TYPE 1486 SYNTAX ApplOpenConnectionEntry 1487 MAX-ACCESS not-accessible 1488 STATUS current 1489 DESCRIPTION 1490 "An applOpenConnectionEntry indicates that a running 1491 application element or service instance has an open 1492 connection. The entry has information describing that 1493 connection. 1495 In the case of a TCP transport, the element 1496 applOpenConnectionNearEndAddr and that row's 1497 applOpenConnectionFarEndAddr would correspond 1498 to a tcpConnEntry. For a UDP transport, a 1499 similar relationship exists with respect to 1500 a udpEntry." 1501 INDEX { applElmtOrSvc, applElmtOrSvcId, 1502 applOpenChannelIndex } 1503 ::= { applOpenConnectionTable 1 } 1505 ApplOpenConnectionEntry ::= SEQUENCE 1506 { 1507 applOpenConnectionTransport TDomain, 1508 applOpenConnectionNearEndAddr ApplTAddress, 1509 applOpenConnectionNearEndpoint SnmpAdminString, 1510 applOpenConnectionFarEndAddr ApplTAddress, 1511 applOpenConnectionFarEndpoint SnmpAdminString, 1512 applOpenConnectionApplication SnmpAdminString 1513 } 1515 applOpenConnectionTransport OBJECT-TYPE 1516 SYNTAX TDomain 1517 MAX-ACCESS read-only 1518 STATUS current 1519 DESCRIPTION 1520 "The applOpenConnectionTransport attribute identifies the 1521 transport protocol in use for this connection. If it is 1522 not practical to determine the underlying transport, this 1523 attribute's value shall have a value of {0 0}." 1524 DEFVAL { zeroDotZero } 1525 ::= { applOpenConnectionEntry 1 } 1527 applOpenConnectionNearEndAddr OBJECT-TYPE 1528 SYNTAX ApplTAddress 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "The applOpenConnectionNearEndAddr attribute reports the 1533 transport address and port information for the near end 1534 of this connection. 1536 If the value is not known, the value has a length 1537 of zero." 1538 DEFVAL { "" } 1539 ::= { applOpenConnectionEntry 2 } 1541 applOpenConnectionNearEndpoint OBJECT-TYPE 1542 SYNTAX SnmpAdminString 1543 MAX-ACCESS read-only 1544 STATUS current 1545 DESCRIPTION 1546 "The applOpenConnectionNearEndpoint attribute reports the 1547 fully-qualified domain name and port information for the 1548 near end of this connection. 1550 The format of this attribute for TCP and UDP-based 1551 protocols is the fully-qualified domain name immediately 1552 followed by a colon which is immediately followed by 1553 the decimal representation of the port number. 1555 If the value is not known, the value has a length 1556 of zero." 1557 DEFVAL { "" } 1558 ::= { applOpenConnectionEntry 3 } 1560 applOpenConnectionFarEndAddr OBJECT-TYPE 1561 SYNTAX ApplTAddress 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "The applOpenConnectionFarEndAddr attribute reports the 1566 transport address and port information for the far end 1567 of this connection. 1569 If not known, as in the case of a connectionless 1570 transport, the value of this attribute shall be a 1571 zero-length string." 1572 DEFVAL { "" } 1573 ::= { applOpenConnectionEntry 4 } 1575 applOpenConnectionFarEndpoint OBJECT-TYPE 1576 SYNTAX SnmpAdminString 1577 MAX-ACCESS read-only 1578 STATUS current 1579 DESCRIPTION 1580 "The applOpenConnectionFarEndpoint attribute reports 1581 the fully-qualified domain name and port information 1582 for the far end of this connection. 1584 The format of this attribute for TCP and UDP-based 1585 protocols is the fully-qualified domain name immediately 1586 followed by a colon which is immediately followed by 1587 the decimal representation of the port number. 1589 If not known, as in the case of a connectionless 1590 transport, the value of this attribute shall be a 1591 zero-length string." 1592 DEFVAL { "" } 1593 ::= { applOpenConnectionEntry 5 } 1595 applOpenConnectionApplication OBJECT-TYPE 1596 SYNTAX SnmpAdminString 1597 MAX-ACCESS read-only 1598 STATUS current 1599 DESCRIPTION 1600 "The applOpenConnectionApplication attribute identifies 1601 the application layer protocol in use. If not known, 1602 the value of this attribute shall be a zero-length 1603 string. 1605 When possible, protocol names should be those used in 1606 the 'ASSIGNED NUMBERS' [13]. For example, an SMTP mail 1607 server would use 'SMTP'." 1608 DEFVAL { "" } 1609 ::= { applOpenConnectionEntry 6 } 1611 -- **************************************************************** 1612 -- 1613 -- applTransactionStreamTable - common 1614 -- information for transaction stream monitoring 1615 -- 1616 -- **************************************************************** 1618 applTransactionStreamTable OBJECT-TYPE 1619 SYNTAX SEQUENCE OF ApplTransactionStreamEntry 1620 MAX-ACCESS not-accessible 1621 STATUS current 1622 DESCRIPTION 1623 "The applTransactionStreamTable contains common 1624 information for transaction statistic accumulation." 1625 ::= { applChannelGroup 4 } 1627 applTransactionStreamEntry OBJECT-TYPE 1628 SYNTAX ApplTransactionStreamEntry 1629 MAX-ACCESS not-accessible 1630 STATUS current 1631 DESCRIPTION 1632 "An applTransactionStreamEntry contains information for 1633 a single transaction stream. A transaction stream 1634 can be a network connection, file, or other source 1635 of transactions." 1636 INDEX { applElmtOrSvc, applElmtOrSvcId, 1637 applOpenChannelIndex } 1638 ::= { applTransactionStreamTable 1 } 1640 ApplTransactionStreamEntry ::= SEQUENCE { 1641 applTransactStreamDescr SnmpAdminString, 1642 applTransactStreamUnitOfWork SnmpAdminString, 1643 applTransactStreamInvokes Counter64, 1644 applTransactStreamInvokesLow Counter32, 1645 applTransactStreamInvCumTimes Counter32, 1646 applTransactStreamInvRspTimes Counter32, 1647 applTransactStreamPerforms Counter64, 1648 applTransactStreamPerformsLow Counter32, 1649 applTransactStreamPrfCumTimes Counter32, 1650 applTransactStreamPrfRspTimes Counter32 } 1652 applTransactStreamDescr OBJECT-TYPE 1653 SYNTAX SnmpAdminString 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION 1657 "The applTransactStreamDescr attribute provides a 1658 human-readable description of this transaction stream. 1660 If no descriptive information is available, this 1661 attribute's value shall be a zero-length string." 1662 DEFVAL { "" } 1663 ::= { applTransactionStreamEntry 1 } 1665 applTransactStreamUnitOfWork OBJECT-TYPE 1666 SYNTAX SnmpAdminString 1667 MAX-ACCESS read-only 1668 STATUS current 1669 DESCRIPTION 1670 "The applTransactStreamUnitOfWork attribute provides a 1671 human-readable definition of what the unit of work is 1672 for this transaction stream. 1674 If no descriptive information is available, this 1675 attribute's value shall be a zero-length string." 1676 DEFVAL { "" } 1677 ::= { applTransactionStreamEntry 2 } 1679 applTransactStreamInvokes OBJECT-TYPE 1680 SYNTAX Counter64 1681 UNITS "transactions" 1682 MAX-ACCESS read-only 1683 STATUS current 1684 DESCRIPTION 1685 "Cumulative count of requests / invocations issued. 1687 Discontinuities in this counter can be detected 1688 by monitoring the corresponding instance of 1689 applOpenChannelOpenTime." 1690 ::= { applTransactionStreamEntry 3 } 1692 applTransactStreamInvokesLow OBJECT-TYPE 1693 SYNTAX Counter32 1694 UNITS "transactions" 1695 MAX-ACCESS read-only 1696 STATUS current 1697 DESCRIPTION 1698 "This counter corresponds to the low thirty-two 1699 bits of applTransactStreamInvokes. 1701 Discontinuities in this counter can be detected 1702 by monitoring the corresponding instance of 1703 applOpenChannelOpenTime." 1704 ::= { applTransactionStreamEntry 4 } 1706 applTransactStreamInvCumTimes OBJECT-TYPE 1707 SYNTAX Counter32 1708 UNITS "milliseconds" 1709 MAX-ACCESS read-only 1710 STATUS current 1711 DESCRIPTION 1712 "The applTransactStreamInvCumTimes attribute reports the 1713 cumulative sum of the lengths of the intervals measured 1714 between the transmission of requests and the receipt of 1715 (the first of) the corresponding response(s). 1717 Discontinuities in this counter can be detected 1718 by monitoring the corresponding instance of 1719 applOpenChannelOpenTime." 1720 ::= { applTransactionStreamEntry 5 } 1722 applTransactStreamInvRspTimes OBJECT-TYPE 1723 SYNTAX Counter32 1724 UNITS "milliseconds" 1725 MAX-ACCESS read-only 1726 STATUS current 1727 DESCRIPTION 1728 "The applTransactStreamInvRspTimes attribute reports the 1729 cumulative sum of the lengths of the intervals measured 1730 between the receipt of the first and last of multiple 1731 responses to a request. 1733 For transaction streams which do not permit multiple 1734 responses to a single request, this attribute will be 1735 constant. 1737 Discontinuities in this counter can be detected 1738 by monitoring the corresponding instance of 1739 applOpenChannelOpenTime." 1740 ::= { applTransactionStreamEntry 6 } 1742 applTransactStreamPerforms OBJECT-TYPE 1743 SYNTAX Counter64 1744 UNITS "transactions" 1745 MAX-ACCESS read-only 1746 STATUS current 1747 DESCRIPTION 1748 "Cumulative count of transactions performed. 1750 Discontinuities in this counter can be detected 1751 by monitoring the corresponding instance of 1752 applOpenChannelOpenTime." 1753 ::= { applTransactionStreamEntry 7 } 1755 applTransactStreamPerformsLow OBJECT-TYPE 1756 SYNTAX Counter32 1757 UNITS "transactions" 1758 MAX-ACCESS read-only 1759 STATUS current 1760 DESCRIPTION 1761 "This counter reports the low thirty-two bits of 1762 applTransactStreamPerforms. 1764 Discontinuities in this counter can be detected 1765 by monitoring the corresponding instance of 1766 applOpenChannelOpenTime." 1767 ::= { applTransactionStreamEntry 8 } 1769 applTransactStreamPrfCumTimes OBJECT-TYPE 1770 SYNTAX Counter32 1771 UNITS "milliseconds" 1772 MAX-ACCESS read-only 1773 STATUS current 1774 DESCRIPTION 1775 "The applTransactStreamPrfCumTimes attribute reports the 1776 cumulative sum of the interval lengths measured between 1777 receipt of requests and the transmission of the 1778 corresponding responses. 1780 Discontinuities in this counter can be detected 1781 by monitoring the corresponding instance of 1782 applOpenChannelOpenTime." 1783 ::= { applTransactionStreamEntry 9 } 1785 applTransactStreamPrfRspTimes OBJECT-TYPE 1786 SYNTAX Counter32 1787 UNITS "milliseconds" 1788 MAX-ACCESS read-only 1789 STATUS current 1790 DESCRIPTION 1791 "For each transaction performed, the elapsed time between 1792 when the first response is enqueued and when the last 1793 response is enqueued is added to this cumulative sum. 1795 For single-response protocols, the value of 1796 applTransactStreamPrfRspTimes will be constant. 1798 Discontinuities in this counter can be detected 1799 by monitoring the corresponding instance of 1800 applOpenChannelOpenTime." 1801 ::= { applTransactionStreamEntry 10 } 1803 -- **************************************************************** 1804 -- 1805 -- applTransactFlowTable 1806 -- 1807 -- **************************************************************** 1809 applTransactFlowTable OBJECT-TYPE 1810 SYNTAX SEQUENCE OF ApplTransactFlowEntry 1811 MAX-ACCESS not-accessible 1812 STATUS current 1813 DESCRIPTION 1814 "The applTransactFlowTable contains entries, organized by 1815 application instance or running application element, 1816 direction of flow, and type (request/response) for each 1817 open transaction stream. 1819 The simple model of a transaction used here looks like 1820 this: 1822 invoker | Request | performer 1823 | - - - - - - > | 1824 | | 1825 | Response | 1826 | < - - - - - - | 1827 | | 1829 Since in some protocols it is possible for an entity 1830 to take on both the invoker and performer roles, 1831 information here is accumulated for transmitted and 1832 received requests, as well as for transmitted and 1833 received responses. Counts are maintained for both 1834 transactions and bytes transferred." 1835 ::= { applChannelGroup 5 } 1837 applTransactFlowEntry OBJECT-TYPE 1838 SYNTAX ApplTransactFlowEntry 1839 MAX-ACCESS not-accessible 1840 STATUS current 1841 DESCRIPTION 1842 "An applTransactFlowEntry reports transaction throughput 1843 information for requests or response in a particular 1844 direction (transmit / receive) for a transaction stream. 1846 Entries in this table correspond to those in the 1847 applTransactionStreamTable with identical values for the 1848 applElmtOrSvc, applElmtOrSvcId, and applOpenChannelIndex. 1850 For all counter objects in one of these entries, 1851 the corresponding (same value for applElmtOrSvc, 1852 applElmtOrSvcId, and applOpenChannelIndex) 1853 applOpenChannelOpenTime object serves as a discontinuity 1854 indicator. " 1855 INDEX { applElmtOrSvc, 1856 applElmtOrSvcId, 1857 applOpenChannelIndex, 1858 applTransactFlowDirection, 1859 applTransactFlowReqRsp } 1860 ::= { applTransactFlowTable 1 } 1862 ApplTransactFlowEntry ::= SEQUENCE { 1863 applTransactFlowDirection INTEGER, 1864 applTransactFlowReqRsp INTEGER, 1865 applTransactFlowTrans Counter64, 1866 applTransactFlowTransLow Counter32, 1867 applTransactFlowBytes Counter64, 1868 applTransactFlowBytesLow Counter32, 1869 applTransactFlowTime DateAndTime } 1871 applTransactFlowDirection OBJECT-TYPE 1872 SYNTAX INTEGER { transmit(1), 1873 receive(2) } 1874 MAX-ACCESS not-accessible 1875 STATUS current 1876 DESCRIPTION 1877 "The applTransactFlowDirection index serves to identify 1878 an entry as containing information pertaining to the 1879 transmit (1) or receive (2) flow of a transaction 1880 stream." 1881 ::= { applTransactFlowEntry 1 } 1883 applTransactFlowReqRsp OBJECT-TYPE 1884 SYNTAX INTEGER { request(1), 1885 response(2) } 1886 MAX-ACCESS not-accessible 1887 STATUS current 1888 DESCRIPTION 1889 "The value of the applTransactFlowReqRsp index indicates 1890 whether this entry contains information on requests 1891 (1), or responses (2)." 1892 ::= { applTransactFlowEntry 2 } 1894 applTransactFlowTrans OBJECT-TYPE 1895 SYNTAX Counter64 1896 UNITS "transactions" 1897 MAX-ACCESS read-only 1898 STATUS current 1899 DESCRIPTION 1900 "The applTransactFlowTrans attribute reports the number 1901 of request/response transactions (as indicated by 1902 the applTransactFlowReqRsp index) received/generated 1903 (as indicated by the applTransactFlowDirection index) 1904 that this service instance or running application 1905 element has processed for this transaction stream. 1907 Discontinuities in this counter can be detected 1908 by monitoring the corresponding instance of 1909 applOpenChannelOpenTime." 1910 ::= { applTransactFlowEntry 3 } 1912 applTransactFlowTransLow OBJECT-TYPE 1913 SYNTAX Counter32 1914 UNITS "transactions" 1915 MAX-ACCESS read-only 1916 STATUS current 1917 DESCRIPTION 1918 "This attribute corresponds to the low thirty-two 1919 bits of applTransactFlowTrans. 1921 Discontinuities in this counter can be detected 1922 by monitoring the corresponding instance of 1923 applOpenChannelOpenTime." 1924 ::= { applTransactFlowEntry 4 } 1926 applTransactFlowBytes OBJECT-TYPE 1927 SYNTAX Counter64 1928 UNITS "bytes" 1929 MAX-ACCESS read-only 1930 STATUS current 1931 DESCRIPTION 1932 "The applTransactFlowBytes attribute reports the number 1933 of request/response (as indicated by the 1934 applTransactFlowReqRsp index) bytes received/generated 1935 (as indicated by the applTransactFlowDirection index) 1936 handled by this application element or service instance 1937 on this transaction stream. 1939 All application layer bytes are included in this count, 1940 including any application layer wrappers, headers, or 1941 other overhead. 1943 Discontinuities in this counter can be detected 1944 by monitoring the corresponding instance of 1945 applOpenChannelOpenTime." 1946 ::= { applTransactFlowEntry 5 } 1948 applTransactFlowBytesLow OBJECT-TYPE 1949 SYNTAX Counter32 1950 UNITS "bytes" 1951 MAX-ACCESS read-only 1952 STATUS current 1953 DESCRIPTION 1954 "This attribute corresponds to the low thirty-two 1955 bits of applTransactFlowBytes. 1957 Discontinuities in this counter can be detected 1958 by monitoring the corresponding instance of 1959 applOpenChannelOpenTime." 1960 ::= { applTransactFlowEntry 6 } 1962 applTransactFlowTime OBJECT-TYPE 1963 SYNTAX DateAndTime 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "The applTransactFlowTime attribute records the time of 1968 the processing (receipt or transmission as indicated 1969 by the applTransactFlowDirection index) by this 1970 running application element or service instance of 1971 the most recent request/response (as indicated by 1972 the applTransactFlowReqRsp index) on this transaction 1973 stream. 1975 If no requests/responses been received/transmitted by 1976 this entity over this transaction stream, the value 1977 of this attribute shall be '0000000000000000'H " 1978 DEFVAL { '0000000000000000'H } 1979 ::= { applTransactFlowEntry 7 } 1981 -- **************************************************************** 1982 -- 1983 -- applTransactKindTable - transaction statistics broken down 1984 -- according to the kinds of transactions in each direction 1985 -- for a transaction stream. 1986 -- 1987 -- **************************************************************** 1989 applTransactKindTable OBJECT-TYPE 1990 SYNTAX SEQUENCE OF ApplTransactKindEntry 1991 MAX-ACCESS not-accessible 1992 STATUS current 1993 DESCRIPTION 1994 "The applTransactKindTable provides transaction statistics 1995 broken down by kinds of transaction. The definition of 1996 the kinds of transactions is specific to the application 1997 protocol in use, and may be documented in the form of an 1998 applicability statement. " 1999 ::= { applChannelGroup 6 } 2001 applTransactKindEntry OBJECT-TYPE 2002 SYNTAX ApplTransactKindEntry 2003 MAX-ACCESS not-accessible 2004 STATUS current 2005 DESCRIPTION 2006 "An applTransactKindEntry reports information for a 2007 specific service instance or running application 2008 element's use of a specific transaction stream in 2009 a particular direction in requests or responses 2010 (as indicated by the applTransactFlowReqRsp index) 2011 broken down by transaction kind, as indicated by the 2012 applTransactKind index. 2014 Discontinuities in any of the counters in an entry can 2015 be detected by monitoring the corresponding instance of 2016 applOpenChannelOpenTime." 2018 INDEX { applElmtOrSvc, 2019 applElmtOrSvcId, 2020 applOpenChannelIndex, 2021 applTransactFlowDirection, 2022 applTransactFlowReqRsp, 2023 applTransactKind } 2024 ::= { applTransactKindTable 1 } 2026 ApplTransactKindEntry ::= SEQUENCE 2027 { 2028 applTransactKind SnmpAdminString, 2029 applTransactKindTrans Counter64, 2030 applTransactKindTransLow Counter32, 2031 applTransactKindBytes Counter64, 2032 applTransactKindBytesLow Counter32, 2033 applTransactKindTime DateAndTime 2034 } 2036 applTransactKind OBJECT-TYPE 2037 SYNTAX SnmpAdminString (SIZE (1 .. 32)) 2038 MAX-ACCESS not-accessible 2039 STATUS current 2040 DESCRIPTION 2041 "The applTransactKind index is the human-readable 2042 identifier for a particular transaction kind within 2043 the context of an application protocol. The values 2044 to be used for a particular protocol may be identified 2045 in an applicability statement." 2046 ::= { applTransactKindEntry 1 } 2048 applTransactKindTrans OBJECT-TYPE 2049 SYNTAX Counter64 2050 UNITS "transactions" 2051 MAX-ACCESS read-only 2052 STATUS current 2053 DESCRIPTION 2054 "The applTransactKindTrans attribute reports the number 2055 of request/response (as indicated by the 2056 applTransactFlowReqRsp index) transactions 2057 received/generated (as indicated by the 2058 applTransactFlowDirection index) handled by this 2059 application instance or application element on this 2060 transaction stream for this transaction kind. 2062 Discontinuities in this counter can be detected 2063 by monitoring the corresponding instance of 2064 applOpenChannelOpenTime." 2065 ::= { applTransactKindEntry 2 } 2067 applTransactKindTransLow OBJECT-TYPE 2068 SYNTAX Counter32 2069 UNITS "transactions" 2070 MAX-ACCESS read-only 2071 STATUS current 2072 DESCRIPTION 2073 "The applTransactKindTransLow attribute reports 2074 the low thirty-two bits of applTransactKindTrans. 2076 Discontinuities in this counter can be detected 2077 by monitoring the corresponding instance of 2078 applOpenChannelOpenTime." 2079 ::= { applTransactKindEntry 3 } 2081 applTransactKindBytes OBJECT-TYPE 2082 SYNTAX Counter64 2083 UNITS "bytes" 2084 MAX-ACCESS read-only 2085 STATUS current 2086 DESCRIPTION 2087 "The applTransactKindBytes attribute reports the number 2088 of request/response (as indicated by the 2089 applTransactFlowReqRsp index) bytes received/generated 2090 (as indicated by the applTransactFlowDirection index) 2091 handled by this application element on this transaction 2092 stream for this transaction kind. 2094 All application layer bytes are included in this count, 2095 including any application layer wrappers, headers, or 2096 other overhead. 2098 Discontinuities in this counter can be detected 2099 by monitoring the corresponding instance of 2100 applOpenChannelOpenTime." 2101 ::= { applTransactKindEntry 4 } 2103 applTransactKindBytesLow OBJECT-TYPE 2104 SYNTAX Counter32 2105 UNITS "bytes" 2106 MAX-ACCESS read-only 2107 STATUS current 2108 DESCRIPTION 2109 "The applTransactKindBytesLow attribute corresponds 2110 to the low thirty-two bits of applTransactKindBytes. 2112 Discontinuities in this counter can be detected 2113 by monitoring the corresponding instance of 2114 applOpenChannelOpenTime." 2115 ::= { applTransactKindEntry 5 } 2117 applTransactKindTime OBJECT-TYPE 2118 SYNTAX DateAndTime 2119 MAX-ACCESS read-only 2120 STATUS current 2121 DESCRIPTION 2122 "The applTransactKindTime attribute records the time of 2123 the processing (receipt or transmission as indicated 2124 by the applTransactFlowDirection index) by this 2125 running application element or service instance of 2126 the most recent request/response (as indicated by 2127 the applTransactFlowReqRsp index) of this kind of 2128 transaction on this transaction stream. 2130 If no requests/responses of this kind been 2131 received/transmitted by this running application element 2132 or service instance over this transaction stream, the 2133 value of this attribute shall be '0000000000000000'H " 2134 DEFVAL { '0000000000000000'H } 2135 ::= { applTransactKindEntry 6 } 2137 -- **************************************************************** 2138 -- 2139 -- applPastChannelGroup - logged information on former channels. 2140 -- These tables control the collection of channel history 2141 -- information and represent the accumulated historical data. 2142 -- 2143 -- **************************************************************** 2145 applPastChannelControlTable OBJECT-TYPE 2146 SYNTAX SEQUENCE OF ApplPastChannelControlEntry 2147 MAX-ACCESS not-accessible 2148 STATUS current 2149 DESCRIPTION 2150 "The applPastChannelControlTable controls the 2151 accumulation of history information about channels 2152 from the perspective of service instances and running 2153 application elements. Entries in this table are indexed 2154 by applElmtOrSvc and applElmtOrSvcId, giving control 2155 of channel history accumulation at the level of each 2156 service instance and running application element." 2157 ::= { applPastChannelGroup 1 } 2159 applPastChannelControlEntry OBJECT-TYPE 2160 SYNTAX ApplPastChannelControlEntry 2161 MAX-ACCESS not-accessible 2162 STATUS current 2163 DESCRIPTION 2164 "An applPastChannelControlEntry provides the ability 2165 to control the retention of channel history information 2166 by service instances and running application elements." 2167 INDEX { applElmtOrSvc, applElmtOrSvcId } 2168 ::= { applPastChannelControlTable 1 } 2170 ApplPastChannelControlEntry ::= SEQUENCE 2171 { 2172 applPastChannelControlCollect INTEGER, 2173 applPastChannelControlMaxRows Unsigned32, 2174 applPastChannelControlTimeLimit Unsigned32, 2175 applPastChannelControlRemItems Counter32 2176 } 2178 applPastChannelControlCollect OBJECT-TYPE 2179 SYNTAX INTEGER { enabled (1), 2180 frozen (2), 2181 disabled (3) } 2182 MAX-ACCESS read-write 2183 STATUS current 2184 DESCRIPTION 2185 "When the value of applPastChannelControlCollect is 2186 'enabled', each time the corresponding running 2187 application element or service instance closes 2188 an open channel a new entry will be added to the 2189 applPastChannelTable. 2191 When the value of applPastChannelControlCollect 2192 is 'frozen', no new entries are added to the 2193 applPastChannelTable for this running application 2194 element or service instance, and old entries are not 2195 aged out. 2197 When the value of applPastChannelControlCollect 2198 is 'disabled', all entries are removed from 2199 applPastChannelTable for this running application or 2200 service instance, and no new entries are added." 2201 DEFVAL { enabled } 2202 ::= { applPastChannelControlEntry 1 } 2204 applPastChannelControlMaxRows OBJECT-TYPE 2205 SYNTAX Unsigned32 2206 UNITS "channel history entries" 2207 MAX-ACCESS read-write 2208 STATUS current 2209 DESCRIPTION 2210 "The maximum number of entries allowed in the 2211 applPastChannelTable for this running application element 2212 or service instance. Once the number of rows for this 2213 running application element or service instance in the 2214 applPastChannelTable reaches this value, when new 2215 entries are to be added the management subsystem will 2216 make room for them by removing the oldest entries. 2217 Entries will be removed on the basis of oldest 2218 applPastChannelCloseTime value first." 2219 DEFVAL { 500 } 2220 ::= { applPastChannelControlEntry 2 } 2222 applPastChannelControlTimeLimit OBJECT-TYPE 2223 SYNTAX Unsigned32 2224 UNITS "seconds" 2225 MAX-ACCESS read-write 2226 STATUS current 2227 DESCRIPTION 2228 "The maximum time in seconds which an entry for this 2229 running application element or service instance 2230 may exist in the applPastChannelTable before it 2231 is removed. Any entry that is older than this value 2232 will be removed (aged out) from the table, unless the 2233 applPastChannelControlCollect is set to 'frozen'. 2235 Note that an entry may be aged out prior to reaching 2236 this time limit if it is the oldest entry in the table 2237 and must be removed to make space for a new entry so 2238 as to not exceed applPastChannelControlMaxRows, or if the 2239 applPastChannelControlCollect is set to 'disabled'." 2240 DEFVAL { 7200 } 2241 ::= { applPastChannelControlEntry 3 } 2243 applPastChannelControlRemItems OBJECT-TYPE 2244 SYNTAX Counter32 2245 UNITS "channel history entries" 2246 MAX-ACCESS read-only 2247 STATUS current 2248 DESCRIPTION 2249 "The applPastChannelControlRemItems attribute reports the 2250 number of applPastChannelControlTable entries for this 2251 running application element or service instance that 2252 were deleted in order to make room for new history 2253 entries. 2255 This count does NOT include entries deleted for the 2256 following reasons: 2257 - the corresponding applPastChannelControlCollect 2258 attribute has been set to 'disabled' 2260 - the entry has been in the table longer that the 2261 time limit indicated by the corresponding 2262 applPastChannelControlTimeLimit. 2263 " 2264 ::= { applPastChannelControlEntry 4 } 2266 -- **************************************************************** 2267 -- 2268 -- applPastChannelTable - Table of former channels 2269 -- 2270 -- **************************************************************** 2272 applPastChannelTable OBJECT-TYPE 2273 SYNTAX SEQUENCE OF ApplPastChannelEntry 2274 MAX-ACCESS not-accessible 2275 STATUS current 2276 DESCRIPTION 2277 "The applPastChannelTable provides history information 2278 about channels from the perspective of running 2279 application elements and service instances. 2281 Entries in this table are indexed by applElmtOrSvc, 2282 applElmtOrSvcId, and by applPastChannelIndex, which 2283 serves to uniquely identify each former channel in the 2284 context of a running application element or service 2285 instance. 2287 Note that the value of applPastChannelIndex is 2288 independent of the value applOpenChannelIndex had when 2289 this channel was open. 2291 Entries for closed channels for a given running 2292 application element or service instance can 2293 be added to this table only if its entry in the 2294 applPastChannelControlTable has the value 'enabled' 2295 for the attribute applPastChannelControlCollect. 2297 Entries for closed channels are removed under the 2298 following circumstances: 2300 - the running application element or service 2301 instance no longer exists 2303 - the corresponding applPastChannelControlCollect 2304 attribute has been set to 'disabled' 2306 - the entry has been in the table longer that the 2307 time limit indicated by the corresponding 2308 applPastChannelControlTimeLimit and the value of 2309 applPastChannelControlCollect is not 'frozen' 2311 - this is the oldest entry for the running 2312 application element or service instance in 2313 question and the addition of a new element would 2314 otherwise cause applPastChannelControlMaxRows to 2315 be exceeded for this running application element 2316 or service instance. 2318 - a value of applPastChannelIndex has been re-used. 2319 Note that under normal circumstances, this is 2320 unlikely. 2322 Removal/replacement of an entry under the 2323 last two conditions causes the corresponding 2324 applPastChannelControlRemItems to be incremented." 2325 ::= { applPastChannelGroup 2 } 2327 applPastChannelEntry OBJECT-TYPE 2328 SYNTAX ApplPastChannelEntry 2329 MAX-ACCESS not-accessible 2330 STATUS current 2331 DESCRIPTION 2332 "An applPastChannelEntry indicates that a running 2333 application element or service instance once had an open 2334 channel, which is now closed. The entry has information 2335 describing that channel." 2336 INDEX { applElmtOrSvc, applElmtOrSvcId, 2337 applPastChannelIndex } 2338 ::= { applPastChannelTable 1 } 2340 ApplPastChannelEntry ::= SEQUENCE 2341 { 2342 applPastChannelIndex Unsigned32, 2343 applPastChannelOpenTime DateAndTime, 2344 applPastChannelCloseTime DateAndTime, 2345 applPastChannelReadRequests Unsigned64TC, 2346 applPastChannelReadReqsLow Unsigned32, 2347 applPastChannelReadFailures Unsigned32, 2348 applPastChannelBytesRead Unsigned64TC, 2349 applPastChannelBytesReadLow Unsigned32, 2350 applPastChannelLastReadTime DateAndTime, 2351 applPastChannelWriteRequests Unsigned64TC, 2352 applPastChannelWriteReqsLow Unsigned32, 2353 applPastChannelWriteFailures Unsigned32, 2354 applPastChannelBytesWritten Unsigned64TC, 2355 applPastChannelBytesWritLow Unsigned32, 2356 applPastChannelLastWriteTime DateAndTime 2357 } 2359 applPastChannelIndex OBJECT-TYPE 2360 SYNTAX Unsigned32 (1..'ffffffff'h) 2361 MAX-ACCESS not-accessible 2362 STATUS current 2363 DESCRIPTION 2364 "This attribute serves to uniquely identify this closed 2365 channel in the context of the running application 2366 element or service instance. This attribute has no 2367 other semantics. 2369 Note that the value of applPastChannelIndex is 2370 independent of the value applOpenChannelIndex had when 2371 this channel was active. 2373 In issuing this index value, the implementation must 2374 avoid re-issuing an index value which has already been 2375 assigned to an entry which has not yet been deleted due 2376 to age or space considerations. 2378 The value zero is excluded from the set of permitted 2379 values for this index in order to permit other tables to 2380 possibly represent information that cannot be associated 2381 with a specific entry in this table. " 2382 ::= { applPastChannelEntry 1 } 2384 applPastChannelOpenTime OBJECT-TYPE 2385 SYNTAX DateAndTime 2386 MAX-ACCESS read-only 2387 STATUS current 2388 DESCRIPTION 2389 "This attribute records the time when this channel was 2390 originally opened. Note that this information is quite 2391 different from applOpenChannelOpenTime, which is used 2392 for the detection of counter discontinuities." 2393 ::= { applPastChannelEntry 2 } 2395 applPastChannelCloseTime OBJECT-TYPE 2396 SYNTAX DateAndTime 2397 MAX-ACCESS read-only 2398 STATUS current 2399 DESCRIPTION 2400 "This attribute records the time when this channel 2401 was closed." 2402 ::= { applPastChannelEntry 3 } 2404 applPastChannelReadRequests OBJECT-TYPE 2405 SYNTAX Unsigned64TC 2406 UNITS "read requests" 2407 MAX-ACCESS read-only 2408 STATUS current 2409 DESCRIPTION 2410 "This attribute records the number of read requests for 2411 this channel made by this running application element or 2412 service instance. All read requests for this channel by 2413 this running application element or service instance, 2414 regardless of completion status, are included in this 2415 count. Read requests are counted in terms of system 2416 calls, rather than API calls." 2418 ::= { applPastChannelEntry 4 } 2420 applPastChannelReadReqsLow OBJECT-TYPE 2421 SYNTAX Unsigned32 2422 UNITS "read requests" 2423 MAX-ACCESS read-only 2424 STATUS current 2425 DESCRIPTION 2426 "This attribute corresponds to the low thirty-two bits 2427 of applPastChannelReadRequests." 2428 ::= { applPastChannelEntry 5 } 2430 applPastChannelReadFailures OBJECT-TYPE 2431 SYNTAX Unsigned32 2432 UNITS "failed read requests" 2433 MAX-ACCESS read-only 2434 STATUS current 2435 DESCRIPTION 2436 "This attribute reports the number of failed read 2437 requests." 2438 ::= { applPastChannelEntry 6 } 2440 applPastChannelBytesRead OBJECT-TYPE 2441 SYNTAX Unsigned64TC 2442 UNITS "bytes" 2443 MAX-ACCESS read-only 2444 STATUS current 2445 DESCRIPTION 2446 "This attribute reports the number of bytes read from this 2447 channel by this running application element or service 2448 instance. Only bytes successfully read are included in 2449 this count. " 2450 ::= { applPastChannelEntry 7 } 2452 applPastChannelBytesReadLow OBJECT-TYPE 2453 SYNTAX Unsigned32 2454 UNITS "bytes" 2455 MAX-ACCESS read-only 2456 STATUS current 2457 DESCRIPTION 2458 "This attribute corresponds to the low thirty-two bits 2459 of applPastChannelBytesRead." 2460 ::= { applPastChannelEntry 8 } 2462 applPastChannelLastReadTime OBJECT-TYPE 2463 SYNTAX DateAndTime 2464 MAX-ACCESS read-only 2465 STATUS current 2466 DESCRIPTION 2467 "This attribute reports the time of the most recent read 2468 request made by this running application element or 2469 service instance regardless of completion status, for 2470 this former channel. 2472 If no read requests have been made , the value of this 2473 attribute shall be '0000000000000000'H " 2474 DEFVAL { '0000000000000000'H } 2475 ::= { applPastChannelEntry 9 } 2477 applPastChannelWriteRequests OBJECT-TYPE 2478 SYNTAX Unsigned64TC 2479 UNITS "write requests" 2480 MAX-ACCESS read-only 2481 STATUS current 2482 DESCRIPTION 2483 "The applPastChannelWriteRequests attribute reports 2484 the number of write requests, regardless of completion 2485 status, made by this running application element or 2486 service instance for this former channel. 2488 Write requests are counted in terms of system calls, 2489 rather than API calls." 2490 ::= { applPastChannelEntry 10 } 2492 applPastChannelWriteReqsLow OBJECT-TYPE 2493 SYNTAX Unsigned32 2494 UNITS "write requests" 2495 MAX-ACCESS read-only 2496 STATUS current 2497 DESCRIPTION 2498 "This attribute corresponds to the low thirty-two 2499 bits of applPastChannelWriteRequests." 2500 ::= { applPastChannelEntry 11 } 2502 applPastChannelWriteFailures OBJECT-TYPE 2503 SYNTAX Unsigned32 2504 UNITS "failed write requests" 2505 MAX-ACCESS read-only 2506 STATUS current 2507 DESCRIPTION 2508 "This attribute reports the number of failed write 2509 requests." 2510 ::= { applPastChannelEntry 12 } 2512 applPastChannelBytesWritten OBJECT-TYPE 2513 SYNTAX Unsigned64TC 2514 UNITS "bytes" 2515 MAX-ACCESS read-only 2516 STATUS current 2517 DESCRIPTION 2518 "This attribute reports the number of bytes written to 2519 this former channel by this running application element 2520 or service instance. Only bytes successfully written 2521 (no errors reported by the API in use by the application) 2522 are included in this count." 2523 ::= { applPastChannelEntry 13 } 2525 applPastChannelBytesWritLow OBJECT-TYPE 2526 SYNTAX Unsigned32 2527 UNITS "bytes" 2528 MAX-ACCESS read-only 2529 STATUS current 2530 DESCRIPTION 2531 "This attribute corresponds to the low thirty-two bits of 2532 applPastChannelBytesWritten." 2533 ::= { applPastChannelEntry 14 } 2535 applPastChannelLastWriteTime OBJECT-TYPE 2536 SYNTAX DateAndTime 2537 MAX-ACCESS read-only 2538 STATUS current 2539 DESCRIPTION 2540 "The applPastChannelLastWriteTime attribute reports 2541 the time of the most recent write request made by 2542 this running application element or service instance, 2543 regardless of completion status, for this former 2544 channel. 2546 If no write requests have been made the value of this 2547 attribute shall be '0000000000000000'H " 2548 DEFVAL { '0000000000000000'H } 2549 ::= { applPastChannelEntry 15 } 2551 -- **************************************************************** 2552 -- 2553 -- applPastFileTable - information specific to former files 2554 -- 2555 -- **************************************************************** 2556 applPastFileTable OBJECT-TYPE 2557 SYNTAX SEQUENCE OF ApplPastFileEntry 2558 MAX-ACCESS not-accessible 2559 STATUS current 2560 DESCRIPTION 2561 "The applPastFileTable supplements the 2562 applPastChannelTable for entries corresponding to 2563 channels which were files. The indexing structure is 2564 identical to applPastChannelTable. An entry exists in 2565 the applPastFileTable only if there is a corresponding 2566 (same index values) entry in the applPastChannelTable 2567 and if the channel was a file. 2569 Entries for closed files are removed when the 2570 corresponding entries are removed from the 2571 applPastChannelTable." 2572 ::= { applPastChannelGroup 3 } 2574 applPastFileEntry OBJECT-TYPE 2575 SYNTAX ApplPastFileEntry 2576 MAX-ACCESS not-accessible 2577 STATUS current 2578 DESCRIPTION 2579 "An applPastFileEntry provides additional, file-specific 2580 information to complement the corresponding 2581 applPastChannelEntry for a channel which was a file." 2582 INDEX { applElmtOrSvc, applElmtOrSvcId, 2583 applPastChannelIndex } 2584 ::= { applPastFileTable 1 } 2586 ApplPastFileEntry ::= SEQUENCE 2587 { 2588 applPastFileName LongUtf8String, 2589 applPastFileSizeHigh Unsigned32, 2590 applPastFileSizeLow Unsigned32, 2591 applPastFileMode INTEGER 2592 } 2594 applPastFileName OBJECT-TYPE 2595 SYNTAX LongUtf8String 2596 MAX-ACCESS read-only 2597 STATUS current 2598 DESCRIPTION 2599 "This attribute records the last known value of 2600 applOpenFileName before the channel was closed." 2601 ::= { applPastFileEntry 1 } 2603 applPastFileSizeHigh OBJECT-TYPE 2604 SYNTAX Unsigned32 2605 UNITS "2^32 byte blocks" 2606 MAX-ACCESS read-only 2607 STATUS current 2608 DESCRIPTION 2609 "This attribute records the value of applOpenFileSizeHigh 2610 at the time this channel was closed. 2612 For example, for a file with a total size of 2613 4,294,967,296 bytes, this attribute would have a value 2614 of 1; for a file with a total size of 4,294,967,295 2615 bytes this attribute's value would be 0." 2616 ::= { applPastFileEntry 2 } 2618 applPastFileSizeLow OBJECT-TYPE 2619 SYNTAX Unsigned32 2620 UNITS "bytes" 2621 MAX-ACCESS read-only 2622 STATUS current 2623 DESCRIPTION 2624 "This attribute records the value of applOpenFileSizeLow 2625 at the time this channel was closed. 2627 For example, for a file with a total size of 2628 4,294,967,296 bytes this attribute would have a value 2629 of 0; for a file with a total size of 4,294,967,295 2630 bytes this attribute's value would be 4,294,967,295." 2631 ::= { applPastFileEntry 3 } 2633 applPastFileMode OBJECT-TYPE 2634 SYNTAX INTEGER { read(1), 2635 write(2), 2636 readWrite(3) } 2637 MAX-ACCESS read-only 2638 STATUS current 2639 DESCRIPTION 2640 "This attribute records the value of applOpenFileMode 2641 at the time this channel was closed. " 2642 ::= { applPastFileEntry 4 } 2644 -- **************************************************************** 2645 -- 2646 -- applPastConTable - information specific to former connections 2647 -- 2648 -- **************************************************************** 2649 applPastConTable OBJECT-TYPE 2650 SYNTAX SEQUENCE OF ApplPastConEntry 2651 MAX-ACCESS not-accessible 2652 STATUS current 2653 DESCRIPTION 2654 "The applPastConTable supplements the applPastChannelTable 2655 for entries corresponding to channels which were 2656 connections. The indexing structure is identical 2657 to applPastChannelTable. An entry exists in the 2658 applPastConTable only if there is a corresponding 2659 (same index values) entry in the applPastChannelTable 2660 and if the channel was a connection. 2662 Entries for closed connections are removed when 2663 the corresponding entries are removed from the 2664 applPastChannelTable." 2665 ::= { applPastChannelGroup 4 } 2667 applPastConEntry OBJECT-TYPE 2668 SYNTAX ApplPastConEntry 2669 MAX-ACCESS not-accessible 2670 STATUS current 2671 DESCRIPTION 2672 "An applPastConEntry provides additional, 2673 connection-specific information to complement the 2674 corresponding applPastChannelEntry for a channel which 2675 was a connection." 2676 INDEX { applElmtOrSvc, applElmtOrSvcId, 2677 applPastChannelIndex } 2678 ::= { applPastConTable 1 } 2680 ApplPastConEntry ::= SEQUENCE 2681 { 2682 applPastConTransport TDomain, 2683 applPastConNearEndAddr ApplTAddress, 2684 applPastConNearEndpoint SnmpAdminString, 2685 applPastConFarEndAddr ApplTAddress, 2686 applPastConFarEndpoint SnmpAdminString, 2687 applPastConApplication SnmpAdminString 2688 } 2690 applPastConTransport OBJECT-TYPE 2691 SYNTAX TDomain 2692 MAX-ACCESS read-only 2693 STATUS current 2694 DESCRIPTION 2695 "The applPastConTransport attribute identifies the 2696 transport protocol that was in use for this former 2697 connection. If the transport protocol could not be 2698 determined, the value { 0 0 } shall be used." 2699 DEFVAL { zeroDotZero } 2700 ::= { applPastConEntry 1 } 2702 applPastConNearEndAddr OBJECT-TYPE 2703 SYNTAX ApplTAddress 2704 MAX-ACCESS read-only 2705 STATUS current 2706 DESCRIPTION 2707 "The applPastConNearEndAddr attribute reports the 2708 transport address and port information for the near 2709 end of this former connection. 2711 If the information could not be determined, the value 2712 shall be a zero-length string." 2713 DEFVAL { "" } 2714 ::= { applPastConEntry 2 } 2716 applPastConNearEndpoint OBJECT-TYPE 2717 SYNTAX SnmpAdminString 2718 MAX-ACCESS read-only 2719 STATUS current 2720 DESCRIPTION 2721 "The applPastConNearEndpoint attribute reports the 2722 fully-qualified domain name and port information for the 2723 near end of this former connection. 2725 The format of this attribute for TCP and UDP-based 2726 protocols is the fully-qualified domain name immediately 2727 followed by a colon which is immediately followed by 2728 the decimal representation of the port number. 2730 If the information could not be determined, the value 2731 shall be a zero-length string." 2732 DEFVAL { "" } 2733 ::= { applPastConEntry 3 } 2735 applPastConFarEndAddr OBJECT-TYPE 2736 SYNTAX ApplTAddress 2737 MAX-ACCESS read-only 2738 STATUS current 2739 DESCRIPTION 2740 "The applPastConFarEnd attribute reports the transport 2741 address and port information for the far end of this 2742 former connection. 2744 If not known, as in the case of a connectionless 2745 transport, the value of this attribute shall be a 2746 zero-length string." 2747 DEFVAL { "" } 2748 ::= { applPastConEntry 4 } 2750 applPastConFarEndpoint OBJECT-TYPE 2751 SYNTAX SnmpAdminString 2752 MAX-ACCESS read-only 2753 STATUS current 2754 DESCRIPTION 2755 "The applPastConFarEndpoint attribute reports the 2756 transport address and port information for the far 2757 end of this former connection. 2759 The format of this attribute for TCP and UDP-based 2760 protocols is the fully-qualified domain name immediately 2761 followed by a colon which is immediately followed by 2762 the decimal representation of the port number. 2764 If not known, as in the case of a connectionless 2765 transport, the value of this attribute shall be a 2766 zero-length string." 2767 DEFVAL { "" } 2768 ::= { applPastConEntry 5 } 2770 applPastConApplication OBJECT-TYPE 2771 SYNTAX SnmpAdminString 2772 MAX-ACCESS read-only 2773 STATUS current 2774 DESCRIPTION 2775 "The applPastConApplication attribute identifies the 2776 application layer protocol that was in use. Where 2777 possible, the values defined in [13] shall be used. 2778 If not known, the value of this attribute shall be a 2779 zero-length string." 2780 DEFVAL { "" } 2781 ::= { applPastConEntry 6 } 2783 -- **************************************************************** 2784 -- 2785 -- applPastTransStreamTable - historical 2786 -- information for transaction stream monitoring 2787 -- 2788 -- **************************************************************** 2789 applPastTransStreamTable OBJECT-TYPE 2790 SYNTAX SEQUENCE OF ApplPastTransStreamEntry 2791 MAX-ACCESS not-accessible 2792 STATUS current 2793 DESCRIPTION 2794 "The applPastTransStreamTable contains common 2795 information for historical transaction statistics." 2796 ::= { applPastChannelGroup 5 } 2798 applPastTransStreamEntry OBJECT-TYPE 2799 SYNTAX ApplPastTransStreamEntry 2800 MAX-ACCESS not-accessible 2801 STATUS current 2802 DESCRIPTION 2803 "An applPastTransStreamEntry contains information for 2804 a single former transaction stream. A transaction 2805 stream could have been a network connection, file, or 2806 other source of transactions." 2807 INDEX { applElmtOrSvc, applElmtOrSvcId, 2808 applPastChannelIndex } 2809 ::= { applPastTransStreamTable 1 } 2811 ApplPastTransStreamEntry ::= SEQUENCE { 2812 applPastTransStreamDescr SnmpAdminString, 2813 applPastTransStreamUnitOfWork SnmpAdminString, 2814 applPastTransStreamInvokes Unsigned64TC, 2815 applPastTransStreamInvokesLow Unsigned32, 2816 applPastTransStreamInvCumTimes Unsigned32, 2817 applPastTransStreamInvRspTimes Unsigned32, 2818 applPastTransStreamPerforms Unsigned64TC, 2819 applPastTransStreamPerformsLow Unsigned32, 2820 applPastTransStreamPrfCumTimes Unsigned32, 2821 applPastTransStreamPrfRspTimes Unsigned32 } 2822 applPastTransStreamDescr OBJECT-TYPE 2823 SYNTAX SnmpAdminString 2824 MAX-ACCESS read-only 2825 STATUS current 2826 DESCRIPTION 2827 "The applPastTransStreamDescr attribute provides a 2828 human-readable description of this transaction stream. 2830 If no descriptive information is available, this 2831 attribute's value shall be a zero-length string." 2832 DEFVAL { "" } 2833 ::= { applPastTransStreamEntry 1 } 2835 applPastTransStreamUnitOfWork OBJECT-TYPE 2836 SYNTAX SnmpAdminString 2837 MAX-ACCESS read-only 2838 STATUS current 2839 DESCRIPTION 2840 "The applPastTransStreamUnitOfWork attribute provides a 2841 human-readable definition of what the unit of work is 2842 for this transaction stream. 2844 If no descriptive information is available, this 2845 attribute's value shall be a zero-length string." 2846 DEFVAL { "" } 2847 ::= { applPastTransStreamEntry 2 } 2849 applPastTransStreamInvokes OBJECT-TYPE 2850 SYNTAX Unsigned64TC 2851 UNITS "transactions" 2852 MAX-ACCESS read-only 2853 STATUS current 2854 DESCRIPTION 2855 "Cumulative count of requests / invocations issued 2856 for this transaction stream when it was active." 2857 ::= { applPastTransStreamEntry 3 } 2859 applPastTransStreamInvokesLow OBJECT-TYPE 2860 SYNTAX Unsigned32 2861 UNITS "transactions" 2862 MAX-ACCESS read-only 2863 STATUS current 2864 DESCRIPTION 2865 "This object corresponds to the low thirty-two 2866 bits of applPastTransStreamInvokes." 2867 ::= { applPastTransStreamEntry 4 } 2869 applPastTransStreamInvCumTimes OBJECT-TYPE 2870 SYNTAX Unsigned32 2871 UNITS "milliseconds" 2872 MAX-ACCESS read-only 2873 STATUS current 2874 DESCRIPTION 2875 "The applPastTransStreamInvCumTimes attribute reports the 2876 cumulative sum of the lengths of the intervals times 2877 measured between the transmission of requests and the 2878 receipt of (the first of) the corresponding response(s)." 2879 ::= { applPastTransStreamEntry 5 } 2881 applPastTransStreamInvRspTimes OBJECT-TYPE 2882 SYNTAX Unsigned32 2883 UNITS "milliseconds" 2884 MAX-ACCESS read-only 2885 STATUS current 2886 DESCRIPTION 2887 "The applPastTransStreamInvRspTimes attribute reports the 2888 cumulative sum of the lengths of the intervals measured 2889 between the receipt of the first and last of multiple 2890 responses to a request. 2892 For transaction streams which do not permit multiple 2893 responses to a single request, this attribute will be 2894 zero." 2895 ::= { applPastTransStreamEntry 6 } 2897 applPastTransStreamPerforms OBJECT-TYPE 2898 SYNTAX Unsigned64TC 2899 UNITS "transactions" 2900 MAX-ACCESS read-only 2901 STATUS current 2902 DESCRIPTION 2903 "Total number of transactions performed." 2904 ::= { applPastTransStreamEntry 7 } 2906 applPastTransStreamPerformsLow OBJECT-TYPE 2907 SYNTAX Unsigned32 2908 UNITS "transactions" 2909 MAX-ACCESS read-only 2910 STATUS current 2911 DESCRIPTION 2912 "This objecy reports the low thirty-two bits of 2913 applPastTransStreamPerforms." 2914 ::= { applPastTransStreamEntry 8 } 2916 applPastTransStreamPrfCumTimes OBJECT-TYPE 2917 SYNTAX Unsigned32 2918 UNITS "milliseconds" 2919 MAX-ACCESS read-only 2920 STATUS current 2921 DESCRIPTION 2922 "The applPastTransStreamPrfCumTimes attribute reports the 2923 cumulative sum of the lengths of the intervals measured 2924 between receipt of requests and the transmission of the 2925 corresponding responses." 2926 ::= { applPastTransStreamEntry 9 } 2928 applPastTransStreamPrfRspTimes OBJECT-TYPE 2929 SYNTAX Unsigned32 2930 UNITS "milliseconds" 2931 MAX-ACCESS read-only 2932 STATUS current 2933 DESCRIPTION 2934 "For each transaction performed, the elapsed time between 2935 when the first response is enqueued and when the last 2936 response is enqueued is added to this cumulative sum. 2938 For single-response protocols, the value of 2939 applPastTransStreamPrfRspTimes will be zero." 2940 ::= { applPastTransStreamEntry 10 } 2942 -- **************************************************************** 2943 -- 2944 -- applPastTransFlowTable 2945 -- 2946 -- **************************************************************** 2948 applPastTransFlowTable OBJECT-TYPE 2949 SYNTAX SEQUENCE OF ApplPastTransFlowEntry 2950 MAX-ACCESS not-accessible 2951 STATUS current 2952 DESCRIPTION 2953 "The applPastTransFlowTable contains entries, organized by 2954 application instance or running application element, 2955 direction of flow, and type (request/response) for each 2956 former transaction stream. 2958 The simple model of a transaction used here looks like 2959 this: 2961 invoker | Request | performer 2962 | - - - - - - > | 2963 | | 2964 | Response | 2965 | < - - - - - - | 2966 | | 2968 Since in some protocols it is possible for an entity 2969 to take on both the invoker and performer roles, 2970 information here is accumulated for transmitted and 2971 received requests, as well as for transmitted and 2972 received responses. Counts are maintained for both 2973 transactions and bytes transferred." 2974 ::= { applPastChannelGroup 6 } 2976 applPastTransFlowEntry OBJECT-TYPE 2977 SYNTAX ApplPastTransFlowEntry 2978 MAX-ACCESS not-accessible 2979 STATUS current 2980 DESCRIPTION 2981 "An applPastTransFlowEntry records transaction throughput 2982 information for requests or response in a particular 2983 direction (transmit / receive) for a transaction stream. 2985 Entries in this table correspond to those in the 2986 applPastTransStreamTable with identical values 2987 for the applElmtOrSvc, applElmtOrSvcId, and the 2988 applPastChannelIndex." 2989 INDEX { applElmtOrSvc, 2990 applElmtOrSvcId, 2991 applPastChannelIndex, 2992 applPastTransFlowDirection, 2993 applPastTransFlowReqRsp } 2994 ::= { applPastTransFlowTable 1 } 2996 ApplPastTransFlowEntry ::= SEQUENCE { 2997 applPastTransFlowDirection INTEGER, 2998 applPastTransFlowReqRsp INTEGER, 2999 applPastTransFlowTrans Unsigned64TC, 3000 applPastTransFlowTransLow Unsigned32, 3001 applPastTransFlowBytes Unsigned64TC, 3002 applPastTransFlowBytesLow Unsigned32, 3003 applPastTransFlowTime DateAndTime } 3005 applPastTransFlowDirection OBJECT-TYPE 3006 SYNTAX INTEGER { transmit(1), 3007 receive(2) } 3008 MAX-ACCESS not-accessible 3009 STATUS current 3010 DESCRIPTION 3011 "The applPastTransFlowDirection index serves 3012 to identify an entry as containing information 3013 pertaining to the transmit (1) or receive (2) flow 3014 of a past transaction stream. This index corresponds 3015 to applTransactFlowDirection." 3016 ::= { applPastTransFlowEntry 1 } 3018 applPastTransFlowReqRsp OBJECT-TYPE 3019 SYNTAX INTEGER { request(1), 3020 response(2) } 3021 MAX-ACCESS not-accessible 3022 STATUS current 3023 DESCRIPTION 3024 "The value of the applPastTransFlowReqRsp index indicates 3025 whether this entry contains information on requests 3026 (1), or responses (2). This index corresponds to 3027 applTransactFlowReqRsp." 3028 ::= { applPastTransFlowEntry 2 } 3030 applPastTransFlowTrans OBJECT-TYPE 3031 SYNTAX Unsigned64TC 3032 UNITS "transactions" 3033 MAX-ACCESS read-only 3034 STATUS current 3035 DESCRIPTION 3036 "The applPastTransFlowTrans attribute reports the number 3037 of request/response (as indicated by the 3038 applPastTransFlowReqRsp index) transactions 3039 received/generated (as indicated by the 3040 applPastTransFlowDirection index) handled on this 3041 transaction stream." 3042 ::= { applPastTransFlowEntry 3 } 3044 applPastTransFlowTransLow OBJECT-TYPE 3045 SYNTAX Unsigned32 3046 UNITS "transactions" 3047 MAX-ACCESS read-only 3048 STATUS current 3049 DESCRIPTION 3050 "This attribute corresponds to the low thirty-two 3051 bits of applPastTransFlowTrans." 3052 ::= { applPastTransFlowEntry 4 } 3054 applPastTransFlowBytes OBJECT-TYPE 3055 SYNTAX Unsigned64TC 3056 UNITS "bytes" 3057 MAX-ACCESS read-only 3058 STATUS current 3059 DESCRIPTION 3060 "The applPastTransFlowBytes attribute reports the number 3061 of request/response (as indicated by the 3062 applPastTransFlowReqRsp index) bytes received/generated 3063 (as indicated by the applPastTransFlowDirection index) 3064 handled on this transaction stream. 3066 All application layer bytes are included in this count, 3067 including any application layer wrappers, headers, or 3068 other overhead." 3069 ::= { applPastTransFlowEntry 5 } 3071 applPastTransFlowBytesLow OBJECT-TYPE 3072 SYNTAX Unsigned32 3073 UNITS "bytes" 3074 MAX-ACCESS read-only 3075 STATUS current 3076 DESCRIPTION 3077 "This attribute corresponds to the low thirty-two 3078 bits of applPastTransFlowBytes." 3079 ::= { applPastTransFlowEntry 6 } 3081 applPastTransFlowTime OBJECT-TYPE 3082 SYNTAX DateAndTime 3083 MAX-ACCESS read-only 3084 STATUS current 3085 DESCRIPTION 3086 "The applPastTransFlowTime attribute records the time of 3087 the processing (receipt or transmission as 3088 indicated by the applPastTransFlowDirection index) 3089 of the last request/response (as indicated by the 3090 applPastTransFlowReqRsp index) on this transaction 3091 stream. 3093 If no requests/responses been received/transmitted by 3094 this entity over this transaction stream, the value 3095 of this attribute shall be '0000000000000000'H " 3096 DEFVAL { '0000000000000000'H } 3097 ::= { applPastTransFlowEntry 7 } 3099 -- **************************************************************** 3100 -- 3101 -- applPastTransKindTable - transaction statistics broken down 3102 -- according to the kinds of transactions in each direction 3103 -- for a transaction stream. 3104 -- 3105 -- **************************************************************** 3107 applPastTransKindTable OBJECT-TYPE 3108 SYNTAX SEQUENCE OF ApplPastTransKindEntry 3109 MAX-ACCESS not-accessible 3110 STATUS current 3111 DESCRIPTION 3112 "The applPastTransKindTable provides transaction 3113 statistics broken down by kinds of transaction. 3114 The definition of the kinds of transactions is 3115 specific to the application protocol in use, and may be 3116 documented in the form of an applicability statement. " 3117 ::= { applPastChannelGroup 7 } 3119 applPastTransKindEntry OBJECT-TYPE 3120 SYNTAX ApplPastTransKindEntry 3121 MAX-ACCESS not-accessible 3122 STATUS current 3123 DESCRIPTION 3124 "An applPastTransKindEntry reports historical data for a 3125 specific service instance or running application 3126 element's use of a specific transaction stream in 3127 a particular direction in requests or responses 3128 (as indicated by the applPastTransFlowReqRsp index) 3129 broken down by transaction kind, as indicated by the 3130 applPastTransKind index." 3131 INDEX { applElmtOrSvc, 3132 applElmtOrSvcId, 3133 applPastChannelIndex, 3134 applPastTransFlowDirection, 3135 applPastTransFlowReqRsp, 3136 applPastTransKind } 3137 ::= { applPastTransKindTable 1 } 3139 ApplPastTransKindEntry ::= SEQUENCE 3140 { 3141 applPastTransKind SnmpAdminString, 3142 applPastTransKindTrans Unsigned64TC, 3143 applPastTransKindTransLow Unsigned32, 3144 applPastTransKindBytes Unsigned64TC, 3145 applPastTransKindBytesLow Unsigned32, 3146 applPastTransKindTime DateAndTime 3147 } 3149 applPastTransKind OBJECT-TYPE 3150 SYNTAX SnmpAdminString (SIZE (1 .. 32)) 3151 MAX-ACCESS not-accessible 3152 STATUS current 3153 DESCRIPTION 3154 "The applPastTransKind index is the human-readable 3155 identifier for a particular transaction kind within 3156 the context of an application protocol. The values 3157 to be used for a particular protocol may be identified 3158 in an applicability statement. This index corresponds 3159 to applTransactKind." 3160 ::= { applPastTransKindEntry 1 } 3162 applPastTransKindTrans OBJECT-TYPE 3163 SYNTAX Unsigned64TC 3164 UNITS "transactions" 3165 MAX-ACCESS read-only 3166 STATUS current 3167 DESCRIPTION 3168 "For this transaction stream, this attribute records 3169 the total number of transactions of the type 3170 identified by the indexes. The type is characterized 3171 according to the receive/transmit direction 3172 (applPastTransFlowDirecton), whether it was a request 3173 or a response (applPastTransFlowReqRsp), and the 3174 protocol-specific transaction kind (applPastTransKind). 3175 stream for this transaction kind." 3176 ::= { applPastTransKindEntry 2 } 3178 applPastTransKindTransLow OBJECT-TYPE 3179 SYNTAX Unsigned32 3180 UNITS "transactions" 3181 MAX-ACCESS read-only 3182 STATUS current 3183 DESCRIPTION 3184 "The applPastTransKindTransLow attribute reports 3185 the low thirty-two bits of applPastTransKindTrans." 3186 ::= { applPastTransKindEntry 3 } 3188 applPastTransKindBytes OBJECT-TYPE 3189 SYNTAX Unsigned64TC 3190 UNITS "bytes" 3191 MAX-ACCESS read-only 3192 STATUS current 3193 DESCRIPTION 3194 "For this transaction stream and transaction kind, the 3195 applPastTransKindBytes attribute reports the number 3196 of bytes received or generated (as indicated by 3197 the applPastTransFlowDirection index) in requests or 3198 responses (as indicated by the applPastTransFlowReqRsp 3199 index). 3201 All application layer bytes are included in this count, 3202 including any application layer wrappers, headers, or 3203 other overhead." 3204 ::= { applPastTransKindEntry 4 } 3206 applPastTransKindBytesLow OBJECT-TYPE 3207 SYNTAX Unsigned32 3208 UNITS "bytes" 3209 MAX-ACCESS read-only 3210 STATUS current 3211 DESCRIPTION 3212 "The applPastTransKindBytesLow attribute corresponds 3213 to the low thirty-two bits of applPastTransKindBytes." 3214 ::= { applPastTransKindEntry 5 } 3216 applPastTransKindTime OBJECT-TYPE 3217 SYNTAX DateAndTime 3218 MAX-ACCESS read-only 3219 STATUS current 3220 DESCRIPTION 3221 "The applPastTransKindTime attribute records the time of 3222 the processing (receipt or transmission as 3223 indicated by the applPastTransFlowDirection index) 3224 of the last request/response (as indicated by the 3225 applPastTransFlowReqRsp index) of this kind of 3226 transaction on this transaction stream. 3228 If no requests/responses of this kind were 3229 received/transmitted over this transaction stream, the 3230 value of this attribute shall be '0000000000000000'H " 3231 DEFVAL { '0000000000000000'H } 3232 ::= { applPastTransKindEntry 6 } 3234 -- **************************************************************** 3235 -- 3236 -- applElmtRunControlGroup - monitor and control running 3237 -- application elements 3238 -- 3239 -- **************************************************************** 3241 applElmtRunStatusTable OBJECT-TYPE 3242 SYNTAX SEQUENCE OF ApplElmtRunStatusEntry 3243 MAX-ACCESS not-accessible 3244 STATUS current 3245 DESCRIPTION 3246 "This table provides information on running application 3247 elements, complementing information available in the 3248 correspondingly indexed sysApplElmtRunTable [31]." 3249 ::= { applElmtRunControlGroup 1 } 3251 applElmtRunStatusEntry OBJECT-TYPE 3252 SYNTAX ApplElmtRunStatusEntry 3253 MAX-ACCESS not-accessible 3254 STATUS current 3255 DESCRIPTION 3256 "An applElmtRunStatusEntry contains information to support 3257 the control and monitoring of a single running application 3258 element." 3259 INDEX { sysApplElmtRunIndex } 3260 ::= { applElmtRunStatusTable 1 } 3262 ApplElmtRunStatusEntry ::= SEQUENCE { 3263 applElmtRunStatusSuspended TruthValue, 3264 applElmtRunStatusHeapUsage Unsigned32, 3265 applElmtRunStatusOpenConnections Unsigned32, 3266 applElmtRunStatusOpenFiles Gauge32, 3267 applElmtRunStatusLastErrorMsg SnmpAdminString, 3268 applElmtRunStatusLastErrorTime DateAndTime } 3270 applElmtRunStatusSuspended OBJECT-TYPE 3271 SYNTAX TruthValue 3272 MAX-ACCESS read-only 3273 STATUS current 3274 DESCRIPTION 3275 "The applElmtRunStatusSuspended attribute reports 3276 whether processing by this running application element 3277 has been suspended, whether by management request or by 3278 other means." 3279 ::= { applElmtRunStatusEntry 1 } 3281 applElmtRunStatusHeapUsage OBJECT-TYPE 3282 SYNTAX Unsigned32 3283 UNITS "bytes" 3284 MAX-ACCESS read-only 3285 STATUS current 3286 DESCRIPTION 3287 "The applElmtRunStatusHeapUsage reports the current 3288 approximate heap usage by this running application 3289 element." 3290 ::= { applElmtRunStatusEntry 2 } 3292 applElmtRunStatusOpenConnections OBJECT-TYPE 3293 SYNTAX Unsigned32 3294 UNITS "connections" 3295 MAX-ACCESS read-only 3296 STATUS current 3297 DESCRIPTION 3298 "The applElmtRunStatusOpenConnections attribute reports 3299 the current number of open connections in use by this 3300 running application element." 3301 ::= { applElmtRunStatusEntry 3 } 3303 applElmtRunStatusOpenFiles OBJECT-TYPE 3304 SYNTAX Gauge32 3305 UNITS "files" 3306 MAX-ACCESS read-only 3307 STATUS current 3308 DESCRIPTION 3309 "The applElmtRunStatusOpenFiles attribute reports the 3310 current number of open files in use by this running 3311 application element." 3312 ::= { applElmtRunStatusEntry 4 } 3314 applElmtRunStatusLastErrorMsg OBJECT-TYPE 3315 SYNTAX SnmpAdminString 3316 MAX-ACCESS read-only 3317 STATUS current 3318 DESCRIPTION 3319 "The applElmtRunStatusLastErrorMessage attribute reports 3320 the most recent error message (typically written to 3321 stderr or a system error logging facility) from this 3322 running application element. If no such message has yet 3323 been generated, the value of this attribute shall be a 3324 zero-length string." 3325 DEFVAL { "" } 3326 ::= { applElmtRunStatusEntry 5 } 3328 applElmtRunStatusLastErrorTime OBJECT-TYPE 3329 SYNTAX DateAndTime 3330 MAX-ACCESS read-only 3331 STATUS current 3332 DESCRIPTION 3333 "The applElmtRunStatusLastErrorTime attribute reports the 3334 time of the most recent error message in 3335 applElmtRunStatusLastErrorMsg. 3337 If no such message has yet been generated, the value 3338 of this attribute shall be '0000000000000000'H " 3339 DEFVAL { '0000000000000000'H } 3340 ::= { applElmtRunStatusEntry 6 } 3342 -- **************************************************************** 3343 -- 3344 -- applElmtRunControlTable - control running application 3345 -- elements 3346 -- 3347 -- **************************************************************** 3349 applElmtRunControlTable OBJECT-TYPE 3350 SYNTAX SEQUENCE OF ApplElmtRunControlEntry 3351 MAX-ACCESS not-accessible 3352 STATUS current 3353 DESCRIPTION 3354 "This table provides the ability to control application 3355 elements, complementing information available in the 3356 correspondingly indexed sysApplElmtRunTable [31]." 3357 ::= { applElmtRunControlGroup 2 } 3359 applElmtRunControlEntry OBJECT-TYPE 3360 SYNTAX ApplElmtRunControlEntry 3361 MAX-ACCESS not-accessible 3362 STATUS current 3363 DESCRIPTION 3364 "An applElmtRunControlEntry contains information to 3365 support the control of a single running application 3366 element." 3367 INDEX { sysApplElmtRunIndex } 3368 ::= { applElmtRunControlTable 1 } 3370 ApplElmtRunControlEntry ::= SEQUENCE { 3371 applElmtRunControlSuspend TruthValue, 3372 applElmtRunControlReconfigure TestAndIncr, 3373 applElmtRunControlTerminate TruthValue } 3375 applElmtRunControlSuspend OBJECT-TYPE 3376 SYNTAX TruthValue 3377 MAX-ACCESS read-write 3378 STATUS current 3379 DESCRIPTION 3380 "Setting this variable to 'true' requests the suspension 3381 of processing by this running application element. 3382 Setting this variable to 'false' requests that processing 3383 be resumed. The effect, if any, will be reported by the 3384 applElmtRunStatusSuspended attribute." 3385 DEFVAL { false } 3386 ::= { applElmtRunControlEntry 1 } 3388 applElmtRunControlReconfigure OBJECT-TYPE 3389 SYNTAX TestAndIncr 3390 MAX-ACCESS read-write 3391 STATUS current 3392 DESCRIPTION 3393 "Changing the value of this variable requests that the 3394 running application element re-load its configuration 3395 (like SIGHUP for many UNIX-based daemons). 3397 Note that completion of a SET on this object only implies 3398 that configuration reload was initiated, not necessarily 3399 that the reload has been completed." 3400 ::= { applElmtRunControlEntry 2 } 3402 applElmtRunControlTerminate OBJECT-TYPE 3403 SYNTAX TruthValue 3404 MAX-ACCESS read-write 3405 STATUS current 3406 DESCRIPTION 3407 "Setting the value of applElmtRunControlTerminate to 3408 'true' requests that the running application element 3409 terminate processing and exit in an orderly manner. 3410 This is a 'polite' shutdown request. 3412 When read, this object's value will be 'false' except 3413 when orderly termination is in progress. 3415 Note that completion of a SET on this object only implies 3416 that termination was initiated, not necessarily that the 3417 termination has been completed." 3418 DEFVAL { false } 3419 ::= { applElmtRunControlEntry 3 } 3421 -- **************************************************************** 3422 -- 3423 -- Conformance requirements 3424 -- 3425 -- **************************************************************** 3427 applicationMibGroups OBJECT IDENTIFIER ::= 3428 { applicationMibConformance 1} 3430 applicationMonitorGroup OBJECT-GROUP 3431 OBJECTS { applSrvInstQual, 3432 applSrvName, 3433 applSrvIndex, 3434 applSrvInstance, 3435 applOpenChannelOpenTime, 3436 applOpenChannelReadRequestsLow, 3437 applOpenChannelReadFailures, 3438 applOpenChannelBytesReadLow, 3439 applOpenChannelLastReadTime, 3440 applOpenChannelWriteRequestsLow, 3441 applOpenChannelWriteFailures, 3442 applOpenChannelBytesWrittenLow, 3443 applOpenChannelLastWriteTime, 3444 applOpenFileName, 3445 applOpenFileSizeHigh, 3446 applOpenFileSizeLow, 3447 applOpenFileMode, 3448 applOpenConnectionTransport, 3449 applOpenConnectionNearEndAddr, 3450 applOpenConnectionNearEndpoint, 3451 applOpenConnectionFarEndAddr, 3452 applOpenConnectionFarEndpoint, 3453 applOpenConnectionApplication } 3454 STATUS current 3455 DESCRIPTION 3456 "This group represents the basic capabilities of this MIB." 3457 ::= { applicationMibGroups 1 } 3459 applicationFastMonitorGroup OBJECT-GROUP 3460 OBJECTS { applOpenChannelReadRequests, 3461 applOpenChannelBytesRead, 3462 applOpenChannelWriteRequests, 3463 applOpenChannelBytesWritten } 3464 STATUS current 3465 DESCRIPTION 3466 "This group comprises 64-bit counters mandatory in 3467 high-throughput environments, where 32-bit counters 3468 could wrap in less than an hour." 3469 ::= { applicationMibGroups 2 } 3471 applicationTransactGroup OBJECT-GROUP 3472 OBJECTS { applTransactStreamDescr, 3473 applTransactStreamUnitOfWork, 3474 applTransactStreamInvokesLow, 3475 applTransactStreamInvCumTimes, 3476 applTransactStreamInvRspTimes, 3477 applTransactStreamPerformsLow, 3478 applTransactStreamPrfCumTimes, 3479 applTransactStreamPrfRspTimes, 3480 applTransactFlowTransLow, 3481 applTransactFlowBytesLow, 3482 applTransactFlowTime, 3483 applTransactKindTransLow, 3484 applTransactKindBytesLow, 3485 applTransactKindTime } 3486 STATUS current 3487 DESCRIPTION 3488 "This group comprises objects appropriate from monitoring 3489 transaction-structured flows." 3490 ::= { applicationMibGroups 3 } 3492 applicationFastTransactGroup OBJECT-GROUP 3493 OBJECTS { applTransactStreamInvokes, 3494 applTransactStreamPerforms, 3495 applTransactFlowTrans, 3496 applTransactFlowBytes, 3497 applTransactKindTrans, 3498 applTransactKindBytes } 3499 STATUS current 3500 DESCRIPTION 3501 "This group comprises 64-bit transaction counters required in 3502 high-throughput environments, where 32-bit counters could 3503 wrap in less than an hour." 3504 ::= { applicationMibGroups 4 } 3506 applicationHistoryGroup OBJECT-GROUP 3507 OBJECTS { applPastChannelControlCollect, 3508 applPastChannelControlMaxRows, 3509 applPastChannelControlTimeLimit, 3510 applPastChannelControlRemItems, 3511 applPastChannelOpenTime, 3512 applPastChannelCloseTime, 3513 applPastChannelReadReqsLow, 3514 applPastChannelReadFailures, 3515 applPastChannelBytesReadLow, 3516 applPastChannelLastReadTime, 3517 applPastChannelWriteReqsLow, 3518 applPastChannelWriteFailures, 3519 applPastChannelBytesWritLow, 3520 applPastChannelLastWriteTime, 3521 applPastFileName, 3522 applPastFileSizeHigh, 3523 applPastFileSizeLow, 3524 applPastFileMode, 3525 applPastConTransport, 3526 applPastConNearEndAddr, 3527 applPastConNearEndpoint, 3528 applPastConFarEndAddr, 3529 applPastConFarEndpoint, 3530 applPastConApplication} 3531 STATUS current 3532 DESCRIPTION 3533 "This group models basic historical data." 3534 ::= { applicationMibGroups 5 } 3536 applicationFastHistoryGroup OBJECT-GROUP 3537 OBJECTS { applPastChannelReadRequests, 3538 applPastChannelBytesRead, 3539 applPastChannelWriteRequests, 3540 applPastChannelBytesWritten} 3541 STATUS current 3542 DESCRIPTION 3543 "This group comprises additional 64-bit objects required 3544 for recording historical data in high-volume environments, 3545 where a 32-bit integer would be insufficient." 3546 ::= { applicationMibGroups 6 } 3548 applicationTransHistoryGroup OBJECT-GROUP 3549 OBJECTS { applPastTransStreamDescr, 3550 applPastTransStreamUnitOfWork, 3551 applPastTransStreamInvokesLow, 3552 applPastTransStreamInvCumTimes, 3553 applPastTransStreamInvRspTimes, 3554 applPastTransStreamPerformsLow, 3555 applPastTransStreamPrfCumTimes, 3556 applPastTransStreamPrfRspTimes, 3557 applPastTransFlowTransLow, 3558 applPastTransFlowBytesLow, 3559 applPastTransFlowTime, 3560 applPastTransKindTransLow, 3561 applPastTransKindBytesLow, 3562 applPastTransKindTime } 3563 STATUS current 3564 DESCRIPTION 3565 "This group represents historical data for transaction- 3566 structured information streams." 3567 ::= { applicationMibGroups 7 } 3569 applicationFastTransHistoryGroup OBJECT-GROUP 3570 OBJECTS { applPastTransFlowTrans, 3571 applPastTransFlowBytes, 3572 applPastTransKindTrans, 3573 applPastTransKindBytes, 3574 applPastTransStreamPerforms, 3575 applPastTransStreamInvokes } 3576 STATUS current 3577 DESCRIPTION 3578 "This group contains 64-bit objects required for historical 3579 records on high-volume transaction-structured streams, 3580 where 32-bit integers would be insufficient." 3581 ::= { applicationMibGroups 8 } 3583 applicationRunGroup OBJECT-GROUP 3584 OBJECTS { applElmtRunStatusSuspended, 3585 applElmtRunStatusHeapUsage, 3586 applElmtRunStatusOpenConnections, 3587 applElmtRunStatusOpenFiles, 3588 applElmtRunStatusLastErrorMsg, 3589 applElmtRunStatusLastErrorTime, 3590 applElmtRunControlSuspend, 3591 applElmtRunControlReconfigure, 3592 applElmtRunControlTerminate } 3593 STATUS current 3594 DESCRIPTION 3595 "This group represents extensions to the system application 3596 MIB." 3597 ::= { applicationMibGroups 9 } 3599 applicationMibCompliance MODULE-COMPLIANCE 3600 STATUS current 3601 DESCRIPTION "The compliance statement for the application MIB." 3602 MODULE 3603 MANDATORY-GROUPS { applicationMonitorGroup, 3604 applicationHistoryGroup, 3605 applicationRunGroup } 3607 OBJECT applPastChannelControlCollect 3608 MIN-ACCESS read-only 3609 DESCRIPTION 3610 "This object should be limited to read-only 3611 access in environments with inadequate 3612 security." 3614 OBJECT applPastChannelControlMaxRows 3615 MIN-ACCESS read-only 3616 DESCRIPTION 3617 "This object should be limited to read-only 3618 access in environments with inadequate 3619 security." 3621 OBJECT applPastChannelControlTimeLimit 3622 MIN-ACCESS read-only 3623 DESCRIPTION 3624 "This object should be limited to read-only 3625 access in environments with inadequate 3626 security." 3628 OBJECT applElmtRunControlSuspend 3629 MIN-ACCESS read-only 3630 DESCRIPTION 3631 "This object should be limited to read-only 3632 access in environments with inadequate 3633 security." 3635 OBJECT applElmtRunControlReconfigure 3636 MIN-ACCESS read-only 3637 DESCRIPTION 3638 "This object should be limited to read-only 3639 access in environments with inadequate 3640 security." 3642 OBJECT applElmtRunControlTerminate 3643 MIN-ACCESS read-only 3644 DESCRIPTION 3645 "This object should be limited to read-only 3646 access in environments with inadequate 3647 security." 3649 GROUP applicationTransactGroup 3650 DESCRIPTION 3651 "The applicationTransactGroup is required when the 3652 information stream processed has a transaction 3653 structure. " 3655 GROUP applicationTransHistoryGroup 3656 DESCRIPTION 3657 "The applicationTransHistoryGroup must be implemented 3658 if applicationTransactGroup and applicationHistoryGroup 3659 are implemented." 3661 GROUP applicationFastMonitorGroup 3662 DESCRIPTION 3663 "The applicationFastMonitorGroup is mandatory when 3664 the applicationMonitorGroup is implemented and its 3665 counts group may exceed what can be represented in 32 bits." 3667 GROUP applicationFastTransactGroup 3668 DESCRIPTION 3669 "The applicationFastTransactGroup is mandatory when 3670 the applicationTransactGroup is implemented and its 3671 counts may exceed what can be represented in 32 bits." 3673 GROUP applicationFastHistoryGroup 3674 DESCRIPTION 3675 "The applicationFastHistoryGroup is mandatory when 3676 the applicationHistoryGroup is implemented and its 3677 counts may exceed what can be represented in 32 bits." 3679 GROUP applicationFastTransHistoryGroup 3680 DESCRIPTION 3681 "The applicationFastTransHistoryGroup is mandatory when 3682 the applicationTransHistoryGroup is implemented and its 3683 counts may exceed what can be represented in 32 bits." 3684 ::= { applicationMibConformance 2 } 3686 END 3688 6. Implementation Issues 3690 Unlike the system application MIB [31], in many environments support 3691 for much of this MIB requires instrumentation built into the managed 3692 resource. Some tables may be implemented by a single monitor 3693 process; for others, the implementation may be distributed within the 3694 managed system with the resources being managed. 3696 As a practical matter, this means that the management infrastructure 3697 of the managed system must support different subagents taking 3698 responsibility for different rows of a single table. This can be 3699 supported by AgentX [25], as well as some other subagent protocols 3700 such as [8], [9], and [11]. 3702 The sysApplRunElmtIndex is the key connection between this MIB and 3703 the systems application MIB. Implementations of these two MIBs 3704 intended to run concurrently on a given platform must employ a 3705 consistent policy for assigning this value to running application 3706 elements. 3708 Some of the objects defined in this MIB may carry a high run-time 3709 cost in some environments. For example, tracking transaction elapsed 3710 time could be expensive if it required two kernel calls (start and 3711 finish) per transaction. Similarly, maintaining tables of per- 3712 transaction information, rather than aggregating information by 3713 transaction type or transaction stream, could have significant 3714 storage and performance impacts. 3716 Unless a collision-free mechanism for allocating service instance 3717 indexes is in place, the structure of the service-level tables makes 3718 an index-reservation mechanism necessary. AgentX [25] is an example 3719 of a subagent protocol capable of satisfying this requirement. 3721 7. Intellectual Property 3723 The IETF takes no position regarding the validity or scope of any 3724 intellectual property or other rights that might be claimed to 3725 pertain to the implementation or use of the technology described in 3726 this document or the extent to which any license under such rights 3727 might or might not be available; neither does it represent that it 3728 has made any effort to identify any such rights. Information on the 3729 IETF's procedures with respect to rights in standards-track and 3730 standards-related documentation can be found in BCP-11. Copies of 3731 claims of rights made available for publication and any assurances of 3732 licenses to be made available, or the result of an attempt made to 3733 obtain a general license or permission for the use of such 3734 proprietary rights by implementors or users of this specification can 3735 be obtained from the IETF Secretariat. 3737 The IETF invites any interested party to bring to its attention any 3738 copyrights, patents or patent applications, or other proprietary 3739 rights which may cover technology that may be required to practice 3740 this standard. Please address the information to the IETF Executive 3741 Director. 3743 8. Acknowledgements 3745 This document was produced by the Application MIB working group. 3747 The editor gratefully acknowledges the comments and contributions of 3748 the following individuals: 3750 Harrie Hazewinkel 3751 Carl Kalbfleisch 3752 Cheryl Krupczak 3753 David Partain 3754 Jon Saperia 3755 Juergen Schoenwaelder 3756 Kenneth White 3758 9. Security Considerations 3760 By making potentially sensitive information externally accessible, 3761 the capabilities supported by the MIB have the potential of becoming 3762 security problems. How security fits into SNMP frameworks is 3763 described in [26], and a specific access control model is described 3764 in [30]. 3766 The tables in this MIB are organized to separate sensitive control 3767 capabilities from less sensitive usage information. For example, the 3768 objects to control application suspend/resume are separated from 3769 those to handle reconfiguration, which in turn are distinct from 3770 those for termination. This recognizes the need to support 3771 configurations where the level of authorization needed by a manager 3772 to do a "reconfigure" might be substantially less than the level 3773 needed to terminate an application element. By keeping these in 3774 separate columns, we make it possible to set up access control that 3775 allows, for example, "reconfigure" but not "kill". 3777 The MIB is structured to be useful for managers with read-only access 3778 rights. In some environments, it may be approprate to restrict even 3779 read-only access to these MIBs. 3781 The capabilities supported by this MIB include several that may be of 3782 value to a security administrator. These include the ability to 3783 monitor the level of usage of a given application, and to check the 3784 integrity of application components. 3786 10. References 3788 [1] ARM Working Group, "Application Response Measurement (ARM) API 3789 Guide, Version 2", September, 1997. 3791 [2] IEEE P1387.2, POSIX System Administration - Part 2: Software 3792 Administration. (Draft) 3794 [3] ITU-T Recommendation X.744 | ISO/IEC IS 10164-18:1996, 3795 Information Technology - Open Systems Interconnection - Systems 3796 Management: Software Management Function, 1996. 3798 [4] Rose, M., and K. McCloghrie, "Structure and Identification of 3799 Management Information for TCP/IP-based Internets", RFC 1155, 3800 May 1990. 3802 [5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 3803 Network Management Protocol", RFC 1157, May 1990. 3805 [6] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 3806 March 1991. 3808 [7] M. Rose, "A Convention for Defining Traps for use with the SNMP", 3809 RFC 1215, March 1991. 3811 [8] Rose, M., "SNMP MUX Protocol and MIB", RFC 1227, May 1991. 3813 [9] Carpenter, G. and B. Wijnen, "SNMP-DPI Simple Network Management 3814 Protocol Distributed Program Interface", RFC 1228, May 1991. 3816 [10] Grillo, P., and S. Waldbusser, "Host Resources MIB", RFC 1514, 3817 September 1993. 3819 [11] Carpenter, G., Curran, K., Sehgal, A., Waters, G., and B. 3820 Wijnen, "Simple Network Management Protocol Distributed Protocol 3821 Interface Version 2.0", RFC 1592, March 1994. 3823 [12] Brower, D., Purvy, R., Daniel, A., Sinykin, M., and J. Smith, 3824 "Relational Database Management System (RDBMS) Management 3825 Information Base (MIB) using SMIv2", RFC 1697, August 1994. 3827 [13] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", RFC 1700, STD 2, 3828 October, 1994. 3830 [14] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3831 "Introduction to Community-based SNMPv2", RFC 1901, January 3832 1996. 3834 [15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3835 "Structure of Management Information for Version 2 of the Simple 3836 Network Management Protocol (SNMPv2)", RFC 1902, January 1996. 3838 [16] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 3839 Conventions for Version 2 of the Simple Network Management 3840 Protocol (SNMPv2)", RFC 1903, January 1996. 3842 [17] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3843 "Conformance Statements for Version 2 of the Simple Network 3844 Management Protocol (SNMPv2)", RFC 1904, January 1996. 3846 [18] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 3847 Operations for Version 2 of the Simple Network Management 3848 Protocol (SNMPv2)", RFC 1905, January 1996. 3850 [19] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3851 "Transport Mappings for Version 2 of the Simple Network 3852 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3854 [20] McCloghrie, K., and A Bierman, "Entity MIB using SMIv2", RFC 3855 2037, October 1996. 3857 [21] C. Kalbfleisch, "Applicability of Standards Track MIBs to 3858 Management of World Wide Web Servers", RFC 2039, November 1996. 3860 [22] Bradner, S., "Key words for use in RFCs to Indicate Requirement 3861 Levels", BCP 14, RFC 2119, March 1997. 3863 [23] Freed, N., and S. Kille, "Network Services Monitoring MIB", RFC 3864 2248, January 1998. 3866 [24] Freed, N., and S. Kille, "Mail Monitoring MIB", RFC 2249, 3867 January 1998. 3869 [25] Daniele, M., Francisco, D., and B. Wijnen, "Agent Extensibility 3870 (AgentX) Protocol", RFC 2257, January, 1998. 3872 [26] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 3873 describing SNMP Management Frameworks", RFC 2271, January 1998. 3875 [27] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 3876 Processing and Dispatching for the Simple Network Management 3877 Protocol (SNMP)", RFC 2272, January 1998. 3879 [28] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 3880 2273, January 1998. 3882 [29] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 3883 for version 3 of the Simple Network Management Protocol 3884 (SNMPv3)", RFC 2274, January 1998. 3886 [30] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 3887 Control Model for the Simple Network Management Protocol 3888 (SNMP)", RFC 2275, January 1998. 3890 [31] Krupczak, C., and J. Saperia, "Definitions of System-Level 3891 Managed Objects for Applications", RFC 2287, February 1998. 3893 11. Authors' Addresses 3895 Carl Kalbfleisch 3896 Verio, Inc. 3897 1950 Stemmons Freeway 3898 2004 INFOMART 3899 Dallas, TX 75207 3900 USA 3902 Phone: +1 972-238-8303 3903 Fax: +1 972-238-0268 3904 EMail: cwk@verio.net 3906 Cheryl Krupczak 3907 Empire Technologies, Inc. 3908 541 Tenth Street, NW Suite 169 3909 Atlanta, GA 30318 3910 USA 3912 Phone: +1 770-384-0184 3913 EMail: cheryl@empiretech.com 3914 Randy Presuhn (Editor) 3915 BMC Software, Inc. 3916 965 Stewart Drive 3917 Sunnyvale, CA 94086 3918 USA 3920 Phone: +1 408-616-3100 3921 Fax: +1 408-616-3101 3922 EMail: randy_presuhn@bmc.com 3924 Jon Saperia 3925 IronBridge Networks 3926 55 Hayden Avenue 3927 Lexington, MA 02173 3928 USA 3930 Phone: +1 781-402-8029 3931 Fax: +1 781-402-8090 3932 EMail: saperia@ironbridgenetworks.com 3934 12. Full Copyright Statement 3936 Copyright (C) The Internet Society (1998). All Rights Reserved. 3938 This document and translations of it may be copied and furnished to 3939 others, and derivative works that comment on or otherwise explain it 3940 or assist in its implementation may be prepared, copied, published 3941 and distributed, in whole or in part, without restriction of any 3942 kind, provided that the above copyright notice and this paragraph are 3943 included on all such copies and derivative works. However, this 3944 document itself may not be modified in any way, such as by removing 3945 the copyright notice or references to the Internet Society or other 3946 Internet organizations, except as needed for the purpose of 3947 developing Internet standards in which case the procedures for 3948 copyrights defined in the Internet Standards process must be 3949 followed, or as required to translate it into languages other than 3950 English. 3952 The limited permissions granted above are perpetual and will not be 3953 revoked by the Internet Society or its successors or assigns. 3955 This document and the information contained herein is provided on an 3956 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3957 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3958 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3959 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3960 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.