Internet Draft Andy Bierman Cisco Systems, Inc. 10 March 2000 Application Performance Measurement Capabilities MIB Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 [RFC2026]. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Distribution of this document is unlimited. Please send comments to the authors. 1. Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. 2. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In Internet-Draft APM Capabilities MIB March 2000 particular, it describes managed objects used for classifying and characterizing the application performance measurement (APM) capabilities of various standard and proprietary APM techniques. 3. Table of Contents 1 Copyright Notice ................................................ 1 2 Abstract ........................................................ 1 3 Table of Contents ............................................... 2 4 The SNMP Management Framework ................................... 3 5 Overview ........................................................ 4 5.1 Terms ......................................................... 4 5.1.1 APM Data .................................................... 4 5.1.2 APM Device .................................................. 4 5.1.3 APM Collection Point ........................................ 4 5.1.4 APM Study Class ............................................. 5 5.1.5 APM Study ................................................... 5 5.1.6 APM Report Class ............................................ 5 5.1.7 APM Report .................................................. 6 5.1.8 APM Location ................................................ 6 5.1.9 APM Class ................................................... 6 5.2 Relationship to RMON-2 MIB .................................... 6 5.3 Relationship to IPPM .......................................... 6 5.4 Relationship to Other MIBs .................................... 7 6 APM Framework Components ........................................ 7 6.1 Performance Criteria .......................................... 7 6.2 Performance Measurement Granularity ........................... 7 6.3 Network Traffic Selection Criteria ............................ 7 6.4 Set of Metrics ................................................ 8 6.5 APM Study Class Capabilities .................................. 8 6.6 APM Collection Point Location ................................. 8 6.7 APM Study Configuration ....................................... 8 6.8 APM Study Results Storage and Retrieval ....................... 8 7 APM Caps MIB Groups ............................................. 9 7.1 APM Capabilities .............................................. 9 8 Definitions ..................................................... 9 9 Intellectual Property ........................................... 23 10 References ..................................................... 23 11 Security Considerations ........................................ 27 12 Author's Address ............................................... 28 13 Full Copyright Statement ....................................... 29 Expires September 2000 [Page 2] Internet-Draft APM Capabilities MIB March 2000 4. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [RFC2571]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in RFC 1155 [RFC1155], RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 [RFC2580]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905]. o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable Expires September 2000 [Page 3] Internet-Draft APM Capabilities MIB March 2000 information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 5. Overview There is a need for a standardized way of characterizing the measurement capabilities of tools which provide application performance data. There are many different techniques for measuring and characterizing the performance of specific network-based applications available at this time. A standardized framework for describing the capabilities of a particular technique is needed as a pre-requisite for a standardized APM results reporting framework. This memo addresses the specific requirements of the APM capabilities framework. Other aspects of APM, such as configuration and results reporting are not addressed in this memo. 5.1. Terms Some new terms are used throughout this document: 5.1.1. APM Data The actual measurements, kept in some internal representation, collected from one or more APM Collection Points. This data is converted into one or more APM Reports, in an implementation-specific manner. APM Data is outside the scope of the APM standard. 5.1.2. APM Device A device which contains an SNMP agent which implements the APM MIB. For the purpose of the standard, the APM device is the entity that is reporting the APM results, in the form of standard MIB objects. An APM Device can obtain APM data from one or more APM Collection Points. 5.1.3. APM Collection Point The general location, within the spectrum of possible vantage points, that APM Data is collected, for one or more APM Studies (and perhaps more than one APM device). The interaction between an APM device and an APM Collection Point is outside the scope of the APM standard. Expires September 2000 [Page 4] Internet-Draft APM Capabilities MIB March 2000 5.1.4. APM Study Class The unique set of mechanisms and parameters that classifies and identifies a particular APM collection capability. E.g., - the set of protocols collected - test attributes (standard and proprietary) - collection technique(s) - APM Collection Point information - report capabilities - vendor-specific Study Class ID 5.1.5. APM Study This is an instantiation of a particular APM Study Class. Some parameters, such as: - the dataSource to monitor - any resource restrictions to enforce - the specific set of result data to collect are relevant only in the context of an APM Study, not an APM Study Class. 5.1.6. APM Report Class The type of APM report produced on behalf of a particular APM Study Class. The group identified these distinct APM Report Classes: - distribution-based aggregation - statistica-based aggregation - exception-based reporting Expires September 2000 [Page 5] Internet-Draft APM Capabilities MIB March 2000 5.1.7. APM Report The set of result data for a particular APM Study. This is in the form of standard MIB objects and notifications in the APM MIB. 5.1.8. APM Location The notion of where an APM Collection Point is obtaining APM Data. At the highest level, the possible locations are: - client - network - server 5.1.9. APM Class At the highest level, there are three classes of APM technology. - passive collection No test traffic is introduced into the system being measured. APM Data is derived from observable 'user activity' in the actual operating environment. - active collection Some form of test traffic is introduced into the system being measured. APM Data is derived from measured attributes of this test traffic. - intrusive collection Actual network traffic is modified for the purpose of APM Data collection. APM Data is derived from measured attributes of this modified network traffic. 5.2. Relationship to RMON-2 MIB This MIB uses the protocolDirTable [RFC2021] to identify the protocols which are relevant to a particular APM Study Class. Implementation of the protocolDirectoryGroup is required. 5.3. Relationship to IPPM This MIB uses the Metric definitions found in IPPM documents ([RFC2330] [RFC2678] [RFC2679] [RFC2680] [RFC2681]) to identify the base metrics Expires September 2000 [Page 6] Internet-Draft APM Capabilities MIB March 2000 measured for a given APM Study Class. 5.4. Relationship to Other MIBs This MIB assumes that a standard Application Performance Measurement MIB (APM MIB) will be produced, which will provide support for basic configuration of an APM Study, as well as APM Report data. This MIB also assumes that a standard Transport Performance Measurement MIB (TPM MIB) will be produced, which will provide additional 'drill- down' support for transport layer protocols and additional metrics not directly supported by the APM MIB. 6. APM Framework Components An APM Study is executed and reported within the APM Framework. Usually, some sort of network infrastructure is assumed, in which client devices, application servers, forwarding devices, and one or more APM monitoring devices are connected. However, non-networking based methodologies can also be used. Some basic attributes of the APM Framework are listed below. 6.1. Performance Criteria A set of network, transport, and/or application performance criteria is needed, based on some combination of network traffic attributes. The specification and evaluation of performance test results is beyond the scope of this document. 6.2. Performance Measurement Granularity Each APM Study Class explicitly defines the granularity of the test, in terms of the purpose, selected metrics, and other attributes. 6.3. Network Traffic Selection Criteria For APM techniques which monitor or generate network traffic, a set of rules is needed which specifies which packets will be included in a particular performance test. This includes device attributes such as interface identity, and packet attributes such as VLAN ID, QoS value, IP subnet or host addresses, application type(s), and application payload. Expires September 2000 [Page 7] Internet-Draft APM Capabilities MIB March 2000 6.4. Set of Metrics For each APM Study Class, there are one or more metrics, appropriate for the associated network traffic and performance selection criteria, which are measured by the APM device(s) used for an individual APM Study. 6.5. APM Study Class Capabilities For each APM Study Class supported by an APM Device, there is a set of capabilities associated with the selected set of metrics and performance criteria. There is also a set of possible report output capabilities associated with each class. 6.6. APM Collection Point Location The physical location of each APM Collection Point is an important attribute of each APM Study Class. +------------+ +---------+ +----------+ +----------+ | | | Last | | Last Hop | | | | Client |<-->| Hop for |<--> ... <-->| for Net |<-->| Network | | | | Client | | Service | | Service | +------------+ +---------+ +----------+ +----------+ <------------- Measurement Device Location ------------> For the purposes of this MIB, an APM Collection Point resides in either the 'client', the 'network', or the 'server'. 6.7. APM Study Configuration Each APM Study may require some combination of generic and test-specific configuration commands in order to prepare the network environment for measurement. Specific APM Study configuration mechanisms are beyond the scope of this document. 6.8. APM Study Results Storage and Retrieval Each APM Device must be able to store the APM Reports generated on behalf of each APM Study, and convey these reports to a management application. The specification of these mechanisms are beyond the scope of this document. Expires September 2000 [Page 8] Internet-Draft APM Capabilities MIB March 2000 7. APM Caps MIB Groups The APM Caps MIB contains one MIB group. 7.1. APM Capabilities This group contains MIB objects used to report the capabilities of the APM Study Classes supported by a particular APM Device. 8. Definitions APMCAPS-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowPointer, TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF SnmpAdminString FROM SNMP-FRAMEWORK-MIB rmon FROM RMON-MIB protocolDirLocalIndex, protocolDirectoryGroup PROM RMON2-MIB; apmCapsMIB MODULE-IDENTITY LAST-UPDATED "200003100000Z" ORGANIZATION "IETF RMONMIB WG" CONTACT-INFO " E-mail: rmonmib@cisco.com Subscribe: majordomo@cisco.com w/ msg body: subscribe rmonmib Andy Bierman Cisco Systems Inc. 170 West Tasman Drive San Jose, CA 95134 +1 408-527-3711 abierman@cisco.com" DESCRIPTION "The MIB module for representing Application Performance Measurement Capabilities." REVISION "200003100000Z" Expires September 2000 [Page 9] Internet-Draft APM Capabilities MIB March 2000 DESCRIPTION "Initial Version of the APM Capabilities MIB." ::= { rmon xxx } apmCapsMIBObjects OBJECT IDENTIFIER ::= { apmCapsMIB 1 } apmCaps OBJECT IDENTIFIER ::= { apmCapsMIBObjects 1 } -- -- APM Metric Table -- apmMetricTable OBJECT-TYPE SYNTAX SEQUENCE OF ApmMetricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains one row per APM Metric supported by this APM Device, and should be populated during system initialization." ::= { apmCaps 1 } apmMetricEntry OBJECT-TYPE SYNTAX ApmMetricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a particular APM Metric." INDEX { apmMetricID } ::= { apmMetricTable 1 } ApmMetricEntry ::= SEQUENCE { apmMetricID OBJECT IDENTIFIER, apmMetricType INTEGER, apmMetricDirType INTEGER, apmMetricIsStandard TruthValue, apmMetricName SnmpAdminString, apmMetricReference SnmpAdminString } apmMetricID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS not-accessible STATUS current DESCRIPTION Expires September 2000 [Page 10] Internet-Draft APM Capabilities MIB March 2000 "The index for this entry. This object identifies the standard or vendor-specific registration OBJECT IDENTIFER defined for a particular APM metric." ::= { apmMetricEntry 1 } apmMetricType OBJECT-TYPE SYNTAX INTEGER { other(1), connectMetric(2), delayMetric(3), lossMetric(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The basic type of metric indicated by this entry. The value 'other(1)' indicates that this metric cannot be characterized by any of the remaining enumerations specified for this object. The value 'connectMetric(2)' indicates that this metric measures network connectivity characteristics. The value 'delayMetric(3)' indicates that this metric measures network delay characteristics. The value 'lossMetric(4)' indicates that this metric measures network loss characteristics." ::= { apmMetricEntry 2 } apmMetricDirType OBJECT-TYPE SYNTAX INTEGER { oneWay(1), twoWay(2), multiWay(3), } MAX-ACCESS read-only STATUS current DESCRIPTION "The directional characteristics of the this metric. The value 'oneWay(1)' indicates that this metric is measured with some sort of uni-directional test. Expires September 2000 [Page 11] Internet-Draft APM Capabilities MIB March 2000 The value 'twoWay(2)' indicates that this metric is measured with some sort of bi-directional test. The value 'multiWay(3)' indicates that this metric is measured with some combination of uni-directional and/or bi- directional tests." ::= { apmMetricEntry 3 } apmMetricIsStandard OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates whether this metric is defined in a document defined by a standards organization. The value 'true(1)' indicates that this is a standard metric. The corresponding value of the apmMetricReference object should identify this document. The value 'false(2)' indicates that this is a proprietary metric." ::= { apmMetricEntry 4 } apmMetricName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The textual name of this metric." ::= { apmMetricEntry 5 } apmMetricReference OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains a reference to the document which defines this metric. If this document is available online via electronic download, then a URL should be specified in this object. For example, if this apmMetricEntry identified the IPPM metric 'Type-P-Round-Trip-Delay', then this object should contain the value 'http://www.ietf.org/rfc/rfc2681.txt'." Expires September 2000 [Page 12] Internet-Draft APM Capabilities MIB March 2000 ::= { apmMetricEntry 6 } -- -- APM Study Class Table -- apmStudyClassTable OBJECT-TYPE SYNTAX SEQUENCE OF ApmStudyClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains one row per APM Study Class supported by this APM Device, and should be populated during system initialization." ::= { apmCaps 2 } apmStudyClassEntry OBJECT-TYPE SYNTAX ApmStudyClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a particular APM Study Class." INDEX { apmStudyClassID } ::= { apmStudyClassTable 1 } ApmStudyClassEntry ::= SEQUENCE { apmStudyClassID OBJECT IDENTIFIER, apmStudyClassCollectType BITS, apmStudyClassCollectPts Integer32, apmStudyClassCollectCaps BITS, apmStudyClassOutputCaps BITS, apmStudyClassCtlMibPtr OBJECT IDENTIFIER, apmStudyClassCtlTablePtr OBJECT IDENTIFIER, } apmStudyClassID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS not-accessible STATUS current DESCRIPTION "The index for this entry. This object identifier should specify the standard or vendor-specific registration OID for this APM Study Class." ::= { apmStudyClassEntry 1 } Expires September 2000 [Page 13] Internet-Draft APM Capabilities MIB March 2000 apmStudyClassCollectType OBJECT-TYPE SYNTAX BITS { apmPassiveClient(0), apmPassiveNet(1), apmPassiveServer(2), apmActiveClient(3), apmActiveNet(4), apmActiveServer(5), apmIntrusiveClient(6), apmIntrusiveNet(7), apmIntrusiveServer(8) } MAX-ACCESS read-only STATUS current DESCRIPTION "The type(s) of collection methodologies employed by this APM Study Class. If this APM Study class utilizes some sort of passive monitoring technology, which is located on the host machine being monitored, then the 'apmPassiveClient' BIT will be set. If this APM Study class utilizes some sort of passive monitoring technology which is located on one or more networking devices (e.g., routers, switches, RMON probes), then the 'apmPassiveNet' BIT will be set. If this APM Study class utilizes some sort of passive monitoring technology which is located on the machine(s) providing the network service being monitored, then the 'apmPassiveServer' BIT will be set. If this APM Study class utilizes some sort of active monitoring technology, which is located on a machine acting in the 'client role', then the 'apmActiveClient' BIT will be set. If this APM Study class utilizes some sort of active monitoring technology which is located on one or more networking devices (e.g., routers, switches, RMON probes), then the 'apmActiveNet' BIT will be set. If this APM Study class utilizes some sort of active monitoring technology which is located on a machine acting Expires September 2000 [Page 14] Internet-Draft APM Capabilities MIB March 2000 in the 'server role', then the 'apmActiveServer' BIT will be set. If this APM Study class utilizes some sort of intrusive monitoring technology, which is located on the host machine being monitored, then the 'apmIntrusiveClient' BIT will be set. If this APM Study class utilizes some sort of intrusive monitoring technology which is located on one or more networking devices (e.g., routers, switches, RMON probes), then the 'apmIntrusiveNet' BIT will be set. If this APM Study class utilizes some sort of intrusive monitoring technology which is located on the machine(s) providing the network service being monitored, then the 'apmIntrusiveServer' BIT will be set." ::= { apmStudyClassEntry 2 } apmStudyClassCollectPts OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of APM Collection Points utilized in this APM Study Class. If this is a variable quantity, then this object should contain the minimum number needed for this APM Study Class to function." ::= { apmStudyClassEntry 3 } apmStudyClassCollectCaps OBJECT-TYPE SYNTAX BITS { apmCollectMac(0), apmCollectNet(1), apmCollectTrans(2), apmCollectApp(3), apmCollectFlow(4), apmCollectNonNet(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies some generic characteristics of the collection methodologies employed by this APM Study Class. Expires September 2000 [Page 15] Internet-Draft APM Capabilities MIB March 2000 If this APM Study class utilizes some sort of MAC (and/or VLAN) layer APM Data collection technology, then the 'apmCollectMac' BIT will be set. If this APM Study class utilizes some sort of network layer APM Data collection technology, then the 'apmCollectNet' BIT will be set. If this APM Study class utilizes some sort of transport layer APM Data collection technology, then the 'apmCollectTrans' BIT will be set. If this APM Study class utilizes some sort of application layer APM Data collection technology, then the 'apmCollectApp' BIT will be set. If this APM Study class utilizes some sort of APM Data collection technology based on monitoring of some sort of network flow summary information, then the 'apmCollectFlow' BIT will be set. If this APM Study class utilizes some sort of APM Data collection technology based on monitoring of non-network events, such as UI monitoring of window events, then the 'apmCollectNonNet' BIT will be set." ::= { apmStudyClassEntry 4 } apmStudyClassOutputCaps OBJECT-TYPE SYNTAX BITS { apmOutputOther(0), apmOutputApmDist(1), apmOutputApmStat(2), apmOutputApmHist(3), apmOutputApmFlow(4), apmOutputApmExcept(5), apmOutputApmProp(6), apmOutputTpmDist(7), apmOutputTpmStat(8), apmOutputTpmHist(9), apmOutputTpmExcept(10), apmOutputTpmProp(11) } MAX-ACCESS read-only STATUS current DESCRIPTION Expires September 2000 [Page 16] Internet-Draft APM Capabilities MIB March 2000 "The type(s) of APM Reports that this APM Study Class can provide. If this APM Study class can generate standard reports not described by any of the provided BITS here, then the 'apmOutputOther' BIT will be set. If this APM Study class can generate distribution-oriented reports for application layer protocols, then the 'apmOutputApmDist' BIT will be set. If this APM Study class can generate statistics-oriented reports for application layer protocols, then the 'apmOutputApmStat' BIT will be set. If this APM Study class can generate historical analysis oriented reports for application layer protocols, then the 'apmOutputApmHist' BIT will be set. If this APM Study class can generate flow decomposition analysis oriented reports for application layer protocols, then the 'apmOutputApmFlow' BIT will be set. If this APM Study class can generate profile exception oriented reports for application layer protocols, then the 'apmOutputApmExcept' BIT will be set. If this APM Study class can generate vendor-specific proprietary reports for application layer protocols, in addition to standard reports, then the 'apmOutputApmProp' BIT will be set. If this APM Study class can generate distribution-oriented reports for transport layer protocols, then the 'apmOutputTpmDist' BIT will be set. If this APM Study class can generate statistics-oriented reports for transport layer protocols, then the 'apmOutputTpmStat' BIT will be set. If this APM Study class can generate historical analysis oriented reports for transport layer protocols, then the 'apmOutputTpmHist' BIT will be set. If this APM Study class can generate flow decomposition Expires September 2000 [Page 17] Internet-Draft APM Capabilities MIB March 2000 analysis oriented reports for transport layer protocols, then the 'apmOutputTpmFlow' BIT will be set. If this APM Study class can generate profile exception oriented reports for transport layer protocols, then the 'apmOutputTpmExcept' BIT will be set. If this APM Study class can generate vendor-specific proprietary reports for transport layer protocols, in addition to standard reports, then the 'apmOutputTpmProp' BIT will be set." ::= { apmStudyClassEntry 5 } apmStudyClassCtlMibPtr OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the MIB that can be used to configure detailed aspects of the collection or report processing functions for this APM Study Class. If such a MIB exists, then this object should contain the registration value specified in the MODULE-IDENTITY macro for that MIB. This object just identifies the MIB to use, not any particular agent which implements this MIB. This APM device may or may not contain an implementation of the specified MIB. If no appropriate MIB can be identified, then the value { 0 0 } is returned." ::= { apmStudyClassEntry 6 } apmStudyClassCtlTablePtr OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies a specific MIB table that can be used to configure detailed aspects of the collection or report processing functions for this APM Study Class. If such a MIB table exists, then this object should contain the registration value specified in the OBJECT-TYPE macro for the top-level MIB table definition. This MIB table must be within the MIB module specified by the associated apmStudyClassCtlMibPtr object. This object just identifies Expires September 2000 [Page 18] Internet-Draft APM Capabilities MIB March 2000 the MIB table to use, not any particular agent which implements this MIB table. This APM device may or may not contain an implementation of the specified MIB. If no appropriate MIB table can be identified, then the value { 0 0 } is returned." ::= { apmStudyClassEntry 7 } -- -- APM Study Metric Table -- apmStudyMetricTable OBJECT-TYPE SYNTAX SEQUENCE OF ApmStudyMetricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains one row for each metric supported by the specified APM Study Class, and should be populated during system initialization." ::= { apmCaps 3 } apmStudyMetricEntry OBJECT-TYPE SYNTAX ApmStudyMetricEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Metrics information related to a particular APM Study Class." INDEX { apmStudyClassID } ::= { apmStudyMetricTable 1 } ApmStudyMetricEntry ::= SEQUENCE { apmStudyMetricID OBJECT IDENTIFIER } apmStudyMetricID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the APM Metric associated with this APM Study, and contains the same value as the apmMetricID index for that apmMetricEntry." ::= { apmStudyMetricEntry 1 } Expires September 2000 [Page 19] Internet-Draft APM Capabilities MIB March 2000 -- -- APM Study Protocol Table -- apmStudyProtocolTable OBJECT-TYPE SYNTAX SEQUENCE OF ApmStudyProtocolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains one row for each protocol supported by the specified APM Study Class, and should be populated during system initialization. This is an indication of the protocols the indicated APM Study Class is capable of measuring. The actual protocols present in a given APM Study may be a subset of the protocols identified in this table. This table contain entries which reference any protocol in the protocolDirTable. If the index of this entry identifies an internal node in the protocolDirTable, then the apmStudyProtocolIsSubtree object is relevant." ::= { apmCaps 4 } apmStudyProtocolEntry OBJECT-TYPE SYNTAX ApmStudyProtocolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Protocol information about a particular APM Study." INDEX { apmStudyClassID, protocolDirLocalIndex } ::= { apmStudyProtocolTable 1 } ApmStudyProtocolEntry ::= SEQUENCE { apmStudyProtocolIsSubtree TruthValue } apmStudyProtocolIsSubtree OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates whether or not this entry identifies one node or an entire subtree of the protocolDirTable. If set to 'true(1)' then the specified protocolDirEntry, and Expires September 2000 [Page 20] Internet-Draft APM Capabilities MIB March 2000 all its children, are supported by the specified APM Study Class. If set to 'false(2)', then only the specified protocolDirEntry is supported by this APM Study Class." ::= { apmStudyProtocolEntry 1 } -- placeholder apmCapsNotifications OBJECT IDENTIFIER ::= { apmCapsMIB 2 } -- conformance information apmCapsConformance OBJECT IDENTIFIER ::= { apmCapsMIB 3 } apmCapsCompliances OBJECT IDENTIFIER ::= { apmCapsConformance 1 } apmCapsGroups OBJECT IDENTIFIER ::= { apmCapsConformance 2 } -- compliance statements apmCapsCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities which implement version 1 of the APM Capabilities MIB." MODULE -- this module MANDATORY-GROUPS { protocolDirectoryGroup, apmCapsGroup } ::= { apmCapsCompliances 1 } -- MIB groupings apmCapsGroup OBJECT-GROUP OBJECTS { apmMetricType, apmMetricDirType, apmMetricIsStandard, apmMetricName, apmMetricReference, apmStudyClassCollectType, apmStudyClassCollectPts, apmStudyClassCollectCaps, apmStudyClassOutputCaps, apmStudyClassCtlMibPtr, apmStudyClassCtlTablePtr, apmStudyMetricID, Expires September 2000 [Page 21] Internet-Draft APM Capabilities MIB March 2000 apmStudyProtocolIsSubtree } STATUS current DESCRIPTION "The collection of objects which are used to represent application performance measurement capabilities, for which a single agent provides management information." ::= { apmCapsGroups 1 } END Expires September 2000 [Page 22] Internet-Draft APM Capabilities MIB March 2000 9. Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards- related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 10. References [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", RFC 1155, STD 16, Performance Systems International, Hughes LAN Systems, May 1990. [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, STD 15, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990. [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, STD 16, Performance Systems International, Hughes LAN Systems, March 1991. [RFC1215] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, Performance Systems International, March 1991. Expires September 2000 [Page 23] Internet-Draft APM Capabilities MIB March 2000 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International Network Services, January 1996. [RFC2021] S. Waldbusser, "Remote Network Monitoring MIB (RMON-2)", RFC 2021, International Network Services, January 1997. [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", RFC 2026, Harvard University, October, 1996. [RFC2330] Paxson, V., Almes, G., Mahdavi, J. and M. Mathis, "Framework for IP Performance Metrics", RFC 2330, May 1998. [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc., Ericsson, Cisco Systems, April 1999. [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, Cabletron Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. Expires September 2000 [Page 24] Internet-Draft APM Capabilities MIB March 2000 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999. [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, April 1999. [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, IBM T. J. Watson Research, April 1999. [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., Cisco Systems, Inc., April 1999. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First Virtual Holdings, International Network Services, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First Virtual Holdings, International Network Services, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First Virtual Holdings, International Network Services, April 1999. [RFC2678] Mahdavi, J., and V. Paxson, "IPPM Metrics for Measuring Connectivity", RFC 2678, September 1999. Expires September 2000 [Page 25] Internet-Draft APM Capabilities MIB March 2000 [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, A One-Way Delay Metric for IPPM", RFC 2679, September 1999. [RFC2680] Almes, G., Kalidindi, S., and M. Zekauskas, A One-Way Packet Loss Metric for IPPM", RFC 2680, September 1999. [RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip Delay Metric for IPPM", RFC 2681, September 1999. Expires September 2000 [Page 26] Internet-Draft APM Capabilities MIB March 2000 11. Security Considerations There are no management objects defined in this MIB that have a MAX- ACCESS clause of read-write and/or read-create. So, if this MIB is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB via direct SNMP SET operations. SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User- based Security Model RFC 2574 [RFC2574] and the View- based Access Control Model RFC 2575 [RFC2575] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. Expires September 2000 [Page 27] Internet-Draft APM Capabilities MIB March 2000 12. Author's Address Andy Bierman Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134 USA Phone: +1 408-527-3711 Email: abierman@cisco.com Expires September 2000 [Page 28] Internet-Draft APM Capabilities MIB March 2000 13. Full Copyright Statement Copyright (C) The Internet Society (2000). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Expires September 2000 [Page 29]