1 DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN
4 MODULE-IDENTITY, OBJECT-TYPE,
6 NOTIFICATION-TYPE, Counter32,
7 Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI
8 TEXTUAL-CONVENTION, RowStatus,
9 TruthValue FROM SNMPv2-TC
12 MODULE-COMPLIANCE, OBJECT-GROUP,
13 NOTIFICATION-GROUP FROM SNMPv2-CONF
14 sysUpTime FROM SNMPv2-MIB
15 SnmpTagValue FROM SNMP-TARGET-MIB
16 SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
18 dismanEventMIB MODULE-IDENTITY
19 LAST-UPDATED "200010160000Z" -- 16 October 2000
20 ORGANIZATION "IETF Distributed Management Working Group"
21 CONTACT-INFO "Ramanathan Kavasseri
23 170 West Tasman Drive,
24 San Jose CA 95134-1706.
25 Phone: +1 408 526 4527
26 Email: ramk@cisco.com"
28 "The MIB module for defining event triggers and actions
29 for network management purposes."
32 REVISION "200010160000Z" -- 16 October 2000
33 DESCRIPTION "This is the initial version of this MIB.
34 Published as RFC 2981"
37 dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 }
39 -- Management Triggered Event (MTE) objects
41 mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 }
42 mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 }
43 mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 }
44 mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 }
47 -- Textual Conventions
50 FailureReason ::= TEXTUAL-CONVENTION
53 "Reasons for failures in an attempt to perform a management
56 The first group of errors, numbered less than 0, are related
57 to problems in sending the request. The existence of a
58 particular error code here does not imply that all
59 implementations are capable of sensing that error and
64 The second group, numbered greater than 0, are copied
65 directly from SNMP protocol operations and are intended to
66 carry exactly the meanings defined for the protocol as returned
69 localResourceLack some local resource such as memory
71 mteResourceSampleInstanceMaximum
73 badDestination unrecognized domain name or otherwise
74 invalid destination address
75 destinationUnreachable can't get to destination address
76 noResponse no response to SNMP request
77 badType the data syntax of a retrieved object
79 sampleOverrun another sample attempt occurred before
80 the previous one completed"
82 SYNTAX INTEGER { localResourceLack(-1),
84 destinationUnreachable(-3),
102 inconsistentValue(12),
103 resourceUnavailable(13),
106 authorizationError(16),
108 inconsistentName(18) }
112 -- Resource Control Section
115 mteResourceSampleMinimum OBJECT-TYPE
116 SYNTAX Integer32 (1..2147483647)
118 MAX-ACCESS read-write
121 "The minimum mteTriggerFrequency this system will
122 accept. A system may use the larger values of this minimum to
123 lessen the impact of constant sampling. For larger
124 sampling intervals the system samples less often and
125 suffers less overhead. This object provides a way to enforce
126 such lower overhead for all triggers created after it is
129 Unless explicitly resource limited, a system's value for
130 this object SHOULD be 1, allowing as small as a 1 second
131 interval for ongoing trigger sampling.
133 Changing this value will not invalidate an existing setting
134 of mteTriggerFrequency."
135 ::= { mteResource 1 }
137 mteResourceSampleInstanceMaximum OBJECT-TYPE
140 MAX-ACCESS read-write
143 "The maximum number of instance entries this system will
144 support for sampling.
146 These are the entries that maintain state, one for each
147 instance of each sampled object as selected by
148 mteTriggerValueID. Note that wildcarded objects result
149 in multiple instances of this state.
151 A value of 0 indicates no preset limit, that is, the limit
152 is dynamic based on system operation and resources.
154 Unless explicitly resource limited, a system's value for
155 this object SHOULD be 0.
157 Changing this value will not eliminate or inhibit existing
158 sample state but could prevent allocation of additional state
162 ::= { mteResource 2 }
164 mteResourceSampleInstances OBJECT-TYPE
170 "The number of currently active instance entries as
171 defined for mteResourceSampleInstanceMaximum."
172 ::= { mteResource 3 }
174 mteResourceSampleInstancesHigh OBJECT-TYPE
180 "The highest value of mteResourceSampleInstances that has
181 occurred since initialization of the management system."
182 ::= { mteResource 4 }
184 mteResourceSampleInstanceLacks OBJECT-TYPE
190 "The number of times this system could not take a new sample
191 because that allocation would have exceeded the limit set by
192 mteResourceSampleInstanceMaximum."
193 ::= { mteResource 5 }
201 mteTriggerFailures OBJECT-TYPE
207 "The number of times an attempt to check for a trigger
208 condition has failed. This counts individually for each
209 attempt in a group of targets or each attempt for a
219 mteTriggerTable OBJECT-TYPE
220 SYNTAX SEQUENCE OF MteTriggerEntry
221 MAX-ACCESS not-accessible
224 "A table of management event trigger information."
227 mteTriggerEntry OBJECT-TYPE
228 SYNTAX MteTriggerEntry
229 MAX-ACCESS not-accessible
232 "Information about a single trigger. Applications create and
233 delete entries using mteTriggerEntryStatus."
234 INDEX { mteOwner, IMPLIED mteTriggerName }
235 ::= { mteTriggerTable 1 }
237 MteTriggerEntry ::= SEQUENCE {
238 mteOwner SnmpAdminString,
239 mteTriggerName SnmpAdminString,
240 mteTriggerComment SnmpAdminString,
242 mteTriggerSampleType INTEGER,
243 mteTriggerValueID OBJECT IDENTIFIER,
244 mteTriggerValueIDWildcard TruthValue,
245 mteTriggerTargetTag SnmpTagValue,
246 mteTriggerContextName SnmpAdminString,
247 mteTriggerContextNameWildcard TruthValue,
248 mteTriggerFrequency Unsigned32,
249 mteTriggerObjectsOwner SnmpAdminString,
250 mteTriggerObjects SnmpAdminString,
251 mteTriggerEnabled TruthValue,
252 mteTriggerEntryStatus RowStatus
256 SYNTAX SnmpAdminString (SIZE(0..32))
257 MAX-ACCESS not-accessible
262 "The owner of this entry. The exact semantics of this
263 string are subject to the security policy defined by the
264 security administrator."
265 ::= { mteTriggerEntry 1 }
267 mteTriggerName OBJECT-TYPE
268 SYNTAX SnmpAdminString (SIZE (1..32))
269 MAX-ACCESS not-accessible
272 "A locally-unique, administratively assigned name for the
273 trigger within the scope of mteOwner."
274 ::= { mteTriggerEntry 2 }
276 mteTriggerComment OBJECT-TYPE
277 SYNTAX SnmpAdminString
278 MAX-ACCESS read-create
281 "A description of the trigger's function and use."
283 ::= { mteTriggerEntry 3 }
285 mteTriggerTest OBJECT-TYPE
286 SYNTAX BITS { existence(0), boolean(1), threshold(2) }
287 MAX-ACCESS read-create
290 "The type of trigger test to perform. For 'boolean' and
291 'threshold' tests, the object at mteTriggerValueID MUST
292 evaluate to an integer, that is, anything that ends up encoded
293 for transmission (that is, in BER, not ASN.1) as an integer.
295 For 'existence', the specific test is as selected by
296 mteTriggerExistenceTest. When an object appears, vanishes
297 or changes value, the trigger fires. If the object's
298 appearance caused the trigger firing, the object MUST
299 vanish before the trigger can be fired again for it, and
300 vice versa. If the trigger fired due to a change in the
301 object's value, it will be fired again on every successive
302 value change for that object.
304 For 'boolean', the specific test is as selected by
305 mteTriggerBooleanTest. If the test result is true the trigger
306 fires. The trigger will not fire again until the value has
307 become false and come back to true.
309 For 'threshold' the test works as described below for
312 mteTriggerThresholdStartup, mteTriggerThresholdRising, and
313 mteTriggerThresholdFalling.
315 Note that combining 'boolean' and 'threshold' tests on the
316 same object may be somewhat redundant."
317 DEFVAL { { boolean } }
318 ::= { mteTriggerEntry 4 }
320 mteTriggerSampleType OBJECT-TYPE
321 SYNTAX INTEGER { absoluteValue(1), deltaValue(2) }
322 MAX-ACCESS read-create
325 "The type of sampling to perform.
327 An 'absoluteValue' sample requires only a single sample to be
328 meaningful, and is exactly the value of the object at
329 mteTriggerValueID at the sample time.
331 A 'deltaValue' requires two samples to be meaningful and is
332 thus not available for testing until the second and subsequent
333 samples after the object at mteTriggerValueID is first found
334 to exist. It is the difference between the two samples. For
335 unsigned values it is always positive, based on unsigned
336 arithmetic. For signed values it can be positive or negative.
338 For SNMP counters to be meaningful they should be sampled as a
341 For 'deltaValue' mteTriggerDeltaTable contains further
344 If only 'existence' is set in mteTriggerTest this object has
346 DEFVAL { absoluteValue }
347 ::= { mteTriggerEntry 5 }
349 mteTriggerValueID OBJECT-TYPE
350 SYNTAX OBJECT IDENTIFIER
351 MAX-ACCESS read-create
354 "The object identifier of the MIB object to sample to see
355 if the trigger should fire.
357 This may be wildcarded by truncating all or part of the
358 instance portion, in which case the value is obtained
359 as if with a GetNext function, checking multiple values
362 if they exist. If such wildcarding is applied,
363 mteTriggerValueIDWildcard must be 'true' and if not it must
366 Bad object identifiers or a mismatch between truncating the
367 identifier and the value of mteTriggerValueIDWildcard result
368 in operation as one would expect when providing the wrong
369 identifier to a Get or GetNext operation. The Get will fail
370 or get the wrong object. The GetNext will indeed get whatever
371 is next, proceeding until it runs past the initial part of the
372 identifier and perhaps many unintended objects for confusing
373 results. If the value syntax of those objects is not usable,
374 that results in a 'badType' error that terminates the scan.
376 Each instance that fills the wildcard is independent of any
377 additional instances, that is, wildcarded objects operate
378 as if there were a separate table entry for each instance
379 that fills the wildcard without having to actually predict
380 all possible instances ahead of time."
381 DEFVAL { zeroDotZero }
382 ::= { mteTriggerEntry 6 }
384 mteTriggerValueIDWildcard OBJECT-TYPE
386 MAX-ACCESS read-create
389 "Control for whether mteTriggerValueID is to be treated as
390 fully-specified or wildcarded, with 'true' indicating wildcard."
392 ::= { mteTriggerEntry 7 }
394 mteTriggerTargetTag OBJECT-TYPE
396 MAX-ACCESS read-create
399 "The tag for the target(s) from which to obtain the condition
402 A length of 0 indicates the local system. In this case,
403 access to the objects indicated by mteTriggerValueID is under
404 the security credentials of the requester that set
405 mteTriggerEntryStatus to 'active'. Those credentials are the
406 input parameters for isAccessAllowed from the Architecture for
407 Describing SNMP Management Frameworks.
409 Otherwise access rights are checked according to the security
412 parameters resulting from the tag."
414 ::= { mteTriggerEntry 8 }
416 mteTriggerContextName OBJECT-TYPE
417 SYNTAX SnmpAdminString
418 MAX-ACCESS read-create
421 "The management context from which to obtain mteTriggerValueID.
423 This may be wildcarded by leaving characters off the end. For
424 example use 'Repeater' to wildcard to 'Repeater1',
425 'Repeater2', 'Repeater-999.87b', and so on. To indicate such
426 wildcarding is intended, mteTriggerContextNameWildcard must
429 Each instance that fills the wildcard is independent of any
430 additional instances, that is, wildcarded objects operate
431 as if there were a separate table entry for each instance
432 that fills the wildcard without having to actually predict
433 all possible instances ahead of time.
435 Operation of this feature assumes that the local system has a
436 list of available contexts against which to apply the
437 wildcard. If the objects are being read from the local
438 system, this is clearly the system's own list of contexts.
439 For a remote system a local version of such a list is not
440 defined by any current standard and may not be available, so
441 this function MAY not be supported."
443 ::= { mteTriggerEntry 9 }
445 mteTriggerContextNameWildcard OBJECT-TYPE
447 MAX-ACCESS read-create
450 "Control for whether mteTriggerContextName is to be treated as
451 fully-specified or wildcarded, with 'true' indicating wildcard."
453 ::= { mteTriggerEntry 10 }
455 mteTriggerFrequency OBJECT-TYPE
458 MAX-ACCESS read-create
463 "The number of seconds to wait between trigger samples. To
464 encourage consistency in sampling, the interval is measured
465 from the beginning of one check to the beginning of the next
466 and the timer is restarted immediately when it expires, not
467 when the check completes.
469 If the next sample begins before the previous one completed the
470 system may either attempt to make the check or treat this as an
471 error condition with the error 'sampleOverrun'.
473 A frequency of 0 indicates instantaneous recognition of the
474 condition. This is not possible in many cases, but may
475 be supported in cases where it makes sense and the system is
476 able to do so. This feature allows the MIB to be used in
477 implementations where such interrupt-driven behavior is
478 possible and is not likely to be supported for all MIB objects
479 even then since such sampling generally has to be tightly
480 integrated into low-level code.
482 Systems that can support this SHOULD document those cases
483 where it can be used. In cases where it can not, setting this
484 object to 0 should be disallowed."
486 ::= { mteTriggerEntry 11 }
488 mteTriggerObjectsOwner OBJECT-TYPE
489 SYNTAX SnmpAdminString (SIZE (0..32))
490 MAX-ACCESS read-create
493 "To go with mteTriggerObjects, the mteOwner of a group of
494 objects from mteObjectsTable."
496 ::= { mteTriggerEntry 12 }
498 mteTriggerObjects OBJECT-TYPE
499 SYNTAX SnmpAdminString (SIZE (0..32))
500 MAX-ACCESS read-create
503 "The mteObjectsName of a group of objects from
504 mteObjectsTable. These objects are to be added to any
505 Notification resulting from the firing of this trigger.
507 A list of objects may also be added based on the event or on
508 the value of mteTriggerTest.
512 A length of 0 indicates no additional objects."
514 ::= { mteTriggerEntry 13 }
516 mteTriggerEnabled OBJECT-TYPE
518 MAX-ACCESS read-create
521 "A control to allow a trigger to be configured but not used.
522 When the value is 'false' the trigger is not sampled."
524 ::= { mteTriggerEntry 14 }
526 mteTriggerEntryStatus OBJECT-TYPE
528 MAX-ACCESS read-create
531 "The control that allows creation and deletion of entries.
532 Once made active an entry may not be modified except to
534 ::= { mteTriggerEntry 15 }
537 -- Trigger Delta Table
540 mteTriggerDeltaTable OBJECT-TYPE
541 SYNTAX SEQUENCE OF MteTriggerDeltaEntry
542 MAX-ACCESS not-accessible
545 "A table of management event trigger information for delta
549 mteTriggerDeltaEntry OBJECT-TYPE
550 SYNTAX MteTriggerDeltaEntry
551 MAX-ACCESS not-accessible
554 "Information about a single trigger's delta sampling. Entries
555 automatically exist in this this table for each mteTriggerEntry
556 that has mteTriggerSampleType set to 'deltaValue'."
557 INDEX { mteOwner, IMPLIED mteTriggerName }
558 ::= { mteTriggerDeltaTable 1 }
562 MteTriggerDeltaEntry ::= SEQUENCE {
563 mteTriggerDeltaDiscontinuityID OBJECT IDENTIFIER,
564 mteTriggerDeltaDiscontinuityIDWildcard TruthValue,
565 mteTriggerDeltaDiscontinuityIDType INTEGER
568 sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 }
570 mteTriggerDeltaDiscontinuityID OBJECT-TYPE
571 SYNTAX OBJECT IDENTIFIER
572 MAX-ACCESS read-write
575 "The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or
576 DateAndTime object that indicates a discontinuity in the value
577 at mteTriggerValueID.
579 The OID may be for a leaf object (e.g. sysUpTime.0) or may
580 be wildcarded to match mteTriggerValueID.
582 This object supports normal checking for a discontinuity in a
583 counter. Note that if this object does not point to sysUpTime
584 discontinuity checking MUST still check sysUpTime for an overall
587 If the object identified is not accessible the sample attempt
588 is in error, with the error code as from an SNMP request.
590 Bad object identifiers or a mismatch between truncating the
591 identifier and the value of mteDeltaDiscontinuityIDWildcard
592 result in operation as one would expect when providing the
593 wrong identifier to a Get operation. The Get will fail or get
594 the wrong object. If the value syntax of those objects is not
595 usable, that results in an error that terminates the sample
596 with a 'badType' error code."
597 DEFVAL { sysUpTimeInstance }
598 ::= { mteTriggerDeltaEntry 1 }
600 mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE
602 MAX-ACCESS read-write
605 "Control for whether mteTriggerDeltaDiscontinuityID is to be
606 treated as fully-specified or wildcarded, with 'true'
607 indicating wildcard. Note that the value of this object will
608 be the same as that of the corresponding instance of
609 mteTriggerValueIDWildcard when the corresponding
612 mteTriggerSampleType is 'deltaValue'."
614 ::= { mteTriggerDeltaEntry 2 }
616 mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE
617 SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) }
618 MAX-ACCESS read-write
621 "The value 'timeTicks' indicates the
622 mteTriggerDeltaDiscontinuityID of this row is of syntax
623 TimeTicks. The value 'timeStamp' indicates syntax TimeStamp.
624 The value 'dateAndTime' indicates syntax DateAndTime."
626 ::= { mteTriggerDeltaEntry 3 }
629 -- Trigger Existence Table
632 mteTriggerExistenceTable OBJECT-TYPE
633 SYNTAX SEQUENCE OF MteTriggerExistenceEntry
634 MAX-ACCESS not-accessible
637 "A table of management event trigger information for existence
641 mteTriggerExistenceEntry OBJECT-TYPE
642 SYNTAX MteTriggerExistenceEntry
643 MAX-ACCESS not-accessible
646 "Information about a single existence trigger. Entries
647 automatically exist in this this table for each mteTriggerEntry
648 that has 'existence' set in mteTriggerTest."
649 INDEX { mteOwner, IMPLIED mteTriggerName }
650 ::= { mteTriggerExistenceTable 1 }
652 MteTriggerExistenceEntry ::= SEQUENCE {
653 mteTriggerExistenceTest BITS,
654 mteTriggerExistenceStartup BITS,
655 mteTriggerExistenceObjectsOwner SnmpAdminString,
656 mteTriggerExistenceObjects SnmpAdminString,
657 mteTriggerExistenceEventOwner SnmpAdminString,
658 mteTriggerExistenceEvent SnmpAdminString
662 mteTriggerExistenceTest OBJECT-TYPE
663 SYNTAX BITS { present(0), absent(1), changed(2) }
664 MAX-ACCESS read-write
667 "The type of existence test to perform. The trigger fires
668 when the object at mteTriggerValueID is seen to go from
669 present to absent, from absent to present, or to have it's
670 value changed, depending on which tests are selected:
672 present(0) - when this test is selected, the trigger fires
673 when the mteTriggerValueID object goes from absent to present.
675 absent(1) - when this test is selected, the trigger fires
676 when the mteTriggerValueID object goes from present to absent.
677 changed(2) - when this test is selected, the trigger fires
678 the mteTriggerValueID object value changes.
680 Once the trigger has fired for either presence or absence it
681 will not fire again for that state until the object has been
682 to the other state. "
683 DEFVAL { { present, absent } }
684 ::= { mteTriggerExistenceEntry 1 }
686 mteTriggerExistenceStartup OBJECT-TYPE
687 SYNTAX BITS { present(0), absent(1) }
688 MAX-ACCESS read-write
691 "Control for whether an event may be triggered when this entry
692 is first set to 'active' and the test specified by
693 mteTriggerExistenceTest is true. Setting an option causes
694 that trigger to fire when its test is true."
695 DEFVAL { { present, absent } }
696 ::= { mteTriggerExistenceEntry 2 }
698 mteTriggerExistenceObjectsOwner OBJECT-TYPE
699 SYNTAX SnmpAdminString (SIZE (0..32))
700 MAX-ACCESS read-write
703 "To go with mteTriggerExistenceObjects, the mteOwner of a
704 group of objects from mteObjectsTable."
706 ::= { mteTriggerExistenceEntry 3 }
708 mteTriggerExistenceObjects OBJECT-TYPE
709 SYNTAX SnmpAdminString (SIZE (0..32))
712 MAX-ACCESS read-write
715 "The mteObjectsName of a group of objects from
716 mteObjectsTable. These objects are to be added to any
717 Notification resulting from the firing of this trigger for
720 A list of objects may also be added based on the overall
721 trigger, the event or other settings in mteTriggerTest.
723 A length of 0 indicates no additional objects."
725 ::= { mteTriggerExistenceEntry 4 }
727 mteTriggerExistenceEventOwner OBJECT-TYPE
728 SYNTAX SnmpAdminString (SIZE (0..32))
729 MAX-ACCESS read-write
732 "To go with mteTriggerExistenceEvent, the mteOwner of an event
733 entry from the mteEventTable."
735 ::= { mteTriggerExistenceEntry 5 }
737 mteTriggerExistenceEvent OBJECT-TYPE
738 SYNTAX SnmpAdminString (SIZE (0..32))
739 MAX-ACCESS read-write
742 "The mteEventName of the event to invoke when mteTriggerType is
743 'existence' and this trigger fires. A length of 0 indicates no
746 ::= { mteTriggerExistenceEntry 6 }
749 -- Trigger Boolean Table
752 mteTriggerBooleanTable OBJECT-TYPE
753 SYNTAX SEQUENCE OF MteTriggerBooleanEntry
754 MAX-ACCESS not-accessible
757 "A table of management event trigger information for boolean
762 mteTriggerBooleanEntry OBJECT-TYPE
763 SYNTAX MteTriggerBooleanEntry
764 MAX-ACCESS not-accessible
767 "Information about a single boolean trigger. Entries
768 automatically exist in this this table for each mteTriggerEntry
769 that has 'boolean' set in mteTriggerTest."
770 INDEX { mteOwner, IMPLIED mteTriggerName }
771 ::= { mteTriggerBooleanTable 1 }
773 MteTriggerBooleanEntry ::= SEQUENCE {
774 mteTriggerBooleanComparison INTEGER,
775 mteTriggerBooleanValue Integer32,
776 mteTriggerBooleanStartup TruthValue,
777 mteTriggerBooleanObjectsOwner SnmpAdminString,
778 mteTriggerBooleanObjects SnmpAdminString,
779 mteTriggerBooleanEventOwner SnmpAdminString,
780 mteTriggerBooleanEvent SnmpAdminString
783 mteTriggerBooleanComparison OBJECT-TYPE
784 SYNTAX INTEGER { unequal(1), equal(2),
785 less(3), lessOrEqual(4),
786 greater(5), greaterOrEqual(6) }
787 MAX-ACCESS read-write
790 "The type of boolean comparison to perform.
792 The value at mteTriggerValueID is compared to
793 mteTriggerBooleanValue, so for example if
794 mteTriggerBooleanComparison is 'less' the result would be true
795 if the value at mteTriggerValueID is less than the value of
796 mteTriggerBooleanValue."
798 ::= { mteTriggerBooleanEntry 1 }
800 mteTriggerBooleanValue OBJECT-TYPE
802 MAX-ACCESS read-write
805 "The value to use for the test specified by
806 mteTriggerBooleanTest."
808 ::= { mteTriggerBooleanEntry 2 }
812 mteTriggerBooleanStartup OBJECT-TYPE
814 MAX-ACCESS read-write
817 "Control for whether an event may be triggered when this entry
818 is first set to 'active' or a new instance of the object at
819 mteTriggerValueID is found and the test specified by
820 mteTriggerBooleanComparison is true. In that case an event is
821 triggered if mteTriggerBooleanStartup is 'true'."
823 ::= { mteTriggerBooleanEntry 3 }
825 mteTriggerBooleanObjectsOwner OBJECT-TYPE
826 SYNTAX SnmpAdminString (SIZE (0..32))
827 MAX-ACCESS read-write
830 "To go with mteTriggerBooleanObjects, the mteOwner of a group
831 of objects from mteObjectsTable."
833 ::= { mteTriggerBooleanEntry 4 }
835 mteTriggerBooleanObjects OBJECT-TYPE
836 SYNTAX SnmpAdminString (SIZE (0..32))
837 MAX-ACCESS read-write
840 "The mteObjectsName of a group of objects from
841 mteObjectsTable. These objects are to be added to any
842 Notification resulting from the firing of this trigger for
845 A list of objects may also be added based on the overall
846 trigger, the event or other settings in mteTriggerTest.
848 A length of 0 indicates no additional objects."
850 ::= { mteTriggerBooleanEntry 5 }
852 mteTriggerBooleanEventOwner OBJECT-TYPE
853 SYNTAX SnmpAdminString (SIZE (0..32))
854 MAX-ACCESS read-write
857 "To go with mteTriggerBooleanEvent, the mteOwner of an event
858 entry from mteEventTable."
862 ::= { mteTriggerBooleanEntry 6 }
864 mteTriggerBooleanEvent OBJECT-TYPE
865 SYNTAX SnmpAdminString (SIZE (0..32))
866 MAX-ACCESS read-write
869 "The mteEventName of the event to invoke when mteTriggerType is
870 'boolean' and this trigger fires. A length of 0 indicates no
873 ::= { mteTriggerBooleanEntry 7 }
876 -- Trigger Threshold Table
879 mteTriggerThresholdTable OBJECT-TYPE
880 SYNTAX SEQUENCE OF MteTriggerThresholdEntry
881 MAX-ACCESS not-accessible
884 "A table of management event trigger information for threshold
888 mteTriggerThresholdEntry OBJECT-TYPE
889 SYNTAX MteTriggerThresholdEntry
890 MAX-ACCESS not-accessible
893 "Information about a single threshold trigger. Entries
894 automatically exist in this table for each mteTriggerEntry
895 that has 'threshold' set in mteTriggerTest."
896 INDEX { mteOwner, IMPLIED mteTriggerName }
897 ::= { mteTriggerThresholdTable 1 }
899 MteTriggerThresholdEntry ::= SEQUENCE {
900 mteTriggerThresholdStartup INTEGER,
901 mteTriggerThresholdRising Integer32,
902 mteTriggerThresholdFalling Integer32,
903 mteTriggerThresholdDeltaRising Integer32,
904 mteTriggerThresholdDeltaFalling Integer32,
905 mteTriggerThresholdObjectsOwner SnmpAdminString,
906 mteTriggerThresholdObjects SnmpAdminString,
907 mteTriggerThresholdRisingEventOwner SnmpAdminString,
908 mteTriggerThresholdRisingEvent SnmpAdminString,
909 mteTriggerThresholdFallingEventOwner SnmpAdminString,
912 mteTriggerThresholdFallingEvent SnmpAdminString,
913 mteTriggerThresholdDeltaRisingEventOwner SnmpAdminString,
914 mteTriggerThresholdDeltaRisingEvent SnmpAdminString,
915 mteTriggerThresholdDeltaFallingEventOwner SnmpAdminString,
916 mteTriggerThresholdDeltaFallingEvent SnmpAdminString
919 mteTriggerThresholdStartup OBJECT-TYPE
920 SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) }
921 MAX-ACCESS read-write
924 "The event that may be triggered when this entry is first
925 set to 'active' and a new instance of the object at
926 mteTriggerValueID is found. If the first sample after this
927 instance becomes active is greater than or equal to
928 mteTriggerThresholdRising and mteTriggerThresholdStartup is
929 equal to 'rising' or 'risingOrFalling', then one
930 mteTriggerThresholdRisingEvent is triggered for that instance.
931 If the first sample after this entry becomes active is less
932 than or equal to mteTriggerThresholdFalling and
933 mteTriggerThresholdStartup is equal to 'falling' or
934 'risingOrFalling', then one mteTriggerThresholdRisingEvent is
935 triggered for that instance."
936 DEFVAL { risingOrFalling }
937 ::= { mteTriggerThresholdEntry 1 }
939 mteTriggerThresholdRising OBJECT-TYPE
941 MAX-ACCESS read-write
944 "A threshold value to check against if mteTriggerType is
947 When the current sampled value is greater than or equal to
948 this threshold, and the value at the last sampling interval
949 was less than this threshold, one
950 mteTriggerThresholdRisingEvent is triggered. That event is
951 also triggered if the first sample after this entry becomes
952 active is greater than or equal to this threshold and
953 mteTriggerThresholdStartup is equal to 'rising' or
956 After a rising event is generated, another such event is not
957 triggered until the sampled value falls below this threshold
958 and reaches mteTriggerThresholdFalling."
962 ::= { mteTriggerThresholdEntry 2 }
964 mteTriggerThresholdFalling OBJECT-TYPE
966 MAX-ACCESS read-write
969 "A threshold value to check against if mteTriggerType is
972 When the current sampled value is less than or equal to this
973 threshold, and the value at the last sampling interval was
974 greater than this threshold, one
975 mteTriggerThresholdFallingEvent is triggered. That event is
976 also triggered if the first sample after this entry becomes
977 active is less than or equal to this threshold and
978 mteTriggerThresholdStartup is equal to 'falling' or
981 After a falling event is generated, another such event is not
982 triggered until the sampled value rises above this threshold
983 and reaches mteTriggerThresholdRising."
985 ::= { mteTriggerThresholdEntry 3 }
987 mteTriggerThresholdDeltaRising OBJECT-TYPE
989 MAX-ACCESS read-write
992 "A threshold value to check against if mteTriggerType is
995 When the delta value (difference) between the current sampled
996 value (value(n)) and the previous sampled value (value(n-1))
997 is greater than or equal to this threshold,
998 and the delta value calculated at the last sampling interval
999 (i.e. value(n-1) - value(n-2)) was less than this threshold,
1000 one mteTriggerThresholdDeltaRisingEvent is triggered. That event
1001 is also triggered if the first delta value calculated after this
1002 entry becomes active, i.e. value(2) - value(1), where value(1)
1003 is the first sample taken of that instance, is greater than or
1004 equal to this threshold.
1006 After a rising event is generated, another such event is not
1007 triggered until the delta value falls below this threshold and
1008 reaches mteTriggerThresholdDeltaFalling."
1012 ::= { mteTriggerThresholdEntry 4 }
1014 mteTriggerThresholdDeltaFalling OBJECT-TYPE
1016 MAX-ACCESS read-write
1019 "A threshold value to check against if mteTriggerType is
1022 When the delta value (difference) between the current sampled
1023 value (value(n)) and the previous sampled value (value(n-1))
1024 is less than or equal to this threshold,
1025 and the delta value calculated at the last sampling interval
1026 (i.e. value(n-1) - value(n-2)) was greater than this threshold,
1027 one mteTriggerThresholdDeltaFallingEvent is triggered. That event
1028 is also triggered if the first delta value calculated after this
1029 entry becomes active, i.e. value(2) - value(1), where value(1)
1030 is the first sample taken of that instance, is less than or
1031 equal to this threshold.
1033 After a falling event is generated, another such event is not
1034 triggered until the delta value falls below this threshold and
1035 reaches mteTriggerThresholdDeltaRising."
1037 ::= { mteTriggerThresholdEntry 5 }
1039 mteTriggerThresholdObjectsOwner OBJECT-TYPE
1040 SYNTAX SnmpAdminString (SIZE (0..32))
1041 MAX-ACCESS read-write
1044 "To go with mteTriggerThresholdObjects, the mteOwner of a group
1045 of objects from mteObjectsTable."
1047 ::= { mteTriggerThresholdEntry 6 }
1049 mteTriggerThresholdObjects OBJECT-TYPE
1050 SYNTAX SnmpAdminString (SIZE (0..32))
1051 MAX-ACCESS read-write
1054 "The mteObjectsName of a group of objects from
1055 mteObjectsTable. These objects are to be added to any
1056 Notification resulting from the firing of this trigger for
1059 A list of objects may also be added based on the overall
1062 trigger, the event or other settings in mteTriggerTest.
1064 A length of 0 indicates no additional objects."
1066 ::= { mteTriggerThresholdEntry 7 }
1068 mteTriggerThresholdRisingEventOwner OBJECT-TYPE
1069 SYNTAX SnmpAdminString (SIZE (0..32))
1070 MAX-ACCESS read-write
1073 "To go with mteTriggerThresholdRisingEvent, the mteOwner of an
1074 event entry from mteEventTable."
1076 ::= { mteTriggerThresholdEntry 8 }
1078 mteTriggerThresholdRisingEvent OBJECT-TYPE
1079 SYNTAX SnmpAdminString (SIZE (0..32))
1080 MAX-ACCESS read-write
1083 "The mteEventName of the event to invoke when mteTriggerType is
1084 'threshold' and this trigger fires based on
1085 mteTriggerThresholdRising. A length of 0 indicates no event."
1087 ::= { mteTriggerThresholdEntry 9 }
1089 mteTriggerThresholdFallingEventOwner OBJECT-TYPE
1090 SYNTAX SnmpAdminString (SIZE (0..32))
1091 MAX-ACCESS read-write
1094 "To go with mteTriggerThresholdFallingEvent, the mteOwner of an
1095 event entry from mteEventTable."
1097 ::= { mteTriggerThresholdEntry 10 }
1099 mteTriggerThresholdFallingEvent OBJECT-TYPE
1100 SYNTAX SnmpAdminString (SIZE (0..32))
1101 MAX-ACCESS read-write
1104 "The mteEventName of the event to invoke when mteTriggerType is
1105 'threshold' and this trigger fires based on
1106 mteTriggerThresholdFalling. A length of 0 indicates no event."
1108 ::= { mteTriggerThresholdEntry 11 }
1112 mteTriggerThresholdDeltaRisingEventOwner OBJECT-TYPE
1113 SYNTAX SnmpAdminString (SIZE (0..32))
1114 MAX-ACCESS read-write
1117 "To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner
1118 of an event entry from mteEventTable."
1120 ::= { mteTriggerThresholdEntry 12 }
1122 mteTriggerThresholdDeltaRisingEvent OBJECT-TYPE
1123 SYNTAX SnmpAdminString (SIZE (0..32))
1124 MAX-ACCESS read-write
1127 "The mteEventName of the event to invoke when mteTriggerType is
1128 'threshold' and this trigger fires based on
1129 mteTriggerThresholdDeltaRising. A length of 0 indicates
1132 ::= { mteTriggerThresholdEntry 13 }
1134 mteTriggerThresholdDeltaFallingEventOwner OBJECT-TYPE
1135 SYNTAX SnmpAdminString (SIZE (0..32))
1136 MAX-ACCESS read-write
1139 "To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner
1140 of an event entry from mteEventTable."
1142 ::= { mteTriggerThresholdEntry 14 }
1144 mteTriggerThresholdDeltaFallingEvent OBJECT-TYPE
1145 SYNTAX SnmpAdminString (SIZE (0..32))
1146 MAX-ACCESS read-write
1149 "The mteEventName of the event to invoke when mteTriggerType is
1150 'threshold' and this trigger fires based on
1151 mteTriggerThresholdDeltaFalling. A length of 0 indicates
1154 ::= { mteTriggerThresholdEntry 15 }
1162 mteObjectsTable OBJECT-TYPE
1163 SYNTAX SEQUENCE OF MteObjectsEntry
1164 MAX-ACCESS not-accessible
1167 "A table of objects that can be added to notifications based
1168 on the trigger, trigger test, or event, as pointed to by
1169 entries in those tables."
1170 ::= { mteObjects 1 }
1172 mteObjectsEntry OBJECT-TYPE
1173 SYNTAX MteObjectsEntry
1174 MAX-ACCESS not-accessible
1177 "A group of objects. Applications create and delete entries
1178 using mteObjectsEntryStatus.
1180 When adding objects to a notification they are added in the
1181 lexical order of their index in this table. Those associated
1182 with a trigger come first, then trigger test, then event."
1183 INDEX { mteOwner, mteObjectsName, mteObjectsIndex }
1184 ::= { mteObjectsTable 1 }
1186 MteObjectsEntry ::= SEQUENCE {
1187 mteObjectsName SnmpAdminString,
1188 mteObjectsIndex Unsigned32,
1189 mteObjectsID OBJECT IDENTIFIER,
1190 mteObjectsIDWildcard TruthValue,
1191 mteObjectsEntryStatus RowStatus
1194 mteObjectsName OBJECT-TYPE
1195 SYNTAX SnmpAdminString (SIZE (1..32))
1196 MAX-ACCESS not-accessible
1199 "A locally-unique, administratively assigned name for a group
1201 ::= { mteObjectsEntry 1 }
1203 mteObjectsIndex OBJECT-TYPE
1204 SYNTAX Unsigned32 (1..4294967295)
1205 MAX-ACCESS not-accessible
1208 "An arbitrary integer for the purpose of identifying
1209 individual objects within a mteObjectsName group.
1212 Objects within a group are placed in the notification in the
1213 numerical order of this index.
1215 Groups are placed in the notification in the order of the
1216 selections for overall trigger, trigger test, and event.
1217 Within trigger test they are in the same order as the
1218 numerical values of the bits defined for mteTriggerTest.
1220 Bad object identifiers or a mismatch between truncating the
1221 identifier and the value of mteDeltaDiscontinuityIDWildcard
1222 result in operation as one would expect when providing the
1223 wrong identifier to a Get operation. The Get will fail or get
1224 the wrong object. If the object is not available it is omitted
1225 from the notification."
1226 ::= { mteObjectsEntry 2 }
1228 mteObjectsID OBJECT-TYPE
1229 SYNTAX OBJECT IDENTIFIER
1230 MAX-ACCESS read-create
1233 "The object identifier of a MIB object to add to a
1234 Notification that results from the firing of a trigger.
1236 This may be wildcarded by truncating all or part of the
1237 instance portion, in which case the instance portion of the
1238 OID for obtaining this object will be the same as that used
1239 in obtaining the mteTriggerValueID that fired. If such
1240 wildcarding is applied, mteObjectsIDWildcard must be
1241 'true' and if not it must be 'false'.
1243 Each instance that fills the wildcard is independent of any
1244 additional instances, that is, wildcarded objects operate
1245 as if there were a separate table entry for each instance
1246 that fills the wildcard without having to actually predict
1247 all possible instances ahead of time."
1248 DEFVAL { zeroDotZero }
1249 ::= { mteObjectsEntry 3 }
1251 mteObjectsIDWildcard OBJECT-TYPE
1253 MAX-ACCESS read-create
1256 "Control for whether mteObjectsID is to be treated as
1257 fully-specified or wildcarded, with 'true' indicating wildcard."
1259 ::= { mteObjectsEntry 4 }
1262 mteObjectsEntryStatus OBJECT-TYPE
1264 MAX-ACCESS read-create
1267 "The control that allows creation and deletion of entries.
1268 Once made active an entry MAY not be modified except to
1270 ::= { mteObjectsEntry 5 }
1278 mteEventFailures OBJECT-TYPE
1280 MAX-ACCESS read-only
1283 "The number of times an attempt to invoke an event
1284 has failed. This counts individually for each
1285 attempt in a group of targets or each attempt for a
1286 wildcarded trigger object."
1293 mteEventTable OBJECT-TYPE
1294 SYNTAX SEQUENCE OF MteEventEntry
1295 MAX-ACCESS not-accessible
1298 "A table of management event action information."
1301 mteEventEntry OBJECT-TYPE
1302 SYNTAX MteEventEntry
1303 MAX-ACCESS not-accessible
1306 "Information about a single event. Applications create and
1307 delete entries using mteEventEntryStatus."
1308 INDEX { mteOwner, IMPLIED mteEventName }
1309 ::= { mteEventTable 1 }
1312 MteEventEntry ::= SEQUENCE {
1313 mteEventName SnmpAdminString,
1314 mteEventComment SnmpAdminString,
1315 mteEventActions BITS,
1316 mteEventEnabled TruthValue,
1317 mteEventEntryStatus RowStatus
1320 mteEventName OBJECT-TYPE
1321 SYNTAX SnmpAdminString (SIZE (1..32))
1322 MAX-ACCESS not-accessible
1325 "A locally-unique, administratively assigned name for the
1327 ::= { mteEventEntry 1 }
1329 mteEventComment OBJECT-TYPE
1330 SYNTAX SnmpAdminString
1331 MAX-ACCESS read-create
1334 "A description of the event's function and use."
1336 ::= { mteEventEntry 2 }
1338 mteEventActions OBJECT-TYPE
1339 SYNTAX BITS { notification(0), set(1) }
1340 MAX-ACCESS read-create
1343 "The actions to perform when this event occurs.
1345 For 'notification', Traps and/or Informs are sent according
1346 to the configuration in the SNMP Notification MIB.
1348 For 'set', an SNMP Set operation is performed according to
1349 control values in this entry."
1350 DEFVAL { {} } -- No bits set.
1351 ::= { mteEventEntry 3 }
1353 mteEventEnabled OBJECT-TYPE
1355 MAX-ACCESS read-create
1358 "A control to allow an event to be configured but not used.
1359 When the value is 'false' the event does not execute even if
1364 ::= { mteEventEntry 4 }
1366 mteEventEntryStatus OBJECT-TYPE
1368 MAX-ACCESS read-create
1371 "The control that allows creation and deletion of entries.
1372 Once made active an entry MAY not be modified except to
1374 ::= { mteEventEntry 5 }
1377 -- Event Notification Table
1380 mteEventNotificationTable OBJECT-TYPE
1381 SYNTAX SEQUENCE OF MteEventNotificationEntry
1382 MAX-ACCESS not-accessible
1385 "A table of information about notifications to be sent as a
1386 consequence of management events."
1389 mteEventNotificationEntry OBJECT-TYPE
1390 SYNTAX MteEventNotificationEntry
1391 MAX-ACCESS not-accessible
1394 "Information about a single event's notification. Entries
1395 automatically exist in this this table for each mteEventEntry
1396 that has 'notification' set in mteEventActions."
1397 INDEX { mteOwner, IMPLIED mteEventName }
1398 ::= { mteEventNotificationTable 1 }
1400 MteEventNotificationEntry ::= SEQUENCE {
1401 mteEventNotification OBJECT IDENTIFIER,
1402 mteEventNotificationObjectsOwner SnmpAdminString,
1403 mteEventNotificationObjects SnmpAdminString
1406 mteEventNotification OBJECT-TYPE
1407 SYNTAX OBJECT IDENTIFIER
1408 MAX-ACCESS read-write
1413 "The object identifier from the NOTIFICATION-TYPE for the
1414 notification to use if metEventActions has 'notification' set."
1415 DEFVAL { zeroDotZero }
1416 ::= { mteEventNotificationEntry 1 }
1418 mteEventNotificationObjectsOwner OBJECT-TYPE
1419 SYNTAX SnmpAdminString (SIZE (0..32))
1420 MAX-ACCESS read-write
1423 "To go with mteEventNotificationObjects, the mteOwner of a
1424 group of objects from mteObjectsTable."
1426 ::= { mteEventNotificationEntry 2 }
1428 mteEventNotificationObjects OBJECT-TYPE
1429 SYNTAX SnmpAdminString (SIZE (0..32))
1430 MAX-ACCESS read-write
1433 "The mteObjectsName of a group of objects from
1434 mteObjectsTable if mteEventActions has 'notification' set.
1435 These objects are to be added to any Notification generated by
1438 Objects may also be added based on the trigger that stimulated
1441 A length of 0 indicates no additional objects."
1443 ::= { mteEventNotificationEntry 3 }
1449 mteEventSetTable OBJECT-TYPE
1450 SYNTAX SEQUENCE OF MteEventSetEntry
1451 MAX-ACCESS not-accessible
1454 "A table of management event action information."
1457 mteEventSetEntry OBJECT-TYPE
1458 SYNTAX MteEventSetEntry
1459 MAX-ACCESS not-accessible
1464 "Information about a single event's set option. Entries
1465 automatically exist in this this table for each mteEventEntry
1466 that has 'set' set in mteEventActions."
1467 INDEX { mteOwner, IMPLIED mteEventName }
1468 ::= { mteEventSetTable 1 }
1470 MteEventSetEntry ::= SEQUENCE {
1471 mteEventSetObject OBJECT IDENTIFIER,
1472 mteEventSetObjectWildcard TruthValue,
1473 mteEventSetValue Integer32,
1474 mteEventSetTargetTag SnmpTagValue,
1475 mteEventSetContextName SnmpAdminString,
1476 mteEventSetContextNameWildcard TruthValue
1479 mteEventSetObject OBJECT-TYPE
1480 SYNTAX OBJECT IDENTIFIER
1481 MAX-ACCESS read-write
1484 "The object identifier from the MIB object to set if
1485 mteEventActions has 'set' set.
1487 This object identifier may be wildcarded by leaving
1488 sub-identifiers off the end, in which case
1489 nteEventSetObjectWildCard must be 'true'.
1491 If mteEventSetObject is wildcarded the instance used to set the
1492 object to which it points is the same as the instance from the
1493 value of mteTriggerValueID that triggered the event.
1495 Each instance that fills the wildcard is independent of any
1496 additional instances, that is, wildcarded objects operate
1497 as if there were a separate table entry for each instance
1498 that fills the wildcard without having to actually predict
1499 all possible instances ahead of time.
1501 Bad object identifiers or a mismatch between truncating the
1502 identifier and the value of mteSetObjectWildcard
1503 result in operation as one would expect when providing the
1504 wrong identifier to a Set operation. The Set will fail or set
1505 the wrong object. If the value syntax of the destination
1506 object is not correct, the Set fails with the normal SNMP
1508 DEFVAL { zeroDotZero }
1509 ::= { mteEventSetEntry 1 }
1512 mteEventSetObjectWildcard OBJECT-TYPE
1514 MAX-ACCESS read-write
1517 "Control over whether mteEventSetObject is to be treated as
1518 fully-specified or wildcarded, with 'true' indicating wildcard
1519 if mteEventActions has 'set' set."
1521 ::= { mteEventSetEntry 2 }
1523 mteEventSetValue OBJECT-TYPE
1525 MAX-ACCESS read-write
1528 "The value to which to set the object at mteEventSetObject
1529 if mteEventActions has 'set' set."
1531 ::= { mteEventSetEntry 3 }
1533 mteEventSetTargetTag OBJECT-TYPE
1535 MAX-ACCESS read-write
1538 "The tag for the target(s) at which to set the object at
1539 mteEventSetObject to mteEventSetValue if mteEventActions
1542 Systems limited to self management MAY reject a non-zero
1543 length for the value of this object.
1545 A length of 0 indicates the local system. In this case,
1546 access to the objects indicated by mteEventSetObject is under
1547 the security credentials of the requester that set
1548 mteTriggerEntryStatus to 'active'. Those credentials are the
1549 input parameters for isAccessAllowed from the Architecture for
1550 Describing SNMP Management Frameworks.
1552 Otherwise access rights are checked according to the security
1553 parameters resulting from the tag."
1555 ::= { mteEventSetEntry 4 }
1557 mteEventSetContextName OBJECT-TYPE
1558 SYNTAX SnmpAdminString
1559 MAX-ACCESS read-write
1564 "The management context in which to set mteEventObjectID.
1565 if mteEventActions has 'set' set.
1567 This may be wildcarded by leaving characters off the end. To
1568 indicate such wildcarding mteEventSetContextNameWildcard must
1571 If this context name is wildcarded the value used to complete
1572 the wildcarding of mteTriggerContextName will be appended."
1574 ::= { mteEventSetEntry 5 }
1576 mteEventSetContextNameWildcard OBJECT-TYPE
1578 MAX-ACCESS read-write
1581 "Control for whether mteEventSetContextName is to be treated as
1582 fully-specified or wildcarded, with 'true' indicating wildcard
1583 if mteEventActions has 'set' set."
1585 ::= { mteEventSetEntry 6 }
1591 dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::=
1592 { dismanEventMIB 2 }
1593 dismanEventMIBNotifications OBJECT IDENTIFIER ::=
1594 { dismanEventMIBNotificationPrefix 0 }
1595 dismanEventMIBNotificationObjects OBJECT IDENTIFIER
1596 ::= { dismanEventMIBNotificationPrefix 1 }
1599 -- Notification Objects
1602 mteHotTrigger OBJECT-TYPE
1603 SYNTAX SnmpAdminString
1604 MAX-ACCESS accessible-for-notify
1607 "The name of the trigger causing the notification."
1608 ::= { dismanEventMIBNotificationObjects 1 }
1612 mteHotTargetName OBJECT-TYPE
1613 SYNTAX SnmpAdminString
1614 MAX-ACCESS accessible-for-notify
1617 "The SNMP Target MIB's snmpTargetAddrName related to the
1619 ::= { dismanEventMIBNotificationObjects 2 }
1621 mteHotContextName OBJECT-TYPE
1622 SYNTAX SnmpAdminString
1623 MAX-ACCESS accessible-for-notify
1626 "The context name related to the notification. This MUST be as
1627 fully-qualified as possible, including filling in wildcard
1628 information determined in processing."
1629 ::= { dismanEventMIBNotificationObjects 3 }
1631 mteHotOID OBJECT-TYPE
1632 SYNTAX OBJECT IDENTIFIER
1633 MAX-ACCESS accessible-for-notify
1636 "The object identifier of the destination object related to the
1637 notification. This MUST be as fully-qualified as possible,
1638 including filling in wildcard information determined in
1641 For a trigger-related notification this is from
1644 For a set failure this is from mteEventSetObject."
1645 ::= { dismanEventMIBNotificationObjects 4 }
1647 mteHotValue OBJECT-TYPE
1649 MAX-ACCESS accessible-for-notify
1652 "The value of the object at mteTriggerValueID when a
1654 ::= { dismanEventMIBNotificationObjects 5 }
1656 mteFailedReason OBJECT-TYPE
1657 SYNTAX FailureReason
1658 MAX-ACCESS accessible-for-notify
1663 "The reason for the failure of an attempt to check for a
1664 trigger condition or set an object in response to an event."
1665 ::= { dismanEventMIBNotificationObjects 6 }
1671 mteTriggerFired NOTIFICATION-TYPE
1672 OBJECTS { mteHotTrigger,
1679 "Notification that the trigger indicated by the object
1680 instances has fired, for triggers with mteTriggerType
1681 'boolean' or 'existence'."
1682 ::= { dismanEventMIBNotifications 1 }
1684 mteTriggerRising NOTIFICATION-TYPE
1685 OBJECTS { mteHotTrigger,
1692 "Notification that the rising threshold was met for triggers
1693 with mteTriggerType 'threshold'."
1694 ::= { dismanEventMIBNotifications 2 }
1696 mteTriggerFalling NOTIFICATION-TYPE
1697 OBJECTS { mteHotTrigger,
1704 "Notification that the falling threshold was met for triggers
1705 with mteTriggerType 'threshold'."
1706 ::= { dismanEventMIBNotifications 3 }
1708 mteTriggerFailure NOTIFICATION-TYPE
1709 OBJECTS { mteHotTrigger,
1718 "Notification that an attempt to check a trigger has failed.
1720 The network manager must enable this notification only with
1721 a certain fear and trembling, as it can easily crowd out more
1722 important information. It should be used only to help diagnose
1723 a problem that has appeared in the error counters and can not
1724 be found otherwise."
1725 ::= { dismanEventMIBNotifications 4 }
1727 mteEventSetFailure NOTIFICATION-TYPE
1728 OBJECTS { mteHotTrigger,
1735 "Notification that an attempt to do a set in response to an
1738 The network manager must enable this notification only with
1739 a certain fear and trembling, as it can easily crowd out more
1740 important information. It should be used only to help diagnose
1741 a problem that has appeared in the error counters and can not
1742 be found otherwise."
1743 ::= { dismanEventMIBNotifications 5 }
1749 dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 }
1750 dismanEventMIBCompliances OBJECT IDENTIFIER ::=
1751 { dismanEventMIBConformance 1 }
1752 dismanEventMIBGroups OBJECT IDENTIFIER ::=
1753 { dismanEventMIBConformance 2 }
1757 dismanEventMIBCompliance MODULE-COMPLIANCE
1762 "The compliance statement for entities which implement
1764 MODULE -- this module
1766 dismanEventResourceGroup,
1767 dismanEventTriggerGroup,
1768 dismanEventObjectsGroup,
1769 dismanEventEventGroup,
1770 dismanEventNotificationObjectGroup,
1771 dismanEventNotificationGroup
1774 OBJECT mteTriggerTargetTag
1775 MIN-ACCESS read-only
1777 "Write access is not required, thus limiting
1778 monitoring to the local system or pre-configured
1781 OBJECT mteEventSetTargetTag
1782 MIN-ACCESS read-only
1784 "Write access is not required, thus limiting
1785 setting to the local system or pre-configured
1788 OBJECT mteTriggerValueIDWildcard
1789 MIN-ACCESS read-only
1791 "Write access is not required, thus allowing
1792 the system not to implement wildcarding."
1794 OBJECT mteTriggerContextNameWildcard
1795 MIN-ACCESS read-only
1797 "Write access is not required, thus allowing
1798 the system not to implement wildcarding."
1801 OBJECT mteObjectsIDWildcard
1802 MIN-ACCESS read-only
1804 "Write access is not required, thus allowing
1805 the system not to implement wildcarding."
1807 OBJECT mteEventSetContextNameWildcard
1808 MIN-ACCESS read-only
1812 "Write access is not required, thus allowing
1813 the system not to implement wildcarding."
1815 ::= { dismanEventMIBCompliances 1 }
1817 -- Units of Conformance
1819 dismanEventResourceGroup OBJECT-GROUP
1821 mteResourceSampleMinimum,
1822 mteResourceSampleInstanceMaximum,
1823 mteResourceSampleInstances,
1824 mteResourceSampleInstancesHigh,
1825 mteResourceSampleInstanceLacks
1829 "Event resource status and control objects."
1830 ::= { dismanEventMIBGroups 1 }
1832 dismanEventTriggerGroup OBJECT-GROUP
1838 mteTriggerSampleType,
1840 mteTriggerValueIDWildcard,
1841 mteTriggerTargetTag,
1842 mteTriggerContextName,
1843 mteTriggerContextNameWildcard,
1844 mteTriggerFrequency,
1845 mteTriggerObjectsOwner,
1848 mteTriggerEntryStatus,
1850 mteTriggerDeltaDiscontinuityID,
1851 mteTriggerDeltaDiscontinuityIDWildcard,
1852 mteTriggerDeltaDiscontinuityIDType,
1853 mteTriggerExistenceTest,
1854 mteTriggerExistenceStartup,
1855 mteTriggerExistenceObjectsOwner,
1856 mteTriggerExistenceObjects,
1857 mteTriggerExistenceEventOwner,
1858 mteTriggerExistenceEvent,
1862 mteTriggerBooleanComparison,
1863 mteTriggerBooleanValue,
1864 mteTriggerBooleanStartup,
1865 mteTriggerBooleanObjectsOwner,
1866 mteTriggerBooleanObjects,
1867 mteTriggerBooleanEventOwner,
1868 mteTriggerBooleanEvent,
1870 mteTriggerThresholdStartup,
1871 mteTriggerThresholdObjectsOwner,
1872 mteTriggerThresholdObjects,
1873 mteTriggerThresholdRising,
1874 mteTriggerThresholdFalling,
1875 mteTriggerThresholdDeltaRising,
1876 mteTriggerThresholdDeltaFalling,
1877 mteTriggerThresholdRisingEventOwner,
1878 mteTriggerThresholdRisingEvent,
1879 mteTriggerThresholdFallingEventOwner,
1880 mteTriggerThresholdFallingEvent,
1881 mteTriggerThresholdDeltaRisingEventOwner,
1882 mteTriggerThresholdDeltaRisingEvent,
1883 mteTriggerThresholdDeltaFallingEventOwner,
1884 mteTriggerThresholdDeltaFallingEvent
1889 ::= { dismanEventMIBGroups 2 }
1891 dismanEventObjectsGroup OBJECT-GROUP
1894 mteObjectsIDWildcard,
1895 mteObjectsEntryStatus
1899 "Supplemental objects."
1900 ::= { dismanEventMIBGroups 3 }
1902 dismanEventEventGroup OBJECT-GROUP
1909 mteEventEntryStatus,
1912 mteEventNotification,
1913 mteEventNotificationObjectsOwner,
1914 mteEventNotificationObjects,
1917 mteEventSetObjectWildcard,
1919 mteEventSetTargetTag,
1920 mteEventSetContextName,
1921 mteEventSetContextNameWildcard
1926 ::= { dismanEventMIBGroups 4 }
1928 dismanEventNotificationObjectGroup OBJECT-GROUP
1939 "Notification objects."
1940 ::= { dismanEventMIBGroups 5 }
1942 dismanEventNotificationGroup NOTIFICATION-GROUP
1953 ::= { dismanEventMIBGroups 6 }