smilint in free(): warning: junk pointer, too high to make sense
(exit status 0)
| Message Severities | |
|---|---|
| Severity | Count |
| severe | 12 |
| error | 5 |
| minor error | 2 |
| warning | 5 |
| fyi | 2 |
| Message Types | |
|---|---|
| Type | Count |
| bad-identifier-case (error) | 1 |
| hyphen-end (error) | 1 |
| identifier-external-redefined (warning) | 2 |
| import-failed (error) | 3 |
| internal-flushing (warning) | 3 |
| internal-other (severe) | 4 |
| lexical (severe) | 8 |
| number-leading-zero (minor error) | 1 |
| previous-definition (fyi) | 2 |
| revision-missing (minor error) | 1 |
Messages:
1: -- extracted from draft-stephan-ippm-mib-02.txt 2: -- at Fri May 14 06:20:51 2004
3:
4: IPPM-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY,
8: NOTIFICATION-TYPE,
9: OBJECT-TYPE,
10: Integer32,
11: Counter32,
12: experimental
13: FROM SNMPv2-SMI
14: OwnerString
15: FROM RMON-MIB
16: protocolDir
17: FROM RMON2-MIB
18: DisplayString,
19: TimeStamp,
20: DateAndTime,
21: TruthValue,
22: RowStatus,
23: StorageType,
24: TEXTUAL-CONVENTION
25: FROM SNMPv2-TC
26: MODULE-COMPLIANCE,
27: OBJECT-GROUP,
28: NOTIFICATION-GROUP
29: FROM SNMPv2-CONF;
30:
31:
32: ippmMib MODULE-IDENTITY
33: LAST-UPDATED "200202011200Z" -- Feb 1, 2002
34: ORGANIZATION "France Telecom - R&D"
35: CONTACT-INFO
36: "Postal : Emile Stephan
37: France Telecom - R&D, Dpt. CPN
38: 2, Avenue Pierre Marzin
39: Technopole Anticipa
40: 22307 Lannion Cedex
41: FRANCE
42: Tel: + 33 2 96 05 36 10
43: E-mail: emile.stephan@francetelecom.com"
44: DESCRIPTION
45: " This memo defines a portion of the Management Information Base
46: (MIB) for use with network management protocols in TCP/IP-based
47: internets. In particular, It defines a registry of the IPPM working
48: group metrics and specifies the objects used for managing IPPM
49: metrics measures, pushing alarms and reporting the measures results.
50: "
51: REVISION "200107051500Z" -- July 2001
52: DESCRIPTION
53: "The creation of the IPPM-MIB corresponds to the draft-
54: stephan-ippm-mib-00.txt posted in July 2001. The IPPM-MIB was
55: partially presented during the IPPM WG meeting of London.
56:
57: Two main issues were identified during the 52 th IETF meetings in
58: SLC:
59:
60: + There is a need for a common IPPM metric registry;
61: + There is a short term need for the reporting part of the IPPM-
62: MIB;
63: "
64: REVISION "200201051500Z" -- Jan 2002
65: DESCRIPTION
66: "This release corresponds to draft-stephan-ippm-mib-01.txt
67: posted in January 2002. This draft added sections which
68: presents:
69:
70: + The different measurement architectures;
71: + The integration of the IPPM-MIB in a measurement software;
72: + The use of the IPPM-MIB for reporting.
73:
74: The new items created in this release are:
75:
76: + Fields in the ippmOwnersTable to control the access of an
77: owner to the measures.
78: + The table ippmResultSharingTable to manage the access of an
79: owner to the results of the measure.
80:
81: All the control tables are optional or read only in reporting
82: mode.
83: "
84: REVISION "200202011200Z" -- Feb 2002
85: DESCRIPTION
86: "The current release corresponds to draft-stephan-ippm-mib-
87: 02.txt posted in February 2002. It added a section to present the
88: IPPM metrics registry.
89:
90: The new items created in this release are:
91:
92: + TC IppmReportDefinition and IppmStandardMetrics;
93: + The registry of the IPPM metrics;
94: + The ippmReportSetupTable and the ippmReportTable;
95: + The notification tree.
96: "
97:
98: --
99: -- to be assigned by IANA
100: --
101: ::= { experimental 10000 }
102:
103: --
104: -- registry
105: --
106:
107: metrics OBJECT IDENTIFIER ::= { ippmMib 1 }
108:
109: rfc OBJECT IDENTIFIER ::= { metrics 1 }
110: draft OBJECT IDENTIFIER ::= { metrics 2 }
111: id OBJECT IDENTIFIER ::= { metrics 3 }
112:
113: --
114: -- metrics registry from RFC of the IPPM WG
115: --
116:
117:
118: instantaneousUnidirectionalConnectivity OBJECT IDENTIFIER::={rfc 1}
119: instantaneousBidirectionalConnectivity OBJECT IDENTIFIER ::={rfc 2}
120: intervalUnidirectionalConnectivity OBJECT IDENTIFIER ::= { rfc 3 }
121: intervalBidirectionalConnectivity OBJECT IDENTIFIER ::= { rfc 4 }
122: intervalTemporalConnectivity OBJECT IDENTIFIER ::= { rfc 5 }
123: onewayDelay OBJECT IDENTIFIER ::= { rfc 6 }
124: onewayDelayPoissonStream OBJECT IDENTIFIER ::= { rfc 7 }
125: onewayDelayPercentile OBJECT IDENTIFIER ::= { rfc 8 }
126: onewayDelayMedian OBJECT IDENTIFIER ::= { rfc 9 }
127: onewayDelayMinimum OBJECT IDENTIFIER ::= { rfc 10 }
128: onewayDelayInversePercentile OBJECT IDENTIFIER ::= { rfc 11 }
129: onewayPacketLoss OBJECT IDENTIFIER ::= { rfc 12 }
130: onewayPacketLossPoissonStream OBJECT IDENTIFIER ::= { rfc 13 }
131: onewayPacketLossAverage OBJECT IDENTIFIER ::= { rfc 14 }
132: roundtripDelay OBJECT IDENTIFIER ::= { rfc 15 }
133: roundtripDelayPoissonStream OBJECT IDENTIFIER ::= { rfc 16 }
134: roundtripDelayPercentile OBJECT IDENTIFIER ::= { rfc 17 }
135: roundtripDelayMedian OBJECT IDENTIFIER ::= { rfc 18 }
136: roundtripDelayMinimum OBJECT IDENTIFIER ::= { rfc 19 }
137: roundtripDelayInversePercentile OBJECT IDENTIFIER ::= { rfc 20 }
138:
139: --
140: -- metrics registry from draft of the IPPM WG
141: --
142:
143: --
144: -- metrics registry from individual draft
145: --
146:
147: --
148: -- TEXTUAL-CONVENTION
149: --
150: TimeUnit ::= TEXTUAL-CONVENTION
151: STATUS current
152: DESCRIPTION
153: "A list of time units."
154: SYNTAX INTEGER {
155: year(1),
156: month(2),
157: week(3),
158: day(4),
159: hour(5),
160: second(6),
161: ms(7),
162: us(8),
163: ns(9)
164: }
165: --
166: --
167: -- A absolute, GMT timer using UTC like convention.
168: --
169: --
170:
171: GMTDateAndTime ::= TEXTUAL-CONVENTION
172: DISPLAY-HINT "1d-1d-1d,1d:1d:1d,2d"
173: STATUS current
174: DESCRIPTION
175: "A date-time specification.
176:
177: field octets contents range
178: ----- ------ -------- -----
179: 1 1 year* 0..255
180: 2 2 month 1..12
181: 3 3 day 1..31
182: 4 4 hour 0..23
183: 5 5 minutes 0..59
184: 6 6 seconds 0..59
185: 7 7-8 1/10 milliseconds 0..9999
186:
187: *Notes: 0 stands for year 2000.
188:
189: For example, '0102192015100500' represent 8:15pm, 10
190: seconds and 50 ms GMT on 19 February 2001 and is
191: displayed as 01-02-19,20:15:10,0500"
192: SYNTAX OCTET STRING (SIZE (8))
193:
194:
195:
196: GmtTimeFilter ::= TEXTUAL-CONVENTION
197: STATUS current
198: DESCRIPTION
199: "GmtTimeFilter TC is inspired by the TimeFilter defined
200: in the RMON2. The reference of the time of TimeFilter is
201: the local value of sysUptime while GmtTimeFilter uses a
202: absolute reference of time.
203:
204: GmtTimeFilter is intended to be used for the index of a
205: table. It allows an application to download only those
206: rows changed since a particular time. A row is
207: considered changed if the value of any object in the row
208: changes or if the row is created or deleted.
209:
210: Each new conceptual row will be associated with the
211: timeMark instance which was created at the value of
212: ippmTimeSysTimer.
213:
214: It is intended to provide an absolute timestamp index
215: for the result of measures. Typically to each singleton
216: produced by an IPPM measure is associated the timemark
217: corresponding to the moment of the measure.
218:
219: illustrations:
220:
221: Consider the 2 tables measureTable and resultTable
222:
223: measureTable OBJECT-TYPE
224: SYNTAX SEQUENCE OF MeasureEntry
225: MAX-ACCESS not-accessible
226: STATUS current
227: DESCRIPTION ''
228: ::= { fooMib 1 }
229: INDEX { measureIndex }
230:
231: resultTable OBJECT-TYPE
232: SYNTAX SEQUENCE OF ResultEntry
233: MAX-ACCESS not-accessible
234: STATUS current
235: DESCRIPTION ''
236: ::= { fooMib 2 }
237: INDEX { measureIndex, resultTimeMark }
238:
239: ResultEntry {
240: resultTimeMark TimeFilter,
241: resultCounts Counter
242: }
243:
244: Should there be two measure rows in the measure table
245: (measureIndex == 1, measureIndex == 2) which produced
246: results asynchronously (e.g. made at Poisson intervals
247: or sibling) and log them in the result table.
248: Measure 1 produced the result 34 at time
249: 0102192015100500 GMT, while row 2 produced the value 54
250: most recently (10ms later) at time 0102192015100600 GMT,
251: and both rows are updated on several later occasions
252: such that the current values are 37 and 53 respectively.
253:
254: Then the following resultCounts instances would exist.
255:
256: resultCounts.1.0102192015100500 34
257: resultCounts.2.0102192015100600 54
258: resultCounts.1.0102192015100950 65
259: resultCounts.1.0102192015100600 57
260: resultCounts.2.0102192015100800 48
261: resultCounts.2.0102192015100850 53
262: resultCounts.1.0102192015110050 49
263: resultCounts.1.0102192015110200 37
264:
265: The following get-bulk explains how a NMS retrieves the
266: results of the measures.
267:
268: get-bulk(nonRptrs=1, maxReps=10, resultCounts.1);
269: returns:
270: resultCounts.1.0102192015100500 == 34
271: resultCounts.1.0102192015100950 == 65
272: resultCounts.1.0102192015100600 == 57
273: resultCounts.1.0102192015110050 == 49
274: resultCounts.1.0102192015110200 == 37
275: # return lexigraphically-next two MIB instances
276:
277: get-bulk(nonRptrs=0, maxReps=2,
278: resultCounts.1.0102192015100600,
279: resultCounts.2.0102192015100600);
280: returns:
281: resultCounts.1.0102192015100950 == 65
282: resultCounts.2.0102192015100800 == 48
283: resultCounts.1.0102192015100600 == 57
284: resultCounts.2.0102192015100850 == 53
285:
286:
287: get-bulk(nonRptrs=0, maxReps=2,
288: resultCounts.1.0102192015110200,
289: resultCounts.2.0102192015110200);
290: returns:
291: return lexigraphically-next two MIB instances
292: no 'resultTable' counter values at all are
293: returned because neither counter has been updated since
294: time 0102192015110200
295: "
296: SYNTAX GMTDateAndTime
297:
298: TypeP ::= TEXTUAL-CONVENTION
299: DISPLAY-HINT "1d."
300: STATUS current
301: DESCRIPTION
302: "This textual convention is used to describe the
303: protocols encapsulation list of a packet, and is used as
304: the value of the SYNTAX clause for the type of the Src
305: and Dst of a IPPM measure. The RFC2895 specifies a macro
306: for the definition of protocols identifiers while its
307: companion document, the RFC2896 defines a set of
308: protocols identifiers.
309:
310: Notes: An IPPM TypeP does not differ from RMON2
311: Protocols identifiers but TypeP usage in IPPM MIB
312: differs from Protocol identifier usage in RMON2. A IPPM
313: measure is active so generally TypeP does not describe
314: the link layer (i.e. ether2...). Valid Internet packets
315: are sent from Src to Dst. Then the choice of the link
316: layer relies on the Internet stack.
317:
318: For example, the RFC2896 defines the protocol identifier
319: '16.0.0.0.1.0.0.8.0.0.0.0.6.0.0.0.23.3.0.0.0' which
320: represents ether2.ip.tcp.telnet and the protocol
321: identifier 16.0.0.0.1.0.0.8.0.0.0.0.4.0.0.0.17.3.0.0.0
322: which stands for ether2.ip.ipip4.udp. The corresponding
323: TypeP are '12.0.0.8.0.0.0.0.6.0.0.0.23.3.0.0.0'
324: (ip.tcp.telnet) and 12.0.0.8.0.0.0.0.4.0.0.0.17.3.0.0.0
325: (ip.ipip4.udp)."
326: SYNTAX OCTET STRING
327:
328:
329: IppmReportDefinition ::= TEXTUAL-CONVENTION
330: STATUS current
331: DESCRIPTION
332: "IppmReportDefinition is intended to be used for the description
333: of a report of results of a measure.
334:
335: By default all the results of a measure belong to the report of
336: this measure.
337:
338: The first step of the report elaboration set up triggers on the
339: value of the measure and on the distribution over time of the events
340: generated by these triggers.
341:
342: The measure results corresponding to an event are reported
343: periodically or sent in alarms as soon as the event appears.
344:
345: The end of description describe housekeeping tasks.
346:
347: An action if performed if the corresponding bit is set to 1.
348: onSingleton(1):
349: The actions are performed each time a new result of the
350: measure occurs.
351:
352: onMeasureCycle(2):
353: The actions are performed on the results of the measure
354: at the end of each cycle of measure.
355:
356: onMeasureCompletion(3):
357: The actions are performed on the results of the measure
358: at the end of the measure.
359:
360: reportOnlyUptoDownMetricResults(4):
361: Report the contiguous results which are on opposite sides
362: of the metric threshold.
363:
364: reportOnlyExceededEventsDuration(5):
365: Report the current result of a serie of contiguous
366: results which exceed the metric threshold when the
367: duration of the serie is over the events duration
368: threshold seconds.
369:
370: inIppmReportTable(6):
371: store the report in the local ippmReportTable.
372:
373: inSNMPTrapPDU(7):
374: Send the report using a SNMP-Trap-PDU.
375:
376: inSNMPv2TrapPDU(8):
377: Send the report using a SNMPv2-Trap-PDU.
378:
379: inInformRequestPDU(9):
380: Send the report using a SNMP InformRequest-PDU.
381:
382: inEmail(10):
383: Send the report using an email.
384:
385: inSMS(11):
386: Send the report using a SMS.
387:
388: clearHistory(12):
389: Remove all the results corresponding to this measure
390: from the ippmHistoryTable.
391:
392: clearReport(13):
393: Remove all the results corresponding to this measure
394: from the ippmReportTable.
395: "
396:
397: SYNTAX BITS {
398: none(0), -- reserved
399: onSingleton(1),
400: onMeasureCycle(2),
401: onMeasureCompletion(3),
402: reportOnlyUptoDownMetricResults(4),
403: reportOnlyExceededEventsDuration(5),
404: inIppmReportTable(6),
405: inSNMPTrapPDU(7),
406: inSNMPv2TrapPDU(8),
407: inInformRequestPDU(9),
408: inEmail(10),
409: inSMS(11),
410: clearHistory(12),
411: clearReport(13)
412: }
413:
414:
415:
416: IppmStandardMetrics ::= TEXTUAL-CONVENTION
417: STATUS current
418: DESCRIPTION
419: "The definition of the standardized IPPM metrics.
420: if the draftMetrics bit is set then the other bits describe a WG
421: draft metric identifiers.
422: "
423: SYNTAX BITS {
424: draftMetrics(0),
425: instantaneousUnidirectionalConnectivity(1),
426: instantaneousBidirectionalConnectivity(2),
427: intervalUnidirectionalConnectivity(3),
428: intervalBidirectionalConnectivity(4),
429: intervalTemporalConnectivity(5),
430: onewayDelay(6),
431: onewayDelayPoissonStream(7),
432: onewayDelayPercentile(8),
433: onewayDelayMedian(9),
434: onewayDelayMinimum(10),
435: onewayDelayInversePercentile(11),
436: onewayPacketLoss(12),
437: onewayPacketLossPoissonStream(13),
438: onewayPacketLossAverage(14),
439: roundtripDelay(15),
440: roundtripDelayPoissonStream(16),
441: roundtripDelayPercentile(17),
442: roundtripDelayMedian(18),
443: roundtripDelayMinimum(19),
444: roundtripDelayInversePercentile(20)
445: }
446: -- IPPM Mib objects definitions
447:
448: ippmCompliances OBJECT IDENTIFIER ::= { ippmMib 2 }
449: ippmOwnersGroup OBJECT IDENTIFIER ::= { ippmMib 3 }
450: ippmSystemGroup OBJECT IDENTIFIER ::= { ippmMib 4 }
451: ippmMeasureGroup OBJECT IDENTIFIER ::= { ippmMib 5 }
452: ippmHistoryGroup OBJECT IDENTIFIER ::= { ippmMib 6 }
453: ippmNetworkMeasureGroup OBJECT IDENTIFIER ::= { ippmMib 7 }
454: ippmAggregatedMeasureGroup OBJECT IDENTIFIER ::= { ippmMib 8 }
455: ippmReportGroup OBJECT IDENTIFIER ::= { ippmMib 9 }
456: ippmNotifications OBJECT IDENTIFIER ::= { ippmMib 10 }
457:
458:
459: --
460: -- ippmOwnersGroup
461: --
462: -- The ippmOwnersGroup objects are in charge of the management
463: -- of the access of the owners to the measurements.
464: --
465: --
466: ippmOwnersControlTable OBJECT-TYPE
467: SYNTAX SEQUENCE OF IppmOwnersControlEntry
468: MAX-ACCESS not-accessible
469: STATUS current
470: DESCRIPTION
471: "A NMS entity wishing to create and activate remote Ippm
472: measurements in an agent must previously be registered
473: in the ippmOwnersControlTable using the conceptual row
474: mechanism described in the RMON2.
475:
476: The control of the access to the results of the measures
477: is managed in the table ippmResultSharing.
478: "
479: ::= { ippmOwnersGroup 1 }
480:
481: ippmOwnersControlEntry OBJECT-TYPE
482: SYNTAX IppmOwnersControlEntry
483: MAX-ACCESS not-accessible
484: STATUS current
485: DESCRIPTION
486: "The description of the resources the agent granted to a
487: SNMP application.
488:
489: For example, an instance of ippmOwnersControlOwner with
490: an OwnerString 'acme', which represents the 14th owner
491: created in ippmOwnersControlTable would be named
492: ippmOwnersControlEntryOwner.14.
493:
494: Notes:
495:
496: The ippmOwnersControlIndex value is a local index
497: managed directly by the agent. It is not used in anyway
498: in the other IPPM tables."
499:
500: INDEX { ippmOwnersControlIndex }
501: ::= { ippmOwnersControlTable 1 }
502:
503: IppmOwnersControlEntry ::= SEQUENCE {
504: ippmOwnersControlOwner OwnerString,
505: ippmOwnersControlIndex Integer32,
506: ippmOwnersControlGrantedMetrics IppmStandardMetrics,
507: ippmOwnersControlGrantedRules BITS,
508: ippmOwnersControlIpAddress DisplayString,
509: ippmOwnersControlEmail DisplayString,
510: ippmOwnersControlSMS DisplayString,
511: ippmOwnersControlStatus OwnerString
512: }
513:
514: ippmOwnersControlIndex OBJECT-TYPE
515: SYNTAX Integer32 (1.. 65535)
516: MAX-ACCESS read-create
517: STATUS current
518: DESCRIPTION
519: "An arbitrary index that only identify an entry in this
520: table"
521: ::= { ippmOwnersControlEntry 1 }
522:
523: ippmOwnersControlOwner OBJECT-TYPE
524: SYNTAX OwnerString
525: MAX-ACCESS read-create
526: STATUS current
527: DESCRIPTION
528: "The owner described by this entry."
529: ::= { ippmOwnersControlEntry 2 }
530:
531:
532: ippmOwnersControlGrantedMetrics OBJECT-TYPE
533: SYNTAX IppmStandardMetrics
534: MAX-ACCESS read-create
535: STATUS current
536: DESCRIPTION
537: " Defines the metrics granted to an owner."
538: ::= { ippmOwnersControlEntry 3 }
539:
540: ippmOwnersControlGrantedRules OBJECT-TYPE
541: SYNTAX BITS {
542: all(0),
543: readonly(1),
544: permanent(2),
545: sender(2),
546: receive(3),
547: report(4),
548: alarm(5)
549: }
550: MAX-ACCESS read-create
551: STATUS current
552: DESCRIPTION
553: "Defines the rules this owner may act as in the current IPPM MIB
554: instance.
555: all(0):
556: The owner is granted with all the rules.
557: readonly(1):
558: The measures (not only the metrics) allowed to this
559: owner are setup by the manager of the point of measure. The owner can
560: not add new measures for these metrics. The creation and the
561: configuration of the measures corresponding to these metrics are
562: managed by the manager of the point of measure.
563: permanent(2):
564: The measures (not only the metrics) allowed to this
565: owner are determined by the manager of the point of measure. The
566: owner can not add new measures for these metrics. The creation and
567: the first configuration of the measures corresponding to these
568: metrics are managed by the manager of the point of measure. The owner
569: may modify the measures parameters of the entries of the
570: corresponding ippmMeasureEntry which access is read-write.
571: Typically that permits the owner to suspend the
572: measures, to change the begin and end of the measures.
573:
574: sender(3):
575: The owner may only activate measures for theses metrics
576: that send packets from the current point of measure. This flag is
577: only suitable for network measures. It shall be ignored for derived
578: metrics.
579: receiver(2):
580: The owner may only activate measures for theses metrics
581: that receive packets on the current point of measure. This flag is
582: only suitable for network measures. It shall be ignored for derived
583: metrics. Such control increases the security. The owner may not
584: generate packets from the probe.
585:
586: report(4):
587: The owner may setup aggregated metrics on the measures
588: corresponding to these metrics.
589:
590: alarm(5):
591: The owner may setup alarms on the results of the
592: measures metrics.
593:
594:
595: e.g.:
596: if the owner Acme is granted with the metric Instantaneous-
597: Unidirectional-Connectivity as a Receiver in the current point of
598: measure, then Acme can not setup a Instantaneous-Unidirectional-
599: Connectivity to another point of measure.
600: "
601: DEFVAL { 1 }
602: ::= { ippmOwnersControlEntry 4 }
603:
604: ippmOwnersControlIpAddress OBJECT-TYPE
605: SYNTAX DisplayString
606: MAX-ACCESS read-create
607: STATUS current
608: DESCRIPTION
609: "The IP address of the NMS corresponding to this owner.
610: The address is human readable and is represented using the dot
611: format."
612: ::= { ippmOwnersControlEntry 5 }
613:
614: ippmOwnersControlEmail OBJECT-TYPE
615: SYNTAX DisplayString
616: MAX-ACCESS read-create
617: STATUS current
618: DESCRIPTION
619: "The email address of the NMS corresponding to this
620: owner."
621: ::= { ippmOwnersControlEntry 6 }
622:
623: ippmOwnersControlSMS OBJECT-TYPE
624: SYNTAX DisplayString
625: MAX-ACCESS read-create
626: STATUS current
627: DESCRIPTION
628: "The SMS phone number of the NMS corresponding to this
629: owner."
630: ::= { ippmOwnersControlEntry 7 }
631:
632: ippmOwnersControlStatus OBJECT-TYPE
633: SYNTAX RowStatus
634: MAX-ACCESS read-create
635: STATUS current
636: DESCRIPTION
637: "The status of this table entry."
638: ::= { ippmOwnersControlEntry 8 }
639:
640: --
641: -- ippmResultSharingTable
642: --
643:
644: ippmResultSharingTable OBJECT-TYPE
645: SYNTAX SEQUENCE OF IppmResultSharingEntry
646: MAX-ACCESS not-accessible
647: STATUS current
648: DESCRIPTION
649: " ippmResultSharingTable controls finely the access of
650: an owner to the measure results of other owners. An
651: owner may grant another to read the result of its
652: measure.
653: Entries may exist in ippmResultSharingTable even is the
654: measures to be shared are not yet defined. Deleting a
655: measure entry in the ippmMeasureTable does not delete
656: the entries corresponding to this measure in the
657: ippmResultSharingTable.
658:
659: IppmResultSharingTable is optional. If this table is not
660: implemented then the owner has only access to its
661: measure results."
662:
663: ::= { ippmOwnersGroup 2 }
664:
665: ippmResultSharingEntry OBJECT-TYPE
666: SYNTAX IppmResultSharingEntry
667: MAX-ACCESS not-accessible
668: STATUS current
669: DESCRIPTION
670: "An entry allows an owner to read the results of a
671: measure owned by another owner.
672: It permits 2 typical usages:
673: creating derived measurements on these results;
674: reading the results from a remote NMS.
675:
676: Example: if acme.12 is a One-way-Delay(6) measure
677: Acme may allows Peter to make derived metrics
678: On the results of this measure.
679: "
680:
681: INDEX { ippmResultSharingOwner, ippmResultSharingIndex}
682: ::= { ippmResultSharingTable 1 }
683:
684:
685: IppmResultSharingEntry ::= SEQUENCE {
686: ippmResultSharingOwner OwnerString,
687: ippmResultSharingIndex Integer32,
688: ippmResultSharingMeasureOwner OwnerString,
689: ippmResultSharingMeasureIndex Integer32,
690: ippmResultSharingGrantedOwner OwnerString,
691: ippmResultSharingStatus RowStatus
692: }
693: ippmResultSharingOwner OBJECT-TYPE
694: SYNTAX OwnerString
695: MAX-ACCESS read-create
696: STATUS current
697: DESCRIPTION
698: " The owner of this result control entry. Typically the
699: owner which created this conceptual row."
700: ::= { ippmResultSharingEntry 1 }
701:
702:
703: ippmResultSharingIndex OBJECT-TYPE
704: SYNTAX Integer32 (1.. 65535)
705: MAX-ACCESS read-create
706: STATUS current
707: DESCRIPTION
708: " The index of this result control entry. The value is
709: managed by the owner. On creation a SNMP error 'inconsistentValue' is
710: returned if this value is already in use by this owner."
711: ::= { ippmResultSharingEntry 2 }
712:
713:
714: ippmResultSharingMeasureOwner OBJECT-TYPE
715: SYNTAX OwnerString
716: MAX-ACCESS read-create
717: STATUS current
718: DESCRIPTION
719: "The owner of the measure to be shared. The couple
720: ippmResultSharingMeasureOwner, ippmResultSharingMeasureIndex
721: identifies absolutely a measure"
722: ::= { ippmResultSharingEntry 3 }
723:
724: ippmResultSharingMeasureIndex OBJECT-TYPE
725: SYNTAX Integer32 (1.. 65535)
726: MAX-ACCESS read-create
727: STATUS current
728: DESCRIPTION
729: "The index of the measure to be shared."
730: ::= { ippmResultSharingEntry 4 }
731:
732: ippmResultSharingGrantedOwner OBJECT-TYPE
733: SYNTAX OwnerString
734: MAX-ACCESS read-only
735: STATUS current
736: DESCRIPTION
737:
738: "The owner which is granted to access to the result of
739: the measure described by the couple ippmResultSharingMeasureOwner,
740: ippmResultSharingMeasureIndex."
741: ::= { ippmResultSharingEntry 5 }
742:
743: ippmResultSharingStatus OBJECT-TYPE
744: SYNTAX RowStatus
745: MAX-ACCESS read-only
746: STATUS current
747: DESCRIPTION
748: " The status of this table entry. Once the entry status
749: is set to active."
750: ::= { ippmResultSharingEntry 6 }
751:
752:
753: --
754: -- ippmSystemGroup
755: --
756: --
757:
758:
759: ippmSystemTimer OBJECT-TYPE
760: SYNTAX GMTDateAndTime
761: MAX-ACCESS read-only
762: STATUS current
763: DESCRIPTION
764: "The current time of the system."
765: ::= { ippmSystemGroup 1 }
766:
767:
768: ippmSystemSynchonizationType OBJECT-TYPE
769: SYNTAX INTEGER {
770: other(0),
771: ntp(1),
772: gps(2),
773: cdma(4)
774: }
775: MAX-ACCESS read-only
776: STATUS current
777: DESCRIPTION
778: "ippmSystemSynchonizationType describes the mechanism
779: used to synchronise the system.
780:
781: other
782: The synchronisation process must be defined
783: extensively in the ippmSystemSynchonizationDescription.
784:
785: ntp
786: The system is synchronised using the network
787: time protocol. The NTP synchronisation must be described
788: finely in the ippmSystemSynchonizationDescription.
789:
790: gps
791: The system is synchronised using the GPS clocks.
792:
793: cdma
794: The system is synchronised using the CDMA
795: clocks.
796: "
797: ::= { ippmSystemGroup 2 }
798:
799: ippmSystemSynchonizationDescription OBJECT-TYPE
800: SYNTAX DisplayString
801: MAX-ACCESS read-only
802: STATUS current
803: DESCRIPTION
804: "The description of the synchronization process."
805: ::= { ippmSystemGroup 3 }
806:
807: ippmSystemClockResolution OBJECT-TYPE
808: SYNTAX Integer32
809: MAX-ACCESS read-only
810: STATUS current
811: DESCRIPTION
812: "ippmSystemClockResolution provides the precision of the
813: clock used for the measures. The unit is 1/10 of
814: millisecond. For example, the clock on an old Unix host
815: might advance only once every 10 msec, and thus have a
816: resolution of only 10 msec."
817:
818: ::= { ippmSystemGroup 4 }
819:
820: ippmSystemSynchronisationTime OBJECT-TYPE
821: SYNTAX DateAndTime
822: MAX-ACCESS read-only
823: STATUS current
824: DESCRIPTION
825: "The time when occurs the last synchronisation of the
826: clock. The last synchronisation must be set even if the
827: synchronisation is not automatic."
828: ::= { ippmSystemGroup 5 }
829:
830: ippmSystemClockAccuracy OBJECT-TYPE
831: SYNTAX Integer32
832: MAX-ACCESS read-only
833: STATUS current
834: DESCRIPTION
835: "The most recent accuracy of the clock computed. The
836: accuracy must be compute even if the synchronisation is
837: not automatic."
838: ::= { ippmSystemGroup 6 }
839:
840: ippmSystemClockSkew OBJECT-TYPE
841: SYNTAX Integer32
842: MAX-ACCESS read-only
843: STATUS current
844: DESCRIPTION
845: "The most recent skew of the clock computed. The
846: ippmSystemSkew must be compute even if the
847: synchronisation is not automatic."
848: ::= { ippmSystemGroup 7 }
849:
850:
851: ippmSystemPrevClockAccuracy OBJECT-TYPE
852: SYNTAX Integer32
853: MAX-ACCESS read-only
854: STATUS current
855: DESCRIPTION
856: "The previous accuracy of the clock measured. The
857: ippmSystemPrevClockAccuracy must be computed even if the
858: synchronisation is not automatic."
859: ::= { ippmSystemGroup 8 }
860:
861: ippmSystemPrevClockSkew OBJECT-TYPE
862: SYNTAX Integer32
863: MAX-ACCESS read-only
864: STATUS current
865: DESCRIPTION
866: "The previous skew of the clock measured. The
867: ippmSystemPrevClockSkew must be computed even if the
868: synchronisation is not automatic."
869: ::= { ippmSystemGroup 9 }
870:
871:
872: --
873:
874: --
875: --
876: -- ippmMeasureGroup
877: --
878: --
879: --
880:
881: ippmMetricTable OBJECT-TYPE
882: SYNTAX SEQUENCE OF IppmMetricEntry
883: MAX-ACCESS not-accessible
884: STATUS current
885: DESCRIPTION
886: "This table describes the current implementation. This
887: table is mandatory. Each IPPM standardized metric must
888: be described in the table.
889: In reporting mode the entries of this table may be not
890: accessible. It means that the table is handle internally
891: by the measure software.
892: "
893: ::= { ippmMeasureGroup 1 }
894:
895: ippmMetricEntry OBJECT-TYPE
896: SYNTAX IppmMetricEntry
897: MAX-ACCESS not-accessible
898: STATUS current
899: DESCRIPTION
900: "An entry describes the static capabilities of a metric
901: implementation."
902: INDEX { ippmMetricIndex }
903: ::= { ippmMetricTable 1 }
904:
905: IppmMetricEntry ::=
906: SEQUENCE {
907: ippmMetricIndex Integer32,
908: ippmMetricCapabilities INTEGER,
909: ippmMetricUnit INTEGER,
910: ippmMetricDescription DisplayString,
911: ippmMetricMaxHistorySize Integer32
912: }
913:
914: ippmMetricIndex OBJECT-TYPE
915: SYNTAX Integer32 (1.. 65535)
916: MAX-ACCESS read-only
917: STATUS current
918: DESCRIPTION
919: "ippmMetricIndex defines an unambiguous index for each
920: standardized metric. Its value is the value of the node of the
921: metric in the IPPM-MIB metrics registry ippmMib.metrics.rfc.
922: Each metric registered in the standard registry must be present
923: in this table.
924: This index is used to identify the metric performed among the
925: IPPM-MIB entities involved in the measure.
926: Example:
927: The index of the metric onewayPacketLossAverage which is
928: registered as ippmMib.metrics.rfc.onewayPacketLossAverage will
929: always have the value 14."
930: ::= { ippmMetricEntry 1 }
931:
932:
933: ippmMetricCapabilities OBJECT-TYPE
934: SYNTAX INTEGER {
935: notImplemented(0),
936: implemented(1)
937: }
938: MAX-ACCESS read-only
939: STATUS current
940: DESCRIPTION
941: "notImplemented
942: the metric is not implemented.
943: implemented
944: the metric is implemented."
945: DEFVAL { implemented }
946: ::= { ippmMetricEntry 2 }
947:
948: ippmMetricUnit OBJECT-TYPE
949: SYNTAX INTEGER {
950: noUnit(0),
951: second(1),
952: ms(2),
953: us(3),
954: ns(4),
955: percentage(5),
956: packets(6),
957: byte(6),
958: kbyte(7),
959: megabyte(8)
960: }
961: MAX-ACCESS read-only
962: STATUS current
963: DESCRIPTION
964: "The unit used in the current entity for the results of
965: the measure of this metric."
966: ::= { ippmMetricEntry 3 }
967:
968: ippmMetricDescription OBJECT-TYPE
969: SYNTAX DisplayString
970: MAX-ACCESS read-only
971: STATUS current
972: DESCRIPTION
973: "A textual description of the metric implementation."
974: ::= { ippmMetricEntry 4 }
975:
976: ippmMetricMaxHistorySize OBJECT-TYPE
977: SYNTAX Integer32
978: MAX-ACCESS read-only
979: STATUS current
980: DESCRIPTION
981: "Specifies the maximal number of results that a metric
982: measure can save in the ippmHistoryTable."
983: ::= { ippmMetricEntry 5 }
984:
985:
986:
987: --
988: -- ippmMeasureTable
989: --
990: --
991:
992: ippmMeasureTable OBJECT-TYPE
993: SYNTAX SEQUENCE OF IppmMeasureEntry
994: MAX-ACCESS not-accessible
995: STATUS current
996: DESCRIPTION
997: "The table of all the IPPM measures which are running in
998: the device. They may not be active.
999:
1000: a measure consists in a subset of metrics to compute.
1001: The results of the measure may be saved in the
1002: ippmHistoryTable. The configuration of the measure sets
1003: the size of the history requested in
1004: ippmMeasureHystorySize.
1005:
1006: The maximal number of MIB objects to be collected in the
1007: portion of ippmHistoryTable associated with this metric
1008: depends the value of the ippmMetricMaxHistorySize.
1009: The value of each metric ippmMeasureHystorySize must not
1010: be over the value of ippmMetricMaxHistorySize
1011: corresponding to this metric in ippmMetricTable.
1012:
1013: In reporting mode the entries of this table may be not
1014: accessible. It means that the table is handle internally
1015: by the measure software.
1016: "
1017: ::= { ippmMeasureGroup 2 }
1018:
1019: ippmMeasureEntry OBJECT-TYPE
1020: SYNTAX IppmMeasureEntry
1021: MAX-ACCESS not-accessible
1022: STATUS current
1023: DESCRIPTION
1024: "A SNMP entity wishing to create and activate a
1025: measurement adds a new entry in the ippmMeasureTable.
1026:
1027: Typically the configuration operation set the values of
1028: the conceptual row parameters using an unused owner
1029: index and sets the status of the row to createAndGo.
1030:
1031: An SNMP error 'inconsistentValue' is returned if the
1032: owner index is out of range."
1033: INDEX { ippmMeasureOwner, ippmMeasureIndex }
1034: ::= { ippmMeasureTable 1 }
1035:
1036: IppmMeasureEntry ::=
1037: SEQUENCE {
1038: ippmMeasureOwner OwnerString,
1039: ippmMeasureIndex Integer32,
1040: ippmMeasureName DisplayString,
1041: ippmMeasureMetrics IppmStandardMetrics,
1042: ippmMeasureBeginTime GMTDateAndTime,
1043: ippmMeasureClockPeriodUnit TimeUnit,
1044: ippmMeasureClockPeriod Integer32,
1045: ippmMeasureDurationUnit TimeUnit,
1046: ippmMeasureDuration Integer32,
1047: ippmMeasureHystorySize Integer32,
1048: ippmMeasureStorageType StorageType,
1049: ippmMeasureStatus RowStatus
1050: }
1051:
1052: ippmMeasureOwner OBJECT-TYPE
1053: SYNTAX OwnerString
1054: MAX-ACCESS read-create
1055: STATUS current
1056: DESCRIPTION
1057: "The owner who has configured this entry."
1058: DEFVAL { "acme" }
1059: ::= { ippmMeasureEntry 1 }
1060:
1061: ippmMeasureIndex OBJECT-TYPE
1062: SYNTAX Integer32 (1.. 65535)
1063: MAX-ACCESS read-create
1064: STATUS current
1065: DESCRIPTION
1066: "The owner index of the measure. The value is managed by
1067: the owner. An SNMP error 'inconsistentValue' is returned
1068: if this value is already in use by this owner."
1069: ::= { ippmMeasureEntry 2 }
1070:
1071: ippmMeasureName OBJECT-TYPE
1072: SYNTAX DisplayString
1073: MAX-ACCESS read-create
1074: STATUS current
1075: DESCRIPTION
1076: "The name of the instance of the metric. It illustrates
1077: the specificity of the metric and includes the metric
1078: and the typeP.
1079:
1080: example: IP-port-HTTP-connectivity"
1081: ::= { ippmMeasureEntry 3 }
1082:
1083:
1084:
1085: ippmMeasureMetrics OBJECT-TYPE
1086: SYNTAX IppmStandardMetrics
1087: MAX-ACCESS read-create
1088: STATUS current
1089: DESCRIPTION
1090: "Defines the metrics to compute within this measure. A
1091: measure may be configured for the result of different
1092: metrics singletons to be archive in the
1093: ippmHistoryTable. The ippmMetricIndex of the created
1094: result has the value of the bit index of the
1095: corresponding ippmMeasureMetrics as explained above in
1096: the ippmMetricIndex definition.
1097:
1098: Example:
1099: A measure asking for One-way-Delay(6) and One-way-
1100: Packet-Loss(12) generated a flow of singletons which are
1101: logged in the ippmHistoryTable. The singletons created
1102: for the One-way-Delay measure have a value of
1103: ippmMetricIndex of 6 while the created singletons for
1104: the One-way-Packet-Loss measure have a value of
1105: ippmMetricIndex of 12."
1106: DEFVAL { { one-way-Delay, one-way-Packet-Loss } }
1107: ::= { ippmMeasureEntry 4 }
1108:
1109: ippmMeasureBeginTime OBJECT-TYPE
1109: fyi -
info: previous definition of `ippmMeasureBeginTime'
1110: SYNTAX GMTDateAndTime
1111: MAX-ACCESS read-create
1112: STATUS current
1113: DESCRIPTION
1114: "Specifies the time at which the measure starts."
1115: ::= { ippmMeasureEntry 5 }
1116:
1117:
1118: ippmMeasureClockPeriodUnit OBJECT-TYPE
1119: SYNTAX TimeUnit
1120: MAX-ACCESS read-create
1121: STATUS current
1122: DESCRIPTION
1123: "Specifies the unit of the measure period."
1124: DEFVAL { second }
1125: ::= { ippmMeasureEntry 6 }
1126:
1127: ippmMeasureClockPeriod OBJECT-TYPE
1128: SYNTAX Integer32
1129: MAX-ACCESS read-create
1130: STATUS current
1131: DESCRIPTION
1132: "Specifies the among of time between 2 sampling
1133: intervals.
1134:
1135: Notes:
1136: This interval generates a flow of periodical instants
1137: which may be transformed as a flow of unpredictable
1138: instants of measure by the
1139: ippmNetworkMeasureClockPattern."
1140: DEFVAL { 60 }
1141: ::= { ippmMeasureEntry 7 }
1142:
1143:
1144: ippmMeasureDurationUnit OBJECT-TYPE
1145: SYNTAX TimeUnit
1146:
1147: MAX-ACCESS read-create
1148: STATUS current
1149: DESCRIPTION
1150: "Specifies the unit of the measure duration."
1151: DEFVAL { second }
1152: ::= { ippmMeasureEntry 8 }
1153:
1154: ippmMeasureDuration OBJECT-TYPE
1155: SYNTAX Integer32
1156: MAX-ACCESS read-create
1157: STATUS current
1158: DESCRIPTION
1159: "Specifies the duration of the measure."
1160:
1161: DEFVAL { 120 }
1162: ::= { ippmMeasureEntry 9 }
1163:
1164: ippmMeasureHystorySize OBJECT-TYPE
1165: SYNTAX Integer32
1166: MAX-ACCESS read-create
1167: STATUS current
1168: DESCRIPTION
1169: "Specifies the maximum number of results saved for each
1170: metric of this measure. The history of each metric is
1171: managed as a circular table. The newest result overwrite
1172: the oldest one when the history granted to this metric
1173: measure is full.
1174:
1175: The management of the results may be optimized if
1176: synchronized with the reports steps of this measure.
1177: "
1178: DEFVAL { 120 }
1179: ::= { ippmMeasureEntry 10 }
1180:
1181: ippmMeasureStorageType OBJECT-TYPE
1182: SYNTAX StorageType
1183: MAX-ACCESS read-create
1184: STATUS current
1185: DESCRIPTION
1186: "This object defines whether this row and the measure
1187: controlled by this row are kept in volatile storage and
1188: lost upon reboot or if this row is backed up by
1189: non-volatile or permanent storage.
1190: Possible values are: other(1), volatile(2), nonVolatile(3),
1191: permanent(4), readOnly(5)"
1192: DEFVAL { nonVolatile }
1193: ::= { ippmMeasureEntry 11 }
1194:
1195:
1196: ippmMeasureStatus OBJECT-TYPE
1197: SYNTAX RowStatus
1198: MAX-ACCESS read-create
1199: STATUS current
1200: DESCRIPTION
1201: "The status of this table entry. Once the entry status
1202: is set to active, the associate entry cannot be
1203: modified."
1204: DEFVAL { createAndGo }
1205: ::= { ippmMeasureEntry 12 }
1206:
1207: --
1208: -- ippmHistoryGroup
1209: --
1210: --
1211: --
1212: -- ippmHistoryTable
1213: --
1214:
1215:
1216: ippmHistoryTable OBJECT-TYPE
1217: SYNTAX SEQUENCE OF IppmHistoryEntry
1218: MAX-ACCESS not-accessible
1219: STATUS current
1220: DESCRIPTION
1221: "The table of the results of the measures."
1222:
1223: ::= { ippmHistoryGroup 1 }
1224:
1225:
1226:
1227: ippmHistoryEntry OBJECT-TYPE
1228: SYNTAX IppmHistoryEntry
1229: MAX-ACCESS not-accessible
1230: STATUS current
1231: DESCRIPTION
1232:
1233: "An ippmHistoryEntry entry is one of the result of an
1234: measure identified by the index members ippmMeasureOwner
1235: and ippmMeasureIndex.
1236:
1237: In the index :
1238:
1239: + ippmMeasureOwner and ippmMeasureIndex identify
1240: the ippmMeasureEntry on whose behalf this entry was
1241: created;
1242: + ippmMetricIndex identifies the ippmMetricEntry
1243: of the metric to measure;
1244: + ippmLogTimeMark value is the absolute time
1245: when the result of the metric was measured.
1246:
1247: The ippmHistoryTimeMark value is the absolute time when
1248: the ippmHistoryValue was performed.
1249:
1250: IppmHistoryValue is the value of the metric measured at
1251: the time ippmHistoryTimeMark.
1252:
1253: Example:
1254: A one way delay measure is created by the entity 'acme'
1255: using the owner index 1 and setting the 6th bit
1256: (corresponding to One-way-Delay) of ippmMeasureMetrics
1257: to 1.
1258: Consider that the result of the one way delay measured
1259: for acme on the day 15 of June at 8h20mn 10s 10ms is 23.
1260: The result is identified as the singleton
1261: ippmHistoryValue.acme.1.6.0106150820100100 and stored
1262: with value 23.
1263:
1264: Its value may be retrieved using a get-
1265: next(ippmHistoryValue.acme.1.6.0106150820100099) which
1266: returns (ippmHistoryValue.acme.1.6.0106150820100100 ==
1267: 23). The ippmMetricIndex value of '6' corresponds to the
1268: 6th metric of ippmMetricTable which is Type-P-One-way-
1269: Delay.
1270: "
1271: INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex,
1272: ippmHistoryTimeMark }
1273: ::= { ippmHistoryTable 1 }
1274:
1275: IppmHistoryEntry ::=
1276: SEQUENCE {
1277: ippmHistoryTimeMark GMTDateAndTime,
1278: ippmHistoryValue Integer32
1279: }
1280: ippmHistoryTimeMark OBJECT-TYPE
1281: SYNTAX GMTDateAndTime
1282: MAX-ACCESS read-only
1283: STATUS current
1284: DESCRIPTION
1285: "The instant of the measure of the result."
1286: ::= { ippmHistoryEntry 1 }
1287:
1288: ippmHistoryValue OBJECT-TYPE
1289: SYNTAX Integer32
1290: MAX-ACCESS read-only
1291: STATUS current
1292: DESCRIPTION
1293:
1294: "The value of the measure."
1295: ::= { ippmHistoryEntry 2 }
1296:
1297:
1298:
1299:
1300:
1301: --
1302: -- ippmNetworkMeasureGroup
1303: --
1304:
1305:
1306: --
1307: --
1308: -- ippmNetworkMeasureTable
1309: --
1310: --
1311: ippmNetworkMeasureTable OBJECT-TYPE
1312: SYNTAX SEQUENCE OF IppmNetworkMeasureEntry
1313: MAX-ACCESS not-accessible
1314: STATUS current
1315: DESCRIPTION
1316: "A entry is a measure which performs network measures
1317: and provides a flow of results.
1318:
1319: This table extends the ippmMeasureTable. A network
1320: measure is a specific measure.
1321:
1322: It performs several metrics measure per packet exchange.
1323: Each step of a measure produces a singleton result per
1324: metric. The time of the measure and the value of the
1325: metric are saved in the ippmHistoryTable."
1326: ::= { ippmNetworkMeasureGroup 1 }
1327:
1328: ippmNetworkMeasureEntry OBJECT-TYPE
1329: SYNTAX IppmNetworkMeasureEntry
1330: MAX-ACCESS not-accessible
1331: STATUS current
1332: DESCRIPTION
1333: "A SNMP entity wishing to create and activate a network
1334: measure adds a new entry in the ippmMeasureTable and in
1335: IppmNetworkMeasureTable.
1336:
1337: Typically the configuration operation set both the
1338: values of the new ippmMeasureEntry and of the new
1339: IppmNetworkMeasureEntry and sets the status of the row
1340: to createAndGo.
1341:
1342: An SNMP error 'inconsistentValue' is returned if the
1343: index is out of range.
1344:
1345: The ippmMeasureMetrics is set to a list of metrics to be
1346: computed from the same raw packet exchange. Each step of
1347: measure delivers a singleton per chosen metric. Results
1348: are timestamped and saved in the ippmHistoryTable."
1349: INDEX { ippmMeasureOwner, ippmMeasureIndex }
1350: ::= { ippmNetworkMeasureTable 1 }
1351:
1352: IppmNetworkMeasureEntry ::=
1353: SEQUENCE {
1354: ippmNetworkMeasureSrcTypeP TypeP,
1355: ippmNetworkMeasureSrc OCTET STRING,
1356: ippmNetworkMeasureDstTypeP TypeP,
1357: ippmNetworkMeasureDst OCTET STRING,
1358: ippmNetworkMeasureClockPattern OCTET STRING,
1359: ippmNetworkMeasureTimeoutDelay Integer32,
1360: ippmNetworkMeasureL3PacketSize Integer32,
1361: ippmNetworkMeasureDataPattern OCTET STRING
1362:
1363: }
1364:
1365: ippmNetworkMeasureSrcTypeP OBJECT-TYPE
1366: SYNTAX TypeP
1367: MAX-ACCESS read-create
1368: STATUS current
1369: DESCRIPTION
1370: "Defines the type P of the source address of the packets
1371: sent by the measure."
1372: DEFVAL { '04000080001000'H } -- ->ip: 4.0.0.8.0.1.0
1373: ::= { ippmNetworkMeasureEntry 1 }
1374:
1375: ippmNetworkMeasureSrc OBJECT-TYPE
1376: SYNTAX OCTET STRING
1377: MAX-ACCESS read-create
1378: STATUS current
1379: DESCRIPTION
1380: "Specifies the address of the source of the measure.
1381:
1382: It is represented as an octet string with specific
1383: semantics and length as identified by the
1384: ippmNetworkMeasureSrcTypeP.
1385:
1386: For example, if the ippmNetworkMeasureSrcTypeP indicates
1387: an encapsulation of 'ip', this object length is 4,
1388: followed by the 4 octets of the IP address, in network
1389: byte order."
1390: DEFVAL { '04C0210415'H } -- -> ip: 192.33.4.21
1391: ::= { ippmNetworkMeasureEntry 2}
1392:
1393: ippmNetworkMeasureDstTypeP OBJECT-TYPE
1394: SYNTAX TypeP
1395: MAX-ACCESS read-create
1396: STATUS current
1397: DESCRIPTION
1398: "Defines the type P of the destination address of the
1399: packets sent by the measure."
1400: DEFVAL { '04000080001000'H } -- ->ip: 4.0.0.8.0.1.0
1401: ::= { ippmNetworkMeasureEntry 3 }
1402:
1403: ippmNetworkMeasureDst OBJECT-TYPE
1404: SYNTAX OCTET STRING
1405: MAX-ACCESS read-create
1406: STATUS current
1407: DESCRIPTION
1408: "Specifies the address of the destination of the
1409: measure.
1410:
1411: It is represented as an octet string with specific
1412: semantics and length as identified by the
1413: ippmNetworkMeasureDstTypeP.
1414: For example, if the ippmNetworkMeasureDstTypeP indicates
1415: an encapsulation of 'ip', this object length is 4,
1416: followed by the 4 octets of the IP address, in network
1417: byte order."
1418: DEFVAL { '04C0220414'H } -- -> ip: 192.34.4.20
1419: ::= { ippmNetworkMeasureEntry 4 }
1420:
1421: ippmNetworkMeasureClockPattern OBJECT-TYPE
1422: SYNTAX OCTET STRING
1423: MAX-ACCESS read-create
1424: STATUS current
1425: DESCRIPTION
1426: "This cyclic clock shapes the profile of the instants of
1427: measurement according to an arbitrary distribution law.
1428: The clock resolution is ippmMeasureClockPeriod. The bits
1429: of the clock set to the value 1 determine the valid
1430: instants of measurement. A measure is to be processed if
1431: and only if the current bit value is 1.
1432: This pseudo-random clock pattern allows the
1433: configuration by the NMS of numerous kind of sampling
1434: law such as periodic or Poisson."
1435: DEFVAL { 11111111} -- 100% periodic
1436: ::= { ippmNetworkMeasureEntry 5 }
1437:
1438: ippmNetworkMeasureTimeoutDelay OBJECT-TYPE
1439: SYNTAX Integer32
1440: MAX-ACCESS read-create
1441: STATUS current
1442: -- UNITS "Milliseconds"
1443: DESCRIPTION
1444: "Specifies the delay after which the packet is
1445: considered lost."
1446: DEFVAL { 1 }
1447: ::= { ippmNetworkMeasureEntry 6 }
1448:
1449: ippmNetworkMeasureL3PacketSize OBJECT-TYPE
1450: SYNTAX Integer32
1451: MAX-ACCESS read-create
1452: STATUS current
1453: DESCRIPTION
1454: "Specifies the size of the packets send at the last
1455: network layer in the sense of the TypeP definition."
1456: DEFVAL { 64 }
1457: ::= { ippmNetworkMeasureEntry 7 }
1458:
1459: ippmNetworkMeasureDataPattern OBJECT-TYPE
1460: SYNTAX OCTET STRING
1461: MAX-ACCESS read-create
1462: STATUS current
1463: DESCRIPTION
1464: "The current field defines the round robin pattern used
1465: to fill the packet."
1466: DEFVAL { 'FF'H }
1467: ::= { ippmNetworkMeasureEntry 8 }
1468:
1469:
1470:
1471: --
1472: --
1473: -- ippmAggregatedMeasureGroup
1474: --
1475: --
1476: --
1477: --
1478: -- ippmAggregatedMeasureTable
1479: --
1480: --
1481:
1482: ippmAggregatedMeasureTable OBJECT-TYPE
1483: SYNTAX SEQUENCE OF IppmAggregatedMeasureEntry
1484: MAX-ACCESS not-accessible
1485: STATUS current
1486: DESCRIPTION
1487: " This table extends the ippmMeasureTable.
1488: A aggregated measure summarizes the results of previous
1489: network or aggregated measures. The results may saved in
1490: the ippmHistoryTable.
1491:
1492: Each step of the measure computation produces a
1493: singleton result per metric."
1494: ::= { ippmAggregatedMeasureGroup 1 }
1495:
1496: ippmAggregatedMeasureEntry OBJECT-TYPE
1497: SYNTAX IppmAggregatedMeasureEntry
1498: MAX-ACCESS not-accessible
1499: STATUS current
1500: DESCRIPTION
1501: "A SNMP entity wishing to create and activate a statistic
1502: measure adds a new entry in the ippmMeasureTable and in
1503: ippmAggregatedMeasureTable.
1504:
1505: Typically the configuration operation sets both the values of
1506: the new ippmMeasureEntry and of the new
1507: IppmAggregatedMeasureEntry and sets the status of the row to
1508: createAndGo.
1509:
1510: The ippmMeasureMetrics defines the metric to compute.
1511: The results of the measure to summarize are identified by
1512: ippmAggregatedMeasureHistoryOwner,
1513: IppmAggregatedMeasureHistoryOwnerIndex and
1514: ippmAggregatedMeasureHistoryMetric
1515: The aggregated task starts at ippmMeasureBeginTime and end after
1516: ippmMeasureDuration. A aggregated result is performed and saved
1517: in the ippmHistoryTable for each ippmMeasureClockPeriod.
1518: "
1519: INDEX { ippmMeasureOwner, ippmMeasureIndex }
1520: ::= { ippmAggregatedMeasureTable 1 }
1521:
1522:
1523: IppmAggregatedMeasureEntry ::=
1524: SEQUENCE {
1525: ippmAggregatedMeasureHistoryOwner OwnerString,
1526: ippmAggregatedMeasureHistoryOwnerIndex Integer32,
1527: ippmAggregatedMeasureHistoryMetric Integer32
1528: }
1529:
1530:
1531: ippmAggregatedMeasureHistoryOwner OBJECT-TYPE
1532: SYNTAX OwnerString
1533: MAX-ACCESS read-create
1534: STATUS current
1535: DESCRIPTION
1536: "The owner of the measure to summarize. "
1537: ::= { ippmAggregatedMeasureEntry 1 }
1538:
1539: ippmAggregatedMeasureHistoryOwnerIndex OBJECT-TYPE
1540: SYNTAX Integer32 (1.. 65535)
1541: MAX-ACCESS read-create
1542: STATUS current
1543: DESCRIPTION
1544: "The owner index of the measure to summarize. "
1545: ::= { ippmAggregatedMeasureEntry 2 }
1546:
1547: ippmAggregatedMeasureHistoryMetric OBJECT-TYPE
1548: SYNTAX Integer32
1549: MAX-ACCESS read-create
1550: STATUS current
1551: DESCRIPTION
1552: "The metric of the measure to summarize. "
1553: ::= { ippmAggregatedMeasureEntry 3 }
1554:
1555:
1556: --
1557: -- ippmReportGroup
1558: --
1559:
1560: --
1561: --
1562: -- ippmReportSetupTable
1563: --
1564: --
1565: ippmReportSetupTable OBJECT-TYPE
1566: SYNTAX SEQUENCE OF IppmReportSetupEntry
1567: MAX-ACCESS not-accessible
1568: STATUS current
1569: DESCRIPTION
1570: "The ippmReportSetupTable is a list of definition of reports. It
1571: defines the results of a network or aggregated measures which are to
1572: report. A report is saved in the ippmReportTable or sent to an
1573: application using a SNMP Trap, a SNMP inform PDU, an email or a SMS.
1574: The reporting task is not a batch action processed at the end of the
1575: measure. It is coupled with threshold detections and event filtering
1576: to deliver application level events and data while preserving
1577: scalability.
1578:
1579: It extends the definition of a measure: the definition of an measure
1580: may include the definition of a report."
1581: ::= { ippmReportGroup 1 }
1582:
1583: ippmReportSetupEntry OBJECT-TYPE
1584: SYNTAX IppmReportSetupEntry
1585: MAX-ACCESS not-accessible
1586: STATUS current
1587: DESCRIPTION
1588: "The report applies on the results of the measure which is extended
1589: by the current report definition.
1590:
1591: Typically the creation or a report sets both the values of the new
1592: measure and those of the new IppmReportSetupEntry.
1593: The ippmReportSetupDefinition describes the data and the events to
1594: include in the report. The definition consists in a list of tasks to
1595: perform on the results of the measure."
1596: INDEX { ippmMeasureOwner, ippmMeasureIndex }
1597: ::= { ippmReportSetupTable 1 }
1598:
1599: IppmReportSetupEntry ::=
1600: SEQUENCE {
1601: ippmReportSetupDefinition IppmReportDefinition,
1602: ippmReportSetupMetricThreshold
1603: Integer32,
1604: ippmReportSetupEventsDurationThreshold Integer32,
1605:
1606: ippmReportSetupNMS DisplayString
1607: }
1608:
1609: ippmReportSetupDefinition OBJECT-TYPE
1610: SYNTAX IppmReportDefinition
1611: MAX-ACCESS read-create
1612: STATUS current
1613: DESCRIPTION
1614: "The description of the events and actions which participate to
1615: the elaboration of the report.
1616: Send the report using the type of message selected by the bits 8
1617: to 12. The report consists in the results of the measure which have
1618: been saved in the ippmReportTable. If the onEventSendReport(7) bit is
1619: unset the report is not saved.
1620:
1621: The message sent is a notification defined in the
1622: ippmNotifications node. The notification sent depends on the step of
1623: the measure:
1624:
1625: + Singleton events are sent using the notification
1626: ippmSingletonAlarm;
1627: + Exceeded events duration are sent using the
1628: notification ippmEventsDurationExceededAlarm;
1629: + A report of a cycle of measure is sent using the
1630: notification ippmCycleOfMeasureReport;
1631: + A report of a complete measure is sent using the
1632: notification ippmCompletedMeasureReport;
1633:
1634: Example 1:
1635: The setup of an alarm to be sent to the owner in a SNMP Trap
1636: each time the staircase crosses the metric threshold value of 5:
1637:
1638: ippmReportSetupMetricThreshold 5
1639: ippmReportSetupDefinition {
1640: onSingleton(1),
1641: reportOnlyUptoDownMetricResults(4),
1642: inSNMPTrapPDU(8)
1643: }
1644:
1645: Example 2:
1646: The setup of a report to be sent to the owner in a SNMP
1647: informRequestPDU per measure cycle. It reports the staircase values
1648: corresponding to a metric threshold of 5:
1649:
1650: ippmReportSetupMetricThreshold 5
1651: ippmReportSetupDefinition {
1652: onMeasureCycle(2),
1653: reportOnlyUptoDownMetricResults(4),
1654: inInformRequestPDU(10),
1655: clearHistory(13)
1656: }
1657:
1658: Default report:
1659: The default report provides the control protocol with an
1660: implicit mechanism to forward the result of a cycle of measure to the
1661: owner of the measure while deleting the results from the
1662: ippmHistoryTable on reception of the response to the InformRequestPDU
1663: :
1664: ippmReportSetupDefinition {
1665: onMeasureCycle(2),
1666: inInformRequestPDU(10),
1667: clearHistory(13)
1668: }
1669: "
1670: DEFVAL { { onMeasureCycle, inInformRequestPDU, clearHistory } }
1671: ::= { ippmReportSetupEntry 1 }
1672:
1673: ippmReportSetupMetricThreshold OBJECT-TYPE
1673: fyi -
info: previous definition of `ippmReportSetupMetricThreshold'
1674: SYNTAX Integer32
1675: MAX-ACCESS read-create
1676: STATUS current
1677: DESCRIPTION
1678: "An event is generated when the result of the measure exceeds
1679: the value of ippmReportSetupMetricThreshold.
1680: The threshold has the same unit as the metric. The metric unit
1681: is recorded in the object ippmMetricsUnit of this metric entry in the
1682: ippmMetricTable.
1683: "
1684: ::= { ippmReportSetupEntry 2 }
1685:
1686: ippmReportSetupEventsDurationThreshold OBJECT-TYPE
1687: SYNTAX Integer32
1688: UNITS "Seconds"
1689: MAX-ACCESS read-create
1690: STATUS current
1691: DESCRIPTION
1692: "An event is generated when the duration of a serie of results
1693: which are continuously over the metric threshold cross over the
1694: duration of the ippmReportSetupEventsDurationThreshold.
1695: "
1696: DEFVAL { 15 }
1697: ::= { ippmReportSetupEntry 3 }
1698:
1699: ippmReportSetupNMS OBJECT-TYPE
1700: SYNTAX DisplayString
1701: MAX-ACCESS read-create
1702: STATUS current
1703: DESCRIPTION
1704: "The recipient of the report may be provided in the setup. By
1705: default the recipient of the report is the owner of the measure. Its
1706: addresses are recorded in the ippmOwnersTable.
1707: "
1708: ::= { ippmReportSetupEntry 4 }
1709:
1710:
1711: --
1712: -- ippmReportTable
1713: --
1714: ippmReportTable OBJECT-TYPE
1715: SYNTAX SEQUENCE OF IppmReportEntry
1716: MAX-ACCESS not-accessible
1717: STATUS current
1718: DESCRIPTION
1719: "The ippmReportTable logs the results of the reports.
1720: The results consist in a subset of the results of a measure as
1721: described in the report definition. The activation of a up and down
1722: filtering in the report definition limits the results logged to those
1723: corresponding to major events.
1724: Excepted these points the ippmReportTable is identical
1725: to the ippmHistoryTable.
1726: "
1727:
1728: ::= { ippmReportGroup 2 }
1729:
1730:
1731: ippmReportEntry OBJECT-TYPE
1732: SYNTAX IppmReportEntry
1733: MAX-ACCESS not-accessible
1734: STATUS current
1735: DESCRIPTION
1736: "A report is a list of results of a measure. This sample is
1737: associated with the ippmReportSetupEntry which has set up the report.
1738: An ippmReportEntry entry is one of the results of an measure to
1739: report. The measure and the report definition are identified by the
1740: index members ippmMeasureOwner and ippmMeasureIndex.
1741:
1742: in the index :
1743:
1744: + ippmMeasureOwner and ippmMeasureIndex identify the
1745: ippmMeasureEntry and the ippmReportSetupEntry on whose behalf this
1746: report was created;
1747: + ippmMetricIndex identifies the ippmMetricEntry of the metric
1748: measured;
1749: + ippmReportTimeMark value is the absolute time when the value
1750: of the metric was measured.
1751:
1752:
1753: The ippmReportTimeMark value is the absolute time when the
1754: ippmHistoryValue was performed.
1755: IppmHistoryValue is the value of the metric measured at the time
1756: ippmReportTimeMark.
1757: "
1758: INDEX { ippmMeasureOwner, ippmMeasureIndex, ippmMetricIndex,
1759: ippmReportTimeMark }
1760: ::= { ippmReportTable 1 }
1761:
1762: IppmReportEntry ::=
1763: SEQUENCE {
1764: ippmReportTimeMark GMTDateAndTime,
1765: ippmReportValue Integer32
1766: }
1767: ippmReportTimeMark OBJECT-TYPE
1768: SYNTAX GMTDateAndTime
1769: MAX-ACCESS read-only
1770: STATUS current
1771: DESCRIPTION
1772: "The instant of the measure of the result."
1773: ::= { ippmReportEntry 1 }
1774:
1775: ippmReportValue OBJECT-TYPE
1776: SYNTAX Integer32
1777: MAX-ACCESS read-only
1778: STATUS current
1779: DESCRIPTION
1780:
1781: "The value."
1782: ::= { ippmReportEntry 2 }
1783:
1784:
1785: --
1786: -- ippmNotifications
1787: --
1788:
1789:
1790:
1791:
1792:
1793: ippmSingletonAlarm NOTIFICATION-TYPE
1794: OBJECTS {
1795: ippmReportSetupDefinition,
1796: ippmReportSetupMetricThreshold,
1797: ippmMetricUnit,
1798: ippmHistoryValue
1799: }
1800: STATUS current
1801: DESCRIPTION
1802: "A notification sent because 2 contiguous results are on
1803: opposite sides of the metric threshold value.
1804: The index of the included ippmReportSetupMetricThreshold
1805: object identifies
1806: the ippmMeasureEntry and the ippmResultSetupEntry that
1807: specified the threshold.
1808:
1809: The notification contains the instances of the
1810: ippmReportValue object which raised the threshold. The
1811: ippmHistoryTimeMark of the index identifies the time the
1812: event occurs.
1813: "
1814: ::= { ippmNotifications 1 }
1815:
1816: ippmEventsDurationExceededAlarm NOTIFICATION-TYPE
1817: OBJECTS {
1818: ippmReportSetupDefinition,
1819: ippmReportSetupEventsDurationThreshold,
1820: ippmMetricUnit,
1821: ippmHistoryValue
1822: }
1823: STATUS current
1824: DESCRIPTION
1825: "A notification sent when the duration of contiguous
1826: raising ippmReportSetupMetricThreshold exceeds the
1827: ippmReportSetupEventsDurationThreshold value. The index
1828: of the included ippmReportSetupDefinition object
1829: identifies
1830: the ippmMeasureEntry and the ippmResultSetupEntry that
1831: specified the report.
1832:
1833: The notification contains the instances of the
1834: ippmReportValue objects saved in the ippmReportTable for
1835: this report. The ippmHistoryTimeMark of the index
1836: identifies the time theses measures results where
1837: performed.
1838: "
1839: ::= { ippmNotifications 2 }
1840:
1841:
1842: ippmCycleOfMeasureReport NOTIFICATION-TYPE
1843: OBJECTS {
1844: ippmReportSetupDefinition,
1845: ippmMetricUnit,
1846: ippmHistoryValue
1847: }
1848: STATUS current
1849: DESCRIPTION
1850: "A notification sent when a measure cycle completes.
1851: The index of the included ippmReportSetupDefinition
1852: object identifies
1853: the ippmMeasureEntry and the ippmResultSetupEntry that
1854: specified the report.
1855:
1856: The notification contains the instances of the
1857: ippmReportValue objects saved in the ippmReportTable for
1858: this measure cycle. The ippmHistoryTimeMark of the index
1859: identifies the time the measures where performed.
1860: "
1861: ::= { ippmNotifications 3 }
1862:
1863:
1864: ippmCompletedMeasureReport NOTIFICATION-TYPE
1865: OBJECTS {
1866: ippmReportSetupDefinition,
1867: ippmMetricUnit,
1868: ippmHistoryValue
1869: }
1870: STATUS current
1871: DESCRIPTION
1872: "A notification sent when a measure completes.
1873: The index of the included ippmReportSetupDefinition
1874: object identifies
1875: the ippmMeasureEntry and the ippmResultSetupEntry that
1876: specified the report.
1877:
1878: The notification contains the instances of the
1879: ippmReportValue objects saved in the ippmReportTable for
1880: this measure cycle. The ippmHistoryTimeMark of the index
1881: identifies the time the measures where performed.
1882: "
1883: ::= { ippmNotifications 4 }
1884:
1885:
1886:
1887: --
1888: -- Compliance statements
1889: --
1890:
1891: ippmCompliance MODULE-COMPLIANCE
1892: STATUS current
1893: DESCRIPTION
1894: "The compliance statement for SNMP entities which
1895: implement the IPPM MIB"
1896: MODULE -- this module
1897: MANDATORY-GROUPS { ippmSystemGroup, ippmMeasureGroup,
1898: ippmNetworkMeasureGroup, ippmHistoryGroup }
1899: ::= { ippmCompliances 1 }
1900:
1901: END
1902:
1903: --
1904: --
1905: -- "Copyright (C) The Internet Society (2001). All Rights Reserved.
1906: --
1907: -- This document and translations of it may be copied and furnished to
1908: -- others, and derivative works that comment on or otherwise explain it
1909: -- or assist its implementation may be prepared, copied, published and
1910: -- distributed, in whole or in part, without restriction of any kind,
1911: -- provided that the above copyright notice and this paragraph are
1912: -- included on all such copies and derivative works. However, this
1913: -- document itself may not be modified in any way, such as by removing
1914: -- the copyright notice or references to the Internet Society or other
1915: -- Internet organizations, except as needed for the purpose of
1916: -- developing Internet standards in which case the procedures for
1917: -- copyrights defined in the Internet Standards process must be
1918: -- followed, or as required to translate it into languages other than
1919: -- English.
1920: --
1921: -- The limited permissions granted above are perpetual and will not be
1922: -- revoked by the Internet Society or its successors or assigns.
1923: --
1924: -- This document and the information contained herein is provided on an
1925: -- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1926: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1927: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1928: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1929: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1930:
1: -- extracted from draft-stephan-ippm-multicast-metrics-00.txt 2: -- at Fri May 14 06:20:56 2004
3: 4: IPPM-CONTROL-MIB DEFINITIONS ::= BEGIN 5: 6: IMPORTS 7: IppmMib, 8: InstantaneousUnidirectionalConnectivity, 9: InstantaneousBidirectionalConnectivity, 10: intervalUnidirectionalConnectivity , 11: intervalBidirectionalConnectivity, 12: intervalTemporalConnectivity, 13: onewayDelay, 14: onewayDelayPoissonStream, 15: onewayDelayPercentile, 16: onewayDelayMedian, 17: onewayDelayMinimum, 18: onewayDelayInversePercentile, 19: onewayPacketLoss, 20: onewayPacketLossPoissonStream, 21: onewayPacketLossAverage, 22: roundtripDelay, 23: roundtripDelayPoissonStream, 24: roundtripDelayPercentile, 25: roundtripDelayMedian, 26: roundtripDelayMinimum, 27: roundtripDelayInversePercentile 28: FROM IPPM-MIB28: error - identifier `IppmMib' cannot be imported from module `IPPM-MIB'
29: MODULE-IDENTITY,
30: NOTIFICATION-TYPE,
31: OBJECT-TYPE,
32: Integer32,
33: Counter32,
34: experimental
35: FROM SNMPv2-SMI
36: OwnerString
37: FROM RMON-MIB
38: protocolDir
39: FROM RMON2-MIB
40:
41: DisplayString,
42: TimeStamp,
43: DateAndTime,
44: TruthValue,
45: RowStatus,
46: StorageType,
47: TEXTUAL-CONVENTION
48: FROM SNMPv2-TC
49: MODULE-COMPLIANCE,
50: OBJECT-GROUP,
51: NOTIFICATION-GROUP
52: FROM SNMPv2-CONF;
53:
54:
55: ippmControlMib MODULE-IDENTITY
56: LAST-UPDATED "200202111200Z" -- Feb 21, 2002
57: ORGANIZATION "France Telecom - R&D"
58: CONTACT-INFO
59: "Postal : Emile Stephan
60: France Telecom - R&D, Dpt. CPN
61: 2, Avenue Pierre Marzin
62: Technopole Anticipa
63: 22307 Lannion Cedex
64: FRANCE
65: Tel: + 33 2 96 05 36 10
66: E-mail: emile.stephan@francetelecom.com"
67: DESCRIPTION
68: " This memo defines a portion of the Management Information Base
69: (MIB) for use with network management protocols in TCP/IP-based
70: internets. In particular, It defines a set of NOTIFICATION-TYPE used
71: to control IPPM metrics measures, pushing alarms and reporting the
72: measures results.
73:
74: --
75: -- to be assigned by IANA
76: --
77: ::= { experimental 10001 }
78:
79: --
80: -- IPPM multicast messages for the setup of the measure
81: -- and the reporting of the result.
82: --
83:
84: ippmMulticastInstantaneousMeasureSetup NOTIFICATION-TYPE
85: OBJECTS {
86: -- measure setup
87: ippmMeasureOwner,
88: ippmMeasureIndex,
89:
90: -- Network measure setup
91: ippmNetworkMeasureSrcTypeP,
92: ippmNetworkMeasureSrc,
93: ippmNetworkMeasureDstTypeP,
94: ippmNetworkMeasureDst,
95: ippmNetworkMeasureTimeoutDelay,
96:
97: -- report setup
98: ippmReportSetupNMS,
99: }
100: STATUS current
101: DESCRIPTION
102: "The definition of the setup of an instantaneous multicast
102: minor error -
revision for last update is missing
103: measure is sent by the broadcasting application or the probe in 104: the multicast channel using a SNMP trap defined in this 105: NOTIFICATION-TYPE. 106: 107: On reception of the ippmMulticastInstantaneousMeasureSetup 108: setup the receiver or the router: 109: 110: + timestamp the arrival time of the setup;110: severe - lexically unexpected character, skipping to end of line
111: + considers the following defaults values;111: severe - lexically unexpected character, skipping to end of line
112: + prepare the ippmMulticastInstantaneousMeasureReport112: severe - lexically unexpected character, skipping to end of line
113: notification; 114: + send the report using a SNMP Inform PDU.114: severe - lexically unexpected character, skipping to end of line
115:
116: Defaults values:
117:
118: IppmMeasureEntry default values:
119:
120: ippmMeasureName:
121: ippmMulticastInstantaneousMeasure;
122:
123: ippmMeasureMetrics: {
124: Type-P-One-way-Delay,
125: Type-P-One-way-Packet-Loss,
126: Type-P-Multicast-Instantaneous-Connectivity, (*)
126: severe -
lexically unexpected character, skipping to end of line
127: Type-P-spatial-hop-one-way-delay (*)127: severe - lexically unexpected character, skipping to end of line
128: }128: warning - warning: flushing recent incorrect declaration, see previous error(s)
129: 130: ippmMeasureBeginTime: 0130: warning - warning: redefinition of identifier `IPPM-MIB::ippmMeasureBeginTime'
131:
132: ippmMeasureClockPeriodUnit: 0
133: ippmMeasureClockPeriod: 0
134: ippmMeasureDurationUnit: 0
135: ippmMeasureDuration: 0
136: ippmMeasureHystorySize: 0
137: ippmMeasureStorageType: other
138: ippmMeasureStatus: createAndGo
139:
140: IppmNetworkMeasureEntry default values:
141:
142: IppmNetworkMeasureClockPattern: 0
143: IppmNetworkMeasureTimeoutDelay: 0
144: ippmNetworkMeasureL3PacketSize: 0
145: ippmNetworkMeasureDataPattern: 0
146:
147: IppmippmReportSetupEntry default values:
148:
149: IppmReportSetupDefinition: {
150: onSingleton,
151: inInformRequestPDU,
152: clearHistory
153:
154: }
154: warning -
warning: flushing recent incorrect declaration, see previous error(s)
155: 156: ippmReportSetupMetricThreshold: 0156: warning - warning: redefinition of identifier `IPPM-MIB::ippmReportSetupMetricThreshold'
157: ippmReportSetupEventsDurationThreshold: 0 158: 159: (*) only considered by routers.159: severe - lexically unexpected character, skipping to end of line
160: "
161: ::= { ippmControlMib 1 }
162:
163: ippmMulticastInstantaneousMeasureReport NOTIFICATION-TYPE
164: -- measure setup
165: ippmMeasureOwner,
166: ippmMeasureIndex,
167:
168: -- Network measure setup
169: ippmNetworkMeasureSrcTypeP,
170: ippmNetworkMeasureSrc,
171: ippmNetworkMeasureDstTypeP,
172: ippmNetworkMeasureDst,
173:
174: -- report of the measure
175:
176: -- timestamp
177: ippmHistoryTimeMark,
178:
179: -- value of the Type-P-One-way-Delay
180: ippmHistoryValue,
181:
182: -- value of the Type-P-One-way-Packet-Loss
183: ippmHistoryValue,
184:
185: -- value of the
186: -- Type-P-Multicast-Instantaneous-Connectivity (*)
187: ippmHistoryValue,
188:
189: -- value of the Type-P-spatial-hop-one-way-delay (*)
190: ippmHistoryValue
191:
192: }
193: STATUS current
194: DESCRIPTION
195: "This NOTIFICATION-TYPE is used by the receiver or the
196: router to push the result of the measure performed
197: according the ippmMulticastInstantaneousMeasureSetup
198: setup.
199:
200: (*) is only applicable for router.
200: severe -
lexically unexpected character, skipping to end of line
201: { comment:
202: This report definition has to be split to get one for
203: receiver and one for router.}
203: warning -
warning: flushing recent incorrect declaration, see previous error(s)
204: 205: Note:205: error - `Note' should start with a lower case letter
206: An ippmHistoryValue is indexed using the owner, the 207: owner index, the metric index and the timestamp (e.g.: 208: acme.1.6.0106150820100100). So the metric index208: minor error - leading zero(s) on a number
209: identifies which metric result (One-way-Delay, Packet-209: error - identifier `Packet-' illegally ends in a hyphen
210: Loss, Connectivity) the ippmHistoryValue carries."
211: ::= { ippmControlMib 2 }
212:
213:
214: END
215:
216: --
217: --
218: -- "Copyright (C) The Internet Society (2001). All Rights Reserved.
219: --
220: -- This document and translations of it may be copied and furnished to
221: -- others, and derivative works that comment on or otherwise explain it
222: -- or assist its implementation may be prepared, copied, published and
223: -- distributed, in whole or in part, without restriction of any kind,
224: -- provided that the above copyright notice and this paragraph are
225: -- included on all such copies and derivative works. However, this
226: -- document itself may not be modified in any way, such as by removing
227: -- the copyright notice or references to the Internet Society or other
228: -- Internet organizations, except as needed for the purpose of
229: -- developing Internet standards in which case the procedures for
230: -- copyrights defined in the Internet Standards process must be
231: -- followed, or as required to translate it into languages other than
232: -- English.
233: -- The limited permissions granted above are perpetual and will not be
234: -- revoked by the Internet Society or its successors or assigns.
235: --
236: -- This document and the information contained herein is provided on an
237: -- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
238: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
239: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
240: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
241: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
242: