idnits 2.17.1 draft-ietf-applmib-mib-08.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 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 April 1998) is 9505 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '6' is defined on line 3664, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 3668, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 3675, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 3703, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 3706, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 3709, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 3712, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1514 (ref. '1') (Obsoleted by RFC 2790) ** Obsolete normative reference: RFC 2248 (ref. '2') (Obsoleted by RFC 2788) ** Obsolete normative reference: RFC 1566 (ref. '3') (Obsoleted by RFC 2249, RFC 2789) ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Informational RFC: RFC 2039 (ref. '8') ** Obsolete normative reference: RFC 2044 (ref. '9') (Obsoleted by RFC 2279) -- Possible downref: Non-RFC (?) normative reference: ref. '11' -- Possible downref: Non-RFC (?) normative reference: ref. '12' ** Obsolete normative reference: RFC 2257 (ref. '13') (Obsoleted by RFC 2741) ** Downref: Normative reference to an Historic RFC: RFC 1227 (ref. '14') ** Obsolete normative reference: RFC 1228 (ref. '15') (Obsoleted by RFC 1592) ** Downref: Normative reference to an Experimental RFC: RFC 1592 (ref. '16') ** Obsolete normative reference: RFC 1700 (ref. '17') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 2028 (ref. '18') (Obsoleted by RFC 9281) -- Possible downref: Non-RFC (?) normative reference: ref. '19' ** Obsolete normative reference: RFC 2271 (ref. '20') (Obsoleted by RFC 2571) ** Obsolete normative reference: RFC 2275 (ref. '21') (Obsoleted by RFC 2575) Summary: 25 errors (**), 0 flaws (~~), 9 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 April 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 28 the "1id-abstracts.txt" listing contained in the Internet-Drafts 29 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 30 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au 31 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu 32 (US West Coast). 34 Copyright Notice 36 Copyright (C) The Internet Society (1998). All Rights Reserved. 38 Abstract 40 This memo defines an experimental portion of the Management 41 Information Base (MIB) for use with network management protocols in 42 the Internet Community. In particular, it defines objects used for 43 the management of applications. This MIB complements the System 44 Application MIB, providing for the management of applications' common 45 attributes which could not typically be observed without the 46 cooperation of the software being managed. 48 Table of Contents 50 1. Introduction ................................................ 3 51 2. Overview .................................................... 3 52 3. Architecture ................................................ 4 53 3.1. Relationships to other MIBs ............................... 4 54 3.1.1. Relationship to the System Application MIB .............. 4 55 3.1.2. Relationship to the Host Resources MIB .................. 5 56 3.1.3. Relationship to NSM ..................................... 5 57 4. MIB Structure ............................................... 5 58 4.1. The service-level tables .................................. 7 59 4.1.1. The service name to service instance table .............. 7 60 4.1.2. The service instance to service name table .............. 8 61 4.2. The I/O channel group ..................................... 8 62 4.2.1. The open channels table ................................. 9 63 4.2.2. The open files table .................................... 9 64 4.2.3. The open connections table .............................. 10 65 4.2.4. The transaction stream summary table .................... 10 66 4.2.5. The transaction flow statistics table ................... 12 67 4.2.6. The transaction kind statistics table ................... 12 68 4.3. The former channel group .................................. 12 69 4.3.1. The former channel control table ........................ 12 70 4.3.2. The former channel table ................................ 13 71 4.3.3. The former connection table ............................. 13 72 4.3.4. The former file table ................................... 13 73 4.3.5. The transaction history tables .......................... 13 74 4.4. The running element status and control group .............. 13 75 4.4.1. The running application element status table ............ 13 76 4.4.2. The running application element control table ........... 14 77 5. Definitions ................................................. 14 78 6. Implementation Issues ....................................... 77 79 7. Intellectual Property ....................................... 77 80 8. Acknowledgements ............................................ 78 81 9. Security Considerations ..................................... 78 82 10. References ................................................. 78 83 11. Authors' Addresses ......................................... 80 84 12. Full Copyright Statement ................................... 81 86 1. Introduction 88 This document furthers the work begun in the systems application mib 89 [10]. 91 The development of [1], [2], [3], [4], and [8] provides us with a 92 base of experience in making a variety of applications visible to 93 management; this specification abstracts out the common aspects of 94 applications management and provides a generic base usable for the 95 management of almost any application. 97 2. Overview 99 Due to the design decision to not require application 100 instrumentation, many important topics were not handled in system 101 application MIB [10]. The following topics are within the scope of 102 this document: 104 - Support for generic application throughput 105 measurements; 107 - Providing MIB definitions that allow managed entities 108 to report what they considered to be units of work; 110 - Providing support for generic application response time 111 monitoring capabilities; 113 - Provide explicit support for the management of 114 applications distributed within a single managed system 115 ("local" distribution); 117 - Address generic resource management issues, including: 119 - files in use; 121 - I/O statistics (from the application's 122 perspective, not at the operating system or 123 device driver level); 125 - application-layer networking resource usage 127 - Facilities for the control of applications, including: 129 - Stopping application elements 131 - Suspending and resuming application elements; 133 - Requesting reconfiguration (e.g., SIGHUP). 135 Note that these issues are addressed at least in part by other (non- 136 IETF) standards work, including [11] and [12]. 138 3. Architecture 140 Object-oriented modeling techniques like subclassing and multiple 141 inheritance can be emulated in the SNMP information model through the 142 use of tables with common indexes. 144 The challenge for the developer of management applications is to 145 recognize those situations in which various aspects of a single 146 logical resource are represented in several different tables, 147 possibly defined in different MIBs. 149 Most of the management information defined here may pertain to any 150 number of applications in a managed system. The simplest way of 151 supporting this requirement within the SNMP information model is to 152 use tables. This means that the management information for a 153 particular resource may be found in one or more rows of one or more 154 tables; the fact that this information pertains to a single resource 155 may be inferred from the index values used, possibly with the support 156 of mapping tables. This also means that a single table may contain 157 management information relevant to a number of applications. This 158 has significant implementation implications; see the implementation 159 issues section below for more information. 161 3.1. Relationships to other MIBs 163 This section outlines the relationships of the components of this MIB 164 (usually in the form of common indexing structures) to: 166 - the systems applications MIB [10] 168 - the host resources MIB [1] 170 - the network services monitoring MIB [2] 172 3.1.1. Relationship to the System Application MIB 174 The system application MIB defines attributes for management of 175 applications which can be realized without instrumenting the 176 application itself. This specification extends that framework to 177 include additional attributes which will typically require 178 instrumentation within the managed resource. The sysApplRunElmtIndex 179 is the key connection between these two MIBs; it is essential that 180 implementations of this MIB and of the system applications MIB 181 running concurrently on a given platform employ a consistent policy 182 for assigning this value to identify running application elements. 184 3.1.2. Relationship to the Host Resources MIB 186 The Host Resources MIB [1] supplies information on the hardware, 187 operating system, installed and running software on a host. 189 The Host Resources MIB has three hardware groups ("hrSystem", 190 "hrStorage" and "hrDevice") and three software groups ("hrSWRun", 191 "hrSWRunPerf" and "hrSWInstalled"). Of these, the software groups 192 are of greatest significance to this MIB. 194 The software groups define management information on the software 195 used in the system. The information provided is grouped into (1) the 196 currently running, (2) the performance and (3) the installed 197 applications. 199 The index "hrSWRunIndex" used in the "hrSWRunTable" and other tables 200 to identify running software by process identifier (or equivalent) 201 relates information in the Host Resources MIB to information in the 202 System Applications MIB and this MIB. It is essential that the 203 values assigned to hrSWRunIndex from the Host Resources MIB be 204 consistent with the values used for sysApplRunElmtIndex. 206 3.1.3. Relationship to NSM 208 The Network Services Monitoring MIB [2] is defined as the base set of 209 attributes for managing network applications. The Application MIB 210 includes information normally obtainable only from the managed 211 resource itself, rather than the supporting system. Due to 212 differences in index representation, the relationship between the 213 Network Services Monitoring MIB and the Application MIB is not 214 formally defined. 216 4. MIB Structure 218 This MIB is organized into several groups, which in turn are 219 organized into tables to provide the monitoring and control of 220 information relevant to the management of applications. The groups 221 model: 223 - the service-level view of applications 225 - information on open channels (files, connections, 226 transaction streams) in use by applications 228 - historical information on former channels 230 - process-level status and control information 232 These groups are organized into various tables. Information for a 233 particular running managed application appears in the form of entries 234 in the appropriate tables. The tables are: 236 - the tables providing a service-level view, including: 238 - the service name to service instance table 240 - the service instance to service name table 242 - the service instance to running application 243 element table 245 - the running application element to service 246 instance table 248 - the tables providing information on I/O channels, 249 including: 251 - the table of open channels 253 - the table of open files 255 - the open connections table 257 - the transaction statistics tables 259 - historical information on I/O channels 261 - the running application element status and control 262 group 264 - the running application element status table 266 - the running application element control table 268 In order to support SNMPv1, SNMPv2, and SNMPv3 environments, in cases 269 where counter objects may potentially advance very rapidly, where 270 sixty-four bit counters have been used thirty-two bit counters 271 reporting the low-order thirty-two bits of the value have also been 272 defined. 274 Since rows in most of these tables will come and go with the running 275 application elements whose information is contained in them, 276 sysUpTime.0 is not appropriate as a discontinuity indicator for 277 counters in these tables. By defining separate discontinuity 278 indicators for the rows in these tables, entries can come and go as 279 needed without causing other objects to appear to have 280 discontinuities. As required by [5], the discontinuity indicators 281 for the various information objects in these tables are identified in 282 the relevant DESCRIPTION clauses. Note that a discontinuity in one 283 of these counters does not imply a sysUpTime.0 discontinuity, nor 284 does a sysUpTime.0 discontinuity imply a discontinuity in any of 285 these counters. 287 4.1. The service-level tables 289 The service-level tables permit the identification of one or more 290 instances of named services on a system, and the association of 291 running application elements to these services. 293 Service names are represented as human-readable strings, using values 294 assigned by IANA where possible. The allocation of unique values for 295 service instance identifiers is a local administrative issue; the 296 values allocated must be constant for the lifetime of the service 297 instance, and re-use of values should be avoided. 299 It is important to understand that a service is not the same thing as 300 a protocol. Rather, some services may be at least partially 301 described by the protocol(s) used to provide that service. 303 In deciding what should or should not be considered a service, the 304 following factors merit consideration: 306 - is there an identifiable set of resources associated 307 with providing this service? 309 - is there a reasonably long-lived server or client 310 process? 312 Following this reasoning, one can see where SMTP and HTTP service 313 providers would be good candidates for classification as services for 314 purposes of application management, where finger probably would not. 315 Of course, implementors of this MIB are free to define additional 316 services. An applicability statement may be an appropriate vehicle 317 for standardizing how a specific service's information is reported 318 using this MIB. 320 4.1.1. The service name to service instance table 322 The service name to service instance table uses the service name as 323 its primary key, and the service instance identifier as its secondary 324 key. It facilitates the identification and lookup of the instances 325 of a given service in a system. 327 4.1.2. The service instance to service name table 329 The service instance to service name table uses the service instance 330 identifier as its primary key, and the service name as its secondary 331 key. Given a service instance identifier, it facilitates the lookup 332 of the name of the service being provided. 334 4.1.3. The service instance to running application element table 336 The service instance to running application element table uses the 337 service instance identifier as its primary key, and the running 338 application element index as its secondary key. This facilitates the 339 identification of the set of running application elements providing a 340 given instance of a service. 342 4.1.4. The running application element to service instance table 344 The running application element to service instance table uses the 345 running application element index as its primary key and the service 346 instance identifier as its secondary key. It identifies the set of 347 services provided by a given running application element. 349 4.2. The I/O channel group 351 Information processed by an application can be modeled using the 352 concept of a channel. Two kinds of channels, for example, are files 353 and network connections. 355 +-------+ 356 | File | 357 +---------+ /+-------+ 358 +-------------+ | Generic | / 359 | transaction |----| I/O |-------< 360 | stream | | Channel | \ +------------+ 361 +-------------+ +---------+ \ | open or | 362 \| listening | 363 | connection | 364 +------------+ 366 For each entry in the open channel table, there will be a 367 corresponding entry in either the open file table or the open 368 connection table. 370 The information flowing on a channel may be structured as 371 transactions. When the information flow on a channel is being 372 monitored as a transaction stream, an entry in the transaction stream 373 table will represent this fact and the associated information about 374 that stream. 376 To facilitate traversal of these tables and retrieval of information 377 relevant to a specific running application element or service 378 instances, the initial indexes of these tables are the same. In each 379 case, the first index determines whether the second index is 380 interpreted as a running application element identifier or as a 381 service instance identifier. The third index serves to uniquely 382 identify a channel (and consequently, an open connection or file) in 383 the context of a running application element or service instance. 385 The transaction stream summary table contains per-stream summaries of 386 transaction statistics. The transaction flow statistics table 387 contains statistics broken into both transmit and receive counts for 388 requests and responses on each stream. The transaction kind 389 statistics table contains information further broken down by 390 transaction kind. 392 The transaction tables have a common structure for their indexing, 393 with additional indexes added for increasing detail. The initial 394 three indexes are the same as all the other tables in this group, 395 serving to uniquely identify each transaction stream. 397 4.2.1. The open channels table 399 The following information is available in this table: 401 - time at which the channel was opened 403 - number of read requests 405 - number of bytes read 407 - time at which most recent read operation was initiated 409 - number of write requests 411 - number of bytes written 413 - time at which most recent write operation was initiated 415 4.2.2. The open files table 417 The open files table contains one entry for each file in use by a 418 manageable running application element. (See [10] for a detailed 419 definition of a running application element.) The purpose of this 420 table is to identify the files in use and to record information 421 peculiar to files not already covered in the open channel table. 423 If multiple running application elements open the same file, there 424 will be an entry for each running application element opening that 425 file. Similarly, if a running application element opens a file 426 multiple times, there will be an entry in this table for the file 427 corresponding to each open. 429 The task of combining the information for file activity from this 430 table (organized by running application element) into per-application 431 statistics can be accomplished by a manager using the System 432 Application MIB's [10] sysApplInstallPkgTable to find the installed 433 application, the sysApplRunTable to find the running instances of 434 that application, and the sysApplElmtRunTable to find the relevant 435 values of sysApplElmtRunIndex. The manager, armed with a set of 436 values for sysApplElmtRunIndex, is now able to retrieve the relevant 437 portions of the applOpenFileTable and other tables in this MIB. 439 The following information is available in this table: 441 - file name 443 - file size 445 - current mode (read/write) of this file 447 By convention, the names "stdin", "stdout" and "stderr" are used when 448 these streams cannot be resolved to actual file names. 450 4.2.3. The open connections table 452 This table provides information on channels that are open connections 453 or listeners. 455 The following information is available for each connection: 457 - identification of the transport protocol in use 459 - near-end address and port 461 - far-end address and port 463 - identification of the application layer protocol in use 465 4.2.4. The transaction stream summary table 467 The transaction stream summary table contains per-stream summaries of 468 transaction statistics. The simple model of a transaction used here 469 looks like this: 471 invoker | Request | performer 472 | - - - - - - > | 473 | | 474 | Response | 475 | < - - - - - - | 476 | | 478 Since in some protocols it is possible for an entity to take on both 479 the invoker and performer roles, information here is accumulated for 480 transmitted and received requests, as well as for transmitted and 481 received responses. Counts are maintained for both transactions and 482 bytes transferred. The information represented in this table 483 includes: 485 - identification of the underlying connection or file 486 used for this transaction stream 488 - a human-readable description of this stream 490 - a human-readable description of this stream's notion of 491 what a unit of work is 493 - the cumulative amount of time spent (as an operation 494 invoker) waiting for responses (from queueing of 495 request to arrival of first response) 497 - the cumulative amount of time spent (as an operation 498 invoker) receiving responses (time from the arrival of 499 the first response to the arrival of the last response 500 in a series of responses to a particular request) 502 - the cumulative amount of time spent (as an operation 503 performer) handling requests (time from receipt of 504 request to queueing of first outgoing response) 506 - the cumulative amount of time spent (as an operation 507 performer) sending responses (time from queuing of 508 first response to the last response in a series of 509 responses to a particular request) 511 - the cumulative number of transactions initiated (as an 512 invoker) 514 - the cumulative number of transactions processed (as a 515 performer) 517 4.2.5. The transaction flow statistics table 519 The transaction flow statistics table contains statistics broken into 520 both transmit and receive counts for requests and responses on each 521 stream. In addition to the service instance / running application 522 element and transaction stream identifier indexes, rows in this table 523 are indexed by flow direction (transmit or receive) and role 524 (requests and responses). The information in this table includes: 526 - the number of transactions processed 528 - the number of bytes processed 530 - the time at which the most recent transaction was 531 processed in this flow 533 4.2.6. The transaction kind statistics table 535 The transaction kind statistics table contains summary information 536 organized by direction, request/response, and transaction kind for 537 each stream. The indexing of this table is like that of the 538 transaction flow table, with the addition of a transaction kind 539 index. 541 - number of transactions processed 543 - number of bytes processed 545 - the time at which the most recent transaction of this 546 kind in this direction in this stream was processed 548 4.3. The former channel group 550 The former channel group has several tables. The former channel 551 control table controls the retention of history information by a 552 running application element or service instance. The remaining 553 tables parallel the structure of the channel group, with one 554 significant difference in indexing structure. The closed channel 555 index is independent from the open channel index. 557 4.3.1. The former channel control table 559 The former channel control table provides control over the 560 accumulation of information on former connections for running 561 application elements and service instances. For each one, this 562 table, indexed by the running application element or service instance 563 index, controls whether information on former channels is 564 accumulated, how many of these history records are retained, how long 565 these are retained (within the lifetime of the process), and a count 566 of history entries that were deleted before their expiration time in 567 order to make room for new entries. 569 4.3.2. The former channel table 571 The former channel table provides historical information on channels 572 that have been closed. The number and lifetime of these entries is 573 controlled, for each running application element or service instance, 574 by the former channel control table. Most of the information in this 575 table corresponds to information in the open channel table. 577 For the connection or file-specific aspects of a given former 578 channel, an entry will exist in the former connection table or in the 579 former file table. 581 4.3.3. The former connection table 583 For formerly open channels that were connections, connection-specific 584 historical information is kept in the former connection table. For 585 each entry in the former connection table, there will be an 586 identically indexed entry in the former channel table. 588 4.3.4. The former file table 590 For formerly open channels that were files, file-specific historical 591 information is kept in the former file table. For each entry in the 592 former file table, there will be an identically indexed entry in the 593 former channel table. 595 4.3.5. The transaction history tables 597 Two tables provide per-transaction-kind breakdowns for channels 598 carrying transaction-structured flows. These tables are analogous to 599 the transaction flow and kind statistics tables, with similar index 600 structures. 602 4.4. The running element status and control group 604 The running application element status and control group has two 605 tables. 607 4.4.1. The running application element status table 609 This table provides information for a running application element. 610 Indexed by the sysApplElmtRunIndex, an entry in this table reports 611 useful information on that running element's resource usage. Entries 612 in this table contain: 614 - current heap usage for this running application element 616 - current number of open network connections for this 617 running application element 619 - the most recent error status message issued by this 620 running application element 622 Note that other information, such as the current number of open files 623 for this running application element, is available from the 624 sysapplElmtRunTable in [10]. 626 4.4.2. The running application element control table 628 This table provides rudimentary control over a running application 629 element. Indexed by the sysApplElmtRunIndex, an entry in this table 630 gives a manager with appropriate permissions the ability to suspend 631 and resume processing by this running element, the ability to request 632 reconfiguration, and the ability to terminate the running element. 634 Variables in this table include: 636 - a suspend/resume control 638 - a reconfiguration request control 640 - a termination request control 642 5. Definitions 644 APPLICATION-MIB DEFINITIONS ::= BEGIN 646 IMPORTS 647 MODULE-IDENTITY, OBJECT-TYPE, 648 Counter64, Counter32, Gauge32, 649 mib-2, Unsigned32 FROM SNMPv2-SMI 651 DateAndTime, TEXTUAL-CONVENTION, 652 TAddress, TestAndIncr, TDomain, 653 TimeStamp, TruthValue FROM SNMPv2-TC 655 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 657 MODULE-COMPLIANCE, OBJECT-GROUP 658 FROM SNMPv2-CONF 660 LongUtf8String, sysApplElmtRunIndex FROM SYSAPPL-MIB; 662 applicationMib MODULE-IDENTITY 663 LAST-UPDATED "9804180336Z" 664 ORGANIZATION "Application MIB Working Group" 665 CONTACT-INFO 666 "http://www.ietf.org/html.charters/applmib-charter.html 668 Randy Presuhn 669 BMC Software, Inc. 670 965 Stewart Drive 671 Sunnyvale, CA 94086 672 USA 674 Telephone: +1 408 616-3100 675 Facsimile: +1 408 616-3101 676 EMail: rpresuhn@bmc.com 677 " 678 DESCRIPTION 679 "This MIB defines objects representing generic aspects of 680 applications that are of interest to management but typically 681 require instrumentation within managed application elements. 682 " 683 ::= { mib-2 ??? } -- IANA will make official assignment 685 -- 686 -- Registration hierarchy for this MIB 687 -- 688 applicationMibObjects OBJECT IDENTIFIER ::= 689 { applicationMib 1 } 691 applicationMibTraps OBJECT IDENTIFIER ::= 692 { applicationMib 2 } 694 applicationMibConformance OBJECT IDENTIFIER ::= 695 { applicationMib 3 } 697 -- 698 -- Groups defined in this MIB 699 -- 700 applServiceGroup OBJECT IDENTIFIER ::= 701 { applicationMibObjects 1 } 703 applChannelGroup OBJECT IDENTIFIER ::= 704 { applicationMibObjects 2 } 706 applPastChannelGroup OBJECT IDENTIFIER ::= 707 { applicationMibObjects 3 } 709 applElmtRunControlGroup OBJECT IDENTIFIER ::= 710 { applicationMibObjects 4 } 712 Unsigned64 ::= TEXTUAL-CONVENTION 713 STATUS current 714 DESCRIPTION 715 "A non-negative 64-bit bit integer." 716 SYNTAX Counter64 718 -- **************************************************************** 719 -- 720 -- applServiceGroup - 721 -- 722 -- The service-level tables permit the identification of one 723 -- or more instances of named services on a system, and the 724 -- association of running application elements to services. 725 -- 726 -- **************************************************************** 728 -- **************************************************************** 729 -- 730 -- The service name to service instance table 731 -- 732 -- **************************************************************** 734 applSrvNameToSrvInstTable OBJECT-TYPE 735 SYNTAX SEQUENCE OF ApplSrvNameToSrvInstEntry 736 MAX-ACCESS not-accessible 737 STATUS current 738 DESCRIPTION 739 "The service name to service instance table uses 740 service name as its primary key, and service instance 741 identifier as its secondary key. It facilitates the 742 identification and lookup of the instances a given 743 service in a system." 744 ::= { applServiceGroup 1 } 746 applSrvNameToSrvInstEntry OBJECT-TYPE 747 SYNTAX ApplSrvNameToSrvInstEntry 748 MAX-ACCESS not-accessible 749 STATUS current 750 DESCRIPTION 751 "An applSrvNameToSrvInstEntry identifies an instance of 752 a given service. The allocation and reservation 753 of unique values for applSrvIndex is an administrative 754 issue. 756 An applSrvNameToSrvInstEntry exists for the lifetime of 757 that instance of that service; the index values may not 758 change during that lifetime. " 759 INDEX { applSrvName, applSrvIndex } 760 ::= { applSrvNameToSrvInstTable 1 } 762 ApplSrvNameToSrvInstEntry ::= SEQUENCE 763 { 764 applSrvInstQual SnmpAdminString 765 } 767 applSrvInstQual OBJECT-TYPE 768 SYNTAX SnmpAdminString 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION 772 "The value of applSrcInstQual provides additional 773 information about this particular instance of this 774 service. 776 Although not used for indexing purposes, the value of 777 this attribute should be sufficiently unique to be 778 helpful to an administrator in distinguishing among 779 service instances. " 780 ::= { applSrvNameToSrvInstEntry 1 } 782 -- **************************************************************** 783 -- 784 -- Service instance to Service Name table 785 -- 786 -- **************************************************************** 788 applSrvInstToSrvNameTable OBJECT-TYPE 789 SYNTAX SEQUENCE OF ApplSrvInstToSrvNameEntry 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "The service instance to service name table uses 794 service instance identifier as its primary key, and 795 service name as its secondary key. Given a service 796 instance identifier, it facilitates the lookup of the 797 name of the service being provided." 798 ::= { applServiceGroup 2 } 800 applSrvInstToSrvNameEntry OBJECT-TYPE 801 SYNTAX ApplSrvInstToSrvNameEntry 802 MAX-ACCESS not-accessible 803 STATUS current 804 DESCRIPTION 805 "An applSrvInstToSrvNameEntry maps a service instance 806 identifier back to a service name." 807 INDEX { applSrvIndex, applSrvName } 808 ::= { applSrvInstToSrvNameTable 1 } 810 ApplSrvInstToSrvNameEntry ::= SEQUENCE 811 { 812 applSrvName SnmpAdminString 813 } 815 applSrvName OBJECT-TYPE 816 SYNTAX SnmpAdminString 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "The human-readable name of a service. Where possible, 821 the official protocol name as assigned by IANA or other 822 authority should be used. 823 " 824 ::= { applSrvInstToSrvNameEntry 1 } 826 -- **************************************************************** 827 -- 828 -- The service instance to running application element table 829 -- 830 -- **************************************************************** 832 applSrvInstToRunApplElmtTable OBJECT-TYPE 833 SYNTAX SEQUENCE OF ApplSrvInstToRunApplElmtEntry 834 MAX-ACCESS not-accessible 835 STATUS current 836 DESCRIPTION 837 "The service instance to running application element 838 table uses the service instance identifier as its primary 839 key, and the running application element index as its 840 secondary key. This facilitates the identification 841 of the set of running application elements providing a 842 given instance of a service." 843 ::= { applServiceGroup 3 } 845 applSrvInstToRunApplElmtEntry OBJECT-TYPE 846 SYNTAX ApplSrvInstToRunApplElmtEntry 847 MAX-ACCESS not-accessible 848 STATUS current 849 DESCRIPTION 850 "An applSrvInstToRunApplElmtEntry identifies a running 851 application element providing an instance of a service. 852 Note that there may be multiple running application 853 elements involved in the provision of an instance of 854 a service." 855 INDEX { applSrvIndex, sysApplElmtRunIndex } 856 ::= { applSrvInstToRunApplElmtTable 1 } 858 ApplSrvInstToRunApplElmtEntry ::= SEQUENCE 859 { 860 applSrvIndex Unsigned32 861 } 863 applSrvIndex OBJECT-TYPE 864 SYNTAX Unsigned32 (1..'ffffffff'h) 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "An applSrvIndex is the system-unique identifier of 869 an instance of a service. The value is unique not only 870 across all instances of a given service, but also across 871 all services in a system. 873 Re-use of values for this index should be avoided. 874 No two service instances in a given system shall 875 concurrently have the same value for this index. 877 The value zero is excluded from the set of permitted 878 values for this index. This allows other tables to 879 potentially represent things which cannot be associated 880 with a specific service instance. 881 " 882 ::= { applSrvInstToRunApplElmtEntry 1 } 884 -- **************************************************************** 885 -- 886 -- The running application element to service instance table 887 -- 888 -- **************************************************************** 889 applRunApplElmtToSrvInstTable OBJECT-TYPE 890 SYNTAX SEQUENCE OF ApplRunApplElmtToSrvInstEntry 891 MAX-ACCESS not-accessible 892 STATUS current 893 DESCRIPTION 894 "The running application element to service instance 895 table uses the running application element index as 896 its primary key and the service instance identifier as 897 its secondary key. It identifies the set of services 898 provided by a given running application element." 899 ::= { applServiceGroup 4 } 901 applRunApplElmtToSrvInstEntry OBJECT-TYPE 902 SYNTAX ApplRunApplElmtToSrvInstEntry 903 MAX-ACCESS not-accessible 904 STATUS current 905 DESCRIPTION 906 "An applRunApplElmtToSrvInstEntry serves to identify an 907 instance of a service being provided by a given running 908 application element. Note that a particular running 909 application element may provide multiple services." 910 INDEX { sysApplElmtRunIndex, applSrvInstance } 911 ::= { applRunApplElmtToSrvInstTable 1 } 913 ApplRunApplElmtToSrvInstEntry ::= SEQUENCE 914 { 915 applSrvInstance Unsigned32 916 } 918 applSrvInstance OBJECT-TYPE 919 SYNTAX Unsigned32 (1..'ffffffff'h) 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "An applSrvInstance is the system-unique identifier of an 924 instance of a service. The value is unique not only 925 across all instances of a given service, but also across 926 all services. 928 Re-use of values for this index should be avoided. 929 No two service instances in a given system shall 930 concurrently have the same value for this index. 932 The value zero is excluded from the set of permitted 933 values for this index. This allows other tables to 934 potentially represent things which cannot be associated 935 with a specific service instance. 937 This attribute is semantically identical to 938 applSrvIndex." 939 ::= { applRunApplElmtToSrvInstEntry 1 } 941 -- **************************************************************** 942 -- 943 -- applChannelGroup - group with tables for I/O 944 -- 945 -- In this group, the common abstraction is the Channel. 946 -- Channels are realized as files or connections. 947 -- The information flowing on a channel can always be 948 -- measured in terms of a byte stream. Furthermore, for many 949 -- channels, this information may also be measured in terms 950 -- of transactions. 951 -- 952 -- For all of these tables, the first two indexes determines 953 -- whether what is being measured is for a single running 954 -- application element or for an instance of a service. 955 -- 956 -- The second index identifies the running application element 957 -- or service instance. 958 -- 959 -- The third index is the channel id, which uniquely identifies 960 -- a channel within the context of a running application element 961 -- or service instance. 962 -- 963 -- Any remaining indexes are table-specific. 964 -- 965 -- **************************************************************** 967 -- **************************************************************** 968 -- 969 -- applOpenChannelTable - Table of Open Channels 970 -- 971 -- **************************************************************** 973 applOpenChannelTable OBJECT-TYPE 974 SYNTAX SEQUENCE OF ApplOpenChannelEntry 975 MAX-ACCESS not-accessible 976 STATUS current 977 DESCRIPTION 978 "The applOpenChannelTable reports information on open 979 channels for running application elements 980 and for service instances. This table is 981 indexed by applElmtOrSvc, applElmtOrSvcId, and 982 applOpenChannelIndex. This effectively groups all 983 entries for a given running application element 984 or service instance together. ApplChannelIndex uniquely 985 identifies an open channel (and, consequently, a file 986 or connection) within the context of a particular 987 running application element or service instance. 989 Some of the information in this table is available 990 through both sixty-four and thirty-two bit counters. 991 The sixty-four bit counters are not accessible in 992 protocols that do not support this data type." 993 ::= { applChannelGroup 1 } 995 applOpenChannelEntry OBJECT-TYPE 996 SYNTAX ApplOpenChannelEntry 997 MAX-ACCESS not-accessible 998 STATUS current 999 DESCRIPTION 1000 "An applOpenChannelEntry indicates that a channel has been 1001 opened by this running application element or service 1002 instance and is still open. Note that if a file has been 1003 opened multiple times, even by the same process, it will 1004 have multiple channel entries." 1005 INDEX { applElmtOrSvc, applElmtOrSvcId, 1006 applOpenChannelIndex } 1007 ::= { applOpenChannelTable 1 } 1009 ApplOpenChannelEntry ::= SEQUENCE 1010 { 1011 applElmtOrSvc INTEGER, 1012 applElmtOrSvcId Unsigned32, 1013 applOpenChannelIndex Unsigned32, 1014 applOpenChannelOpenTime TimeStamp, 1015 applOpenChannelReadRequests Counter64, 1016 applOpenChannelReadRequestsLow Counter32, 1017 applOpenChannelReadFailures Counter32, 1018 applOpenChannelBytesRead Counter64, 1019 applOpenChannelBytesReadLow Counter32, 1020 applOpenChannelLastReadTime DateAndTime, 1021 applOpenChannelWriteRequests Counter64, 1022 applOpenChannelWriteRequestsLow Counter32, 1023 applOpenChannelWriteFailures Counter32, 1024 applOpenChannelBytesWritten Counter64, 1025 applOpenChannelBytesWrittenLow Counter32, 1026 applOpenChannelLastWriteTime DateAndTime 1027 } 1029 applElmtOrSvc OBJECT-TYPE 1030 SYNTAX INTEGER { service(1), 1031 element(2) } 1032 MAX-ACCESS not-accessible 1033 STATUS current 1034 DESCRIPTION 1035 "The applElmtOrSvc attribute serves as an index for tables 1036 that can hold information both for individual running 1037 application elements as well as for service instances. 1039 If the value is service(1), the row contains information 1040 gathered at the level of a service. 1042 If the value is element(2), the row contains information 1043 for an individual running application element." 1044 ::= { applOpenChannelEntry 1 } 1046 applElmtOrSvcId OBJECT-TYPE 1047 SYNTAX Unsigned32 (1..'ffffffff'h) 1048 MAX-ACCESS not-accessible 1049 STATUS current 1050 DESCRIPTION 1051 "The applElmtOrSvcId attribute is used as an index in 1052 conjunction with the applElmtOrSvc attribute. 1054 When the value of applElmtOrSvc is service(1), this 1055 attribute's value corresponds to that of applSrvIndex, 1056 when the value of applElmtOrSvc is element(2), this 1057 attribute's value corresponds to sysApplElmtRunIndex." 1058 ::= { applOpenChannelEntry 2 } 1060 applOpenChannelIndex OBJECT-TYPE 1061 SYNTAX Unsigned32 1062 MAX-ACCESS not-accessible 1063 STATUS current 1064 DESCRIPTION 1065 "This attribute serves to uniquely identify this open 1066 connection in the context of the running application 1067 element or service instance. Where suitable, the 1068 application's native descriptor number should be used." 1069 ::= { applOpenChannelEntry 3 } 1071 applOpenChannelOpenTime OBJECT-TYPE 1072 SYNTAX TimeStamp 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "This attribute records the value of sysUpTime.0 1077 when this channel was opened and this entry was added to 1078 this table. This attribute serves as a discontinuity 1079 indicator for the counter attributes in this entry 1080 and for any corresponding entries in the 1081 applOpenConnectionTable, applOpenFileTable, and the 1082 applTransactionStreamTable." 1083 ::= { applOpenChannelEntry 4 } 1085 applOpenChannelReadRequests OBJECT-TYPE 1086 SYNTAX Counter64 1087 UNITS "read requests" 1088 MAX-ACCESS read-only 1089 STATUS current 1090 DESCRIPTION 1091 "This attribute reports the number of read requests 1092 for this channel. All read requests for this channel 1093 by this entity, regardless of completion status, are 1094 included in this count. 1096 Read requests are counted in terms of system calls, 1097 rather than API calls. 1099 Discontinuities in this counter can be detected by 1100 monitoring the applOpenChannelOpenTime value for this 1101 entry." 1102 ::= { applOpenChannelEntry 5 } 1104 applOpenChannelReadRequestsLow OBJECT-TYPE 1105 SYNTAX Counter32 1106 UNITS "read requests" 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 "This attribute reports the low thirty-two bits of 1111 applOpenChannelReadRequests. 1113 Discontinuities in this counter can be detected by 1114 monitoring the applOpenChannelOpenTime value for this 1115 entry." 1116 ::= { applOpenChannelEntry 6 } 1118 applOpenChannelReadFailures OBJECT-TYPE 1119 SYNTAX Counter32 1120 UNITS "failed read requests" 1121 MAX-ACCESS read-only 1122 STATUS current 1123 DESCRIPTION 1124 "This attribute reports the number of failed read 1125 requests. 1127 Discontinuities in this counter can be detected by 1128 monitoring the applOpenChannelOpenTime value for this 1129 entry." 1130 ::= { applOpenChannelEntry 7 } 1132 applOpenChannelBytesRead OBJECT-TYPE 1133 SYNTAX Counter64 1134 UNITS "bytes" 1135 MAX-ACCESS read-only 1136 STATUS current 1137 DESCRIPTION 1138 "This attribute reports the number of bytes read from 1139 this channel. Only bytes successfully read are included 1140 in this count. 1142 Discontinuities in this counter can be detected by 1143 monitoring the applOpenChannelOpenTime value for this 1144 entry." 1145 ::= { applOpenChannelEntry 8 } 1147 applOpenChannelBytesReadLow OBJECT-TYPE 1148 SYNTAX Counter32 1149 UNITS "bytes" 1150 MAX-ACCESS read-only 1151 STATUS current 1152 DESCRIPTION 1153 "This attribute corresponds to the low thirty-two bits 1154 of applOpenChannelBytesRead. 1156 Discontinuities in this counter can be detected by 1157 monitoring the applOpenChannelOpenTime value for this 1158 entry." 1159 ::= { applOpenChannelEntry 9 } 1161 applOpenChannelLastReadTime OBJECT-TYPE 1162 SYNTAX DateAndTime 1163 MAX-ACCESS read-only 1164 STATUS current 1165 DESCRIPTION 1166 "This attribute reports the time of the most recent read 1167 request made by this entity, regardless of completion 1168 status, for this open channel. 1170 If no read requests have been made the value of this 1171 attribute shall be '0000000000000000'H " 1172 DEFVAL { '0000000000000000'H } 1173 ::= { applOpenChannelEntry 10 } 1175 applOpenChannelWriteRequests OBJECT-TYPE 1176 SYNTAX Counter64 1177 UNITS "write requests" 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "This attribute reports the number of write requests for 1182 this channel made by this entity. All write requests 1183 for this channel, regardless of completion status, are 1184 included in this count. 1186 Write requests are counted in terms of system calls, 1187 rather than API calls. 1189 Discontinuities in this counter can be detected by 1190 monitoring the applOpenChannelOpenTime value for this 1191 entry." 1192 ::= { applOpenChannelEntry 11 } 1194 applOpenChannelWriteRequestsLow OBJECT-TYPE 1195 SYNTAX Counter32 1196 UNITS "write requests" 1197 MAX-ACCESS read-only 1198 STATUS current 1199 DESCRIPTION 1200 "This attribute corresponds to the low thirty-two bits 1201 of applOpenChannelWriteRequests. 1203 Discontinuities in this counter can be detected 1204 by monitoring the applOpenChannelOpenTime value for 1205 this entry." 1206 ::= { applOpenChannelEntry 12 } 1208 applOpenChannelWriteFailures OBJECT-TYPE 1209 SYNTAX Counter32 1210 UNITS "failed write requests" 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "This attribute reports the number of failed write 1215 requests. 1217 Discontinuities in this counter can be detected 1218 by monitoring the applOpenChannelOpenTime value for 1219 this entry." 1220 ::= { applOpenChannelEntry 13 } 1222 applOpenChannelBytesWritten OBJECT-TYPE 1223 SYNTAX Counter64 1224 UNITS "bytes" 1225 MAX-ACCESS read-only 1226 STATUS current 1227 DESCRIPTION 1228 "This attribute reports the number of bytes written to 1229 this channel. Only bytes successfully written (without 1230 errors reported by the system to the API in use by the 1231 application) are included in this count. 1233 Discontinuities in this counter can be detected by 1234 monitoring the applOpenChannelOpenTime value for this 1235 entry." 1236 ::= { applOpenChannelEntry 14 } 1238 applOpenChannelBytesWrittenLow OBJECT-TYPE 1239 SYNTAX Counter32 1240 UNITS "bytes" 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "This attribute corresponds to the low thirty-two bits 1245 of applOpenChannelBytesWritten. 1247 Discontinuities in this counter can be detected by 1248 monitoring the applOpenChannelOpenTime value for this 1249 entry." 1250 ::= { applOpenChannelEntry 15 } 1252 applOpenChannelLastWriteTime OBJECT-TYPE 1253 SYNTAX DateAndTime 1254 MAX-ACCESS read-only 1255 STATUS current 1256 DESCRIPTION 1257 "This attribute reports the time of the most recent write 1258 request made by this running application element or 1259 service instance, regardless of completion status, for 1260 this open channel. 1262 If no write requests have been made, the value 1263 of this attribute shall be '0000000000000000'H " 1264 DEFVAL { '0000000000000000'H } 1265 ::= { applOpenChannelEntry 16 } 1267 -- **************************************************************** 1268 -- 1269 -- applOpenFileTable - Table of Open Files 1270 -- 1271 -- **************************************************************** 1273 applOpenFileTable OBJECT-TYPE 1274 SYNTAX SEQUENCE OF ApplOpenFileEntry 1275 MAX-ACCESS not-accessible 1276 STATUS current 1277 DESCRIPTION 1278 "The applOpenFileTable reports information on open files 1279 for service instances or application elements. This 1280 table is indexed by applElmtOrSvc and applElmtOrSvcId, 1281 effectively grouping all entries for a given running 1282 service instance or application element together, and 1283 by applOpenChannelIndex, uniquely identifying an open 1284 channel (and, consequently, a file) within the context 1285 of a particular service instance or application element. 1287 Elements in this table correspond to elements in the 1288 applOpenChannelTable that represent files. For rows in 1289 the applOpenChannelTable that do not represent files, 1290 corresponding rows in this table will not exist." 1291 ::= { applChannelGroup 2 } 1293 applOpenFileEntry OBJECT-TYPE 1294 SYNTAX ApplOpenFileEntry 1295 MAX-ACCESS not-accessible 1296 STATUS current 1297 DESCRIPTION 1298 "An applOpenFileEntry indicates that a file has been 1299 opened by this running application element and is 1300 still open. Note that if a file has been opened 1301 multiple times, even by the same process, it will have 1302 multiple entries." 1303 INDEX { applElmtOrSvc, applElmtOrSvcId, 1304 applOpenChannelIndex } 1305 ::= { applOpenFileTable 1 } 1307 ApplOpenFileEntry ::= SEQUENCE 1308 { 1309 applOpenFileName LongUtf8String, 1310 applOpenFileSizeHigh Unsigned32, 1311 applOpenFileSizeLow Unsigned32, 1312 applOpenFileMode INTEGER 1313 } 1315 applOpenFileName OBJECT-TYPE 1316 SYNTAX LongUtf8String 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "This attribute reports the name of this open file. 1321 Wherever practical, a fully qualified path name should 1322 be reported. 1324 The values 'stdin', 'stdout', and 'stderr' are reserved 1325 in accordance with common usage when the fully qualified 1326 path name cannot be determined." 1327 ::= { applOpenFileEntry 1 } 1329 applOpenFileSizeHigh OBJECT-TYPE 1330 SYNTAX Unsigned32 1331 UNITS "2^32 byte blocks" 1332 MAX-ACCESS read-only 1333 STATUS current 1334 DESCRIPTION 1335 "This file's current size in 2^32 byte blocks. 1337 For example, for a file with a total size of 4,294,967,296 1338 bytes, this attribute would have a value of 1; for a file 1339 with a total size of 4,294,967,295 bytes this attribute's 1340 value would be 0." 1341 ::= { applOpenFileEntry 2 } 1343 applOpenFileSizeLow OBJECT-TYPE 1344 SYNTAX Unsigned32 1345 UNITS "bytes" 1346 MAX-ACCESS read-only 1347 STATUS current 1348 DESCRIPTION 1349 "This file's current size modulo 2^32 bytes. 1351 For example, for a file with a total size of 1352 4,294,967,296 bytes this attribute would have a value 1353 of 0; for a file with a total size of 4,294,967,295 1354 bytes this attribute's value would be 4,294,967,295." 1356 ::= { applOpenFileEntry 3 } 1358 applOpenFileMode OBJECT-TYPE 1359 SYNTAX INTEGER { read(1), 1360 write(2), 1361 readWrite(3) } 1362 MAX-ACCESS read-only 1363 STATUS current 1364 DESCRIPTION 1365 "This attribute reports the current mode of this file from 1366 the perspective of this running application element. 1368 These values have the following meanings: 1370 read(1) - file opened for reading only 1371 write(2) - file opened for writing only 1372 readWrite - file opened for read and write. 1374 These values correspond to the POSIX/ANSI C library 1375 function fopen() 'type' parameter, using the following 1376 mappings: 1378 r -> read(1) 1379 w -> write(2) 1380 a -> write(2) 1381 + -> readWrite(3) 1382 " 1383 ::= { applOpenFileEntry 4 } 1385 -- **************************************************************** 1386 -- 1387 -- applOpenConnectionTable - Open Connection Table 1388 -- 1389 -- **************************************************************** 1391 applOpenConnectionTable OBJECT-TYPE 1392 SYNTAX SEQUENCE OF ApplOpenConnectionEntry 1393 MAX-ACCESS not-accessible 1394 STATUS current 1395 DESCRIPTION 1396 "The applOpenConnectionTable provides information about 1397 open and listening connections from the perspective 1398 of a running application element or service instance. 1399 Entries in this table are indexed by applElmtOrSvc, 1400 applElmtOrSvcID, and by applOpenChannelIndex, which 1401 serves to uniquely identify each connection in the 1402 context of a service instance or running application 1403 element. 1405 For each row in this table, a corresponding row will 1406 exist in the applOpenChannel table. For rows in the 1407 applOpenChannelTable which do not represent open or 1408 listening connections, no corresponding rows will exist 1409 in this table." 1410 ::= { applChannelGroup 3 } 1412 applOpenConnectionEntry OBJECT-TYPE 1413 SYNTAX ApplOpenConnectionEntry 1414 MAX-ACCESS not-accessible 1415 STATUS current 1416 DESCRIPTION 1417 "An applOpenConnectionEntry indicates that a running 1418 application element or service instance has an open 1419 connection. The entry has information describing that 1420 connection." 1421 INDEX { applElmtOrSvc, applElmtOrSvcId, 1422 applOpenChannelIndex } 1423 ::= { applOpenConnectionTable 1 } 1425 ApplOpenConnectionEntry ::= SEQUENCE 1426 { 1427 applOpenConnectionTransport TDomain, 1428 applOpenConnectionNearEndAddr TAddress, 1429 applOpenConnectionNearEndpoint SnmpAdminString, 1430 applOpenConnectionFarEndAddr TAddress, 1431 applOpenConnectionFarEndpoint SnmpAdminString, 1432 applOpenConnectionApplication SnmpAdminString 1433 } 1435 applOpenConnectionTransport OBJECT-TYPE 1436 SYNTAX TDomain 1437 MAX-ACCESS read-only 1438 STATUS current 1439 DESCRIPTION 1440 "The applOpenConnectionTransport attribute identifies the 1441 transport protocol in use for this connection. If it is 1442 not practical to determine the underlying transport, this 1443 attribute's value shall have a value of {0 0}." 1444 DEFVAL { { 0 0 } } 1445 ::= { applOpenConnectionEntry 1 } 1447 applOpenConnectionNearEndAddr OBJECT-TYPE 1448 SYNTAX TAddress 1449 MAX-ACCESS read-only 1450 STATUS current 1451 DESCRIPTION 1452 "The applOpenConnectionNearEndAddr attribute reports the 1453 transport address and port information for the near end 1454 of this connection. 1456 If the value is not known, the value has a length 1457 of zero." 1458 DEFVAL { "" } 1459 ::= { applOpenConnectionEntry 2 } 1461 applOpenConnectionNearEndpoint OBJECT-TYPE 1462 SYNTAX SnmpAdminString 1463 MAX-ACCESS read-only 1464 STATUS current 1465 DESCRIPTION 1466 "The applOpenConnectionNearEndpoint attribute reports the 1467 fully-qualified domain name and port information for the 1468 near end of this connection. 1470 The format of this attribute for TCP and UDP-based 1471 protocols is the fully-qualified domain name immediately 1472 followed by a colon which is immediately followed by 1473 the decimal representation of the port number. 1475 If the value is not known, the value has a length 1476 of zero." 1477 DEFVAL { "" } 1478 ::= { applOpenConnectionEntry 3 } 1480 applOpenConnectionFarEndAddr OBJECT-TYPE 1481 SYNTAX TAddress 1482 MAX-ACCESS read-only 1483 STATUS current 1484 DESCRIPTION 1485 "The applOpenConnectionFarEndAddr attribute reports the 1486 transport address and port information for the far end 1487 of this connection. 1489 If not known, as in the case of a connectionless 1490 transport, the value of this attribute shall be a 1491 zero-length string." 1492 DEFVAL { "" } 1493 ::= { applOpenConnectionEntry 4 } 1495 applOpenConnectionFarEndpoint OBJECT-TYPE 1496 SYNTAX SnmpAdminString 1497 MAX-ACCESS read-only 1498 STATUS current 1499 DESCRIPTION 1500 "The applOpenConnectionFarEndpoint attribute reports 1501 the fully-qualified domain name and port information 1502 for the far end of this connection. 1504 The format of this attribute for TCP and UDP-based 1505 protocols is the fully-qualified domain name immediately 1506 followed by a colon which is immediately followed by 1507 the decimal representation of the port number. 1509 If not known, as in the case of a connectionless 1510 transport, the value of this attribute shall be a 1511 zero-length string." 1512 DEFVAL { "" } 1513 ::= { applOpenConnectionEntry 5 } 1515 applOpenConnectionApplication OBJECT-TYPE 1516 SYNTAX SnmpAdminString 1517 MAX-ACCESS read-only 1518 STATUS current 1519 DESCRIPTION 1520 "The applOpenConnectionApplication attribute identifies 1521 the application layer protocol in use. If not known, 1522 the value of this attribute shall be a zero-length 1523 string. 1525 When possible, protocol names should be those used in 1526 the 'ASSIGNED NUMBERS' [17]. For example, an SMTP mail 1527 server would use 'SMTP'." 1528 DEFVAL { "" } 1529 ::= { applOpenConnectionEntry 6 } 1531 -- **************************************************************** 1532 -- 1533 -- applTransactionStreamTable - common 1534 -- information for transaction stream monitoring 1535 -- 1536 -- **************************************************************** 1538 applTransactionStreamTable OBJECT-TYPE 1539 SYNTAX SEQUENCE OF ApplTransactionStreamEntry 1540 MAX-ACCESS not-accessible 1541 STATUS current 1542 DESCRIPTION 1543 "The applTransactionStreamTable contains common 1544 information for transaction statistic accumulation." 1545 ::= { applChannelGroup 4 } 1547 applTransactionStreamEntry OBJECT-TYPE 1548 SYNTAX ApplTransactionStreamEntry 1549 MAX-ACCESS not-accessible 1550 STATUS current 1551 DESCRIPTION 1552 "An applTransactionStreamEntry contains information for 1553 a single transaction stream. A transaction stream 1554 can be a network connection, file, or other source 1555 of transactions." 1556 INDEX { applElmtOrSvc, applElmtOrSvcId, 1557 applOpenChannelIndex } 1558 ::= { applTransactionStreamTable 1 } 1560 ApplTransactionStreamEntry ::= SEQUENCE { 1561 applTransactStreamDescr SnmpAdminString, 1562 applTransactStreamUnitOfWork SnmpAdminString, 1563 applTransactStreamInvokes Counter64, 1564 applTransactStreamInvokesLow Counter32, 1565 applTransactStreamInvCumTime Counter32, 1566 applTransactStreamInvRspTime Counter32, 1567 applTransactStreamPerforms Counter64, 1568 applTransactStreamPerformsLow Counter32, 1569 applTransactStreamPrfCumTime Counter32, 1570 applTransactStreamPrfRspTime Counter32 } 1572 applTransactStreamDescr OBJECT-TYPE 1573 SYNTAX SnmpAdminString 1574 MAX-ACCESS read-only 1575 STATUS current 1576 DESCRIPTION 1577 "The applTransactStreamDescr attribute provides a 1578 human-readable description of this transaction stream. 1580 If no descriptive information is available, this 1581 attribute's value shall be a zero-length string." 1582 DEFVAL { "" } 1583 ::= { applTransactionStreamEntry 1 } 1585 applTransactStreamUnitOfWork OBJECT-TYPE 1586 SYNTAX SnmpAdminString 1587 MAX-ACCESS read-only 1588 STATUS current 1589 DESCRIPTION 1590 "The applTransactStreamUnitOfWork attribute provides a 1591 human-readable definition of what the unit of work is 1592 for this transaction stream. 1594 If no descriptive information is available, this 1595 attribute's value shall be a zero-length string." 1596 DEFVAL { "" } 1597 ::= { applTransactionStreamEntry 2 } 1599 applTransactStreamInvokes OBJECT-TYPE 1600 SYNTAX Counter64 1601 UNITS "transactions" 1602 MAX-ACCESS read-only 1603 STATUS current 1604 DESCRIPTION 1605 "Cumulative count of requests / invocations issued. 1607 Discontinuities in this counter can be detected 1608 by monitoring the corresponding instance of 1609 applOpenChannelOpenTime." 1610 ::= { applTransactionStreamEntry 3 } 1612 applTransactStreamInvokesLow OBJECT-TYPE 1613 SYNTAX Counter32 1614 UNITS "transactions" 1615 MAX-ACCESS read-only 1616 STATUS current 1617 DESCRIPTION 1618 "This counter corresponds to the low thirty-two 1619 bits of applTransactStreamInvokes. 1621 Discontinuities in this counter can be detected 1622 by monitoring the corresponding instance of 1623 applOpenChannelOpenTime." 1624 ::= { applTransactionStreamEntry 4 } 1626 applTransactStreamInvCumTime OBJECT-TYPE 1627 SYNTAX Counter32 1628 UNITS "milliseconds" 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "The applTransactStreamInvCumTime attribute reports the 1633 cumulative sum of the times measured between the 1634 transmission of requests and the receipt of (the first 1635 of) the corresponding response(s). 1637 Discontinuities in this counter can be detected 1638 by monitoring the corresponding instance of 1639 applOpenChannelOpenTime." 1640 ::= { applTransactionStreamEntry 5 } 1642 applTransactStreamInvRspTime OBJECT-TYPE 1643 SYNTAX Counter32 1644 UNITS "milliseconds" 1645 MAX-ACCESS read-only 1646 STATUS current 1647 DESCRIPTION 1648 "The applTransactStreamInvRspTime attribute reports the 1649 cumulative sum of the times measured between the receipt 1650 of the first and last of multiple responses to a request. 1652 For transaction streams which do not permit multiple 1653 responses to a single request, this attribute will be 1654 constant. 1656 Discontinuities in this counter can be detected 1657 by monitoring the corresponding instance of 1658 applOpenChannelOpenTime." 1659 ::= { applTransactionStreamEntry 6 } 1661 applTransactStreamPerforms OBJECT-TYPE 1662 SYNTAX Counter64 1663 UNITS "transactions" 1664 MAX-ACCESS read-only 1665 STATUS current 1666 DESCRIPTION 1667 "Cumulative count of transactions performed. 1669 Discontinuities in this counter can be detected 1670 by monitoring the corresponding instance of 1671 applOpenChannelOpenTime." 1672 ::= { applTransactionStreamEntry 7 } 1674 applTransactStreamPerformsLow OBJECT-TYPE 1675 SYNTAX Counter32 1676 UNITS "transactions" 1677 MAX-ACCESS read-only 1678 STATUS current 1679 DESCRIPTION 1680 "This counter reports the low thirty-two bits of 1681 applTransactStreamPerforms. 1683 Discontinuities in this counter can be detected 1684 by monitoring the corresponding instance of 1685 applOpenChannelOpenTime." 1686 ::= { applTransactionStreamEntry 8 } 1688 applTransactStreamPrfCumTime OBJECT-TYPE 1689 SYNTAX Counter32 1690 UNITS "milliseconds" 1691 MAX-ACCESS read-only 1692 STATUS current 1693 DESCRIPTION 1694 "The applTransactStreamPrfCumTime attribute reports the 1695 cumulative sum of the times measured between receipt 1696 of requests and the transmission of the corresponding 1697 responses. 1699 Discontinuities in this counter can be detected 1700 by monitoring the corresponding instance of 1701 applOpenChannelOpenTime." 1702 ::= { applTransactionStreamEntry 9 } 1704 applTransactStreamPrfRspTime OBJECT-TYPE 1705 SYNTAX Counter32 1706 UNITS "milliseconds" 1707 MAX-ACCESS read-only 1708 STATUS current 1709 DESCRIPTION 1710 "For each transaction performed, the elapsed time between 1711 when the first response is enqueued and when the last 1712 response is enqueued is added to this cumulative sum. 1714 For single-response protocols, the value of 1715 applTransactStreamPrfRspTime will be constant. 1717 Discontinuities in this counter can be detected 1718 by monitoring the corresponding instance of 1719 applOpenChannelOpenTime." 1720 ::= { applTransactionStreamEntry 10 } 1722 -- **************************************************************** 1723 -- 1724 -- applTransactFlowTable 1725 -- 1726 -- **************************************************************** 1728 applTransactFlowTable OBJECT-TYPE 1729 SYNTAX SEQUENCE OF ApplTransactFlowEntry 1730 MAX-ACCESS not-accessible 1731 STATUS current 1732 DESCRIPTION 1733 "The applTransactFlowTable contains entries, organized by 1734 application instance or running application element, 1735 direction of flow, and type (request/response) for each 1736 open transaction stream. 1738 The simple model of a transaction used here looks like 1739 this: 1741 invoker | Request | performer 1742 | - - - - - - > | 1743 | | 1744 | Response | 1745 | < - - - - - - | 1746 | | 1748 Since in some protocols it is possible for an entity 1749 to take on both the invoker and performer roles, 1750 information here is accumulated for transmitted and 1751 received requests, as well as for transmitted and 1752 received responses. Counts are maintained for both 1753 transactions and bytes transferred." 1754 ::= { applChannelGroup 5 } 1756 applTransactFlowEntry OBJECT-TYPE 1757 SYNTAX ApplTransactFlowEntry 1758 MAX-ACCESS not-accessible 1759 STATUS current 1760 DESCRIPTION 1761 "An applTransactFlowEntry reports transaction throughput 1762 information for requests or response in a particular 1763 direction (transmit / receive) for a transaction stream. 1765 Entries in this table correspond to those in the 1766 applTransactionStreamTable with identical values for the 1767 applElmtOrSvc, applElmtOrSvcId, and applOpenChannelIndex. 1769 For all counter objects in one of these entries, 1770 the corresponding (same value for applElmtOrSvc, 1771 applElmtOrSvcId, and applOpenChannelIndex) 1772 applOpenChannelOpenTime object serves as a discontinuity 1773 indicator. " 1774 INDEX { applElmtOrSvc, 1775 applElmtOrSvcId, 1776 applOpenChannelIndex, 1777 applTransactFlowDirection, 1778 applTransactFlowReqRsp } 1779 ::= { applTransactFlowTable 1 } 1781 ApplTransactFlowEntry ::= SEQUENCE { 1782 applTransactFlowDirection INTEGER, 1783 applTransactFlowReqRsp INTEGER, 1784 applTransactFlowTrans Counter64, 1785 applTransactFlowTransLow Counter32, 1786 applTransactFlowBytes Counter64, 1787 applTransactFlowBytesLow Counter32, 1788 applTransactFlowTime DateAndTime } 1790 applTransactFlowDirection OBJECT-TYPE 1791 SYNTAX INTEGER { transmit(1), 1792 receive(2) } 1793 MAX-ACCESS not-accessible 1794 STATUS current 1795 DESCRIPTION 1796 "The applTransactFlowDirection index serves to identify 1797 an entry as containing information pertaining to the 1798 transmit (1) or receive (2) flow of a transaction 1799 stream." 1800 ::= { applTransactFlowEntry 1 } 1802 applTransactFlowReqRsp OBJECT-TYPE 1803 SYNTAX INTEGER { request(1), 1804 response(2) } 1805 MAX-ACCESS not-accessible 1806 STATUS current 1807 DESCRIPTION 1808 "The value of the applTransactFlowReqRsp index indicates 1809 whether this entry contains information on requests 1810 (1), or responses (2)." 1811 ::= { applTransactFlowEntry 2 } 1813 applTransactFlowTrans OBJECT-TYPE 1814 SYNTAX Counter64 1815 UNITS "transactions" 1816 MAX-ACCESS read-only 1817 STATUS current 1818 DESCRIPTION 1819 "The applTransactFlowTrans attribute reports the number 1820 of request/response transactions (as indicated by 1821 the applTransactFlowReqRsp index) received/generated 1822 (as indicated by the applTransactFlowDirection index) 1823 that this service instance or running application 1824 element has processed for this transaction stream. 1826 Discontinuities in this counter can be detected 1827 by monitoring the corresponding instance of 1828 applOpenChannelOpenTime." 1829 ::= { applTransactFlowEntry 3 } 1831 applTransactFlowTransLow OBJECT-TYPE 1832 SYNTAX Counter32 1833 UNITS "transactions" 1834 MAX-ACCESS read-only 1835 STATUS current 1836 DESCRIPTION 1837 "This attribute corresponds to the low thirty-two 1838 bits of applTransactFlowTrans. 1840 Discontinuities in this counter can be detected 1841 by monitoring the corresponding instance of 1842 applOpenChannelOpenTime." 1843 ::= { applTransactFlowEntry 4 } 1845 applTransactFlowBytes OBJECT-TYPE 1846 SYNTAX Counter64 1847 UNITS "bytes" 1848 MAX-ACCESS read-only 1849 STATUS current 1850 DESCRIPTION 1851 "The applTransactFlowBytes attribute reports the number 1852 of request/response (as indicated by the 1853 applTransactFlowReqRsp index) bytes received/generated 1854 (as indicated by the applTransactFlowDirection index) 1855 handled by this application element or service instance 1856 on this transaction stream. 1858 All application layer bytes are included in this count, 1859 including any application layer wrappers, headers, or 1860 other overhead. 1862 Discontinuities in this counter can be detected 1863 by monitoring the corresponding instance of 1864 applOpenChannelOpenTime." 1865 ::= { applTransactFlowEntry 5 } 1867 applTransactFlowBytesLow OBJECT-TYPE 1868 SYNTAX Counter32 1869 UNITS "bytes" 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "This attribute corresponds to the low thirty-two 1874 bits of applTransactFlowBytes. 1876 Discontinuities in this counter can be detected 1877 by monitoring the corresponding instance of 1878 applOpenChannelOpenTime." 1879 ::= { applTransactFlowEntry 6 } 1881 applTransactFlowTime OBJECT-TYPE 1882 SYNTAX DateAndTime 1883 MAX-ACCESS read-only 1884 STATUS current 1885 DESCRIPTION 1886 "The applTransactFlowTime attribute records the time of 1887 the processing (receipt or transmission as indicated 1888 by the applTransactFlowDirection index) by this 1889 running application element or service instance of 1890 the most recent request/response (as indicated by 1891 the applTransactFlowReqRsp index) on this transaction 1892 stream. 1894 If no requests/responses been received/transmitted by 1895 this entity over this transaction stream, the value 1896 of this attribute shall be '0000000000000000'H " 1897 DEFVAL { '0000000000000000'H } 1898 ::= { applTransactFlowEntry 7 } 1900 -- **************************************************************** 1901 -- 1902 -- applTransactKindTable - transaction statistics broken down 1903 -- according to the kinds of transactions in each direction 1904 -- for a transaction stream. 1905 -- 1906 -- **************************************************************** 1908 applTransactKindTable OBJECT-TYPE 1909 SYNTAX SEQUENCE OF ApplTransactKindEntry 1910 MAX-ACCESS not-accessible 1911 STATUS current 1912 DESCRIPTION 1913 "The applTransactKindTable provides transaction statistics 1914 broken down by kinds of transaction. The definition of 1915 the kinds of transactions is specific to the application 1916 protocol in use, and may be documented in the form of an 1917 applicability statement. " 1918 ::= { applChannelGroup 6 } 1920 applTransactKindEntry OBJECT-TYPE 1921 SYNTAX ApplTransactKindEntry 1922 MAX-ACCESS not-accessible 1923 STATUS current 1924 DESCRIPTION 1925 "An applTransactKindEntry reports information for a 1926 specific service instance or running application 1927 element's use of a specific transaction stream in 1928 a particular direction in requests or responses 1929 (as indicated by the applTransactFlowReqRsp index) 1930 broken down by transaction kind, as indicated by the 1931 applTransactKind index. 1933 Discontinuities in any of the counters in an entry can 1934 be detected by monitoring the corresponding instance of 1935 applOpenChannelOpenTime." 1937 INDEX { applElmtOrSvc, 1938 applElmtOrSvcId, 1939 applOpenChannelIndex, 1940 applTransactFlowDirection, 1941 applTransactFlowReqRsp, 1942 applTransactKind } 1943 ::= { applTransactKindTable 1 } 1945 ApplTransactKindEntry ::= SEQUENCE 1946 { 1947 applTransactKind SnmpAdminString, 1948 applTransactKindTrans Counter64, 1949 applTransactKindTransLow Counter32, 1950 applTransactKindBytes Counter64, 1951 applTransactKindBytesLow Counter32, 1952 applTransactKindTime DateAndTime 1953 } 1955 applTransactKind OBJECT-TYPE 1956 SYNTAX SnmpAdminString (SIZE (1 .. 32)) 1957 MAX-ACCESS not-accessible 1958 STATUS current 1959 DESCRIPTION 1960 "The applTransactKind index is the human-readable 1961 identifier for a particular transaction kind within 1962 the context of an application protocol. The values 1963 to be used for a particular protocol may be identified 1964 in an applicability statement." 1965 ::= { applTransactKindEntry 1 } 1967 applTransactKindTrans OBJECT-TYPE 1968 SYNTAX Counter64 1969 UNITS "transactions" 1970 MAX-ACCESS read-only 1971 STATUS current 1972 DESCRIPTION 1973 "The applTransactKindTrans attribute reports the number 1974 of request/response (as indicated by the 1975 applTransactFlowReqRsp index) transactions 1976 received/generated (as indicated by the 1977 applTransactFlowDirection index) handled by this 1978 application instance or application element on this 1979 transaction stream for this transaction kind. 1981 Discontinuities in this counter can be detected 1982 by monitoring the corresponding instance of 1983 applOpenChannelOpenTime." 1984 ::= { applTransactKindEntry 2 } 1986 applTransactKindTransLow OBJECT-TYPE 1987 SYNTAX Counter32 1988 UNITS "transactions" 1989 MAX-ACCESS read-only 1990 STATUS current 1991 DESCRIPTION 1992 "The applTransactKindTransLow attribute reports 1993 the low thirty-two bits of applTransactKindTrans. 1995 Discontinuities in this counter can be detected 1996 by monitoring the corresponding instance of 1997 applOpenChannelOpenTime." 1998 ::= { applTransactKindEntry 3 } 2000 applTransactKindBytes OBJECT-TYPE 2001 SYNTAX Counter64 2002 UNITS "bytes" 2003 MAX-ACCESS read-only 2004 STATUS current 2005 DESCRIPTION 2006 "The applTransactKindBytes attribute reports the number 2007 of request/response (as indicated by the 2008 applTransactFlowReqRsp index) bytes received/generated 2009 (as indicated by the applTransactFlowDirection index) 2010 handled by this application element on this transaction 2011 stream for this transaction kind. 2013 All application layer bytes are included in this count, 2014 including any application layer wrappers, headers, or 2015 other overhead. 2017 Discontinuities in this counter can be detected 2018 by monitoring the corresponding instance of 2019 applOpenChannelOpenTime." 2020 ::= { applTransactKindEntry 4 } 2022 applTransactKindBytesLow OBJECT-TYPE 2023 SYNTAX Counter32 2024 UNITS "bytes" 2025 MAX-ACCESS read-only 2026 STATUS current 2027 DESCRIPTION 2028 "The applTransactKindBytesLow attribute corresponds 2029 to the low thirty-two bits of applTransactKindBytes. 2031 Discontinuities in this counter can be detected 2032 by monitoring the corresponding instance of 2033 applOpenChannelOpenTime." 2034 ::= { applTransactKindEntry 5 } 2036 applTransactKindTime OBJECT-TYPE 2037 SYNTAX DateAndTime 2038 MAX-ACCESS read-only 2039 STATUS current 2040 DESCRIPTION 2041 "The applTransactKindTime attribute records the time of 2042 the processing (receipt or transmission as indicated 2043 by the applTransactFlowDirection index) by this 2044 running application element or service instance of 2045 the most recent request/response (as indicated by 2046 the applTransactFlowReqRsp index) of this kind of 2047 transaction on this transaction stream. 2049 If no requests/responses of this kind been 2050 received/transmitted by this running application element 2051 or service instance over this transaction stream, the 2052 value of this attribute shall be '0000000000000000'H " 2053 DEFVAL { '0000000000000000'H } 2054 ::= { applTransactKindEntry 6 } 2056 -- **************************************************************** 2057 -- 2058 -- applPastChannelGroup - logged information on former channels. 2059 -- These tables control the collection of channel history 2060 -- information and represent the accumulated historical data. 2061 -- 2062 -- **************************************************************** 2064 applPastChannelControlTable OBJECT-TYPE 2065 SYNTAX SEQUENCE OF ApplPastChannelControlEntry 2066 MAX-ACCESS not-accessible 2067 STATUS current 2068 DESCRIPTION 2069 "The applPastChannelControlTable controls the 2070 accumulation of history information about channels 2071 from the perspective of service instances and running 2072 application elements. Entries in this table are indexed 2073 by applElmtOrSvc and applElmtOrSvcId, giving control 2074 of channel history accumulation at the level of each 2075 service instance and running application element." 2076 ::= { applPastChannelGroup 1 } 2078 applPastChannelControlEntry OBJECT-TYPE 2079 SYNTAX ApplPastChannelControlEntry 2080 MAX-ACCESS not-accessible 2081 STATUS current 2082 DESCRIPTION 2083 "An applPastChannelControlEntry provides the ability 2084 to control the retention of channel history information 2085 by service instances and running application elements." 2086 INDEX { applElmtOrSvc, applElmtOrSvcId } 2087 ::= { applPastChannelControlTable 1 } 2089 ApplPastChannelControlEntry ::= SEQUENCE 2090 { 2091 applPastChannelControlCollect INTEGER, 2092 applPastChannelControlMaxRows Unsigned32, 2093 applPastChannelControlTimeLimit Unsigned32, 2094 applPastChannelControlRemItems Counter32 2095 } 2097 applPastChannelControlCollect OBJECT-TYPE 2098 SYNTAX INTEGER { enabled (1), 2099 frozen (2), 2100 disabled (3) } 2101 MAX-ACCESS read-write 2102 STATUS current 2103 DESCRIPTION 2104 "When the value of applPastChannelControlCollect is 2105 'enabled', each time the corresponding running 2106 application element or service instance closes 2107 an open channel a new entry will be added to the 2108 applPastChannelTable. 2110 When the value of applPastChannelControlCollect 2111 is 'frozen', no new entries are added to the 2112 applPastChannelTable for this running application 2113 element or service instance, and old entries are not 2114 aged out. 2116 When the value of applPastChannelControlCollect 2117 is 'disabled', all entries are removed from 2118 applPastChannelTable for this running application or 2119 service instance, and no new entries are added." 2120 DEFVAL { enabled } 2121 ::= { applPastChannelControlEntry 1 } 2123 applPastChannelControlMaxRows OBJECT-TYPE 2124 SYNTAX Unsigned32 2125 UNITS "channel history entries" 2126 MAX-ACCESS read-write 2127 STATUS current 2128 DESCRIPTION 2129 "The maximum number of entries allowed in the 2130 applPastChannelTable for this running application element 2131 or service instance. Once the number of rows for this 2132 running application element or service instance in the 2133 applPastChannelTable reaches this value, when new 2134 entries are to be added the management subsystem will 2135 make room for them by removing the oldest entries. 2136 Entries will be removed on the basis of oldest 2137 applPastChannelCloseTime value first." 2138 DEFVAL { 500 } 2139 ::= { applPastChannelControlEntry 2 } 2141 applPastChannelControlTimeLimit OBJECT-TYPE 2142 SYNTAX Unsigned32 2143 UNITS "seconds" 2144 MAX-ACCESS read-write 2145 STATUS current 2146 DESCRIPTION 2147 "The maximum time in seconds which an entry for this 2148 running application element or service instance 2149 may exist in the applPastChannelTable before it 2150 is removed. Any entry that is older than this value 2151 will be removed (aged out) from the table, unless the 2152 applPastChannelControlCollect is set to 'frozen'. 2154 Note that an entry may be aged out prior to reaching 2155 this time limit if it is the oldest entry in the table 2156 and must be removed to make space for a new entry so 2157 as to not exceed applPastChannelControlMaxRows, or if the 2158 applPastChannelControlCollect is set to 'disabled'." 2159 DEFVAL { 7200 } 2160 ::= { applPastChannelControlEntry 3 } 2162 applPastChannelControlRemItems OBJECT-TYPE 2163 SYNTAX Counter32 2164 UNITS "channel history entries" 2165 MAX-ACCESS read-only 2166 STATUS current 2167 DESCRIPTION 2168 "The applPastChannelControlRemItems attribute reports the 2169 number of applPastChannelControlTable entries for this 2170 running application element or service instance that 2171 were deleted in order to make room for new history 2172 entries. 2174 This count does NOT include entries deleted for the 2175 following reasons: 2176 - the corresponding applPastChannelControlCollect 2177 attribute has been set to 'disabled' 2179 - the entry has been in the table longer that the 2180 time limit indicated by the corresponding 2181 applPastChannelControlTimeLimit. 2182 " 2183 ::= { applPastChannelControlEntry 4 } 2185 -- **************************************************************** 2186 -- 2187 -- applPastChannelTable - Table of former channels 2188 -- 2189 -- **************************************************************** 2191 applPastChannelTable OBJECT-TYPE 2192 SYNTAX SEQUENCE OF ApplPastChannelEntry 2193 MAX-ACCESS not-accessible 2194 STATUS current 2195 DESCRIPTION 2196 "The applPastChannelTable provides history information 2197 about channels from the perspective of running 2198 application elements and service instances. 2200 Entries in this table are indexed by applElmtOrSvc, 2201 applElmtOrSvcId, and by applPastChannelIndex, which 2202 serves to uniquely identify each former channel in the 2203 context of a running application element or service 2204 instance. 2206 Note that the value of applPastChannelIndex is 2207 independent of the value applOpenChannelIndex had when 2208 this channel was open. 2210 Entries for closed channels for a given running 2211 application element or service instance can 2212 be added to this table only if its entry in the 2213 applPastChannelControlTable has the value 'enabled' 2214 for the attribute applPastChannelControlCollect. 2216 Entries for closed channels are removed under the 2217 following circumstances: 2219 - the running application element or service 2220 instance no longer exists 2222 - the corresponding applPastChannelControlCollect 2223 attribute has been set to 'disabled' 2225 - the entry has been in the table longer that the 2226 time limit indicated by the corresponding 2227 applPastChannelControlTimeLimit and the value of 2228 applPastChannelControlCollect is not 'frozen' 2230 - this is the oldest entry for the running 2231 application element or service instance in 2232 question and the addition of a new element would 2233 otherwise cause applPastChannelControlMaxRows to 2234 be exceeded for this running application element 2235 or service instance. 2237 - a value of applPastChannelIndex has been re-used. 2238 Note that under normal circumstances, this is 2239 unlikely. 2241 Removal/replacement of an entry under the 2242 last two conditions causes the corresponding 2243 applPastChannelControlRemItems to be incremented." 2244 ::= { applPastChannelGroup 2 } 2246 applPastChannelEntry OBJECT-TYPE 2247 SYNTAX ApplPastChannelEntry 2248 MAX-ACCESS not-accessible 2249 STATUS current 2250 DESCRIPTION 2251 "An applPastChannelEntry indicates that a running 2252 application element or service instance once had an open 2253 channel, which is now closed. The entry has information 2254 describing that channel." 2255 INDEX { applElmtOrSvc, applElmtOrSvcId, 2256 applPastChannelIndex } 2257 ::= { applPastChannelTable 1 } 2259 ApplPastChannelEntry ::= SEQUENCE 2260 { 2261 applPastChannelIndex Unsigned32, 2262 applPastChannelOpenTime DateAndTime, 2263 applPastChannelCloseTime DateAndTime, 2264 applPastChannelReadRequests Unsigned64, 2265 applPastChannelReadReqsLow Unsigned32, 2266 applPastChannelReadFailures Unsigned32, 2267 applPastChannelBytesRead Unsigned64, 2268 applPastChannelBytesReadLow Unsigned32, 2269 applPastChannelLastReadTime DateAndTime, 2270 applPastChannelWriteRequests Unsigned64, 2271 applPastChannelWriteReqsLow Unsigned32, 2272 applPastChannelWriteFailures Unsigned32, 2273 applPastChannelBytesWritten Unsigned64, 2274 applPastChannelBytesWritLow Unsigned32, 2275 applPastChannelLastWriteTime DateAndTime 2276 } 2278 applPastChannelIndex OBJECT-TYPE 2279 SYNTAX Unsigned32 (1..'ffffffff'h) 2280 MAX-ACCESS read-only 2281 STATUS current 2282 DESCRIPTION 2283 "This attribute serves to uniquely identify this closed 2284 channel in the context of the running application 2285 element or service instance. This attribute has no 2286 other semantics. 2288 Note that the value of applPastChannelIndex is 2289 independent of the value applOpenChannelIndex had when 2290 this channel was active. 2292 In issuing this index value, the implementation must 2293 avoid re-issuing an index value which has already been 2294 assigned to an entry which has not yet been deleted due 2295 to age or space considerations. 2297 The value zero is excluded from the set of permitted 2298 values for this index in order to permit other tables to 2299 possibly represent information that cannot be associated 2300 with a specific entry in this table. " 2301 ::= { applPastChannelEntry 1 } 2303 applPastChannelOpenTime OBJECT-TYPE 2304 SYNTAX DateAndTime 2305 MAX-ACCESS read-only 2306 STATUS current 2307 DESCRIPTION 2308 "This attribute records the time when this channel was 2309 originally opened. Note that this information is quite 2310 different from applOpenChannelOpenTime, which is used 2311 for the detection of counter discontinuities." 2312 ::= { applPastChannelEntry 2 } 2314 applPastChannelCloseTime OBJECT-TYPE 2315 SYNTAX DateAndTime 2316 MAX-ACCESS read-only 2317 STATUS current 2318 DESCRIPTION 2319 "This attribute records the time when this channel 2320 was closed." 2321 ::= { applPastChannelEntry 3 } 2323 applPastChannelReadRequests OBJECT-TYPE 2324 SYNTAX Unsigned64 2325 UNITS "read requests" 2326 MAX-ACCESS read-only 2327 STATUS current 2328 DESCRIPTION 2329 "This attribute records the number of read requests for 2330 this channel made by this running application element or 2331 service instance. All read requests for this channel by 2332 this running application element or service instance, 2333 regardless of completion status, are included in this 2334 count. Read requests are counted in terms of system 2335 calls, rather than API calls." 2337 ::= { applPastChannelEntry 4 } 2339 applPastChannelReadReqsLow OBJECT-TYPE 2340 SYNTAX Unsigned32 2341 UNITS "read requests" 2342 MAX-ACCESS read-only 2343 STATUS current 2344 DESCRIPTION 2345 "This attribute corresponds to the low thirty-two bits 2346 of applPastChannelReadRequests." 2347 ::= { applPastChannelEntry 5 } 2349 applPastChannelReadFailures OBJECT-TYPE 2350 SYNTAX Unsigned32 2351 UNITS "failed read requests" 2352 MAX-ACCESS read-only 2353 STATUS current 2354 DESCRIPTION 2355 "This attribute reports the number of failed read 2356 requests." 2357 ::= { applPastChannelEntry 6 } 2359 applPastChannelBytesRead OBJECT-TYPE 2360 SYNTAX Unsigned64 2361 UNITS "bytes" 2362 MAX-ACCESS read-only 2363 STATUS current 2364 DESCRIPTION 2365 "This attribute reports the number of bytes read from this 2366 channel by this running application element or service 2367 instance. Only bytes successfully read are included in 2368 this count. " 2369 ::= { applPastChannelEntry 7 } 2371 applPastChannelBytesReadLow OBJECT-TYPE 2372 SYNTAX Unsigned32 2373 UNITS "bytes" 2374 MAX-ACCESS read-only 2375 STATUS current 2376 DESCRIPTION 2377 "This attribute corresponds to the low thirty-two bits 2378 of applPastChannelBytesRead." 2379 ::= { applPastChannelEntry 8 } 2381 applPastChannelLastReadTime OBJECT-TYPE 2382 SYNTAX DateAndTime 2383 MAX-ACCESS read-only 2384 STATUS current 2385 DESCRIPTION 2386 "This attribute reports the time of the most recent read 2387 request made by this running application element or 2388 service instance regardless of completion status, for 2389 this former channel. 2391 If no read requests have been made , the value of this 2392 attribute shall be '0000000000000000'H " 2393 DEFVAL { '0000000000000000'H } 2394 ::= { applPastChannelEntry 9 } 2396 applPastChannelWriteRequests OBJECT-TYPE 2397 SYNTAX Unsigned64 2398 UNITS "write requests" 2399 MAX-ACCESS read-only 2400 STATUS current 2401 DESCRIPTION 2402 "The applPastChannelWriteRequests attribute reports 2403 the number of write requests, regardless of completion 2404 status, made by this running application element or 2405 service instance for this former channel. 2407 Write requests are counted in terms of system calls, 2408 rather than API calls." 2409 ::= { applPastChannelEntry 10 } 2411 applPastChannelWriteReqsLow OBJECT-TYPE 2412 SYNTAX Unsigned32 2413 UNITS "write requests" 2414 MAX-ACCESS read-only 2415 STATUS current 2416 DESCRIPTION 2417 "This attribute corresponds to the low thirty-two 2418 bits of applPastChannelWriteRequests." 2419 ::= { applPastChannelEntry 11 } 2421 applPastChannelWriteFailures OBJECT-TYPE 2422 SYNTAX Unsigned32 2423 UNITS "failed write requests" 2424 MAX-ACCESS read-only 2425 STATUS current 2426 DESCRIPTION 2427 "This attribute reports the number of failed write 2428 requests." 2429 ::= { applPastChannelEntry 12 } 2431 applPastChannelBytesWritten OBJECT-TYPE 2432 SYNTAX Unsigned64 2433 UNITS "bytes" 2434 MAX-ACCESS read-only 2435 STATUS current 2436 DESCRIPTION 2437 "This attribute reports the number of bytes written to 2438 this former channel by this running application element 2439 or service instance. Only bytes successfully written 2440 (no errors reported by the API in use by the application) 2441 are included in this count." 2442 ::= { applPastChannelEntry 13 } 2444 applPastChannelBytesWritLow OBJECT-TYPE 2445 SYNTAX Unsigned32 2446 UNITS "bytes" 2447 MAX-ACCESS read-only 2448 STATUS current 2449 DESCRIPTION 2450 "This attribute corresponds to the low thirty-two bits of 2451 applPastChannelBytesWritten." 2452 ::= { applPastChannelEntry 14 } 2454 applPastChannelLastWriteTime OBJECT-TYPE 2455 SYNTAX DateAndTime 2456 MAX-ACCESS read-only 2457 STATUS current 2458 DESCRIPTION 2459 "The applPastChannelLastWriteTime attribute reports 2460 the time of the most recent write request made by 2461 this running application element or service instance, 2462 regardless of completion status, for this former 2463 channel. 2465 If no write requests have been made the value of this 2466 attribute shall be '0000000000000000'H " 2467 DEFVAL { '0000000000000000'H } 2468 ::= { applPastChannelEntry 15 } 2470 -- **************************************************************** 2471 -- 2472 -- applPastFileTable - information specific to former files 2473 -- 2474 -- **************************************************************** 2475 applPastFileTable OBJECT-TYPE 2476 SYNTAX SEQUENCE OF ApplPastFileEntry 2477 MAX-ACCESS not-accessible 2478 STATUS current 2479 DESCRIPTION 2480 "The applPastFileTable supplements the 2481 applPastChannelTable for entries corresponding to 2482 channels which were files. The indexing structure is 2483 identical to applPastChannelTable. An entry exists in 2484 the applPastFileTable only if there is a corresponding 2485 (same index values) entry in the applPastChannelTable 2486 and if the channel was a file. 2488 Entries for closed files are removed when the 2489 corresponding entries are removed from the 2490 applPastChannelTable." 2491 ::= { applPastChannelGroup 3 } 2493 applPastFileEntry OBJECT-TYPE 2494 SYNTAX ApplPastFileEntry 2495 MAX-ACCESS not-accessible 2496 STATUS current 2497 DESCRIPTION 2498 "An applPastFileEntry provides additional, file-specific 2499 information to complement the corresponding 2500 applPastChannelEntry for a channel which was a file." 2501 INDEX { applElmtOrSvc, applElmtOrSvcId, 2502 applPastChannelIndex } 2503 ::= { applPastFileTable 1 } 2505 ApplPastFileEntry ::= SEQUENCE 2506 { 2507 applPastFileName LongUtf8String, 2508 applPastFileSizeHigh Unsigned32, 2509 applPastFileSizeLow Unsigned32, 2510 applPastFileMode INTEGER 2511 } 2513 applPastFileName OBJECT-TYPE 2514 SYNTAX LongUtf8String 2515 MAX-ACCESS read-only 2516 STATUS current 2517 DESCRIPTION 2518 "This attribute records the last known value of 2519 applOpenFileName before the channel was closed." 2520 ::= { applPastFileEntry 1 } 2522 applPastFileSizeHigh OBJECT-TYPE 2523 SYNTAX Unsigned32 2524 UNITS "2^32 byte blocks" 2525 MAX-ACCESS read-only 2526 STATUS current 2527 DESCRIPTION 2528 "This attribute records the value of applOpenFileSizeHigh 2529 at the time this channel was closed. 2531 For example, for a file with a total size of 2532 4,294,967,296 bytes, this attribute would have a value 2533 of 1; for a file with a total size of 4,294,967,295 2534 bytes this attribute's value would be 0." 2535 ::= { applPastFileEntry 2 } 2537 applPastFileSizeLow OBJECT-TYPE 2538 SYNTAX Unsigned32 2539 UNITS "bytes" 2540 MAX-ACCESS read-only 2541 STATUS current 2542 DESCRIPTION 2543 "This attribute records the value of applOpenFileSizeLow 2544 at the time this channel was closed. 2546 For example, for a file with a total size of 2547 4,294,967,296 bytes this attribute would have a value 2548 of 0; for a file with a total size of 4,294,967,295 2549 bytes this attribute's value would be 4,294,967,295." 2550 ::= { applPastFileEntry 3 } 2552 applPastFileMode OBJECT-TYPE 2553 SYNTAX INTEGER { read(1), 2554 write(2), 2555 readWrite(3) } 2556 MAX-ACCESS read-only 2557 STATUS current 2558 DESCRIPTION 2559 "This attribute records the value of applOpenFileMode 2560 at the time this channel was closed. " 2561 ::= { applPastFileEntry 4 } 2563 -- **************************************************************** 2564 -- 2565 -- applPastConTable - information specific to former connections 2566 -- 2567 -- **************************************************************** 2568 applPastConTable OBJECT-TYPE 2569 SYNTAX SEQUENCE OF ApplPastConEntry 2570 MAX-ACCESS not-accessible 2571 STATUS current 2572 DESCRIPTION 2573 "The applPastConTable supplements the applPastChannelTable 2574 for entries corresponding to channels which were 2575 connections. The indexing structure is identical 2576 to applPastChannelTable. An entry exists in the 2577 applPastConTable only if there is a corresponding 2578 (same index values) entry in the applPastChannelTable 2579 and if the channel was a connection. 2581 Entries for closed connections are removed when 2582 the corresponding entries are removed from the 2583 applPastChannelTable." 2584 ::= { applPastChannelGroup 4 } 2586 applPastConEntry OBJECT-TYPE 2587 SYNTAX ApplPastConEntry 2588 MAX-ACCESS not-accessible 2589 STATUS current 2590 DESCRIPTION 2591 "An applPastConEntry provides additional, 2592 connection-specific information to complement the 2593 corresponding applPastChannelEntry for a channel which 2594 was a connection." 2595 INDEX { applElmtOrSvc, applElmtOrSvcId, 2596 applPastChannelIndex } 2597 ::= { applPastConTable 1 } 2599 ApplPastConEntry ::= SEQUENCE 2600 { 2601 applPastConTransport TDomain, 2602 applPastConNearEndAddr TAddress, 2603 applPastConNearEndpoint SnmpAdminString, 2604 applPastConFarEndAddr TAddress, 2605 applPastConFarEndpoint SnmpAdminString, 2606 applPastConApplication SnmpAdminString 2607 } 2609 applPastConTransport OBJECT-TYPE 2610 SYNTAX TDomain 2611 MAX-ACCESS read-only 2612 STATUS current 2613 DESCRIPTION 2614 "The applPastConTransport attribute identifies the 2615 transport protocol that was in use for this former 2616 connection. If the transport protocol could not be 2617 determined, the value { 0 0 } shall be used." 2618 DEFVAL { { 0 0 } } 2619 ::= { applPastConEntry 1 } 2621 applPastConNearEndAddr OBJECT-TYPE 2622 SYNTAX TAddress 2623 MAX-ACCESS read-only 2624 STATUS current 2625 DESCRIPTION 2626 "The applPastConNearEndAddr attribute reports the 2627 transport address and port information for the near 2628 end of this former connection. 2630 If the information could not be determined, the value 2631 shall be a zero-length string." 2632 DEFVAL { "" } 2633 ::= { applPastConEntry 2 } 2635 applPastConNearEndpoint OBJECT-TYPE 2636 SYNTAX SnmpAdminString 2637 MAX-ACCESS read-only 2638 STATUS current 2639 DESCRIPTION 2640 "The applPastConNearEndpoint attribute reports the 2641 fully-qualified domain name and port information for the 2642 near end of this former connection. 2644 The format of this attribute for TCP and UDP-based 2645 protocols is the fully-qualified domain name immediately 2646 followed by a colon which is immediately followed by 2647 the decimal representation of the port number. 2649 If the information could not be determined, the value 2650 shall be a zero-length string." 2651 DEFVAL { "" } 2652 ::= { applPastConEntry 3 } 2654 applPastConFarEndAddr OBJECT-TYPE 2655 SYNTAX TAddress 2656 MAX-ACCESS read-only 2657 STATUS current 2658 DESCRIPTION 2659 "The applPastConFarEnd attribute reports the transport 2660 address and port information for the far end of this 2661 former connection. 2663 If not known, as in the case of a connectionless 2664 transport, the value of this attribute shall be a 2665 zero-length string." 2666 DEFVAL { "" } 2667 ::= { applPastConEntry 4 } 2669 applPastConFarEndpoint OBJECT-TYPE 2670 SYNTAX SnmpAdminString 2671 MAX-ACCESS read-only 2672 STATUS current 2673 DESCRIPTION 2674 "The applPastConFarEndpoint attribute reports the 2675 transport address and port information for the far 2676 end of this former connection. 2678 The format of this attribute for TCP and UDP-based 2679 protocols is the fully-qualified domain name immediately 2680 followed by a colon which is immediately followed by 2681 the decimal representation of the port number. 2683 If not known, as in the case of a connectionless 2684 transport, the value of this attribute shall be a 2685 zero-length string." 2686 DEFVAL { "" } 2687 ::= { applPastConEntry 5 } 2689 applPastConApplication OBJECT-TYPE 2690 SYNTAX SnmpAdminString 2691 MAX-ACCESS read-only 2692 STATUS current 2693 DESCRIPTION 2694 "The applPastConApplication attribute identifies the 2695 application layer protocol that was in use. Where 2696 possible, the values defined in [17] shall be used. 2697 If not known, the value of this attribute shall be a 2698 zero-length string." 2699 DEFVAL { "" } 2700 ::= { applPastConEntry 6 } 2702 -- **************************************************************** 2703 -- 2704 -- applPastTransStreamTable - historical 2705 -- information for transaction stream monitoring 2706 -- 2707 -- **************************************************************** 2708 applPastTransStreamTable OBJECT-TYPE 2709 SYNTAX SEQUENCE OF ApplPastTransStreamEntry 2710 MAX-ACCESS not-accessible 2711 STATUS current 2712 DESCRIPTION 2713 "The applPastTransStreamTable contains common 2714 information for historical transaction statistics." 2715 ::= { applPastChannelGroup 5 } 2717 applPastTransStreamEntry OBJECT-TYPE 2718 SYNTAX ApplPastTransStreamEntry 2719 MAX-ACCESS not-accessible 2720 STATUS current 2721 DESCRIPTION 2722 "An applPastTransStreamEntry contains information for 2723 a single former transaction stream. A transaction 2724 stream could have been a network connection, file, or 2725 other source of transactions." 2726 INDEX { applElmtOrSvc, applElmtOrSvcId, 2727 applPastChannelIndex } 2728 ::= { applPastTransStreamTable 1 } 2730 ApplPastTransStreamEntry ::= SEQUENCE { 2731 applPastTransStreamDescr SnmpAdminString, 2732 applPastTransStreamUnitOfWork SnmpAdminString, 2733 applPastTransStreamInvCumTime Unsigned32, 2734 applPastTransStreamInvRspTime Unsigned32, 2735 applPastTransStreamPrfCumTime Unsigned32, 2736 applPastTransStreamPrfRspTime Unsigned32 } 2738 applPastTransStreamDescr OBJECT-TYPE 2739 SYNTAX SnmpAdminString 2740 MAX-ACCESS read-only 2741 STATUS current 2742 DESCRIPTION 2743 "The applPastTransStreamDescr attribute provides a 2744 human-readable description of this transaction stream. 2746 If no descriptive information is available, this 2747 attribute's value shall be a zero-length string." 2748 DEFVAL { "" } 2749 ::= { applPastTransStreamEntry 1 } 2751 applPastTransStreamUnitOfWork OBJECT-TYPE 2752 SYNTAX SnmpAdminString 2753 MAX-ACCESS read-only 2754 STATUS current 2755 DESCRIPTION 2756 "The applPastTransStreamUnitOfWork attribute provides a 2757 human-readable definition of what the unit of work is 2758 for this transaction stream. 2760 If no descriptive information is available, this 2761 attribute's value shall be a zero-length string." 2762 DEFVAL { "" } 2763 ::= { applPastTransStreamEntry 2 } 2765 applPastTransStreamInvCumTime OBJECT-TYPE 2766 SYNTAX Unsigned32 2767 UNITS "milliseconds" 2768 MAX-ACCESS read-only 2769 STATUS current 2770 DESCRIPTION 2771 "The applPastTransStreamInvCumTime attribute reports the 2772 cumulative sum of the times measured between the 2773 transmission of requests and the receipt of (the first 2774 of) the corresponding response(s)." 2775 ::= { applPastTransStreamEntry 3 } 2777 applPastTransStreamInvRspTime OBJECT-TYPE 2778 SYNTAX Unsigned32 2779 UNITS "milliseconds" 2780 MAX-ACCESS read-only 2781 STATUS current 2782 DESCRIPTION 2783 "The applPastTransStreamInvRspTime attribute reports the 2784 cumulative sum of the times measured between the receipt 2785 of the first and last of multiple responses to a request. 2787 For transaction streams which do not permit multiple 2788 responses to a single request, this attribute will be 2789 zero." 2790 ::= { applPastTransStreamEntry 4 } 2792 applPastTransStreamPrfCumTime OBJECT-TYPE 2793 SYNTAX Unsigned32 2794 UNITS "milliseconds" 2795 MAX-ACCESS read-only 2796 STATUS current 2797 DESCRIPTION 2798 "The applPastTransStreamPrfCumTime attribute reports the 2799 cumulative sum of the times measured between receipt 2800 of requests and the transmission of the corresponding 2801 responses." 2802 ::= { applPastTransStreamEntry 5 } 2804 applPastTransStreamPrfRspTime OBJECT-TYPE 2805 SYNTAX Unsigned32 2806 UNITS "milliseconds" 2807 MAX-ACCESS read-only 2808 STATUS current 2809 DESCRIPTION 2810 "For each transaction performed, the elapsed time between 2811 when the first response is enqueued and when the last 2812 response is enqueued is added to this cumulative sum. 2814 For single-response protocols, the value of 2815 applPastTransStreamPrfRspTime will be zero." 2816 ::= { applPastTransStreamEntry 6 } 2818 -- **************************************************************** 2819 -- 2820 -- applPastTransFlowTable 2821 -- 2822 -- **************************************************************** 2824 applPastTransFlowTable OBJECT-TYPE 2825 SYNTAX SEQUENCE OF ApplPastTransFlowEntry 2826 MAX-ACCESS not-accessible 2827 STATUS current 2828 DESCRIPTION 2829 "The applPastTransFlowTable contains entries, organized by 2830 application instance or running application element, 2831 direction of flow, and type (request/response) for each 2832 former transaction stream. 2834 The simple model of a transaction used here looks like 2835 this: 2837 invoker | Request | performer 2838 | - - - - - - > | 2839 | | 2840 | Response | 2841 | < - - - - - - | 2842 | | 2844 Since in some protocols it is possible for an entity 2845 to take on both the invoker and performer roles, 2846 information here is accumulated for transmitted and 2847 received requests, as well as for transmitted and 2848 received responses. Counts are maintained for both 2849 transactions and bytes transferred." 2850 ::= { applPastChannelGroup 6 } 2852 applPastTransFlowEntry OBJECT-TYPE 2853 SYNTAX ApplPastTransFlowEntry 2854 MAX-ACCESS not-accessible 2855 STATUS current 2856 DESCRIPTION 2857 "An applPastTransFlowEntry records transaction throughput 2858 information for requests or response in a particular 2859 direction (transmit / receive) for a transaction stream. 2861 Entries in this table correspond to those in the 2862 applPastTransStreamTable with identical values 2863 for the applElmtOrSvc, applElmtOrSvcId, and the 2864 applPastChannelIndex." 2865 INDEX { applElmtOrSvc, 2866 applElmtOrSvcId, 2867 applPastChannelIndex, 2868 applPastTransFlowDirection, 2869 applPastTransFlowReqRsp } 2870 ::= { applPastTransFlowTable 1 } 2872 ApplPastTransFlowEntry ::= SEQUENCE { 2873 applPastTransFlowDirection INTEGER, 2874 applPastTransFlowReqRsp INTEGER, 2875 applPastTransFlowTrans Unsigned64, 2876 applPastTransFlowTransLow Unsigned32, 2877 applPastTransFlowBytes Unsigned64, 2878 applPastTransFlowBytesLow Unsigned32, 2879 applPastTransFlowTime DateAndTime } 2881 applPastTransFlowDirection OBJECT-TYPE 2882 SYNTAX INTEGER { transmit(1), 2883 receive(2) } 2884 MAX-ACCESS not-accessible 2885 STATUS current 2886 DESCRIPTION 2887 "The applPastTransFlowDirection index serves 2888 to identify an entry as containing information 2889 pertaining to the transmit (1) or receive (2) flow 2890 of a past transaction stream. This index corresponds 2891 to applTransactFlowDirection." 2892 ::= { applPastTransFlowEntry 1 } 2894 applPastTransFlowReqRsp OBJECT-TYPE 2895 SYNTAX INTEGER { request(1), 2896 response(2) } 2897 MAX-ACCESS not-accessible 2898 STATUS current 2899 DESCRIPTION 2900 "The value of the applPastTransFlowReqRsp index indicates 2901 whether this entry contains information on requests 2902 (1), or responses (2). This index corresponds to 2903 applTransactFlowReqRsp." 2904 ::= { applPastTransFlowEntry 2 } 2906 applPastTransFlowTrans OBJECT-TYPE 2907 SYNTAX Unsigned64 2908 UNITS "transactions" 2909 MAX-ACCESS read-only 2910 STATUS current 2911 DESCRIPTION 2912 "The applPastTransFlowTrans attribute reports the number 2913 of request/response (as indicated by the 2914 applPastTransFlowReqRsp index) transactions 2915 received/generated (as indicated by the 2916 applPastTransFlowDirection index) handled on this 2917 transaction stream." 2918 ::= { applPastTransFlowEntry 3 } 2920 applPastTransFlowTransLow OBJECT-TYPE 2921 SYNTAX Unsigned32 2922 UNITS "transactions" 2923 MAX-ACCESS read-only 2924 STATUS current 2925 DESCRIPTION 2926 "This attribute corresponds to the low thirty-two 2927 bits of applPastTransFlowTrans." 2928 ::= { applPastTransFlowEntry 4 } 2930 applPastTransFlowBytes OBJECT-TYPE 2931 SYNTAX Unsigned64 2932 UNITS "bytes" 2933 MAX-ACCESS read-only 2934 STATUS current 2935 DESCRIPTION 2936 "The applPastTransFlowBytes attribute reports the number 2937 of request/response (as indicated by the 2938 applPastTransFlowReqRsp index) bytes received/generated 2939 (as indicated by the applPastTransFlowDirection index) 2940 handled on this transaction stream. 2942 All application layer bytes are included in this count, 2943 including any application layer wrappers, headers, or 2944 other overhead." 2945 ::= { applPastTransFlowEntry 5 } 2947 applPastTransFlowBytesLow OBJECT-TYPE 2948 SYNTAX Unsigned32 2949 UNITS "bytes" 2950 MAX-ACCESS read-only 2951 STATUS current 2952 DESCRIPTION 2953 "This attribute corresponds to the low thirty-two 2954 bits of applPastTransFlowBytes." 2955 ::= { applPastTransFlowEntry 6 } 2957 applPastTransFlowTime OBJECT-TYPE 2958 SYNTAX DateAndTime 2959 MAX-ACCESS read-only 2960 STATUS current 2961 DESCRIPTION 2962 "The applPastTransFlowTime attribute records the time of 2963 the processing (receipt or transmission as 2964 indicated by the applPastTransFlowDirection index) 2965 of the last request/response (as indicated by the 2966 applPastTransFlowReqRsp index) on this transaction 2967 stream. 2969 If no requests/responses been received/transmitted by 2970 this entity over this transaction stream, the value 2971 of this attribute shall be '0000000000000000'H " 2972 DEFVAL { '0000000000000000'H } 2973 ::= { applPastTransFlowEntry 7 } 2975 -- **************************************************************** 2976 -- 2977 -- applPastTransKindTable - transaction statistics broken down 2978 -- according to the kinds of transactions in each direction 2979 -- for a transaction stream. 2980 -- 2981 -- **************************************************************** 2983 applPastTransKindTable OBJECT-TYPE 2984 SYNTAX SEQUENCE OF ApplPastTransKindEntry 2985 MAX-ACCESS not-accessible 2986 STATUS current 2987 DESCRIPTION 2988 "The applPastTransKindTable provides transaction 2989 statistics broken down by kinds of transaction. 2990 The definition of the kinds of transactions is 2991 specific to the application protocol in use, and may be 2992 documented in the form of an applicability statement. " 2993 ::= { applPastChannelGroup 7 } 2995 applPastTransKindEntry OBJECT-TYPE 2996 SYNTAX ApplPastTransKindEntry 2997 MAX-ACCESS not-accessible 2998 STATUS current 2999 DESCRIPTION 3000 "An applPastTransKindEntry reports historical data for a 3001 specific service instance or running application 3002 element's use of a specific transaction stream in 3003 a particular direction in requests or responses 3004 (as indicated by the applPastTransFlowReqRsp index) 3005 broken down by transaction kind, as indicated by the 3006 applPastTransKind index." 3007 INDEX { applElmtOrSvc, 3008 applElmtOrSvcId, 3009 applPastChannelIndex, 3010 applPastTransFlowDirection, 3011 applPastTransFlowReqRsp, 3012 applPastTransKind } 3013 ::= { applPastTransKindTable 1 } 3015 ApplPastTransKindEntry ::= SEQUENCE 3016 { 3017 applPastTransKind SnmpAdminString, 3018 applPastTransKindTrans Unsigned64, 3019 applPastTransKindTransLow Unsigned32, 3020 applPastTransKindBytes Unsigned64, 3021 applPastTransKindBytesLow Unsigned32, 3022 applPastTransKindTime DateAndTime 3023 } 3025 applPastTransKind OBJECT-TYPE 3026 SYNTAX SnmpAdminString (SIZE (1 .. 32)) 3027 MAX-ACCESS not-accessible 3028 STATUS current 3029 DESCRIPTION 3030 "The applPastTransKind index is the human-readable 3031 identifier for a particular transaction kind within 3032 the context of an application protocol. The values 3033 to be used for a particular protocol may be identified 3034 in an applicability statement. This index corresponds 3035 to applTransactKind." 3036 ::= { applPastTransKindEntry 1 } 3038 applPastTransKindTrans OBJECT-TYPE 3039 SYNTAX Unsigned64 3040 UNITS "transactions" 3041 MAX-ACCESS read-only 3042 STATUS current 3043 DESCRIPTION 3044 "For this transaction stream, this attribute records 3045 the total number of transactions of the type 3046 identified by the indexes. The type is characterized 3047 according to the receive/transmit direction 3048 (applPastTransFlowDirecton), whether it was a request 3049 or a response (applPastTransFlowReqRsp), and the 3050 protocol-specific transaction kind (applPastTransKind). 3051 stream for this transaction kind." 3052 ::= { applPastTransKindEntry 2 } 3054 applPastTransKindTransLow OBJECT-TYPE 3055 SYNTAX Unsigned32 3056 UNITS "transactions" 3057 MAX-ACCESS read-only 3058 STATUS current 3059 DESCRIPTION 3060 "The applPastTransKindTransLow attribute reports 3061 the low thirty-two bits of applPastTransKindTrans." 3062 ::= { applPastTransKindEntry 3 } 3064 applPastTransKindBytes OBJECT-TYPE 3065 SYNTAX Unsigned64 3066 UNITS "bytes" 3067 MAX-ACCESS read-only 3068 STATUS current 3069 DESCRIPTION 3070 "For this transaction stream and transaction kind, the 3071 applPastTransKindBytes attribute reports the number 3072 of bytes received or generated (as indicated by 3073 the applPastTransFlowDirection index) in requests or 3074 responses (as indicated by the applPastTransFlowReqRsp 3075 index). 3077 All application layer bytes are included in this count, 3078 including any application layer wrappers, headers, or 3079 other overhead." 3080 ::= { applPastTransKindEntry 4 } 3082 applPastTransKindBytesLow OBJECT-TYPE 3083 SYNTAX Unsigned32 3084 UNITS "bytes" 3085 MAX-ACCESS read-only 3086 STATUS current 3087 DESCRIPTION 3088 "The applPastTransKindBytesLow attribute corresponds 3089 to the low thirty-two bits of applPastTransKindBytes." 3090 ::= { applPastTransKindEntry 5 } 3092 applPastTransKindTime OBJECT-TYPE 3093 SYNTAX DateAndTime 3094 MAX-ACCESS read-only 3095 STATUS current 3096 DESCRIPTION 3097 "The applPastTransKindTime attribute records the time of 3098 the processing (receipt or transmission as 3099 indicated by the applPastTransFlowDirection index) 3100 of the last request/response (as indicated by the 3101 applPastTransFlowReqRsp index) of this kind of 3102 transaction on this transaction stream. 3104 If no requests/responses of this kind were 3105 received/transmitted over this transaction stream, the 3106 value of this attribute shall be '0000000000000000'H " 3107 DEFVAL { '0000000000000000'H } 3108 ::= { applPastTransKindEntry 6 } 3110 -- **************************************************************** 3111 -- 3112 -- applElmtRunControlGroup - monitor and control running 3113 -- application elements 3114 -- 3115 -- **************************************************************** 3117 applElmtRunStatusTable OBJECT-TYPE 3118 SYNTAX SEQUENCE OF ApplElmtRunStatusEntry 3119 MAX-ACCESS not-accessible 3120 STATUS current 3121 DESCRIPTION 3122 "This table provides information on running application 3123 elements, complementing information available in the 3124 correspondingly indexed sysApplElmtRunTable [10]." 3125 ::= { applElmtRunControlGroup 1 } 3127 applElmtRunStatusEntry OBJECT-TYPE 3128 SYNTAX ApplElmtRunStatusEntry 3129 MAX-ACCESS not-accessible 3130 STATUS current 3131 DESCRIPTION 3132 "An applElmtRunStatusEntry contains information to support 3133 the control and monitoring of a single running application 3134 element." 3135 INDEX { sysApplElmtRunIndex } 3136 ::= { applElmtRunStatusTable 1 } 3138 ApplElmtRunStatusEntry ::= SEQUENCE { 3139 applElmtRunStatusSuspended TruthValue, 3140 applElmtRunStatusHeapUsage Unsigned32, 3141 applElmtRunStatusOpenConnections Unsigned32, 3142 applElmtRunStatusOpenFiles Unsigned32, 3143 applElmtRunStatusLastErrorMsg SnmpAdminString, 3144 applElmtRunStatusLastErrorTime DateAndTime } 3146 applElmtRunStatusSuspended OBJECT-TYPE 3147 SYNTAX TruthValue 3148 MAX-ACCESS read-only 3149 STATUS current 3150 DESCRIPTION 3151 "The applElmtRunStatusSuspended attribute reports 3152 whether processing by this running application element 3153 has been suspended, whether by management request or by 3154 other means." 3155 ::= { applElmtRunStatusEntry 1 } 3157 applElmtRunStatusHeapUsage OBJECT-TYPE 3158 SYNTAX Unsigned32 3159 UNITS "bytes" 3160 MAX-ACCESS read-only 3161 STATUS current 3162 DESCRIPTION 3163 "The applElmtRunStatusHeapUsage reports the current 3164 approximate heap usage by this running application 3165 element." 3166 ::= { applElmtRunStatusEntry 2 } 3168 applElmtRunStatusOpenConnections OBJECT-TYPE 3169 SYNTAX Unsigned32 3170 UNITS "connections" 3171 MAX-ACCESS read-only 3172 STATUS current 3173 DESCRIPTION 3174 "The applElmtRunStatusOpenConnections attribute reports 3175 the current number of open connections in use by this 3176 running application element." 3177 ::= { applElmtRunStatusEntry 3 } 3179 applElmtRunStatusOpenFiles OBJECT-TYPE 3180 SYNTAX Gauge32 3181 UNITS "files" 3182 MAX-ACCESS read-only 3183 STATUS current 3184 DESCRIPTION 3185 "The applElmtRunStatusOpenFiles attribute reports the 3186 current number of open files in use by this running 3187 application element." 3188 ::= { applElmtRunStatusEntry 4 } 3190 applElmtRunStatusLastErrorMsg OBJECT-TYPE 3191 SYNTAX SnmpAdminString 3192 MAX-ACCESS read-only 3193 STATUS current 3194 DESCRIPTION 3195 "The applElmtRunStatusLastErrorMessage attribute reports 3196 the most recent error message (typically written to 3197 stderr or a system error logging facility) from this 3198 running application element. If no such message has yet 3199 been generated, the value of this attribute shall be a 3200 zero-length string." 3201 DEFVAL { "" } 3202 ::= { applElmtRunStatusEntry 5 } 3204 applElmtRunStatusLastErrorTime OBJECT-TYPE 3205 SYNTAX DateAndTime 3206 MAX-ACCESS read-only 3207 STATUS current 3208 DESCRIPTION 3209 "The applElmtRunStatusLastErrorTime attribute reports the 3210 time of the most recent error message in 3211 applElmtRunStatusLastErrorMsg. 3213 If no such message has yet been generated, the value 3214 of this attribute shall be '0000000000000000'H " 3215 DEFVAL { '0000000000000000'H } 3216 ::= { applElmtRunStatusEntry 6 } 3218 -- **************************************************************** 3219 -- 3220 -- applElmtRunControlTable - control running application 3221 -- elements 3222 -- 3223 -- **************************************************************** 3225 applElmtRunControlTable OBJECT-TYPE 3226 SYNTAX SEQUENCE OF ApplElmtRunControlEntry 3227 MAX-ACCESS not-accessible 3228 STATUS current 3229 DESCRIPTION 3230 "This table provides the ability to control application 3231 elements, complementing information available in the 3232 correspondingly indexed sysApplElmtRunTable [10]." 3233 ::= { applElmtRunControlGroup 2 } 3235 applElmtRunControlEntry OBJECT-TYPE 3236 SYNTAX ApplElmtRunControlEntry 3237 MAX-ACCESS not-accessible 3238 STATUS current 3239 DESCRIPTION 3240 "An applElmtRunControlEntry contains information to 3241 support the control of a single running application 3242 element." 3243 INDEX { sysApplElmtRunIndex } 3244 ::= { applElmtRunControlTable 1 } 3246 ApplElmtRunControlEntry ::= SEQUENCE { 3247 applElmtRunControlSuspend TruthValue, 3248 applElmtRunControlReconfigure TestAndIncr, 3249 applElmtRunControlTerminate TruthValue } 3251 applElmtRunControlSuspend OBJECT-TYPE 3252 SYNTAX TruthValue 3253 MAX-ACCESS read-write 3254 STATUS current 3255 DESCRIPTION 3256 "Setting this variable to 'true' requests the suspension 3257 of processing by this running application element. 3258 Setting this variable to 'false' requests that processing 3259 be resumed. The effect, if any, will be reported by the 3260 applElmtRunStatusSuspended attribute." 3261 DEFVAL { false } 3262 ::= { applElmtRunControlEntry 1 } 3264 applElmtRunControlReconfigure OBJECT-TYPE 3265 SYNTAX TestAndIncr 3266 MAX-ACCESS read-write 3267 STATUS current 3268 DESCRIPTION 3269 "Changing the value of this variable requests that the 3270 running application element re-load its configuration 3271 (like SIGHUP for many UNIX-based daemons)." 3272 ::= { applElmtRunControlEntry 2 } 3274 applElmtRunControlTerminate OBJECT-TYPE 3275 SYNTAX TruthValue 3276 MAX-ACCESS read-write 3277 STATUS current 3278 DESCRIPTION 3279 "Setting the value of applElmtRunControlTerminate to 3280 'true' requests that the running application element 3281 terminate processing and exit in an orderly manner. 3282 This is a 'polite' shutdown request." 3283 DEFVAL { false } 3284 ::= { applElmtRunControlEntry 3 } 3286 -- **************************************************************** 3287 -- 3288 -- Conformance requirements 3289 -- 3290 -- **************************************************************** 3292 applicationMibGroups OBJECT IDENTIFIER ::= 3293 { applicationMibConformance 1} 3295 applicationMonitorGroup OBJECT-GROUP 3296 OBJECTS { applSrvInstQual, 3297 applSrvName, 3298 applSrvIndex, 3299 applSrvInstance, 3300 applOpenChannelOpenTime, 3301 applOpenChannelReadRequestsLow, 3302 applOpenChannelReadFailures, 3303 applOpenChannelBytesReadLow, 3304 applOpenChannelLastReadTime, 3305 applOpenChannelWriteRequestsLow, 3306 applOpenChannelWriteFailures, 3307 applOpenChannelBytesWrittenLow, 3308 applOpenChannelLastWriteTime, 3309 applOpenFileName, 3310 applOpenFileSizeHigh, 3311 applOpenFileSizeLow, 3312 applOpenFileMode, 3313 applOpenConnectionTransport, 3314 applOpenConnectionNearEndAddr, 3315 applOpenConnectionNearEndpoint, 3316 applOpenConnectionFarEndAddr, 3317 applOpenConnectionFarEndpoint, 3318 applOpenConnectionApplication } 3319 STATUS current 3320 DESCRIPTION 3321 "This group represents the basic capabilities of this MIB." 3322 ::= { applicationMibGroups 1 } 3324 applicationFastMonitorGroup OBJECT-GROUP 3325 OBJECTS { applOpenChannelReadRequests, 3326 applOpenChannelBytesRead, 3327 applOpenChannelWriteRequests, 3328 applOpenChannelBytesWritten } 3329 STATUS current 3330 DESCRIPTION 3331 "This group comprises 64-bit counters mandatory only in 3332 high-throughput environments." 3333 ::= { applicationMibGroups 2 } 3335 applicationTransactGroup OBJECT-GROUP 3336 OBJECTS { applTransactStreamDescr, 3337 applTransactStreamUnitOfWork, 3338 applTransactStreamInvokesLow, 3339 applTransactStreamInvCumTime, 3340 applTransactStreamInvRspTime, 3341 applTransactStreamPerformsLow, 3342 applTransactStreamPrfCumTime, 3343 applTransactStreamPrfRspTime, 3344 applTransactFlowTable, 3345 applTransactFlowEntry, 3346 applTransactFlowDirection, 3347 applTransactFlowReqRsp, 3348 applTransactFlowTransLow, 3349 applTransactFlowBytesLow, 3350 applTransactFlowTime, 3351 applTransactKindTable, 3352 applTransactKindEntry, 3353 applTransactKind, 3354 applTransactKindTransLow, 3355 applTransactKindBytesLow, 3356 applTransactKindTime } 3357 STATUS current 3358 DESCRIPTION 3359 "This group comprises objects appropriate from monitoring 3360 transaction-structured flows." 3361 ::= { applicationMibGroups 3 } 3363 applicationFastTransactGroup OBJECT-GROUP 3364 OBJECTS { applTransactStreamInvokes, 3365 applTransactStreamPerforms, 3366 applTransactFlowTrans, 3367 applTransactFlowBytes, 3368 applTransactKindTrans, 3369 applTransactKindBytes } 3370 STATUS current 3371 DESCRIPTION 3372 "This group comprises 64-bit transaction counters required in 3373 high-throughput environments." 3374 ::= { applicationMibGroups 4 } 3376 applicationHistoryGroup OBJECT-GROUP 3377 OBJECTS { applPastChannelControlCollect, 3378 applPastChannelControlMaxRows, 3379 applPastChannelControlTimeLimit, 3380 applPastChannelControlRemItems, 3381 applPastChannelOpenTime, 3382 applPastChannelCloseTime, 3383 applPastChannelReadReqsLow, 3384 applPastChannelReadFailures, 3385 applPastChannelBytesReadLow, 3386 applPastChannelLastReadTime, 3387 applPastChannelWriteReqsLow, 3388 applPastChannelWriteFailures, 3389 applPastChannelBytesWritLow, 3390 applPastChannelLastWriteTime, 3391 applPastFileName, 3392 applPastFileSizeHigh, 3393 applPastFileSizeLow, 3394 applPastFileMode, 3395 applPastConTransport, 3396 applPastConNearEndAddr, 3397 applPastConNearEndpoint, 3398 applPastConFarEndAddr, 3399 applPastConFarEndpoint, 3400 applPastConApplication} 3401 STATUS current 3402 DESCRIPTION 3403 "This group models basic historical data." 3404 ::= { applicationMibGroups 5 } 3406 applicationFastHistoryGroup OBJECT-GROUP 3407 OBJECTS { applPastChannelReadRequests, 3408 applPastChannelBytesRead, 3409 applPastChannelWriteRequests, 3410 applPastChannelBytesWritten} 3411 STATUS current 3412 DESCRIPTION 3413 "This group comprises additional 64-bit objects required 3414 for recording historical data in high-volume environments." 3415 ::= { applicationMibGroups 6 } 3417 applicationTransHistoryGroup OBJECT-GROUP 3418 OBJECTS { applPastTransStreamDescr, 3419 applPastTransStreamUnitOfWork, 3420 applPastTransStreamInvCumTime, 3421 applPastTransStreamInvRspTime, 3422 applPastTransStreamPrfCumTime, 3423 applPastTransStreamPrfRspTime, 3424 applPastTransFlowTransLow, 3425 applPastTransFlowBytesLow, 3426 applPastTransFlowTime, 3427 applPastTransKindTransLow, 3428 applPastTransKindBytesLow, 3429 applPastTransKindTime } 3430 STATUS current 3431 DESCRIPTION 3432 "This group represents historical data for transaction- 3433 structured information streams." 3434 ::= { applicationMibGroups 7 } 3436 applicationFastTransHistoryGroup OBJECT-GROUP 3437 OBJECTS { applPastTransFlowTrans, 3438 applPastTransFlowBytes, 3439 applPastTransKindTrans, 3440 applPastTransKindBytes} 3441 STATUS current 3442 DESCRIPTION 3443 "This group contains 64-bit objects required for historical 3444 records on high-volume transaction-structured streams." 3445 ::= { applicationMibGroups 8 } 3447 applicationRunGroup OBJECT-GROUP 3448 OBJECTS { applElmtRunStatusSuspended, 3449 applElmtRunStatusHeapUsage, 3450 applElmtRunStatusOpenConnections, 3451 applElmtRunStatusOpenFiles, 3452 applElmtRunStatusLastErrorMsg, 3453 applElmtRunStatusLastErrorTime, 3454 applElmtRunControlSuspend, 3455 applElmtRunControlReconfigure, 3456 applElmtRunControlTerminate } 3457 STATUS current 3458 DESCRIPTION 3459 "This group represents extensions to the system application 3460 mib." 3461 ::= { applicationMibGroups 9 } 3463 applicationMibCompliance MODULE-COMPLIANCE 3464 STATUS current 3465 DESCRIPTION "The compliance statement for the application MIB." 3466 MODULE 3467 MANDATORY-GROUPS { applicationMonitorGroup, 3468 applicationHistoryGroup, 3469 applicationRunGroup } 3471 OBJECT applPastChannelControlCollect 3472 MIN-ACCESS read-only 3473 DESCRIPTION 3474 "This object should be limited to read-only 3475 access in environments with inadequate 3476 security." 3478 OBJECT applPastChannelControlMaxRows 3479 MIN-ACCESS read-only 3480 DESCRIPTION 3481 "This object should be limited to read-only 3482 access in environments with inadequate 3483 security." 3485 OBJECT applPastChannelControlTimeLimit 3486 MIN-ACCESS read-only 3487 DESCRIPTION 3488 "This object should be limited to read-only 3489 access in environments with inadequate 3490 security." 3492 OBJECT applElmtRunControlSuspend 3493 MIN-ACCESS read-only 3494 DESCRIPTION 3495 "This object should be limited to read-only 3496 access in environments with inadequate 3497 security." 3499 OBJECT applElmtRunControlReconfigure 3500 DESCRIPTION 3501 MIN-ACCESS read-only 3502 "This object should be limited to read-only 3503 access in environments with inadequate 3504 security." 3506 OBJECT applElmtRunControlTerminate 3507 MIN-ACCESS read-only 3508 DESCRIPTION 3509 "This object should be limited to read-only 3510 access in environments with inadequate 3511 security." 3513 GROUP applicationTransactGroup 3514 DESCRIPTION 3515 "The applicationTransactGroup is required when the 3516 information stream processed has a transaction 3517 structure. " 3519 GROUP applicationTransHistoryGroup 3520 DESCRIPTION 3521 "The applicationTransHistoryGroup must be implemented 3522 if applicationTransactGroup and applicationHistoryGroup 3523 are implemented." 3525 GROUP applicationFastMonitorGroup 3526 DESCRIPTION 3527 "The applicationFastMonitorGroup is mandatory when 3528 the applicationMonitorGroup is implemented and its 3529 counts group may exceed what can be represented in 32 bits." 3531 GROUP applicationFastTransactGroup 3532 DESCRIPTION 3533 "The applicationFastTransactGroup is mandatory when 3534 the applicationTransactGroup is implemented and its 3535 counts may exceed what can be represented in 32 bits." 3537 GROUP applicationFastHistoryGroup 3538 DESCRIPTION 3539 "The applicationFastHistoryGroup is mandatory when 3540 the applicationHistoryGroup is implemented and its 3541 counts may exceed what can be represented in 32 bits." 3543 GROUP applicationFastTransHistoryGroup 3544 DESCRIPTION 3545 "The applicationFastTransHistoryGroup is mandatory when 3546 the applicationTransHistoryGroup is implemented and its 3547 counts may exceed what can be represented in 32 bits." 3548 ::= { applicationMibConformance 2 } 3550 END 3552 6. Implementation Issues 3554 Unlike the system application MIB [10], in many environments support 3555 for much of this MIB requires instrumentation built into the managed 3556 resource. Some tables may be implemented by a single monitor 3557 process; for others, the implementation may be distributed within the 3558 managed system with the resources being managed. 3560 As a practical matter, this means that the management infrastructure 3561 of the managed system must support different subagents taking 3562 responsibility for different rows of a single table. This can be 3563 supported by AgentX [13], as well as some other subagent protocols 3564 such as [14], [15], and [16]. 3566 The sysApplRunElmtIndex is the key connection between this MIB and 3567 the systems application MIB. Implementations of these two MIBs 3568 intended to run concurrently on a given platform must employ a 3569 consistent policy for assigning this value to running application 3570 elements. 3572 Some of the objects defined in this MIB may carry a high run-time 3573 cost in some environments. For example, tracking transaction elapsed 3574 time could be expensive if it required two kernel calls (start and 3575 finish) per transaction. Similarly, maintaining tables of per- 3576 transaction information, rather than aggregating information by 3577 transaction type or transaction stream, could have significant 3578 storage and performance impacts. 3580 Unless a collision-free mechanism for allocating service instance 3581 indexes is in place, the structure of the service-level tables makes 3582 an index-reservation mechanism necessary. AgentX [13] is an example 3583 of a subagent protocol capable of satisfying this requirement. 3585 7. Intellectual Property 3587 The IETF takes no position regarding the validity or scope of any 3588 intellectual property or other rights that might be claimed to 3589 pertain to the implementation or use of the technology described in 3590 this document or the extent to which any license under such rights 3591 might or might not be available; neither does it represent that it 3592 has made any effort to identify any such rights. Information on the 3593 IETF's procedures with respect to rights in standards-track and 3594 standards-related documentation can be found in BCP-11. Copies of 3595 claims of rights made available for publication and any assurances of 3596 licenses to be made available, or the result of an attempt made to 3597 obtain a general license or permission for the use of such 3598 proprietary rights by implementors or users of this specification can 3599 be obtained from the IETF Secretariat. 3601 The IETF invites any interested party to bring to its attention any 3602 copyrights, patents or patent applications, or other proprietary 3603 rights which may cover technology that may be required to practice 3604 this standard. Please address the information to the IETF Executive 3605 Director. 3607 8. Acknowledgements 3609 This document was produced by the Application MIB working group. 3611 The editor gratefully acknowledges the comments and contributions of 3612 the following individuals: 3614 Harrie Hazewinkel 3615 Carl Kalbfleisch 3616 Cheryl Krupczak 3617 John Saperia 3618 Juergen Schoenwaelder 3620 9. Security Considerations 3622 By making potentially sensitive information externally accessible, 3623 the capabilities supported by the MIB have the potential of becoming 3624 security problems. 3626 The tables in this MIB are organized to separate sensitive control 3627 capabilities from less sensitive usage information. For example, the 3628 objects to control application suspend/resume are separated from 3629 those to handle reconfiguration, which in turn are distinct from 3630 those for termination. This recognizes the need to support 3631 configurations where the level of authorization needed by a manager 3632 to do a "reconfigure" might be substantially less than the level 3633 needed to terminate an application element. By keeping these in 3634 separate columns, we make it possible to set up access control that 3635 allows, for example, "reconfigure" but not "kill". 3637 The MIB is structured to be useful for managers with read-only access 3638 rights. 3640 The capabilities supported by this MIB include several that may be of 3641 value to a security administrator. These include the ability to 3642 monitor the level of usage of a given application, and to check the 3643 integrity of application components. 3645 10. References 3647 [1] Grillo, P., and S. Waldbusser, "Host Resources MIB", RFC 1514, 3648 September 1993. 3650 [2] Freed, N., and S. Kille, "Network Services Monitoring MIB", RFC 3651 2248, January 1998. 3653 [3] Freed, N., and S. Kille, "Mail Monitoring MIB", RFC 1566, January 3654 1994. 3656 [4] Brower, D., Purvy, R., Daniel, A., Sinykin, M., and J. Smith, 3657 "Relational Database Management System (RDBMS) Management 3658 Information Base (MIB) using SMIv2", RFC 1697, August 1994. 3660 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 3661 of Management Information for Version 2 of the Simple Network 3662 Management Protocol (SNMPv2)", RFC 1902, January 1996. 3664 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 3665 Conventions for Version 2 of the Simple Network Management 3666 Protocol (SNMPv2)", RFC 1903, January 1996. 3668 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3669 "Conformance Statements for Version 2 of the Simple Network 3670 Management Protocol (SNMPv2)", RFC 1904, January 1996. 3672 [8] C. Kalbfleisch, "Applicability of Standards Track MIBs to 3673 Management of World Wide Web Servers", RFC 2039, November 1996. 3675 [9] Yergeau, F., "UTF-8, a transformation format of Unicode and ISO 3676 10646", RFC 2044, October 1996. 3678 [10] Krupczak, C., and J. Saperia, "Definitions of System-Level 3679 Managed Objects for Applications", RFC 2287, February 1998. 3681 [11] ITU-T Recommendation X.744 | ISO/IEC IS 10164-18:1996, 3682 Information Technology - Open Systems Interconnection - Systems 3683 Management: Software Management Function, 1996. 3685 [12] IEEE P1387.2, POSIX System Administration - Part 2: Software 3686 Administration. (Draft) 3688 [13] Daniele, M., Francisco, D., and B. Wijnen, "Agent Extensibility 3689 (AgentX) Protocol", RFC 2257, January, 1998. 3691 [14] Rose, M., "SNMP MUX Protocol and MIB", RFC 1227, May 1991. 3693 [15] Carpenter, G. and B. Wijnen, "SNMP-DPI Simple Network Management 3694 Protocol Distributed Program Interface", RFC 1228, May 1991. 3696 [16] Carpenter, G., Curran, K., Sehgal, A., Waters, G., and B. 3697 Wijnen, "Simple Network Management Protocol Distributed Protocol 3698 Interface Version 2.0", RFC 1592, March 1994. 3700 [17] Reynolds, J. and J. Postel, "ASSIGNED NUMBERS", RFC 1700, STD 2, 3701 October, 1994. 3703 [18] Hovey, R., and S. Bradner, "The Organizations Involved in the 3704 IETF Standards Process", BCP 11, RFC 2028, October 1996. 3706 [19] ARM Working Group, "Application Response Measurement (ARM) API 3707 Guide, Version 2", September, 1997. 3709 [20] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 3710 describing SNMP Management Frameworks", RFC 2271, January 1998. 3712 [21] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 3713 Control Model for the Simple Network Management Protocol 3714 (SNMP)", RFC 2275, January 1998. 3716 11. Authors' Addresses 3718 Carl Kalbfleisch 3719 Verio, Inc. 3720 1950 Stemmons Freeway 3721 2004 INFOMART 3722 Dallas, TX 75207 3723 USA 3725 Phone: +1 972-238-8303 3726 Fax: +1 972-238-0268 3727 EMail: cwk@verio.net 3729 Cheryl Krupczak 3730 Empire Technologies, Inc. 3731 541 Tenth Street, NW Suite 169 3732 Atlanta, GA 30318 3733 USA 3735 Phone: +1 770-384-0184 3736 EMail: cheryl@empiretech.com 3737 Randy Presuhn (Editor) 3738 BMC Software, Inc. 3739 965 Stewart Drive 3740 Sunnyvale, CA 94086 3741 USA 3743 Phone: +1 408-616-3100 3744 Fax: +1 408-616-3101 3745 EMail: rpresuhn@bmc.com 3747 Jon Saperia 3748 IronBridge Networks 3749 55 Hayden Avenue 3750 Lexington, MA 02173 3751 USA 3753 Phone: +1 781-402-8029 3754 Fax: +1 781-402-8090 3755 EMail: saperia@ironbridgenetworks.com 3757 12. Full Copyright Statement 3759 Copyright (C) The Internet Society (1998). All Rights Reserved. 3761 This document and translations of it may be copied and furnished to 3762 others, and derivative works that comment on or otherwise explain it 3763 or assist in its implementation may be prepared, copied, published 3764 and distributed, in whole or in part, without restriction of any 3765 kind, provided that the above copyright notice and this paragraph are 3766 included on all such copies and derivative works. However, this 3767 document itself may not be modified in any way, such as by removing 3768 the copyright notice or references to the Internet Society or other 3769 Internet organizations, except as needed for the purpose of 3770 developing Internet standards in which case the procedures for 3771 copyrights defined in the Internet Standards process must be 3772 followed, or as required to translate it into languages other than 3773 English. 3775 The limited permissions granted above are perpetual and will not be 3776 revoked by the Internet Society or its successors or assigns. 3778 This document and the information contained herein is provided on an 3779 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3780 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3781 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3782 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3783 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.