smilint output for ./PMCAPS-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| severe | 1 |
| Message Types |
|---|
| Type | Count |
|---|
| internal-other (severe) | 1 |
Messages:
PMCAPS-MIB
1: -- extracted from draft-ietf-rmonmib-pmcaps-01.txt
2: -- at Sat Jul 22 07:08:03 2000
3:
4: PMCAPS-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Integer32
8: FROM SNMPv2-SMI
9: TruthValue, RowPointer
10: FROM SNMPv2-TC
11: MODULE-COMPLIANCE, OBJECT-GROUP
12: FROM SNMPv2-CONF
13: SnmpAdminString
14: FROM SNMP-FRAMEWORK-MIB
15: rmon
16: FROM RMON-MIB
17: protocolDirLocalIndex, protocolDirectoryGroup
18: PROM RMON2-MIB;
18: severe -
syntax error, unexpected UPPERCASE_IDENTIFIER, expecting FROM or ','
19:
20: pmCapsMIB MODULE-IDENTITY
21: LAST-UPDATED "200007140000Z"
22: ORGANIZATION "IETF RMONMIB WG"
23: CONTACT-INFO
24: " Andy Bierman
25: Cisco Systems, Inc.
26: RMONMIB WG Chair and PMCAPS MIB Editor
27:
28: Postal: 170 West Tasman Drive
29: San Jose, CA USA 95134
30: Tel: +1 408 527-3711
31: E-mail: abierman@cisco.com
32:
33: Send comments to <rmonmib@ietf.org>
34: Mailing list subscription information:
35: http://www.ietf.org/mailman/listinfo/rmonmib "
36: DESCRIPTION
37: "The MIB module for representing Performance
38: Measurement Capabilities."
39: REVISION "200007140000Z"
40: DESCRIPTION
41: "Initial Version of the Performance Measurement
42: Capabilities MIB."
43: ::= { rmon 25 }
44:
45:
46: pmCapsMIBObjects OBJECT IDENTIFIER ::= { pmCapsMIB 1 }
47: pmCaps OBJECT IDENTIFIER ::= { pmCapsMIBObjects 1 }
48: pmMetrics OBJECT IDENTIFIER ::= { pmCapsMIBObjects 2 }
49:
50: --
51: -- PM Metric Table
52: --
53: pmMetricTable OBJECT-TYPE
54: SYNTAX SEQUENCE OF PmMetricEntry
55: MAX-ACCESS not-accessible
56: STATUS current
57: DESCRIPTION
58: "This table contains one row per PM Metric supported by this
59: agent, and should be populated during system
60: initialization."
61: ::= { pmCaps 1 }
62:
63: pmMetricEntry OBJECT-TYPE
64: SYNTAX PmMetricEntry
65: MAX-ACCESS not-accessible
66: STATUS current
67: DESCRIPTION
68: "Information about a particular PM Metric."
69: INDEX { pmMetricID }
70: ::= { pmMetricTable 1 }
71:
72: PmMetricEntry ::= SEQUENCE {
73: pmMetricID OBJECT IDENTIFIER,
74: pmMetricType INTEGER,
75: pmMetricDirType INTEGER,
76: pmMetricName SnmpAdminString,
77: pmMetricReference SnmpAdminString
78: }
79:
80: pmMetricID OBJECT-TYPE
81: SYNTAX OBJECT IDENTIFIER
82: MAX-ACCESS not-accessible
83: STATUS current
84: DESCRIPTION
85: "The index for this entry. This object identifies the
86: standard or vendor-specific registration OBJECT IDENTIFER
87: defined for a particular PM metric."
88: ::= { pmMetricEntry 1 }
89:
90: pmMetricType OBJECT-TYPE
91: SYNTAX INTEGER {
92: other(1),
93: connectMetric(2),
94: delayMetric(3),
95: lossMetric(4)
96: }
97: MAX-ACCESS read-only
98: STATUS current
99: DESCRIPTION
100: "The basic type of metric indicated by this entry.
101:
102: The value 'other(1)' indicates that this metric cannot be
103: characterized by any of the remaining enumerations specified
104: for this object.
105:
106: The value 'connectMetric(2)' indicates that this metric
107: measures connectivity characteristics.
108:
109: The value 'delayMetric(3)' indicates that this metric
110: measures delay characteristics.
111:
112: The value 'lossMetric(4)' indicates that this metric
113: measures loss characteristics."
114: ::= { pmMetricEntry 2 }
115:
116: pmMetricDirType OBJECT-TYPE
117: SYNTAX INTEGER {
118: oneWay(1),
119: twoWay(2),
120: multiWay(3)
121: }
122: MAX-ACCESS read-only
123: STATUS current
124: DESCRIPTION
125: "The directional characteristics of the this metric.
126:
127: The value 'oneWay(1)' indicates that this metric is measured
128: with some sort of uni-directional test.
129:
130: The value 'twoWay(2)' indicates that this metric is measured
131: with some sort of bi-directional test.
132:
133: The value 'multiWay(3)' indicates that this metric is
134: measured with some combination of uni-directional and/or bi-
135: directional tests."
136: ::= { pmMetricEntry 3 }
137:
138: pmMetricName OBJECT-TYPE
139: SYNTAX SnmpAdminString
140: MAX-ACCESS read-only
141: STATUS current
142: DESCRIPTION
143: "The textual name of this metric."
144: ::= { pmMetricEntry 4 }
145:
146: pmMetricReference OBJECT-TYPE
147: SYNTAX SnmpAdminString
148: MAX-ACCESS read-only
149: STATUS current
150: DESCRIPTION
151: "This object contains a reference to the document which
152: defines this metric. If this document is available online
153: via electronic download, then a URL should be specified in
154: this object.
155:
156: For example, if this pmMetricEntry identified the IPPM
157: metric 'Type-P-Round-Trip-Delay', then this object should
158: contain the value 'http://www.ietf.org/rfc/rfc2681.txt'."
159: ::= { pmMetricEntry 5 }
160:
161:
162: --
163: -- PM Study Class Table
164: --
165:
166: pmStudyClassTable OBJECT-TYPE
167: SYNTAX SEQUENCE OF PmStudyClassEntry
168: MAX-ACCESS not-accessible
169: STATUS current
170: DESCRIPTION
171: "This table contains one row per PM Study Class supported by
172: this APM/TPM Device, and should be populated during system
173: initialization."
174: ::= { pmCaps 2 }
175:
176: pmStudyClassEntry OBJECT-TYPE
177: SYNTAX PmStudyClassEntry
178: MAX-ACCESS not-accessible
179: STATUS current
180: DESCRIPTION
181: "Information about a particular PM Study Class."
182: INDEX { pmStudyClassID }
183: ::= { pmStudyClassTable 1 }
184:
185: PmStudyClassEntry ::= SEQUENCE {
186: pmStudyClassID OBJECT IDENTIFIER,
187: pmStudyClassMeasLoc BITS,
188: pmStudyClassMeasType BITS,
189: pmStudyClassCollectPts Integer32,
190: pmStudyClassCollectCaps BITS,
191: pmStudyClassOutputCaps BITS,
192: pmStudyClassCtlTablePtr RowPointer
193: }
194:
195: pmStudyClassID OBJECT-TYPE
196: SYNTAX OBJECT IDENTIFIER
197: MAX-ACCESS not-accessible
198: STATUS current
199: DESCRIPTION
200: "The index for this entry. This object identifier should
201: specify the standard or vendor-specific registration OID for
202: this PM Study Class."
203: ::= { pmStudyClassEntry 1 }
204:
205: pmStudyClassMeasLoc OBJECT-TYPE
206: SYNTAX BITS {
207: pmClient(0),
208: pmNetwork(1),
209: pmServer(2)
210: }
211: MAX-ACCESS read-only
212: STATUS current
213: DESCRIPTION
214: "The measurement location characteristics of the PM Data
215: collection methodologies employed by this PM Study Class.
216:
217: If this PM Study class utilizes some sort of measurement
218: technology located on the host machine being monitored, then
219: the 'pmClient' BIT will be set. Note that this bit should
220: only be set if any PM technology is installed on the client,
221: in addition to the 'normal' protocol operations supported by
222: that machine.
223:
224: If this PM Study class utilizes some sort of measurement
225: technology located on one or more networking devices (e.g.,
226: routers, switches, RMON probes), then the 'pmNetwork' BIT
227: will be set.
228:
229: If this PM Study class utilizes some sort of measurement
230: technology located on the application server being
231: monitored, then the 'pmServer' BIT will be set. Note that
232: this bit should only be set if any PM technology is
233: installed on the server, in addition to the 'normal'
234: protocol operations supported by that machine."
235: ::= { pmStudyClassEntry 2 }
236:
237: pmStudyClassMeasType OBJECT-TYPE
238: SYNTAX BITS {
239: pmPassive(0),
240: pmActive(1),
241: pmBuiltin(2)
242: }
243: MAX-ACCESS read-only
244: STATUS current
245: DESCRIPTION
246: "The type(s) of collection methodologies employed by this PM
247: Study Class.
248:
249: If this PM Study class utilizes some sort of passive
250: monitoring technology, (i.e., UI operations and/or protocol
251: transactions of real users are measured) the 'pmPassive' BIT
252: will be set.
253:
254: If this PM Study class utilizes some sort of active
255: monitoring technology, (i.e., protocol transactions
256: generated for the purpose of obtaining PM Data) the
257: 'pmPassive' BIT will be set.
258:
259: If this PM Study class utilizes some sort of built-in
260: monitoring technology, (i.e., UI operations and/or protocol
261: transactions of real users are somehow altered to provide PM
262: Data) the 'pmBuiltin' BIT will be set."
263: ::= { pmStudyClassEntry 3 }
264:
265: pmStudyClassCollectPts OBJECT-TYPE
266: SYNTAX Integer32 (1..2147483647)
267: MAX-ACCESS read-only
268: STATUS current
269: DESCRIPTION
270: "The number of PM Collection Points utilized in this PM
271: Study Class. If this is a variable quantity, then this
272: object should contain the minimum number needed for this PM
273: Study Class to function."
274: ::= { pmStudyClassEntry 4 }
275:
276: pmStudyClassCollectCaps OBJECT-TYPE
277: SYNTAX BITS {
278: pmCollectTrans(0),
279: pmCollectApp(1),
280: pmCollectFlow(2),
281: pmCollectNonNet(3)
282: }
283: MAX-ACCESS read-only
284: STATUS current
285: DESCRIPTION
286: "This object identifies some generic characteristics of the
287: collection methodologies employed by this PM Study Class.
288:
289: If this PM Study class utilizes some sort of transport layer
290: PM Data collection technology, then the 'pmCollectTrans' BIT
291: will be set.
292:
293: If this PM Study class utilizes some sort of application
294: layer PM Data collection technology, then the 'pmCollectApp'
295: BIT will be set.
296:
297: If this PM Study class utilizes PM Data collection
298: technology based on monitoring of some sort of network flow
299: summary information, then the 'pmCollectFlow' BIT will be
300: set.
301:
302: If this PM Study class utilizes some sort of PM Data
303: collection technology based on monitoring of non-network
304: events, such as UI monitoring of window events, then the
305: 'pmCollectNonNet' BIT will be set."
306: ::= { pmStudyClassEntry 5 }
307:
308: pmStudyClassOutputCaps OBJECT-TYPE
309: SYNTAX BITS {
310: pmOutputOther(0),
311: pmOutputApmDist(1),
312: pmOutputApmStat(2),
313: pmOutputApmHist(3),
314: pmOutputApmFlow(4),
315: pmOutputApmExcept(5),
316: pmOutputApmProp(6),
317: pmOutputTpmDist(7),
318: pmOutputTpmStat(8),
319: pmOutputTpmHist(9),
320: pmOutputTpmExcept(10),
321: pmOutputTpmProp(11)
322: }
323: MAX-ACCESS read-only
324: STATUS current
325: DESCRIPTION
326: "The type(s) of APM and/or TPM Reports that this PM Study
327: Class can provide. [ed. - this list will change as the APM
328: and TPM MIBs are finalized.]
329:
330: If this PM Study class can generate standard reports not
331: described by any of the provided BITS here, then the
332: 'pmOutputOther' BIT will be set.
333:
334: If this PM Study class can generate distribution-oriented
335: reports for application layer protocols, then the
336: 'pmOutputApmDist' BIT will be set.
337:
338: If this PM Study class can generate statistics-oriented
339: reports for application layer protocols, then the
340: 'pmOutputApmStat' BIT will be set.
341:
342: If this PM Study class can generate historical analysis
343: oriented reports for application layer protocols, then the
344: 'pmOutputApmHist' BIT will be set.
345:
346: If this PM Study class can generate flow decomposition
347: analysis oriented reports for application layer protocols,
348: then the 'pmOutputApmFlow' BIT will be set.
349:
350: If this PM Study class can generate profile exception
351: oriented reports for application layer protocols, then the
352: 'pmOutputApmExcept' BIT will be set.
353:
354: If this PM Study class can generate vendor-specific
355: proprietary reports for application layer protocols, in
356: addition to standard reports, then the 'pmOutputApmProp' BIT
357: will be set.
358:
359: If this PM Study class can generate distribution-oriented
360: reports for transport layer protocols, then the
361: 'pmOutputTpmDist' BIT will be set.
362:
363: If this PM Study class can generate statistics-oriented
364: reports for transport layer protocols, then the
365: 'pmOutputTpmStat' BIT will be set.
366:
367: If this PM Study class can generate historical analysis
368: oriented reports for transport layer protocols, then the
369: 'pmOutputTpmHist' BIT will be set.
370:
371: If this PM Study class can generate flow decomposition
372: analysis oriented reports for transport layer protocols,
373: then the 'pmOutputTpmFlow' BIT will be set.
374:
375: If this PM Study class can generate profile exception
376: oriented reports for transport layer protocols, then the
377: 'pmOutputTpmExcept' BIT will be set.
378:
379: If this PM Study class can generate vendor-specific
380: proprietary reports for transport layer protocols, in
381: addition to standard reports, then the 'pmOutputTpmProp' BIT
382: will be set."
383: ::= { pmStudyClassEntry 6 }
384:
385: pmStudyClassCtlTablePtr OBJECT-TYPE
386: SYNTAX RowPointer
387: MAX-ACCESS read-only
388: STATUS current
389: DESCRIPTION
390: "This object identifies a specific MIB table that can be
391: used to configure detailed aspects of the collection or
392: report processing functions for this PM Study Class.
393:
394: This object just identifies a particular row in the MIB
395: table to use, not any particular agent which implements this
396: MIB table. This agent may or may not contain an
397: implementation of the specified MIB, and/or the specified
398: MIB may not be accessible in the same views as the this MIB.
399:
400: If no appropriate row in a MIB table can be identified, then
401: the value { 0 0 } is returned."
402: ::= { pmStudyClassEntry 7 }
403:
404:
405: --
406: -- PM Study Metric Table
407: --
408: pmStudyMetricTable OBJECT-TYPE
409: SYNTAX SEQUENCE OF PmStudyMetricEntry
410: MAX-ACCESS not-accessible
411: STATUS current
412: DESCRIPTION
413: "This table contains one row for each metric supported by
414: the specified PM Study Class, and should be populated during
415: system initialization."
416: ::= { pmCaps 3 }
417:
418: pmStudyMetricEntry OBJECT-TYPE
419: SYNTAX PmStudyMetricEntry
420: MAX-ACCESS not-accessible
421: STATUS current
422: DESCRIPTION
423: "Metrics information related to a particular PM Study Class.
424:
425: The pmStudyClassID value in the index identifies the
426: pmStudyClassEntry with the same index value."
427: INDEX { pmStudyClassID }
428: ::= { pmStudyMetricTable 1 }
429:
430: PmStudyMetricEntry ::= SEQUENCE {
431: pmStudyMetricID OBJECT IDENTIFIER
432: }
433:
434: pmStudyMetricID OBJECT-TYPE
435: SYNTAX OBJECT IDENTIFIER
436: MAX-ACCESS read-only
437: STATUS current
438: DESCRIPTION
439: "This object identifies the PM Metric associated with this
440: PM Study, and contains the same value as the pmMetricID
441: index for that pmMetricEntry."
442: ::= { pmStudyMetricEntry 1 }
443:
444:
445: --
446: -- PM Study Protocol Table
447: --
448:
449: pmStudyProtocolTable OBJECT-TYPE
450: SYNTAX SEQUENCE OF PmStudyProtocolEntry
451: MAX-ACCESS not-accessible
452: STATUS current
453: DESCRIPTION
454: "This table contains one row for each protocol supported by
455: the specified PM Study Class, and should be populated during
456: system initialization.
457: This is an indication of the protocols the indicated PM
458: Study Class is capable of measuring. The actual protocols
459: present in a given APM or TPM Report may be a subset of the
460: protocols identified in this table.
461:
462: This table contain entries which reference any protocol in
463: the protocolDirTable. If the index of this entry identifies
464: an internal node in the protocolDirTable, then the
465: pmStudyProtocolIsSubtree object is relevant."
466: ::= { pmCaps 4 }
467:
468: pmStudyProtocolEntry OBJECT-TYPE
469: SYNTAX PmStudyProtocolEntry
470: MAX-ACCESS not-accessible
471: STATUS current
472: DESCRIPTION
473: "Protocol information about a particular PM Study Class.
474:
475: The pmStudyClassID value in the index identifies the
476: pmStudyClassEntry with the same index value, associated with
477: the list of protocols in this table.
478:
479: The protocolDirLocalIndex value identifies the
480: protocolDirEntry which contains the same value in the
481: protocolDirLocalIndex object."
482: INDEX { pmStudyClassID, protocolDirLocalIndex }
483: ::= { pmStudyProtocolTable 1 }
484:
485: PmStudyProtocolEntry ::= SEQUENCE {
486: pmStudyProtocolIsSubtree TruthValue
487: }
488:
489: pmStudyProtocolIsSubtree OBJECT-TYPE
490: SYNTAX TruthValue
491: MAX-ACCESS read-only
492: STATUS current
493: DESCRIPTION
494: "This object indicates whether or not this entry identifies
495: one node or an entire subtree of the protocolDirTable.
496:
497: If set to 'true(1)' then the specified protocolDirEntry, and
498: all its children, are supported by the specified PM Study
499: Class.
500:
501: If set to 'false(2)', then the specified protocolDirEntry
502: identified by this entry is supported by the PM Study
503: Class."
504: ::= { pmStudyProtocolEntry 1 }
505:
506:
507: --
508: -- APM Metric Registry
509: --
510:
511: -- APM Avaiability Metric for all transaction types
512: pmAppAvailMetric OBJECT-IDENTITY
513: STATUS current
514: DESCRIPTION
515: "Metric Name:
516: Type-P-APM-Availability
517:
518: Metric Definition:
519: This metric characterizes the availability of a
520: network service by measuring the percentage of
521: successful transactions the network service
522: delivers over a given time interval.
523:
524: This metric is calculated by first measuring
525: the IPPM metric
526: 'Type-P-Interval-Bidirectional-Connectivity'
527: for the interval starting at the instant 'Src'
528: initiates a transaction of Type-P with the 'Dst'
529: host, and ending at the instant the last packet
530: of the transaction has been received. In addition to
531: successful connectivity over this interval, the
532: particular application request must also succeed,
533: for a transaction to be considered successful.
534: If either condition is false, then that transaction
535: is considered to be unsuccessful.
536:
537: The derived metric is defined as the total number
538: of successful transactions between Src and Dst,
539: divided by the total number of transaction attempts
540: between Src and Dst, during the time interval dT.
541:
542: Metric Parameters:
543: Src, the network address of a host
544: Dst, the network address of a host
545: dT, a time interval
546:
547: Metric Units:
548: Percentage
549:
550: Mapping of Type P:
551: Type P refers to an application protocol
552: encapsulation, identified by a specific
553: protocolDirEntry.
554:
555: Metric Type: connectMetric(1)
556: Metric Dir Type: twoWay(2)"
557: REFERENCE
558: "IPPM Metrics for Measuring Connectivity, RFC 2678
559: [RFC2678], Section 5, September 1999."
560: ::= { pmMetrics 1 }
561:
562: -- APM Responsiveness Metric for Transaction-oriented applications
563: pmAppTransRespMetric OBJECT-IDENTITY
564: STATUS current
565: DESCRIPTION
566: "Metric Name:
567: Type-P-APM-Transaction-Responsiveness
568:
569: Metric Definition:
570: This metric characterizes the speed at which a
571: transaction-oriented network application delivers
572: a requested service, by measuring the speed of
573: individual application transactions.
574:
575: This metric is calculated by utilizing a variation of
576: the IPPM metric 'Type-P-Round-trip-Delay'. The
577: total transaction time (dT) is determined by summing
578: all the packet transactions of Type-P between the
579: Src and Dst hosts. The bi-directional flight times
580: are measured (as specified by the IPPM metric definition),
581: but the server response time for each request is included
582: in the measurement.
583:
584: The derived metric is defined as the total number
585: of tenths of seconds for the transaction between
586: Src and Dst to complete.
587:
588: Metric Parameters:
589: Src, the network address of a host
590: Dst, the network address of a host
591: dT, a time interval
592:
593: Metric Units:
594: Tenths of seconds
595:
596: Mapping of Type P:
597: Type P refers to an application protocol
598: encapsulation, identified by a specific
599: protocolDirEntry, which is characterized
600: as a transaction-oriented protocol.
601:
602: Metric Type: delayMetric(2)
603: Metric Dir Type: twoWay(2)"
604: REFERENCE
605: "Round-trip for Delay Metric for IPPM, RFC 2681 [RFC2681],
606: Section 2, September 1999."
607: ::= { pmMetrics 2 }
608:
609: -- APM Responsiveness Metric for Throughput-oriented applications
610: -- [ed., in progress]
611: pmAppTputRespMetric OBJECT-IDENTITY
612: STATUS current
613: DESCRIPTION
614: "Metric Name:
615: Type-P-APM-Throughput-Responsiveness
616:
617: Metric Definition:
618: This metric characterizes the speed at which a
619: throughput-oriented network application delivers
620: a requested service, by measuring the transfer rate
621: of individual application transactions.
622:
623: This metric is calculated by ... [rest of para is TBD]
624:
625: The derived metric is normalized and inverted, into
626: units of 'seconds per terabit'. For transactions
627: up to one terabit in size, it is defined as the
628: total number of seconds it would take for the
629: transaction between Src and Dst to complete, if
630: the transaction size included one terabit of data.
631: For transactions over one terabit in size, it
632: is defined as the average number of seconds for the
633: transaction between Src and Dst to complete, for
634: each terabit of data.
635:
636: E.g., a transfer rate of 2Kbps equals 500,000,000 and
637: a transfer rate of 1Gbps = 1000.
638:
639: Metric Parameters:
640: Src, the network address of a host
641: Dst, the network address of a host
642: dT, a time interval
643: B, a number of terabits
644:
645: Metric Units:
646: Seconds Per Terabit
647:
648: Mapping of Type P:
649: Type P refers to an application protocol
650: encapsulation, identified by a specific
651: protocolDirEntry, which is characterized
652: as a throughput-oriented protocol.
653:
654: Metric Type: delayMetric(2)
655: Metric Dir Type: twoWay(2)"
656: REFERENCE
657: "Round-trip for Delay Metric for IPPM, RFC 2681 [RFC2681],
658: Section 2, September 1999."
659: ::= { pmMetrics 3 }
660:
661: -- APM Responsiveness Metric for Stream-oriented applications
662: -- [ed., in progress]
663: pmAppStreamRespMetric OBJECT-IDENTITY
664: STATUS current
665: DESCRIPTION
666: "Metric Name:
667: Type-P-APM-Stream-Responsiveness
668:
669: Metric Definition:
670: This metric characterizes the 'quality' at which a
671: streaming-oriented network application delivers
672: a requested service, by measuring the percentage
673: of time that the service is degraded or interrupted
674: to the total time to deliver the service.
675:
676: [Rest of definition TBD]
677:
678: Metric Parameters:
679: Src, the network address of a host
680: Dst, the network address of a host
681:
682: Metric Units:
683: [TBD]
684:
685: Mapping of Type P:
686: Type P refers to an application protocol
687: encapsulation, identified by a specific
688: protocolDirEntry, which is characterized
689: as a streaming-oriented protocol.
690:
691: Metric Type: delayMetric(2)
692: Metric Dir Type: twoWay(2)"
693: REFERENCE
694: "Round-trip for Delay Metric for IPPM, RFC 2681 [RFC2681],
695: Section 2, September 1999."
696: ::= { pmMetrics 4 }
697:
698: --
699: -- TPM Metric Registry [TBD]
700: --
701:
702:
703: -- placeholder for notifications
704: pmCapsNotifications OBJECT IDENTIFIER ::= { pmCapsMIB 2 }
705:
706: -- conformance information
707: pmCapsConformance OBJECT IDENTIFIER ::= { pmCapsMIB 3 }
708:
709: pmCapsCompliances OBJECT IDENTIFIER ::= { pmCapsConformance 1 }
710: pmCapsGroups OBJECT IDENTIFIER ::= { pmCapsConformance 2 }
711:
712:
713: -- compliance statements
714: pmCapsCompliance MODULE-COMPLIANCE
715: STATUS current
716: DESCRIPTION
717: "The compliance statement for SNMP entities which implement
718: version 1 of the APM Capabilities MIB."
719: MODULE -- this module
720: MANDATORY-GROUPS {
721: protocolDirectoryGroup,
722: pmCapsGroup
723: }
724: ::= { pmCapsCompliances 1 }
725:
726:
727: -- MIB groupings
728: pmCapsGroup OBJECT-GROUP
729: OBJECTS {
730: pmMetricType,
731: pmMetricDirType,
732: pmMetricName,
733: pmMetricReference,
734: pmStudyClassMeasLoc,
735: pmStudyClassMeasType,
736: pmStudyClassCollectPts,
737: pmStudyClassCollectCaps,
738: pmStudyClassOutputCaps,
739: pmStudyClassCtlTablePtr,
740: pmStudyMetricID,
741: pmStudyProtocolIsSubtree
742: }
743: STATUS current
744: DESCRIPTION
745: "The collection of objects which are used to represent
746: application performance measurement capabilities, for which
747: a single agent provides management information."
748: ::= { pmCapsGroups 1 }
749:
750:
751: END
752:
753: --
754: -- Copyright (C) The Internet Society (2000). All Rights Reserved.
755: --
756: -- This document and translations of it may be copied and furnished to
757: -- others, and derivative works that comment on or otherwise explain it or
758: -- assist in its implementation may be prepared, copied, published and
759: -- distributed, in whole or in part, without restriction of any kind,
760: -- provided that the above copyright notice and this paragraph are included
761: -- on all such copies and derivative works. However, this document itself
762: -- may not be modified in any way, such as by removing the copyright notice
763: -- or references to the Internet Society or other Internet organizations,
764: -- except as needed for the purpose of developing Internet standards in
765: -- which case the procedures for copyrights defined in the Internet
766: -- Standards process must be followed, or as required to translate it into
767: -- languages other than English.
768: --
769: -- The limited permissions granted above are perpetual and will not be
770: -- revoked by the Internet Society or its successors or assigns.
771: --
772: -- This document and the information contained herein is provided on an "AS
773: -- IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
774: -- FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
775: -- LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
776: -- INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
777: -- FITNESS FOR A PARTICULAR PURPOSE.
778: