smilint output for ./DISMAN-EVENT-MIB
Message Severities |
Severity | Count |
severe | 4 |
error | 5 |
minor error | 1 |
change recommended | 5 |
warning | 5 |
fyi | 1 |
Message Types |
Type | Count |
default-too-long-smiv2 (error) | 1 |
defval-syntax (error) | 1 |
group-membership (change recommended) | 5 |
identifier-external-redefined (warning) | 1 |
internal-flushing (warning) | 2 |
internal-other (severe) | 2 |
named-numbers-ascending (warning) | 1 |
node-implicit (warning) | 1 |
object-identifier-not-prefix (error) | 1 |
object-identifier-unknown (severe) | 2 |
previous-definition (fyi) | 1 |
revision-missing (minor error) | 1 |
sequence-type-mismatch (error) | 2 |
Messages:
/home/fenner/mibindex/latest2/SNMPv2-SMI
1: -- extracted from rfc2578.txt
2: -- at Mon Nov 15 17:12:02 1999
3:
4: SNMPv2-SMI DEFINITIONS ::= BEGIN
5:
6:
7: -- the path to the root
8:
9: org OBJECT IDENTIFIER ::= { iso 3 } -- "iso" = 1
10: dod OBJECT IDENTIFIER ::= { org 6 }
11: internet OBJECT IDENTIFIER ::= { dod 1 }
12:
13: directory OBJECT IDENTIFIER ::= { internet 1 }
14:
15: mgmt OBJECT IDENTIFIER ::= { internet 2 }
16: mib-2 OBJECT IDENTIFIER ::= { mgmt 1 }
17: transmission OBJECT IDENTIFIER ::= { mib-2 10 }
18:
19: experimental OBJECT IDENTIFIER ::= { internet 3 }
20:
21: private OBJECT IDENTIFIER ::= { internet 4 }
22: enterprises OBJECT IDENTIFIER ::= { private 1 }
23:
24: security OBJECT IDENTIFIER ::= { internet 5 }
25:
26: snmpV2 OBJECT IDENTIFIER ::= { internet 6 }
27:
28: -- transport domains
29: snmpDomains OBJECT IDENTIFIER ::= { snmpV2 1 }
30:
31: -- transport proxies
32: snmpProxys OBJECT IDENTIFIER ::= { snmpV2 2 }
33:
34: -- module identities
35: snmpModules OBJECT IDENTIFIER ::= { snmpV2 3 }
36:
37: -- Extended UTCTime, to allow dates with four-digit years
38: -- (Note that this definition of ExtUTCTime is not to be IMPORTed
39: -- by MIB modules.)
40: ExtUTCTime ::= OCTET STRING(SIZE(11 | 13))
41: -- format is YYMMDDHHMMZ or YYYYMMDDHHMMZ
42: -- where: YY - last two digits of year (only years
43: -- between 1900-1999)
44: -- YYYY - last four digits of the year (any year)
45: -- MM - month (01 through 12)
46: -- DD - day of month (01 through 31)
47: -- HH - hours (00 through 23)
48: -- MM - minutes (00 through 59)
49: -- Z - denotes GMT (the ASCII character Z)
50: --
51: -- For example, "9502192015Z" and "199502192015Z" represent
52: -- 8:15pm GMT on 19 February 1995. Years after 1999 must use
53: -- the four digit year format. Years 1900-1999 may use the
54: -- two or four digit format.
55:
56: -- definitions for information modules
57:
58: MODULE-IDENTITY MACRO ::=
59: BEGIN
60: TYPE NOTATION ::=
61: "LAST-UPDATED" value(Update ExtUTCTime)
62: "ORGANIZATION" Text
63: "CONTACT-INFO" Text
64: "DESCRIPTION" Text
65: RevisionPart
66:
67: VALUE NOTATION ::=
68: value(VALUE OBJECT IDENTIFIER)
69:
70: RevisionPart ::=
71: Revisions
72: | empty
73: Revisions ::=
74: Revision
75: | Revisions Revision
76: Revision ::=
77: "REVISION" value(Update ExtUTCTime)
78: "DESCRIPTION" Text
79:
80: -- a character string as defined in section 3.1.1
81: Text ::= value(IA5String)
82: END
83:
84:
85: OBJECT-IDENTITY MACRO ::=
86: BEGIN
87: TYPE NOTATION ::=
88: "STATUS" Status
89: "DESCRIPTION" Text
90: ReferPart
91:
92: VALUE NOTATION ::=
93: value(VALUE OBJECT IDENTIFIER)
94:
95: Status ::=
96: "current"
97: | "deprecated"
98: | "obsolete"
99:
100: ReferPart ::=
101: "REFERENCE" Text
102: | empty
103:
104: -- a character string as defined in section 3.1.1
105: Text ::= value(IA5String)
106: END
107:
108:
109: -- names of objects
110: -- (Note that these definitions of ObjectName and NotificationName
111: -- are not to be IMPORTed by MIB modules.)
112:
113: ObjectName ::=
114: OBJECT IDENTIFIER
115:
116: NotificationName ::=
117: OBJECT IDENTIFIER
118:
119: -- syntax of objects
120:
121: -- the "base types" defined here are:
122: -- 3 built-in ASN.1 types: INTEGER, OCTET STRING, OBJECT IDENTIFIER
123: -- 8 application-defined types: Integer32, IpAddress, Counter32,
124: -- Gauge32, Unsigned32, TimeTicks, Opaque, and Counter64
125:
126: ObjectSyntax ::=
127: CHOICE {
128: simple
129: SimpleSyntax,
130:
131: -- note that SEQUENCEs for conceptual tables and
132: -- rows are not mentioned here...
133:
134: application-wide
135: ApplicationSyntax
136: }
137:
138: -- built-in ASN.1 types
139:
140: SimpleSyntax ::=
141: CHOICE {
142: -- INTEGERs with a more restrictive range
143: -- may also be used
144: integer-value -- includes Integer32
145: INTEGER (-2147483648..2147483647),
146:
147: -- OCTET STRINGs with a more restrictive size
148: -- may also be used
149: string-value
150: OCTET STRING (SIZE (0..65535)),
151:
152: objectID-value
153: OBJECT IDENTIFIER
154: }
155:
156: -- indistinguishable from INTEGER, but never needs more than
157: -- 32-bits for a two's complement representation
158: Integer32 ::=
159: INTEGER (-2147483648..2147483647)
160:
161:
162: -- application-wide types
163:
164: ApplicationSyntax ::=
165: CHOICE {
166: ipAddress-value
167: IpAddress,
168:
169: counter-value
170: Counter32,
171:
172: timeticks-value
173: TimeTicks,
174:
175: arbitrary-value
176: Opaque,
177:
178: big-counter-value
179: Counter64,
180:
181: unsigned-integer-value -- includes Gauge32
182: Unsigned32
183: }
184:
185: -- in network-byte order
186: -- (this is a tagged type for historical reasons)
187: IpAddress ::=
188: [APPLICATION 0]
189: IMPLICIT OCTET STRING (SIZE (4))
190:
191: -- this wraps
192: Counter32 ::=
193: [APPLICATION 1]
194: IMPLICIT INTEGER (0..4294967295)
195:
196: -- this doesn't wrap
197: Gauge32 ::=
198: [APPLICATION 2]
199: IMPLICIT INTEGER (0..4294967295)
200:
201: -- an unsigned 32-bit quantity
202: -- indistinguishable from Gauge32
203: Unsigned32 ::=
204: [APPLICATION 2]
205: IMPLICIT INTEGER (0..4294967295)
206:
207: -- hundredths of seconds since an epoch
208: TimeTicks ::=
209: [APPLICATION 3]
210: IMPLICIT INTEGER (0..4294967295)
211:
212: -- for backward-compatibility only
213: Opaque ::=
214: [APPLICATION 4]
215: IMPLICIT OCTET STRING
216:
217: -- for counters that wrap in less than one hour with only 32 bits
218: Counter64 ::=
219: [APPLICATION 6]
220: IMPLICIT INTEGER (0..18446744073709551615)
221:
222:
223: -- definition for objects
224:
225: OBJECT-TYPE MACRO ::=
226: BEGIN
227: TYPE NOTATION ::=
228: "SYNTAX" Syntax
229: UnitsPart
230: "MAX-ACCESS" Access
231: "STATUS" Status
232: "DESCRIPTION" Text
233: ReferPart
234: IndexPart
235: DefValPart
236:
237: VALUE NOTATION ::=
238: value(VALUE ObjectName)
239:
240: Syntax ::= -- Must be one of the following:
241: -- a base type (or its refinement),
242: -- a textual convention (or its refinement), or
243: -- a BITS pseudo-type
244: type
245: | "BITS" "{" NamedBits "}"
246:
247: NamedBits ::= NamedBit
248: | NamedBits "," NamedBit
249:
250: NamedBit ::= identifier "(" number ")" -- number is nonnegative
251:
252: UnitsPart ::=
253: "UNITS" Text
254: | empty
255:
256: Access ::=
257: "not-accessible"
258: | "accessible-for-notify"
259: | "read-only"
260: | "read-write"
261: | "read-create"
262:
263: Status ::=
264: "current"
265: | "deprecated"
266: | "obsolete"
267:
268: ReferPart ::=
269: "REFERENCE" Text
270: | empty
271:
272: IndexPart ::=
273: "INDEX" "{" IndexTypes "}"
274: | "AUGMENTS" "{" Entry "}"
275: | empty
276: IndexTypes ::=
277: IndexType
278: | IndexTypes "," IndexType
279: IndexType ::=
280: "IMPLIED" Index
281: | Index
282:
283: Index ::=
284: -- use the SYNTAX value of the
285: -- correspondent OBJECT-TYPE invocation
286: value(ObjectName)
287: Entry ::=
288: -- use the INDEX value of the
289: -- correspondent OBJECT-TYPE invocation
290: value(ObjectName)
291:
292: DefValPart ::= "DEFVAL" "{" Defvalue "}"
293: | empty
294:
295: Defvalue ::= -- must be valid for the type specified in
296: -- SYNTAX clause of same OBJECT-TYPE macro
297: value(ObjectSyntax)
298: | "{" BitsValue "}"
299:
300: BitsValue ::= BitNames
301: | empty
302:
303: BitNames ::= BitName
304: | BitNames "," BitName
305:
306: BitName ::= identifier
307:
308: -- a character string as defined in section 3.1.1
309: Text ::= value(IA5String)
310: END
311:
312:
313: -- definitions for notifications
314:
315: NOTIFICATION-TYPE MACRO ::=
316: BEGIN
317: TYPE NOTATION ::=
318: ObjectsPart
319: "STATUS" Status
320: "DESCRIPTION" Text
321: ReferPart
322:
323: VALUE NOTATION ::=
324: value(VALUE NotificationName)
325:
326: ObjectsPart ::=
327: "OBJECTS" "{" Objects "}"
328: | empty
329: Objects ::=
330: Object
331:
332: | Objects "," Object
333: Object ::=
334: value(ObjectName)
335:
336: Status ::=
337: "current"
338: | "deprecated"
339: | "obsolete"
340:
341: ReferPart ::=
342: "REFERENCE" Text
343: | empty
344:
345: -- a character string as defined in section 3.1.1
346: Text ::= value(IA5String)
347: END
348:
349: -- definitions of administrative identifiers
350:
351: zeroDotZero OBJECT-IDENTITY
351: fyi -
info: previous definition of `zeroDotZero'
352: STATUS current
353: DESCRIPTION
354: "A value used for null identifiers."
355: ::= { 0 0 }
356:
357: END
358:
359: --
360: -- Copyright (C) The Internet Society (1999). All Rights Reserved.
361: --
362: -- This document and translations of it may be copied and furnished to
363: -- others, and derivative works that comment on or otherwise explain it
364: -- or assist in its implementation may be prepared, copied, published
365: -- and distributed, in whole or in part, without restriction of any
366: -- kind, provided that the above copyright notice and this paragraph are
367: -- included on all such copies and derivative works. However, this
368: -- document itself may not be modified in any way, such as by removing
369: -- the copyright notice or references to the Internet Society or other
370: -- Internet organizations, except as needed for the purpose of
371: -- developing Internet standards in which case the procedures for
372: -- copyrights defined in the Internet Standards process must be
373: -- followed, or as required to translate it into languages other than
374: -- English.
375: --
376: -- The limited permissions granted above are perpetual and will not be
377: -- revoked by the Internet Society or its successors or assigns.
378: --
379: -- This document and the information contained herein is provided on an
380: -- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
381: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
382: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
383: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
384: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
385:
DISMAN-EVENT-MIB
1: -- extracted from draft-ietf-disman-event-mib-06.txt
2: -- at Mon Nov 15 17:10:51 1999
3:
4: DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8: experimental, Integer32, Unsigned32,
9: NOTIFICATION-TYPE, Counter32,
10: Gauge32 FROM SNMPv2-SMI
11: TEXTUAL-CONVENTION, RowStatus,
12: TruthValue FROM SNMPv2-TC
13: MODULE-COMPLIANCE, OBJECT-GROUP,
14: NOTIFICATION-GROUP FROM SNMPv2-CONF
15: sysUpTime FROM SNMPv2-MIB
16: SnmpTagValue FROM SNMP-TARGET-MIB
17: SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
18:
19: dismanEventMIB MODULE-IDENTITY
20: LAST-UPDATED "9902221700Z"
21: ORGANIZATION "IETF Distributed Management Working Group"
22: CONTACT-INFO "Bob Stewart
23: Cisco Systems, Inc.
24: 170 West Tasman Drive,
25: San Jose CA 95134-1706.
26: Phone: +1 408 526 4527
27: Email: bstewart@cisco.com"
28: DESCRIPTION
29: "The MIB module for defining event triggers and actions
30: for network management purposes."
31: ::= { experimental xx }
31: minor error -
revision for last update is missing
31: error -
Object identifier element `xx' name only allowed as first element
32:
33: dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 }
34:
35: mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 }
36: mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 }
37: mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 }
38: mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 }
39:
40: -- For use as a default OID:
41:
42: zeroDotZero OBJECT IDENTIFIER ::= { 0 0 }
42: warning -
warning: redefinition of identifier `SNMPv2-SMI::zeroDotZero'
42: warning -
warning: implicit node definition
43:
44:
45: --
46: -- Textual Conventions
47: --
48:
49: FailureReason ::= TEXTUAL-CONVENTION
50: STATUS current
51: DESCRIPTION
52: "Reasons for failures in an attempt to perform a management
53: request.
54:
55: The first group of errors, numbered less than 0, are related
56: to problems in sending the request. The existence of a
57: particular error code here does not imply that all
58: implementations are capable of sensing that error and
59: returning that code.
60:
61: The second group, numbered greater than 0, are copied
62: directly from SNMP protocol operations and are intended to carry
63: exactly the meanings defined for the protocol as returned in
64: an SNMP response.
65:
66: localResourceLack some local resource such as memory lacking
67: or mteResourceSampleInstanceMaximum
68: exceeded
69: badDestination unrecognized domain name or otherwise
70: invalid destination address
71: destinationUnreachable can't get to destination address
72: noResponse no response to SNMP request
73: badType the data syntax of a retrieved object
74: as not as expected
75: sampleOverrun another sample attempt occurred before
76: the previous one completed"
77:
78: SYNTAX INTEGER { localResourceLack(-1),
79: badDestination(-2),
80: destinationUnreachable(-3),
81: noResponse(-4),
82: badType(-5),
83: sampleOverrun(-6),
84:
85: noError(0),
86:
87: tooBig(1),
88: noSuchName(2),
89: badValue(3),
90: readOnly(4),
91: genErr(5),
92: noAccess(6),
93: wrongType(7),
94: wrongLength(8),
95: wrongEncoding(9),
96: wrongValue(10),
97: noCreation(11),
98: inconsistentValue(12),
99: resourceUnavailable(13),
100: commitFailed(14),
101: undoFailed(15),
102: authorizationError(16),
103: notWritable(17),
104: inconsistentName(18) }
104: warning -
warning: named numbers not in ascending order
105: --
106: -- Resource Control Section
107: --
108:
109: mteResourceSampleMinimum OBJECT-TYPE
110: SYNTAX Integer32 (-1 | 1..600)
111: UNITS "seconds"
112: MAX-ACCESS read-write
113: STATUS current
114: DESCRIPTION
115:
116: "The minimum mteTriggerFrequency this system will accept. A
117: system may use the larger values of this minimum to lessen the
118: impact of sampling.
119:
120: Unless explicitly resource limited, a system's value for
121: this object should be 1.
122:
123: Changing this value will not invalidate an existing setting
124: of mteTriggerFrequency."
125: ::= { mteResource 1 }
126:
127: mteResourceSampleInstanceMaximum OBJECT-TYPE
128: SYNTAX Unsigned32
129: UNITS "instances"
130: MAX-ACCESS read-write
131: STATUS current
132: DESCRIPTION
133: "The maximum number of instance entries this system will
134: support for sampling.
135:
136: These are the entries that maintain state, one for each
137: instance of each sampled object as selected by
138: mteTriggerValueID. Note that wildcarded objects result
139: in multiple instances of this state.
140:
141: A value of 0 indicates no preset limit, that is, the limit
142: is dynamic based on system operation and resources.
143:
144: Unless explicitly resource limited, a system's value for
145: this object should be 0.
146:
147: Changing this value will not eliminate or inhibit existing sample
148: state but could prevent allocation of additional state
149: information."
150: ::= { mteResource 2 }
151:
152: mteResourceSampleInstances OBJECT-TYPE
153: SYNTAX Gauge32
154: UNITS "instances"
155: MAX-ACCESS read-only
156: STATUS current
157: DESCRIPTION
158: "The number of currently active instance entries as
159: defined for mteResourceSampleInstanceMaximum."
160: ::= { mteResource 3 }
161:
162: mteResourceSampleInstancesHigh OBJECT-TYPE
163: SYNTAX Gauge32
164: UNITS "instances"
165: MAX-ACCESS read-only
166: STATUS current
167: DESCRIPTION
168: "The highest value of mteResourceSampleInstances that has
169: occurred since initialization of the management system."
170: ::= { mteResource 4 }
171:
172: mteResourceSampleInstanceLacks OBJECT-TYPE
173: SYNTAX Counter32
174: UNITS "instances"
175: MAX-ACCESS read-only
176: STATUS current
177: DESCRIPTION
178: "The number of times this system could not take a new sample
179: because that allocation would have exceeded the limit set by
180: mteResourceSampleInstanceMaximum."
181: ::= { mteResource 5 }
182:
183: --
184: -- Trigger Section
185: --
186:
187: -- Counters
188:
189: mteTriggerFailures OBJECT-TYPE
190: SYNTAX Counter32
191: MAX-ACCESS read-only
192: STATUS current
193: DESCRIPTION
194: "The number of times an attempt to check for a trigger
195: condition has failed. This counts individually for each
196: attempt in a group of targets or each attempt for a
197: wildcarded object."
198: ::= { mteTrigger 1 }
199:
200:
201: --
202: -- Trigger Table
203: --
204:
205: mteTriggerTable OBJECT-TYPE
206: SYNTAX SEQUENCE OF MteTriggerEntry
207: MAX-ACCESS not-accessible
208: STATUS current
209: DESCRIPTION
210: "A table of management event trigger information."
211: ::= { mteTrigger 2 }
212:
213: mteTriggerEntry OBJECT-TYPE
214: SYNTAX MteTriggerEntry
215: MAX-ACCESS not-accessible
216: STATUS current
217: DESCRIPTION
218: "Information about a single trigger. Applications create and
219: delete entries using mteTriggerEntryStatus."
220: INDEX { mteOwner, IMPLIED mteTriggerName }
221: ::= { mteTriggerTable 1 }
222:
223: MteTriggerEntry ::= SEQUENCE {
224: mteOwner SnmpAdminString,
225: mteTriggerName SnmpAdminString,
226: mteTriggerComment SnmpAdminString,
227: mteTriggerTest BITS,
228: mteTriggerSampleType INTEGER,
229: mteTriggerValueID OBJECT IDENTIFIER,
230: mteTriggerValueIDWildcard TruthValue,
231: mteTriggerTargetTag SnmpTagValue,
232: mteTriggerContextName SnmpAdminString,
233: mteTriggerContextNameWildcard TruthValue,
234: mteTriggerFrequency Unsigned32,
235: mteTriggerObjectsOwner SnmpAdminString,
236: mteTriggerObjects SnmpAdminString,
237: mteTriggerEnabled TruthValue,
238: mteTriggerEntryStatus RowStatus
239: }
240:
241: mteOwner OBJECT-TYPE
242: SYNTAX SnmpAdminString (SIZE(0..32))
243: MAX-ACCESS not-accessible
244: STATUS current
245: DESCRIPTION
246: "The owner of this entry. The exact semantics of this
247: string are subject to the security policy defined by the
248: security administrator."
249: ::= { mteTriggerEntry 1 }
250:
251: mteTriggerName OBJECT-TYPE
252: SYNTAX SnmpAdminString (SIZE (1..32))
253: MAX-ACCESS not-accessible
254: STATUS current
255: DESCRIPTION
256: "A locally-unique, administratively assigned name for the
257: trigger within the scope of mteOwner."
258: ::= { mteTriggerEntry 2 }
259:
260: mteTriggerComment OBJECT-TYPE
261: SYNTAX SnmpAdminString
262: MAX-ACCESS read-create
263: STATUS current
264: DESCRIPTION
265: "A description of the trigger's function and use."
266: DEFVAL { ''H }
267: ::= { mteTriggerEntry 3 }
268:
269: mteTriggerTest OBJECT-TYPE
270: SYNTAX BITS { existence(0), boolean(1), threshold(2) }
271: MAX-ACCESS read-create
272: STATUS current
273: DESCRIPTION
274: "The type of trigger test to perform. For 'boolean' and
275: 'threshold' tests, the object at mteTriggerValueID must
276: evaluate to an integer, that is, anything that ends up encoded
277: for transmission as an integer.
278:
279: For 'existence', the specific test is as selected by
280: mteTriggerExistenceTest. When an object appears or vanishes
281: the trigger fires. The trigger will not fire again until the
282: object has changed states.
283:
284: For 'boolean', the specific test is as selected by
285: mteTriggerBooleanTest. If the test result is true the trigger
286: fires. The trigger will not fire again until the value has
287: become false and come back to true.
288:
289: For 'threshold' the test works as described below for
290: mteTriggerThresholdStartup, mteTriggerThresholdRising, and
291: mteTriggerThresholdFalling.
292:
293: Note that combining 'boolean' and 'threshold' tests on the
294: same object may be somewhat redundant."
295: DEFVAL { boolean }
295: error -
default value syntax does not match object syntax
296: ::= { mteTriggerEntry 4 }
297:
298: mteTriggerSampleType OBJECT-TYPE
299: SYNTAX INTEGER { absoluteValue(1), deltaValue(2) }
300: MAX-ACCESS read-create
301: STATUS current
302: DESCRIPTION
303: "The type of sampling to perform.
304:
305: An 'absoluteValue' sample requires only a single sample to be
306: meaningful, and is exactly the value of the object at
307: mteTriggerValueID at the sample time.
308:
309: A 'deltaValue' requires two samples to be meaningful and is
310: thus not available for testing until the second and subsequent
311: samples after the object at mteTriggerValueID is first found
312: to exist. It is the difference between the two samples. For
313: unsigned values it is always positive, based on unsigned
314: arithmetic. For signed values it can be positive or negative.
315:
316: For SNMP counters to be meaningful they must be sampled as a
317: 'deltaValue'.
318: For 'deltaValue' mteTriggerDeltaTable contains further
319: parameters.
320:
321: If only 'existence' is set in mteTriggerTest this object has
322: no meaning."
323: DEFVAL { absoluteValue }
324: ::= { mteTriggerEntry 5 }
325:
326: mteTriggerValueID OBJECT-TYPE
327: SYNTAX OBJECT IDENTIFIER
328: MAX-ACCESS read-create
329: STATUS current
330: DESCRIPTION
331: "The object identifier of the MIB object to sample to see
332: if the trigger should fire.
333:
334: This may be wildcarded by truncating all or part of the
335: instance portion, in which case the value is obtained
336: as if with a GetNext function, checking multiple values
337: if they exist. If such wildcarding is applied,
338: mteTriggerValueIDWildcard must be 'true' and if not it must
339: be 'false'.
340:
341: Bad object identifiers or a mismatch between truncating the
342: identifier and the value of mteTriggerValueIDWildcard result
343: in operation as one would expect when providing the wrong
344: identifier to a Get or GetNext operation. The Get will fail
345: or get the wrong object. The GetNext will indeed get whatever
346: is next, proceeding until it runs past the initial part of the
347: identifier and perhaps many unintended objects for confusing
348: results. If the value syntax of those objects is not usable,
349: that results in a 'badType' error that terminates the scan.
350:
351: Each instance that fills the wildcard is independent of any
352: additional instances, that is, wildcarded objects operate
353: as if there were a separate table entry for each instance
354: that fills the wildcard without having to actually predict
355: all possible instances ahead of time."
356: DEFVAL { zeroDotZero }
357: ::= { mteTriggerEntry 6 }
358:
359: mteTriggerValueIDWildcard OBJECT-TYPE
360: SYNTAX TruthValue
361: MAX-ACCESS read-create
362: STATUS current
363: DESCRIPTION
364: "Control for whether mteTriggerValueID is to be treated as
365: fully-specified or wildcarded, with 'true' indicating wildcard."
366: DEFVAL { false }
367: ::= { mteTriggerEntry 7 }
368:
369: mteTriggerTargetTag OBJECT-TYPE
370: SYNTAX SnmpTagValue
371: MAX-ACCESS read-create
372: STATUS current
373: DESCRIPTION
374: "The tag for the target(s) from which to obtain the condition
375: for a trigger check.
376:
377: A length of 0 indicates the local system. In this case,
378: access to the objects indicated by mteTriggerValueID is under
379: the security credentials of the requester that set
380: mteTriggerEntryStatus to 'active'. Those credentials are the
381: input parameters for isAccessAllowed from the Architecture for
382: Describing SNMP Management Frameworks.
383:
384: Otherwise access rights are checked according to the security
385: parameters resulting from the tag."
386: DEFVAL { ''H }
387: ::= { mteTriggerEntry 8 }
388:
389: mteTriggerContextName OBJECT-TYPE
390: SYNTAX SnmpAdminString
391: MAX-ACCESS read-create
392: STATUS current
393: DESCRIPTION
394: "The management context from which to obtain mteTriggerValueID.
395:
396: This may be wildcarded by leaving characters off the end. For
397: example use 'Repeater' to wildcard to 'Repeater1',
398: 'Repeater2', 'Repeater-999.87b', and so on. To indicate such
399: wildcarding is intended, mteTriggerContextNameWildcard must
400: be 'true'.
401:
402: Each instance that fills the wildcard is independent of any
403: additional instances, that is, wildcarded objects operate
404: as if there were a separate table entry for each instance
405: that fills the wildcard without having to actually predict
406: all possible instances ahead of time.
407: Operation of this feature assumes that the local system has a
408: list of available contexts against which to apply the
409: wildcard. If the objects are being read from the local
410: system, this is clearly the system's own list of contexts.
411: For a remote system a local version of such a list is not
412: defined by any current standard and may not be available, so
413: this function may not be supported."
414: DEFVAL { ''H }
415: ::= { mteTriggerEntry 9 }
416:
417: mteTriggerContextNameWildcard OBJECT-TYPE
418: SYNTAX TruthValue
419: MAX-ACCESS read-create
420: STATUS current
421: DESCRIPTION
422: "Control for whether mteTriggerContextName is to be treated as
423: fully-specified or wildcarded, with 'true' indicating wildcard."
424: DEFVAL { false }
425: ::= { mteTriggerEntry 10 }
426:
427: mteTriggerFrequency OBJECT-TYPE
428: SYNTAX Unsigned32
429: UNITS "seconds"
430: MAX-ACCESS read-create
431: STATUS current
432: DESCRIPTION
433: "The number of seconds to wait between trigger samples. To
434: encourage consistency in sampling, the interval is measured
435: from the beginning of one check to the beginning of the next
436: and the timer is restarted immediately when it expires, not
437: when the check completes.
438:
439: If the next sample begins before the previous one completed the
440: system may either attempt to make the check or treat this as an
441: error condition with the error 'sampleOverrun'.
442:
443: A frequency of 0 indicates instantaneous recognition of the
444: condition. This is not possible in many cases, but may
445: be supported in cases where it makes sense and the system is
446: able to do so. This feature allows the MIB to be used in
447: implementations where such interrupt-driven behavior is
448: possible and is not likely to be supported for all MIB objects
449: even then since such sampling generally has to be tightly
450: integrated into low-level code.
451: Systems that can support this should document those cases
452: where it can be used. In cases where it can not, setting this
453: object to 0 simply returns a bad value error."
454: DEFVAL { 600 }
455: ::= { mteTriggerEntry 11 }
456:
457: mteTriggerObjectsOwner OBJECT-TYPE
458: SYNTAX SnmpAdminString (SIZE (0..32))
459: MAX-ACCESS read-create
460: STATUS current
461: DESCRIPTION
462: "To go with mteTriggerObjects, the mteOwner of a group of
463: objects from mteObjectsTable."
464: DEFVAL { ''H }
465: ::= { mteTriggerEntry 12 }
466:
467: mteTriggerObjects OBJECT-TYPE
468: SYNTAX SnmpAdminString (SIZE (0..32))
469: MAX-ACCESS read-create
470: STATUS current
471: DESCRIPTION
472: "The mteObjectsName of a group of objects from
473: mteObjectsTable. These objects are to be added to any
474: Notification resulting from the firing of this trigger.
475:
476: A list of objects may also be added based on the event or on
477: the value of mteTriggerTest.
478:
479: A length of 0 indicates no additional objects."
480: DEFVAL { ''H }
481: ::= { mteTriggerEntry 13 }
482:
483: mteTriggerEnabled OBJECT-TYPE
484: SYNTAX TruthValue
485: MAX-ACCESS read-create
486: STATUS current
487: DESCRIPTION
488: "A control to allow a trigger to be configured but not used.
489: When the value is 'false' the trigger is not sampled."
490: DEFVAL { false }
491: ::= { mteTriggerEntry 14 }
492:
493: mteTriggerEntryStatus OBJECT-TYPE
494: SYNTAX RowStatus
495: MAX-ACCESS read-create
496: STATUS current
497: DESCRIPTION
498: "The control that allows creation and deletion of entries.
499: Once made active an entry may not be modified except to
500: delete it."
501: ::= { mteTriggerEntry 15 }
502:
503:
504: --
505: -- Trigger Delta Table
506: --
507:
508: mteTriggerDeltaTable OBJECT-TYPE
509: SYNTAX SEQUENCE OF MteTriggerDeltaEntry
510: MAX-ACCESS not-accessible
511: STATUS current
512: DESCRIPTION
513: "A table of management event trigger information for delta
514: sampling."
515: ::= { mteTrigger 3 }
516:
517: mteTriggerDeltaEntry OBJECT-TYPE
518: SYNTAX MteTriggerDeltaEntry
519: MAX-ACCESS not-accessible
520: STATUS current
521: DESCRIPTION
522: "Information about a single trigger's delta sampling. Entries
523: automatically exist in this this table for each mteTriggerEntry
524: that has mteTriggerSampleType set to 'deltaValue'."
525: INDEX { mteOwner, IMPLIED mteTriggerName }
526: ::= { mteTriggerDeltaTable 1 }
527:
528: MteTriggerDeltaEntry ::= SEQUENCE {
529: mteTriggerDeltaDiscontinuityID OBJECT IDENTIFIER,
530: mteTriggerDeltaDiscontinuityIDWildcard TruthValue,
531: mteTriggerDeltaDiscontinuityIDType INTEGER
532: }
533:
534:
535: sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 }
536:
537: mteTriggerDeltaDiscontinuityID OBJECT-TYPE
538: SYNTAX OBJECT IDENTIFIER
539: MAX-ACCESS read-write
540: STATUS current
541: DESCRIPTION
542: "The OBJECT IDENTIFIER (OID) of a TimeTicks or TimeStamp object
543: that indicates a discontinuity in the value at
544: mteTriggerValueID.
545:
546: The OID may be for a leaf object (e.g. sysUpTime.0) or may
547: be wildcarded to match mteTriggerValueID.
548:
549: This object supports normal checking for a discontinuity in a
550: counter. Note that if this object does not point to sysUpTime
551: discontinuity checking must still check sysUpTime for an overall
552: discontinuity.
553:
554: If the object identified is not accessible the sample attempt
555: is in error, with the error code as from an SNMP request.
556:
557: Bad object identifiers or a mismatch between truncating the
558: identifier and the value of mteDeltaDiscontinuityIDWildcard
559: result in operation as one would expect when providing the
560: wrong identifier to a Get operation. The Get will fail or get
561: the wrong object. If the value syntax of those objects is not
562: usable, that results in an error that terminates the sample
563: with a 'badType' error code."
564: DEFVAL { sysUpTimeInstance }
565: ::= { mteTriggerDeltaEntry 1 }
566:
567: mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE
568: SYNTAX TruthValue
569: MAX-ACCESS read-write
570: STATUS current
571: DESCRIPTION
572: "Control for whether mteTriggerDeltaDiscontinuityID is to be
573: treated as fully-specified or wildcarded, with 'true'
574: indicating wildcard."
575: DEFVAL { false }
576: ::= { mteTriggerDeltaEntry 2 }
577:
578: mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE
579: SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) }
580: MAX-ACCESS read-write
581: STATUS current
582: DESCRIPTION
583: "The value 'timeTicks' indicates the
584: mteTriggerDeltaDiscontinuityID of this row is of syntax
585: TimeTicks. The value 'timeStamp' indicates syntax TimeStamp.
586: The value 'dateAndTime' indicates syntax DateAndTime."
587: DEFVAL { timeTicks }
588: ::= { mteTriggerDeltaEntry 3 }
589:
590:
591: --
592: -- Trigger Existence Table
593: --
594:
595: mteTriggerExistenceTable OBJECT-TYPE
596: SYNTAX SEQUENCE OF MteTriggerExistenceEntry
597: MAX-ACCESS not-accessible
598: STATUS current
599: DESCRIPTION
600: "A table of management event trigger information for existence
601: triggers."
602: ::= { mteTrigger 4 }
603:
604: mteTriggerExistenceEntry OBJECT-TYPE
605: SYNTAX MteTriggerExistenceEntry
606: MAX-ACCESS not-accessible
607: STATUS current
608: DESCRIPTION
609: "Information about a single existence trigger. Entries
610: automatically exist in this this table for each mteTriggerEntry
611: that has 'existence' set in mteTriggerTest."
612: INDEX { mteOwner, IMPLIED mteTriggerName }
613: ::= { mteTriggerExistenceTable 1 }
614:
615: MteTriggerExistenceEntry ::= SEQUENCE {
616: mteTriggerExistenceTest INTEGER,
617: mteTriggerExistenceStartup TruthValue,
618: mteTriggerExistenceObjectsOwner SnmpAdminString,
619: mteTriggerExistenceObjects SnmpAdminString,
620: mteTriggerExistenceEventOwner SnmpAdminString,
621: mteTriggerExistenceEvent SnmpAdminString
622: }
623:
624: mteTriggerExistenceTest OBJECT-TYPE
625: SYNTAX BITS { present(0), absent(1), changed(2) }
626: MAX-ACCESS read-write
627: STATUS current
628: DESCRIPTION
629: "The type of existence test to perform. The trigger fires
630: when the object at mteTriggerValueID is seen to go from
631: present to absent, from absent to present, or to have it's
632: value changed, depending on which tests are selected.
633:
634: Once the trigger has fired for either presence or absence it
635: will not fire again for that state until the object has been
636: to the other state."
637: DEFVAL { { present, absent } }
638: ::= { mteTriggerExistenceEntry 1 }
638: error -
type of `mteTriggerExistenceTest' in sequence and object type definition do not match
639:
640: mteTriggerExistenceStartup OBJECT-TYPE
641: SYNTAX BITS { present(0), absent(1), changed(2) }
642: MAX-ACCESS read-write
643: STATUS current
644: DESCRIPTION
645: "Control for whether an event may be triggered when this entry
646: is first set to 'active' and the test specified by
647: mteTriggerExistenceTest is true. Setting an option causes
648: that trigger to fire when its test is true."
649: DEFVAL { { present, absent } }
650: ::= { mteTriggerExistenceEntry 2 }
650: error -
type of `mteTriggerExistenceStartup' in sequence and object type definition do not match
651:
652: mteTriggerExistenceObjectsOwner OBJECT-TYPE
653: SYNTAX SnmpAdminString (SIZE (0..32))
654: MAX-ACCESS read-write
655: STATUS current
656: DESCRIPTION
657: "To go with mteTriggerExistenceObjects, the mteOwner of a
658: group of objects from mteObjectsTable."
659: DEFVAL { ''H }
660: ::= { mteTriggerExistenceEntry 3 }
661:
662: mteTriggerExistenceObjects OBJECT-TYPE
663: SYNTAX SnmpAdminString (SIZE (0..32))
664: MAX-ACCESS read-write
665: STATUS current
666: DESCRIPTION
667: "The mteObjectsName of a group of objects from
668: mteObjectsTable. These objects are to be added to any
669: Notification resulting from the firing of this trigger for
670: this test.
671:
672: A list of objects may also be added based on the overall
673: trigger, the event or other settings in mteTriggerTest.
674:
675: A length of 0 indicates no additional objects."
676:
677: DEFVAL { ''H }
678: ::= { mteTriggerExistenceEntry 4 }
679:
680: mteTriggerExistenceEventOwner OBJECT-TYPE
681: SYNTAX SnmpAdminString (SIZE (0..32))
682: MAX-ACCESS read-write
683: STATUS current
684: DESCRIPTION
685: "To go with mteTriggerExistenceEvent, the mteOwner of a group
686: of objects from mteObjectsTable."
687: DEFVAL { ''H }
688: ::= { mteTriggerExistenceEntry 5 }
689:
690: mteTriggerExistenceEvent OBJECT-TYPE
691: SYNTAX SnmpAdminString (SIZE (0..32))
692: MAX-ACCESS read-write
693: STATUS current
694: DESCRIPTION
695: "The mteEventName of the event to invoke when mteTriggerType is
696: 'existence' and this trigger fires. A length of 0 indicates no
697: event."
698: DEFVAL { ''H }
699: ::= { mteTriggerExistenceEntry 6 }
700:
701:
702: --
703: -- Trigger Boolean Table
704: --
705:
706: mteTriggerBooleanTable OBJECT-TYPE
707: SYNTAX SEQUENCE OF MteTriggerBooleanEntry
708: MAX-ACCESS not-accessible
709: STATUS current
710: DESCRIPTION
711: "A table of management event trigger information for boolean
712: triggers."
713: ::= { mteTrigger 5 }
714:
715: mteTriggerBooleanEntry OBJECT-TYPE
716: SYNTAX MteTriggerBooleanEntry
717: MAX-ACCESS not-accessible
718: STATUS current
719: DESCRIPTION
720: "Information about a single boolean trigger. Entries
721: automatically exist in this this table for each mteTriggerEntry
722: that has 'boolean' set in mteTriggerTest."
723: INDEX { mteOwner, IMPLIED mteTriggerName }
724: ::= { mteTriggerBooleanTable 1 }
725:
726: MteTriggerBooleanEntry ::= SEQUENCE {
727: mteTriggerBooleanComparison INTEGER,
728: mteTriggerBooleanValue Integer32,
729: mteTriggerBooleanStartup TruthValue,
730: mteTriggerBooleanObjectsOwner SnmpAdminString,
731: mteTriggerBooleanObjects SnmpAdminString,
732: mteTriggerBooleanEventOwner SnmpAdminString,
733: mteTriggerBooleanEvent SnmpAdminString
734: }
735:
736: mteTriggerBooleanComparison OBJECT-TYPE
737: SYNTAX INTEGER { unequal(1), equal(2),
738: less(3), lessOrEqual(4),
739: greater(5), greaterOrEqual(6) }
740: MAX-ACCESS read-write
741: STATUS current
742: DESCRIPTION
743: "The type of boolean comparison to perform.
744:
745: The value at mteTriggerValueID is compared to
746: mteTriggerBooleanValue, so for example if
747: mteTriggerBooleanComparison is 'less' the result would be true
748: if the value at mteTriggerValueID is less than the value of
749: mteTriggerBooleanValue."
750: DEFVAL { unequal }
751: ::= { mteTriggerBooleanEntry 1 }
752:
753: mteTriggerBooleanValue OBJECT-TYPE
754: SYNTAX Integer32
755: MAX-ACCESS read-write
756: STATUS current
757: DESCRIPTION
758: "The value to use for the test specified by
759: mteTriggerBooleanTest."
760: DEFVAL { 0 }
761: ::= { mteTriggerBooleanEntry 2 }
762:
763: mteTriggerBooleanStartup OBJECT-TYPE
764: SYNTAX TruthValue
765: MAX-ACCESS read-write
766: STATUS current
767: DESCRIPTION
768: "Control for whether an event may be triggered when this entry
769: is first set to 'active' or a new instance of the object at
770: mteTriggerValueID is found and the test specified by
771: mteTriggerBooleanComparison is true. In that case an event is
772: triggered if mteTriggerBooleanStartup is 'true'."
773: DEFVAL { true }
774: ::= { mteTriggerBooleanEntry 3 }
775:
776: mteTriggerBooleanObjectsOwner OBJECT-TYPE
777: SYNTAX SnmpAdminString (SIZE (0..32))
778: MAX-ACCESS read-write
779: STATUS current
780: DESCRIPTION
781: "To go with mteTriggerBooleanObjects, the mteOwner of a group
782: of objects from mteObjectsTable."
783: DEFVAL { ''H }
784: ::= { mteTriggerBooleanEntry 4 }
785:
786: mteTriggerBooleanObjects OBJECT-TYPE
787: SYNTAX SnmpAdminString (SIZE (0..32))
788: MAX-ACCESS read-write
789: STATUS current
790: DESCRIPTION
791: "The mteObjectsName of a group of objects from
792: mteObjectsTable. These objects are to be added to any
793: Notification resulting from the firing of this trigger for
794: this test.
795:
796: A list of objects may also be added based on the overall
797: trigger, the event or other settings in mteTriggerTest.
798:
799: A length of 0 indicates no additional objects."
800: DEFVAL { ''H }
801: ::= { mteTriggerBooleanEntry 5 }
802:
803: mteTriggerBooleanEventOwner OBJECT-TYPE
804: SYNTAX SnmpAdminString (SIZE (0..32))
805: MAX-ACCESS read-write
806: STATUS current
807: DESCRIPTION
808: "To go with mteTriggerBooleanEvent, the mteOwner of an event
809: entry from mteEventTable."
810: DEFVAL { ''H }
811: ::= { mteTriggerBooleanEntry 6 }
812:
813: mteTriggerBooleanEvent OBJECT-TYPE
814: SYNTAX SnmpAdminString (SIZE (0..32))
815: MAX-ACCESS read-write
816: STATUS current
817: DESCRIPTION
818: "The mteEventName of the event to invoke when mteTriggerType is
819: 'boolean' and this trigger fires. A length of 0 indicates no
820: event."
821: DEFVAL { ''H }
822: ::= { mteTriggerBooleanEntry 7 }
823:
824:
825: --
826: -- Trigger Threshold Table
827: --
828:
829: mteTriggerThresholdTable OBJECT-TYPE
830: SYNTAX SEQUENCE OF MteTriggerThresholdEntry
831: MAX-ACCESS not-accessible
832: STATUS current
833: DESCRIPTION
834: "A table of management event trigger information for threshold
835: triggers."
836: ::= { mteTrigger 6 }
837:
838: mteTriggerThresholdEntry OBJECT-TYPE
839: SYNTAX MteTriggerThresholdEntry
840: MAX-ACCESS not-accessible
841: STATUS current
842: DESCRIPTION
843: "Information about a single threshold trigger. Entries
844: automatically exist in this table for each mteTriggerEntry
845: that has 'threshold' set in mteTriggerTest."
846: INDEX { mteOwner, IMPLIED mteTriggerName }
847: ::= { mteTriggerThresholdTable 1 }
848:
849: MteTriggerThresholdEntry ::= SEQUENCE {
850: mteTriggerThresholdValue Integer32,
851: mteTriggerThresholdStartup INTEGER,
852: mteTriggerThresholdRising Integer32,
853: mteTriggerThresholdFalling Integer32,
854: mteTriggerThresholdObjectsOwner SnmpAdminString,
855: mteTriggerThresholdObjects SnmpAdminString,
856: mteTriggerThresholdRisingEventOwner SnmpAdminString,
857: mteTriggerThresholdRisingEvent SnmpAdminString,
858: mteTriggerThresholdFallingEventOwner SnmpAdminString,
859: mteTriggerThresholdFallingEvent SnmpAdminString
860: }
861:
862: mteTriggerThresholdValue OBJECT-TYPE
863: SYNTAX Integer32
864: MAX-ACCESS read-write
865: STATUS current
866: DESCRIPTION
867: "The value to use for the threshold test."
868: DEFVAL { 0 }
869: ::= { mteTriggerThresholdEntry 1 }
870:
871: mteTriggerThresholdStartup OBJECT-TYPE
872: SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) }
873: MAX-ACCESS read-write
874: STATUS current
875: DESCRIPTION
876: "The event that may be triggered when this entry is first
877: set to 'active' and a new instance of the object at
878: mteTriggerValueID is found. If the first sample after this
879: instance becomes active is greater than or equal to
880: mteTriggerThresholdRising and mteTriggerThresholdStartup is
881: equal to 'rising' or 'risingOrFalling', then one
882: mteTriggerThresholdRisingEvent is triggered for that instance.
883: If the first sample after this entry becomes active is less than
884: or equal to mteTriggerThresholdFalling and
885: mteTriggerThresholdStartup is equal to 'falling' or
886: 'risingOrFalling', then one mteTriggerThresholdRisingEvent is
887: triggered for that instance."
888: DEFVAL { risingOrFalling }
889: ::= { mteTriggerThresholdEntry 2 }
890:
891: mteTriggerThresholdRising OBJECT-TYPE
892: SYNTAX Integer32
893: MAX-ACCESS read-write
894: STATUS current
895: DESCRIPTION
896: "A threshold value to check against if mteTriggerType is
897: 'threshold'.
898:
899: When the current sampled value is greater than or equal to
900: this threshold, and the value at the last sampling interval
901: was less than this threshold, one
902: mteTriggerThresholdRisingEvent is triggered. That event is
903: also triggered if the first sample afer this entry bcomes
904: active is greater than or equal to this threshold and
905: mteTriggerThresholdStartup is equal to 'rising' or
906: 'risingOrFalling'.
907:
908: After a rising event is generated, another such event is not
909: triggered until the sampled value falls below this threshold and
910: reaches mteTriggerThresholdFalling."
911: DEFVAL { 0 }
912: ::= { mteTriggerThresholdEntry 3 }
913:
914: mteTriggerThresholdFalling OBJECT-TYPE
915: SYNTAX Integer32
916: MAX-ACCESS read-write
917: STATUS current
918: DESCRIPTION
919: "A threshold value to check against if mteTriggerType is
920: 'threshold'.
921:
922: When the current sampled value is less than or equal to this
923: threshold, and the value at the last sampling interval was
924: greater than this threshold, one
925: mteTriggerThresholdFallingEvent is triggered. That event is
926: also triggered if the first sample afer this entry bcomes
927: active is less than or equal to this threshold and
928: mteTriggerThresholdStartup is equal to 'falling' or
929: 'risingOrFalling'.
930:
931: After a falling event is generated, another such event is not
932: triggered until the sampled value rises above this threshold and
933: reaches mteTriggerThresholdRising."
934: DEFVAL { 0 }
935: ::= { mteTriggerThresholdEntry 4 }
936:
937: mteTriggerThresholdObjectsOwner OBJECT-TYPE
938: SYNTAX SnmpAdminString (SIZE (0..32))
939: MAX-ACCESS read-write
940: STATUS current
941: DESCRIPTION
942: "To go with mteTriggerThresholdObjects, the mteOwner of a group
943: of objects from mteObjectsTable."
944: DEFVAL { ''H }
945: ::= { mteTriggerThresholdEntry 5 }
946:
947: mteTriggerThresholdObjects OBJECT-TYPE
948: SYNTAX SnmpAdminString (SIZE (0..32))
949: MAX-ACCESS read-write
950: STATUS current
951: DESCRIPTION
952: "The mteObjectsName of a group of objects from
953: mteObjectsTable. These objects are to be added to any
954: Notification resulting from the firing of this trigger for
955: this test.
956:
957: A list of objects may also be added based on the overall
958: trigger, the event or other settings in mteTriggerTest.
959:
960: A length of 0 indicates no additional objects."
961: DEFVAL { ''H }
962: ::= { mteTriggerThresholdEntry 6 }
963:
964: mteTriggerThresholdRisingEventOwner OBJECT-TYPE
965: SYNTAX SnmpAdminString (SIZE (0..32))
966: MAX-ACCESS read-write
967: STATUS current
968: DESCRIPTION
969: "To go with mteTriggerThresholdRisingEvent, the mteOwner of an
970: event entry from mteEventTable."
971: DEFVAL { ''H }
972: ::= { mteTriggerThresholdEntry 7 }
973:
974: mteTriggerThresholdRisingEvent OBJECT-TYPE
975: SYNTAX SnmpAdminString (SIZE (0..32))
976: MAX-ACCESS read-write
977: STATUS current
978: DESCRIPTION
979: "The mteEventName of the event to invoke when mteTriggerType is
980: 'threshold' and this trigger fires based on
981: mteTriggerThresholdRising. A length of 0 indicates no event."
982: DEFVAL { ''H }
983: ::= { mteTriggerThresholdEntry 8 }
984:
985: mteTriggerThresholdFallingEventOwner OBJECT-TYPE
986: SYNTAX SnmpAdminString (SIZE (0..32))
987: MAX-ACCESS read-write
988: STATUS current
989: DESCRIPTION
990: "To go with mteTriggerThresholdFallingEvent, the mteOwner of an
991: event entry from mteEventTable."
992: DEFVAL { ''H }
993: ::= { mteTriggerThresholdEntry 9 }
994:
995: mteTriggerThresholdFallingEvent OBJECT-TYPE
996: SYNTAX SnmpAdminString (SIZE (0..32))
997: MAX-ACCESS read-write
998: STATUS current
999: DESCRIPTION
1000: "The mteEventName of the event to invoke when mteTriggerType is
1001: 'threshold' and this trigger fires based on
1002: mteTriggerThresholdFalling. A length of 0 indicates no event."
1003: DEFVAL { ''H }
1004: ::= { mteTriggerThresholdEntry 10 }
1005:
1006:
1007: --
1008: -- Objects Table
1009: --
1010:
1011: mteObjectsTable OBJECT-TYPE
1012: SYNTAX SEQUENCE OF MteObjectsEntry
1013: MAX-ACCESS not-accessible
1014: STATUS current
1015: DESCRIPTION
1016: "A table of objects that can be added to notifications based
1017: on the trigger, trigger test, or event, as pointed to by
1018: entries in those tables."
1019: ::= { mteObjects 1 }
1020:
1021: mteObjectsEntry OBJECT-TYPE
1022: SYNTAX MteObjectsEntry
1023: MAX-ACCESS not-accessible
1024: STATUS current
1025: DESCRIPTION
1026: "A group of objects. Applications create and delete entries
1027: using mteObjectsEntryStatus."
1028: INDEX { mteOwner, mteObjectsName, mteObjecsIndex }
1028: severe -
unknown object identifier label `mteObjecsIndex'
1029: ::= { mteObjectsTable 1 }
1030:
1031: MteObjectsEntry ::= SEQUENCE {
1032: mteObjectsName SnmpAdminString,
1033: mteObjectsIndex Unsigned32,
1034: mteObjectsID OBJECT IDENTIFIER,
1035: mteObjectsIDWildcard TruthValue,
1036: mteObjectsEntryStatus RowStatus
1037: }
1038:
1039: mteObjectsName OBJECT-TYPE
1040: SYNTAX SnmpAdminString (SIZE (1..32))
1041: MAX-ACCESS not-accessible
1042: STATUS current
1043: DESCRIPTION
1044: "A locally-unique, administratively assigned name for a group of
1045: objects."
1046: ::= { mteObjectsEntry 1 }
1047:
1048: mteObjectsIndex OBJECT-TYPE
1049: SYNTAX Unsigned32 (1..4294967295)
1050: MAX-ACCESS not-accessible
1051: STATUS current
1052: DESCRIPTION
1053: "An arbitrary small integer for the purpose of identifying
1054: individual objects within a mteObjectsName group.
1055:
1056: Objects within a group are placed in the notification in the
1057: numerical order of this index.
1058:
1059: Groups are placed in the notification in the order of the
1060: selections for overall trigger, trigger test, and event.
1061: Within trigger test they are in the same order as the
1062: numerical values of the bits defined for mteTriggerTest.
1063:
1064: Bad object identifiers or a mismatch between truncating the
1065: identifier and the value of mteDeltaDiscontinuityIDWildcard
1066: result in operation as one would expect when providing the
1067: wrong identifier to a Get operation. The Get will fail or get
1068: the wrong object. If the object is not available it is omitted
1069: from the notification."
1070: ::= { mteObjectsEntry 2 }
1071:
1072: mteObjectsID OBJECT-TYPE
1073: SYNTAX OBJECT IDENTIFIER
1074: MAX-ACCESS read-create
1075: STATUS current
1076: DESCRIPTION
1077: "The object identifier of a MIB object to add to a
1078: Notification that results from the firing of a trigger.
1079:
1080: This may be wildcarded by truncating all or part of the
1081: instance portion, in which case the instance portion of the
1082: OID for obtaining this object will be the same as that used
1083: in obtaining the mteTriggerValueID that fired. If such
1084: wildcarding is applied, mteObjectsIDWildcard must be
1085: 'true' and if not it must be 'false'.
1086:
1087: Each instance that fills the wildcard is independent of any
1088: additional instances, that is, wildcarded objects operate
1089: as if there were a separate table entry for each instance
1090: that fills the wildcard without having to actually predict
1091: all possible instances ahead of time."
1092: DEFVAL { zeroDotZero }
1093: ::= { mteObjectsEntry 3 }
1094:
1095: mteObjectsIDWildcard OBJECT-TYPE
1096: SYNTAX TruthValue
1097: MAX-ACCESS read-create
1098: STATUS current
1099: DESCRIPTION
1100: "Control for whether mteObjectsID is to be treated as
1101: fully-specified or wildcarded, with 'true' indicating wildcard."
1102: DEFVAL { false }
1103: ::= { mteObjectsEntry 4 }
1104:
1105: mteObjectsEntryStatus OBJECT-TYPE
1106: SYNTAX RowStatus
1107: MAX-ACCESS read-create
1108: STATUS current
1109: DESCRIPTION
1110: "The control that allows creation and deletion of entries.
1111: Once made active an entry may not be modified except to
1112: delete it."
1113: ::= { mteObjectsEntry 5 }
1114:
1115:
1116: --
1117: -- Event Section
1118: --
1119:
1120: -- Counters
1121:
1122: mteEventFailures OBJECT-TYPE
1123: SYNTAX Counter32
1124: MAX-ACCESS read-only
1125: STATUS current
1126: DESCRIPTION
1127: "The number of times an attempt to invoke an event
1128: has failed. This counts individually for each
1129: attempt in a group of targets or each attempt for a
1130: wildcarded trigger object."
1131: ::= { mteEvent 1 }
1132:
1133:
1134: --
1135: -- Event Table
1136: --
1137:
1138: mteEventTable OBJECT-TYPE
1139: SYNTAX SEQUENCE OF MteEventEntry
1140: MAX-ACCESS not-accessible
1141: STATUS current
1142: DESCRIPTION
1143: "A table of management event action information."
1144: ::= { mteEvent 2 }
1145:
1146: mteEventEntry OBJECT-TYPE
1147: SYNTAX MteEventEntry
1148: MAX-ACCESS not-accessible
1149: STATUS current
1150: DESCRIPTION
1151: "Information about a single event. Applications create and
1152: delete entries using mteEventEntryStatus."
1153: INDEX { mteOwner, IMPLIED mteEventName }
1154: ::= { mteEventTable 1 }
1155:
1156: MteEventEntry ::= SEQUENCE {
1157: mteEventName SnmpAdminString,
1158: mteEventComment SnmpAdminString,
1159: mteEventActions BITS,
1160: mteEventEnabled TruthValue,
1161: mteEventEntryStatus RowStatus
1162: }
1163:
1164: mteEventName OBJECT-TYPE
1165: SYNTAX SnmpAdminString (SIZE (1..32))
1166: MAX-ACCESS not-accessible
1167: STATUS current
1168: DESCRIPTION
1169: "A locally-unique, administratively assigned name for the
1170: event."
1171: ::= { mteEventEntry 1 }
1172:
1173: mteEventComment OBJECT-TYPE
1174: SYNTAX SnmpAdminString
1175: MAX-ACCESS read-create
1176: STATUS current
1177: DESCRIPTION
1178: "A description of the event's function and use."
1179: DEFVAL { ''H }
1180: ::= { mteEventEntry 2 }
1181:
1182: mteEventActions OBJECT-TYPE
1183: SYNTAX BITS { notification(0), set(1) }
1184: MAX-ACCESS read-create
1185: STATUS current
1186: DESCRIPTION
1187: "The actions to perform when this event occurs.
1188:
1189: For 'notification', Traps and/or Informs are sent according
1190: to the configuration in the SNMP Notification MIB.
1191:
1192: For 'set', an SNMP Set operation is performed according to
1193: control values in this entry."
1194: DEFVAL { { 0 } }
1194: error -
object identifier default values must be expressed as a single identifier
1195: ::= { mteEventEntry 3 }
1196:
1197: mteEventEnabled OBJECT-TYPE
1198: SYNTAX TruthValue
1199: MAX-ACCESS read-create
1200: STATUS current
1201: DESCRIPTION
1202: "A control to allow an event to be configured but not used.
1203: When the value is 'false' the event does not execute even if
1204: triggered."
1205: DEFVAL { false }
1206: ::= { mteEventEntry 4 }
1207:
1208: mteEventEntryStatus OBJECT-TYPE
1209: SYNTAX RowStatus
1210: MAX-ACCESS read-create
1211: STATUS current
1212: DESCRIPTION
1213: "The control that allows creation and deletion of entries.
1214: Once made active an entry may not be modified except to
1215: delete it."
1216: ::= { mteEventEntry 5 }
1217:
1218: --
1219: -- Event Notification Table
1220: --
1221:
1222: mteEventNotificationTable OBJECT-TYPE
1223: SYNTAX SEQUENCE OF MteEventNotificationEntry
1224: MAX-ACCESS not-accessible
1225: STATUS current
1226: DESCRIPTION
1227: "A table of management event action notification information."
1228: ::= { mteEvent 3 }
1229:
1230: mteEventNotificationEntry OBJECT-TYPE
1231: SYNTAX MteEventNotificationEntry
1232: MAX-ACCESS not-accessible
1233: STATUS current
1234: DESCRIPTION
1235: "Information about a single event's notification. Entries
1236: automatically exist in this this table for each mteTriggerEntry
1237: that has 'notification' set in mteEventAction."
1238: INDEX { mteOwner, IMPLIED mteTriggerName }
1239: ::= { mteEventNotificationTable 1 }
1240:
1241: MteEventNotificationEntry ::= SEQUENCE {
1242: mteEventNotification OBJECT IDENTIFIER,
1243: mteEventNotificationObjectsOwner SnmpAdminString,
1244: mteEventNotificationObjects SnmpAdminString
1245: }
1246:
1247: mteEventNotification OBJECT-TYPE
1248: SYNTAX OBJECT IDENTIFIER
1249: MAX-ACCESS read-write
1250: STATUS current
1251: DESCRIPTION
1252: "The object identifier from the NOTIFICATION-TYPE for the
1253: notification to use if metEventActions has 'notification' set."
1254: DEFVAL { zeroDotZero }
1255: ::= { mteEventNotificationEntry 1 }
1256:
1257: mteEventNotificationObjectsOwner OBJECT-TYPE
1258: SYNTAX SnmpAdminString (SIZE (0..32))
1259: MAX-ACCESS read-write
1260: STATUS current
1261: DESCRIPTION
1262: "To go with mteEventNotificationObjects, the mteOwner of a
1263: group of objects from mteObjectsTable."
1264: DEFVAL { ''H }
1265: ::= { mteEventNotificationEntry 2 }
1266:
1267: mteEventNotificationObjects OBJECT-TYPE
1268: SYNTAX SnmpAdminString (SIZE (0..32))
1269: MAX-ACCESS read-write
1270: STATUS current
1271: DESCRIPTION
1272: "The mteObjectsName of a group of objects from
1273: mteObjectsTable if mteEventActions has 'notification' set.
1274: These objects are to be added to any Notification generated by
1275: this event.
1276:
1277: Objects may also be added based on the trigger that stimulated
1278: the event.
1279:
1280: A length of 0 indicates no additional objects."
1281: DEFVAL { ''H }
1282: ::= { mteEventNotificationEntry 3 }
1283:
1284:
1285: --
1286: -- Event Set Table
1287: --
1288:
1289: mteEventSetTable OBJECT-TYPE
1290: SYNTAX SEQUENCE OF MteEventSetEntry
1291: MAX-ACCESS not-accessible
1292: STATUS current
1293: DESCRIPTION
1294: "A table of management event action information."
1295: ::= { mteEvent 4 }
1296:
1297: mteEventSetEntry OBJECT-TYPE
1298: SYNTAX MteEventSetEntry
1299: MAX-ACCESS not-accessible
1300: STATUS current
1301: DESCRIPTION
1302: "Information about a single event's set option. Entries
1303: automatically exist in this this table for each mteTriggerEntry
1304: that has 'set' set in mteEventAction."
1305: INDEX { mteOwner, IMPLIED mteTriggerName }
1306: ::= { mteEventSetTable 1 }
1307:
1308: MteEventSetEntry ::= SEQUENCE {
1309: mteEventSetObject OBJECT IDENTIFIER,
1310: mteEventSetObjectWildcard TruthValue,
1311: mteEventSetValue Integer32,
1312: mteEventSetTargetTag SnmpTagValue,
1313: mteEventSetContextName SnmpAdminString,
1314: mteEventSetContextNameWildcard TruthValue
1315: }
1316:
1317: mteEventSetObject OBJECT-TYPE
1318: SYNTAX OBJECT IDENTIFIER
1319: MAX-ACCESS read-write
1320: STATUS current
1321: DESCRIPTION
1322: "The object identifier from the MIB object to set if
1323: mteEventActions has 'set' set.
1324:
1325: This object identifier may be wildcarded by leaving
1326: sub-identifiers off the end, in which case
1327: nteEventSetObjectWildCard must be 'true'.
1328:
1329: If mteEventSetObject is wildcarded the instance used to set the
1330: object to which it points is the same as the instance from the
1331: value of mteTriggerValueID that triggered the event.
1332:
1333: Each instance that fills the wildcard is independent of any
1334: additional instances, that is, wildcarded objects operate
1335: as if there were a separate table entry for each instance
1336: that fills the wildcard without having to actually predict
1337: all possible instances ahead of time.
1338:
1339: Bad object identifiers or a mismatch between truncating the
1340: identifier and the value of mteSetObjectWildcard
1341: result in operation as one would expect when providing the
1342: wrong identifier to a Set operation. The Set will fail or set
1343: the wrong object. If the value syntax of the destination
1344: object is not correct, the Set fails with the normal SNMP
1345: error code."
1346: DEFVAL { zeroDotZero }
1347: ::= { mteEventSetEntry 1 }
1348:
1349: mteEventSetObjectWildcard OBJECT-TYPE
1350: SYNTAX TruthValue
1351: MAX-ACCESS read-write
1352: STATUS current
1353: DESCRIPTION
1354: "Control over whether mteEventSetObject is to be treated as
1355: fully-specified or wildcarded, with 'true' indicating wildcard
1356: if mteEventActions has 'set' set."
1357: DEFVAL { false }
1358: ::= { mteEventSetEntry 2 }
1359:
1360: mteEventSetValue OBJECT-TYPE
1361: SYNTAX Integer32
1362: MAX-ACCESS read-write
1363: STATUS current
1364: DESCRIPTION
1365: "The value to which to set the object at mteEventSetObject
1366: if mteEventActions has 'set' set."
1367: DEFVAL { 0 }
1368: ::= { mteEventSetEntry 3 }
1369:
1370: mteEventSetTargetTag OBJECT-TYPE
1371: SYNTAX SnmpTagValue
1372: MAX-ACCESS read-write
1373: STATUS current
1374: DESCRIPTION
1375: "The tag for the target(s) at which to set the object at
1376: mteEventSetObject to mteEventSetValue if mteEventActions
1377: has 'set' set.
1378:
1379: Systems limited to self management may not accept a non-zero
1380: length for the value of this object.
1381:
1382: A length of 0 indicates the local system. In this case,
1383: access to the objects indicated by mteEventSetObject is under
1384: the security credentials of the requester that set
1385: mteTriggerEntryStatus to 'active'. Those credentials are the
1386: input parameters for isAccessAllowed from the Architecture for
1387: Describing SNMP Management Frameworks.
1388:
1389: Otherwise access rights are checked according to the security
1390: parameters resulting from the tag."
1391: DEFVAL { ''H }
1392: ::= { mteEventSetEntry 4 }
1393:
1394: mteEventSetContextName OBJECT-TYPE
1395: SYNTAX SnmpAdminString
1396: MAX-ACCESS read-write
1397: STATUS current
1398: DESCRIPTION
1399: "The management context in which to set mteEventObjectID.
1400: if mteEventActions has 'set' set.
1401:
1402: This may be wildcarded by leaving characters off the end. To
1403: indicate such wildcarding mteEventSetContextNameWildcard must
1404: be 'true'.
1405:
1406: If this context name is wildcarded the value used to complete
1407: the wildcarding of mteTriggerContextName will be appended."
1408: DEFVAL { ''H }
1409: ::= { mteEventSetEntry 5 }
1410:
1411: mteEventSetContextNameWildcard OBJECT-TYPE
1412: SYNTAX TruthValue
1413: MAX-ACCESS read-write
1414: STATUS current
1415: DESCRIPTION
1416: "Control for whether mteEventSetContextName is to be treated as
1417: fully-specified or wildcarded, with 'true' indicating wildcard
1418: if mteEventActions has 'set' set."
1419: DEFVAL { false }
1420: ::= { mteEventSetEntry 6 }
1421:
1422:
1423: --
1424: -- Notifications
1425: --
1426:
1427: dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::= { dismanEventMIB 2 }
1428: dismanEventMIBNotifications OBJECT IDENTIFIER ::=
1429: { dismanEventMIBNotificationPrefix 0 }
1430: dismanEventMIBNotificationObjects OBJECT IDENTIFIER
1431: ::= { dismanEventMIBNotificationPrefix 1 }
1432:
1433: --
1434: -- Notification Objects
1435: --
1436:
1437: mteHotTrigger OBJECT-TYPE
1438: SYNTAX SnmpAdminString
1439: MAX-ACCESS accessible-for-notify
1440: STATUS current
1441: DESCRIPTION
1442: "The name of the trigger causing the notification."
1443: ::= { dismanEventMIBNotificationObjects 1 }
1444:
1445: mteHotTargetName OBJECT-TYPE
1446: SYNTAX SnmpAdminString
1447: MAX-ACCESS accessible-for-notify
1448: STATUS current
1449: DESCRIPTION
1450: "The SNMP Target MIB's snmpTargetAddrName related to the
1451: notification."
1452: ::= { dismanEventMIBNotificationObjects 2 }
1453:
1454: mteHotContextName OBJECT-TYPE
1455: SYNTAX SnmpAdminString
1456: MAX-ACCESS accessible-for-notify
1457: STATUS current
1458: DESCRIPTION
1459: "The context name related to the notification. This must be as
1460: fully-qualified as possible, including filling in wildcard
1461: information determined in processing."
1462: ::= { dismanEventMIBNotificationObjects 3 }
1463:
1464: mteHotOID OBJECT-TYPE
1465: SYNTAX OBJECT IDENTIFIER
1466: MAX-ACCESS accessible-for-notify
1467: STATUS current
1468: DESCRIPTION
1469: "The object identifier of the destination object related to the
1470: notification. This must be as fully-qualified as possible,
1471: inluding filling in wildcard informaation determined in
1472: processing.
1473:
1474: For a trigger-related notification this is from
1475: mteTriggerValueID.
1476:
1477: For a set failure this is from mteEventSetObject."
1478: ::= { dismanEventMIBNotificationObjects 4 }
1479:
1480: mteHotValue OBJECT-TYPE
1481: SYNTAX Integer32
1482: MAX-ACCESS accessible-for-notify
1483: STATUS current
1484: DESCRIPTION
1485: "The value of the object at mteTriggerValueID when a
1486: trigger fired."
1487: ::= { dismanEventMIBNotificationObjects 5 }
1488:
1489: mteFailedReason OBJECT-TYPE
1490: SYNTAX FailureReason
1491: MAX-ACCESS accessible-for-notify
1492: STATUS current
1493: DESCRIPTION
1494: "The reason for the failure of an attempt to check for a
1495: trigger condition or set an object in response to an event."
1496: ::= { dismanEventMIBNotificationObjects 6 }
1497:
1498: --
1499: -- Notifications
1500: --
1501:
1502: mteTriggerFired NOTIFICATION-TYPE
1502: change recommended -
warning: notification `mteTriggerFired' must be contained in at least one conformance group
1503: OBJECTS { mteHotTrigger,
1504: mteHotTargetName,
1505: mteHotContextName,
1506: mteHotOID,
1507: mteHotValue }
1508: STATUS current
1509: DESCRIPTION
1510: "Notification that the trigger indicated by the object
1511: instances has fired, for triggers with mteTriggerType
1512: 'boolean'."
1513: ::= { dismanEventMIBNotifications 1 }
1514:
1515: mteTriggerRising NOTIFICATION-TYPE
1515: change recommended -
warning: notification `mteTriggerRising' must be contained in at least one conformance group
1516: OBJECTS { mteHotTrigger,
1517: mteHotTargetName,
1518: mteHotContextName,
1519: mteHotOID,
1520: mteHotValue }
1521: STATUS current
1522: DESCRIPTION
1523: "Notification that the rising threshold was met for triggers
1524: with mteTriggerType 'threshold'."
1525: ::= { dismanEventMIBNotifications 2 }
1526:
1527: mteTriggerFalling NOTIFICATION-TYPE
1527: change recommended -
warning: notification `mteTriggerFalling' must be contained in at least one conformance group
1528: OBJECTS { mteHotTrigger,
1529: mteHotTargetName,
1530: mteHotContextName,
1531: mteHotOID,
1532: mteHotValue }
1533: STATUS current
1534: DESCRIPTION
1535: "Notification that the falling threshold was met for triggers
1536: with mteTriggerType 'threshold'."
1537: ::= { dismanEventMIBNotifications 3 }
1538:
1539: mteTriggerFailure NOTIFICATION-TYPE
1539: change recommended -
warning: notification `mteTriggerFailure' must be contained in at least one conformance group
1540: OBJECTS { mteHotTrigger,
1541: mteHotTargetName,
1542: mteHotContextName,
1543: mteHotOID,
1544: mteFailedReason }
1545: STATUS current
1546: DESCRIPTION
1547: "Notification that an attempt to check a trigger has failed.
1548:
1549: The network manager must enable this notification only with
1550: a certain fear and trembling, as it can easily crowd out more
1551: important information. It should be used only to help diagnose
1552: a problem that has appeared in the error counters and can not
1553: be found otherwise."
1554: ::= { dismanEventMIBNotifications 4 }
1555:
1556: mteEventSetFailure NOTIFICATION-TYPE
1556: change recommended -
warning: notification `mteEventSetFailure' must be contained in at least one conformance group
1557: OBJECTS { mteHotTrigger,
1558: mteHotTargetName,
1559: mteHotContextName,
1560: mteHotOID,
1561: mteFailedReason }
1562: STATUS current
1563: DESCRIPTION
1564: "Notification that an attempt to do a set in response to an
1565: event has failed.
1566:
1567: The network manager must enable this notification only with
1568: a certain fear and trembling, as it can easily crowd out more
1569: important information. It should be used only to help diagnose
1570: a problem that has appeared in the error counters and can not
1571: be found otherwise."
1572: ::= { dismanEventMIBNotifications 5 }
1573:
1574:
1575: --
1576: -- Conformance
1577: --
1578: dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 }
1579: dismanEventMIBCompliances OBJECT IDENTIFIER ::= { dismanEventMIBConformance 1 }
1580: dismanEventMIBGroups OBJECT IDENTIFIER ::= { dismanEventMIBConformance 2 }
1581:
1582: -- Compliance
1583:
1584: dismanEventMIBCompliance MODULE-COMPLIANCE
1585: STATUS current
1586: DESCRIPTION
1587: "The compliance statement for entities which implement
1588: the Event MIB."
1589: MODULE -- this module
1590: MANDATORY-GROUPS {
1591: dismanEventResourceGroup,
1592: dismanEventTriggerGroup,
1593: dismanEventObjectsGroup,
1594: dismanEventEventGroup,
1595: dismanEventNotificationObjectGroup,
1596: dismanEventNotificationGroup
1597: }
1597: severe -
unknown object identifier label `dismanEventNotificationGroup'
1598:
1599: OBJECT mteTriggerTargetTag
1600: MIN-ACCESS read-only
1601: DESCRIPTION
1602: "Write access is not required, thus limiting
1603: monitoring to the local system or preconfigured
1604: remote systems."
1605:
1606: OBJECT mteEventSetTargetTag
1607: MIN-ACCESS read-only
1608: DESCRIPTION
1609: "Write access is not required, thus limiting
1610: setting to the local system or preconfigured
1611: remote systems."
1612:
1613: OBJECT mteTriggerValueIDWildcard
1614: MIN-ACCESS read-only
1615: DESCRIPTION
1616: "Write access is not required, thus allowing
1617: the system not to implement wildcarding."
1618:
1619: OBJECT mteTriggerContextNameWildcard
1620: MIN-ACCESS read-only
1621: DESCRIPTION
1622: "Write access is not required, thus allowing
1623: the system not to implement wildcarding."
1624:
1625:
1626: OBJECT mteObjectsIDWildcard
1627: MIN-ACCESS read-only
1628: DESCRIPTION
1629: "Write access is not required, thus allowing
1630: the system not to implement wildcarding."
1631:
1632: OBJECT mteEventSetContextNameWildcard
1633: MIN-ACCESS read-only
1634: DESCRIPTION
1635: "Write access is not required, thus allowing
1636: the system not to implement wildcarding."
1637:
1638: ::= { dismanEventMIBCompliances 1 }
1639:
1640: -- Units of Conformance
1641:
1642:
1643:
1644: dismanEventResourceGroup OBJECT-GROUP
1645: OBJECTS {
1646: mteResourceSampleMinimum,
1647: mteResourceSampleInstanceMaximum,
1648: mteResourceSampleInstances,
1649: mteResourceSampleInstancesHigh,
1650: mteResourceSampleInstanceLacks
1651: }
1652: STATUS current
1653: DESCRIPTION
1654: "Event resource status and control objects."
1655: ::= { dismanEventMIBGroups 1 }
1656:
1657: dismanEventTriggerGroup OBJECT-GROUP
1658: OBJECTS {
1659: mteTriggerFailures,
1660:
1661: mteTriggerComment,
1662: mteTriggerTest,
1663: mteTriggerSampleType,
1664: mteTriggerValueID,
1665: mteTriggerValueIDWildcard,
1666: mteTriggerTargetTag,
1667: mteTriggerContextName,
1668: mteTriggerContextNameWildcard,
1669: mteTriggerFrequency,
1670: mteTriggerObjectsOwner,
1671: mteTriggerObjects,
1672: mteTriggerEnabled,
1673: mteTriggerEntryStatus,
1674:
1675: mteTriggerDeltaDiscontinuityID,
1676: mteTriggerDeltaDiscontinuityIDWildcard,
1677: mteTriggerDeltaDiscontinuityIDType,
1678:
1679: mteTriggerExistenceTest,
1680: mteTriggerExistenceStartup,
1681: mteTriggerExistenceObjectsOwner,
1682: mteTriggerExistenceObjects,
1683: mteTriggerExistenceEventOwner,
1684: mteTriggerExistenceEvent,
1685:
1686: mteTriggerBooleanComparison,
1687: mteTriggerBooleanValue,
1688: mteTriggerBooleanStartup,
1689: mteTriggerBooleanObjectsOwner,
1690: mteTriggerBooleanObjects,
1691: mteTriggerBooleanEventOwner,
1692: mteTriggerBooleanEvent,
1693:
1694: mteTriggerThresholdValue,
1695: mteTriggerThresholdStartup,
1696: mteTriggerThresholdObjectsOwner,
1697: mteTriggerThresholdObjects,
1698: mteTriggerThresholdRising,
1699: mteTriggerThresholdFalling,
1700: mteTriggerThresholdRisingEventOwner,
1701: mteTriggerThresholdRisingEvent,
1702: mteTriggerThresholdFallingEventOwner,
1703: mteTriggerThresholdFallingEvent
1704: }
1705: STATUS current
1706: DESCRIPTION
1707: "Event triggers."
1708: ::= { dismanEventMIBGroups 2 }
1709:
1710: dismanEventObjectsGroup OBJECT-GROUP
1711: OBJECTS {
1712: mteObjectsID,
1713: mteObjectsIDWildcard,
1714: mteObjectsEntryStatus
1715: }
1716: STATUS current
1717: DESCRIPTION
1718: "Supplemental objects."
1719: ::= { dismanEventMIBGroups 3 }
1720:
1721: dismanEventEventGroup OBJECT-GROUP
1722: OBJECTS {
1723: mteEventFailures,
1724:
1725: mteEventComment,
1726: mteEventActions,
1727: mteEventEnabled,
1728: mteEventEntryStatus,
1729:
1730: mteEventNotification,
1731: mteEventNotificationObjectsOwner,
1732: mteEventNotificationObjects,
1733:
1734: mteEventSetObject,
1735: mteEventSetObjectWildcard,
1736: mteEventSetValue,
1737: mteEventSetTargetTag,
1738: mteEventSetContextName,
1739: mteEventSetContextNameWildcard
1740: }
1741: STATUS current
1742: DESCRIPTION
1743: "Events."
1744: ::= { dismanEventMIBGroups 4 }
1745:
1746: dismanEventNotificationObjectGroup OBJECT-GROUP
1747: OBJECTS {
1748: mteHotTrigger,
1749: mteHotTargetName,
1750: mteHotContextName,
1751: mteHotOID,
1752: mteHotValue,
1753: mteFailedReason
1754: }
1755: STATUS current
1756: DESCRIPTION
1757: "Notification objects."
1758: ::= { dismanEventMIBGroups 5 }
1759:
1760: dismanEventNotificationGroup NOTIFICATION-GROUP
1761: OBJECTS {
1761: severe -
syntax error, unexpected OBJECTS, expecting NOTIFICATIONS
1762: mteTriggerFired,
1763: mteTriggerRising,
1764: mteTriggerFalling,
1765: mteTriggerFailure,
1766: mteEventSetFailure
1767: }
1767: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1768: STATUS current
1768: severe -
syntax error, unexpected STATUS
1769: DESCRIPTION
1770: "Notifications."
1771: ::= { dismanEventMIBGroups 6 }
1771: warning -
warning: flushing recent incorrect declaration, see previous error(s)
1772:
1773: END
1774:
1775: --
1776: -- Copyright (C) The Internet Society (1999). All Rights Reserved.
1777: --
1778: -- This document and translations of it may be copied and furnished to
1779: -- others, and derivative works that comment on or otherwise explain it or
1780: -- assist in its implementation may be prepared, copied, published and
1781: -- distributed, in whole or in part, without restriction of any kind,
1782: -- provided that the above copyright notice and this paragraph are included
1783: -- on all such copies and derivative works. However, this document itself
1784: -- may not be modified in any way, such as by removing the copyright notice
1785: -- or references to the Internet Society or other Internet organizations,
1786: -- except as needed for the purpose of developing Internet standards in
1787: -- which case the procedures for copyrights defined in the Internet
1788: -- Standards process must be followed, or as required to translate it into
1789: -- languages other than English.
1790: --
1791: -- The limited permissions granted above are perpetual and will not be
1792: -- revoked by the Internet Society or its successors or assigns.
1793: --
1794: -- This document and the information contained herein is provided on an "AS
1795: -- IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
1796: -- FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
1797: -- LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
1798: -- INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
1799: -- FITNESS FOR A PARTICULAR PURPOSE.
1800: