telemetry-snmp 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +7 -0
- data/.github/workflows/rspec.yml +44 -0
- data/.github/workflows/rubocop.yml +28 -0
- data/.github/workflows/sourcehawk-scan.yml +20 -0
- data/.gitignore +14 -0
- data/.rspec +4 -0
- data/.rubocop.yml +26 -0
- data/CHANGELOG.md +4 -0
- data/CODE_OF_CONDUCT.md +75 -0
- data/CONTRIBUTING.md +54 -0
- data/Gemfile +10 -0
- data/INDIVIDUAL_CONTRIBUTOR_LICENSE.md +30 -0
- data/LICENSE +201 -0
- data/NOTICE.txt +9 -0
- data/README.md +54 -0
- data/attribution.txt +1 -0
- data/config.ru +15 -0
- data/exe/snmp_collector +55 -0
- data/lib/telemetry/snmp.rb +23 -0
- data/lib/telemetry/snmp/api.rb +55 -0
- data/lib/telemetry/snmp/auth.rb +54 -0
- data/lib/telemetry/snmp/auth/defaults.rb +41 -0
- data/lib/telemetry/snmp/client.rb +104 -0
- data/lib/telemetry/snmp/controllers/device_creds.rb +105 -0
- data/lib/telemetry/snmp/controllers/devices.rb +94 -0
- data/lib/telemetry/snmp/controllers/oid_groups.rb +71 -0
- data/lib/telemetry/snmp/controllers/oids.rb +80 -0
- data/lib/telemetry/snmp/controllers/users.rb +81 -0
- data/lib/telemetry/snmp/controllers/walks.rb +89 -0
- data/lib/telemetry/snmp/data.rb +69 -0
- data/lib/telemetry/snmp/data/default_opts.rb +73 -0
- data/lib/telemetry/snmp/data/migrations/001_device_creds.rb +19 -0
- data/lib/telemetry/snmp/data/migrations/002_create_devices_table.rb +31 -0
- data/lib/telemetry/snmp/data/migrations/003_create_oids_tables.rb +16 -0
- data/lib/telemetry/snmp/data/migrations/004_create_oid_groups.rb +15 -0
- data/lib/telemetry/snmp/data/migrations/005_create_oids_oid_groups.rb +17 -0
- data/lib/telemetry/snmp/data/migrations/006_device_to_oid_group.rb +15 -0
- data/lib/telemetry/snmp/data/migrations/007_create_users.rb +20 -0
- data/lib/telemetry/snmp/data/migrations/008_create_walks_table.rb +14 -0
- data/lib/telemetry/snmp/data/migrations/009_create_tag_name_column.rb +7 -0
- data/lib/telemetry/snmp/data/migrations/010_create_user_audit_table.rb +18 -0
- data/lib/telemetry/snmp/data/models/device.rb +11 -0
- data/lib/telemetry/snmp/data/models/device_cred.rb +11 -0
- data/lib/telemetry/snmp/data/models/oid.rb +10 -0
- data/lib/telemetry/snmp/data/models/oid_group.rb +10 -0
- data/lib/telemetry/snmp/data/models/oid_oid_groups.rb +10 -0
- data/lib/telemetry/snmp/data/models/oid_walk.rb +10 -0
- data/lib/telemetry/snmp/data/models/user.rb +10 -0
- data/lib/telemetry/snmp/data/models/user_audit_log.rb +19 -0
- data/lib/telemetry/snmp/mibs/AGENTX-MIB.txt +527 -0
- data/lib/telemetry/snmp/mibs/AIRPORT-BASESTATION-3-MIB.txt +461 -0
- data/lib/telemetry/snmp/mibs/BRIDGE-MIB.txt +1472 -0
- data/lib/telemetry/snmp/mibs/DISMAN-EVENT-MIB.txt +1882 -0
- data/lib/telemetry/snmp/mibs/DISMAN-SCHEDULE-MIB.txt +699 -0
- data/lib/telemetry/snmp/mibs/DISMAN-SCRIPT-MIB.txt +1764 -0
- data/lib/telemetry/snmp/mibs/EtherLike-MIB.txt +1862 -0
- data/lib/telemetry/snmp/mibs/HCNUM-TC.txt +118 -0
- data/lib/telemetry/snmp/mibs/HOST-RESOURCES-MIB.txt +1540 -0
- data/lib/telemetry/snmp/mibs/HOST-RESOURCES-TYPES.txt +389 -0
- data/lib/telemetry/snmp/mibs/IANA-ADDRESS-FAMILY-NUMBERS-MIB.txt +123 -0
- data/lib/telemetry/snmp/mibs/IANA-LANGUAGE-MIB.txt +123 -0
- data/lib/telemetry/snmp/mibs/IANA-RTPROTO-MIB.txt +91 -0
- data/lib/telemetry/snmp/mibs/IANAifType-MIB.txt +619 -0
- data/lib/telemetry/snmp/mibs/IF-INVERTED-STACK-MIB.txt +149 -0
- data/lib/telemetry/snmp/mibs/IF-MIB.txt +1814 -0
- data/lib/telemetry/snmp/mibs/INET-ADDRESS-MIB.txt +402 -0
- data/lib/telemetry/snmp/mibs/IP-FORWARD-MIB.txt +1277 -0
- data/lib/telemetry/snmp/mibs/IP-MIB.txt +4993 -0
- data/lib/telemetry/snmp/mibs/IPV6-FLOW-LABEL-MIB.txt +58 -0
- data/lib/telemetry/snmp/mibs/IPV6-ICMP-MIB.txt +529 -0
- data/lib/telemetry/snmp/mibs/IPV6-MIB.txt +1443 -0
- data/lib/telemetry/snmp/mibs/IPV6-TC.txt +67 -0
- data/lib/telemetry/snmp/mibs/IPV6-TCP-MIB.txt +211 -0
- data/lib/telemetry/snmp/mibs/IPV6-UDP-MIB.txt +141 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-AGENT-MIB.txt +554 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-EXAMPLES-MIB.txt +285 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-EXTEND-MIB.txt +325 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-MIB.txt +67 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-PASS-MIB.txt +124 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-TC.txt +128 -0
- data/lib/telemetry/snmp/mibs/NET-SNMP-VACM-MIB.txt +154 -0
- data/lib/telemetry/snmp/mibs/NOTIFICATION-LOG-MIB.txt +753 -0
- data/lib/telemetry/snmp/mibs/PAN-COMMON-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-COMMON-MIB.my +2293 -0
- data/lib/telemetry/snmp/mibs/PAN-ENTITY-EXT-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-ENTITY-EXT-MIB.my +293 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-REG-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-REG-MIB.my +84 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-TC-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-GLOBAL-TC-MIB.my +68 -0
- data/lib/telemetry/snmp/mibs/PAN-LC-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-LC-MIB.my +204 -0
- data/lib/telemetry/snmp/mibs/PAN-PRODUCT-MIB.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-PRODUCT-MIB.my +305 -0
- data/lib/telemetry/snmp/mibs/PAN-TRAPS.md5 +1 -0
- data/lib/telemetry/snmp/mibs/PAN-TRAPS.my +7809 -0
- data/lib/telemetry/snmp/mibs/RFC-1215.txt +38 -0
- data/lib/telemetry/snmp/mibs/RFC1155-SMI.txt +119 -0
- data/lib/telemetry/snmp/mibs/RFC1213-MIB.txt +2613 -0
- data/lib/telemetry/snmp/mibs/RMON-MIB.txt +3980 -0
- data/lib/telemetry/snmp/mibs/SCTP-MIB.txt +1342 -0
- data/lib/telemetry/snmp/mibs/SMUX-MIB.txt +160 -0
- data/lib/telemetry/snmp/mibs/SNMP-COMMUNITY-MIB.txt +429 -0
- data/lib/telemetry/snmp/mibs/SNMP-FRAMEWORK-MIB.txt +526 -0
- data/lib/telemetry/snmp/mibs/SNMP-MPD-MIB.txt +145 -0
- data/lib/telemetry/snmp/mibs/SNMP-NOTIFICATION-MIB.txt +589 -0
- data/lib/telemetry/snmp/mibs/SNMP-PROXY-MIB.txt +294 -0
- data/lib/telemetry/snmp/mibs/SNMP-TARGET-MIB.txt +660 -0
- data/lib/telemetry/snmp/mibs/SNMP-USER-BASED-SM-MIB.txt +912 -0
- data/lib/telemetry/snmp/mibs/SNMP-USM-AES-MIB.txt +62 -0
- data/lib/telemetry/snmp/mibs/SNMP-USM-DH-OBJECTS-MIB.txt +532 -0
- data/lib/telemetry/snmp/mibs/SNMP-VIEW-BASED-ACM-MIB.txt +830 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-CONF.txt +322 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-MIB.txt +854 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-SMI.txt +344 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-TC.txt +772 -0
- data/lib/telemetry/snmp/mibs/SNMPv2-TM.txt +176 -0
- data/lib/telemetry/snmp/mibs/TCP-MIB.txt +785 -0
- data/lib/telemetry/snmp/mibs/TRANSPORT-ADDRESS-MIB.txt +421 -0
- data/lib/telemetry/snmp/mibs/TUNNEL-MIB.txt +738 -0
- data/lib/telemetry/snmp/mibs/UCD-DEMO-MIB.txt +74 -0
- data/lib/telemetry/snmp/mibs/UCD-DISKIO-MIB.txt +171 -0
- data/lib/telemetry/snmp/mibs/UCD-DLMOD-MIB.txt +124 -0
- data/lib/telemetry/snmp/mibs/UCD-IPFWACC-MIB.txt +327 -0
- data/lib/telemetry/snmp/mibs/UCD-SNMP-MIB.txt +1712 -0
- data/lib/telemetry/snmp/mibs/UDP-MIB.txt +549 -0
- data/lib/telemetry/snmp/publisher.rb +130 -0
- data/lib/telemetry/snmp/version.rb +7 -0
- data/sourcehawk.yml +4 -0
- data/telemetry-snmp.gemspec +48 -0
- metadata +456 -0
|
@@ -0,0 +1,1882 @@
|
|
|
1
|
+
DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN
|
|
2
|
+
|
|
3
|
+
IMPORTS
|
|
4
|
+
MODULE-IDENTITY, OBJECT-TYPE,
|
|
5
|
+
Integer32, Unsigned32,
|
|
6
|
+
NOTIFICATION-TYPE, Counter32,
|
|
7
|
+
Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI
|
|
8
|
+
TEXTUAL-CONVENTION, RowStatus,
|
|
9
|
+
TruthValue FROM SNMPv2-TC
|
|
10
|
+
|
|
11
|
+
MODULE-COMPLIANCE, OBJECT-GROUP,
|
|
12
|
+
NOTIFICATION-GROUP FROM SNMPv2-CONF
|
|
13
|
+
sysUpTime FROM SNMPv2-MIB
|
|
14
|
+
SnmpTagValue FROM SNMP-TARGET-MIB
|
|
15
|
+
SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
|
|
16
|
+
|
|
17
|
+
dismanEventMIB MODULE-IDENTITY
|
|
18
|
+
LAST-UPDATED "200010160000Z" -- 16 October 2000
|
|
19
|
+
ORGANIZATION "IETF Distributed Management Working Group"
|
|
20
|
+
CONTACT-INFO "Ramanathan Kavasseri
|
|
21
|
+
Cisco Systems, Inc.
|
|
22
|
+
170 West Tasman Drive,
|
|
23
|
+
San Jose CA 95134-1706.
|
|
24
|
+
Phone: +1 408 526 4527
|
|
25
|
+
Email: ramk@cisco.com"
|
|
26
|
+
DESCRIPTION
|
|
27
|
+
"The MIB module for defining event triggers and actions
|
|
28
|
+
for network management purposes."
|
|
29
|
+
-- Revision History
|
|
30
|
+
|
|
31
|
+
REVISION "200010160000Z" -- 16 October 2000
|
|
32
|
+
DESCRIPTION "This is the initial version of this MIB.
|
|
33
|
+
Published as RFC 2981"
|
|
34
|
+
::= { mib-2 88 }
|
|
35
|
+
|
|
36
|
+
dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 }
|
|
37
|
+
|
|
38
|
+
-- Management Triggered Event (MTE) objects
|
|
39
|
+
|
|
40
|
+
mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 }
|
|
41
|
+
mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 }
|
|
42
|
+
mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 }
|
|
43
|
+
mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 }
|
|
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
|
+
|
|
60
|
+
returning that code.
|
|
61
|
+
|
|
62
|
+
The second group, numbered greater than 0, are copied
|
|
63
|
+
directly from SNMP protocol operations and are intended to
|
|
64
|
+
carry exactly the meanings defined for the protocol as returned
|
|
65
|
+
in an SNMP response.
|
|
66
|
+
|
|
67
|
+
localResourceLack some local resource such as memory
|
|
68
|
+
lacking or
|
|
69
|
+
mteResourceSampleInstanceMaximum
|
|
70
|
+
exceeded
|
|
71
|
+
badDestination unrecognized domain name or otherwise
|
|
72
|
+
invalid destination address
|
|
73
|
+
destinationUnreachable can't get to destination address
|
|
74
|
+
noResponse no response to SNMP request
|
|
75
|
+
badType the data syntax of a retrieved object
|
|
76
|
+
as not as expected
|
|
77
|
+
sampleOverrun another sample attempt occurred before
|
|
78
|
+
the previous one completed"
|
|
79
|
+
SYNTAX INTEGER { localResourceLack(-1),
|
|
80
|
+
badDestination(-2),
|
|
81
|
+
destinationUnreachable(-3),
|
|
82
|
+
noResponse(-4),
|
|
83
|
+
badType(-5),
|
|
84
|
+
sampleOverrun(-6),
|
|
85
|
+
noError(0),
|
|
86
|
+
tooBig(1),
|
|
87
|
+
noSuchName(2),
|
|
88
|
+
badValue(3),
|
|
89
|
+
readOnly(4),
|
|
90
|
+
genErr(5),
|
|
91
|
+
noAccess(6),
|
|
92
|
+
wrongType(7),
|
|
93
|
+
wrongLength(8),
|
|
94
|
+
wrongEncoding(9),
|
|
95
|
+
wrongValue(10),
|
|
96
|
+
noCreation(11),
|
|
97
|
+
inconsistentValue(12),
|
|
98
|
+
resourceUnavailable(13),
|
|
99
|
+
commitFailed(14),
|
|
100
|
+
undoFailed(15),
|
|
101
|
+
authorizationError(16),
|
|
102
|
+
notWritable(17),
|
|
103
|
+
inconsistentName(18) }
|
|
104
|
+
--
|
|
105
|
+
|
|
106
|
+
-- Resource Control Section
|
|
107
|
+
--
|
|
108
|
+
|
|
109
|
+
mteResourceSampleMinimum OBJECT-TYPE
|
|
110
|
+
SYNTAX Integer32 (1..2147483647)
|
|
111
|
+
UNITS "seconds"
|
|
112
|
+
MAX-ACCESS read-write
|
|
113
|
+
STATUS current
|
|
114
|
+
DESCRIPTION
|
|
115
|
+
"The minimum mteTriggerFrequency this system will
|
|
116
|
+
accept. A system may use the larger values of this minimum to
|
|
117
|
+
lessen the impact of constant sampling. For larger
|
|
118
|
+
sampling intervals the system samples less often and
|
|
119
|
+
suffers less overhead. This object provides a way to enforce
|
|
120
|
+
such lower overhead for all triggers created after it is
|
|
121
|
+
set.
|
|
122
|
+
|
|
123
|
+
Unless explicitly resource limited, a system's value for
|
|
124
|
+
this object SHOULD be 1, allowing as small as a 1 second
|
|
125
|
+
interval for ongoing trigger sampling.
|
|
126
|
+
|
|
127
|
+
Changing this value will not invalidate an existing setting
|
|
128
|
+
of mteTriggerFrequency."
|
|
129
|
+
::= { mteResource 1 }
|
|
130
|
+
|
|
131
|
+
mteResourceSampleInstanceMaximum OBJECT-TYPE
|
|
132
|
+
SYNTAX Unsigned32
|
|
133
|
+
UNITS "instances"
|
|
134
|
+
MAX-ACCESS read-write
|
|
135
|
+
STATUS current
|
|
136
|
+
DESCRIPTION
|
|
137
|
+
"The maximum number of instance entries this system will
|
|
138
|
+
support for sampling.
|
|
139
|
+
|
|
140
|
+
These are the entries that maintain state, one for each
|
|
141
|
+
instance of each sampled object as selected by
|
|
142
|
+
mteTriggerValueID. Note that wildcarded objects result
|
|
143
|
+
in multiple instances of this state.
|
|
144
|
+
|
|
145
|
+
A value of 0 indicates no preset limit, that is, the limit
|
|
146
|
+
is dynamic based on system operation and resources.
|
|
147
|
+
|
|
148
|
+
Unless explicitly resource limited, a system's value for
|
|
149
|
+
this object SHOULD be 0.
|
|
150
|
+
|
|
151
|
+
Changing this value will not eliminate or inhibit existing
|
|
152
|
+
sample state but could prevent allocation of additional state
|
|
153
|
+
information."
|
|
154
|
+
::= { mteResource 2 }
|
|
155
|
+
|
|
156
|
+
mteResourceSampleInstances OBJECT-TYPE
|
|
157
|
+
SYNTAX Gauge32
|
|
158
|
+
UNITS "instances"
|
|
159
|
+
MAX-ACCESS read-only
|
|
160
|
+
STATUS current
|
|
161
|
+
DESCRIPTION
|
|
162
|
+
"The number of currently active instance entries as
|
|
163
|
+
defined for mteResourceSampleInstanceMaximum."
|
|
164
|
+
::= { mteResource 3 }
|
|
165
|
+
|
|
166
|
+
mteResourceSampleInstancesHigh OBJECT-TYPE
|
|
167
|
+
SYNTAX Gauge32
|
|
168
|
+
UNITS "instances"
|
|
169
|
+
MAX-ACCESS read-only
|
|
170
|
+
STATUS current
|
|
171
|
+
DESCRIPTION
|
|
172
|
+
"The highest value of mteResourceSampleInstances that has
|
|
173
|
+
occurred since initialization of the management system."
|
|
174
|
+
::= { mteResource 4 }
|
|
175
|
+
|
|
176
|
+
mteResourceSampleInstanceLacks OBJECT-TYPE
|
|
177
|
+
SYNTAX Counter32
|
|
178
|
+
UNITS "instances"
|
|
179
|
+
MAX-ACCESS read-only
|
|
180
|
+
STATUS current
|
|
181
|
+
DESCRIPTION
|
|
182
|
+
"The number of times this system could not take a new sample
|
|
183
|
+
because that allocation would have exceeded the limit set by
|
|
184
|
+
mteResourceSampleInstanceMaximum."
|
|
185
|
+
::= { mteResource 5 }
|
|
186
|
+
|
|
187
|
+
--
|
|
188
|
+
-- Trigger Section
|
|
189
|
+
--
|
|
190
|
+
|
|
191
|
+
-- Counters
|
|
192
|
+
|
|
193
|
+
mteTriggerFailures OBJECT-TYPE
|
|
194
|
+
SYNTAX Counter32
|
|
195
|
+
UNITS "failures"
|
|
196
|
+
MAX-ACCESS read-only
|
|
197
|
+
STATUS current
|
|
198
|
+
DESCRIPTION
|
|
199
|
+
"The number of times an attempt to check for a trigger
|
|
200
|
+
condition has failed. This counts individually for each
|
|
201
|
+
attempt in a group of targets or each attempt for a
|
|
202
|
+
|
|
203
|
+
wildcarded object."
|
|
204
|
+
::= { mteTrigger 1 }
|
|
205
|
+
|
|
206
|
+
--
|
|
207
|
+
-- Trigger Table
|
|
208
|
+
--
|
|
209
|
+
|
|
210
|
+
mteTriggerTable OBJECT-TYPE
|
|
211
|
+
SYNTAX SEQUENCE OF MteTriggerEntry
|
|
212
|
+
MAX-ACCESS not-accessible
|
|
213
|
+
STATUS current
|
|
214
|
+
DESCRIPTION
|
|
215
|
+
"A table of management event trigger information."
|
|
216
|
+
::= { mteTrigger 2 }
|
|
217
|
+
|
|
218
|
+
mteTriggerEntry OBJECT-TYPE
|
|
219
|
+
SYNTAX MteTriggerEntry
|
|
220
|
+
MAX-ACCESS not-accessible
|
|
221
|
+
STATUS current
|
|
222
|
+
DESCRIPTION
|
|
223
|
+
"Information about a single trigger. Applications create and
|
|
224
|
+
delete entries using mteTriggerEntryStatus."
|
|
225
|
+
INDEX { mteOwner, IMPLIED mteTriggerName }
|
|
226
|
+
::= { mteTriggerTable 1 }
|
|
227
|
+
|
|
228
|
+
MteTriggerEntry ::= SEQUENCE {
|
|
229
|
+
mteOwner SnmpAdminString,
|
|
230
|
+
mteTriggerName SnmpAdminString,
|
|
231
|
+
mteTriggerComment SnmpAdminString,
|
|
232
|
+
mteTriggerTest BITS,
|
|
233
|
+
mteTriggerSampleType INTEGER,
|
|
234
|
+
mteTriggerValueID OBJECT IDENTIFIER,
|
|
235
|
+
mteTriggerValueIDWildcard TruthValue,
|
|
236
|
+
mteTriggerTargetTag SnmpTagValue,
|
|
237
|
+
mteTriggerContextName SnmpAdminString,
|
|
238
|
+
mteTriggerContextNameWildcard TruthValue,
|
|
239
|
+
mteTriggerFrequency Unsigned32,
|
|
240
|
+
mteTriggerObjectsOwner SnmpAdminString,
|
|
241
|
+
mteTriggerObjects SnmpAdminString,
|
|
242
|
+
mteTriggerEnabled TruthValue,
|
|
243
|
+
mteTriggerEntryStatus RowStatus
|
|
244
|
+
}
|
|
245
|
+
|
|
246
|
+
mteOwner OBJECT-TYPE
|
|
247
|
+
SYNTAX SnmpAdminString (SIZE(0..32))
|
|
248
|
+
MAX-ACCESS not-accessible
|
|
249
|
+
STATUS current
|
|
250
|
+
DESCRIPTION
|
|
251
|
+
"The owner of this entry. The exact semantics of this
|
|
252
|
+
string are subject to the security policy defined by the
|
|
253
|
+
security administrator."
|
|
254
|
+
::= { mteTriggerEntry 1 }
|
|
255
|
+
|
|
256
|
+
mteTriggerName OBJECT-TYPE
|
|
257
|
+
SYNTAX SnmpAdminString (SIZE (1..32))
|
|
258
|
+
MAX-ACCESS not-accessible
|
|
259
|
+
STATUS current
|
|
260
|
+
DESCRIPTION
|
|
261
|
+
"A locally-unique, administratively assigned name for the
|
|
262
|
+
trigger within the scope of mteOwner."
|
|
263
|
+
::= { mteTriggerEntry 2 }
|
|
264
|
+
|
|
265
|
+
mteTriggerComment OBJECT-TYPE
|
|
266
|
+
SYNTAX SnmpAdminString
|
|
267
|
+
MAX-ACCESS read-create
|
|
268
|
+
STATUS current
|
|
269
|
+
DESCRIPTION
|
|
270
|
+
"A description of the trigger's function and use."
|
|
271
|
+
DEFVAL { ''H }
|
|
272
|
+
::= { mteTriggerEntry 3 }
|
|
273
|
+
|
|
274
|
+
mteTriggerTest OBJECT-TYPE
|
|
275
|
+
SYNTAX BITS { existence(0), boolean(1), threshold(2) }
|
|
276
|
+
MAX-ACCESS read-create
|
|
277
|
+
STATUS current
|
|
278
|
+
DESCRIPTION
|
|
279
|
+
"The type of trigger test to perform. For 'boolean' and
|
|
280
|
+
'threshold' tests, the object at mteTriggerValueID MUST
|
|
281
|
+
evaluate to an integer, that is, anything that ends up encoded
|
|
282
|
+
for transmission (that is, in BER, not ASN.1) as an integer.
|
|
283
|
+
|
|
284
|
+
For 'existence', the specific test is as selected by
|
|
285
|
+
mteTriggerExistenceTest. When an object appears, vanishes
|
|
286
|
+
or changes value, the trigger fires. If the object's
|
|
287
|
+
appearance caused the trigger firing, the object MUST
|
|
288
|
+
vanish before the trigger can be fired again for it, and
|
|
289
|
+
vice versa. If the trigger fired due to a change in the
|
|
290
|
+
object's value, it will be fired again on every successive
|
|
291
|
+
value change for that object.
|
|
292
|
+
|
|
293
|
+
For 'boolean', the specific test is as selected by
|
|
294
|
+
mteTriggerBooleanTest. If the test result is true the trigger
|
|
295
|
+
fires. The trigger will not fire again until the value has
|
|
296
|
+
become false and come back to true.
|
|
297
|
+
|
|
298
|
+
For 'threshold' the test works as described below for
|
|
299
|
+
|
|
300
|
+
mteTriggerThresholdStartup, mteTriggerThresholdRising, and
|
|
301
|
+
mteTriggerThresholdFalling.
|
|
302
|
+
|
|
303
|
+
Note that combining 'boolean' and 'threshold' tests on the
|
|
304
|
+
same object may be somewhat redundant."
|
|
305
|
+
DEFVAL { { boolean } }
|
|
306
|
+
::= { mteTriggerEntry 4 }
|
|
307
|
+
|
|
308
|
+
mteTriggerSampleType OBJECT-TYPE
|
|
309
|
+
SYNTAX INTEGER { absoluteValue(1), deltaValue(2) }
|
|
310
|
+
MAX-ACCESS read-create
|
|
311
|
+
STATUS current
|
|
312
|
+
DESCRIPTION
|
|
313
|
+
"The type of sampling to perform.
|
|
314
|
+
|
|
315
|
+
An 'absoluteValue' sample requires only a single sample to be
|
|
316
|
+
meaningful, and is exactly the value of the object at
|
|
317
|
+
mteTriggerValueID at the sample time.
|
|
318
|
+
|
|
319
|
+
A 'deltaValue' requires two samples to be meaningful and is
|
|
320
|
+
thus not available for testing until the second and subsequent
|
|
321
|
+
samples after the object at mteTriggerValueID is first found
|
|
322
|
+
to exist. It is the difference between the two samples. For
|
|
323
|
+
unsigned values it is always positive, based on unsigned
|
|
324
|
+
arithmetic. For signed values it can be positive or negative.
|
|
325
|
+
|
|
326
|
+
For SNMP counters to be meaningful they should be sampled as a
|
|
327
|
+
'deltaValue'.
|
|
328
|
+
|
|
329
|
+
For 'deltaValue' mteTriggerDeltaTable contains further
|
|
330
|
+
parameters.
|
|
331
|
+
|
|
332
|
+
If only 'existence' is set in mteTriggerTest this object has
|
|
333
|
+
no meaning."
|
|
334
|
+
DEFVAL { absoluteValue }
|
|
335
|
+
::= { mteTriggerEntry 5 }
|
|
336
|
+
|
|
337
|
+
mteTriggerValueID OBJECT-TYPE
|
|
338
|
+
SYNTAX OBJECT IDENTIFIER
|
|
339
|
+
MAX-ACCESS read-create
|
|
340
|
+
STATUS current
|
|
341
|
+
DESCRIPTION
|
|
342
|
+
"The object identifier of the MIB object to sample to see
|
|
343
|
+
if the trigger should fire.
|
|
344
|
+
|
|
345
|
+
This may be wildcarded by truncating all or part of the
|
|
346
|
+
instance portion, in which case the value is obtained
|
|
347
|
+
as if with a GetNext function, checking multiple values
|
|
348
|
+
|
|
349
|
+
if they exist. If such wildcarding is applied,
|
|
350
|
+
mteTriggerValueIDWildcard must be 'true' and if not it must
|
|
351
|
+
be 'false'.
|
|
352
|
+
|
|
353
|
+
Bad object identifiers or a mismatch between truncating the
|
|
354
|
+
identifier and the value of mteTriggerValueIDWildcard result
|
|
355
|
+
in operation as one would expect when providing the wrong
|
|
356
|
+
identifier to a Get or GetNext operation. The Get will fail
|
|
357
|
+
or get the wrong object. The GetNext will indeed get whatever
|
|
358
|
+
is next, proceeding until it runs past the initial part of the
|
|
359
|
+
identifier and perhaps many unintended objects for confusing
|
|
360
|
+
results. If the value syntax of those objects is not usable,
|
|
361
|
+
that results in a 'badType' error that terminates the scan.
|
|
362
|
+
|
|
363
|
+
Each instance that fills the wildcard is independent of any
|
|
364
|
+
additional instances, that is, wildcarded objects operate
|
|
365
|
+
as if there were a separate table entry for each instance
|
|
366
|
+
that fills the wildcard without having to actually predict
|
|
367
|
+
all possible instances ahead of time."
|
|
368
|
+
DEFVAL { zeroDotZero }
|
|
369
|
+
::= { mteTriggerEntry 6 }
|
|
370
|
+
|
|
371
|
+
mteTriggerValueIDWildcard OBJECT-TYPE
|
|
372
|
+
SYNTAX TruthValue
|
|
373
|
+
MAX-ACCESS read-create
|
|
374
|
+
STATUS current
|
|
375
|
+
DESCRIPTION
|
|
376
|
+
"Control for whether mteTriggerValueID is to be treated as
|
|
377
|
+
fully-specified or wildcarded, with 'true' indicating wildcard."
|
|
378
|
+
DEFVAL { false }
|
|
379
|
+
::= { mteTriggerEntry 7 }
|
|
380
|
+
|
|
381
|
+
mteTriggerTargetTag OBJECT-TYPE
|
|
382
|
+
SYNTAX SnmpTagValue
|
|
383
|
+
MAX-ACCESS read-create
|
|
384
|
+
STATUS current
|
|
385
|
+
DESCRIPTION
|
|
386
|
+
"The tag for the target(s) from which to obtain the condition
|
|
387
|
+
for a trigger check.
|
|
388
|
+
|
|
389
|
+
A length of 0 indicates the local system. In this case,
|
|
390
|
+
access to the objects indicated by mteTriggerValueID is under
|
|
391
|
+
the security credentials of the requester that set
|
|
392
|
+
mteTriggerEntryStatus to 'active'. Those credentials are the
|
|
393
|
+
input parameters for isAccessAllowed from the Architecture for
|
|
394
|
+
Describing SNMP Management Frameworks.
|
|
395
|
+
|
|
396
|
+
Otherwise access rights are checked according to the security
|
|
397
|
+
|
|
398
|
+
parameters resulting from the tag."
|
|
399
|
+
DEFVAL { ''H }
|
|
400
|
+
::= { mteTriggerEntry 8 }
|
|
401
|
+
|
|
402
|
+
mteTriggerContextName OBJECT-TYPE
|
|
403
|
+
SYNTAX SnmpAdminString
|
|
404
|
+
MAX-ACCESS read-create
|
|
405
|
+
STATUS current
|
|
406
|
+
DESCRIPTION
|
|
407
|
+
"The management context from which to obtain mteTriggerValueID.
|
|
408
|
+
|
|
409
|
+
This may be wildcarded by leaving characters off the end. For
|
|
410
|
+
example use 'Repeater' to wildcard to 'Repeater1',
|
|
411
|
+
'Repeater2', 'Repeater-999.87b', and so on. To indicate such
|
|
412
|
+
wildcarding is intended, mteTriggerContextNameWildcard must
|
|
413
|
+
be 'true'.
|
|
414
|
+
|
|
415
|
+
Each instance that fills the wildcard is independent of any
|
|
416
|
+
additional instances, that is, wildcarded objects operate
|
|
417
|
+
as if there were a separate table entry for each instance
|
|
418
|
+
that fills the wildcard without having to actually predict
|
|
419
|
+
all possible instances ahead of time.
|
|
420
|
+
|
|
421
|
+
Operation of this feature assumes that the local system has a
|
|
422
|
+
list of available contexts against which to apply the
|
|
423
|
+
wildcard. If the objects are being read from the local
|
|
424
|
+
system, this is clearly the system's own list of contexts.
|
|
425
|
+
For a remote system a local version of such a list is not
|
|
426
|
+
defined by any current standard and may not be available, so
|
|
427
|
+
this function MAY not be supported."
|
|
428
|
+
DEFVAL { ''H }
|
|
429
|
+
::= { mteTriggerEntry 9 }
|
|
430
|
+
|
|
431
|
+
mteTriggerContextNameWildcard OBJECT-TYPE
|
|
432
|
+
SYNTAX TruthValue
|
|
433
|
+
MAX-ACCESS read-create
|
|
434
|
+
STATUS current
|
|
435
|
+
DESCRIPTION
|
|
436
|
+
"Control for whether mteTriggerContextName is to be treated as
|
|
437
|
+
fully-specified or wildcarded, with 'true' indicating wildcard."
|
|
438
|
+
DEFVAL { false }
|
|
439
|
+
::= { mteTriggerEntry 10 }
|
|
440
|
+
|
|
441
|
+
mteTriggerFrequency OBJECT-TYPE
|
|
442
|
+
SYNTAX Unsigned32
|
|
443
|
+
UNITS "seconds"
|
|
444
|
+
MAX-ACCESS read-create
|
|
445
|
+
STATUS current
|
|
446
|
+
DESCRIPTION
|
|
447
|
+
"The number of seconds to wait between trigger samples. To
|
|
448
|
+
encourage consistency in sampling, the interval is measured
|
|
449
|
+
from the beginning of one check to the beginning of the next
|
|
450
|
+
and the timer is restarted immediately when it expires, not
|
|
451
|
+
when the check completes.
|
|
452
|
+
|
|
453
|
+
If the next sample begins before the previous one completed the
|
|
454
|
+
system may either attempt to make the check or treat this as an
|
|
455
|
+
error condition with the error 'sampleOverrun'.
|
|
456
|
+
|
|
457
|
+
A frequency of 0 indicates instantaneous recognition of the
|
|
458
|
+
condition. This is not possible in many cases, but may
|
|
459
|
+
be supported in cases where it makes sense and the system is
|
|
460
|
+
able to do so. This feature allows the MIB to be used in
|
|
461
|
+
implementations where such interrupt-driven behavior is
|
|
462
|
+
possible and is not likely to be supported for all MIB objects
|
|
463
|
+
even then since such sampling generally has to be tightly
|
|
464
|
+
integrated into low-level code.
|
|
465
|
+
|
|
466
|
+
Systems that can support this SHOULD document those cases
|
|
467
|
+
where it can be used. In cases where it can not, setting this
|
|
468
|
+
object to 0 should be disallowed."
|
|
469
|
+
DEFVAL { 600 }
|
|
470
|
+
::= { mteTriggerEntry 11 }
|
|
471
|
+
|
|
472
|
+
mteTriggerObjectsOwner OBJECT-TYPE
|
|
473
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
474
|
+
MAX-ACCESS read-create
|
|
475
|
+
STATUS current
|
|
476
|
+
DESCRIPTION
|
|
477
|
+
"To go with mteTriggerObjects, the mteOwner of a group of
|
|
478
|
+
objects from mteObjectsTable."
|
|
479
|
+
DEFVAL { ''H }
|
|
480
|
+
::= { mteTriggerEntry 12 }
|
|
481
|
+
|
|
482
|
+
mteTriggerObjects OBJECT-TYPE
|
|
483
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
484
|
+
MAX-ACCESS read-create
|
|
485
|
+
STATUS current
|
|
486
|
+
DESCRIPTION
|
|
487
|
+
"The mteObjectsName of a group of objects from
|
|
488
|
+
mteObjectsTable. These objects are to be added to any
|
|
489
|
+
Notification resulting from the firing of this trigger.
|
|
490
|
+
|
|
491
|
+
A list of objects may also be added based on the event or on
|
|
492
|
+
the value of mteTriggerTest.
|
|
493
|
+
|
|
494
|
+
A length of 0 indicates no additional objects."
|
|
495
|
+
DEFVAL { ''H }
|
|
496
|
+
::= { mteTriggerEntry 13 }
|
|
497
|
+
|
|
498
|
+
mteTriggerEnabled OBJECT-TYPE
|
|
499
|
+
SYNTAX TruthValue
|
|
500
|
+
MAX-ACCESS read-create
|
|
501
|
+
STATUS current
|
|
502
|
+
DESCRIPTION
|
|
503
|
+
"A control to allow a trigger to be configured but not used.
|
|
504
|
+
When the value is 'false' the trigger is not sampled."
|
|
505
|
+
DEFVAL { false }
|
|
506
|
+
::= { mteTriggerEntry 14 }
|
|
507
|
+
|
|
508
|
+
mteTriggerEntryStatus OBJECT-TYPE
|
|
509
|
+
SYNTAX RowStatus
|
|
510
|
+
MAX-ACCESS read-create
|
|
511
|
+
STATUS current
|
|
512
|
+
DESCRIPTION
|
|
513
|
+
"The control that allows creation and deletion of entries.
|
|
514
|
+
Once made active an entry may not be modified except to
|
|
515
|
+
delete it."
|
|
516
|
+
::= { mteTriggerEntry 15 }
|
|
517
|
+
|
|
518
|
+
--
|
|
519
|
+
-- Trigger Delta Table
|
|
520
|
+
--
|
|
521
|
+
|
|
522
|
+
mteTriggerDeltaTable OBJECT-TYPE
|
|
523
|
+
SYNTAX SEQUENCE OF MteTriggerDeltaEntry
|
|
524
|
+
MAX-ACCESS not-accessible
|
|
525
|
+
STATUS current
|
|
526
|
+
DESCRIPTION
|
|
527
|
+
"A table of management event trigger information for delta
|
|
528
|
+
sampling."
|
|
529
|
+
::= { mteTrigger 3 }
|
|
530
|
+
|
|
531
|
+
mteTriggerDeltaEntry OBJECT-TYPE
|
|
532
|
+
SYNTAX MteTriggerDeltaEntry
|
|
533
|
+
MAX-ACCESS not-accessible
|
|
534
|
+
STATUS current
|
|
535
|
+
DESCRIPTION
|
|
536
|
+
"Information about a single trigger's delta sampling. Entries
|
|
537
|
+
automatically exist in this this table for each mteTriggerEntry
|
|
538
|
+
that has mteTriggerSampleType set to 'deltaValue'."
|
|
539
|
+
INDEX { mteOwner, IMPLIED mteTriggerName }
|
|
540
|
+
::= { mteTriggerDeltaTable 1 }
|
|
541
|
+
|
|
542
|
+
MteTriggerDeltaEntry ::= SEQUENCE {
|
|
543
|
+
mteTriggerDeltaDiscontinuityID OBJECT IDENTIFIER,
|
|
544
|
+
mteTriggerDeltaDiscontinuityIDWildcard TruthValue,
|
|
545
|
+
mteTriggerDeltaDiscontinuityIDType INTEGER
|
|
546
|
+
}
|
|
547
|
+
|
|
548
|
+
sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 }
|
|
549
|
+
|
|
550
|
+
mteTriggerDeltaDiscontinuityID OBJECT-TYPE
|
|
551
|
+
SYNTAX OBJECT IDENTIFIER
|
|
552
|
+
MAX-ACCESS read-write
|
|
553
|
+
STATUS current
|
|
554
|
+
DESCRIPTION
|
|
555
|
+
"The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or
|
|
556
|
+
DateAndTime object that indicates a discontinuity in the value
|
|
557
|
+
at mteTriggerValueID.
|
|
558
|
+
|
|
559
|
+
The OID may be for a leaf object (e.g. sysUpTime.0) or may
|
|
560
|
+
be wildcarded to match mteTriggerValueID.
|
|
561
|
+
|
|
562
|
+
This object supports normal checking for a discontinuity in a
|
|
563
|
+
counter. Note that if this object does not point to sysUpTime
|
|
564
|
+
discontinuity checking MUST still check sysUpTime for an overall
|
|
565
|
+
discontinuity.
|
|
566
|
+
|
|
567
|
+
If the object identified is not accessible the sample attempt
|
|
568
|
+
is in error, with the error code as from an SNMP request.
|
|
569
|
+
|
|
570
|
+
Bad object identifiers or a mismatch between truncating the
|
|
571
|
+
identifier and the value of mteDeltaDiscontinuityIDWildcard
|
|
572
|
+
result in operation as one would expect when providing the
|
|
573
|
+
wrong identifier to a Get operation. The Get will fail or get
|
|
574
|
+
the wrong object. If the value syntax of those objects is not
|
|
575
|
+
usable, that results in an error that terminates the sample
|
|
576
|
+
with a 'badType' error code."
|
|
577
|
+
DEFVAL { sysUpTimeInstance }
|
|
578
|
+
::= { mteTriggerDeltaEntry 1 }
|
|
579
|
+
|
|
580
|
+
mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE
|
|
581
|
+
SYNTAX TruthValue
|
|
582
|
+
MAX-ACCESS read-write
|
|
583
|
+
STATUS current
|
|
584
|
+
DESCRIPTION
|
|
585
|
+
"Control for whether mteTriggerDeltaDiscontinuityID is to be
|
|
586
|
+
treated as fully-specified or wildcarded, with 'true'
|
|
587
|
+
indicating wildcard. Note that the value of this object will
|
|
588
|
+
be the same as that of the corresponding instance of
|
|
589
|
+
mteTriggerValueIDWildcard when the corresponding
|
|
590
|
+
|
|
591
|
+
mteTriggerSampleType is 'deltaValue'."
|
|
592
|
+
DEFVAL { false }
|
|
593
|
+
::= { mteTriggerDeltaEntry 2 }
|
|
594
|
+
|
|
595
|
+
mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE
|
|
596
|
+
SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) }
|
|
597
|
+
MAX-ACCESS read-write
|
|
598
|
+
STATUS current
|
|
599
|
+
DESCRIPTION
|
|
600
|
+
"The value 'timeTicks' indicates the
|
|
601
|
+
mteTriggerDeltaDiscontinuityID of this row is of syntax
|
|
602
|
+
TimeTicks. The value 'timeStamp' indicates syntax TimeStamp.
|
|
603
|
+
The value 'dateAndTime' indicates syntax DateAndTime."
|
|
604
|
+
DEFVAL { timeTicks }
|
|
605
|
+
::= { mteTriggerDeltaEntry 3 }
|
|
606
|
+
|
|
607
|
+
--
|
|
608
|
+
-- Trigger Existence Table
|
|
609
|
+
--
|
|
610
|
+
|
|
611
|
+
mteTriggerExistenceTable OBJECT-TYPE
|
|
612
|
+
SYNTAX SEQUENCE OF MteTriggerExistenceEntry
|
|
613
|
+
MAX-ACCESS not-accessible
|
|
614
|
+
STATUS current
|
|
615
|
+
DESCRIPTION
|
|
616
|
+
"A table of management event trigger information for existence
|
|
617
|
+
triggers."
|
|
618
|
+
::= { mteTrigger 4 }
|
|
619
|
+
|
|
620
|
+
mteTriggerExistenceEntry OBJECT-TYPE
|
|
621
|
+
SYNTAX MteTriggerExistenceEntry
|
|
622
|
+
MAX-ACCESS not-accessible
|
|
623
|
+
STATUS current
|
|
624
|
+
DESCRIPTION
|
|
625
|
+
"Information about a single existence trigger. Entries
|
|
626
|
+
automatically exist in this this table for each mteTriggerEntry
|
|
627
|
+
that has 'existence' set in mteTriggerTest."
|
|
628
|
+
INDEX { mteOwner, IMPLIED mteTriggerName }
|
|
629
|
+
::= { mteTriggerExistenceTable 1 }
|
|
630
|
+
|
|
631
|
+
MteTriggerExistenceEntry ::= SEQUENCE {
|
|
632
|
+
mteTriggerExistenceTest BITS,
|
|
633
|
+
mteTriggerExistenceStartup BITS,
|
|
634
|
+
mteTriggerExistenceObjectsOwner SnmpAdminString,
|
|
635
|
+
mteTriggerExistenceObjects SnmpAdminString,
|
|
636
|
+
mteTriggerExistenceEventOwner SnmpAdminString,
|
|
637
|
+
mteTriggerExistenceEvent SnmpAdminString
|
|
638
|
+
}
|
|
639
|
+
|
|
640
|
+
mteTriggerExistenceTest OBJECT-TYPE
|
|
641
|
+
SYNTAX BITS { present(0), absent(1), changed(2) }
|
|
642
|
+
MAX-ACCESS read-write
|
|
643
|
+
STATUS current
|
|
644
|
+
DESCRIPTION
|
|
645
|
+
"The type of existence test to perform. The trigger fires
|
|
646
|
+
when the object at mteTriggerValueID is seen to go from
|
|
647
|
+
present to absent, from absent to present, or to have it's
|
|
648
|
+
value changed, depending on which tests are selected:
|
|
649
|
+
|
|
650
|
+
present(0) - when this test is selected, the trigger fires
|
|
651
|
+
when the mteTriggerValueID object goes from absent to present.
|
|
652
|
+
|
|
653
|
+
absent(1) - when this test is selected, the trigger fires
|
|
654
|
+
when the mteTriggerValueID object goes from present to absent.
|
|
655
|
+
changed(2) - when this test is selected, the trigger fires
|
|
656
|
+
the mteTriggerValueID object value changes.
|
|
657
|
+
|
|
658
|
+
Once the trigger has fired for either presence or absence it
|
|
659
|
+
will not fire again for that state until the object has been
|
|
660
|
+
to the other state. "
|
|
661
|
+
DEFVAL { { present, absent } }
|
|
662
|
+
::= { mteTriggerExistenceEntry 1 }
|
|
663
|
+
|
|
664
|
+
mteTriggerExistenceStartup OBJECT-TYPE
|
|
665
|
+
SYNTAX BITS { present(0), absent(1) }
|
|
666
|
+
MAX-ACCESS read-write
|
|
667
|
+
STATUS current
|
|
668
|
+
DESCRIPTION
|
|
669
|
+
"Control for whether an event may be triggered when this entry
|
|
670
|
+
is first set to 'active' and the test specified by
|
|
671
|
+
mteTriggerExistenceTest is true. Setting an option causes
|
|
672
|
+
that trigger to fire when its test is true."
|
|
673
|
+
DEFVAL { { present, absent } }
|
|
674
|
+
::= { mteTriggerExistenceEntry 2 }
|
|
675
|
+
|
|
676
|
+
mteTriggerExistenceObjectsOwner OBJECT-TYPE
|
|
677
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
678
|
+
MAX-ACCESS read-write
|
|
679
|
+
STATUS current
|
|
680
|
+
DESCRIPTION
|
|
681
|
+
"To go with mteTriggerExistenceObjects, the mteOwner of a
|
|
682
|
+
group of objects from mteObjectsTable."
|
|
683
|
+
DEFVAL { ''H }
|
|
684
|
+
::= { mteTriggerExistenceEntry 3 }
|
|
685
|
+
|
|
686
|
+
mteTriggerExistenceObjects OBJECT-TYPE
|
|
687
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
688
|
+
MAX-ACCESS read-write
|
|
689
|
+
STATUS current
|
|
690
|
+
DESCRIPTION
|
|
691
|
+
"The mteObjectsName of a group of objects from
|
|
692
|
+
mteObjectsTable. These objects are to be added to any
|
|
693
|
+
Notification resulting from the firing of this trigger for
|
|
694
|
+
this test.
|
|
695
|
+
|
|
696
|
+
A list of objects may also be added based on the overall
|
|
697
|
+
trigger, the event or other settings in mteTriggerTest.
|
|
698
|
+
|
|
699
|
+
A length of 0 indicates no additional objects."
|
|
700
|
+
DEFVAL { ''H }
|
|
701
|
+
::= { mteTriggerExistenceEntry 4 }
|
|
702
|
+
|
|
703
|
+
mteTriggerExistenceEventOwner OBJECT-TYPE
|
|
704
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
705
|
+
MAX-ACCESS read-write
|
|
706
|
+
STATUS current
|
|
707
|
+
DESCRIPTION
|
|
708
|
+
"To go with mteTriggerExistenceEvent, the mteOwner of an event
|
|
709
|
+
entry from the mteEventTable."
|
|
710
|
+
DEFVAL { ''H }
|
|
711
|
+
::= { mteTriggerExistenceEntry 5 }
|
|
712
|
+
|
|
713
|
+
mteTriggerExistenceEvent OBJECT-TYPE
|
|
714
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
715
|
+
MAX-ACCESS read-write
|
|
716
|
+
STATUS current
|
|
717
|
+
DESCRIPTION
|
|
718
|
+
"The mteEventName of the event to invoke when mteTriggerType is
|
|
719
|
+
'existence' and this trigger fires. A length of 0 indicates no
|
|
720
|
+
event."
|
|
721
|
+
DEFVAL { ''H }
|
|
722
|
+
::= { mteTriggerExistenceEntry 6 }
|
|
723
|
+
|
|
724
|
+
--
|
|
725
|
+
-- Trigger Boolean Table
|
|
726
|
+
--
|
|
727
|
+
|
|
728
|
+
mteTriggerBooleanTable OBJECT-TYPE
|
|
729
|
+
SYNTAX SEQUENCE OF MteTriggerBooleanEntry
|
|
730
|
+
MAX-ACCESS not-accessible
|
|
731
|
+
STATUS current
|
|
732
|
+
DESCRIPTION
|
|
733
|
+
"A table of management event trigger information for boolean
|
|
734
|
+
triggers."
|
|
735
|
+
::= { mteTrigger 5 }
|
|
736
|
+
|
|
737
|
+
mteTriggerBooleanEntry OBJECT-TYPE
|
|
738
|
+
SYNTAX MteTriggerBooleanEntry
|
|
739
|
+
MAX-ACCESS not-accessible
|
|
740
|
+
STATUS current
|
|
741
|
+
DESCRIPTION
|
|
742
|
+
"Information about a single boolean trigger. Entries
|
|
743
|
+
automatically exist in this this table for each mteTriggerEntry
|
|
744
|
+
that has 'boolean' set in mteTriggerTest."
|
|
745
|
+
INDEX { mteOwner, IMPLIED mteTriggerName }
|
|
746
|
+
::= { mteTriggerBooleanTable 1 }
|
|
747
|
+
|
|
748
|
+
MteTriggerBooleanEntry ::= SEQUENCE {
|
|
749
|
+
mteTriggerBooleanComparison INTEGER,
|
|
750
|
+
mteTriggerBooleanValue Integer32,
|
|
751
|
+
mteTriggerBooleanStartup TruthValue,
|
|
752
|
+
mteTriggerBooleanObjectsOwner SnmpAdminString,
|
|
753
|
+
mteTriggerBooleanObjects SnmpAdminString,
|
|
754
|
+
mteTriggerBooleanEventOwner SnmpAdminString,
|
|
755
|
+
mteTriggerBooleanEvent SnmpAdminString
|
|
756
|
+
}
|
|
757
|
+
|
|
758
|
+
mteTriggerBooleanComparison OBJECT-TYPE
|
|
759
|
+
SYNTAX INTEGER { unequal(1), equal(2),
|
|
760
|
+
less(3), lessOrEqual(4),
|
|
761
|
+
greater(5), greaterOrEqual(6) }
|
|
762
|
+
MAX-ACCESS read-write
|
|
763
|
+
STATUS current
|
|
764
|
+
DESCRIPTION
|
|
765
|
+
"The type of boolean comparison to perform.
|
|
766
|
+
|
|
767
|
+
The value at mteTriggerValueID is compared to
|
|
768
|
+
mteTriggerBooleanValue, so for example if
|
|
769
|
+
mteTriggerBooleanComparison is 'less' the result would be true
|
|
770
|
+
if the value at mteTriggerValueID is less than the value of
|
|
771
|
+
mteTriggerBooleanValue."
|
|
772
|
+
DEFVAL { unequal }
|
|
773
|
+
::= { mteTriggerBooleanEntry 1 }
|
|
774
|
+
|
|
775
|
+
mteTriggerBooleanValue OBJECT-TYPE
|
|
776
|
+
SYNTAX Integer32
|
|
777
|
+
MAX-ACCESS read-write
|
|
778
|
+
STATUS current
|
|
779
|
+
DESCRIPTION
|
|
780
|
+
"The value to use for the test specified by
|
|
781
|
+
mteTriggerBooleanTest."
|
|
782
|
+
DEFVAL { 0 }
|
|
783
|
+
::= { mteTriggerBooleanEntry 2 }
|
|
784
|
+
|
|
785
|
+
mteTriggerBooleanStartup OBJECT-TYPE
|
|
786
|
+
SYNTAX TruthValue
|
|
787
|
+
MAX-ACCESS read-write
|
|
788
|
+
STATUS current
|
|
789
|
+
DESCRIPTION
|
|
790
|
+
"Control for whether an event may be triggered when this entry
|
|
791
|
+
is first set to 'active' or a new instance of the object at
|
|
792
|
+
mteTriggerValueID is found and the test specified by
|
|
793
|
+
mteTriggerBooleanComparison is true. In that case an event is
|
|
794
|
+
triggered if mteTriggerBooleanStartup is 'true'."
|
|
795
|
+
DEFVAL { true }
|
|
796
|
+
::= { mteTriggerBooleanEntry 3 }
|
|
797
|
+
|
|
798
|
+
mteTriggerBooleanObjectsOwner OBJECT-TYPE
|
|
799
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
800
|
+
MAX-ACCESS read-write
|
|
801
|
+
STATUS current
|
|
802
|
+
DESCRIPTION
|
|
803
|
+
"To go with mteTriggerBooleanObjects, the mteOwner of a group
|
|
804
|
+
of objects from mteObjectsTable."
|
|
805
|
+
DEFVAL { ''H }
|
|
806
|
+
::= { mteTriggerBooleanEntry 4 }
|
|
807
|
+
|
|
808
|
+
mteTriggerBooleanObjects OBJECT-TYPE
|
|
809
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
810
|
+
MAX-ACCESS read-write
|
|
811
|
+
STATUS current
|
|
812
|
+
DESCRIPTION
|
|
813
|
+
"The mteObjectsName of a group of objects from
|
|
814
|
+
mteObjectsTable. These objects are to be added to any
|
|
815
|
+
Notification resulting from the firing of this trigger for
|
|
816
|
+
this test.
|
|
817
|
+
|
|
818
|
+
A list of objects may also be added based on the overall
|
|
819
|
+
trigger, the event or other settings in mteTriggerTest.
|
|
820
|
+
|
|
821
|
+
A length of 0 indicates no additional objects."
|
|
822
|
+
DEFVAL { ''H }
|
|
823
|
+
::= { mteTriggerBooleanEntry 5 }
|
|
824
|
+
|
|
825
|
+
mteTriggerBooleanEventOwner OBJECT-TYPE
|
|
826
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
827
|
+
MAX-ACCESS read-write
|
|
828
|
+
STATUS current
|
|
829
|
+
DESCRIPTION
|
|
830
|
+
"To go with mteTriggerBooleanEvent, the mteOwner of an event
|
|
831
|
+
entry from mteEventTable."
|
|
832
|
+
DEFVAL { ''H }
|
|
833
|
+
::= { mteTriggerBooleanEntry 6 }
|
|
834
|
+
|
|
835
|
+
mteTriggerBooleanEvent OBJECT-TYPE
|
|
836
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
837
|
+
MAX-ACCESS read-write
|
|
838
|
+
STATUS current
|
|
839
|
+
DESCRIPTION
|
|
840
|
+
"The mteEventName of the event to invoke when mteTriggerType is
|
|
841
|
+
'boolean' and this trigger fires. A length of 0 indicates no
|
|
842
|
+
event."
|
|
843
|
+
DEFVAL { ''H }
|
|
844
|
+
::= { mteTriggerBooleanEntry 7 }
|
|
845
|
+
|
|
846
|
+
--
|
|
847
|
+
-- Trigger Threshold Table
|
|
848
|
+
--
|
|
849
|
+
|
|
850
|
+
mteTriggerThresholdTable OBJECT-TYPE
|
|
851
|
+
SYNTAX SEQUENCE OF MteTriggerThresholdEntry
|
|
852
|
+
MAX-ACCESS not-accessible
|
|
853
|
+
STATUS current
|
|
854
|
+
DESCRIPTION
|
|
855
|
+
"A table of management event trigger information for threshold
|
|
856
|
+
triggers."
|
|
857
|
+
::= { mteTrigger 6 }
|
|
858
|
+
|
|
859
|
+
mteTriggerThresholdEntry OBJECT-TYPE
|
|
860
|
+
SYNTAX MteTriggerThresholdEntry
|
|
861
|
+
MAX-ACCESS not-accessible
|
|
862
|
+
STATUS current
|
|
863
|
+
DESCRIPTION
|
|
864
|
+
"Information about a single threshold trigger. Entries
|
|
865
|
+
automatically exist in this table for each mteTriggerEntry
|
|
866
|
+
that has 'threshold' set in mteTriggerTest."
|
|
867
|
+
INDEX { mteOwner, IMPLIED mteTriggerName }
|
|
868
|
+
::= { mteTriggerThresholdTable 1 }
|
|
869
|
+
|
|
870
|
+
MteTriggerThresholdEntry ::= SEQUENCE {
|
|
871
|
+
mteTriggerThresholdStartup INTEGER,
|
|
872
|
+
mteTriggerThresholdRising Integer32,
|
|
873
|
+
mteTriggerThresholdFalling Integer32,
|
|
874
|
+
mteTriggerThresholdDeltaRising Integer32,
|
|
875
|
+
mteTriggerThresholdDeltaFalling Integer32,
|
|
876
|
+
mteTriggerThresholdObjectsOwner SnmpAdminString,
|
|
877
|
+
mteTriggerThresholdObjects SnmpAdminString,
|
|
878
|
+
mteTriggerThresholdRisingEventOwner SnmpAdminString,
|
|
879
|
+
mteTriggerThresholdRisingEvent SnmpAdminString,
|
|
880
|
+
mteTriggerThresholdFallingEventOwner SnmpAdminString,
|
|
881
|
+
mteTriggerThresholdFallingEvent SnmpAdminString,
|
|
882
|
+
mteTriggerThresholdDeltaRisingEventOwner SnmpAdminString,
|
|
883
|
+
mteTriggerThresholdDeltaRisingEvent SnmpAdminString,
|
|
884
|
+
mteTriggerThresholdDeltaFallingEventOwner SnmpAdminString,
|
|
885
|
+
mteTriggerThresholdDeltaFallingEvent SnmpAdminString
|
|
886
|
+
}
|
|
887
|
+
|
|
888
|
+
mteTriggerThresholdStartup OBJECT-TYPE
|
|
889
|
+
SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) }
|
|
890
|
+
MAX-ACCESS read-write
|
|
891
|
+
STATUS current
|
|
892
|
+
DESCRIPTION
|
|
893
|
+
"The event that may be triggered when this entry is first
|
|
894
|
+
set to 'active' and a new instance of the object at
|
|
895
|
+
mteTriggerValueID is found. If the first sample after this
|
|
896
|
+
instance becomes active is greater than or equal to
|
|
897
|
+
mteTriggerThresholdRising and mteTriggerThresholdStartup is
|
|
898
|
+
equal to 'rising' or 'risingOrFalling', then one
|
|
899
|
+
mteTriggerThresholdRisingEvent is triggered for that instance.
|
|
900
|
+
If the first sample after this entry becomes active is less
|
|
901
|
+
than or equal to mteTriggerThresholdFalling and
|
|
902
|
+
mteTriggerThresholdStartup is equal to 'falling' or
|
|
903
|
+
'risingOrFalling', then one mteTriggerThresholdRisingEvent is
|
|
904
|
+
triggered for that instance."
|
|
905
|
+
DEFVAL { risingOrFalling }
|
|
906
|
+
::= { mteTriggerThresholdEntry 1 }
|
|
907
|
+
|
|
908
|
+
mteTriggerThresholdRising OBJECT-TYPE
|
|
909
|
+
SYNTAX Integer32
|
|
910
|
+
MAX-ACCESS read-write
|
|
911
|
+
STATUS current
|
|
912
|
+
DESCRIPTION
|
|
913
|
+
"A threshold value to check against if mteTriggerType is
|
|
914
|
+
'threshold'.
|
|
915
|
+
|
|
916
|
+
When the current sampled value is greater than or equal to
|
|
917
|
+
this threshold, and the value at the last sampling interval
|
|
918
|
+
was less than this threshold, one
|
|
919
|
+
mteTriggerThresholdRisingEvent is triggered. That event is
|
|
920
|
+
also triggered if the first sample after this entry becomes
|
|
921
|
+
active is greater than or equal to this threshold and
|
|
922
|
+
mteTriggerThresholdStartup is equal to 'rising' or
|
|
923
|
+
'risingOrFalling'.
|
|
924
|
+
|
|
925
|
+
After a rising event is generated, another such event is not
|
|
926
|
+
triggered until the sampled value falls below this threshold
|
|
927
|
+
and reaches mteTriggerThresholdFalling."
|
|
928
|
+
DEFVAL { 0 }
|
|
929
|
+
::= { mteTriggerThresholdEntry 2 }
|
|
930
|
+
|
|
931
|
+
mteTriggerThresholdFalling OBJECT-TYPE
|
|
932
|
+
SYNTAX Integer32
|
|
933
|
+
MAX-ACCESS read-write
|
|
934
|
+
STATUS current
|
|
935
|
+
DESCRIPTION
|
|
936
|
+
"A threshold value to check against if mteTriggerType is
|
|
937
|
+
'threshold'.
|
|
938
|
+
|
|
939
|
+
When the current sampled value is less than or equal to this
|
|
940
|
+
threshold, and the value at the last sampling interval was
|
|
941
|
+
greater than this threshold, one
|
|
942
|
+
mteTriggerThresholdFallingEvent is triggered. That event is
|
|
943
|
+
also triggered if the first sample after this entry becomes
|
|
944
|
+
active is less than or equal to this threshold and
|
|
945
|
+
mteTriggerThresholdStartup is equal to 'falling' or
|
|
946
|
+
'risingOrFalling'.
|
|
947
|
+
|
|
948
|
+
After a falling event is generated, another such event is not
|
|
949
|
+
triggered until the sampled value rises above this threshold
|
|
950
|
+
and reaches mteTriggerThresholdRising."
|
|
951
|
+
DEFVAL { 0 }
|
|
952
|
+
::= { mteTriggerThresholdEntry 3 }
|
|
953
|
+
|
|
954
|
+
mteTriggerThresholdDeltaRising OBJECT-TYPE
|
|
955
|
+
SYNTAX Integer32
|
|
956
|
+
MAX-ACCESS read-write
|
|
957
|
+
STATUS current
|
|
958
|
+
DESCRIPTION
|
|
959
|
+
"A threshold value to check against if mteTriggerType is
|
|
960
|
+
'threshold'.
|
|
961
|
+
|
|
962
|
+
When the delta value (difference) between the current sampled
|
|
963
|
+
value (value(n)) and the previous sampled value (value(n-1))
|
|
964
|
+
is greater than or equal to this threshold,
|
|
965
|
+
and the delta value calculated at the last sampling interval
|
|
966
|
+
(i.e. value(n-1) - value(n-2)) was less than this threshold,
|
|
967
|
+
one mteTriggerThresholdDeltaRisingEvent is triggered. That event
|
|
968
|
+
is also triggered if the first delta value calculated after this
|
|
969
|
+
entry becomes active, i.e. value(2) - value(1), where value(1)
|
|
970
|
+
is the first sample taken of that instance, is greater than or
|
|
971
|
+
equal to this threshold.
|
|
972
|
+
|
|
973
|
+
After a rising event is generated, another such event is not
|
|
974
|
+
triggered until the delta value falls below this threshold and
|
|
975
|
+
reaches mteTriggerThresholdDeltaFalling."
|
|
976
|
+
DEFVAL { 0 }
|
|
977
|
+
::= { mteTriggerThresholdEntry 4 }
|
|
978
|
+
|
|
979
|
+
mteTriggerThresholdDeltaFalling OBJECT-TYPE
|
|
980
|
+
SYNTAX Integer32
|
|
981
|
+
MAX-ACCESS read-write
|
|
982
|
+
STATUS current
|
|
983
|
+
DESCRIPTION
|
|
984
|
+
"A threshold value to check against if mteTriggerType is
|
|
985
|
+
'threshold'.
|
|
986
|
+
|
|
987
|
+
When the delta value (difference) between the current sampled
|
|
988
|
+
value (value(n)) and the previous sampled value (value(n-1))
|
|
989
|
+
is less than or equal to this threshold,
|
|
990
|
+
and the delta value calculated at the last sampling interval
|
|
991
|
+
(i.e. value(n-1) - value(n-2)) was greater than this threshold,
|
|
992
|
+
one mteTriggerThresholdDeltaFallingEvent is triggered. That event
|
|
993
|
+
is also triggered if the first delta value calculated after this
|
|
994
|
+
entry becomes active, i.e. value(2) - value(1), where value(1)
|
|
995
|
+
is the first sample taken of that instance, is less than or
|
|
996
|
+
equal to this threshold.
|
|
997
|
+
|
|
998
|
+
After a falling event is generated, another such event is not
|
|
999
|
+
triggered until the delta value falls below this threshold and
|
|
1000
|
+
reaches mteTriggerThresholdDeltaRising."
|
|
1001
|
+
DEFVAL { 0 }
|
|
1002
|
+
::= { mteTriggerThresholdEntry 5 }
|
|
1003
|
+
|
|
1004
|
+
mteTriggerThresholdObjectsOwner OBJECT-TYPE
|
|
1005
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1006
|
+
MAX-ACCESS read-write
|
|
1007
|
+
STATUS current
|
|
1008
|
+
DESCRIPTION
|
|
1009
|
+
"To go with mteTriggerThresholdObjects, the mteOwner of a group
|
|
1010
|
+
of objects from mteObjectsTable."
|
|
1011
|
+
DEFVAL { ''H }
|
|
1012
|
+
::= { mteTriggerThresholdEntry 6 }
|
|
1013
|
+
|
|
1014
|
+
mteTriggerThresholdObjects OBJECT-TYPE
|
|
1015
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1016
|
+
MAX-ACCESS read-write
|
|
1017
|
+
STATUS current
|
|
1018
|
+
DESCRIPTION
|
|
1019
|
+
"The mteObjectsName of a group of objects from
|
|
1020
|
+
mteObjectsTable. These objects are to be added to any
|
|
1021
|
+
Notification resulting from the firing of this trigger for
|
|
1022
|
+
this test.
|
|
1023
|
+
|
|
1024
|
+
A list of objects may also be added based on the overall
|
|
1025
|
+
|
|
1026
|
+
trigger, the event or other settings in mteTriggerTest.
|
|
1027
|
+
|
|
1028
|
+
A length of 0 indicates no additional objects."
|
|
1029
|
+
DEFVAL { ''H }
|
|
1030
|
+
::= { mteTriggerThresholdEntry 7 }
|
|
1031
|
+
|
|
1032
|
+
mteTriggerThresholdRisingEventOwner OBJECT-TYPE
|
|
1033
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1034
|
+
MAX-ACCESS read-write
|
|
1035
|
+
STATUS current
|
|
1036
|
+
DESCRIPTION
|
|
1037
|
+
"To go with mteTriggerThresholdRisingEvent, the mteOwner of an
|
|
1038
|
+
event entry from mteEventTable."
|
|
1039
|
+
DEFVAL { ''H }
|
|
1040
|
+
::= { mteTriggerThresholdEntry 8 }
|
|
1041
|
+
|
|
1042
|
+
mteTriggerThresholdRisingEvent OBJECT-TYPE
|
|
1043
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1044
|
+
MAX-ACCESS read-write
|
|
1045
|
+
STATUS current
|
|
1046
|
+
DESCRIPTION
|
|
1047
|
+
"The mteEventName of the event to invoke when mteTriggerType is
|
|
1048
|
+
'threshold' and this trigger fires based on
|
|
1049
|
+
mteTriggerThresholdRising. A length of 0 indicates no event."
|
|
1050
|
+
DEFVAL { ''H }
|
|
1051
|
+
::= { mteTriggerThresholdEntry 9 }
|
|
1052
|
+
|
|
1053
|
+
mteTriggerThresholdFallingEventOwner OBJECT-TYPE
|
|
1054
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1055
|
+
MAX-ACCESS read-write
|
|
1056
|
+
STATUS current
|
|
1057
|
+
DESCRIPTION
|
|
1058
|
+
"To go with mteTriggerThresholdFallingEvent, the mteOwner of an
|
|
1059
|
+
event entry from mteEventTable."
|
|
1060
|
+
DEFVAL { ''H }
|
|
1061
|
+
::= { mteTriggerThresholdEntry 10 }
|
|
1062
|
+
|
|
1063
|
+
mteTriggerThresholdFallingEvent OBJECT-TYPE
|
|
1064
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1065
|
+
MAX-ACCESS read-write
|
|
1066
|
+
STATUS current
|
|
1067
|
+
DESCRIPTION
|
|
1068
|
+
"The mteEventName of the event to invoke when mteTriggerType is
|
|
1069
|
+
'threshold' and this trigger fires based on
|
|
1070
|
+
mteTriggerThresholdFalling. A length of 0 indicates no event."
|
|
1071
|
+
DEFVAL { ''H }
|
|
1072
|
+
::= { mteTriggerThresholdEntry 11 }
|
|
1073
|
+
|
|
1074
|
+
mteTriggerThresholdDeltaRisingEventOwner OBJECT-TYPE
|
|
1075
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1076
|
+
MAX-ACCESS read-write
|
|
1077
|
+
STATUS current
|
|
1078
|
+
DESCRIPTION
|
|
1079
|
+
"To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner
|
|
1080
|
+
of an event entry from mteEventTable."
|
|
1081
|
+
DEFVAL { ''H }
|
|
1082
|
+
::= { mteTriggerThresholdEntry 12 }
|
|
1083
|
+
|
|
1084
|
+
mteTriggerThresholdDeltaRisingEvent OBJECT-TYPE
|
|
1085
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1086
|
+
MAX-ACCESS read-write
|
|
1087
|
+
STATUS current
|
|
1088
|
+
DESCRIPTION
|
|
1089
|
+
"The mteEventName of the event to invoke when mteTriggerType is
|
|
1090
|
+
'threshold' and this trigger fires based on
|
|
1091
|
+
mteTriggerThresholdDeltaRising. A length of 0 indicates
|
|
1092
|
+
no event."
|
|
1093
|
+
DEFVAL { ''H }
|
|
1094
|
+
::= { mteTriggerThresholdEntry 13 }
|
|
1095
|
+
|
|
1096
|
+
mteTriggerThresholdDeltaFallingEventOwner OBJECT-TYPE
|
|
1097
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1098
|
+
MAX-ACCESS read-write
|
|
1099
|
+
STATUS current
|
|
1100
|
+
DESCRIPTION
|
|
1101
|
+
"To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner
|
|
1102
|
+
of an event entry from mteEventTable."
|
|
1103
|
+
DEFVAL { ''H }
|
|
1104
|
+
::= { mteTriggerThresholdEntry 14 }
|
|
1105
|
+
|
|
1106
|
+
mteTriggerThresholdDeltaFallingEvent OBJECT-TYPE
|
|
1107
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1108
|
+
MAX-ACCESS read-write
|
|
1109
|
+
STATUS current
|
|
1110
|
+
DESCRIPTION
|
|
1111
|
+
"The mteEventName of the event to invoke when mteTriggerType is
|
|
1112
|
+
'threshold' and this trigger fires based on
|
|
1113
|
+
mteTriggerThresholdDeltaFalling. A length of 0 indicates
|
|
1114
|
+
no event."
|
|
1115
|
+
DEFVAL { ''H }
|
|
1116
|
+
::= { mteTriggerThresholdEntry 15 }
|
|
1117
|
+
|
|
1118
|
+
--
|
|
1119
|
+
-- Objects Table
|
|
1120
|
+
--
|
|
1121
|
+
|
|
1122
|
+
mteObjectsTable OBJECT-TYPE
|
|
1123
|
+
SYNTAX SEQUENCE OF MteObjectsEntry
|
|
1124
|
+
MAX-ACCESS not-accessible
|
|
1125
|
+
STATUS current
|
|
1126
|
+
DESCRIPTION
|
|
1127
|
+
"A table of objects that can be added to notifications based
|
|
1128
|
+
on the trigger, trigger test, or event, as pointed to by
|
|
1129
|
+
entries in those tables."
|
|
1130
|
+
::= { mteObjects 1 }
|
|
1131
|
+
|
|
1132
|
+
mteObjectsEntry OBJECT-TYPE
|
|
1133
|
+
SYNTAX MteObjectsEntry
|
|
1134
|
+
MAX-ACCESS not-accessible
|
|
1135
|
+
STATUS current
|
|
1136
|
+
DESCRIPTION
|
|
1137
|
+
"A group of objects. Applications create and delete entries
|
|
1138
|
+
using mteObjectsEntryStatus.
|
|
1139
|
+
|
|
1140
|
+
When adding objects to a notification they are added in the
|
|
1141
|
+
lexical order of their index in this table. Those associated
|
|
1142
|
+
with a trigger come first, then trigger test, then event."
|
|
1143
|
+
INDEX { mteOwner, mteObjectsName, mteObjectsIndex }
|
|
1144
|
+
::= { mteObjectsTable 1 }
|
|
1145
|
+
|
|
1146
|
+
MteObjectsEntry ::= SEQUENCE {
|
|
1147
|
+
mteObjectsName SnmpAdminString,
|
|
1148
|
+
mteObjectsIndex Unsigned32,
|
|
1149
|
+
mteObjectsID OBJECT IDENTIFIER,
|
|
1150
|
+
mteObjectsIDWildcard TruthValue,
|
|
1151
|
+
mteObjectsEntryStatus RowStatus
|
|
1152
|
+
}
|
|
1153
|
+
|
|
1154
|
+
mteObjectsName OBJECT-TYPE
|
|
1155
|
+
SYNTAX SnmpAdminString (SIZE (1..32))
|
|
1156
|
+
MAX-ACCESS not-accessible
|
|
1157
|
+
STATUS current
|
|
1158
|
+
DESCRIPTION
|
|
1159
|
+
"A locally-unique, administratively assigned name for a group
|
|
1160
|
+
of objects."
|
|
1161
|
+
::= { mteObjectsEntry 1 }
|
|
1162
|
+
|
|
1163
|
+
mteObjectsIndex OBJECT-TYPE
|
|
1164
|
+
SYNTAX Unsigned32 (1..4294967295)
|
|
1165
|
+
MAX-ACCESS not-accessible
|
|
1166
|
+
STATUS current
|
|
1167
|
+
DESCRIPTION
|
|
1168
|
+
"An arbitrary integer for the purpose of identifying
|
|
1169
|
+
individual objects within a mteObjectsName group.
|
|
1170
|
+
|
|
1171
|
+
Objects within a group are placed in the notification in the
|
|
1172
|
+
numerical order of this index.
|
|
1173
|
+
|
|
1174
|
+
Groups are placed in the notification in the order of the
|
|
1175
|
+
selections for overall trigger, trigger test, and event.
|
|
1176
|
+
Within trigger test they are in the same order as the
|
|
1177
|
+
numerical values of the bits defined for mteTriggerTest.
|
|
1178
|
+
|
|
1179
|
+
Bad object identifiers or a mismatch between truncating the
|
|
1180
|
+
identifier and the value of mteDeltaDiscontinuityIDWildcard
|
|
1181
|
+
result in operation as one would expect when providing the
|
|
1182
|
+
wrong identifier to a Get operation. The Get will fail or get
|
|
1183
|
+
the wrong object. If the object is not available it is omitted
|
|
1184
|
+
from the notification."
|
|
1185
|
+
::= { mteObjectsEntry 2 }
|
|
1186
|
+
|
|
1187
|
+
mteObjectsID OBJECT-TYPE
|
|
1188
|
+
SYNTAX OBJECT IDENTIFIER
|
|
1189
|
+
MAX-ACCESS read-create
|
|
1190
|
+
STATUS current
|
|
1191
|
+
DESCRIPTION
|
|
1192
|
+
"The object identifier of a MIB object to add to a
|
|
1193
|
+
Notification that results from the firing of a trigger.
|
|
1194
|
+
|
|
1195
|
+
This may be wildcarded by truncating all or part of the
|
|
1196
|
+
instance portion, in which case the instance portion of the
|
|
1197
|
+
OID for obtaining this object will be the same as that used
|
|
1198
|
+
in obtaining the mteTriggerValueID that fired. If such
|
|
1199
|
+
wildcarding is applied, mteObjectsIDWildcard must be
|
|
1200
|
+
'true' and if not it must be 'false'.
|
|
1201
|
+
|
|
1202
|
+
Each instance that fills the wildcard is independent of any
|
|
1203
|
+
additional instances, that is, wildcarded objects operate
|
|
1204
|
+
as if there were a separate table entry for each instance
|
|
1205
|
+
that fills the wildcard without having to actually predict
|
|
1206
|
+
all possible instances ahead of time."
|
|
1207
|
+
DEFVAL { zeroDotZero }
|
|
1208
|
+
::= { mteObjectsEntry 3 }
|
|
1209
|
+
|
|
1210
|
+
mteObjectsIDWildcard OBJECT-TYPE
|
|
1211
|
+
SYNTAX TruthValue
|
|
1212
|
+
MAX-ACCESS read-create
|
|
1213
|
+
STATUS current
|
|
1214
|
+
DESCRIPTION
|
|
1215
|
+
"Control for whether mteObjectsID is to be treated as
|
|
1216
|
+
fully-specified or wildcarded, with 'true' indicating wildcard."
|
|
1217
|
+
DEFVAL { false }
|
|
1218
|
+
::= { mteObjectsEntry 4 }
|
|
1219
|
+
|
|
1220
|
+
mteObjectsEntryStatus OBJECT-TYPE
|
|
1221
|
+
SYNTAX RowStatus
|
|
1222
|
+
MAX-ACCESS read-create
|
|
1223
|
+
STATUS current
|
|
1224
|
+
DESCRIPTION
|
|
1225
|
+
"The control that allows creation and deletion of entries.
|
|
1226
|
+
Once made active an entry MAY not be modified except to
|
|
1227
|
+
delete it."
|
|
1228
|
+
::= { mteObjectsEntry 5 }
|
|
1229
|
+
|
|
1230
|
+
--
|
|
1231
|
+
-- Event Section
|
|
1232
|
+
--
|
|
1233
|
+
|
|
1234
|
+
-- Counters
|
|
1235
|
+
|
|
1236
|
+
mteEventFailures OBJECT-TYPE
|
|
1237
|
+
SYNTAX Counter32
|
|
1238
|
+
MAX-ACCESS read-only
|
|
1239
|
+
STATUS current
|
|
1240
|
+
DESCRIPTION
|
|
1241
|
+
"The number of times an attempt to invoke an event
|
|
1242
|
+
has failed. This counts individually for each
|
|
1243
|
+
attempt in a group of targets or each attempt for a
|
|
1244
|
+
wildcarded trigger object."
|
|
1245
|
+
::= { mteEvent 1 }
|
|
1246
|
+
|
|
1247
|
+
--
|
|
1248
|
+
-- Event Table
|
|
1249
|
+
--
|
|
1250
|
+
|
|
1251
|
+
mteEventTable OBJECT-TYPE
|
|
1252
|
+
SYNTAX SEQUENCE OF MteEventEntry
|
|
1253
|
+
MAX-ACCESS not-accessible
|
|
1254
|
+
STATUS current
|
|
1255
|
+
DESCRIPTION
|
|
1256
|
+
"A table of management event action information."
|
|
1257
|
+
::= { mteEvent 2 }
|
|
1258
|
+
|
|
1259
|
+
mteEventEntry OBJECT-TYPE
|
|
1260
|
+
SYNTAX MteEventEntry
|
|
1261
|
+
MAX-ACCESS not-accessible
|
|
1262
|
+
STATUS current
|
|
1263
|
+
DESCRIPTION
|
|
1264
|
+
"Information about a single event. Applications create and
|
|
1265
|
+
delete entries using mteEventEntryStatus."
|
|
1266
|
+
INDEX { mteOwner, IMPLIED mteEventName }
|
|
1267
|
+
::= { mteEventTable 1 }
|
|
1268
|
+
|
|
1269
|
+
MteEventEntry ::= SEQUENCE {
|
|
1270
|
+
mteEventName SnmpAdminString,
|
|
1271
|
+
mteEventComment SnmpAdminString,
|
|
1272
|
+
mteEventActions BITS,
|
|
1273
|
+
mteEventEnabled TruthValue,
|
|
1274
|
+
mteEventEntryStatus RowStatus
|
|
1275
|
+
}
|
|
1276
|
+
|
|
1277
|
+
mteEventName OBJECT-TYPE
|
|
1278
|
+
SYNTAX SnmpAdminString (SIZE (1..32))
|
|
1279
|
+
MAX-ACCESS not-accessible
|
|
1280
|
+
STATUS current
|
|
1281
|
+
DESCRIPTION
|
|
1282
|
+
"A locally-unique, administratively assigned name for the
|
|
1283
|
+
event."
|
|
1284
|
+
::= { mteEventEntry 1 }
|
|
1285
|
+
|
|
1286
|
+
mteEventComment OBJECT-TYPE
|
|
1287
|
+
SYNTAX SnmpAdminString
|
|
1288
|
+
MAX-ACCESS read-create
|
|
1289
|
+
STATUS current
|
|
1290
|
+
DESCRIPTION
|
|
1291
|
+
"A description of the event's function and use."
|
|
1292
|
+
DEFVAL { ''H }
|
|
1293
|
+
::= { mteEventEntry 2 }
|
|
1294
|
+
|
|
1295
|
+
mteEventActions OBJECT-TYPE
|
|
1296
|
+
SYNTAX BITS { notification(0), set(1) }
|
|
1297
|
+
MAX-ACCESS read-create
|
|
1298
|
+
STATUS current
|
|
1299
|
+
DESCRIPTION
|
|
1300
|
+
"The actions to perform when this event occurs.
|
|
1301
|
+
|
|
1302
|
+
For 'notification', Traps and/or Informs are sent according
|
|
1303
|
+
to the configuration in the SNMP Notification MIB.
|
|
1304
|
+
|
|
1305
|
+
For 'set', an SNMP Set operation is performed according to
|
|
1306
|
+
control values in this entry."
|
|
1307
|
+
DEFVAL { {} } -- No bits set.
|
|
1308
|
+
::= { mteEventEntry 3 }
|
|
1309
|
+
|
|
1310
|
+
mteEventEnabled OBJECT-TYPE
|
|
1311
|
+
SYNTAX TruthValue
|
|
1312
|
+
MAX-ACCESS read-create
|
|
1313
|
+
STATUS current
|
|
1314
|
+
DESCRIPTION
|
|
1315
|
+
"A control to allow an event to be configured but not used.
|
|
1316
|
+
When the value is 'false' the event does not execute even if
|
|
1317
|
+
|
|
1318
|
+
triggered."
|
|
1319
|
+
DEFVAL { false }
|
|
1320
|
+
::= { mteEventEntry 4 }
|
|
1321
|
+
|
|
1322
|
+
mteEventEntryStatus OBJECT-TYPE
|
|
1323
|
+
SYNTAX RowStatus
|
|
1324
|
+
MAX-ACCESS read-create
|
|
1325
|
+
STATUS current
|
|
1326
|
+
DESCRIPTION
|
|
1327
|
+
"The control that allows creation and deletion of entries.
|
|
1328
|
+
Once made active an entry MAY not be modified except to
|
|
1329
|
+
delete it."
|
|
1330
|
+
::= { mteEventEntry 5 }
|
|
1331
|
+
|
|
1332
|
+
--
|
|
1333
|
+
-- Event Notification Table
|
|
1334
|
+
--
|
|
1335
|
+
|
|
1336
|
+
mteEventNotificationTable OBJECT-TYPE
|
|
1337
|
+
SYNTAX SEQUENCE OF MteEventNotificationEntry
|
|
1338
|
+
MAX-ACCESS not-accessible
|
|
1339
|
+
STATUS current
|
|
1340
|
+
DESCRIPTION
|
|
1341
|
+
"A table of information about notifications to be sent as a
|
|
1342
|
+
consequence of management events."
|
|
1343
|
+
::= { mteEvent 3 }
|
|
1344
|
+
|
|
1345
|
+
mteEventNotificationEntry OBJECT-TYPE
|
|
1346
|
+
SYNTAX MteEventNotificationEntry
|
|
1347
|
+
MAX-ACCESS not-accessible
|
|
1348
|
+
STATUS current
|
|
1349
|
+
DESCRIPTION
|
|
1350
|
+
"Information about a single event's notification. Entries
|
|
1351
|
+
automatically exist in this this table for each mteEventEntry
|
|
1352
|
+
that has 'notification' set in mteEventActions."
|
|
1353
|
+
INDEX { mteOwner, IMPLIED mteEventName }
|
|
1354
|
+
::= { mteEventNotificationTable 1 }
|
|
1355
|
+
|
|
1356
|
+
MteEventNotificationEntry ::= SEQUENCE {
|
|
1357
|
+
mteEventNotification OBJECT IDENTIFIER,
|
|
1358
|
+
mteEventNotificationObjectsOwner SnmpAdminString,
|
|
1359
|
+
mteEventNotificationObjects SnmpAdminString
|
|
1360
|
+
}
|
|
1361
|
+
|
|
1362
|
+
mteEventNotification OBJECT-TYPE
|
|
1363
|
+
SYNTAX OBJECT IDENTIFIER
|
|
1364
|
+
MAX-ACCESS read-write
|
|
1365
|
+
STATUS current
|
|
1366
|
+
DESCRIPTION
|
|
1367
|
+
"The object identifier from the NOTIFICATION-TYPE for the
|
|
1368
|
+
notification to use if metEventActions has 'notification' set."
|
|
1369
|
+
DEFVAL { zeroDotZero }
|
|
1370
|
+
::= { mteEventNotificationEntry 1 }
|
|
1371
|
+
|
|
1372
|
+
mteEventNotificationObjectsOwner OBJECT-TYPE
|
|
1373
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1374
|
+
MAX-ACCESS read-write
|
|
1375
|
+
STATUS current
|
|
1376
|
+
DESCRIPTION
|
|
1377
|
+
"To go with mteEventNotificationObjects, the mteOwner of a
|
|
1378
|
+
group of objects from mteObjectsTable."
|
|
1379
|
+
DEFVAL { ''H }
|
|
1380
|
+
::= { mteEventNotificationEntry 2 }
|
|
1381
|
+
|
|
1382
|
+
mteEventNotificationObjects OBJECT-TYPE
|
|
1383
|
+
SYNTAX SnmpAdminString (SIZE (0..32))
|
|
1384
|
+
MAX-ACCESS read-write
|
|
1385
|
+
STATUS current
|
|
1386
|
+
DESCRIPTION
|
|
1387
|
+
"The mteObjectsName of a group of objects from
|
|
1388
|
+
mteObjectsTable if mteEventActions has 'notification' set.
|
|
1389
|
+
These objects are to be added to any Notification generated by
|
|
1390
|
+
this event.
|
|
1391
|
+
|
|
1392
|
+
Objects may also be added based on the trigger that stimulated
|
|
1393
|
+
the event.
|
|
1394
|
+
|
|
1395
|
+
A length of 0 indicates no additional objects."
|
|
1396
|
+
DEFVAL { ''H }
|
|
1397
|
+
::= { mteEventNotificationEntry 3 }
|
|
1398
|
+
|
|
1399
|
+
--
|
|
1400
|
+
-- Event Set Table
|
|
1401
|
+
--
|
|
1402
|
+
|
|
1403
|
+
mteEventSetTable OBJECT-TYPE
|
|
1404
|
+
SYNTAX SEQUENCE OF MteEventSetEntry
|
|
1405
|
+
MAX-ACCESS not-accessible
|
|
1406
|
+
STATUS current
|
|
1407
|
+
DESCRIPTION
|
|
1408
|
+
"A table of management event action information."
|
|
1409
|
+
::= { mteEvent 4 }
|
|
1410
|
+
|
|
1411
|
+
mteEventSetEntry OBJECT-TYPE
|
|
1412
|
+
SYNTAX MteEventSetEntry
|
|
1413
|
+
MAX-ACCESS not-accessible
|
|
1414
|
+
STATUS current
|
|
1415
|
+
DESCRIPTION
|
|
1416
|
+
"Information about a single event's set option. Entries
|
|
1417
|
+
automatically exist in this this table for each mteEventEntry
|
|
1418
|
+
that has 'set' set in mteEventActions."
|
|
1419
|
+
INDEX { mteOwner, IMPLIED mteEventName }
|
|
1420
|
+
::= { mteEventSetTable 1 }
|
|
1421
|
+
|
|
1422
|
+
MteEventSetEntry ::= SEQUENCE {
|
|
1423
|
+
mteEventSetObject OBJECT IDENTIFIER,
|
|
1424
|
+
mteEventSetObjectWildcard TruthValue,
|
|
1425
|
+
mteEventSetValue Integer32,
|
|
1426
|
+
mteEventSetTargetTag SnmpTagValue,
|
|
1427
|
+
mteEventSetContextName SnmpAdminString,
|
|
1428
|
+
mteEventSetContextNameWildcard TruthValue
|
|
1429
|
+
}
|
|
1430
|
+
|
|
1431
|
+
mteEventSetObject OBJECT-TYPE
|
|
1432
|
+
SYNTAX OBJECT IDENTIFIER
|
|
1433
|
+
MAX-ACCESS read-write
|
|
1434
|
+
STATUS current
|
|
1435
|
+
DESCRIPTION
|
|
1436
|
+
"The object identifier from the MIB object to set if
|
|
1437
|
+
mteEventActions has 'set' set.
|
|
1438
|
+
|
|
1439
|
+
This object identifier may be wildcarded by leaving
|
|
1440
|
+
sub-identifiers off the end, in which case
|
|
1441
|
+
nteEventSetObjectWildCard must be 'true'.
|
|
1442
|
+
|
|
1443
|
+
If mteEventSetObject is wildcarded the instance used to set the
|
|
1444
|
+
object to which it points is the same as the instance from the
|
|
1445
|
+
value of mteTriggerValueID that triggered the event.
|
|
1446
|
+
|
|
1447
|
+
Each instance that fills the wildcard is independent of any
|
|
1448
|
+
additional instances, that is, wildcarded objects operate
|
|
1449
|
+
as if there were a separate table entry for each instance
|
|
1450
|
+
that fills the wildcard without having to actually predict
|
|
1451
|
+
all possible instances ahead of time.
|
|
1452
|
+
|
|
1453
|
+
Bad object identifiers or a mismatch between truncating the
|
|
1454
|
+
identifier and the value of mteSetObjectWildcard
|
|
1455
|
+
result in operation as one would expect when providing the
|
|
1456
|
+
wrong identifier to a Set operation. The Set will fail or set
|
|
1457
|
+
the wrong object. If the value syntax of the destination
|
|
1458
|
+
object is not correct, the Set fails with the normal SNMP
|
|
1459
|
+
error code."
|
|
1460
|
+
DEFVAL { zeroDotZero }
|
|
1461
|
+
::= { mteEventSetEntry 1 }
|
|
1462
|
+
|
|
1463
|
+
mteEventSetObjectWildcard OBJECT-TYPE
|
|
1464
|
+
SYNTAX TruthValue
|
|
1465
|
+
MAX-ACCESS read-write
|
|
1466
|
+
STATUS current
|
|
1467
|
+
DESCRIPTION
|
|
1468
|
+
"Control over whether mteEventSetObject is to be treated as
|
|
1469
|
+
fully-specified or wildcarded, with 'true' indicating wildcard
|
|
1470
|
+
if mteEventActions has 'set' set."
|
|
1471
|
+
DEFVAL { false }
|
|
1472
|
+
::= { mteEventSetEntry 2 }
|
|
1473
|
+
|
|
1474
|
+
mteEventSetValue OBJECT-TYPE
|
|
1475
|
+
SYNTAX Integer32
|
|
1476
|
+
MAX-ACCESS read-write
|
|
1477
|
+
STATUS current
|
|
1478
|
+
DESCRIPTION
|
|
1479
|
+
"The value to which to set the object at mteEventSetObject
|
|
1480
|
+
if mteEventActions has 'set' set."
|
|
1481
|
+
DEFVAL { 0 }
|
|
1482
|
+
::= { mteEventSetEntry 3 }
|
|
1483
|
+
|
|
1484
|
+
mteEventSetTargetTag OBJECT-TYPE
|
|
1485
|
+
SYNTAX SnmpTagValue
|
|
1486
|
+
MAX-ACCESS read-write
|
|
1487
|
+
STATUS current
|
|
1488
|
+
DESCRIPTION
|
|
1489
|
+
"The tag for the target(s) at which to set the object at
|
|
1490
|
+
mteEventSetObject to mteEventSetValue if mteEventActions
|
|
1491
|
+
has 'set' set.
|
|
1492
|
+
|
|
1493
|
+
Systems limited to self management MAY reject a non-zero
|
|
1494
|
+
length for the value of this object.
|
|
1495
|
+
|
|
1496
|
+
A length of 0 indicates the local system. In this case,
|
|
1497
|
+
access to the objects indicated by mteEventSetObject is under
|
|
1498
|
+
the security credentials of the requester that set
|
|
1499
|
+
mteTriggerEntryStatus to 'active'. Those credentials are the
|
|
1500
|
+
input parameters for isAccessAllowed from the Architecture for
|
|
1501
|
+
Describing SNMP Management Frameworks.
|
|
1502
|
+
|
|
1503
|
+
Otherwise access rights are checked according to the security
|
|
1504
|
+
parameters resulting from the tag."
|
|
1505
|
+
DEFVAL { ''H }
|
|
1506
|
+
::= { mteEventSetEntry 4 }
|
|
1507
|
+
|
|
1508
|
+
mteEventSetContextName OBJECT-TYPE
|
|
1509
|
+
SYNTAX SnmpAdminString
|
|
1510
|
+
MAX-ACCESS read-write
|
|
1511
|
+
STATUS current
|
|
1512
|
+
DESCRIPTION
|
|
1513
|
+
"The management context in which to set mteEventObjectID.
|
|
1514
|
+
if mteEventActions has 'set' set.
|
|
1515
|
+
|
|
1516
|
+
This may be wildcarded by leaving characters off the end. To
|
|
1517
|
+
indicate such wildcarding mteEventSetContextNameWildcard must
|
|
1518
|
+
be 'true'.
|
|
1519
|
+
|
|
1520
|
+
If this context name is wildcarded the value used to complete
|
|
1521
|
+
the wildcarding of mteTriggerContextName will be appended."
|
|
1522
|
+
DEFVAL { ''H }
|
|
1523
|
+
::= { mteEventSetEntry 5 }
|
|
1524
|
+
|
|
1525
|
+
mteEventSetContextNameWildcard OBJECT-TYPE
|
|
1526
|
+
SYNTAX TruthValue
|
|
1527
|
+
MAX-ACCESS read-write
|
|
1528
|
+
STATUS current
|
|
1529
|
+
DESCRIPTION
|
|
1530
|
+
"Control for whether mteEventSetContextName is to be treated as
|
|
1531
|
+
fully-specified or wildcarded, with 'true' indicating wildcard
|
|
1532
|
+
if mteEventActions has 'set' set."
|
|
1533
|
+
DEFVAL { false }
|
|
1534
|
+
::= { mteEventSetEntry 6 }
|
|
1535
|
+
|
|
1536
|
+
--
|
|
1537
|
+
-- Notifications
|
|
1538
|
+
--
|
|
1539
|
+
|
|
1540
|
+
dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::=
|
|
1541
|
+
{ dismanEventMIB 2 }
|
|
1542
|
+
dismanEventMIBNotifications OBJECT IDENTIFIER ::=
|
|
1543
|
+
{ dismanEventMIBNotificationPrefix 0 }
|
|
1544
|
+
dismanEventMIBNotificationObjects OBJECT IDENTIFIER
|
|
1545
|
+
::= { dismanEventMIBNotificationPrefix 1 }
|
|
1546
|
+
|
|
1547
|
+
--
|
|
1548
|
+
-- Notification Objects
|
|
1549
|
+
--
|
|
1550
|
+
|
|
1551
|
+
mteHotTrigger OBJECT-TYPE
|
|
1552
|
+
SYNTAX SnmpAdminString
|
|
1553
|
+
MAX-ACCESS accessible-for-notify
|
|
1554
|
+
STATUS current
|
|
1555
|
+
DESCRIPTION
|
|
1556
|
+
"The name of the trigger causing the notification."
|
|
1557
|
+
::= { dismanEventMIBNotificationObjects 1 }
|
|
1558
|
+
|
|
1559
|
+
mteHotTargetName OBJECT-TYPE
|
|
1560
|
+
SYNTAX SnmpAdminString
|
|
1561
|
+
MAX-ACCESS accessible-for-notify
|
|
1562
|
+
STATUS current
|
|
1563
|
+
DESCRIPTION
|
|
1564
|
+
"The SNMP Target MIB's snmpTargetAddrName related to the
|
|
1565
|
+
notification."
|
|
1566
|
+
::= { dismanEventMIBNotificationObjects 2 }
|
|
1567
|
+
|
|
1568
|
+
mteHotContextName OBJECT-TYPE
|
|
1569
|
+
SYNTAX SnmpAdminString
|
|
1570
|
+
MAX-ACCESS accessible-for-notify
|
|
1571
|
+
STATUS current
|
|
1572
|
+
DESCRIPTION
|
|
1573
|
+
"The context name related to the notification. This MUST be as
|
|
1574
|
+
fully-qualified as possible, including filling in wildcard
|
|
1575
|
+
information determined in processing."
|
|
1576
|
+
::= { dismanEventMIBNotificationObjects 3 }
|
|
1577
|
+
|
|
1578
|
+
mteHotOID OBJECT-TYPE
|
|
1579
|
+
SYNTAX OBJECT IDENTIFIER
|
|
1580
|
+
MAX-ACCESS accessible-for-notify
|
|
1581
|
+
STATUS current
|
|
1582
|
+
DESCRIPTION
|
|
1583
|
+
"The object identifier of the destination object related to the
|
|
1584
|
+
notification. This MUST be as fully-qualified as possible,
|
|
1585
|
+
including filling in wildcard information determined in
|
|
1586
|
+
processing.
|
|
1587
|
+
|
|
1588
|
+
For a trigger-related notification this is from
|
|
1589
|
+
mteTriggerValueID.
|
|
1590
|
+
|
|
1591
|
+
For a set failure this is from mteEventSetObject."
|
|
1592
|
+
::= { dismanEventMIBNotificationObjects 4 }
|
|
1593
|
+
|
|
1594
|
+
mteHotValue OBJECT-TYPE
|
|
1595
|
+
SYNTAX Integer32
|
|
1596
|
+
MAX-ACCESS accessible-for-notify
|
|
1597
|
+
STATUS current
|
|
1598
|
+
DESCRIPTION
|
|
1599
|
+
"The value of the object at mteTriggerValueID when a
|
|
1600
|
+
trigger fired."
|
|
1601
|
+
::= { dismanEventMIBNotificationObjects 5 }
|
|
1602
|
+
|
|
1603
|
+
mteFailedReason OBJECT-TYPE
|
|
1604
|
+
SYNTAX FailureReason
|
|
1605
|
+
MAX-ACCESS accessible-for-notify
|
|
1606
|
+
STATUS current
|
|
1607
|
+
DESCRIPTION
|
|
1608
|
+
"The reason for the failure of an attempt to check for a
|
|
1609
|
+
trigger condition or set an object in response to an event."
|
|
1610
|
+
::= { dismanEventMIBNotificationObjects 6 }
|
|
1611
|
+
|
|
1612
|
+
--
|
|
1613
|
+
-- Notifications
|
|
1614
|
+
--
|
|
1615
|
+
|
|
1616
|
+
mteTriggerFired NOTIFICATION-TYPE
|
|
1617
|
+
OBJECTS { mteHotTrigger,
|
|
1618
|
+
mteHotTargetName,
|
|
1619
|
+
mteHotContextName,
|
|
1620
|
+
mteHotOID,
|
|
1621
|
+
mteHotValue }
|
|
1622
|
+
STATUS current
|
|
1623
|
+
DESCRIPTION
|
|
1624
|
+
"Notification that the trigger indicated by the object
|
|
1625
|
+
instances has fired, for triggers with mteTriggerType
|
|
1626
|
+
'boolean' or 'existence'."
|
|
1627
|
+
::= { dismanEventMIBNotifications 1 }
|
|
1628
|
+
|
|
1629
|
+
mteTriggerRising NOTIFICATION-TYPE
|
|
1630
|
+
OBJECTS { mteHotTrigger,
|
|
1631
|
+
mteHotTargetName,
|
|
1632
|
+
mteHotContextName,
|
|
1633
|
+
mteHotOID,
|
|
1634
|
+
mteHotValue }
|
|
1635
|
+
STATUS current
|
|
1636
|
+
DESCRIPTION
|
|
1637
|
+
"Notification that the rising threshold was met for triggers
|
|
1638
|
+
with mteTriggerType 'threshold'."
|
|
1639
|
+
::= { dismanEventMIBNotifications 2 }
|
|
1640
|
+
|
|
1641
|
+
mteTriggerFalling NOTIFICATION-TYPE
|
|
1642
|
+
OBJECTS { mteHotTrigger,
|
|
1643
|
+
mteHotTargetName,
|
|
1644
|
+
mteHotContextName,
|
|
1645
|
+
mteHotOID,
|
|
1646
|
+
mteHotValue }
|
|
1647
|
+
STATUS current
|
|
1648
|
+
DESCRIPTION
|
|
1649
|
+
"Notification that the falling threshold was met for triggers
|
|
1650
|
+
with mteTriggerType 'threshold'."
|
|
1651
|
+
::= { dismanEventMIBNotifications 3 }
|
|
1652
|
+
|
|
1653
|
+
mteTriggerFailure NOTIFICATION-TYPE
|
|
1654
|
+
OBJECTS { mteHotTrigger,
|
|
1655
|
+
mteHotTargetName,
|
|
1656
|
+
mteHotContextName,
|
|
1657
|
+
mteHotOID,
|
|
1658
|
+
mteFailedReason }
|
|
1659
|
+
STATUS current
|
|
1660
|
+
DESCRIPTION
|
|
1661
|
+
"Notification that an attempt to check a trigger has failed.
|
|
1662
|
+
|
|
1663
|
+
The network manager must enable this notification only with
|
|
1664
|
+
a certain fear and trembling, as it can easily crowd out more
|
|
1665
|
+
important information. It should be used only to help diagnose
|
|
1666
|
+
a problem that has appeared in the error counters and can not
|
|
1667
|
+
be found otherwise."
|
|
1668
|
+
::= { dismanEventMIBNotifications 4 }
|
|
1669
|
+
|
|
1670
|
+
mteEventSetFailure NOTIFICATION-TYPE
|
|
1671
|
+
OBJECTS { mteHotTrigger,
|
|
1672
|
+
mteHotTargetName,
|
|
1673
|
+
mteHotContextName,
|
|
1674
|
+
mteHotOID,
|
|
1675
|
+
mteFailedReason }
|
|
1676
|
+
STATUS current
|
|
1677
|
+
DESCRIPTION
|
|
1678
|
+
"Notification that an attempt to do a set in response to an
|
|
1679
|
+
event has failed.
|
|
1680
|
+
|
|
1681
|
+
The network manager must enable this notification only with
|
|
1682
|
+
a certain fear and trembling, as it can easily crowd out more
|
|
1683
|
+
important information. It should be used only to help diagnose
|
|
1684
|
+
a problem that has appeared in the error counters and can not
|
|
1685
|
+
be found otherwise."
|
|
1686
|
+
::= { dismanEventMIBNotifications 5 }
|
|
1687
|
+
|
|
1688
|
+
--
|
|
1689
|
+
-- Conformance
|
|
1690
|
+
--
|
|
1691
|
+
|
|
1692
|
+
dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 }
|
|
1693
|
+
dismanEventMIBCompliances OBJECT IDENTIFIER ::=
|
|
1694
|
+
{ dismanEventMIBConformance 1 }
|
|
1695
|
+
dismanEventMIBGroups OBJECT IDENTIFIER ::=
|
|
1696
|
+
{ dismanEventMIBConformance 2 }
|
|
1697
|
+
|
|
1698
|
+
-- Compliance
|
|
1699
|
+
|
|
1700
|
+
dismanEventMIBCompliance MODULE-COMPLIANCE
|
|
1701
|
+
STATUS current
|
|
1702
|
+
DESCRIPTION
|
|
1703
|
+
"The compliance statement for entities which implement
|
|
1704
|
+
the Event MIB."
|
|
1705
|
+
MODULE -- this module
|
|
1706
|
+
MANDATORY-GROUPS {
|
|
1707
|
+
dismanEventResourceGroup,
|
|
1708
|
+
dismanEventTriggerGroup,
|
|
1709
|
+
dismanEventObjectsGroup,
|
|
1710
|
+
dismanEventEventGroup,
|
|
1711
|
+
dismanEventNotificationObjectGroup,
|
|
1712
|
+
dismanEventNotificationGroup
|
|
1713
|
+
}
|
|
1714
|
+
|
|
1715
|
+
OBJECT mteTriggerTargetTag
|
|
1716
|
+
MIN-ACCESS read-only
|
|
1717
|
+
DESCRIPTION
|
|
1718
|
+
"Write access is not required, thus limiting
|
|
1719
|
+
monitoring to the local system or pre-configured
|
|
1720
|
+
remote systems."
|
|
1721
|
+
|
|
1722
|
+
OBJECT mteEventSetTargetTag
|
|
1723
|
+
MIN-ACCESS read-only
|
|
1724
|
+
DESCRIPTION
|
|
1725
|
+
"Write access is not required, thus limiting
|
|
1726
|
+
setting to the local system or pre-configured
|
|
1727
|
+
remote systems."
|
|
1728
|
+
|
|
1729
|
+
OBJECT mteTriggerValueIDWildcard
|
|
1730
|
+
MIN-ACCESS read-only
|
|
1731
|
+
DESCRIPTION
|
|
1732
|
+
"Write access is not required, thus allowing
|
|
1733
|
+
the system not to implement wildcarding."
|
|
1734
|
+
|
|
1735
|
+
OBJECT mteTriggerContextNameWildcard
|
|
1736
|
+
MIN-ACCESS read-only
|
|
1737
|
+
DESCRIPTION
|
|
1738
|
+
"Write access is not required, thus allowing
|
|
1739
|
+
the system not to implement wildcarding."
|
|
1740
|
+
|
|
1741
|
+
OBJECT mteObjectsIDWildcard
|
|
1742
|
+
MIN-ACCESS read-only
|
|
1743
|
+
DESCRIPTION
|
|
1744
|
+
"Write access is not required, thus allowing
|
|
1745
|
+
the system not to implement wildcarding."
|
|
1746
|
+
|
|
1747
|
+
OBJECT mteEventSetContextNameWildcard
|
|
1748
|
+
MIN-ACCESS read-only
|
|
1749
|
+
DESCRIPTION
|
|
1750
|
+
"Write access is not required, thus allowing
|
|
1751
|
+
the system not to implement wildcarding."
|
|
1752
|
+
::= { dismanEventMIBCompliances 1 }
|
|
1753
|
+
|
|
1754
|
+
-- Units of Conformance
|
|
1755
|
+
|
|
1756
|
+
dismanEventResourceGroup OBJECT-GROUP
|
|
1757
|
+
OBJECTS {
|
|
1758
|
+
mteResourceSampleMinimum,
|
|
1759
|
+
mteResourceSampleInstanceMaximum,
|
|
1760
|
+
mteResourceSampleInstances,
|
|
1761
|
+
mteResourceSampleInstancesHigh,
|
|
1762
|
+
mteResourceSampleInstanceLacks
|
|
1763
|
+
}
|
|
1764
|
+
STATUS current
|
|
1765
|
+
DESCRIPTION
|
|
1766
|
+
"Event resource status and control objects."
|
|
1767
|
+
::= { dismanEventMIBGroups 1 }
|
|
1768
|
+
|
|
1769
|
+
dismanEventTriggerGroup OBJECT-GROUP
|
|
1770
|
+
OBJECTS {
|
|
1771
|
+
mteTriggerFailures,
|
|
1772
|
+
mteTriggerComment,
|
|
1773
|
+
mteTriggerTest,
|
|
1774
|
+
mteTriggerSampleType,
|
|
1775
|
+
mteTriggerValueID,
|
|
1776
|
+
mteTriggerValueIDWildcard,
|
|
1777
|
+
mteTriggerTargetTag,
|
|
1778
|
+
mteTriggerContextName,
|
|
1779
|
+
mteTriggerContextNameWildcard,
|
|
1780
|
+
mteTriggerFrequency,
|
|
1781
|
+
mteTriggerObjectsOwner,
|
|
1782
|
+
mteTriggerObjects,
|
|
1783
|
+
mteTriggerEnabled,
|
|
1784
|
+
mteTriggerEntryStatus,
|
|
1785
|
+
mteTriggerDeltaDiscontinuityID,
|
|
1786
|
+
mteTriggerDeltaDiscontinuityIDWildcard,
|
|
1787
|
+
mteTriggerDeltaDiscontinuityIDType,
|
|
1788
|
+
mteTriggerExistenceTest,
|
|
1789
|
+
mteTriggerExistenceStartup,
|
|
1790
|
+
mteTriggerExistenceObjectsOwner,
|
|
1791
|
+
mteTriggerExistenceObjects,
|
|
1792
|
+
mteTriggerExistenceEventOwner,
|
|
1793
|
+
mteTriggerExistenceEvent,
|
|
1794
|
+
mteTriggerBooleanComparison,
|
|
1795
|
+
mteTriggerBooleanValue,
|
|
1796
|
+
mteTriggerBooleanStartup,
|
|
1797
|
+
mteTriggerBooleanObjectsOwner,
|
|
1798
|
+
mteTriggerBooleanObjects,
|
|
1799
|
+
mteTriggerBooleanEventOwner,
|
|
1800
|
+
mteTriggerBooleanEvent,
|
|
1801
|
+
mteTriggerThresholdStartup,
|
|
1802
|
+
mteTriggerThresholdObjectsOwner,
|
|
1803
|
+
mteTriggerThresholdObjects,
|
|
1804
|
+
mteTriggerThresholdRising,
|
|
1805
|
+
mteTriggerThresholdFalling,
|
|
1806
|
+
mteTriggerThresholdDeltaRising,
|
|
1807
|
+
mteTriggerThresholdDeltaFalling,
|
|
1808
|
+
mteTriggerThresholdRisingEventOwner,
|
|
1809
|
+
mteTriggerThresholdRisingEvent,
|
|
1810
|
+
mteTriggerThresholdFallingEventOwner,
|
|
1811
|
+
mteTriggerThresholdFallingEvent,
|
|
1812
|
+
mteTriggerThresholdDeltaRisingEventOwner,
|
|
1813
|
+
mteTriggerThresholdDeltaRisingEvent,
|
|
1814
|
+
mteTriggerThresholdDeltaFallingEventOwner,
|
|
1815
|
+
mteTriggerThresholdDeltaFallingEvent
|
|
1816
|
+
}
|
|
1817
|
+
STATUS current
|
|
1818
|
+
DESCRIPTION
|
|
1819
|
+
"Event triggers."
|
|
1820
|
+
::= { dismanEventMIBGroups 2 }
|
|
1821
|
+
|
|
1822
|
+
dismanEventObjectsGroup OBJECT-GROUP
|
|
1823
|
+
OBJECTS {
|
|
1824
|
+
mteObjectsID,
|
|
1825
|
+
mteObjectsIDWildcard,
|
|
1826
|
+
mteObjectsEntryStatus
|
|
1827
|
+
}
|
|
1828
|
+
STATUS current
|
|
1829
|
+
DESCRIPTION
|
|
1830
|
+
"Supplemental objects."
|
|
1831
|
+
::= { dismanEventMIBGroups 3 }
|
|
1832
|
+
|
|
1833
|
+
dismanEventEventGroup OBJECT-GROUP
|
|
1834
|
+
OBJECTS {
|
|
1835
|
+
mteEventFailures,
|
|
1836
|
+
mteEventComment,
|
|
1837
|
+
mteEventActions,
|
|
1838
|
+
mteEventEnabled,
|
|
1839
|
+
mteEventEntryStatus,
|
|
1840
|
+
mteEventNotification,
|
|
1841
|
+
mteEventNotificationObjectsOwner,
|
|
1842
|
+
mteEventNotificationObjects,
|
|
1843
|
+
mteEventSetObject,
|
|
1844
|
+
mteEventSetObjectWildcard,
|
|
1845
|
+
mteEventSetValue,
|
|
1846
|
+
mteEventSetTargetTag,
|
|
1847
|
+
mteEventSetContextName,
|
|
1848
|
+
mteEventSetContextNameWildcard
|
|
1849
|
+
}
|
|
1850
|
+
STATUS current
|
|
1851
|
+
DESCRIPTION
|
|
1852
|
+
"Events."
|
|
1853
|
+
::= { dismanEventMIBGroups 4 }
|
|
1854
|
+
|
|
1855
|
+
dismanEventNotificationObjectGroup OBJECT-GROUP
|
|
1856
|
+
OBJECTS {
|
|
1857
|
+
mteHotTrigger,
|
|
1858
|
+
mteHotTargetName,
|
|
1859
|
+
mteHotContextName,
|
|
1860
|
+
mteHotOID,
|
|
1861
|
+
mteHotValue,
|
|
1862
|
+
mteFailedReason
|
|
1863
|
+
}
|
|
1864
|
+
STATUS current
|
|
1865
|
+
DESCRIPTION
|
|
1866
|
+
"Notification objects."
|
|
1867
|
+
::= { dismanEventMIBGroups 5 }
|
|
1868
|
+
|
|
1869
|
+
dismanEventNotificationGroup NOTIFICATION-GROUP
|
|
1870
|
+
NOTIFICATIONS {
|
|
1871
|
+
mteTriggerFired,
|
|
1872
|
+
mteTriggerRising,
|
|
1873
|
+
mteTriggerFalling,
|
|
1874
|
+
mteTriggerFailure,
|
|
1875
|
+
mteEventSetFailure
|
|
1876
|
+
}
|
|
1877
|
+
STATUS current
|
|
1878
|
+
DESCRIPTION
|
|
1879
|
+
"Notifications."
|
|
1880
|
+
::= { dismanEventMIBGroups 6 }
|
|
1881
|
+
|
|
1882
|
+
END
|