idnits 2.17.1 draft-bierman-rmon-atmrmon-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-18) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** 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 == The page length should not exceed 58 lines per page, but there was 2 longer pages, the longest (page 19) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** 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 are 56 instances of too long lines in the document, the longest one being 12 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 249 has weird spacing: '...such as high ...' == Line 445 has weird spacing: '...n. Both types...' -- 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 (February 23, 1996) is 10282 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) -- Looks like a reference, but probably isn't: 'TBD' on line 1511 -- Looks like a reference, but probably isn't: 'ATM2-MIB' on line 1110 -- Looks like a reference, but probably isn't: 'RMON2-MIB' on line 2566 == Unused Reference: '5' is defined on line 2875, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1757 (ref. '5') (Obsoleted by RFC 2819) ** Downref: Normative reference to an Historic RFC: RFC 1513 (ref. '6') -- Possible downref: Normative reference to a draft: ref. '7' == Outdated reference: A later version (-02) exists of draft-ietf-rmonmib-rmonprot-01 ** Obsolete normative reference: RFC 1695 (ref. '9') (Obsoleted by RFC 2515) == Outdated reference: A later version (-19) exists of draft-ietf-atommib-atm2-05 Summary: 17 errors (**), 0 flaws (~~), 7 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Draft ATM-RMON MIB February 1996 4 Remote Network Monitoring MIB Extensions for ATM Networks 5 7 February 23, 1996 9 Andy Bierman 10 Bierman Consulting 11 abierman@west.net 13 Keith McCloghrie 14 Cisco Systems, Inc. 15 kzm@cisco.com 17 Status of this Memo 19 This document is an Internet-Draft. Internet-Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its areas, and 21 its working groups. Note that other groups may also distribute working 22 documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet- Drafts as reference material 27 or to cite them other than as ``work in progress.'' 29 To learn the current status of any Internet-Draft, please check the 30 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 31 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 32 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 34 Draft ATM-RMON MIB February 1996 36 1. Introduction 38 This memo defines an experimental portion of the Management Information 39 Base (MIB) for use with network management protocols in the Internet 40 community. In particular, it describes managed objects used for 41 managing remote monitoring probes, specifically for ATM networks. 43 1.1. The SNMP Network Management Framework 45 The SNMP Network Management Framework presently consists of three major 46 components. They are: 48 the SMI, described in RFC 1902 [1] - the mechanisms used for 49 describing and naming objects for the purpose of management. 51 the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects 52 for the Internet suite of protocols. 54 the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for 55 accessing managed objects. 57 The Framework permits new objects to be defined for the purpose of 58 experimentation and evaluation. 60 1.2. Object Definitions 62 Managed objects are accessed via a virtual information store, termed the 63 Management Information Base or MIB. Objects in the MIB are defined 64 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 65 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 66 an administratively assigned name. The object type together with an 67 object instance serves to uniquely identify a specific instantiation of 68 the object. For human convenience, we often use a textual string, 69 termed the descriptor, to refer to the object type. 71 Draft ATM-RMON MIB February 1996 73 2. Overview 75 This document addresses issues related to applying 'RMON technology' to 76 ATM Networks: 78 - functional applicability of existing RMON groups 80 - new functionality for ATM networks 82 - collection source design issues 84 - flexible resource allocation 86 - data reduction mechanisms 88 - standardization track issues 90 RMON-based applications can provide system administrators with valuable 91 data about network utilization and behavior. RMON agents offer 92 applications developers resource-intensive functions such as high-level 93 statistics gathering and low-level filtering/capture of MAC frames. 95 RMON is traditionally deployed as one or more NMS applications managing 96 multiple RMON probes, each of which is monitoring one or more network 97 segments. RMON for ATM networks will require a different deployment 98 model, as well as many other new MIB features. 100 2.1. RMON Resource Sharing Model 102 There are some design features that are used throughout all the RMON 103 MIBs. The most important is the RMON resource-sharing model. RMON 104 agents are expected to create certain 'common' data-collection resources 105 (ownerString starts with the string "monitor"). Only system 106 administrators should be allowed to delete or modify these 'monitor- 107 owned' resources. 109 NMS applications can create short-lived control entries (ownerString set 110 to unique NMS-ID) if the monitor-owned collections are not appropriate 111 for a given task. Some features, such as topN reporting, event- 112 reporting, history collection (other than 30 sec/30 min intervals), and 113 filter/capture, require NMS configuration in most implementations. 115 The resource owner (NMS) is expected to pick a unique value for the 116 owner string and supply this value in the first setRequest PDU creating 117 Draft ATM-RMON MIB February 1996 119 the control row. An NMS must check the rowStatus object (i.e. 120 errorStatus of PDU setting status to createAnd* before using the 121 resource, to make sure another NMS was not allocated the resource 122 instead. Before terminating, the NMS application must delete any 123 control entries that it created. There is no control-row garbage 124 collection defined in RMON, so an NMS application must check for its own 125 stale control entries before creating new ones, upon startup. 127 An NMS application may optionally use another applications' resources in 128 a read-only manner, if applicable. Usually, this is only done when a 129 resource request is refused. The system administrator is responsible for 130 deleting RMON resources (monitor or NMS-owned) to make room for new 131 applications. 133 2.2. Relationship to Existing MIBs 135 There are several RFCs (and I-Ds) which specify RMON MIBs and agent 136 specifications: 138 2.2.1. RMON 140 The Remote Network Monitoring MIB (RMON or RMON-1) (RFC1757) [5]] 141 provides several management functions that may be directly or indirectly 142 applicable to ATM Networks: 144 - detailed link layer statistics for ethernet segments (etherStats 145 group) 147 - remote polling of detailed link layer statistics for ethernet 148 segments (history, etherHistory groups) 150 - basic statistics--per host and per conversation--for all valid MAC 151 addresses discovered on each monitored segment (host and matrix 152 groups) 154 - TopN Report statistics (topN talkers or errors)--per-host--for each 155 valid MAC address discovered on each monitored segment (hostTopN 156 group) bit-level frame filtering and frame-slice capture (filter, 157 channel, capture groups) 159 - simple threshold monitoring, event-logging, and event-notification 160 for any MIB instance 162 Draft ATM-RMON MIB February 1996 164 2.2.2. TR-RMON 166 The Token Ring Extensions for RMON MIB (RFC1513) (TR-RMON) [6] provides 167 the same kind of detailed link layer statistics and remote polling as 168 found in RMON-1 (tokenRingMLStats/History, tokenRingPStats/History). The 169 TR-RMON MIB is highly integrated with RMON-1, which is possible because 170 both link layers use the same address format. An RMON MIB for ATM could 171 be structured and positioned like the TR-MIB, but none of the shared 172 tables can be directly applied to ATM. Since RMON-1 will be augmented 173 and updated by RMON-2, any ATM-RMON standardization effort within the 174 IETF should align with the RMON-2 MIB, but maintain the same 'extensions 175 MIB' structure as found in the TR-RMON MIB. 177 2.2.3. RMON-2 MIB 179 The emerging 'RMON-2' standard (RMON-2) [7] provides many additions and 180 improvements to RMON-1: 182 - complete protocol distribution per segment (or 'collection source') 184 - collection of network to MAC address bindings seen in packets on 185 all segments 187 - collection of source MAC address to physical interface bindings on 188 all segments 190 - probe configuration, such as startup parameters and trap 191 destination management 193 - collection of per network-layer host basic statistics (network 194 layer and above) 196 - collection of per-conversation basic statistics (network layer and 197 above) 199 - TopN Report statistics per conversation (network layer and above) 201 - improvements such as relative-offset frame filtering, user-defined 202 remote-polling, faster table retrieval, and better accuracy 203 reporting. 205 Although the protocol analysis features are not directly applicable, 206 there are many design improvements in RMON-2 that can be integrated into 207 ATM-RMON: 209 Draft ATM-RMON MIB February 1996 211 - TimeFilter indexing (see section on post-collection data reduction 212 for details) 214 - TopN report improvements such as auto-restart, report count, and 215 'last-create-time' to detect discontinuities 217 - Control entry inserts and deletes counters (this replaces the 218 RMON-1 'table-size' object) 220 - ProtocolDirectory collection-control design (i.e. central 221 configuration defines what data is collected in each functional 222 group) 224 2.2.4. RMON-2 Protocol Identifiers 226 The RMON Protocol Identifiers Specification (RMONPROT) [8] defines 227 encoding rules for protocolDirID, protocolDirParameters, and 228 protocolDirType MIB objects It is required only if RMON-2 packet 229 analysis is applied to frames monitored (on circuits which use frames). 230 It is not directly applicable to the ATM-RMON MIB, and not discussed in 231 this document. 233 2.2.5. ATOM MIB 235 The Atom MIB is the fundemental MIB for manging ATM networks (RFC 1695) 236 [9], but it is not directly referenced by this MIB, except for use of 237 the 'IfIndex' textual convention. It is possible other textual 238 conventions will be imported as well (TBD). 240 2.2.6. ATOM Supplemental MIB 242 The Atom Supplemental MIB [10] defines additional management 243 capabilities for ATM networks. The 'AtmAddr' textual convention is 244 imported from this MIB, but no other relationship exists at this time. 246 2.3. ATM-RMON Functional Requirements 248 Applying RMON to ATM networks will require some new design changes and 249 new functionality. Special problems such as high speeds, "cells vs. 250 frames" issues, and the connection-oriented nature of ATM need special 251 MIB solutions in order to implement RMON for ATM networks. 253 Draft ATM-RMON MIB February 1996 255 2.3.1. Collection Perspective 257 There are four different 'collection perspectives' that should be 258 accommodated: 260 (A) stand-alone probe attached to a single port of a switch. ATM 261 traffic is copied somehow to the RMON probe. 263 (B) embedded probe within a switch., with no access to the switch 264 fabric. ATM traffic is copied somehow to the RMON probe. 266 (C) embedded probe within a switch, with access to the switch fabric. 267 ATM traffic is monitored directly, probably implemented in 268 hardware. Probes of this type are likely to monitor traffic at 269 cell header level only. A lower level of conformance, or some other 270 mechanism (e.g. additional software), will most likely be needed 271 for this type of probe. 273 (D) stand-alone probe, tapping an NNI link between two switches. ATM 274 traffic is monitored directly (subject to probe capabilities), 275 without switch intervention. All cells in both directions are 276 copied somehow to the RMON probe. 278 Draft ATM-RMON MIB February 1996 280 Figure 1: Probe Location 282 +----------------------------------------------------------------------------+ 283 | | 284 | External Probe w/Circuit Steering Internal Probe w/Circuit Steering | 285 | --------------------------------- --------------------------------- | 286 | | 287 | || || | 288 | || || | 289 | +----------++----------+ +----------++-----------+ | 290 | | (A) | | (B) | | 291 | ====| ATM Switch |==== ====| ATM Switch | | |==== | 292 | | | | V V | | 293 | +----------++----------+ | +------------------+ | | 294 | || | | | | RMON probe | | | 295 | || V V | +------------------+ | | 296 | +----------------------+ +----------++-----------+ | 297 | | RMON probe | || | 298 | +----------------------+ || | 299 | | 300 | | 301 | Internal Probe wo/Circuit Steering External Probe wo/Circuit Steering | 302 | ---------------------------------- ---------------------------------- | 303 | | 304 | || || || | 305 | || || || | 306 | +--------++-------+ +------++------+ +------++------+ | 307 | | (C) | | (D) | | | | 308 | ====| ATM Switch w/ |==== ====| ATM Switch 1 |===++==| ATM Switch 2 | | 309 | | internal RMON | | | || | | | 310 | | instrumentation | +------++------+ || +------++------+ | 311 | +-----------------+ || || || | 312 | || || || || | 313 | || +------++------+ | 314 | | RMON probe | | 315 | +--------------+ | 316 | | 317 +----------------------------------------------------------------------------+ 319 Unless RMON instrumentation is embedded into the switch fabric (C), or 320 placed between two switches (D), then circuit steering is required (A 321 and B) for RMON instrumentation software to access ATM traffic. For such 322 probes, each full-duplex circuit is (presumably) mapped into two 323 redirected half-duplex circuits: 325 Draft ATM-RMON MIB February 1996 327 - inbound(ifIndex/VPI/VCI) 329 - outbound(ifIndex/VPI/VCI) 331 A 'probe-tap' (D) does not pre-filter data by selecting particular 332 circuits for monitoring. Instead, it receives al VCs on an NNI link, 333 without switch participation. 335 2.3.2. Cell Collection Requirements 337 The ATM-RMON MIB will provide the following new functionality: 339 - ATM layer instrumentation 341 - complex collection source aggregation 343 - data reduction configuration and status 345 - basic cell statistics (i.e. statsTable) 347 - basic cell statistics per host (i.e. hostTable) 349 - basic cell counts per conversation (i.e. matrixTable) 351 Circuit Steering requirements are not addressed in this document. RMON 352 collection requirements will be considered independently of circuit 353 steering techniques. Although references to 'copied' circuits are made 354 in this document, actual circuit-steering implementation may be 355 different. 357 At this time, only some very basic statistics are defined: 359 - point-to-point cell count 361 - point-to-multipoint cell count 363 - number of point-to-point calls 365 - number of point-to-multipoint calls 367 - total point-to-point connection time 369 - total point-to-multipoint connection time 371 Draft ATM-RMON MIB February 1996 373 Other statistics (e.g. error counters) may be added in the future. 375 2.3.3. Frame Collection Requirements 377 An optional feature set for ATM-RMON is the analysis of frames on AAL-5 378 circuits. This can be accomplished with some minor additions to the 379 RMON-1 or RMON-2 MIBs. New values for dataSource objects can be defined 380 which reference ATM collection sources (see MIB proposal below). The 381 data can be formatted into RMON-1 host, matrix, hostTopN, and 382 filter/capture groups with virtually no MIB changes. By adding 383 encapsulation definitions to the RMON-2 protocolDirectory, RMON-2 host, 384 matrix, matrixTopN, and filter2 groups can be implemented for ATM 385 network traffic. 387 [TBD: Details on frame analysis integration w/RMON-1 and RMON-2 MIBs.] 389 2.4. ATM-RMON Design Goals 391 The RMON Working Group within the Internet Engineering Task Force (IETF) 392 will be updating and augmenting the RMON MIB soon, and several of these 393 changes can be incorporated into an ATM-RMON MIB. The main advantages to 394 'borrowing' from the existing RMON MIB: 396 - allow system administrators to reuse operational experience with 397 RMON concepts and RMON data presentation (e.g. basic/host/matrix 398 stats for a given media or protocol). 400 - allow portions of standard MIBs to be applied directly to ATM-RMON 401 without modification. 403 - allow RMON NMS and probe vendors to possibly take advantage of 404 their RMON-1 implementation experience. 406 - allow flexible configuration with low complexity. 408 ATM-RMON will require new configuration mechanisms to deal with varying 409 application needs and probe capabilities. RMON-1 defines a 'dataSource' 410 object of type OBJECT IDENTIFIER, which allows new or proprietary 411 mechanisms beyond the 'ifIndex' object. RMON-2 provides for extension of 412 allowable dataSource values. (The 'ifIndex.N' and 413 'rptrGroupPortIndex.N.M' formats are the only collection sources 414 supported by the RMON WG at this time, but vendors are free to define 415 unofficial values.) New MIB tables to specify collection parameters for 416 Draft ATM-RMON MIB February 1996 418 ATM will be required. The dataSource object can be used to reference a 419 circuit-selection control entry instead of an instance of ifIndex. 421 The ability to select circuits for monitoring is important for the 422 conservation of agent resources. An NMS must be able to specify an 423 arbitrary number of circuits (subject to agent capabilities), in 424 combination with circuits that are selected by the ATM address(es). This 425 requires: 427 - a mechanism to include or exclude connections by {ifIndex/VPI/VCI} 428 tuples -- intended for PVC capture 430 - a mechanism to include or exclude all connections for a given ATM 431 address or masked address -- intended for SVC capture 433 - a mechanism to 'glue' all the selection logic together 435 2.4.1. Data Reduction 437 Traditionally, RMON host and matrix tables can be very large, and take a 438 great deal of resources to manage by the NMS and maintain by the agent. 439 The high speeds and complex collection requirements make it very 440 desirable to reduce both the agent and NMS load for processing RMON 441 data. 443 Generally, agent resources can be saved with pre-collection data 444 reduction, and NMS resources can be saved with post-collection data 445 reduction. Both types are integrated into ATM-RMON. 447 2.4.1.1. Pre-collection Data Reduction 449 The most effective way to save probe resources is to limit what data is 450 ever processed in any manner by the probe: 452 - sampling of frames to allow a probe to decode a subset of all 453 possible frames on a given collection source. 455 - need to disallow sampling on some circuits. 457 - sampling configuration -- need balance between NMS and agent 458 configuration 460 - need sampling accuracy reporting 462 Draft ATM-RMON MIB February 1996 464 - need powerful, yet easy-to-configure circuit selection to direct 465 probe resources most efficiently 467 Resources can be optimized (in an implementation-specific manner) by 468 statistical sampling of all cells within a given cell flow. Sampling 469 may also apply to circuit selection on one or more ports within a given 470 switch. 472 Sampling can be useful for frame analysis, and accomplished (in an 473 implementation-specific manner) by capturing all the consecutive cells 474 which comprise a particular frame. 476 2.4.1.2. Post-collection Data Reduction 478 Even with pre-collection data reduction it is likely ATM-RMON data 479 tables will grow quite large, so it is also desirable to minimimze the 480 number of SNMP transactions required to retrieve or refresh these data 481 tables. The mechanisms included in this MIB are: 483 - Time Filter indexing -- allows an NMS to retrieve only the changed 484 values since its last polling interval. 486 - selection aggregation -- address-masking capability of the circuit 487 selection feature allows an NMS to reduce the number of actual 488 counters maintained by the probe. 490 - TopN Report aggregation -- probe continuously monitors the top 491 talkers over a given interval, and automatically generates a report 492 at the end of each interval. 494 2.4.2. Collection Source Issues 496 The current RMON 'dataSource' model is not particularly useful for ATM 497 networks, since ATM is connection-oriented, and is not used in this MIB. 498 Instead, a set of global tables are used to define 'circuit selection 499 groups' (called 'vcSelectGroups'). Traditional RMON collections (e.g. 500 stats, host, hostTopN, matrix) can be done using a vcSelectGroup as the 501 dataSource. Some issues regarding the design of the ATM-RMON 'dataSource 502 model' include: 504 - collection criteria must be detailed -- combined criteria with 505 include/exclude , masking 507 Draft ATM-RMON MIB February 1996 509 - collection criteria setup cannot be modified on the fly for a 510 particular vcSelectGroup, while any collections based on that 511 vcSelectGroup are in progress. However, vcSelectGroups can be added 512 and deleted while collections based on existed vcSelectGroups are 513 in progress. 515 - selection MIB table setup rules TBD (i.e. overall logic is 516 combinatorial, but some precedence rules and corner cases must be 517 documented). 519 Draft ATM-RMON MIB February 1996 521 3. MIB Proposal 523 The following MIB proposal is based, in part, on the RMON-2 MIB. The 524 open issues list: 526 - no error counter instrumentation yet 528 - no matrix TopN functionality yet 530 - no notifications/traps defined yet 532 - still needs to be syntax-checked and MIB-linted 534 some details on configuration, rollover time issues, 64-bit counter 535 SMI issues, and frame/cells/both selection are still TBD 537 RMON-1 and RMON-2 integration is achieved by setting the particular 538 dataSource object to reference an instance of the 'vcSelectGroupIndex' 539 object, but details are not discussed in this MIB. 541 3.1. MIB Structure 543 The MIB contains four groups: 545 - vcSelect -- circuit selection; data tables indexed by a common 546 index 'vcSelectGroupIndex', which replaces the dataSource indirect 547 pointer and arbitrary small integer index used in RMON-1/RMON-2 549 - atmStats -- basic statistics; allows individual host traffic 550 contribution percentage to be easily calculated. 552 - atmHost -- ATM host statistics and hostTopN reporting 554 - atmMatrix -- ATM circuit statistics 556 Draft ATM-RMON MIB February 1996 558 Figure 2: ATM-RMON MIB Structure 560 +-----------------------------------------------------------------------------+ 561 | | 562 | +---------------+ | 563 | | vcSelectGroup | +------------+ | 564 | +---------------+ > ----> | atmStats | | 565 | | | > +------------+ | 566 | | | > | 567 | | | +-----------+ > +-------------+ | 568 | | +-> | pvcSelect | > +------------+ +-+-----------+ | | 569 | | +-----------+ > ----> | atmHost | ---> | atmHostTopN |-+ | 570 | | > +------------+ +-------------+ | 571 | | > | 572 | | +-----------+ > | 573 | +---> | svcSelect | > +------------+ | 574 | +-----------+ > ----> + atmMatrix | | 575 | > +------------+ | 576 | > | 577 | | 578 +-----------------------------------------------------------------------------+ 580 The vcSelectGroup is used to define the VCCs to be monitored for a 581 particular set of functions (a subset of all ATM-RMON, RMON-1, and 582 RMON-2 groups). Each vcSelectGroup is used as a collection source for 583 zero or one atmStats, atmHost, and atmMatrix collections. There may be 584 an arbitrary number of atmHostTopN entries defined per vcSelectGroup. 586 For processing of frames collected (in an implementation-specific way) 587 from the vcSelectGroup, the appropriate RMON-1 or RMON-2 dataSource 588 instance is set to the OBJECT IDENTIFIER 'vcSelectGroupIndex.I'. [TBD: 589 Row creation, modification, and deletion problems related to table 590 dependencies between ATM-RMON and the other RMON MIBs. 592 For processing of packets collected on behalf the RMON-2 MIB, the 593 propoer protocol identifiers must be set up before the nlHost, alHost, 594 nlMatrix, alMatrix, and filter2 groups can be utilized. [TBD ATM 595 encapsulation macro identifier additions to [8].] 596 Draft ATM-RMON MIB February 1996 598 4. Definitions 600 ATM-RMON-MIB DEFINITIONS ::= BEGIN 602 IMPORTS 603 MODULE-IDENTITY, OBJECT-TYPE, Counter32, 604 Integer32, Gauge32, IpAddress, 605 TimeTicks, Counter64, experimental 606 FROM SNMPv2-SMI 607 TEXTUAL-CONVENTION, RowStatus, DisplayString, 608 TimeStamp, TruthValue 609 FROM SNMPv2-TC 610 MODULE-COMPLIANCE, OBJECT-GROUP 611 FROM SNMPv2-CONF 612 OwnerString 613 FROM RFC1757-MIB 614 ZeroBasedCounter32, LastCreateTime, TimeFilter 615 FROM RMON2-MIB 616 IfIndex 617 FROM ATM-MIB 618 AtmAddr 619 FROM ATM2-MIB; 621 -- Remote Network Monitoring MIB for ATM Networks 623 atmRmon MODULE-IDENTITY 624 LAST-UPDATED "9602210000Z" 625 ORGANIZATION "IETF" 626 CONTACT-INFO 627 "Andy Bierman 628 Bierman Consulting 629 Phone: +1 805 648 2028 630 Email: abierman@west.net 632 Keith McCloghrie 633 Cisco Systems, Inc. 634 Phone: +1 408 526-5260 635 Email: kzm@cisco.com" 636 DESCRIPTION 637 "The MIB module for managing remote monitoring device 638 implementations for ATM networks." 639 ::= { experimental xx } 641 vcSelect OBJECT IDENTIFIER ::= { atmRmon 1 } 642 atmStats OBJECT IDENTIFIER ::= { atmRmon 2 } 643 Draft ATM-RMON MIB February 1996 645 atmHost OBJECT IDENTIFIER ::= { atmRmon 3 } 646 atmMatrix OBJECT IDENTIFIER ::= { atmRmon 4 } 648 atmRmonConformance OBJECT IDENTIFIER ::= { atmRmon 5 } 649 Draft ATM-RMON MIB February 1996 651 -- Textual Conventions: 653 QoSIndex ::= TEXTUAL-CONVENTION 654 STATUS current 655 DESCRIPTION 656 "This TC describes an object that identifies the cell 657 delivery quality-of-service classification, associated with 658 a particular vcSelectGroup collection." 659 SYNTAX INTEGER { 660 unknownQos(1), -- includes 'other'; [need separate enum?] 661 cbrQos(2), -- constant bit rate 662 rtVbrQos(3), -- variable bit rate (real-time) 663 nrtVbrQos(4), -- variable bit-rate (non-real-time) 664 abrQos(5), -- available bit rate 665 ubrQos(6) -- unspecified bit rate 666 } 668 ResourcePriority ::= TEXTUAL-CONVENTION 669 STATUS current 670 DESCRIPTION 671 "This TC describes an object which indicates the resource 672 priority of the entire entry. Lower priorities indicate a 673 lesser requirement to retain resources than higher priority 674 values. A probe is strongly encouraged, but not required, 675 to honor all priority requests, all of the time. 677 Objects declared with this TC should be contained within a 678 conceptual control table entry. The indicated resource 679 priority applies to the control entry and all internal data 680 structures maintained on behalf of the control entry. 682 A probe is expected to honor the priority requests in an 683 implementation-dependent way. At this time, it is 684 unspecified as to the priority ordering of entries with the 685 same ResourcePriority value." 686 SYNTAX INTEGER { 687 lowPriority(1), 688 normalPriority(2), 689 highPriority(3) 690 } 692 ZeroBasedCounter64 ::= TEXTUAL-CONVENTION 693 STATUS current 695 Draft ATM-RMON MIB February 1996 697 DESCRIPTION 698 "This TC describes an object which counts events with the 699 following semantics: objects of this type will be set to 700 zero(0) on creation and will thereafter count appropriate 701 events, wrapping back to zero(0) when the value 2^64 is 702 reached. 704 Provided that an application discovers the new object within 705 the minimum time to wrap it can use the initial value as a 706 delta since it last polled the table of which this object is 707 part. It is important for a management station to be aware 709 of this minimum time and the actual time between polls, and 710 to discard data if the actual time is too long or there is 711 no defined minimum time. 713 Typically this TC is used in tables where the INDEX space is 714 constantly changing and/or the TimeFilter mechanism is in 715 use." 716 -- THIS IS BROKEN AND NEEDS TO BE CHANGED ASAP! 717 -- For SNMPv2, a new type Unsigned64 is needed 718 -- don't know what to do for SNMPv1 yet 719 -- choices are OCTET STRING (SIZE(8)) using 2 720 -- ZeroBasedCounter32 objects instead 721 SYNTAX Counter64 723 Draft ATM-RMON MIB February 1996 725 -- 726 -- Virtual Circuit Selection group (vcSelect) 727 -- 728 -- Defines the circuits to be included or excluded in 729 -- a particular host or matrix collection 730 -- vcSelectGroupTable 731 -- pvcSelectTable 732 -- svcSelectTable 734 vcSelectGroupTable OBJECT-TYPE 735 SYNTAX SEQUENCE OF VcSelectGroupEntry 736 MAX-ACCESS not-accessible 737 STATUS current 738 DESCRIPTION 739 "Controls the setup of virtual circuit selection criteria 740 used on behalf of any collection associated with entries in 741 this table (e.g. atmHostTable). 743 This table allows pvcSelect and svcSelect entries with the 744 same value of vcSelectGroupIndex to be grouped together to 745 form selection criteria logical-OR expressions. 747 Rules for combining and prioritizing the order of pvcSelect 748 and svcSelect entries: 750 Each pvcSelect or svcSelect entry is grouped together by 751 its major index (vcSelectGroupIndex), and is evaluated in 752 the order of its minor index (pvcSelectIndex or 753 svcSelectIndex). 755 Each successive pvcEntry defines a PVC to be included or 756 excluded from the vcSelectGroup. These are evaluated, in 757 ascending order of pvcSelectIndex, to determine the PVC 758 select criteria for this vcSelectGroup. Higher-indexed 759 entries have precedence when resolving conflicts. [TBD: 760 More detail, Error checking and reporting] 762 Each successive svcEntry defines a group of SVCs to be 763 included or excluded from the vcSelectGroup, by masked 764 ATM address. This mask identifies ATM addresses (calling 765 or called party) that are using one or more SVCs 766 identified by the probe (in an implementation-specific 767 manner). 769 Each entry is evaluated, in ascending order of 771 Draft ATM-RMON MIB February 1996 773 svcSelectIndex, to determine the SVC select criteria for 774 this vcSelectGroup. Higher-indexed entries have 775 precedence when resolving conflicts. [TBD: More detail 776 on conflicts, error checking, and error reporting] 778 Rationale: This table controls selection of the circuits to 779 be monitored on behalf of one or more collections (e.g. host 780 or matrix) performed by this probe." 781 ::= { vcSelect 1 } 783 vcSelectGroupEntry OBJECT-TYPE 784 SYNTAX VcSelectGroupEntry 785 MAX-ACCESS not-accessible 786 STATUS current 787 DESCRIPTION 788 "A conceptual row in the vcSelectGroupTable. 790 An example of the indexing of this entry is 791 vcSelectGroupCreateTime.7" 792 INDEX { vcSelectGroupIndex } 793 ::= { vcSelectGroupTable 1 } 795 VcSelectGroupEntry ::= SEQUENCE { 796 vcSelectGroupIndex Integer32, 797 vcSelectGroupDescr DisplayString, 798 vcSelectGroupCreateTime LastCreateTime, 799 vcSelectGroupOwner OwnerString, 800 vcSelectGroupStatus RowStatus 801 } 803 vcSelectGroupIndex OBJECT-TYPE 804 SYNTAX Integer32 (1..65535) 805 MAX-ACCESS not-accessible 806 STATUS current 807 DESCRIPTION 808 "A unique index for this vcSelectGroupEntry." 809 ::= { vcSelectGroupEntry 1 } 811 vcSelectGroupDescr OBJECT-TYPE 812 SYNTAX DisplayString (SIZE(0..64)) 813 MAX-ACCESS read-create 814 STATUS current 815 DESCRIPTION 816 "An administratively-assigned descriptive label for this 817 vcSelectGroup entry." 819 Draft ATM-RMON MIB February 1996 821 ::= { vcSelectGroupEntry 2 } 823 vcSelectGroupCreateTime OBJECT-TYPE 824 SYNTAX LastCreateTime 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "The value of sysUpTime when this Group entry was activated. 829 This can be used by the management station to ensure that 830 the table has not been deleted and recreated between polls." 831 ::= { vcSelectGroupEntry 3 } 833 vcSelectGroupOwner OBJECT-TYPE 834 SYNTAX OwnerString 835 MAX-ACCESS read-create 836 STATUS current 837 DESCRIPTION 838 "The entity that configured this entry and is therefore 839 using the resources assigned to it." 840 ::= { vcSelectGroupEntry 4 } 842 vcSelectGroupStatus OBJECT-TYPE 843 SYNTAX RowStatus 844 MAX-ACCESS read-create 845 STATUS current 846 DESCRIPTION 847 "The status of this row. 849 An entry may not exist in the active state unless all 850 objects in the entry have an appropriate value. All 851 pvcSelectEntries and svcSelectEntries with a corresponding 852 value of vcSelectGroupIndex must be in the active state 853 before this object may be set to active(1). 855 If this object is not equal to active(1), all associated 856 data collections shall be deleted. That is, any associated 857 collections in the atmHostTable or atmMatrixTable. 859 Note that pvcSelectEntries and svcSelectEntries are not 860 deleted when this entry leaves the active state." 861 ::= { vcSelectGroupEntry 5 } 863 Draft ATM-RMON MIB February 1996 865 -- pvcSelectTable 866 -- 867 -- Defines the PVCs to be included or excluded in 868 -- a particular data collection (e.g. host or matrix) 870 pvcSelectTable OBJECT-TYPE 871 SYNTAX SEQUENCE OF PvcSelectEntry 872 MAX-ACCESS not-accessible 873 STATUS current 874 DESCRIPTION 875 "Controls the setup of PVC circuit selection criteria for 876 the host and matrix groups. 878 Rationale: This table controls selection of the virtual 879 circuits to be monitored on behalf of one or more 880 collections performed by this probe." 881 ::= { vcSelect 2 } 883 pvcSelectEntry OBJECT-TYPE 884 SYNTAX PvcSelectEntry 885 MAX-ACCESS not-accessible 886 STATUS current 887 DESCRIPTION 888 "A conceptual row in the pvcSelectTable. 890 An example of the indexing of this entry is 891 pvcSelectCreateTime.7.2" 892 INDEX { vcSelectGroupIndex, pvcSelectIndex } 893 ::= { pvcSelectTable 1 } 895 PvcSelectEntry ::= SEQUENCE { 896 pvcSelectIndex Integer32, 897 pvcSelectIfIndex IfIndex, 898 pvcSelectVPI Integer32, 899 pvcSelectVCI Integer32, 900 pvcSelectInclude TruthValue, 901 pvcSelectCreateTime LastCreateTime, 902 pvcSelectOwner OwnerString, 903 pvcSelectStatus RowStatus 904 } 906 pvcSelectIndex OBJECT-TYPE 907 SYNTAX Integer32 (1..65535) 908 MAX-ACCESS not-accessible 909 STATUS current 911 Draft ATM-RMON MIB February 1996 913 DESCRIPTION 914 "A unique index for this pvcSelectEntry." 915 ::= { pvcSelectEntry 1 } 917 pvcSelectIfIndex OBJECT-TYPE 918 SYNTAX IfIndex 919 MAX-ACCESS read-create 920 STATUS current 921 DESCRIPTION 922 "The ifIndex value describing the ATM interface associated 923 with this pvcSelectEntry. 925 This object may not be modified if the associated instance 926 of pvcSelectStatus is equal to active(1)." 927 ::= { pvcSelectEntry 2 } 929 pvcSelectVPI OBJECT-TYPE 930 SYNTAX Integer32 931 MAX-ACCESS read-create 932 STATUS current 933 DESCRIPTION 934 "The VPI value associated with this pvcSelectEntry. 936 [TBD: wildcarding] 938 This object may not be modified if the associated instance 939 of pvcSelectStatus is equal to active(1)." 940 ::= { pvcSelectEntry 3 } 942 pvcSelectVCI OBJECT-TYPE 943 SYNTAX Integer32 944 MAX-ACCESS read-create 945 STATUS current 946 DESCRIPTION 947 "The VCI value associated with this pvcSelectEntry. 949 [TBD: wildcarding] 951 This object may not be modified if the associated instance 952 of pvcSelectStatus is equal to active(1)." 953 ::= { pvcSelectEntry 4 } 955 pvcSelectInclude OBJECT-TYPE 956 SYNTAX TruthValue 957 MAX-ACCESS read-create 959 Draft ATM-RMON MIB February 1996 961 STATUS current 962 DESCRIPTION 963 "This object controls whether the indicated PVC is included 964 or excluded in the associated vcSelectGroup. 966 If this object has the value true(1), the circuit indicated 967 by this entry is included in the vcSelectGroup. 969 If it has the value false(2), the circuit indicated by this 970 entry is excluded from the vcSelectGroup. 972 This object may not be modified if the associated instance 973 of pvcSelectStatus is equal to active(1)." 974 ::= { pvcSelectEntry 5 } 976 pvcSelectLastCreateTime OBJECT-TYPE 977 SYNTAX LastCreateTime 978 MAX-ACCESS read-only 979 STATUS current 980 DESCRIPTION 981 "The value of sysUpTime when this pvcSelect entry was 982 activated. This can be used by the management station to 983 ensure that the table has not been deleted and recreated 984 between polls." 985 ::= { pvcSelectEntry 6 } 987 pvcSelectOwner OBJECT-TYPE 988 SYNTAX OwnerString 989 MAX-ACCESS read-create 990 STATUS current 991 DESCRIPTION 992 "The entity that configured this entry and is therefore 993 using the resources assigned to it." 994 ::= { pvcSelectEntry 7 } 996 pvcSelectStatus OBJECT-TYPE 997 SYNTAX RowStatus 998 MAX-ACCESS read-create 999 STATUS current 1000 DESCRIPTION 1001 "The status of this row. 1003 An entry may not exist in the active state unless all 1004 objects in the entry have an appropriate value. 1006 Draft ATM-RMON MIB February 1996 1008 This object may not be modified if the associated instance 1009 of vcSelectGroupStatus is equal to active(1). 1011 If this object is not equal to active(1), all associated 1012 data collections shall be deleted. That is, any associated 1013 collections in the atmHostTable or atmMatrixTable." 1014 ::= { pvcSelectEntry 8 } 1016 -- svcSelectTable 1017 -- 1018 -- Defines the SVCs to be included or excluded in 1019 -- a particular host or matrix collection 1021 svcSelectTable OBJECT-TYPE 1022 SYNTAX SEQUENCE OF SvcSelectEntry 1023 MAX-ACCESS not-accessible 1024 STATUS current 1025 DESCRIPTION 1026 "Controls the setup of SVC circuit selection criteria for 1027 the host and matrix groups. 1029 Rules for combining multiple svcSelectEntries within the 1030 same vcSelectGroup [TBD]. 1032 [TBD -- Error conditions, conflict resolution] 1034 Rationale: This table controls selection of the circuits to 1035 be monitored on behalf of one or more collections (either 1036 host or matrix) performed by this probe." 1037 ::= { vcSelect 3 } 1039 svcSelectEntry OBJECT-TYPE 1040 SYNTAX SvcSelectEntry 1041 MAX-ACCESS not-accessible 1042 STATUS current 1043 DESCRIPTION 1044 "A conceptual row in the svcSelectTable. 1046 An example of the indexing of this entry is 1047 svcSelectControlCreateTime.7.1" 1048 INDEX { vcSelectGroupIndex, svcSelectIndex } 1049 ::= { svcSelectTable 1 } 1051 SvcSelectEntry ::= SEQUENCE { 1052 Draft ATM-RMON MIB February 1996 1054 svcSelectIndex Integer32, 1055 svcSelectIfIndex IfIndex, 1056 svcSelectAddr AtmAddr, 1057 svcSelectAddrMask AtmAddr, 1058 svcSelectInclude TruthValue, 1059 svcSelectCreateTime LastCreateTime, 1060 svcSelectOwner OwnerString, 1061 svcSelectStatus RowStatus 1062 } 1064 svcSelectIndex OBJECT-TYPE 1065 SYNTAX Integer32 (1..65535) 1066 MAX-ACCESS not-accessible 1067 STATUS current 1068 DESCRIPTION 1069 "A unique index for this svcSelectEntry." 1070 ::= { svcSelectEntry 1 } 1072 svcSelectIfIndex OBJECT-TYPE 1073 SYNTAX IfIndex 1074 MAX-ACCESS read-create 1075 STATUS current 1076 DESCRIPTION 1077 "The ifIndex value describing the ATM interface associated 1078 with this svcSelectEntry. The SVCs are identified for this 1079 entry on this interface only. 1081 This object may not be modified if the associated instance 1082 of svcSelectStatus is equal to active(1)." 1083 ::= { svcSelectEntry 2 } 1085 svcSelectAddr OBJECT-TYPE 1086 SYNTAX AtmAddr 1087 MAX-ACCESS read-create 1088 STATUS current 1089 DESCRIPTION 1090 "This object describes the SVCs, selected by ATM 1091 address(es), identified by this svcSelectEntry. Note that 1092 only non-zero length variants of the AtmAddr are permitted 1093 in this table. 1095 If the associated svcSelectInclude instance is true(1), all 1096 cells transmitted on behalf of calling or called parties 1097 identified by the SVC-match-algorithm are included in the 1098 indicated vcSelectGroup. 1100 Draft ATM-RMON MIB February 1996 1102 If the associated svcSelectInclude instance is false(2), all 1103 cells transmitted on behalf of calling or called parties 1104 identified by the SVC-match-algorithm are excluded from the 1105 indicated vcSelectGroup. 1107 The associated instance of svcSelectAddrMask must be the 1108 same type and length as this object. Address types are 1109 determined by the length of this object, as defined in 1110 [ATM2-MIB]. 1112 SVC-match-algorithm: 1114 boolean SVC-match-algorithm() 1115 { 1116 for (each corresponding bit in the calling-party or 1117 called-party atmAddr, svcSelectAddr, and 1118 svcSelectAddrMask objects) 1119 { 1120 if (svcSelectAddrMask-bit) 1121 if (svcSelectAddr-bit ^ atmAddr-bit) 1122 return(FALSE); 1123 } 1124 return(TRUE); 1125 } 1127 Address-to-cell association is done in an implementation- 1128 specific manner, requiring examination of signaling 1129 information related to the SVCs described by this 1130 svcSelectEntry. 1132 This object may not be modified if the associated instance 1133 of svcSelectStatus is equal to active(1)." 1134 ::= { svcSelectEntry 3 } 1136 svcSelectAddrMask OBJECT-TYPE 1137 SYNTAX AtmAddr 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION 1141 "This object controls the SVC-match-algorithm performed on 1142 cells identified by this svcSelectEntry. This object must be 1143 the same exact type and length as the associated 1144 svcSelectAddr object. 1146 While executing the SVC-match-algorithm, each bit in the 1148 Draft ATM-RMON MIB February 1996 1150 svcSelectAddrMask is examined. If the value is one, then the 1151 corresponding svcSelectAddr bit must match the calling or 1152 called party address bit. If the value is zero, then no test 1153 is done for this bit position. Refer to the svcSelectAddr 1154 object description for more details on the SVC-match- 1155 algorithm. 1157 This object may not be modified if the associated instance 1158 of svcSelectStatus is equal to active(1)." 1159 ::= { svcSelectEntry 4 } 1161 svcSelectInclude OBJECT-TYPE 1162 SYNTAX TruthValue 1163 MAX-ACCESS read-create 1164 STATUS current 1165 DESCRIPTION 1166 "This object controls whether SVCs for the indicated 1167 addresses are included or excluded in the associated 1168 vcSelectGroup. 1170 If this object has the value true(1), then circuits 1171 indicated by this entry are included in the 1172 vcSelectionGroup. 1174 If this object has the value false(2), then circuits 1175 indicated by this entry are excluded from the 1176 vcSelectionGroup. 1178 This object may not be modified if the associated instance 1179 of svcSelectStatus is equal to active(1)." 1180 ::= { svcSelectEntry 5 } 1182 svcSelectLastCreateTime OBJECT-TYPE 1183 SYNTAX LastCreateTime 1184 MAX-ACCESS read-only 1185 STATUS current 1186 DESCRIPTION 1187 "The value of sysUpTime when this svcSelect entry was 1188 activated. This can be used by the management station to 1189 ensure that the table has not been deleted and recreated 1190 between polls." 1191 ::= { svcSelectEntry 6 } 1193 svcSelectOwner OBJECT-TYPE 1194 SYNTAX OwnerString 1196 Draft ATM-RMON MIB February 1996 1198 MAX-ACCESS read-create 1199 STATUS current 1200 DESCRIPTION 1201 "The entity that configured this entry and is therefore 1202 using the resources assigned to it." 1203 ::= { svcSelectEntry 7 } 1205 svcSelectStatus OBJECT-TYPE 1206 SYNTAX RowStatus 1207 MAX-ACCESS read-create 1208 STATUS current 1209 DESCRIPTION 1210 "The status of this row. 1212 An entry may not exist in the active state unless all 1213 objects in the entry have an appropriate value. 1215 This object may not be modified if the associated instance 1216 of vcSelectGroupStatus is equal to active(1). 1218 If this object is not equal to active(1), all associated 1219 data collections shall be deleted. That is, any associated 1220 collections in the atmHostTable or atmMatrixTable." 1221 ::= { svcSelectEntry 8 } 1223 Draft ATM-RMON MIB February 1996 1225 -- 1226 -- ATM Stats Group 1227 -- 1228 -- Counts the total amount of traffic sent on behalf all ATM addresses 1229 -- discovered by the probe, according to associated vcSelectGroup 1230 -- criteria 1232 atmStatsControlTable OBJECT-TYPE 1233 SYNTAX SEQUENCE OF AtmStatsControlEntry 1234 MAX-ACCESS not-accessible 1235 STATUS current 1236 DESCRIPTION 1237 "A list of ATM basic statistic collection table control 1238 entries. These entries will enable the collection of 1239 statistical totals for an entire vcSelectGroup." 1240 ::= { atmStats 1 } 1242 atmStatsControlEntry OBJECT-TYPE 1243 SYNTAX AtmStatsControlEntry 1244 MAX-ACCESS not-accessible 1245 STATUS current 1246 DESCRIPTION 1247 "A conceptual row in the atmStatsControlTable. Entries in 1248 this table are identified and indexed by the 1249 vcSelectGroupIndex object. At most one atmStats collection 1250 is done per vcSelectGroup. 1252 An example of the indexing of this entry is 1253 atmStatsDroppedCells.1" 1254 INDEX { vcSelectGroupIndex } 1255 ::= { atmStatsControlTable 1 } 1257 AtmStatsControlEntry ::= SEQUENCE { 1258 atmStatsControlDroppedCells Counter32, 1259 atmStatsControlHCDroppedCells Counter64, 1260 atmStatsControlOwner OwnerString, 1261 atmStatsControlStatus RowStatus 1262 } 1264 atmStatsControlDroppedCells OBJECT-TYPE 1265 SYNTAX Counter32 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "The total number of cells which were received by the probe 1271 Draft ATM-RMON MIB February 1996 1273 but for which the probe chose not to count in this 1274 collection for whatever reason. Most often, this event 1275 occurs when the probe is out of some resources and decides 1276 to shed load from one or more collections. 1278 This count does not include cells that were not counted 1279 because they had errors." 1280 ::= { atmStatsControlEntry 1 } 1282 atmStatsControlHCDroppedCells OBJECT-TYPE 1283 SYNTAX Counter64 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "The total number of cells which were received by the probe 1288 but for which the probe chose not to count in this 1289 collection for whatever reason. Most often, this event 1290 occurs when the probe is out of some resources and decides 1291 to shed load from one or more collections. 1293 This count does not include cells that were not counted 1294 because they had errors." 1295 ::= { atmStatsControlEntry 2 } 1297 atmStatsControlOwner OBJECT-TYPE 1298 SYNTAX OwnerString 1299 MAX-ACCESS read-create 1300 STATUS current 1301 DESCRIPTION 1302 "The entity that configured this entry and is therefore 1303 using the resources assigned to it." 1304 ::= { atmStatsControlEntry 3 } 1306 atmStatsControlStatus OBJECT-TYPE 1307 SYNTAX RowStatus 1308 MAX-ACCESS read-create 1309 STATUS current 1310 DESCRIPTION 1311 "The status of this atmStatsControlEntry. 1313 An entry may not exist in the active state unless all 1314 objects in the entry have an appropriate value. 1315 Specifically, the associated instance of vcSelectGroupStatus 1316 must be equal to active(1) before this object may be set to 1317 active(1). 1319 Draft ATM-RMON MIB February 1996 1321 If this object is not equal to active(1), all associated 1322 entries in the atmStatsTable shall be deleted." 1323 ::= { atmStatsControlEntry 4 } 1325 Draft ATM-RMON MIB February 1996 1327 -- atmStatsTable 1328 -- call and traffic basic statistics collected on behalf of specific 1329 -- vcSelectGroups 1331 atmStatsTable OBJECT-TYPE 1332 SYNTAX SEQUENCE OF atmStatsEntry 1333 MAX-ACCESS not-accessible 1334 STATUS current 1335 DESCRIPTION 1336 "A collection of statistical totals for all ATM host 1337 addresses that have been discovered on behalf of the 1338 vcSelectGroup associated with this entry." 1339 ::= { atmStats 2 } 1341 atmStatsEntry OBJECT-TYPE 1342 SYNTAX AtmStatsEntry 1343 MAX-ACCESS not-accessible 1344 STATUS current 1345 DESCRIPTION 1346 "A conceptual row in the atmStatsTable. 1348 The vcSelectGroupIndex value in the index identifies the 1349 vcSelectGroup on whose behalf this entry was created. 1351 An example of the indexing of this entry is 1352 atmStatsP2pCells.8.28775.3" 1353 INDEX { vcSelectGroupIndex, atmStatsTimeMark, atmStatsQoS } 1354 ::= { atmStatsTable 1 } 1356 AtmStatsEntry ::= SEQUENCE { 1357 atmStatsTimeMark TimeFilter, 1358 atmStatsQoS QoSIndex, 1359 atmStatsCreateTime LastCreateTime, 1360 atmStatsP2pCells Counter32, 1361 atmStatsP2mpCells Counter32, 1362 atmStatsHCP2pCells Counter64, 1363 atmStatsHCP2mpCells Counter64, 1364 atmStatsNumP2pCalls Counter32, 1365 atmStatsNumP2mpCalls Counter32, 1366 atmStatsP2pConnectionTime TimeStamp, 1367 atmStatsP2mpConnectionTime TimeStamp 1368 } 1370 atmStatsTimeMark OBJECT-TYPE 1371 SYNTAX TimeFilter 1373 Draft ATM-RMON MIB February 1996 1375 MAX-ACCESS not-accessible 1376 STATUS current 1377 DESCRIPTION 1378 "A TimeFilter for this entry. See the TimeFilter textual 1379 convention in [RMON2-MIB] to see how this works." 1380 ::= { atmStatsEntry 1 } 1382 atmStatsQoS OBJECT-TYPE 1383 SYNTAX QoSIndex 1384 MAX-ACCESS not-accessible 1385 STATUS current 1386 DESCRIPTION 1387 "The quality of service classification for this entry. See 1388 the QoSFilter textual convention for details and specific 1389 QoS values." 1390 ::= { atmStatsEntry 2 } 1392 atmStatsCreateTime OBJECT-TYPE 1393 SYNTAX LastCreateTime 1394 MAX-ACCESS read-only 1395 STATUS current 1396 DESCRIPTION 1397 "The value of sysUpTime when this entry was activated. This 1398 can be used by the management station to ensure that the 1399 entry has not been deleted and recreated between polls." 1400 ::= { atmStatsEntry 3 } 1402 atmStatsP2pCells OBJECT-TYPE 1403 SYNTAX Counter32 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "The total number of error-free cells detected on point-to- 1408 point circuits on behalf of this vcSelectGroup collection." 1409 ::= { atmStatsEntry 4 } 1411 atmStatsP2mpCells OBJECT-TYPE 1412 SYNTAX Counter32 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "The total number of error-free cells detected on point-to- 1417 multipoint circuits on behalf of this vcSelectGroup 1418 collection." 1419 ::= { atmStatsEntry 5 } 1421 Draft ATM-RMON MIB February 1996 1423 atmStatsHCP2pCells OBJECT-TYPE 1424 SYNTAX Counter64 1425 MAX-ACCESS read-only 1426 STATUS current 1427 DESCRIPTION 1428 "The total number of error-free cells detected on point-to- 1429 point circuits on behalf of this vcSelectGroup collection." 1430 ::= { atmStatsEntry 6 } 1432 atmStatsHCP2mpCells OBJECT-TYPE 1433 SYNTAX Counter64 1434 MAX-ACCESS read-only 1435 STATUS current 1436 DESCRIPTION 1437 "The total number of error-free cells detected on point-to- 1438 multipoint circuits on behalf of this vcSelectGroup 1439 collection." 1440 ::= { atmStatsEntry 7 } 1442 atmStatsNumP2pCalls OBJECT-TYPE 1443 SYNTAX Counter32 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "The total number of calls detected on point-to-point 1448 circuits on behalf of this vcSelectGroup collection." 1449 ::= { atmStatsEntry 8 } 1451 atmStatsNumP2mpCalls OBJECT-TYPE 1452 SYNTAX Counter32 1453 MAX-ACCESS read-only 1454 STATUS current 1455 DESCRIPTION 1456 "The number of calls detected on point-to-multipoint 1457 circuits on behalf of this vcSelectGroup collection." 1458 ::= { atmStatsEntry 9 } 1460 atmStatsP2pConnectionTime OBJECT-TYPE 1461 SYNTAX TimeStamp 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "The elapsed time of all calls identified by the associated 1466 instance of atmStatsNumP2pCalls." -- will this roll too fast 1467 to be useful? -- to rollover in < 1 hour, approx. 12000 1469 Draft ATM-RMON MIB February 1996 1471 sustained, concurrent -- have to be active. 1472 ::= { atmStatsEntry 10 } 1474 atmStatsP2mpConnectionTime OBJECT-TYPE 1475 SYNTAX TimeStamp 1476 MAX-ACCESS read-only 1477 STATUS current 1478 DESCRIPTION 1479 "The elapsed time of all calls identified by the associated 1480 instance of atmStatsNumP2mpCalls." -- will this roll too 1481 fast to be useful? -- to rollover in < 1 hour, approx. 1482 12000 sustained, concurrent -- have to be active. 1483 ::= { atmStatsEntry 11 } 1485 Draft ATM-RMON MIB February 1996 1487 -- 1488 -- ATM Host Group 1489 -- 1490 -- Counts the amount of traffic sent on behalf of each ATM address 1491 -- discovered by the probe, according to associated vcSelectGroup 1492 -- criteria 1494 atmHostControlTable OBJECT-TYPE 1495 SYNTAX SEQUENCE OF AtmHostControlEntry 1496 MAX-ACCESS not-accessible 1497 STATUS current 1498 DESCRIPTION 1499 "A list of ATM host table control entries. 1501 These entries will enable the collection of ATM host 1502 information in the atmHostTable. 1504 Entries in the atmHostTable will be created on behalf of 1505 each entry in this table. A probe is required to support at 1506 most one atmHost collection per instance of an associated 1507 vcSelectGroup, therefore the table is indexed by the 1508 vcSelectGroupIndex. 1510 Default monitor-owned atmHostControl entries: 1511 [TBD] " 1512 ::= { atmHost 1 } 1514 atmHostControlEntry OBJECT-TYPE 1515 SYNTAX AtmHostControlEntry 1516 MAX-ACCESS not-accessible 1517 STATUS current 1518 DESCRIPTION 1519 "A conceptual row in the atmHostControlTable. Entries in 1520 this table are identified and indexed by the 1521 vcSelectGroupIndex object. At most one atmHost collection 1522 is done per vcSelectGroup. 1524 An example of the indexing of this entry is 1525 atmHostControlInserts.1" 1526 INDEX { vcSelectGroupIndex } 1527 ::= { atmHostControlTable 1 } 1529 AtmHostControlEntry ::= SEQUENCE { 1530 atmHostControlInserts Counter32, 1531 atmHostControlDeletes Counter32, 1533 Draft ATM-RMON MIB February 1996 1535 atmHostControlMaxDesiredEntries Integer32, 1536 atmHostControlPriority ResourcePriority, 1537 atmHostControlDroppedCells Counter32, 1538 atmHostControlHCDroppedCells Counter64, 1539 atmHostControlOwner OwnerString, 1540 atmHostControlStatus RowStatus 1541 } 1543 atmHostControlInserts OBJECT-TYPE 1544 SYNTAX Counter32 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "The number of times an atmHost entry has been inserted into 1549 the atmHost table. If an entry is inserted, then deleted, 1550 and then inserted, this counter will be incremented by 2. 1552 To allow for efficient implementation strategies, agents may 1553 delay updating this object for short periods of time. For 1554 example, an implementation strategy may allow internal data 1555 structures to differ from those visible via SNMP for short 1556 periods of time. This counter may reflect the internal data 1557 structures for those short periods of time. 1559 Note that the table size can be determined by subtracting 1560 atmHostControlDeletes from atmHostControlInserts." 1561 ::= { atmHostControlEntry 1 } 1563 atmHostControlDeletes OBJECT-TYPE 1564 SYNTAX Counter32 1565 MAX-ACCESS read-only 1566 STATUS current 1567 DESCRIPTION 1568 "The number of times an atmHost entry has been deleted from 1569 the atmHost table (for any reason). If an entry is deleted, 1570 then inserted, and then deleted, this counter will be 1571 incremented by 2. 1573 To allow for efficient implementation strategies, agents may 1574 delay updating this object for short periods of time. For 1575 example, an implementation strategy may allow internal data 1576 structures to differ from those visible via SNMP for short 1577 periods of time. This counter may reflect the internal data 1578 structures for those short periods of time. 1580 Draft ATM-RMON MIB February 1996 1582 Note that the table size can be determined by subtracting 1583 atmHostControlDeletes from atmHostControlInserts." 1584 ::= { atmHostControlEntry 2 } 1586 atmHostControlMaxDesiredEntries OBJECT-TYPE 1587 SYNTAX Integer32 1588 MAX-ACCESS read-create 1589 STATUS current 1590 DESCRIPTION 1591 "The maximum number of entries that are desired in the 1592 atmHostTable on behalf of this control entry. The probe will 1593 not create more than this number of associated entries in 1594 the table, but may choose to create fewer entries in this 1595 table for any reason including the lack of resources. 1597 If this object is set to a value less than the current 1598 number of entries, enough entries are chosen in an 1599 implementation-dependent manner and deleted so that the 1600 number of entries in the table equals the value of this 1601 object. 1603 If this value is set to -1, the probe may create any number 1604 of entries in this table. If the associated 1605 atmHostControlStatus object is equal to active(1), this 1606 object may not be modified. 1608 This object may be used to control how resources are 1609 allocated on the probe for the various RMON functions." 1610 ::= { atmHostControlEntry 3 } 1612 atmHostControlPriority OBJECT-TYPE 1613 SYNTAX ResourcePriority 1614 MAX-ACCESS read-create 1615 STATUS current 1616 DESCRIPTION 1617 "The priority this collection should be given to retain 1618 resources, in the event the probe must reclaim some 1619 resources in order to add new entries to an existing atmHost 1620 collection or add new collections of other types." 1621 DEFVAL { normalPriority(2) } 1622 ::= { atmHostControlEntry 4 } 1624 atmHostControlDroppedCells OBJECT-TYPE 1625 SYNTAX Counter32 1626 MAX-ACCESS read-only 1628 Draft ATM-RMON MIB February 1996 1630 STATUS current 1631 DESCRIPTION 1632 "The total number of cells which were received by the probe 1633 but for which the probe chose not to count in this 1634 collection for whatever reason. Most often, this event 1635 occurs when the probe is out of some resources and decides 1636 to shed load from one or more collections. 1638 This count does not include cells that were not counted 1639 because they had errors." 1640 ::= { atmHostControlEntry 5 } 1642 atmHostControlHCDroppedCells OBJECT-TYPE 1643 SYNTAX Counter64 1644 MAX-ACCESS read-only 1645 STATUS current 1646 DESCRIPTION 1647 "The total number of cells which were received by the probe 1648 but for which the probe chose not to count in this 1649 collection for whatever reason. Most often, this event 1650 occurs when the probe is out of some resources and decides 1651 to shed load from one or more collections. 1653 This count does not include cells that were not counted 1654 because they had errors." 1655 ::= { atmHostControlEntry 6 } 1657 atmHostControlOwner OBJECT-TYPE 1658 SYNTAX OwnerString 1659 MAX-ACCESS read-create 1660 STATUS current 1661 DESCRIPTION 1662 "The entity that configured this entry and is therefore 1663 using the resources assigned to it." 1664 ::= { atmHostControlEntry 7 } 1666 atmHostControlStatus OBJECT-TYPE 1667 SYNTAX RowStatus 1668 MAX-ACCESS read-create 1669 STATUS current 1670 DESCRIPTION 1671 "The status of this atmHostControlEntry. 1673 An entry may not exist in the active state unless all 1674 objects in the entry have an appropriate value. 1676 Draft ATM-RMON MIB February 1996 1678 Specifically, the associated instances of 1679 atmHostControlMaxDesiredEntries, atmHostControlPriority, and 1680 vcSelectGroupStatus must be equal to active(1) before this 1681 object may be set to active(1). 1683 If this object is not equal to active(1), all associated 1684 entries in the atmHostTable shall be deleted." 1685 ::= { atmHostControlEntry 8 } 1687 Draft ATM-RMON MIB February 1996 1689 -- atmHostTable 1690 -- call and traffic data collected on behalf of specific 1691 -- vcSelectGroups 1693 atmHostTable OBJECT-TYPE 1694 SYNTAX SEQUENCE OF AtmHostEntry 1695 MAX-ACCESS not-accessible 1696 STATUS current 1697 DESCRIPTION 1698 "A collection of statistics for a particular ATM host 1699 address that has been discovered on behalf of the 1700 vcSelectGroup associated with this entry. Note that only 1701 non-zero length variants of the AtmAddr object are collected 1702 in this table. 1704 The probe will add to this table all addresses seen as the 1705 source or destination address in all cells identified by the 1706 associated vcSelectGroupEntry criteria." 1707 ::= { atmHost 2 } 1709 atmHostEntry OBJECT-TYPE 1710 SYNTAX AtmHostEntry 1711 MAX-ACCESS not-accessible 1712 STATUS current 1713 DESCRIPTION 1714 "A conceptual row in the atmHostTable. 1716 The vcSelectGroupIndex value in the index identifies the 1717 vcSelectGroup on whose behalf this entry was created. 1719 An example of the indexing of this entry is 1720 atmHostInP2pCells.4.28375.20..3" 1721 INDEX { vcSelectGroupIndex, atmHostTimeMark, 1722 atmHostAddress, atmHostQoS } 1723 ::= { atmHostTable 1 } 1725 AtmHostEntry ::= SEQUENCE { 1726 atmHostTimeMark TimeFilter, 1727 atmHostAddress AtmAddr, 1728 atmHostQos QoSIndex, 1729 atmHostCreateTime LastCreateTime, 1730 atmHostInP2pCells ZeroBasedCounter32, 1731 atmHostOutP2pCells ZeroBasedCounter32, 1732 atmHostInP2mpCells ZeroBasedCounter32, 1733 atmHostOutPm2pCells ZeroBasedCounter32, 1735 Draft ATM-RMON MIB February 1996 1737 atmHostInHCP2pCells ZeroBasedCounter64, 1738 atmHostOutHCP2pCells ZeroBasedCounter64, 1739 atmHostInHCP2mpCells ZeroBasedCounter64, 1740 atmHostOutHCPm2pCells ZeroBasedCounter64, 1741 atmHostInNumP2pCalls ZeroBasedCounter32, 1742 atmHostOutNumP2pCalls ZeroBasedCounter32, 1743 atmHostInNumP2mpCalls ZeroBasedCounter32, 1744 atmHostOutNumP2mpCalls ZeroBasedCounter32, 1745 atmHostP2pConnectionTime TimeStamp, 1746 atmHostP2mpConnectionTime TimeStamp 1747 } 1749 atmHostTimeMark OBJECT-TYPE 1750 SYNTAX TimeFilter 1751 MAX-ACCESS not-accessible 1752 STATUS current 1753 DESCRIPTION 1754 "A TimeFilter for this entry. See the TimeFilter textual 1755 convention in [RMON2-MIB] to see how this works." 1756 ::= { atmHostEntry 1 } 1758 atmHostAddress OBJECT-TYPE 1759 SYNTAX AtmAddr 1760 MAX-ACCESS not-accessible 1761 STATUS current 1762 DESCRIPTION 1763 "The ATM address for this atmHostEntry. 1765 This is represented as an octet string with specific 1766 semantics and length as identified by the AtmAddr textual 1767 convention." 1768 ::= { atmHostEntry 2 } 1770 atmHostQoS OBJECT-TYPE 1771 SYNTAX QoSIndex 1772 MAX-ACCESS not-accessible 1773 STATUS current 1774 DESCRIPTION 1775 "The quality of service classification for this entry. See 1776 the QoSFilter textual convention for details and specific 1777 QoS values." 1778 ::= { atmHostEntry 3 } 1780 atmHostCreateTime OBJECT-TYPE 1781 SYNTAX LastCreateTime 1783 Draft ATM-RMON MIB February 1996 1785 MAX-ACCESS read-only 1786 STATUS current 1787 DESCRIPTION 1788 "The value of sysUpTime when this entry was activated. This 1789 can be used by the management station to ensure that the 1790 entry has not been deleted and recreated between polls." 1791 ::= { atmHostEntry 4 } 1793 atmHostInP2pCells OBJECT-TYPE 1794 SYNTAX ZeroBasedCounter32 1795 MAX-ACCESS read-only 1796 STATUS current 1797 DESCRIPTION 1798 "The number of error-free cells detected on point-to-point 1799 circuits in which this ATM address was identified as the 1800 called party." 1801 ::= { atmHostEntry 5 } 1803 atmHostOutP2pCells OBJECT-TYPE 1804 SYNTAX ZeroBasedCounter32 1805 MAX-ACCESS read-only 1806 STATUS current 1807 DESCRIPTION 1808 "The number of error-free cells detected on point-to-point 1809 circuits in which this ATM address was identified as the 1810 calling party." 1811 ::= { atmHostEntry 6 } 1813 atmHostInP2mpCells OBJECT-TYPE 1814 SYNTAX ZeroBasedCounter32 1815 MAX-ACCESS read-only 1816 STATUS current 1817 DESCRIPTION 1818 "The number of error-free cells detected on point-to- 1819 multipoint circuits in which this ATM address was identified 1820 as the called party." 1821 ::= { atmHostEntry 7 } 1823 atmHostOutP2mpCells OBJECT-TYPE 1824 SYNTAX ZeroBasedCounter32 1825 MAX-ACCESS read-only 1826 STATUS current 1827 DESCRIPTION 1828 "The number of error-free cells detected on point-to- 1829 multipoint circuits in which this ATM address was identified 1831 Draft ATM-RMON MIB February 1996 1833 as the calling party." 1834 ::= { atmHostEntry 8 } 1836 atmHostInHCP2pCells OBJECT-TYPE 1837 SYNTAX ZeroBasedCounter64 1838 MAX-ACCESS read-only 1839 STATUS current 1840 DESCRIPTION 1841 "The number of error-free cells detected on point-to-point 1842 circuits in which this ATM address was identified as the 1843 called party." 1844 ::= { atmHostEntry 9 } 1846 atmHostOutHCP2pCells OBJECT-TYPE 1847 SYNTAX ZeroBasedCounter64 1848 MAX-ACCESS read-only 1849 STATUS current 1850 DESCRIPTION 1851 "The number of error-free cells detected on point-to-point 1852 circuits in which this ATM address Was identified as the 1853 calling party." 1854 ::= { atmHostEntry 10 } 1856 atmHostInHCP2mpCells OBJECT-TYPE 1857 SYNTAX ZeroBasedCounter64 1858 MAX-ACCESS read-only 1859 STATUS current 1860 DESCRIPTION 1861 "The number of error-free cells detected on point-to- 1862 multipoint circuits in which this ATM address was identified 1863 as the called party." 1864 ::= { atmHostEntry 11 } 1866 atmHostOutHCP2mpCells OBJECT-TYPE 1867 SYNTAX ZeroBasedCounter64 1868 MAX-ACCESS read-only 1869 STATUS current 1870 DESCRIPTION 1871 "The number of error-free cells detected on point-to- 1872 multipoint circuits in which this ATM address was identified 1873 as the calling party." 1874 ::= { atmHostEntry 12 } 1876 atmHostInNumP2pCalls OBJECT-TYPE 1877 SYNTAX ZeroBasedCounter32 1879 Draft ATM-RMON MIB February 1996 1881 MAX-ACCESS read-only 1882 STATUS current 1883 DESCRIPTION 1884 "The number of calls detected on point-to-point circuits in 1885 which this ATM address was identified as the called party." 1886 ::= { atmHostEntry 13 } 1888 atmHostOutNumP2pCalls OBJECT-TYPE 1889 SYNTAX ZeroBasedCounter32 1890 MAX-ACCESS read-only 1891 STATUS current 1892 DESCRIPTION 1893 "The number of calls detected on point-to-point circuits in 1894 which this ATM address was identified as the calling party." 1895 ::= { atmHostEntry 14 } 1897 atmHostInNumP2mpCalls OBJECT-TYPE 1898 SYNTAX ZeroBasedCounter32 1899 MAX-ACCESS read-only 1900 STATUS current 1901 DESCRIPTION 1902 "The number of calls detected on point-to-multipoint 1903 circuits in which this ATM address was identified as the 1904 called party." 1905 ::= { atmHostEntry 15 } 1907 atmHostOutNumP2mpCalls OBJECT-TYPE 1908 SYNTAX ZeroBasedCounter32 1909 MAX-ACCESS read-only 1910 STATUS current 1911 DESCRIPTION 1912 "The number of calls detected on point-to-multipoint 1913 circuits in which this ATM address was identified as the 1914 calling party." 1915 ::= { atmHostEntry 16 } 1917 atmHostP2pConnectionTime OBJECT-TYPE 1918 SYNTAX TimeStamp 1919 MAX-ACCESS read-only 1920 STATUS current 1921 DESCRIPTION 1922 "The elapsed time of all calls identified by the associated 1923 instances of atmHostInNumP2pCalls and 1924 atmHostOutNumP2pCalls." 1925 ::= { atmHostEntry 17 } 1927 Draft ATM-RMON MIB February 1996 1929 atmHostP2mpConnectionTime OBJECT-TYPE 1930 SYNTAX TimeStamp 1931 MAX-ACCESS read-only 1932 STATUS current 1933 DESCRIPTION 1934 "The elapsed time of all calls identified by the associated 1935 instances of atmHostInNumP2mpCalls and 1936 atmHostOutNumP2mpCalls." 1937 ::= { atmHostEntry 18 } 1939 Draft ATM-RMON MIB February 1996 1941 -- 1942 -- ATM HostTopN Group 1943 -- 1944 -- Finds and reports the top traffic contributors, 1945 -- according to associated vcSelectGroup criteria 1947 atmHostTopNControlTable OBJECT-TYPE 1948 SYNTAX SEQUENCE OF AtmHostTopNControlEntry 1949 MAX-ACCESS not-accessible 1950 STATUS current 1951 DESCRIPTION 1952 "A set of parameters that control the creation of a report 1953 of the top N host entries according to a selected metric." 1954 ::= { atmHost 3 } 1956 atmHostTopNControlEntry OBJECT-TYPE 1957 SYNTAX AtmHostTopNControlEntry 1958 MAX-ACCESS not-accessible 1959 STATUS current 1960 DESCRIPTION 1961 "A conceptual row in the atmHostTopNControlTable. 1963 An example of the indexing of this table is 1964 atmHostTopNControlDuration.3.1" 1965 INDEX { vcSelectGroupIndex, atmHostTopNControlIndex } 1966 ::= { atmHostTopNControlTable 1 } 1968 AtmHostTopNControlEntry ::= SEQUENCE { 1969 atmHostTopNControlIndex Integer32, 1970 atmHostTopNControlRateBase INTEGER, 1971 atmHostTopNControlTimeRemaining Integer32, 1972 atmHostTopNControlGeneratedReports Counter32, 1973 atmHostTopNControlDuration Integer32, 1974 atmHostTopNControlRequestedSize Integer32, 1975 atmHostTopNControlGrantedSize Integer32, 1976 atmHostTopNControlStartTime TimeStamp, 1977 atmHostTopNControlOwner OwnerString, 1978 atmHostTopNControlStatus RowStatus 1979 } 1981 atmHostTopNControlIndex OBJECT-TYPE 1982 SYNTAX Integer32 (1..65535) 1983 MAX-ACCESS not-accessible 1984 STATUS current 1985 DESCRIPTION 1987 Draft ATM-RMON MIB February 1996 1989 "An index that is used to uniquely identify an entry in the 1990 atmHostTopNControlTable. Each such entry defines one top N 1991 report prepared on behalf of one atmHost entry and one 1992 vcSelectGroup entry." 1993 ::= { atmHostTopNControlEntry 1 } 1995 atmHostTopNControlRateBase OBJECT-TYPE 1996 SYNTAX INTEGER { 1997 atmHostTopNInP2pCells(1), 1998 atmHostTopNOutP2pCells(2), 1999 atmHostTopNInP2mpCells(3), 2000 atmHostTopNOutP2mpCells(4), 2001 atmHostTopNInNumP2pCalls(5), 2002 atmHostTopNOutNumP2pCalls(6), 2003 atmHostTopNInNumP2mpCalls(7), 2004 atmHostTopNOutNumP2mpCalls(8), 2005 atmHostTopNP2pConnectionTime(9), 2006 atmHostTopNP2mpConnectionTime(10) 2007 } 2008 MAX-ACCESS read-create 2009 STATUS current 2010 DESCRIPTION 2011 "The variable for each atmHost entry that the 2012 atmHostTopNEntries are sorted by. 2014 This object may not be modified if the associated 2015 atmHostTopNControl STATUS object is equal to active(1)." 2016 ::= { atmHostTopNControlEntry 2 } 2018 atmHostTopNControlTimeRemaining OBJECT-TYPE 2019 SYNTAX Integer32 2020 MAX-ACCESS read-create 2021 STATUS current 2022 DESCRIPTION 2023 "The number of seconds left in the report currently being 2024 collected. When this object is modified by the management 2025 station, a new collection is started, possibly aborting a 2026 currently running report. The new value is used as the 2027 requested duration of this report, and is immediately loaded 2028 into the associated atmHostTopNControlDuration object. When 2029 the report finishes, the probe will automatically start 2030 another collection with the same initial value of 2031 atmHostTopNControlTimeRemaining. Thus the management 2032 station may simply read the resulting reports repeatedly, 2033 checking the startTime and duration each time to ensure that 2035 Draft ATM-RMON MIB February 1996 2037 a report was not missed or that the report parameters were 2038 not changed. 2040 While the value of this object is non-zero, it decrements by 2041 one per second until it reaches zero. At the time that this 2042 object decrements to zero, the report is made accessible in 2043 the atmHostTopNTable, overwriting any report that may be 2044 there. 2046 When this object is modified by the management station, any 2047 associated entries in the atmHostTopNTable shall be 2048 deleted." 2049 DEFVAL { 1800 } 2050 ::= { atmHostTopNControlEntry 3 } 2052 atmHostTopNControlGeneratedReports OBJECT-TYPE 2053 SYNTAX Counter32 2054 MAX-ACCESS read-only 2055 STATUS current 2056 DESCRIPTION 2057 "The number of reports that have been generated by this 2058 entry." 2059 ::= { atmHostTopNControlEntry 4 } 2061 atmHostTopNControlDuration OBJECT-TYPE 2062 SYNTAX Integer32 2063 MAX-ACCESS read-only 2064 STATUS current 2065 DESCRIPTION 2066 "The number of seconds that this report has collected during 2067 the last sampling interval. 2069 When the associated atmHostTopNControlTimeRemaining object 2070 is set, this object shall be set by the probe to the same 2071 value and shall not be modified until the next time the 2072 atmHostTopNControlTimeRemaining is set. 2074 This value shall be zero if no reports have been requested 2075 for this atmHostTopNControlEntry." 2076 ::= { atmHostTopNControlEntry 5 } 2078 atmHostTopNControlRequestedSize OBJECT-TYPE 2079 SYNTAX Integer32 2080 MAX-ACCESS read-create 2081 STATUS current 2083 Draft ATM-RMON MIB February 1996 2085 DESCRIPTION 2086 "The maximum number of host entries requested for this 2087 report. 2089 When this object is created or modified, the probe should 2090 set atmHostTopNControlGrantedSize as closely to this object 2091 as is possible for the particular probe implementation and 2092 available resources." 2093 DEFVAL { 150 } 2094 ::= { atmHostTopNControlEntry 6 } 2096 atmHostTopNControlGrantedSize OBJECT-TYPE 2097 SYNTAX Integer32 2098 MAX-ACCESS read-only 2099 STATUS current 2100 DESCRIPTION 2101 "The maximum number of host entries in this report. 2103 When the associated atmHostTopNControlRequestedSize object 2104 is created or modified, the probe should set this object as 2105 closely to the requested value as is possible for the 2106 particular implementation and available resources. The probe 2107 must not lower this value except as a result of a set to the 2108 associated atmHostTopNControlRequestedSize object. 2110 For example, if the value of atmHostTopNControlRateBase is 2111 equal to atmHostTopNP2pCells(1), when the next topN report 2112 is generated, host entries with the highest value of 2113 atmHostP2pCells shall be placed in this table in decreasing 2114 order of this rate until there is no more room or until 2115 there are no more host entries. Each atmHostP2pCells value 2116 is copied to the associated atmHostTopNRate object. 2118 It is an implementation-specific matter how entries with the 2119 same value are sorted. It is also an implementation- 2120 specific matter as to whether or not zero-valued entries are 2121 available." 2122 ::= { atmHostTopNControlEntry 7 } 2124 atmHostTopNControlStartTime OBJECT-TYPE 2125 SYNTAX TimeStamp 2126 MAX-ACCESS read-only 2127 STATUS current 2128 DESCRIPTION 2129 "The value of sysUpTime when this top N report was last 2131 Draft ATM-RMON MIB February 1996 2133 started. In other words, this is the time that the 2134 associated atmHostTopNControlTimeRemaining object was 2135 modified to start the requested report or the time the 2136 report was last automatically (re)started. 2138 This object may be used by the management station to 2139 determine if a report was missed or not." 2140 ::= { atmHostTopNControlEntry 8 } 2142 atmHostTopNControlOwner OBJECT-TYPE 2143 SYNTAX OwnerString 2144 MAX-ACCESS read-create 2145 STATUS current 2146 DESCRIPTION 2147 "The entity that configured this entry and is therefore 2148 using the resources assigned to it." 2149 ::= { atmHostTopNControlEntry 9 } 2151 atmHostTopNControlStatus OBJECT-TYPE 2152 SYNTAX RowStatus 2153 MAX-ACCESS read-create 2154 STATUS current 2155 DESCRIPTION 2156 "The status of this atmHostTopNControlEntry. 2158 An entry may not exist in the active state unless all 2159 objects in the entry have an appropriate value. 2161 If this object is not equal to active(1), all associated 2162 entries in the atmHostTopNTable shall be deleted by the 2163 agent." 2164 ::= { atmHostTopNControlEntry 10 } 2166 Draft ATM-RMON MIB February 1996 2168 -- 2169 -- atmHostTopNTable 2170 -- 2171 atmHostTopNTable OBJECT-TYPE 2172 SYNTAX SEQUENCE OF AtmHostTopNEntry 2173 MAX-ACCESS not-accessible 2174 STATUS current 2175 DESCRIPTION 2176 "A set of statistics for those network layer matrix entries 2177 that have counted the highest number of octets or packets." 2178 ::= { atmHost 4 } 2180 atmHostTopNEntry OBJECT-TYPE 2181 SYNTAX AtmHostTopNEntry 2182 MAX-ACCESS not-accessible 2183 STATUS current 2184 DESCRIPTION 2185 "A conceptual row in the atmHostTopNTable. 2187 The atmHostTopNControlIndex value in the index identifies 2188 the atmHostTopNControlEntry on whose behalf this entry was 2189 created. 2191 An example of the indexing of this table is 2192 atmHostTopNAddress.1.3.10" 2193 INDEX { vcSelectGroupIndex, atmHostTopNControlIndex, 2194 atmHostTopNIndex } 2195 ::= { atmHostTopNTable 1 } 2197 AtmHostTopNEntry ::= SEQUENCE { 2198 atmHostTopNIndex Integer32, 2199 atmHostTopNAddress AtmAddr, 2200 atmHostTopNRate Integer32 2201 -- what to do about HCRate?? Need the SMI to support Integer64! 2202 } 2204 atmHostTopNIndex OBJECT-TYPE 2205 SYNTAX Integer32 (1..65535) 2206 MAX-ACCESS not-accessible 2207 STATUS current 2208 DESCRIPTION 2209 "An index that uniquely identifies an entry in the 2210 atmHostTopNTable among those in the same report. This index 2211 is between 1 and N, where N is the number of entries in this 2212 report. 2214 Draft ATM-RMON MIB February 1996 2216 Each host in the selected hostTable, for the report 2217 interval, is ranked in descending order of the metric 2218 identified by the atmHostTopNRate object. 2220 For example, if the value of atmHostTopNControlRateBase is 2221 equal to atmHostTopNP2pCells(1), increasing values of 2222 atmHostTopNIndex shall be assigned to entries with 2223 decreasing delta values of atmHostP2pCells (for the report 2224 interval), until index N is assigned or there are no more 2225 atmHostTopNEntries." 2226 ::= { atmHostTopNEntry 1 } 2228 atmHostTopNAddress OBJECT-TYPE 2229 SYNTAX AtmAddr 2230 MAX-ACCESS read-only 2231 STATUS current 2232 DESCRIPTION 2233 "The ATM address of this host. Only non-zero length variants 2234 of AtmAddr textual convention are allowed in this table." 2235 ::= { atmHostTopNEntry 2 } 2237 atmHostTopNRate OBJECT-TYPE 2238 SYNTAX Integer32 2239 MAX-ACCESS read-only 2240 STATUS current 2241 DESCRIPTION 2242 "The value of the ranked metric for this host, for this 2243 report. 2245 If the associated value of atmHostTopNRateBase is equal to 2246 atmHostTopNInP2pCells(1), then this object is assigned the 2247 delta value of the atmHostInP2pCells object during this 2248 report interval. 2250 If the associated value of atmHostTopNRateBase is equal to 2251 atmHostTopNOutP2pCells(2), then this object is assigned the 2252 delta value of the atmHostOutP2pCells object during this 2253 report interval. 2255 If the associated value of atmHostTopNRateBase is equal to 2256 atmHostTopNInP2mpCells(3), then this object is assigned the 2257 delta value of the atmHostInP2mpCells object during this 2258 report interval. 2260 If the associated value of atmHostTopNRateBase is equal to 2262 Draft ATM-RMON MIB February 1996 2264 atmHostTopNOutP2mpCells(4), then this object is assigned the 2265 delta value of the atmHostOutP2mpCells object during this 2266 report interval. 2268 If the associated value of atmHostTopNRateBase is equal to 2269 atmHostTopNInNumP2pCalls(5), then this object is assigned 2270 the delta value of the atmHostInNumP2pCalls object during 2271 this report interval. 2273 If the associated value of atmHostTopNRateBase is equal to 2274 atmHostTopNOutNumP2pCalls(6), then this object is assigned 2275 the delta value of the atmHostOutNumP2pCalls object during 2276 this report interval. 2278 If the associated value of atmHostTopNRateBase is equal to 2279 atmHostTopNInNumP2mpCalls(7), then this object is assigned 2280 the delta value of the atmHostInNumP2mpCalls object during 2281 this report interval. 2283 If the associated value of atmHostTopNRateBase is equal to 2284 atmHostTopNOutNumP2mpCalls(8), then this object is assigned 2285 the delta value of the atmHostOutNumP2mpCalls object during 2286 this report interval. 2288 If the associated value of atmHostTopNRateBase is equal to 2289 atmHostTopNP2pConnectionTime(9), then this object is 2290 assigned the delta value of the atmHostP2pConnectionTime 2291 object during this report interval. 2293 If the associated value of atmHostTopNRateBase is equal to 2294 atmHostTopNP2mpConnectionTime(10), then this object is 2295 assigned the delta value of the atmHostP2mpConnectionTime 2296 object during this report interval." 2297 ::= { atmHostTopNEntry 3 } 2299 Draft ATM-RMON MIB February 1996 2301 -- 2302 -- ATM Matrix Group 2303 -- 2304 -- Counts the amount of traffic sent on behalf of each source 2305 -- and destination ATM address discovered by the probe, 2306 -- according to associated vcSelectGroup criteria 2308 atmMatrixControlTable OBJECT-TYPE 2309 SYNTAX SEQUENCE OF AtmMatrixControlEntry 2310 MAX-ACCESS not-accessible 2311 STATUS current 2312 DESCRIPTION 2313 "A list of ATM matrix table control entries. 2315 These entries will enable the collection of ATM matrix 2316 information in the atmMatrixTable. 2318 Entries in the atmMatrixTable will be created on behalf of 2319 each entry in this table. A probe is required to support at 2320 most one atmMatrix collection per instance of an associated 2321 vcSelectGroup, therefore the table is indexed by the 2322 vcSelectGroupIndex. 2324 Default monitor-owned atmMatrixControl entries: 2325 [TBD]" 2326 ::= { atmMatrix 1 } 2328 atmMatrixControlEntry OBJECT-TYPE 2329 SYNTAX AtmMatrixControlEntry 2330 MAX-ACCESS not-accessible 2331 STATUS current 2332 DESCRIPTION 2333 "A conceptual row in the atmMatrixControlTable. Entries in 2334 this table are identified and indexed by the 2335 vcSelectGroupIndex object. At most one atmMatrix collection 2336 is done per vcSelectGroup. 2338 An example of the indexing of this entry is 2339 atmMatrixControlInserts.1" 2340 INDEX { vcSelectGroupIndex } 2341 ::= { atmMatrixControlTable 1 } 2343 AtmMatrixControlEntry ::= SEQUENCE { 2344 atmMatrixControlInserts Counter32, 2345 atmMatrixControlDeletes Counter32, 2347 Draft ATM-RMON MIB February 1996 2349 atmMatrixControlMaxDesiredEntries Integer32, 2350 atmMatrixControlPriority ResourcePriority, 2351 atmMatrixControlDroppedCells Counter32, 2352 atmMatrixControlHCDroppedCells Counter64, 2353 atmMatrixControlOwner OwnerString, 2354 atmMatrixControlStatus RowStatus 2355 } 2357 atmMatrixControlInserts OBJECT-TYPE 2358 SYNTAX Counter32 2359 MAX-ACCESS read-only 2360 STATUS current 2361 DESCRIPTION 2362 "The number of times an atmMatrix entry has been inserted 2363 into the atmMatrix table. If an entry is inserted, then 2364 deleted, and then inserted, this counter will be incremented 2365 by 2. 2367 To allow for efficient implementation strategies, agents may 2368 delay updating this object for short periods of time. For 2369 example, an implementation strategy may allow internal data 2370 structures to differ from those visible via SNMP for short 2371 periods of time. This counter may reflect the internal data 2372 structures for those short periods of time. 2374 Note that the table size can be determined by subtracting 2375 atmMatrixControlDeletes from atmMatrixControlInserts." 2376 ::= { atmMatrixControlEntry 1 } 2378 atmMatrixControlDeletes OBJECT-TYPE 2379 SYNTAX Counter32 2380 MAX-ACCESS read-only 2381 STATUS current 2382 DESCRIPTION 2383 "The number of times an atmMatrix entry has been deleted 2384 from the atmMatrix table (for any reason). If an entry is 2385 deleted, then inserted, and then deleted, this counter will 2386 be incremented by 2. 2388 To allow for efficient implementation strategies, agents may 2389 delay updating this object for short periods of time. For 2390 example, an implementation strategy may allow internal data 2391 structures to differ from those visible via SNMP for short 2392 periods of time. This counter may reflect the internal data 2393 structures for those short periods of time. 2395 Draft ATM-RMON MIB February 1996 2397 Note that the table size can be determined by subtracting 2398 atmMatrixControlDeletes from atmMatrixControlInserts." 2399 ::= { atmMatrixControlEntry 2 } 2401 atmMatrixControlMaxDesiredEntries OBJECT-TYPE 2402 SYNTAX Integer32 2403 MAX-ACCESS read-create 2404 STATUS current 2405 DESCRIPTION 2406 "The maximum number of entries that are desired in the 2407 atmMatrixTable on behalf of this control entry. The probe 2408 will not create more than this number of associated entries 2409 in the table, but may choose to create fewer entries in this 2410 table for any reason including the lack of resources. 2412 If this object is set to a value less than the current 2413 number of entries, enough entries are chosen in an 2414 implementation-dependent manner and deleted so that the 2415 number of entries in the table equals the value of this 2416 object. 2418 If this value is set to -1, the probe may create any number 2419 of entries in this table. If the associated 2420 atmMatrixControl STATUS object is equal to active(1), this 2421 object may not be modified. 2423 This object may be used to control how resources are 2424 allocated on the probe for the various RMON functions." 2425 ::= { atmMatrixControlEntry 3 } 2427 atmMatrixControlPriority OBJECT-TYPE 2428 SYNTAX ResourcePriority 2429 MAX-ACCESS read-create 2430 STATUS current 2431 DESCRIPTION 2432 "The priority this collection should be given to retain 2433 resources, in the event the probe must reclaim some 2434 resources in order to add new entries to an existing 2435 atmMatrix collection or add new collections of other types." 2436 DEFVAL { normalPriority(2) } 2437 ::= { atmMatrixControlEntry 4 } 2439 atmMatrixControlDroppedCells OBJECT-TYPE 2440 SYNTAX Counter32 2441 MAX-ACCESS read-only 2443 Draft ATM-RMON MIB February 1996 2445 STATUS current 2446 DESCRIPTION 2447 "The total number of cells which were received by the probe 2448 but for which the probe chose not to count in this 2449 collection for whatever reason. Most often, this event 2450 occurs when the probe is out of some resources and decides 2451 to shed load from one or more collections. 2453 This count does not include cells that were not counted 2454 because they had errors." 2455 ::= { atmMatrixControlEntry 5 } 2457 atmMatrixControlHCDroppedCells OBJECT-TYPE 2458 SYNTAX Counter64 2459 MAX-ACCESS read-only 2460 STATUS current 2461 DESCRIPTION 2462 "The total number of cells which were received by the 2463 probe but for which the probe chose not to count in this 2464 collection for whatever reason. Most often, this event 2465 occurs when the probe is out of some resources and decides 2466 to shed load from one or more collections. 2468 This count does not include cells that were not counted 2469 because they had errors." 2470 ::= { atmMatrixControlEntry 6 } 2472 atmMatrixControlOwner OBJECT-TYPE 2473 SYNTAX OwnerString 2474 MAX-ACCESS read-create 2475 STATUS current 2476 DESCRIPTION 2477 "The entity that configured this entry and is therefore 2478 using the resources assigned to it." 2479 ::= { atmMatrixControlEntry 7 } 2481 atmMatrixControlStatus OBJECT-TYPE 2482 SYNTAX RowStatus 2483 MAX-ACCESS read-create 2484 STATUS current 2485 DESCRIPTION 2486 "The status of this atmMatrixControlEntry. 2488 An entry may not exist in the active state unless all 2489 objects in the entry have an appropriate value. 2491 Draft ATM-RMON MIB February 1996 2493 Specifically, the associated instances of 2494 atmMatrixControlMaxDesiredEntries, atmMatrixControlPriority, 2495 and vcSelectGroup STATUS must be equal to active(1) before 2496 this object may be set to active(1). 2498 If this object is not equal to active(1), all associated 2499 entries in the atmMatrixTable shall be deleted." 2500 ::= { atmMatrixControlEntry 8 } 2502 Draft ATM-RMON MIB February 1996 2504 -- atmMatrixTable 2505 -- call and traffic data collected on behalf of specific 2506 -- vcSelectGroups 2508 atmMatrixTable OBJECT-TYPE 2509 SYNTAX SEQUENCE OF AtmMatrixEntry 2510 MAX-ACCESS not-accessible 2511 STATUS current 2512 DESCRIPTION 2513 "A collection of statistics for a particular ATM host 2514 address that has been discovered on behalf of the 2515 vcSelectGroup associated with this entry. Note that only 2516 non-zero length variants of the AtmAddr object are collected 2517 in this table. 2519 The probe will add to this table all addresses seen as the 2520 source or destination address in all cells identified by the 2521 associated vcSelectGroupEntry criteria." 2522 ::= { atmMatrix 2 } 2524 atmMatrixEntry OBJECT-TYPE 2525 SYNTAX AtmMatrixEntry 2526 MAX-ACCESS not-accessible 2527 STATUS current 2528 DESCRIPTION 2529 "A conceptual row in the atmMatrixTable. 2531 The vcSelectGroupIndex value in the index identifies the 2532 vcSelectGroup on whose behalf this entry was created. 2534 An example of the indexing of this entry is 2535 atmMatrixInP2pCells.4.28980.20..20..3" 2536 INDEX { vcSelectGroupIndex, atmMatrixTimeMark, 2537 atmMatrixCallingAddress, atmMatrixCalled, 2538 atmMatrixQoS } 2539 ::= { atmMatrixTable 1 } 2541 AtmMatrixEntry ::= SEQUENCE { 2542 atmMatrixTimeMark TimeFilter, 2543 atmMatrixCallingAddress AtmAddr, 2544 atmMatrixCalledAddress AtmAddr, 2545 atmMatrixQos QoSIndex, 2546 atmMatrixCreateTime LastCreateTime, 2547 atmMatrixP2pCells ZeroBasedCounter32, 2548 atmMatrixP2mpCells ZeroBasedCounter32, 2550 Draft ATM-RMON MIB February 1996 2552 atmMatrixHCP2pCells ZeroBasedCounter64, 2553 atmMatrixHCP2mpCells ZeroBasedCounter64, 2554 atmMatrixNumP2pCalls ZeroBasedCounter32, 2555 atmMatrixNumP2mpCalls ZeroBasedCounter32, 2556 atmMatrixP2pConnectionTime TimeStamp, 2557 atmMatrixP2mpConnectionTime TimeStamp 2558 } 2560 atmMatrixTimeMark OBJECT-TYPE 2561 SYNTAX TimeFilter 2562 MAX-ACCESS not-accessible 2563 STATUS current 2564 DESCRIPTION 2565 "A TimeFilter for this entry. See the TimeFilter textual 2566 convention in [RMON2-MIB] to see how this works." 2567 ::= { atmMatrixEntry 1 } 2569 atmMatrixCallingAddress OBJECT-TYPE 2570 SYNTAX AtmAddr 2571 MAX-ACCESS not-accessible 2572 STATUS current 2573 DESCRIPTION 2574 "The calling party ATM address for this atmMatrixEntry. 2576 This is represented as an octet string with specific 2577 semantics and length as identified by the AtmAddr textual 2578 convention." 2579 ::= { atmMatrixEntry 2 } 2581 atmMatrixCalledAddress OBJECT-TYPE 2582 SYNTAX AtmAddr 2583 MAX-ACCESS not-accessible 2584 STATUS current 2585 DESCRIPTION 2586 "The called party ATM address for this atmMatrixEntry. 2588 This is represented as an octet string with specific 2589 semantics and length as identified by the AtmAddr textual 2590 convention." 2591 ::= { atmMatrixEntry 3 } 2593 atmMatrixQos OBJECT-TYPE 2594 SYNTAX QoSIndex 2595 MAX-ACCESS not-accessible 2596 STATUS current 2598 Draft ATM-RMON MIB February 1996 2600 DESCRIPTION 2601 "The quality of service classification for this entry. See 2602 the QoSFilter textual convention for details and specific 2603 QoS values." 2604 ::= { atmMatrixEntry 4 } 2606 atmMatrixCreateTime OBJECT-TYPE 2607 SYNTAX LastCreateTime 2608 MAX-ACCESS read-only 2609 STATUS current 2610 DESCRIPTION 2611 "The value of sysUpTime when this entry was activated. This 2612 can be used by the management station to ensure that the 2613 entry has not been deleted and recreated between polls." 2614 ::= { atmMatrixEntry 5 } 2616 atmMatrixP2pCells OBJECT-TYPE 2617 SYNTAX ZeroBasedCounter32 2618 MAX-ACCESS read-only 2619 STATUS current 2620 DESCRIPTION 2621 "The number of error-free cells detected on point-to-point 2622 circuits in which these ATM addresses were identified as the 2623 calling and called parties." 2624 ::= { atmMatrixEntry 6 } 2626 atmMatrixP2mpCells OBJECT-TYPE 2627 SYNTAX ZeroBasedCounter32 2628 MAX-ACCESS read-only 2629 STATUS current 2630 DESCRIPTION 2631 "The number of error-free cells detected on point-to- 2632 multipoint circuits in which these ATM addresses were 2633 identified as the calling and called parties." 2634 ::= { atmMatrixEntry 7 } 2636 atmMatrixHCP2pCells OBJECT-TYPE 2637 SYNTAX ZeroBasedCounter64 2638 MAX-ACCESS read-only 2639 STATUS current 2640 DESCRIPTION 2641 "The number of error-free cells detected on point-to-point 2642 circuits in which these ATM addresses were identified as the 2643 calling and called parties." 2644 ::= { atmMatrixEntry 8 } 2646 Draft ATM-RMON MIB February 1996 2648 atmMatrixHCP2mpCells OBJECT-TYPE 2649 SYNTAX ZeroBasedCounter64 2650 MAX-ACCESS read-only 2651 STATUS current 2652 DESCRIPTION 2653 "The number of error-free cells detected on point-to- 2654 multipoint circuits in which these ATM addresses were 2655 identified as the calling and called parties." 2656 ::= { atmMatrixEntry 9 } 2658 atmMatrixNumP2pCalls OBJECT-TYPE 2659 SYNTAX ZeroBasedCounter32 2660 MAX-ACCESS read-only 2661 STATUS current 2662 DESCRIPTION 2663 "The number of calls detected on point-to-point circuits in 2664 which these ATM addresses were identified as the calling and 2665 called parties." 2666 ::= { atmMatrixEntry 10 } 2668 atmMatrixNumP2mpCalls OBJECT-TYPE 2669 SYNTAX ZeroBasedCounter32 2670 MAX-ACCESS read-only 2671 STATUS current 2672 DESCRIPTION 2673 "The number of calls detected on point-to-multipoint 2674 circuits in which these ATM addresses were identified as the 2675 calling and called parties." 2676 ::= { atmMatrixEntry 11 } 2678 atmMatrixP2pConnectionTime OBJECT-TYPE 2679 SYNTAX TimeStamp 2680 MAX-ACCESS read-only 2681 STATUS current 2682 DESCRIPTION 2683 "The elapsed time of all calls identified by the associated 2684 instance of atmMatrixNumP2pCalls." 2685 ::= { atmMatrixEntry 12 } 2687 atmMatrixP2mpConnectionTime OBJECT-TYPE 2688 SYNTAX TimeStamp 2689 MAX-ACCESS read-only 2690 STATUS current 2691 DESCRIPTION 2692 "The elapsed time of all calls identified by the associated 2694 Draft ATM-RMON MIB February 1996 2696 instance of atmMatrixNumP2mpCalls." 2697 ::= { atmMatrixEntry 13 } 2699 -- TBD: atmMatrixTopN group 2701 Draft ATM-RMON MIB February 1996 2703 -- Conformance Macros 2705 atmRmonMIBCompliances OBJECT IDENTIFIER ::= { atmRmonConformance 1 } 2706 atmRmonMIBGroups OBJECT IDENTIFIER ::= { atmRmonConformance 2 } 2708 atmRmonMIBCompliance MODULE-COMPLIANCE 2709 STATUS current 2710 DESCRIPTION 2711 "Describes the requirements for conformance to the ATM-RMON 2712 MIB. 2714 TBD: separate conformance statements with and without 64 bit 2715 counters." 2716 MODULE -- this module 2717 MANDATORY-GROUPS { vcSelectGroup, 2718 atmStatsGroup, 2719 atmHostGroup, 2720 atmMatrixGroup } 2721 ::= { atmRmonMIBCompliances 1 } 2723 vcSelectGroup OBJECT-GROUP 2724 OBJECTS { vcSelectGroupDescr, vcSelectGroupCreateTime, 2725 vcSelectGroupOwner, vcSelectGroupStatus, 2726 pvcSelectIfIndex, pvcSelectVPI, 2727 pvcSelectVCI, pvcSelectInclude, 2728 pvcSelectCreateTime, pvcSelectOwner, 2729 pvcSelectStatus, svcSelectIndex, 2730 svcSelectIfIndex, svcSelectAddr, 2731 svcSelectAddrMask, svcSelectInclude, 2732 svcSelectCreateTime, svcSelectOwner, 2733 svcSelectStatus } 2734 STATUS current 2735 DESCRIPTION 2736 "Selects the virtual circuits that should be monitored as 2737 part of a specific collection-group." 2738 ::= { atmRmonMIBGroups 1 } 2740 atmStatsGroup OBJECT-GROUP 2741 OBJECTS { atmStatsControlDroppedCells, 2742 atmStatsControlHCDroppedCells, 2743 atmStatsControlOwner, 2744 atmStatsControlStatus, 2745 atmStatsCreateTime, 2746 atmStatsP2pCells, 2748 Draft ATM-RMON MIB February 1996 2750 atmStatsP2mpCells, 2751 atmStatsHCP2pCells, 2752 atmStatsHCP2mpCells, 2753 atmStatsNumP2pCalls, 2754 atmStatsNumP2mpCalls, 2755 atmStatsP2pConnectionTime, 2756 atmStatsP2mpConnectionTime } 2757 STATUS current 2758 DESCRIPTION 2759 "Counts the basic statistics for collections on behalf of 2760 particular vcSelectGroup collections." 2761 ::= { atmRmonMIBGroups 2 } 2763 atmHostGroup OBJECT-GROUP 2764 OBJECTS { 2765 atmHostControlInserts, 2766 atmHostControlDeletes, 2767 atmHostControlMaxDesiredEntries, 2768 atmHostControlPriority, 2769 atmHostControlDroppedCells, 2770 atmHostControlHCDroppedCells, 2771 atmHostControlOwner, 2772 atmHostControlStatus, 2773 atmHostCreateTime, 2774 atmHostInP2pCells, atmHostOutP2pCells, 2775 atmHostInP2mpCells, atmHostOutPm2pCells, 2776 atmHostInHCP2pCells, atmHostOutHCP2pCells, 2777 atmHostInHCP2mpCells, atmHostOutHCPm2pCells, 2778 atmHostInNumP2pCalls, atmHostOutNumP2pCalls, 2779 atmHostInNumP2mpCalls, atmHostOutNumP2mpCalls, 2780 atmHostP2pConnectionTime, 2781 atmHostP2mpConnectionTime, 2782 atmHostTopNControlRateBase, 2783 atmHostTopNControlTimeRemaining, 2784 atmHostTopNControlGeneratedReports, 2785 atmHostTopNControlDuration, 2786 atmHostTopNControlRequestedSize, 2787 atmHostTopNControlGrantedSize, 2788 atmHostTopNControlStartTime, 2789 atmHostTopNControlOwner, 2790 atmHostTopNControl STATUS, 2791 atmHostTopNAddress, atmHostTopNRate } 2792 STATUS current 2793 DESCRIPTION 2794 "Counts the amount of traffic sent from and to each ATM 2796 Draft ATM-RMON MIB February 1996 2798 address discovered by the probe, on behalf of particular 2799 vcSelectGroup collections." 2800 ::= { atmRmonMIBGroups 3 } 2802 atmMatrixGroup OBJECT-GROUP 2803 OBJECTS { atmMatrixControlInserts, 2804 atmMatrixControlDeletes, 2805 atmMatrixControlMaxDesiredEntries, 2806 atmMatrixControlPriority, 2807 atmMatrixControlDroppedCells, 2808 atmMatrixControlHCDroppedCells, 2809 atmMatrixControlOwner, 2810 atmMatrixControlStatus, 2811 atmMatrixCreateTime, 2812 atmMatrixP2pCells, 2813 atmMatrixP2mpCells, 2814 atmMatrixHCP2pCells, 2815 atmMatrixHCP2mpCells, 2816 atmMatrixNumP2pCalls, 2817 atmMatrixNumP2mpCalls, 2818 atmMatrixP2pConnectionTime, 2819 atmMatrixP2mpConnectionTime } 2820 STATUS current 2821 DESCRIPTION 2822 "Counts the amount of traffic sent between each pair of ATM 2823 addresses discovered by the probe, on behalf of particular 2824 vcSelectGroup collections." 2825 ::= { atmRmonMIBGroups 4 } 2827 END 2828 Draft ATM-RMON MIB February 1996 2830 5. Acknowledgements 2832 The authors wish to thank the following people for their comments and 2833 contributions in the development of this document: 2835 Ralph Beck 2836 Net2Net Corporation 2837 ralphb@net2net.com 2839 Robin A. Iddon 2840 AXON Networks, Inc. 2841 robini@axon.com 2843 Karen Sage 2844 NETSYS Technologies, Inc. 2845 karens@netsystech.com 2847 Anil Singhal 2848 Frontier Software Development, Inc. 2849 anil@frontier.com 2851 King Won 2852 Network General Corporation 2853 wonk@ngc.com 2855 Draft ATM-RMON MIB February 1996 2857 6. References 2859 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2860 S. Waldbusser, "Structure of Management Information for version 2 2861 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 2862 January 1996. 2864 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2865 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2866 RFC 1213, March 1991. 2868 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 2869 Management Protocol", RFC 1157, May 1990. 2871 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2872 S. Waldbusser, "Protocol Operations for version 2 of the Simple 2873 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 2875 [5] S. Waldbusser, "Remote Network Monitoring MIB", RFC 1757, Carnegie 2876 Mellon University, February 1995. 2878 [6] S. Waldbusser, "Token Ring Extensions to the Remote Network 2879 Monitoring MIB", RFC 1513, Carnegie Mellon University, September 2880 1993. 2882 [7] S. Waldbusser, "Remote Network Monitoring MIB (RMON-2)", draft- 2883 ietf-rmonmib-rmon2-03.txt, International Network Services, January 2884 1996. 2886 [8] Bierman, A., Iddon, R., "RMON Protocol Identifiers", draft-ietf- 2887 rmonmib-rmonprot-01.txt, Bierman Consulting, AXON Networks, Inc., 2888 January 1996. 2890 [9] Ahmed, M., and K. Tesink, Editors, "Definitions of Managed Objects 2891 for ATM Management Version 8.0 using SMIv2", RFC 1695, Bell 2892 Communications Research, August 1994. 2894 [10] Ly, F., Noto, M., Smith, A., Tesink, K., "Definitions of 2895 Supplemental Managed Objects for ATM Management", draft-ietf- 2896 atommib-atm2-05.txt, Bay Networks, Bell Communications Research, 2897 February 1996. 2899 Draft ATM-RMON MIB February 1996 2901 7. Security Considerations 2903 Security issues are not discussed in this memo. 2905 8. Authors' Addresses 2907 Andy Bierman 2908 Bierman Consulting 2909 1200 Sagamore Lane 2910 Ventura, CA 93001 2911 Phone: 805-648-2028 2912 Email: abierman@west.net 2914 Keith McCloghrie 2915 Cisco Systems, Inc. 2916 170 West Tasman Drive 2917 San Jose, CA 95134 2918 Phone: 408-526-5260 2919 Email: kzm@cisco.com 2921 Draft ATM-RMON MIB February 1996 2923 Table of Contents 2925 1 Introduction .................................................... 2 2926 1.1 The SNMP Network Management Framework ......................... 2 2927 1.2 Object Definitions ............................................ 2 2928 2 Overview ........................................................ 3 2929 2.1 RMON Resource Sharing Model ................................... 3 2930 2.2 Relationship to Existing MIBs ................................. 4 2931 2.2.1 RMON ........................................................ 4 2932 2.2.2 TR-RMON ..................................................... 5 2933 2.2.3 RMON-2 MIB .................................................. 5 2934 2.2.4 RMON-2 Protocol Identifiers ................................. 6 2935 2.2.5 ATOM MIB .................................................... 6 2936 2.2.6 ATOM Supplemental MIB ....................................... 6 2937 2.3 ATM-RMON Functional Requirements .............................. 6 2938 2.3.1 Collection Perspective ...................................... 7 2939 2.3.2 Cell Collection Requirements ................................ 9 2940 2.3.3 Frame Collection Requirements ............................... 10 2941 2.4 ATM-RMON Design Goals ......................................... 10 2942 2.4.1 Data Reduction .............................................. 11 2943 2.4.1.1 Pre-collection Data Reduction ............................. 11 2944 2.4.1.2 Post-collection Data Reduction ............................ 12 2945 2.4.2 Collection Source Issues .................................... 12 2946 3 MIB Proposal .................................................... 14 2947 3.1 MIB Structure ................................................. 14 2948 4 Definitions ..................................................... 16 2949 5 Acknowledgements ................................................ 70 2950 6 References ...................................................... 71 2951 7 Security Considerations ......................................... 72 2952 8 Authors' Addresses .............................................. 72