Draft ATM-RMON MIB May 1996 Remote Network Monitoring MIB Extensions for ATM Networks May 21, 1996 Andy Bierman Cisco Systems abierman@cisco.com Keith McCloghrie Cisco Systems, Inc. kzm@cisco.com Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as ``work in progress.'' To learn the current status of any Internet-Draft, please check the ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). Bierman/McCloghrie Expires November 21, 1996 [Page 1] =0C Draft ATM-RMON MIB May 1996 1. Introduction This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing remote monitoring probes, specifically for ATM networks. Bierman/McCloghrie Expires November 21, 1996 [Page 2] =0C Draft ATM-RMON MIB May 1996 2. The SNMP Network Management Framework The SNMP Network Management Framework presently consists of three major components. They are: o the SMI, described in RFC 1902 [1], - the mechanisms used for describing and naming objects for the purpose of management. o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects for the Internet suite of protocols. o the protocol, RFC 1157 [6] and/or RFC 1905 [4], - the protocol for accessing managed information. Textual conventions are defined in RFC 1903 [3], and conformance statements are defined in RFC 1905 [5]. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 2.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. Bierman/McCloghrie Expires November 21, 1996 [Page 3] =0C Draft ATM-RMON MIB May 1996 3. Overview This document addresses issues related to applying 'RMON technology' to ATM Networks: - functional applicability of existing RMON groups - new functionality for ATM networks - collection source design issues - flexible resource allocation - data reduction mechanisms RMON-based applications can provide system administrators with valuable data about network utilization and behavior. RMON agents offer applications developers resource-intensive functions such as high-level statistics gathering and low-level filtering/capture of MAC frames. RMON is traditionally deployed as one or more NMS applications managing multiple RMON probes, each of which is monitoring one or more network segments. RMON for ATM networks will require a different deployment model, as well as many other new MIB features. 3.1. RMON Resource Sharing Model There are some design features that are used throughout all the RMON MIBs. The most important is the RMON resource-sharing model. RMON agents are expected to create certain 'common' data-collection resources (ownerString starts with the string 'monitor'). Only system administrators should be allowed to delete or modify these 'monitor- owned' resources. NMS applications can create short-lived control entries (ownerString set to unique NMS-ID) if the monitor-owned collections are not appropriate for a given task. Some features, such as topN reporting, event- reporting, history collection (other than 30 sec/30 min intervals), and filter/capture, require some NMS configuration in most implementations. The resource owner (NMS) is expected to pick a unique value for the owner string and supply this value in the first setRequest PDU creating the control row. An NMS must check the rowStatus object (i.e. Bierman/McCloghrie Expires November 21, 1996 [Page 4] =0C Draft ATM-RMON MIB May 1996 errorStatus of PDU setting status to createAnd* before using the resource, to make sure another NMS was not allocated the resource instead. Before terminating, the NMS application must delete any control entries that it created. There is no control-row garbage collection defined in RMON, so an NMS application must check for its own stale control entries before creating new ones, upon startup. An NMS application may optionally use another applications' resources in a read-only manner, if applicable. Usually, this is only done when a resource request is refused. The system administrator is responsible for deleting RMON resources (monitor or NMS-owned) to make room for new applications. The latest RMON documents also provide a time-stamp in every data table row, to help an NMS detect the deletion and re-creation of that row. This MIB also provides 'lastCreateTime' time-stamps in all the data tables, as well as the control tables which do not have associated data tables. This MIB also contains a new resource management feature called the 'ResourcePriority'. Each control entry contains a configurable resource priority identifier ('low', 'normal', or 'high'), which the probe may inspect during garbage-collection of host or matrix entries, in order to avoid inadvertent deletion of important data. Note that the ResourcePriority only provides additional information to the probe for use during that probe's proprietary garbage collection algorithm (if any) any does not mandate any specific garbage collection or memory management design or implementation. At this time, least recently used (LRU) garbage collection is the recommended approach for probe host and matrix data table memory management. 3.2. Relationship to Existing MIBs There are several RFCs and Internet drafts which define RMON technology, which may relate to this MIB: 3.2.1. RMON The Remote Network Monitoring MIB (RMON or RMON-1) [7]] provides several management functions that may be directly or indirectly applicable to ATM Networks: Bierman/McCloghrie Expires November 21, 1996 [Page 5] =0C Draft ATM-RMON MIB May 1996 - Detailed link layer statistics for ethernet segments (etherStats group); ATM-RMON maintains a 'stats' group, simply to provide a grand total for the associated host and matrix tables. - Remote polling of detailed link layer statistics for ethernet segments (history, etherHistory groups); ATM-RMON utilizes the generic history collection application, found in the RMON-2 MIB [9] (see the section on RMON-2 for details). - Basic statistics--per host and per conversation--for all valid MAC addresses discovered on each monitored segment (host and matrix groups); ATM-RMON contains host and matrix functionality based on the versions found in RMON-2, which contain some updates to the RMON-1 versions. - TopN Report statistics (topN talkers or errors)--per-host--for each valid MAC address discovered on each monitored segment (hostTopN group) bit-level frame filtering and frame-slice capture (filter, channel, capture groups); ATM-RMON does not implement a hostTopN function, but rather a matrixTopN instead, since hostTopN can be derived from matrixTopN data. - Simple threshold monitoring, event-logging, and event-notification for any MIB instance; ATM-RMON utilizes the alarms and events groups from RMON-1 [7] without modification. These groups from RMON-1 [7] should be implemented on ATM-RMON probes if a simple thresholding mechanism is desired. 3.2.2. TR-RMON The Token Ring Extensions for RMON MIB (RFC1513) (TR-RMON) [8] provides the same kind of detailed link layer statistics and remote polling as found in RMON-1 (tokenRingMLStats/History, tokenRingPStats/History). The TR-RMON MIB is highly integrated with RMON-1, which is possible because both link layers use the same address format. An RMON MIB for ATM could be structured and positioned like the TR-MIB, but none of the shared tables can be directly applied to ATM. Since RMON-1 will be augmented and updated by RMON-2, any ATM-RMON standardization effort within the IETF should align with the RMON-2 MIB [9], but maintain the same 'extensions MIB' structure as found in the TR-RMON MIB. Bierman/McCloghrie Expires November 21, 1996 [Page 6] =0C Draft ATM-RMON MIB May 1996 3.2.3. RMON-2 MIB The emerging 'RMON-2' standard (RMON-2) [9] provides many additions and improvements to RMON-1: - Complete protocol distribution per segment (or 'collection source'). - Collection of network to MAC address bindings seen in packets on all segments. - Collection of source MAC address to physical interface bindings on all segments. - Probe configuration, such as startup parameters and trap destination management. - Collection of per network-layer host basic statistics (network layer and above). - Collection of per-conversation basic statistics (network layer and above). - TopN Report statistics per conversation (network layer and above). - Improvements such as relative-offset frame filtering, user-defined remote-polling, faster table retrieval, better NMS control of probe resources, and better accuracy reporting. Although the protocol analysis features are not directly applicable, there are many design improvements in RMON-2 that can be integrated into ATM-RMON: - TimeFilter indexing (see section on post-collection data reduction for details). - TopN report improvements such as auto-restart, report count, reverse-rates, and 'last-create-time' to detect discontinuities. - Control entry inserts and deletes counters (this replaces the RMON-1 'table-size' object). - ProtocolDirectory collection-control design (i.e. central configuration defines what data is collected in each functional group). Bierman/McCloghrie Expires November 21, 1996 [Page 7] =0C Draft ATM-RMON MIB May 1996 The usrHistory group (user-defined history collection) should be implemented on ATM-RMON probes if a history collection mechanism is desired for atmStats entries. 3.2.4. RMON-2 Protocol Identifiers The RMON Protocol Identifiers Specification (RMONPROT) [10] defines encoding rules for protocolDirID, protocolDirParameters, and protocolDirType MIB objects It is required only if RMON-2 packet analysis is applied to frames monitored (on circuits which use frames). Statistical analysis of frames is not directly applicable to this MIB, and is not discussed in this document. 3.2.5. ATOM MIB The Atom MIB is the fundamental MIB for managing ATM networks (RFC 1695) [11], but it is not directly referenced by this MIB, except for use of the 'IfIndex' textual convention. It is possible other textual conventions will be imported as well. 3.2.6. ATOM Supplemental MIB The Atom Supplemental MIB [12] defines additional management capabilities for ATM networks. The 'AtmAddr' textual convention is used from this MIB, as well as the AtmVclAddrBindTable. Since ATM-RMON only monitors address-based traffic, endpoint addresses have to be configured for a PVC before it can be counted by a probe. An agent implementation may choose to support statistics collection on PVC circuits if the AtmVclAddrBindTable is implemented as well. An NMS must properly configure the endpoint addresses on each PVC to be monitored, before activating any related ATM-RMON collections. 3.3. ATM-RMON Functional Requirements Applying RMON to ATM networks will require some new design changes and new functionality. Special problems such as high speeds, "cells vs. frames" issues, and the connection-oriented nature of ATM need special MIB solutions in order to implement RMON for ATM networks. Bierman/McCloghrie Expires November 21, 1996 [Page 8] =0C Draft ATM-RMON MIB May 1996 3.3.1. Physical Ports and Logical Ports Support for VP-tunneling via ATM Logical Ports [12] should be supported without special-case MIB objects. An NMS should be able to specify 'monitored-connections' (in part) by the ifIndex values associated with the ATM interfaces to be monitored. Any ifIndex value associated with an ifType value of 'atm(37)' (Interfaces MIB RFC 1573 [13]) or 'atmLogicalPort(80)' [12] can be specified for monitoring purposes. Note that a given ATM port is allowed to be included in at most one collection group, so as not to require a probe to count each monitored cell-stream more than once per function (e.g. stats, host, matrix). 3.3.2. Address-Based vs. Non-Address-Based Traffic Although ATM networks are capable of carrying many types of traffic (e.g. voice, video, data), only a subset of this traffic is monitored by ATM-RMON probes. RMON technology traditionally provides functions to monitor address-based traffic (i.e. transmissions for which the source and destination entities can be identified by examination). Therefore, an ATM-RMON probe only monitors connections established between two endpoint addresses. Although the 'AtmAddr' textual convention [12] allows several address type variants, only the twenty- octet NSAP format is used in this MIB. An NMS can monitor the 'ifInOctets' and 'ifOutOctets' objects for a particular ATM port (ifType =3D 'atm(37)' or 'atmLogicalPort(80)') to determine the total cell traffic through that port. The ATM-RMON MIB can be configured to provide the total address-based cell-traffic for a given port, which can be subtracted from the if*Octets counters to produce the non-address-based traffic totals. 3.3.3. Cell-Level Filter and Capture Since most applications requiring filter/capture functionality in the probe are for frame-based traffic (handled by RMON-1 and RMON-2), no cell-specific filter/capture MIB objects are included at this time. This functionality may be added in a future release of this MIB. Note that cell-specific filter/capture would not be restricted to address-based traffic, and may possibly be specified several ways (e.g. Bierman/McCloghrie Expires November 21, 1996 [Page 9] =0C Draft ATM-RMON MIB May 1996 ifIndex/VPI/VCI or endpoint address). 3.3.4. Collection Perspective There are four different 'collection perspectives' that should be accommodated: (A) stand-alone probe attached to a single port of a switch. ATM traffic is copied somehow to the RMON probe. (B) embedded probe within a switch., with no access to the switch fabric. ATM traffic is copied somehow to the RMON probe. (C) embedded probe within a switch, with access to the switch fabric. ATM traffic is monitored directly, probably implemented in hardware. Probes of this type are likely to monitor traffic at cell header level only. A lower level of conformance, or some other mechanism (e.g. additional software), will most likely be needed for this type of probe. (D) stand-alone probe, tapping an NNI link between two switches. ATM traffic is monitored directly (subject to probe capabilities), without switch intervention. All cells in both directions are copied somehow to the RMON probe. Bierman/McCloghrie Expires November 21, 1996 [Page 10] =0C Draft ATM-RMON MIB May 1996 Figure 1: Probe Location +------------------------------------------------------------------------= ----+ | = | | External Probe w/Circuit Steering Internal Probe w/Circuit Steeri= ng | | --------------------------------- -------------------------------= -- | | = | | || || = | | || || = | | +----------++----------+ +----------++-----------+ = | | | (A) | | (B) | = | | =3D=3D=3D=3D| ATM Switch |=3D=3D=3D=3D =3D=3D=3D=3D| A= TM Switch | | |=3D=3D=3D=3D | | | | | V V | = | | +----------++----------+ | +------------------+ | = | | || | | | | RMON probe | | = | | || V V | +------------------+ | = | | +----------------------+ +----------++-----------+ = | | | RMON probe | || = | | +----------------------+ || = | | = | | = | | Internal Probe wo/Circuit Steering External Probe wo/Circuit Steeri= ng | | ---------------------------------- --------------------------------= -- | | = | | || || || = | | || || || = | | +--------++-------+ +------++------+ +------++----= --+ | | | (C) | | (D) | | = | | | =3D=3D=3D=3D| ATM Switch w/ |=3D=3D=3D=3D =3D=3D=3D=3D| ATM Switch= 1 |=3D=3D=3D++=3D=3D| ATM Switch 2 | | | | internal RMON | | | || | = | | | | instrumentation | +------++------+ || +------++----= --+ | | +-----------------+ || || || = | | || || || || = | | || +------++------+ = | | | RMON probe | = | | +--------------+ = | | = | +------------------------------------------------------------------------= ----+ Unless RMON instrumentation is embedded into the switch fabric (C), or placed between two switches (D), then circuit steering is required (A and B) for RMON instrumentation software to access ATM traffic. For such probes, each full-duplex circuit is (presumably) mapped into two redirected half-duplex circuits: Bierman/McCloghrie Expires November 21, 1996 [Page 11] =0C Draft ATM-RMON MIB May 1996 - inbound(ifIndex/VPI/VCI) - outbound(ifIndex/VPI/VCI) A 'probe-tap' (D) does not pre-filter data by selecting particular circuits for monitoring. Instead, it receives all VCs on an NNI link, without switch participation. 3.3.5. Cell Collection Requirements This MIB provides the following new functionality: - ATM layer instrumentation - collection source aggregation - data reduction configuration and status - basic cell statistics (i.e. statsTable) - basic cell statistics per host (i.e. hostTable) - basic cell counts per conversation (i.e. matrixTable) - sorted reports, based on basic cell counts per conversation (i.e. matrixTopNTable) Circuit Steering requirements are not addressed in this document. RMON collection requirements will be considered independently of circuit steering techniques. Although references to 'copied' circuits are made in this document, actual circuit-steering implementation may be different. Therefore, this MIB is (presently) only directly applicable to collection models which do not require circuit-steering (i.e. models 'C' and 'D' in figure 1). At this time, only some very basic statistics are defined in the proposed MIB: - cells-sent count (32/32 pair and 64-bit counter) Bierman/McCloghrie Expires November 21, 1996 [Page 12] =0C Draft ATM-RMON MIB May 1996 - cells-received count (32/32 pair and 64-bit counter) - number of successful call setups (32 bit counter) - number of attempted call setups (32 bit counter) - total connection time (32 bit counter) Other statistics (e.g. error counters) may be added in the future. 3.3.6. Frame Collection Requirements An optional feature set for ATM-RMON is the analysis of frames on AAL-5 circuits. This can be accomplished with some minor additions to the RMON-2 MIB [9]. New values for dataSource objects can be defined which reference ATM collection sources (see MIB proposal below). The data can be formatted into RMON-2 host, matrix, matrixTopN, and filter/capture groups without requiring any RMON-2 MIB changes. (Encapsulation definitions have to be added to the Protocol Identifiers Specification [10].) Details on frame analysis integration with RMON-1 and RMON-2 MIBs are not discussed in this document, and will be deferred to a future release. 3.4. ATM-RMON Design The RMON Working Group within the Internet Engineering Task Force (IETF) will be updating and augmenting the RMON MIB soon, and several of these changes can be incorporated into an ATM-RMON MIB. The main advantages of borrowing from the RMON MIB [7]: - allow system administrators to reuse operational experience with RMON concepts and RMON data presentation (e.g. basic stats/host/matrix for a given media or protocol). - allow portions of standard MIBs to be applied directly to ATM-RMON without modification. - allow RMON NMS and probe vendors to possibly take advantage of their RMON-1 implementation experience. Bierman/McCloghrie Expires November 21, 1996 [Page 13] =0C Draft ATM-RMON MIB May 1996 - allow flexible configuration with low complexity. ATM-RMON will require new configuration mechanisms to deal with varying application needs and probe capabilities. RMON-1 [7] defines a 'dataSource' object of type OBJECT IDENTIFIER, which allows new or proprietary mechanisms beyond the 'ifIndex' object. RMON-2 provides for extension of allowable dataSource values. (The 'ifIndex.N' and 'rptrGroupPortIndex.N.M' formats are the only collection sources supported by the RMON WG at this time, but vendors are free to define unofficial values.) The ability to select circuits for monitoring is important for the conservation of agent resources. An NMS must be able to monitor an arbitrary number of circuits (subject to agent capabilities), which are selected by the endpoint address(es). Since RMON focuses on network entities which have addresses, the circuit selection mechanism should be address-based, allowing features such as per-port prefix-filtering. 3.4.1. Switch Port Aggregation Since ATM-RMON implementation is (in part) intended for ATM switches, special consideration for switches is desirable. All switched-based-RMON technology shares a similar problem regarding the per-port nature of RMON. AN NMS must configure and collect statistics (e.g. stats, host, matrix) independently for each monitored port. Usually, an NMS will 'collapse' most of the per-port statistics into an aggregate version for the switch. ATM-RMON provides a flexible mechanism to specify a particular 'data- source', including the ability to aggregate traffic from different ports into a single collection. See the portSelectGroup set of MIB objects for more details on port aggregation. 3.4.2. Data Reduction Traditionally, RMON host and matrix tables can be very large, and take a great deal of resources to manage by the NMS and maintain by the agent. The high speeds and complex collection requirements of ATM-RMON make it very desirable to reduce both the agent and NMS load for processing cell-traffic data. Bierman/McCloghrie Expires November 21, 1996 [Page 14] =0C Draft ATM-RMON MIB May 1996 Generally, agent resources can be saved with pre-collection data reduction, and NMS resources can be saved with post-collection data reduction. Both types are integrated into ATM-RMON. 3.4.2.1. Pre-collection Data Reduction The most effective way to save probe resources is to limit what data is processed in any manner by the probe, such as the use of statistical sampling. Note that statistical sampling only applies to frame capture and analysis. Frame capture mechanisms for ATM are not defined in this document, and there is no provision for the sampling of cells in the ATM-RMON MIB. The portSelectGroup mechanism described in the ATM-RMON MIB provides configurable filtering of cell traffic by the endpoint addresses associated with a particular connection, on a per-port basis. 3.4.2.2. Post-collection Data Reduction Even with pre-collection data reduction it is possible that ATM-RMON data tables will grow quite large, so it is also desirable to minimize the number of SNMP transactions required to retrieve or refresh these data tables. The mechanisms included in this MIB are: - Time Filter indexing -- allows an NMS to retrieve only the changed values since its last polling interval. - collection aggregation -- ability to control the granularity of the entries in the host and matrix tables. Entries can be selected by full-address or partial-address (i.e. the ESI bytes can be cleared to zero for indexing and counting purposes). This reduces the number of entries actually maintained by the probe. - TopN Report aggregation -- probe can continuously monitor the top talkers over a given interval, and automatically generate a report at the end of each interval. 3.4.3. Collection Source Identifier This MIB does not use the traditional RMON 'dataSource and arbitrary integer index' model for identifying collection sources. Instead, a set Bierman/McCloghrie Expires November 21, 1996 [Page 15] =0C Draft ATM-RMON MIB May 1996 of global tables are used to define 'circuit selection groups' (called 'portSelectGroups'). Traditional RMON collections (e.g. stats, host, matrix, matrixTopN) can be done using a portSelectGroup as the 'dataSource'. However, instead of an OBJECT IDENTIFIER dataSource identifier, a common integer index (identifying the portSelectGroup) is used in each control and data table. This allows an NMS to identify the source of a collection by examining the index of any columnar object. It also prevents duplicate collections from occurring on the probe. Note the collection criteria setup cannot be modified on the fly for a particular portSelectGroup, while any collections based on that portSelectGroup are in progress. In order to reduce agent complexity and maintain data integrity, specific collections must be halted, reconfigured, and then restarted (with an empty data-set) if runtime changes are required. Bierman/McCloghrie Expires November 21, 1996 [Page 16] =0C Draft ATM-RMON MIB May 1996 4. MIB Proposal The following MIB proposal is based, in part, on the RMON-2 MIB [9]. The open issues list: - No error counter instrumentation yet. - No notifications/traps defined yet. - The ZeroBasedCounter64 TC cannot be implemented with the current SMI. - No Cell-specific filter/capture functionality defined yet. - No frame-level statistics; RMON-2 integration is achieved by setting the particular dataSource object to reference an instance of the 'portSelGrpIndex' object, but details are not discussed in this MIB. RMON Protocol Identifier macros for ATM encapsulations also must be defined in order to monitor frame-based traffic with the RMON-2 MIB. 4.1. MIB Structure The MIB contains four groups: - portSelect -- port and circuit selection; data tables are indexed by a common object (portSelGrpIndex), which replaces the columnar 'dataSource' pointer and arbitrary integer index used in all other RMON MIBs. - atmStats -- basic statistics; allows individual host traffic contribution percentage to be easily calculated. - atmHost -- ATM per-host statistics. - atmMatrix -- ATM per-circuit statistics and ATM per-circuit matrixTopN reporting. Bierman/McCloghrie Expires November 21, 1996 [Page 17] =0C Draft ATM-RMON MIB May 1996 Figure 2: ATM-RMON MIB Structure +------------------------------------------------------------------------= + | = | | ATM-RMON Circuit Selection and Data Collection: Control Flow = | | ------------------------------------------------------------ = | | = | | +-----------------+ = | | | portSelGrp | > = | | +-----------------+ > +------------+ = | | | > ----> | atmStats | = | | V > +------------+ = | | +--------------+ > = | | +-+------------+ | > = | | | portSel |-+ > +------------+ = | | +--------------+ > ----> | atmHost | = | | | > +------------+ = | | V > = | | +---------------+ > +---------------+ = | | | addrFilterGrp | > +-----------+ +-+-------------+ | = | | +---------------+ > ----> | atmMatrix | --> | atmMatrixTopN |-+ = | | | +-----------+ +---------------+ = | | V = | | +-------------+ = | | +-+-----------+ | = | | | addrFilter |-+ = | | +-------------+ = | +------------------------------------------------------------------------= + The portSelectGroup is used to define the ports to be monitored for a particular set of functions (a subset of all ATM-RMON, RMON-1, and RMON-2 groups). It contains the addrFilterTable, which allows a set of filters to be specified for each monitored port. Each addrFilterGroup is used as a collection source for zero or one atmStats, atmHost, and atmMatrix collections. There may be an arbitrary number of atmMatrixTopN entries defined per portSelectGroup. Note that an agent implementation may limit the number of topN reports that may be concurrently configured, due to limited probe resources. For processing of frames collected (in an implementation-specific manner) from the portSelectGroup, the appropriate RMON-1 or RMON-2 dataSource instance is set to the OBJECT IDENTIFIER 'portSelGrpIndex.I'. [TBD: Row creation, modification, and deletion problems related to table dependencies between ATM-RMON and the other RMON MIBs.] Bierman/McCloghrie Expires November 21, 1996 [Page 18] =0C Draft ATM-RMON MIB May 1996 For processing of packets collected on behalf of RMON-2 functions, the proper protocol identifiers must be set up before the nlHost, alHost, nlMatrix, alMatrix, and filter2 groups can be utilized. [TBD: ATM encapsulation macro identifier additions to [10].] Bierman/McCloghrie Expires November 21, 1996 [Page 19] =0C Draft ATM-RMON MIB May 1996 5. Definitions ATM-RMON-MIB DEFINITIONS ::=3D BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, Gauge32, IpAddress, TimeTicks, Counter64, experimental FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, DisplayString, TimeStamp, TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF OwnerString FROM RFC1757-MIB ZeroBasedCounter32, LastCreateTime, TimeFilter FROM RMON2-MIB ifIndex, InterfaceIndex FROM IF-MIB IfIndex FROM ATM-MIB AtmAddr FROM ATM2-MIB; -- Remote Network Monitoring MIB for ATM Networks atmRmon MODULE-IDENTITY LAST-UPDATED "9605190000Z" ORGANIZATION "IETF" CONTACT-INFO "Andy Bierman Cisco Systems, Inc. Phone: +1 408 527-3711 Email: abierman@cisco.com Keith McCloghrie Cisco Systems, Inc. Phone: +1 408 526-5260 Email: kzm@cisco.com" DESCRIPTION "The MIB module for managing remote monitoring device implementations for ATM networks." ::=3D { experimental xx } -- ATM-RMON MIB groups Bierman/McCloghrie Expires November 21, 1996 [Page 20] =0C Draft ATM-RMON MIB May 1996 atmRmonMIBObjects OBJECT IDENTIFIER ::=3D { atmRmon 1 } atmRmonNotifications OBJECT IDENTIFIER ::=3D { atmRmon 2 } atmRmonConformance OBJECT IDENTIFIER ::=3D { atmRmon 3 } -- ATM-RMON MIB object groups portSelect OBJECT IDENTIFIER ::=3D { atmRmonMIBObjects 1 } atmStats OBJECT IDENTIFIER ::=3D { atmRmonMIBObjects 2 } atmHost OBJECT IDENTIFIER ::=3D { atmRmonMIBObjects 3 } atmMatrix OBJECT IDENTIFIER ::=3D { atmRmonMIBObjects 4 } Bierman/McCloghrie Expires November 21, 1996 [Page 21] =0C Draft ATM-RMON MIB May 1996 -- Textual Conventions: ServiceClass ::=3D TEXTUAL-CONVENTION STATUS current DESCRIPTION "This TC describes an object that identifies the cell delivery class-of-service classification, associated with a particular statistics collection. In order to conserve agent resources, the classifications are limited to two enumerations which distinguish delay-guarantee. Statistics gathered on behalf on collections identified by the 'cbrAndVbr(1)' enumeration represent constant-bit-rate (CBR), real-time and non-real-time variable bit rate (VBR) traffic. Statistics gathered on behalf on collections identified by the 'abrAndUbr(2)' enumeration represent available-bit-rate (ABR) and unspecified-bit-rate (UBR) traffic." SYNTAX INTEGER { cbrAndVbr(1), -- constant and variable bit rate abrAndUbr(2) -- available and unspecified bit rate } ResourcePriority ::=3D TEXTUAL-CONVENTION STATUS current DESCRIPTION "This TC describes an object which indicates the resource priority of the entire entry. Lower priorities indicate a lesser requirement to retain resources than higher priority values. A probe is strongly encouraged, but not required, to honor all priority requests, all of the time. Objects declared with this TC should be contained within a conceptual control table entry. The indicated resource priority applies to the control entry, all internal data structures maintained on behalf of the control entry, and all external MIB data represented by the control entry. A probe is expected to honor the priority requests in an implementation-dependent way. The following algorithm is suggested for those agents which implement garbage- collection based on 'least-recently used' (LRU) criteria: Bierman/McCloghrie Expires November 21, 1996 [Page 22] =0C Draft ATM-RMON MIB May 1996 In the event that the probe runs short of resources, and data entries are to be LRU-removed from particular tables, then entries associated with lower resourcePriority values shall be deleted before entries associated with higher resourcePriority values, regardless of the LRU algorithm in use. Note that the priority ordering of entries with the same ResourcePriority value is unspecified." SYNTAX INTEGER { lowPriority(1), normalPriority(2), highPriority(3) } ZeroBasedCounter64 ::=3D TEXTUAL-CONVENTION STATUS current DESCRIPTION "This TC describes an object which counts events with the following semantics: objects of this type will be set to zero(0) on creation and will thereafter count appropriate events, wrapping back to zero(0) when the value 2^64 is reached. Provided that an application discovers the new object within the minimum time to wrap it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time. Typically this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use." -- THIS IS BROKEN AND NEEDS TO BE CHANGED ASAP! -- (broken because Counter64 is defined not to start from zero) -- For SNMPv2, a new type Unsigned64 is needed -- no support in SNMPv1 for 64-bit counters SYNTAX Counter64 Bierman/McCloghrie Expires November 21, 1996 [Page 23] =0C Draft ATM-RMON MIB May 1996 -- -- Circuit Selection (portSelect Group) -- -- Defines the circuits to be included or excluded in -- a particular stats, host or matrix collection -- -- A set of ports is selected, and (optionally) a set of -- address-prefix filters is selected for each port. -- portSelGrpTable -- portSelTable -- addrFilterGrpTable -- addrFilterTable portSelGrpTable OBJECT-TYPE SYNTAX SEQUENCE OF PortSelGrpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Controls the setup of port and virtual circuit selection criteria used on behalf of any collection associated with entries in this table (e.g. atmHostTable). This table allows portSelTable entries with the same value of the portSelCollectGroup object to be grouped together to form port select groups. Note that an agent implementation may restrict the actual number of portSelGrp entries, due to resource limitations." ::=3D { portSelect 1 } portSelGrpEntry OBJECT-TYPE SYNTAX PortSelGrpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the portSelGrpTable. An example of the indexing of this entry is portSelGrpCreateTime.7 ." INDEX { portSelGrpIndex } ::=3D { portSelGrpTable 1 } PortSelGrpEntry ::=3D SEQUENCE { Bierman/McCloghrie Expires November 21, 1996 [Page 24] =0C Draft ATM-RMON MIB May 1996 portSelGrpIndex Integer32, portSelGrpDescr DisplayString, portSelGrpCreateTime LastCreateTime, portSelGrpOwner OwnerString, portSelGrpStatus RowStatus } portSelGrpIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An arbitrary and unique index for this portSelGrpEntry." ::=3D { portSelGrpEntry 1 } portSelGrpDescr OBJECT-TYPE SYNTAX DisplayString (SIZE(0..64)) MAX-ACCESS read-create STATUS current DESCRIPTION "An administratively-assigned descriptive label for this portSelGrp entry." ::=3D { portSelGrpEntry 2 } portSelGrpCreateTime OBJECT-TYPE SYNTAX LastCreateTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this Group entry was activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls." ::=3D { portSelGrpEntry 3 } portSelGrpOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." Bierman/McCloghrie Expires November 21, 1996 [Page 25] =0C Draft ATM-RMON MIB May 1996 ::=3D { portSelGrpEntry 4 } portSelGrpStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row. An entry may not exist in the active state unless all objects in the entry have an appropriate value. There are no required objects at this time, however all portSelTable, addrFilterGrpTable, and addrFilterTable entries, which are to be included in collections on behalf of this portSelectGroup, must be completely configured and activated before this object is set to active(1). If this object is not equal to active(1), all associated data collections shall be deleted (e.g. any associated collections in the atmHostTable or atmMatrixTable). Note that portSelTable, addrFilterGrpTable, and addrFilterTable entries are not deleted when this entry leaves the active state." ::=3D { portSelGrpEntry 5 } Bierman/McCloghrie Expires November 21, 1996 [Page 26] =0C Draft ATM-RMON MIB May 1996 -- -- portSelTable: used to specify the collection configuration -- for a single ATM port -- portSelTable OBJECT-TYPE SYNTAX SEQUENCE OF PortSelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Controls the setup of selection criteria for a single port, used on behalf of any collections identified with the associated portSelectGroup (identified by its portSelGrpIndex value). This table identifies the collection characteristics for the ATM port indicated by the ifIndex value in the index. Note that an agent implementation may restrict the actual number of portSelTable entries, due to resource limitations." ::=3D { portSelect 2 } portSelEntry OBJECT-TYPE SYNTAX PortSelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the portSelTable. Entries may only be created on behalf of ATM interfaces. That is, the ifType value associated with each ifIndex value must be equal to atm(37) or atmLogicalPort(80). An example of the indexing of this entry is portSelCreateTime.7 ." INDEX { ifIndex } ::=3D { portSelTable 1 } PortSelEntry ::=3D SEQUENCE { portSelCollectGroup Integer32, portSelFilterGroup Integer32, portSelCreateTime LastCreateTime, Bierman/McCloghrie Expires November 21, 1996 [Page 27] =0C Draft ATM-RMON MIB May 1996 portSelOwner OwnerString, portSelStatus RowStatus } portSelCollectGroup OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "This object identifies the associated instance of portSelGrpIndex, which indicates the portSelectGroup to which this port is assigned. This object may not be modified if the associated instance of portSelStatus is equal to active(1)." ::=3D { portSelEntry 1 } portSelFilterGroup OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "This object identifies the associated instance of addrFilterGrpIndex, which indicates which addrFilterTable entries should be applied to traffic seen on this port. Refer to the addrFilterGrpTable for more details on address filters. If this object has the value zero, or if this object references a non-existent set of address filters, then no addrFilterTable entries are applied to traffic on this port. If this references an existent, but incomplete set of address filters, then only those filters which are incomplete or misconfigured are ignored by the probe during the address filtering process. An agent may wish to verify a set of address filters before activating any portSelTable entries which reference them. This object may not be modified if the associated instance of portSelStatus is equal to active(1)." DEFVAL { 0 } ::=3D { portSelEntry 2 } Bierman/McCloghrie Expires November 21, 1996 [Page 28] =0C Draft ATM-RMON MIB May 1996 portSelCreateTime OBJECT-TYPE SYNTAX LastCreateTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this entry was activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls." ::=3D { portSelEntry 3 } portSelOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." ::=3D { portSelEntry 4 } portSelStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Specifically, appropriate values for the portSelCollectGroup and portSelFilterGroup objects must be set before this object may be set to active(1). An agent may wish to allow portSelTable entries to exist which reference non-existent portSelGrpTable entries, in order to reduce row creation order dependencies. All portSelTable, addrFilterGrpTable, and addrFilterTable entries, which are to be included in collections on behalf of this portSelectGroup, should be completely configured and activated before this object is set to active(1). Configuration of a portSelectGroup cannot be modified once collections on its behalf have been started. If this object is not equal to active(1), all associated Bierman/McCloghrie Expires November 21, 1996 [Page 29] =0C Draft ATM-RMON MIB May 1996 data collections shall be deleted (e.g. any associated collections in the atmHostTable or atmMatrixTable). This object may not be modified if the portSelGroupEntry, indicated by the same value of the portSelCollectGroup object in this table, is in the active(1) state." ::=3D { portSelEntry 5 } Bierman/McCloghrie Expires November 21, 1996 [Page 30] =0C Draft ATM-RMON MIB May 1996 -- addrFilterGrpTable -- -- Defines the PVCs and SVCs to be included or excluded from -- a particular portSelectGroup addrFilterGrpTable OBJECT-TYPE SYNTAX SEQUENCE OF AddrFilterGrpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Controls the setup of virtual circuit selection criteria used on behalf of any collection associated with entries in this table (e.g. atmHostTable). Each entry in this table controls and identifies zero or more associated entries in the addrFilterTable. Note that an agent implementation may restrict the actual number of addrFilterGrp entries supported by a single agent, due to resource limitations." ::=3D { portSelect 3 } addrFilterGrpEntry OBJECT-TYPE SYNTAX AddrFilterGrpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the addrFilterGrpTable. An example of the indexing of this entry is addrFilterGrpCreateTime.10 ." INDEX { addrFilterGrpIndex } ::=3D { addrFilterGrpTable 1 } AddrFilterGrpEntry ::=3D SEQUENCE { addrFilterGrpIndex Integer32, addrFilterGrpAcceptType INTEGER, addrFilterGrpCreateTime LastCreateTime, addrFilterGrpOwner OwnerString, addrFilterGrpStatus RowStatus } addrFilterGrpIndex OBJECT-TYPE Bierman/McCloghrie Expires November 21, 1996 [Page 31] =0C Draft ATM-RMON MIB May 1996 SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An arbitrary and unique index for this addrFilterGrpEntry." ::=3D { addrFilterGrpEntry 1 } addrFilterGrpAcceptType OBJECT-TYPE SYNTAX INTEGER { acceptMatch(1), acceptNotMatch(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object affects the way associated addrFilter entries are interpreted. It it similar to the 'channelAcceptType' object from RMON-1 [7]. If this object has the value 'acceptMatch(1)', then any circuits identified by addrSelect entries associated with this entry are included in the collection group. If this object has the value 'acceptNotMatch(1)', then any circuits not identified by addrSelect entries associated with this entry are included in the collection group. That is, all circuits are counted, except those which match any of the addrFilter entry filter criteria associated with this addrFilter group. Note that zero or more portSelTable entries may utilize the same addrFilterGrpEntry. This object may not be modified if the associated instance of addrFilterGrpStatus is equal to active(1)." ::=3D { addrFilterGrpEntry 2 } addrFilterGrpCreateTime OBJECT-TYPE SYNTAX LastCreateTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this addrFilterGrp entry was Bierman/McCloghrie Expires November 21, 1996 [Page 32] =0C Draft ATM-RMON MIB May 1996 activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls." ::=3D { addrFilterGrpEntry 3 } addrFilterGrpOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." ::=3D { addrFilterGrpEntry 4 } addrFilterGrpStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Specifically, the associated instance of addrFilterGrpAcceptType must be set before this object may be set to active(1). This object may not be modified if any active portSelectGroups reference this addrFilterGrpEntry. That is, if any instance of the portSelFilterGroup object is equal to the value of the addrSelectGrpIndex object identifying this entry, for any portSelEntry in the active state." ::=3D { addrFilterGrpEntry 5 } -- addrFilterTable -- -- Defines the PVCs and SVCs to be included or excluded from -- a particular addrFilter Group addrFilterTable OBJECT-TYPE SYNTAX SEQUENCE OF AddrFilterEntry MAX-ACCESS not-accessible Bierman/McCloghrie Expires November 21, 1996 [Page 33] =0C Draft ATM-RMON MIB May 1996 STATUS current DESCRIPTION "Controls the setup of address-prefix filters. A user may select a variable-length prefix to match against endpoint addresses on all circuits identified on a particular port. For ATM-RMON purposes, all of the prefix prefix portion (first 13 octets) and most of the ESI portion (first six octets) may be examined during address comparisons. In implementation, the probe actually screens ATM connections by the calling and called parties involved in the SVC connection setup. (A probe must identify the endpoint addresses associated with each applicable connection in an implementation-specific manner.) After the address endpoints are identified for a particular connection (i.e. calling and called party addresses for point-to-point connections; root and list-of-leaf addresses for point-to-multipoint), the Connection Match Algorithm (CMA) is executed for each appropriate addrFilterEntry in the address filter group assigned to the identified ATM port. (See below for details on the CMA.) In order for PVC traffic to be monitored, the 'AtmVclAddrBindTable' from the Supplemental Atom MIB [12] must be implemented by the same agent providing this MIB. The probe must then identify PVC address endpoints by examining each AtmVclAddrBindEntry with the same ifIndex index value as the addrFilterIfIndex object in each related addrFilterEntry. Local and remote address pairs and local ifIndex/VPI/VCI values are identified, and the CMA is executed for each appropriate addrFilterEntry. For SVC selection, a probe may choose to monitor the appropriate signaling traffic to determine the endpoint addresses associated with each SVC call setup on the specified port. Once the endpoint addresses have been identified for a particular circuit, the CMA is performed for each appropriate addrFilterEntry. The statistics collections done on behalf of each portSelectGroup will either include or exclude the identified circuit based on the value of the Bierman/McCloghrie Expires November 21, 1996 [Page 34] =0C Draft ATM-RMON MIB May 1996 associated portSelGrpAcceptType object. Connection Match Algorithm (CMA): INPUTS: addr1 =3D=3D one of the endpoint addresses associated w= ith this connection setup. addr2 =3D=3D the other endpoint address associated with= this connection setup. ifIndex_A =3D=3D ATM interface number associated with the connection setup ifIndex_B =3D=3D ATM interface number associated with the connection setup (may be the same as ifIndex_A) addrFilterEntry =3D=3D the address filter entry current= ly being evaluated. RETURNS: TRUE if the connection matches the filter criteria for = this entry FALSE if this connection does not match the filter crit= eria boolean CMA ( addr1, addr2, ifIndex_A, ifIndex_B, addrFilterEntry) { if (addrFilterPrefixCareBits =3D=3D 0) return FALSE; examine addr1 and/or addr2 according to addrFilterScope (for circuits on the port indicate= d by ifIndex_A and ifIndex_B values only); for (each prefix bit from left to right, from 0 to addrFilterPrefixCareBits-1) { compare appropriate addrFilterPrefixData bit to the appropriate addr1 and/or addr2 bit(s); return FALSE on first compare not-equal; } return TRUE because all bit compares equal; } Bierman/McCloghrie Expires November 21, 1996 [Page 35] =0C Draft ATM-RMON MIB May 1996 For the purpose of identifying leaf address values in point-to-multipoint circuits, any one of the leaf addresses may cause a match-condition (logical OR expression). During operation, each active addrFilter entry is grouped together by its major index (addrFilterGrpIndex), and is evaluated in the order of its minor index (addrFilterIndex). Successive entries are logically 'ORed' together to determine the boolean result of the CMA. The first positive result causes processing of addrFilter entries to cease, as a 'match condition' exists for the identified circuit. Note that an agent implementation may wish to detect broken configurations and possibly disallow misconfigured addrFilter entries. However, an NMS is responsible for preventing incorrect configuration of the addrFilterTable. Rationale: This table controls selection of the circuits to be monitored on behalf of one or more collections (either host or matrix) performed by this probe. It allows PVCs and SVCs to be selected by address-prefix masking, rather than VPI/VCI values." ::=3D { portSelect 4 } addrFilterEntry OBJECT-TYPE SYNTAX AddrFilterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the addrFilterTable. An example of the indexing of this entry is addrFilterIfIndex.1.2 . Note that an agent implementation may restrict the actual number of addrFilter entries supported for a given portSelectGroup." INDEX { addrFilterGrpIndex, addrFilterIndex } ::=3D { addrFilterTable 1 } AddrFilterEntry ::=3D SEQUENCE { addrFilterIndex Integer32, addrFilterPrefixData OCTET STRING, Bierman/McCloghrie Expires November 21, 1996 [Page 36] =0C Draft ATM-RMON MIB May 1996 addrFilterPrefixCareBits Integer32, addrFilterScope INTEGER, addrFilterCreateTime LastCreateTime, addrFilterOwner OwnerString, addrFilterStatus RowStatus } addrFilterIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique index for this addrFilterEntry. This index value identifies the addrFilterEntry and also defines its evaluation order within the filter group. AddrFilter entries are evaluated in ascending index order." ::=3D { addrFilterEntry 1 } addrFilterPrefixData OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..19)) MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used in the CMA, providing the address- prefix data bits used in address comparisons. If the associated instance of addrFilterPrefixCareBits is greater than the number of bits provided in this object, then this object is conceptually extended with zero bits, during the address comparison process. Note that address-to-cell association is done in an implementation-specific manner, requiring examination of signaling or configuration information related to the circuits described by this addrFilterEntry. This object may not be modified if the associated instance of addrFilterStatus is equal to active(1)." ::=3D { addrFilterEntry 2 } addrFilterPrefixCareBits OBJECT-TYPE Bierman/McCloghrie Expires November 21, 1996 [Page 37] =0C Draft ATM-RMON MIB May 1996 SYNTAX Integer32 (0..152) MAX-ACCESS read-create STATUS current DESCRIPTION "This object provides the number of prefix comparison bits, used in the CMA performed on circuits identified by this addrFilterEntry. It specifies the prefix-mask width, which is used in address comparisons of relevant called or calling party addresses. This object is assigned the number of consecutive bits, starting from the first bit of the prefix and counting from left to right, that should be checked in the appropriate address(es) and addrFilterPrefixData objects during the CMA. Note that if this object has the value zero, the CMA is not performed, and the boolean addr-match result for this entry is considered to be 'FALSE'. This object may not be modified if the associated instance of addrFilterStatus is equal to active(1)." ::=3D { addrFilterEntry 3 } addrFilterScope OBJECT-TYPE SYNTAX INTEGER { matchCallingOrCalled(1), matchCallingAndCalled(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object controls the scope of the selection criteria for this addrFilterEntry, by specifying which addresses associated with particular cell flows are being examined and possibly filtered by the probe. Note that cell flow direction is not examined, but rather calling and called party identities when implementing this object. That is, a probe must retain the address-endpoint association for a given connection, but does not have to identify call-origination or traffic direction for the purposes of address filter evaluation. If this object has the value 'matchCallingOrCalled(1)', then Bierman/McCloghrie Expires November 21, 1996 [Page 38] =0C Draft ATM-RMON MIB May 1996 circuits indicated by this entry are selected by applying the addrFilter algorithm to both addresses for each applicable cell flow, in any order. Either the calling party address or called party address (logical OR expression) can cause a match condition. If this object has the value 'matchCallingAndCalled(2)', then circuits indicated by this entry are selected by applying the addrFilter algorithm to both addresses for each applicable cell flow, in any order. Both the calling party and called party addresses (logical AND expression) must match in order for the entire addrFilter entry to cause a match condition. Note that at most one set of address filters (per portSelectGroup) may be evaluated for any given connection, even though two sets of address filters may be configured (i.e. different values of portSelCollectGroup for the ingress and egress ports). In such a case, the probe must evaluate the filters for the lower-numbered port and ignore the other set of filters. This restriction only applies if the two ports are in the same portSelectGroup (i.e. same values of portSelCollectGroup), but are configured to use different filter groups (i.e. same non-zero value of portSelFilterGroup). This object may not be modified if the associated instance of addrFilterStatus is equal to active(1)." ::=3D { addrFilterEntry 4 } addrFilterCreateTime OBJECT-TYPE SYNTAX LastCreateTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this addrFilter entry was activated. This can be used by the management station to ensure that the table has not been deleted and recreated between polls." ::=3D { addrFilterEntry 5 } addrFilterOwner OBJECT-TYPE SYNTAX OwnerString Bierman/McCloghrie Expires November 21, 1996 [Page 39] =0C Draft ATM-RMON MIB May 1996 MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." ::=3D { addrFilterEntry 6 } addrFilterStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Specifically, associated instances of addrFilterIfIndex, addrFilterPrefixData, addrFilterPrefixCareBits, and addrFilterScope must be set before this object may be set to active(1). This object may not be modified if the associated instance of addrFilterGrpStatus is equal to active(1). If this object is not equal to active(1), all associated data collections shall be deleted (e.g. any associated collections in the atmHostTable or atmMatrixTable)." ::=3D { addrFilterEntry 7 } Bierman/McCloghrie Expires November 21, 1996 [Page 40] =0C Draft ATM-RMON MIB May 1996 -- -- ATM Stats Group -- -- Counts the total amount of traffic -- counted on behalf of one or more portSelectGroups atmStatsControlTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmStatsControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of ATM basic statistic collection table control entries. These entries will enable the collection of statistical totals for an entire portSelectGroup." ::=3D { atmStats 1 } atmStatsControlEntry OBJECT-TYPE SYNTAX AtmStatsControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the atmStatsControlTable. Entries in this table are identified and indexed by the portSelGrpIndex object. At most one atmStats collection is done per portSelectGroup. An example of the indexing of this entry is atmStatsDropEvents.1 ." INDEX { portSelGrpIndex } ::=3D { atmStatsControlTable 1 } AtmStatsControlEntry ::=3D SEQUENCE { atmStatsControlDropEvents Counter32, atmStatsControlOwner OwnerString, atmStatsControlStatus RowStatus } atmStatsControlDropEvents OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION Bierman/McCloghrie Expires November 21, 1996 [Page 41] =0C Draft ATM-RMON MIB May 1996 "The total number of events in which cells which should have been counted in the associated atmStatsEntry, but were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of cells or calls dropped; it is just the number of times this condition has been detected." ::=3D { atmStatsControlEntry 1 } atmStatsControlOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." ::=3D { atmStatsControlEntry 2 } atmStatsControlStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this atmStatsControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Specifically, the associated instance of portSelGrpStatus (identified by its portSelGrpIndex index value) must be equal to active(1) before this object may be set to active(1). If this object is not equal to active(1), all associated entries in the atmStatsTable shall be deleted." ::=3D { atmStatsControlEntry 3 } Bierman/McCloghrie Expires November 21, 1996 [Page 42] =0C Draft ATM-RMON MIB May 1996 -- atmStatsTable -- call and traffic basic statistics collected on behalf of specific -- portSelectGroups atmStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF atmStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A collection of statistical totals for all ATM addresses that have been discovered on behalf of the portSelectGroup associated with this entry." ::=3D { atmStats 2 } atmStatsEntry OBJECT-TYPE SYNTAX AtmStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the atmStatsTable. The portSelGrpIndex value in the index identifies the portSelectGroup on whose behalf this entry was created. An example of the indexing of this entry is atmStatsCells.8.1" INDEX { portSelGrpIndex, atmStatsSClass } ::=3D { atmStatsTable 1 } AtmStatsEntry ::=3D SEQUENCE { atmStatsSClass ServiceClass, atmStatsCreateTime LastCreateTime, atmStatsCells Counter32, atmStatsCellsRollovers Counter32, atmStatsHCCells Counter64, atmStatsNumCallAttempts Counter32, atmStatsNumCalls Counter32, atmStatsConnTime TimeTicks } atmStatsSClass OBJECT-TYPE SYNTAX ServiceClass Bierman/McCloghrie Expires November 21, 1996 [Page 43] =0C Draft ATM-RMON MIB May 1996 MAX-ACCESS not-accessible STATUS current DESCRIPTION "The quality of service classification for this entry. See the ServiceClass textual convention for details and specific class-of-service values." ::=3D { atmStatsEntry 1 } atmStatsCreateTime OBJECT-TYPE SYNTAX LastCreateTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this entry was activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls." ::=3D { atmStatsEntry 2 } atmStatsCells OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of error-free cells detected on all circuits on behalf of this portSelectGroup collection. Note that a particular cell may only cause this counter to increment once, even if multiple criteria is met for inclusion in this portSelectGroup." ::=3D { atmStatsEntry 3 } atmStatsCellsRollovers OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times that the associated instance of the atmStatsCells object has transitioned from the value 2^^32-1 to zero." ::=3D { atmStatsEntry 4 } atmStatsHCCells OBJECT-TYPE SYNTAX Counter64 Bierman/McCloghrie Expires November 21, 1996 [Page 44] =0C Draft ATM-RMON MIB May 1996 MAX-ACCESS read-only STATUS current DESCRIPTION "The high capacity version of the atmStatsCells object." ::=3D { atmStatsEntry 5 } atmStatsNumCallAttempts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of call attempts detected on all SVCs on behalf of this portSelectGroup collection. A probe should increment this counter each time a connection setup attempt (identified with this portSelectGroup) is detected. For point-to-multipoint connections, this counter is incremented once per counted connection, regardless of the number of leafs identified in the connection." ::=3D { atmStatsEntry 6 } atmStatsNumCalls OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of successfully established calls detected on all SVCs on behalf of this portSelectGroup collection. Note that this value includes successfully established calls that are currently in progress. A probe should increment this counter each time a valid connection (identified with this portSelectGroup) is successfully established. For point-to- multipoint circuits, this counter is incremented once per counted connection, regardless of the number of leafs identified in the connection." ::=3D { atmStatsEntry 7 } atmStatsConnTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The elapsed time of all calls identified by the associated Bierman/McCloghrie Expires November 21, 1996 [Page 45] =0C Draft ATM-RMON MIB May 1996 instance of the atmStatsNumCallAttempts object. Note that point-to-multipoint calls are counted only once, regardless of the number of leafs participating in the call." ::=3D { atmStatsEntry 8 } Bierman/McCloghrie Expires November 21, 1996 [Page 46] =0C Draft ATM-RMON MIB May 1996 -- -- ATM Host Group -- -- Counts the amount of traffic sent on behalf of each ATM address -- discovered by the probe, according to associated portSelectGroup -- criteria atmHostControlTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmHostControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of ATM host table control entries. These entries will enable the collection of ATM host information in the atmHostTable. Entries in the atmHostTable will be created on behalf of each entry in this table. A probe is required to support at most one atmHost collection per instance of an associated portSelectGroup, therefore the table is indexed by the portSelGrpIndex." ::=3D { atmHost 1 } atmHostControlEntry OBJECT-TYPE SYNTAX AtmHostControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the atmHostControlTable. Entries in this table are identified and indexed by the portSelGrpIndex object. At most one atmHost collection is done per portSelectGroup. An example of the indexing of this entry is atmHostControlInserts.1" INDEX { portSelGrpIndex } ::=3D { atmHostControlTable 1 } AtmHostControlEntry ::=3D SEQUENCE { atmHostControlInserts Counter32, atmHostControlDeletes Counter32, atmHostControlMaxDesiredEntries Integer32, atmHostControlPriority ResourcePriority, atmHostControlCollectESI TruthValue, Bierman/McCloghrie Expires November 21, 1996 [Page 47] =0C Draft ATM-RMON MIB May 1996 atmHostControlDropEvents Counter32, atmHostControlOwner OwnerString, atmHostControlStatus RowStatus } atmHostControlInserts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times an atmHost entry has been inserted into the atmHost table. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting atmHostControlDeletes from atmHostControlInserts." ::=3D { atmHostControlEntry 1 } atmHostControlDeletes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times an atmHost entry has been deleted from the atmHost table (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting Bierman/McCloghrie Expires November 21, 1996 [Page 48] =0C Draft ATM-RMON MIB May 1996 atmHostControlDeletes from atmHostControlInserts." ::=3D { atmHostControlEntry 2 } atmHostControlMaxDesiredEntries OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of entries that are desired in the atmHostTable on behalf of this control entry. The probe will not create more than this number of associated entries in the table, but may choose to create fewer entries in this table for any reason including the lack of resources. If this value is set to -1, the probe may create any number of entries in this table. If the associated instance of atmHostControlStatus object is equal to active(1), this object may not be modified." ::=3D { atmHostControlEntry 3 } atmHostControlPriority OBJECT-TYPE SYNTAX ResourcePriority MAX-ACCESS read-create STATUS current DESCRIPTION "The priority this collection should be given to retain resources, in the event the probe must reclaim some resources in order to add new entries to an existing atmHost collection or add new collections of other types. If the associated instance of atmHostControlStatus object is equal to active(1), this object may not be modified." DEFVAL { normalPriority(2) } ::=3D { atmHostControlEntry 4 } atmHostControlCollectESI OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If this object has a value of 'true(1)', then atmHost Bierman/McCloghrie Expires November 21, 1996 [Page 49] =0C Draft ATM-RMON MIB May 1996 entries created on behalf of this control entry will identify the ESI portion of each selected address (according the the CMA), for the purposes of indexing and counting. If this object has a value of 'false(1)', then atmHost entries created on behalf of this control entry will not identify the ESI portion of each selected address (according the the CMA), and each ESI address bit will be cleared to zero for the purposes of indexing and counting. That is, all entries with the same 13 octet prefix will be aggregated into the same collection entry. If the associated instance of atmHostControlStatus object is equal to active(1), this object may not be modified." DEFVAL { true(1) } ::=3D { atmHostControlEntry 5 } atmHostControlDropEvents OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of events in which cells which should have been counted in the associated atmHostEntry, but were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of cells or calls dropped; it is just the number of times this condition has been detected." ::=3D { atmHostControlEntry 6 } atmHostControlOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." ::=3D { atmHostControlEntry 7 } atmHostControlStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create Bierman/McCloghrie Expires November 21, 1996 [Page 50] =0C Draft ATM-RMON MIB May 1996 STATUS current DESCRIPTION "The status of this atmHostControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Specifically, appropriate values for the associated instances of atmHostControlMaxDesiredEntries, atmHostControlPriority, atmHostControlCollectESI, and portSelGrpStatus must be set before this object may be set to active(1). If this object is not equal to active(1), all associated entries in the atmHostTable shall be deleted." ::=3D { atmHostControlEntry 8 } Bierman/McCloghrie Expires November 21, 1996 [Page 51] =0C Draft ATM-RMON MIB May 1996 atmHostTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmHostEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A collection of statistics for a particular ATM host address that has been discovered on behalf of the portSelectGroup associated with this entry. Note that only addresses of the 20 octet length variant of the AtmAddr textual convention are collected in this table. The probe will add to this table all addresses seen as the source or destination address in all cells identified by the associated portSelectGroup criteria." ::=3D { atmHost 2 } atmHostEntry OBJECT-TYPE SYNTAX AtmHostEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the atmHostTable. The portSelGrpIndex value in the index identifies the portSelectGroup on whose behalf this entry was created. An example of the indexing of this entry is atmHostInCells.4.28375.20..2" INDEX { portSelGrpIndex, atmHostTimeMark, atmHostAddress, atmHostSClass } ::=3D { atmHostTable 1 } AtmHostEntry ::=3D SEQUENCE { atmHostTimeMark TimeFilter, atmHostAddress AtmAddr, atmHostSClass ServiceClass, atmHostCreateTime LastCreateTime, atmHostInCells ZeroBasedCounter32, atmHostInCellsRollovers ZeroBasedCounter32, atmHostInHCCells ZeroBasedCounter64, atmHostOutCells ZeroBasedCounter32, atmHostOutCellsRollovers ZeroBasedCounter32, atmHostOutHCCells ZeroBasedCounter64, atmHostInNumCallAttempts ZeroBasedCounter32, Bierman/McCloghrie Expires November 21, 1996 [Page 52] =0C Draft ATM-RMON MIB May 1996 atmHostInNumCalls ZeroBasedCounter32, atmHostOutNumCallAttempts ZeroBasedCounter32, atmHostOutNumCalls ZeroBasedCounter32, atmHostInConnTime TimeTicks, atmHostOutConnTime TimeTicks } atmHostTimeMark OBJECT-TYPE SYNTAX TimeFilter MAX-ACCESS not-accessible STATUS current DESCRIPTION "A TimeFilter for this entry. See the TimeFilter textual convention in the RMON-2 MIB [9] to see how this works." ::=3D { atmHostEntry 1 } atmHostAddress OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS not-accessible STATUS current DESCRIPTION "The ATM address for this atmHostEntry. This is represented as an octet string with specific semantics and length as identified by the AtmAddr textual convention." ::=3D { atmHostEntry 2 } atmHostSClass OBJECT-TYPE SYNTAX ServiceClass MAX-ACCESS not-accessible STATUS current DESCRIPTION "The quality of service classification for this entry. See the ServiceClass textual convention for details and specific class-of-service values." ::=3D { atmHostEntry 3 } atmHostCreateTime OBJECT-TYPE SYNTAX LastCreateTime MAX-ACCESS read-only Bierman/McCloghrie Expires November 21, 1996 [Page 53] =0C Draft ATM-RMON MIB May 1996 STATUS current DESCRIPTION "The value of sysUpTime when this entry was activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls." ::=3D { atmHostEntry 4 } atmHostInCells OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of error-free cells detected on circuits associated with this portSelectGroup, in which this ATM address was identified as the receiver address, or one of the leaf addresses on a point-to-multipoint circuit." ::=3D { atmHostEntry 5 } atmHostInCellsRollovers OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times that the associated instance of the atmHostInCells object has transitioned from the value 2^^32-1 to zero." ::=3D { atmHostEntry 6 } atmHostInHCCells OBJECT-TYPE SYNTAX ZeroBasedCounter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The high capacity version of the atmHostInCells object." ::=3D { atmHostEntry 7 } atmHostOutCells OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION Bierman/McCloghrie Expires November 21, 1996 [Page 54] =0C Draft ATM-RMON MIB May 1996 "The number of error-free cells detected on circuits associated with this portSelectGroup, in which this ATM address was identified as the sender address." ::=3D { atmHostEntry 8 } atmHostOutCellsRollovers OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times that the associated instance of the atmHostOutCells object has transitioned from the value 2^^32-1 to zero." ::=3D { atmHostEntry 9 } atmHostOutHCCells OBJECT-TYPE SYNTAX ZeroBasedCounter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The high capacity version of the atmHostOutCells object." ::=3D { atmHostEntry 10 } atmHostInNumCallAttempts OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of calls detected on circuits associated with this entry, in which the associated endpoint address was identified as the called party in an SVC establishment attempt. Note that this value includes calls that are currently in progress. A probe should increment this counter each time a connection attempt is detected in which this ATM host is identified as the called party, or one of the leaf addresses for point-to-multipoint circuits." ::=3D { atmHostEntry 11 } atmHostInNumCalls OBJECT-TYPE Bierman/McCloghrie Expires November 21, 1996 [Page 55] =0C Draft ATM-RMON MIB May 1996 SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of successfully established calls detected on circuits associated with this entry, in which the associated endpoint address was identified as the called party address. Note that this value includes calls that are currently in progress. A probe should increment this counter each time a connection is successfully established in which this ATM host is identified as the called party address, or one of the leaf addresses for point-to-multipoint circuits." ::=3D { atmHostEntry 12 } atmHostOutNumCallAttempts OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of calls detected on circuits associated with this entry, in which the associated endpoint address was identified as the calling party in an SVC establishment attempt. Note that this value includes calls that are currently in progress. A probe should increment this counter each time a connection attempt is detected in which this ATM host is identified as the calling party. Note that for point-to-multipoint circuits, this counter is incremented only once per call, regardless of the number of leafs established at setup time or the number of leaf- initiated-join attempts since the call was established." ::=3D { atmHostEntry 13 } atmHostOutNumCalls OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of successfully established calls detected on circuits associated with this entry, in which the associated Bierman/McCloghrie Expires November 21, 1996 [Page 56] =0C Draft ATM-RMON MIB May 1996 endpoint address was identified as the calling party address. Note that this value includes calls that are currently in progress. A probe should increment this counter each time a connection is successfully established in which this ATM host is identified as the calling party address." ::=3D { atmHostEntry 14 } atmHostInConnTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The elapsed time of all calls identified by the associated instance of atmHostInNumCallAttempts." ::=3D { atmHostEntry 15 } atmHostOutConnTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The elapsed time of all calls identified by the associated instance of atmHostOutNumCallAttempts." ::=3D { atmHostEntry 16 } Bierman/McCloghrie Expires November 21, 1996 [Page 57] =0C Draft ATM-RMON MIB May 1996 -- -- ATM Matrix Group -- -- Counts the amount of traffic sent on behalf of each source -- and destination ATM address discovered by the probe, -- according to associated portSelectGroup criteria atmMatrixControlTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmMatrixControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of ATM matrix table control entries. These entries will enable the collection of ATM matrix information in the atmMatrixSDTable and atmMatrixDSTable. A probe is required to support at most one atmMatrix collection per instance of an associated portSelectGroup, therefore the table is indexed by the portSelGrpIndex. Note that only addresses of the twenty-byte-length variant (of the AtmAddr textual convention) are collected in this table." ::=3D { atmMatrix 1 } atmMatrixControlEntry OBJECT-TYPE SYNTAX AtmMatrixControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the atmMatrixControlTable. An example of the indexing of this entry is atmMatrixControlInserts.1" INDEX { portSelGrpIndex } ::=3D { atmMatrixControlTable 1 } AtmMatrixControlEntry ::=3D SEQUENCE { atmMatrixControlInserts Counter32, atmMatrixControlDeletes Counter32, atmMatrixControlMaxDesiredEntries Integer32, atmMatrixControlPriority ResourcePriority, atmMatrixControlCollectESIScope INTEGER, Bierman/McCloghrie Expires November 21, 1996 [Page 58] =0C Draft ATM-RMON MIB May 1996 atmMatrixControlDropEvents Counter32, atmMatrixControlOwner OwnerString, atmMatrixControlStatus RowStatus } atmMatrixControlInserts OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times an atmMatrix entry has been inserted into the atmMatrix table. If an entry is inserted, then deleted, and then inserted, this counter will be incremented by 2. The addition of a conversation into both the atmMatrixSDTable and atmMatrixDSTable shall be counted as two insertions (even though every addition into one table must be accompanied by an insertion into the other). To allow for efficient implementation strategies, agents may delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting atmMatrixControlDeletes from atmMatrixControlInserts." ::=3D { atmMatrixControlEntry 1 } atmMatrixControlDeletes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times an atmMatrix entry has been deleted from the atmMatrix table (for any reason). If an entry is deleted, then inserted, and then deleted, this counter will be incremented by 2. The deletion of a conversation from both the atmMatrixSDTable and atmMatrixDSTable shall be counted as two deletions (even though every deletion from one table must be accompanied by a deletion from the other). To allow for efficient implementation strategies, agents may Bierman/McCloghrie Expires November 21, 1996 [Page 59] =0C Draft ATM-RMON MIB May 1996 delay updating this object for short periods of time. For example, an implementation strategy may allow internal data structures to differ from those visible via SNMP for short periods of time. This counter may reflect the internal data structures for those short periods of time. Note that the table size can be determined by subtracting atmMatrixControlDeletes from atmMatrixControlInserts." ::=3D { atmMatrixControlEntry 2 } atmMatrixControlMaxDesiredEntries OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of entries that are desired in the atmMatrixTable on behalf of this control entry. The probe will not create more than this number of associated entries in the table, but may choose to create fewer entries in this table for any reason including the lack of resources. If this value is set to -1, the probe may create any number of entries in this table. If the associated instance of atmMatrixControlStatus object is equal to active(1), this object may not be modified." ::=3D { atmMatrixControlEntry 3 } atmMatrixControlPriority OBJECT-TYPE SYNTAX ResourcePriority MAX-ACCESS read-create STATUS current DESCRIPTION "The priority this collection should be given to retain resources, in the event the probe must reclaim some resources in order to add new entries to an existing atmMatrix collection or add new collections of other types. If the associated instance of atmMatrixControlStatus object is equal to active(1), this object may not be modified." DEFVAL { normalPriority(2) } ::=3D { atmMatrixControlEntry 4 } Bierman/McCloghrie Expires November 21, 1996 [Page 60] =0C Draft ATM-RMON MIB May 1996 atmMatrixControlCollectESIScope OBJECT-TYPE SYNTAX INTEGER { srcESI(1), dstESI(2), noESI(3), bothESI(4) } MAX-ACCESS read-create STATUS current DESCRIPTION "If this object has a value of 'srcESI(1)', then atmMatrix entries created on behalf of this control entry in the atmMatrixSDTable and atmMatrixDSTable will identify the ESI portion of each selected source address (according the the CMA), for the purposes of indexing and counting. The ESI component of the destination address will be cleared to zero bits for the purposes of indexing and counting. If this object has a value of 'dstESI(2)', then atmMatrix entries created on behalf of this control entry in the atmMatrixSDTable and atmMatrixDSTable will identify the ESI portion of each selected destination address (according the the CMA), for the purposes of indexing and counting. The ESI component of the source address will be cleared to zero bits for the purposes of indexing and counting. If this object has a value of 'noESI(3)', then atmMatrix entries created on behalf of this control entry in the atmMatrixSDTable and atmMatrixDSTable will not identify the ESI portion of either the source or destination addresses (according the the CMA), for the purposes of indexing and counting. The ESI component of the source and destination addresses will be cleared to zero bits for the purposes of indexing and counting. If this object has a value of 'bothESI(4)', then atmMatrix entries created on behalf of this control entry in the atmMatrixSDTable and atmMatrixDSTable will identify the ESI portion of each selected source and destination address (according the the CMA), for the purposes of indexing and counting. Note that this object does not affect the CMA, just the representation of addresses stored in atmMatrix data tables on behalf of this control entry. Bierman/McCloghrie Expires November 21, 1996 [Page 61] =0C Draft ATM-RMON MIB May 1996 If the associated instance of atmMatrixControlStatus object is equal to active(1), this object may not be modified." DEFVAL { bothESI(4) } ::=3D { atmMatrixControlEntry 5 } atmMatrixControlDropEvents OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of events in which cells which should have been counted in the associated atmMatrixSDEntry and atmMatrixDSEntry, but were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of cells or calls dropped; it is just the number of times this condition has been detected." ::=3D { atmMatrixControlEntry 6 } atmMatrixControlOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." ::=3D { atmMatrixControlEntry 7 } atmMatrixControlStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this atmMatrixControlEntry. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Specifically, the associated instances of atmMatrixControlMaxDesiredEntries, atmMatrixControlPriority, atmMatrixControlCollectESIScope, and portSelGrpStatus objects must be set to appropriate values before this object may be set to active(1). Bierman/McCloghrie Expires November 21, 1996 [Page 62] =0C Draft ATM-RMON MIB May 1996 If this object is not equal to active(1), all associated entries in the atmMatrixSDTable and atmMatrixDSTable shall be deleted." ::=3D { atmMatrixControlEntry 8 } Bierman/McCloghrie Expires November 21, 1996 [Page 63] =0C Draft ATM-RMON MIB May 1996 -- atmMatrixSDTable -- call and traffic data collected on behalf of specific -- portSelectGroups -- sorted by src address first atmMatrixSDTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmMatrixSDEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A collection of statistics for conversations between particular ATM endpoint addresses that have been discovered on behalf of the portSelectGroup associated with this entry. Note that only addresses of the 20 octet length variant of the AtmAddr textual convention are collected in this table. The probe will add a new entry to this table for all conversations (connections) between distinct source and destination address pairs, detected in all cells identified by the associated portSelGrpEntry criteria. Further, this table will only contain entries that have a corresponding entry in the atmMatrixDSTable with the same source address and destination address." ::=3D { atmMatrix 2 } atmMatrixSDEntry OBJECT-TYPE SYNTAX AtmMatrixSDEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the atmMatrixSDTable. The portSelGrpIndex value in the index identifies the portSelectGroup on whose behalf this entry was created. An example of the indexing of this entry is atmMatrixSDCells.1.28980.20..20..2" INDEX { portSelGrpIndex, atmMatrixSDTimeMark, atmMatrixSDSrcAddress, atmMatrixSDDstAddress, atmMatrixSDSClass } ::=3D { atmMatrixSDTable 1 } Bierman/McCloghrie Expires November 21, 1996 [Page 64] =0C Draft ATM-RMON MIB May 1996 AtmMatrixSDEntry ::=3D SEQUENCE { atmMatrixSDTimeMark TimeFilter, atmMatrixSDSrcAddress AtmAddr, atmMatrixSDDstAddress AtmAddr, atmMatrixSDSClass ServiceClass, atmMatrixSDCreateTime LastCreateTime, atmMatrixSDCells ZeroBasedCounter32, atmMatrixSDCellsRollovers ZeroBasedCounter32, atmMatrixSDHCCells ZeroBasedCounter64, atmMatrixSDNumCallAttempts ZeroBasedCounter32, atmMatrixSDNumCalls ZeroBasedCounter32, atmMatrixSDConnTime TimeTicks } atmMatrixSDTimeMark OBJECT-TYPE SYNTAX TimeFilter MAX-ACCESS not-accessible STATUS current DESCRIPTION "A TimeFilter for this entry. See the TimeFilter textual convention in the RMON-2 MIB [9] to see how this works." ::=3D { atmMatrixSDEntry 1 } atmMatrixSDSrcAddress OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS not-accessible STATUS current DESCRIPTION "The transmitting endpoint ATM address for this atmMatrixSDEntry. This is represented as an octet string with specific semantics and length as identified by the AtmAddr textual convention." ::=3D { atmMatrixSDEntry 2 } atmMatrixSDDstAddress OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS not-accessible STATUS current DESCRIPTION "The destination endpoint ATM address for this Bierman/McCloghrie Expires November 21, 1996 [Page 65] =0C Draft ATM-RMON MIB May 1996 atmMatrixSDEntry. This is represented as an octet string with specific semantics and length as identified by the AtmAddr textual convention." ::=3D { atmMatrixSDEntry 3 } atmMatrixSDSClass OBJECT-TYPE SYNTAX ServiceClass MAX-ACCESS not-accessible STATUS current DESCRIPTION "The quality of service classification for this entry. See the ServiceClass textual convention for details and specific class-of-service values." ::=3D { atmMatrixSDEntry 4 } atmMatrixSDCreateTime OBJECT-TYPE SYNTAX LastCreateTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this entry was activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls." ::=3D { atmMatrixSDEntry 5 } atmMatrixSDCells OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of error-free cells detected on circuits in which these ATM addresses were identified as the transmitting and receiving endpoint addresses. Note that for point-to-multipoint connections, an entry is created for each root-to-leaf address-pair that exists, and each cell sent from the root on a point-to-multipoint circuit is counted once in each distinct matrix entry." ::=3D { atmMatrixSDEntry 6 } Bierman/McCloghrie Expires November 21, 1996 [Page 66] =0C Draft ATM-RMON MIB May 1996 atmMatrixSDCellsRollovers OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times that the associated instance of the atmMatrixSDCells object has transitioned from the value 2^^32-1 to zero." ::=3D { atmMatrixSDEntry 7 } atmMatrixSDHCCells OBJECT-TYPE SYNTAX ZeroBasedCounter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The high capacity version of the atmMatrixSDCells object." ::=3D { atmMatrixSDEntry 8 } atmMatrixSDNumCallAttempts OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SVC call setup attempts detected on circuits within the specified portSelectGroup, in which the indicated atmMatrixSDSrcAddress endpoint address was identified as the calling party and the indicated atmMatrixSDDstAddress was identified as the called party. Note that this value includes calls that are currently in progress. A probe should increment this counter each time a connection attempt is detected in which these ATM addresses are identified as the calling and called parties." ::=3D { atmMatrixSDEntry 9 } atmMatrixSDNumCalls OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of successful SVC call setups detected on circuits within the specified portSelectGroup, in which the indicated atmMatrixSDSrcAddress endpoint address was Bierman/McCloghrie Expires November 21, 1996 [Page 67] =0C Draft ATM-RMON MIB May 1996 identified as the calling party and the indicated atmMatrixSDDstAddress was identified as the called party. Note that this value includes calls that are currently in progress. A probe should increment this counter each time a valid connection is established in which these ATM addresses are identified as the calling and called parties." ::=3D { atmMatrixSDEntry 10 } atmMatrixSDConnTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The elapsed time of all calls identified by the associated instance of atmMatrixSDNumCallAttempts." ::=3D { atmMatrixSDEntry 11 } Bierman/McCloghrie Expires November 21, 1996 [Page 68] =0C Draft ATM-RMON MIB May 1996 -- atmMatrixDSTable -- call and traffic data collected on behalf of specific -- portSelectGroups -- sorted by destination address first atmMatrixDSTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmMatrixDSEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A collection of statistics for conversations between particular ATM endpoint addresses that have been discovered on behalf of the portSelectGroup associated with this entry. Note that only addresses of the 20 octet length variant of the AtmAddr textual convention are collected in this table. The probe will add a new entry to this table for all conversations (connections) between distinct source and destination address pairs, detected in all cells identified by the associated portSelGrpEntry criteria. Further, this table will only contain entries that have a corresponding entry in the atmMatrixSDTable with the same source address and destination address." ::=3D { atmMatrix 3 } atmMatrixDSEntry OBJECT-TYPE SYNTAX AtmMatrixDSEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the atmMatrixDSTable. The portSelGrpIndex value in the index identifies the portSelectGroup on whose behalf this entry was created. An example of the indexing of this entry is atmMatrixDSCells.1.28980.20..20..2" INDEX { portSelGrpIndex, atmMatrixDSTimeMark, atmMatrixDSDstAddress, atmMatrixDSSrcAddress, atmMatrixDSSClass } ::=3D { atmMatrixDSTable 1 } atmMatrixDSEntry ::=3D SEQUENCE { Bierman/McCloghrie Expires November 21, 1996 [Page 69] =0C Draft ATM-RMON MIB May 1996 atmMatrixDSTimeMark TimeFilter, atmMatrixDSSrcAddress AtmAddr, atmMatrixDSDstAddress AtmAddr, atmMatrixDSSClass ServiceClass, atmMatrixDSCreateTime LastCreateTime, atmMatrixDSCells ZeroBasedCounter32, atmMatrixDSCellsRollovers ZeroBasedCounter32, atmMatrixDSHCCells ZeroBasedCounter64, atmMatrixDSNumCallAttempts ZeroBasedCounter32, atmMatrixDSNumCalls ZeroBasedCounter32, atmMatrixDSConnTime TimeTicks } atmMatrixDSTimeMark OBJECT-TYPE SYNTAX TimeFilter MAX-ACCESS not-accessible STATUS current DESCRIPTION "A TimeFilter for this entry. See the TimeFilter textual convention in the RMON-2 MIB [9] to see how this works." ::=3D { atmMatrixDSEntry 1 } atmMatrixDSSrcAddress OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS not-accessible STATUS current DESCRIPTION "The transmitting endpoint ATM address for this atmMatrixDSEntry. This is represented as an octet string with specific semantics and length as identified by the AtmAddr textual convention." ::=3D { atmMatrixDSEntry 2 } atmMatrixDSDstAddress OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS not-accessible STATUS current DESCRIPTION "The destination endpoint ATM address for this atmMatrixDSEntry. Bierman/McCloghrie Expires November 21, 1996 [Page 70] =0C Draft ATM-RMON MIB May 1996 This is represented as an octet string with specific semantics and length as identified by the AtmAddr textual convention." ::=3D { atmMatrixDSEntry 3 } atmMatrixDSSClass OBJECT-TYPE SYNTAX ServiceClass MAX-ACCESS not-accessible STATUS current DESCRIPTION "The quality of service classification for this entry. See the ServiceClass textual convention for details and specific class-of-service values." ::=3D { atmMatrixDSEntry 4 } atmMatrixDSCreateTime OBJECT-TYPE SYNTAX LastCreateTime MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this entry was activated. This can be used by the management station to ensure that the entry has not been deleted and recreated between polls." ::=3D { atmMatrixDSEntry 5 } atmMatrixDSCells OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of error-free cells detected on circuits in which these ATM addresses were identified as the transmitting and receiving endpoint addresses. Note that for point-to-multipoint connections, an entry is created for each root-to-leaf address-pair that exists, and each cell sent from the root on a point-to-multipoint circuit is counted once in each distinct matrix entry." ::=3D { atmMatrixDSEntry 6 } atmMatrixDSCellsRollovers OBJECT-TYPE Bierman/McCloghrie Expires November 21, 1996 [Page 71] =0C Draft ATM-RMON MIB May 1996 SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of times that the associated instance of the atmMatrixDSCells object has transitioned from the value 2^^32-1 to zero." ::=3D { atmMatrixDSEntry 7 } atmMatrixDSHCCells OBJECT-TYPE SYNTAX ZeroBasedCounter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The high capacity version of the atmMatrixDSCells object." ::=3D { atmMatrixDSEntry 8 } atmMatrixDSNumCallAttempts OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of SVC call setup attempts detected on circuits within the specified portSelectGroup, in which the indicated atmMatrixDSSrcAddress endpoint address was identified as the calling party and the indicated atmMatrixDSDstAddress was identified as the called party. Note that this value includes calls that are currently in progress. A probe should increment this counter each time a connection attempt is detected in which these ATM addresses are identified as the calling and called parties." ::=3D { atmMatrixDSEntry 9 } atmMatrixDSNumCalls OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of successful SVC call setups detected on circuits within the specified portSelectGroup, in which the indicated atmMatrixDSSrcAddress endpoint address was identified as the calling party and the indicated Bierman/McCloghrie Expires November 21, 1996 [Page 72] =0C Draft ATM-RMON MIB May 1996 atmMatrixDSDstAddress was identified as the called party. Note that this value includes calls that are currently in progress. A probe should increment this counter each time a valid connection is established in which these ATM addresses are identified as the calling and called parties." ::=3D { atmMatrixDSEntry 10 } atmMatrixDSConnTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The elapsed time of all calls identified by the associated instance of atmMatrixDSNumCallAttempts." ::=3D { atmMatrixDSEntry 11 } Bierman/McCloghrie Expires November 21, 1996 [Page 73] =0C Draft ATM-RMON MIB May 1996 -- -- ATM MatrixTopN Tables -- -- Finds and reports the top traffic contributors, -- according to associated portSelectGroup criteria atmMatrixTopNControlTable OBJECT-TYPE SYNTAX SEQUENCE OF atmMatrixTopNControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of parameters that control the creation of a report of the top N matrix entries according to a selected metric." ::=3D { atmMatrix 4 } atmMatrixTopNControlEntry OBJECT-TYPE SYNTAX AtmMatrixTopNControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the atmMatrixTopNControlTable. An example of the indexing of this table is atmMatrixTopNControlDuration.3.1" INDEX { portSelGrpIndex, atmMatrixTopNControlIndex } ::=3D { atmMatrixTopNControlTable 1 } AtmMatrixTopNControlEntry ::=3D SEQUENCE { atmMatrixTopNControlIndex Integer32, atmMatrixTopNControlRateBase INTEGER, atmMatrixTopNControlSClass ServiceClass, atmMatrixTopNControlTimeRemaining Integer32, atmMatrixTopNControlGeneratedReports Counter32, atmMatrixTopNControlDuration Integer32, atmMatrixTopNControlRequestedSize Integer32, atmMatrixTopNControlGrantedSize Integer32, atmMatrixTopNControlStartTime TimeStamp, atmMatrixTopNControlOwner OwnerString, atmMatrixTopNControlStatus RowStatus } atmMatrixTopNControlIndex OBJECT-TYPE Bierman/McCloghrie Expires November 21, 1996 [Page 74] =0C Draft ATM-RMON MIB May 1996 SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An index that is used to uniquely identify an entry in the atmMatrixTopNControlTable. Each such entry defines one top N report prepared on behalf of one atmMatrix entry, which must exist before this entry may be created." ::=3D { atmMatrixTopNControlEntry 1 } atmMatrixTopNControlRateBase OBJECT-TYPE SYNTAX INTEGER { atmMatrixTopNCells(1), atmMatrixTopNNumCallAttempts(2), atmMatrixTopNNumCalls(3), atmMatrixTopNConnTime(4) } MAX-ACCESS read-create STATUS current DESCRIPTION "The variable for each atmMatrix entry that the atmMatrixTopNEntries are sorted by. This object may not be modified if the associated atmMatrixTopNControlStatus object is equal to active(1)." ::=3D { atmMatrixTopNControlEntry 2 } atmMatrixTopNControlSClass OBJECT-TYPE SYNTAX ServiceClass MAX-ACCESS read-create STATUS current DESCRIPTION "The service class for which this topN control entry is collecting information in associated atmMatrixTopN reports. This object may not be modified if the associated atmMatrixTopNControlStatus object is equal to active(1)." ::=3D { atmMatrixTopNControlEntry 3 } atmMatrixTopNControlTimeRemaining OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create Bierman/McCloghrie Expires November 21, 1996 [Page 75] =0C Draft ATM-RMON MIB May 1996 STATUS current DESCRIPTION "The number of seconds left in the report currently being collected. When this object is modified by the management station, a new collection is started, possibly aborting a currently running report. The new value is used as the requested duration of this report, and is immediately loaded into the associated atmMatrixTopNControlDuration object. When the report finishes, the probe will automatically start another collection with the same initial value of atmMatrixTopNControlTimeRemaining. Thus the management station may simply read the resulting reports repeatedly, checking the startTime and duration each time to ensure that a report was not missed or that the report parameters were not changed. While the value of this object is non-zero, it decrements by one per second until it reaches zero. At the time that this object decrements to zero, the report is made accessible in the atmMatrixTopNTable, overwriting any report that may be there. When this object is modified by the management station, any associated entries in the atmMatrixTopNTable shall be deleted." DEFVAL { 1800 } ::=3D { atmMatrixTopNControlEntry 4 } atmMatrixTopNControlGeneratedReports OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of reports that have been generated by this entry." ::=3D { atmMatrixTopNControlEntry 5 } atmMatrixTopNControlDuration OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of seconds that this report has collected during Bierman/McCloghrie Expires November 21, 1996 [Page 76] =0C Draft ATM-RMON MIB May 1996 the last sampling interval. When the associated atmMatrixTopNControlTimeRemaining object is set, this object shall be set by the probe to the same value and shall not be modified until the next time the atmMatrixTopNControlTimeRemaining is set. This value shall be zero if no reports have been requested for this atmMatrixTopNControlEntry." ::=3D { atmMatrixTopNControlEntry 6 } atmMatrixTopNControlRequestedSize OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum number of host entries requested for this report. When this object is created or modified, the probe should set atmMatrixTopNControlGrantedSize as closely to this object as is possible for the particular probe implementation and available resources." DEFVAL { 150 } ::=3D { atmMatrixTopNControlEntry 7 } atmMatrixTopNControlGrantedSize OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of host entries in this report. When the associated atmMatrixTopNControlRequestedSize object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular implementation and available resources. The probe must not lower this value except as a result of a set to the associated atmMatrixTopNControlRequestedSize object. For example, if the value of atmMatrixTopNControlRateBase is equal to atmMatrixTopNCells(1), when the next topN report is generated, host entries with the highest value of Bierman/McCloghrie Expires November 21, 1996 [Page 77] =0C Draft ATM-RMON MIB May 1996 atmMatrixSDCells shall be placed in this table in decreasing order of this rate until there is no more room or until there are no more matrix entries. Each atmMatrixSDCells value is copied to the associated atmMatrixTopNRate object. It is an implementation-specific matter how entries with the same value are sorted. It is also an implementation- specific matter as to whether or not zero-valued entries are available." ::=3D { atmMatrixTopNControlEntry 8 } atmMatrixTopNControlStartTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime when this top N report was last started. In other words, this is the time that the associated atmMatrixTopNControlTimeRemaining object was modified to start the requested report or the time the report was last automatically (re)started. This object may be used by the management station to determine if a report was missed or not." ::=3D { atmMatrixTopNControlEntry 9 } atmMatrixTopNControlOwner OBJECT-TYPE SYNTAX OwnerString MAX-ACCESS read-create STATUS current DESCRIPTION "The entity that configured this entry and is therefore using the resources assigned to it." ::=3D { atmMatrixTopNControlEntry 10 } atmMatrixTopNControlStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this atmMatrixTopNControlEntry. Bierman/McCloghrie Expires November 21, 1996 [Page 78] =0C Draft ATM-RMON MIB May 1996 An entry may not exist in the active state unless all objects in the entry have an appropriate value. If this object is not equal to active(1), all associated entries in the atmMatrixTopNTable shall be deleted by the agent." ::=3D { atmMatrixTopNControlEntry 11 } Bierman/McCloghrie Expires November 21, 1996 [Page 79] =0C Draft ATM-RMON MIB May 1996 -- -- atmMatrixTopNTable -- atmMatrixTopNTable OBJECT-TYPE SYNTAX SEQUENCE OF AtmMatrixTopNEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A set of statistics for those matrix entries that have counted the highest number of cells, calls, or connection time." ::=3D { atmMatrix 5 } atmMatrixTopNEntry OBJECT-TYPE SYNTAX AtmMatrixTopNEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the atmMatrixTopNTable. The atmMatrixTopNControlIndex value in the index identifies the atmMatrixTopNControlEntry on whose behalf this entry was created. An example of the indexing of this table is atmMatrixTopNSrcAddress.1.3.10" INDEX { portSelGrpIndex, atmMatrixTopNControlIndex, atmMatrixTopNIndex } ::=3D { atmMatrixTopNTable 1 } AtmMatrixTopNEntry ::=3D SEQUENCE { atmMatrixTopNIndex Integer32, atmMatrixTopNSrcAddress AtmAddr, atmMatrixTopNDstAddress AtmAddr, atmMatrixTopNRate Integer32, atmMatrixTopNReverseRate Integer32 } atmMatrixTopNIndex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION Bierman/McCloghrie Expires November 21, 1996 [Page 80] =0C Draft ATM-RMON MIB May 1996 "An index that uniquely identifies an entry in the atmMatrixTopNTable among those in the same report. This index is between 1 and N, where N is the number of entries in this report. Each conversation in the selected atmMatrixSDTable, for the report interval, is ranked in descending order of the metric identified by the atmMatrixTopNRate object. For example, if the value of atmMatrixTopNControlRateBase is equal to atmMatrixTopNCells(1), increasing values of atmMatrixTopNIndex shall be assigned to entries with decreasing delta values of atmMatrixSDCells (for the report interval), until index N is assigned or there are no more atmMatrixSDEntries." ::=3D { atmMatrixTopNEntry 1 } atmMatrixTopNSrcAddress OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS read-only STATUS current DESCRIPTION "The ATM endpoint address identified as the source of the traffic measured in this report. Note that only the twenty octet length variant of the AtmAddr textual convention is allowed in this table." ::=3D { atmMatrixTopNEntry 2 } atmMatrixTopNDstAddress OBJECT-TYPE SYNTAX AtmAddr MAX-ACCESS read-only STATUS current DESCRIPTION "The ATM endpoint address identified as the destination of the traffic measured in this report. Note that only the twenty octet length variant of the AtmAddr textual convention is allowed in this table." ::=3D { atmMatrixTopNEntry 3 } atmMatrixTopNRate OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only Bierman/McCloghrie Expires November 21, 1996 [Page 81] =0C Draft ATM-RMON MIB May 1996 STATUS current DESCRIPTION "The value of the ranked metric for this conversation, for this report. If the associated value of atmMatrixTopNRateBase is equal to atmMatrixTopNCells(1), then this object is assigned the delta value of the atmMatrixSDCells object during this report interval. If the associated value of atmMatrixTopNRateBase is equal to atmMatrixTopNNumCallAttempts(2), then this object is assigned the delta value of the atmMatrixSDNumCallAttempts object during this report interval. If the associated value of atmMatrixTopNRateBase is equal to atmMatrixTopNNumCalls(3), then this object is assigned the delta value of the atmMatrixSDNumCalls object during this report interval. If the associated value of atmMatrixTopNRateBase is equal to atmMatrixTopNConnTime(4), then this object is assigned the delta value of the atmMatrixSDConnTime object during this report interval." ::=3D { atmMatrixTopNEntry 4 } atmMatrixTopNReverseRate OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The value of the associated metric for this conversation, and for this report, but for the reverse direction. For example, if the associated value of atmMatrixTopNRateBase is equal to atmMatrixTopNCells(1), then this object contains the atmMatrixSDCells delta cell rate for the reverse direction traffic (i.e. destination to source traffic)." ::=3D { atmMatrixTopNEntry 5 } Bierman/McCloghrie Expires November 21, 1996 [Page 82] =0C Draft ATM-RMON MIB May 1996 -- Conformance Macros atmRmonMIBCompliances OBJECT IDENTIFIER ::=3D { atmRmonConformance 1 } atmRmonMIBGroups OBJECT IDENTIFIER ::=3D { atmRmonConformance 2 } atmRmonMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Describes the requirements for conformance to the ATM-RMON MIB." MODULE -- this module MANDATORY-GROUPS { portSelectGroup, atmStatsGroup, atmHostGroup, atmMatrixGroup ::=3D { atmRmonMIBCompliances 1 } portSelectGroup OBJECT-GROUP OBJECTS { portSelGrpDescr, portSelGrpCreateTime, portSelGrpOwner, portSelGrpStatus, portSelCollectGroup, portSelFilterGroup, portSelCreateTime, portSelOwner, portSelStatus, addrFilterGrpAcceptType, addrFilterGrpCreateTime, addrFilterGrpOwner, addrFilterGrpStatus, addrFilterIfIndex, addrFilterPrefixData, addrFilterPrefixCareBits, addrFilterInclude, addrFilterScope, addrFilterCreateTime, addrFilterOwner, addrFilterStatus } STATUS current DESCRIPTION Bierman/McCloghrie Expires November 21, 1996 [Page 83] =0C Draft ATM-RMON MIB May 1996 "Selects the virtual circuits that should be monitored as part of a specific collection-group." ::=3D { atmRmonMIBGroups 1 } atmStatsGroup OBJECT-GROUP OBJECTS { atmStatsControlDropEvents, atmStatsControlOwner, atmStatsControlStatus, atmStatsCreateTime, atmStatsCells, atmStatsCellsRollovers, atmStatsNumCallAttempts, atmStatsNumCalls, atmStatsConnTime } STATUS current DESCRIPTION "Counts the basic statistics for collections on behalf of particular portSelectGroup collections." ::=3D { atmRmonMIBGroups 2 } atmStatsHCGroup OBJECT-GROUP OBJECTS { atmStatsHCCells } STATUS current DESCRIPTION "Counts the high capacity basic statistics for collections on behalf of particular portSelectGroup collections. The atmStatsGroup must be implemented if the atmStatsHCGroup is implemented. This group is mandatory for implementations which support high capacity counters." ::=3D { atmRmonMIBGroups 3 } atmHostGroup OBJECT-GROUP OBJECTS { atmHostControlInserts, atmHostControlDeletes, atmHostControlMaxDesiredEntries, atmHostControlPriority, atmHostControlCollectESI, Bierman/McCloghrie Expires November 21, 1996 [Page 84] =0C Draft ATM-RMON MIB May 1996 atmHostControlDropEvents, atmHostControlOwner, atmHostControlStatus, atmHostCreateTime, atmHostInCells, atmHostInCellsRollovers, atmHostOutCells, atmHostOutCellsRollovers, atmHostInNumCallAttempts, atmHostInNumCalls, atmHostOutNumCallAttempts, atmHostOutNumCalls, atmHostInConnTime, atmHostOutConnTime } STATUS current DESCRIPTION "Counts the amount of traffic sent from and to each ATM address discovered by the probe, on behalf of particular portSelectGroup collections." ::=3D { atmRmonMIBGroups 4 } atmHostHCGroup OBJECT-GROUP OBJECTS { atmHostInHCCells, atmHostOutHCCells } STATUS current DESCRIPTION "Counts the amount of traffic sent from and to each ATM address discovered by the probe, on behalf of particular portSelectGroup collections, using high-capacity counters. The atmHostGroup must be implemented if the atmHostHCGroup is implemented. This group is mandatory for implementations which support high capacity counters." ::=3D { atmRmonMIBGroups 5 } atmMatrixGroup OBJECT-GROUP OBJECTS { atmMatrixControlInserts, atmMatrixControlDeletes, atmMatrixControlMaxDesiredEntries, atmMatrixControlPriority, Bierman/McCloghrie Expires November 21, 1996 [Page 85] =0C Draft ATM-RMON MIB May 1996 atmMatrixControlCollectESIScope, atmMatrixControlDropEvents, atmMatrixControlOwner, atmMatrixControlStatus, atmMatrixSDCreateTime, atmMatrixSDCells, atmMatrixSDCellsRollovers, atmMatrixSDNumCallAttempts, atmMatrixSDNumCalls, atmMatrixSDConnTime, atmMatrixDSCreateTime, atmMatrixDSCells, atmMatrixDSCellsRollovers, atmMatrixDSNumCallAttempts, atmMatrixDSNumCalls, atmMatrixDSConnTime, atmMatrixTopNControlRateBase, atmMatrixTopNControlSClass, atmMatrixTopNControlTimeRemaining, atmMatrixTopNControlGeneratedReports, atmMatrixTopNControlDuration, atmMatrixTopNControlRequestedSize, atmMatrixTopNControlGrantedSize, atmMatrixTopNControlStartTime, atmMatrixTopNControlOwner, atmMatrixTopNControlStatus, atmMatrixTopNSrcAddress, atmMatrixTopNDstAddress, atmMatrixTopNRate, atmMatrixTopNReverseRate } STATUS current DESCRIPTION "Counts the amount of traffic sent between each pair of ATM addresses discovered by the probe, on behalf of particular portSelectGroup collections." ::=3D { atmRmonMIBGroups 6 } atmMatrixHCGroup OBJECT-GROUP OBJECTS { atmMatrixSDHCCells, atmMatrixDSHCCells } STATUS current Bierman/McCloghrie Expires November 21, 1996 [Page 86] =0C Draft ATM-RMON MIB May 1996 DESCRIPTION "Counts the amount of traffic sent between each pair of ATM addresses discovered by the probe, on behalf of particular portSelectGroup collections, using high capacity counters. The atmMatrixGroup must be implemented if the atmMatrixHCGroup is implemented. This group is mandatory for implementations which support high capacity counters." ::=3D { atmRmonMIBGroups 7 } END Bierman/McCloghrie Expires November 21, 1996 [Page 87] =0C Draft ATM-RMON MIB May 1996 6. Acknowledgements The authors wish to thank the following people for their comments and contributions in the development of this document: Ralph Beck Net2Net Corporation ralphb@net2net.com Robin A. Iddon AXON Networks, Inc. robini@axon.com Karen Sage NETSYS Technologies, Inc. karens@netsystech.com Anil Singhal Frontier Software Development, Inc. anil@frontier.com King Won Network General Corporation wonk@ngc.com Bierman/McCloghrie Expires November 21, 1996 [Page 88] =0C Draft ATM-RMON MIB May 1996 7. References [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996. [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991. [3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996. [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996. [6] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network Management Protocol", RFC 1157, SNMP Research, Performance Systems International, MIT Laboratory for Computer Science, May 1990. [7] S. Waldbusser, "Remote Network Monitoring MIB", RFC 1757, Carnegie Mellon University, February 1995. [8] S. Waldbusser, "Token Ring Extensions to the Remote Network Monitoring MIB", RFC 1513, Carnegie Mellon University, September 1993. [9] S. Waldbusser, "Remote Network Monitoring MIB (RMON-2)", draft- ietf-rmonmib-rmon2-03.txt, International Network Services, January 1996. [10] Bierman, A., Iddon, R., "RMON Protocol Identifiers", draft-ietf- rmonmib-rmonprot-01.txt, Bierman Consulting, AXON Networks, Inc., January 1996. [11] Ahmed, M., and K. Tesink, Editors, "Definitions of Managed Objects for ATM Management Version 8.0 using SMIv2", RFC 1695, Bell Bierman/McCloghrie Expires November 21, 1996 [Page 89] =0C Draft ATM-RMON MIB May 1996 Communications Research, August 1994. [12] Ly, F., Noto, M., Smith, A., Tesink, K., "Definitions of Supplemental Managed Objects for ATM Management", draft-ietf- atommib-atm2-05.txt, Bay Networks, Bell Communications Research, February 1996. [13] K. McCloghrie and F. Kastenholz, "Evolution of the Interfaces Group of MIB-II", RFC 1573. Network Information Center, SRI International, January, 1994. 8. Security Considerations Security issues are not discussed in this memo. 9. Authors' Addresses Andy Bierman Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 Phone: 408-527-3711 Email: abierman@cisco.com Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 Phone: 408-526-5260 Email: kzm@cisco.com Bierman/McCloghrie Expires November 21, 1996 [Page 90] =0C Draft ATM-RMON MIB May 1996 Table of Contents 1 Introduction .................................................... 2 2 The SNMP Network Management Framework ........................... 3 2.1 Object Definitions ............................................ 3 3 Overview ........................................................ 4 3.1 RMON Resource Sharing Model ................................... 4 3.2 Relationship to Existing MIBs ................................. 5 3.2.1 RMON ........................................................ 5 3.2.2 TR-RMON ..................................................... 6 3.2.3 RMON-2 MIB .................................................. 7 3.2.4 RMON-2 Protocol Identifiers ................................. 8 3.2.5 ATOM MIB .................................................... 8 3.2.6 ATOM Supplemental MIB ....................................... 8 3.3 ATM-RMON Functional Requirements .............................. 8 3.3.1 Physical Ports and Logical Ports ............................ 9 3.3.2 Address-Based vs. Non-Address-Based Traffic ................. 9 3.3.3 Cell-Level Filter and Capture ............................... 9 3.3.4 Collection Perspective ...................................... 10 3.3.5 Cell Collection Requirements ................................ 12 3.3.6 Frame Collection Requirements ............................... 13 3.4 ATM-RMON Design ............................................... 13 3.4.1 Switch Port Aggregation ..................................... 14 3.4.2 Data Reduction .............................................. 14 3.4.2.1 Pre-collection Data Reduction ............................. 15 3.4.2.2 Post-collection Data Reduction ............................ 15 3.4.3 Collection Source Identifier ................................ 15 4 MIB Proposal .................................................... 17 4.1 MIB Structure ................................................. 17 5 Definitions ..................................................... 20 6 Acknowledgements ................................................ 88 7 References ...................................................... 89 8 Security Considerations ......................................... 90 9 Authors' Addresses .............................................. 90 Bierman/McCloghrie Expires November 21, 1996 [Page 91] =0C --nVD6HXc3VDr28l5toaV01U2g7C1ZWya7--