|
1
|
ftp://ftp.cisco.com/pub/mibs/v2/SNMPv2-MIB.my
|
|
2
|
|
|
3
|
-- *****************************************************************
|
|
4
|
-- SNMPv2-MIB.my: Management Information Base (MIB) for the
|
|
5
|
-- Simple Network Management Protocol (SNMP)
|
|
6
|
--
|
|
7
|
-- March 2006, Wen Xu
|
|
8
|
--
|
|
9
|
-- Copyright (c) 2006 by cisco Systems, Inc.
|
|
10
|
-- All rights reserved.
|
|
11
|
-- *****************************************************************
|
|
12
|
--
|
|
13
|
-- This mib was extracted from RFC 3418
|
|
14
|
|
|
15
|
|
|
16
|
SNMPv2-MIB DEFINITIONS ::= BEGIN
|
|
17
|
|
|
18
|
IMPORTS
|
|
19
|
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
|
|
20
|
TimeTicks, Counter32, snmpModules, mib-2
|
|
21
|
FROM SNMPv2-SMI
|
|
22
|
DisplayString, TestAndIncr, TimeStamp
|
|
23
|
FROM SNMPv2-TC
|
|
24
|
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
|
|
25
|
FROM SNMPv2-CONF;
|
|
26
|
|
|
27
|
snmpMIB MODULE-IDENTITY
|
|
28
|
LAST-UPDATED "200210160000Z"
|
|
29
|
ORGANIZATION "IETF SNMPv3 Working Group"
|
|
30
|
CONTACT-INFO
|
|
31
|
"WG-EMail: snmpv3@lists.tislabs.com
|
|
32
|
Subscribe: snmpv3-request@lists.tislabs.com
|
|
33
|
|
|
34
|
Co-Chair: Russ Mundy
|
|
35
|
Network Associates Laboratories
|
|
36
|
postal: 15204 Omega Drive, Suite 300
|
|
37
|
Rockville, MD 20850-4601
|
|
38
|
USA
|
|
39
|
EMail: mundy@tislabs.com
|
|
40
|
phone: +1 301 947-7107
|
|
41
|
|
|
42
|
Co-Chair: David Harrington
|
|
43
|
Enterasys Networks
|
|
44
|
postal: 35 Industrial Way
|
|
45
|
P. O. Box 5005
|
|
46
|
Rochester, NH 03866-5005
|
|
47
|
USA
|
|
48
|
EMail: dbh@enterasys.com
|
|
49
|
phone: +1 603 337-2614
|
|
50
|
|
|
51
|
Editor: Randy Presuhn
|
|
52
|
BMC Software, Inc.
|
|
53
|
postal: 2141 North First Street
|
|
54
|
San Jose, CA 95131
|
|
55
|
USA
|
|
56
|
EMail: randy_presuhn@bmc.com
|
|
57
|
phone: +1 408 546-1006"
|
|
58
|
DESCRIPTION
|
|
59
|
"The MIB module for SNMP entities.
|
|
60
|
|
|
61
|
Copyright (C) The Internet Society (2002). This
|
|
62
|
version of this MIB module is part of RFC 3418;
|
|
63
|
see the RFC itself for full legal notices.
|
|
64
|
"
|
|
65
|
REVISION "200210160000Z"
|
|
66
|
DESCRIPTION
|
|
67
|
"This revision of this MIB module was published as
|
|
68
|
RFC 3418."
|
|
69
|
REVISION "199511090000Z"
|
|
70
|
DESCRIPTION
|
|
71
|
"This revision of this MIB module was published as
|
|
72
|
RFC 1907."
|
|
73
|
REVISION "199304010000Z"
|
|
74
|
DESCRIPTION
|
|
75
|
"The initial revision of this MIB module was published
|
|
76
|
as RFC 1450."
|
|
77
|
::= { snmpModules 1 }
|
|
78
|
|
|
79
|
snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 }
|
|
80
|
|
|
81
|
-- ::= { snmpMIBObjects 1 } this OID is obsolete
|
|
82
|
-- ::= { snmpMIBObjects 2 } this OID is obsolete
|
|
83
|
-- ::= { snmpMIBObjects 3 } this OID is obsolete
|
|
84
|
|
|
85
|
-- the System group
|
|
86
|
--
|
|
87
|
-- a collection of objects common to all managed systems.
|
|
88
|
|
|
89
|
system OBJECT IDENTIFIER ::= { mib-2 1 }
|
|
90
|
|
|
91
|
sysDescr OBJECT-TYPE
|
|
92
|
SYNTAX DisplayString (SIZE (0..255))
|
|
93
|
MAX-ACCESS read-only
|
|
94
|
STATUS current
|
|
95
|
DESCRIPTION
|
|
96
|
"A textual description of the entity. This value should
|
|
97
|
include the full name and version identification of
|
|
98
|
the system's hardware type, software operating-system,
|
|
99
|
and networking software."
|
|
100
|
::= { system 1 }
|
|
101
|
|
|
102
|
sysObjectID OBJECT-TYPE
|
|
103
|
SYNTAX OBJECT IDENTIFIER
|
|
104
|
MAX-ACCESS read-only
|
|
105
|
STATUS current
|
|
106
|
DESCRIPTION
|
|
107
|
"The vendor's authoritative identification of the
|
|
108
|
network management subsystem contained in the entity.
|
|
109
|
This value is allocated within the SMI enterprises
|
|
110
|
subtree (1.3.6.1.4.1) and provides an easy and
|
|
111
|
unambiguous means for determining `what kind of box' is
|
|
112
|
being managed. For example, if vendor `Flintstones,
|
|
113
|
Inc.' was assigned the subtree 1.3.6.1.4.1.424242,
|
|
114
|
it could assign the identifier 1.3.6.1.4.1.424242.1.1
|
|
115
|
to its `Fred Router'."
|
|
116
|
::= { system 2 }
|
|
117
|
|
|
118
|
sysUpTime OBJECT-TYPE
|
|
119
|
SYNTAX TimeTicks
|
|
120
|
MAX-ACCESS read-only
|
|
121
|
STATUS current
|
|
122
|
DESCRIPTION
|
|
123
|
"The time (in hundredths of a second) since the
|
|
124
|
network management portion of the system was last
|
|
125
|
re-initialized."
|
|
126
|
::= { system 3 }
|
|
127
|
|
|
128
|
sysContact OBJECT-TYPE
|
|
129
|
SYNTAX DisplayString (SIZE (0..255))
|
|
130
|
MAX-ACCESS read-write
|
|
131
|
STATUS current
|
|
132
|
DESCRIPTION
|
|
133
|
"The textual identification of the contact person for
|
|
134
|
this managed node, together with information on how
|
|
135
|
to contact this person. If no contact information is
|
|
136
|
known, the value is the zero-length string."
|
|
137
|
::= { system 4 }
|
|
138
|
|
|
139
|
sysName OBJECT-TYPE
|
|
140
|
SYNTAX DisplayString (SIZE (0..255))
|
|
141
|
MAX-ACCESS read-write
|
|
142
|
STATUS current
|
|
143
|
DESCRIPTION
|
|
144
|
"An administratively-assigned name for this managed
|
|
145
|
node. By convention, this is the node's fully-qualified
|
|
146
|
domain name. If the name is unknown, the value is
|
|
147
|
the zero-length string."
|
|
148
|
::= { system 5 }
|
|
149
|
|
|
150
|
sysLocation OBJECT-TYPE
|
|
151
|
SYNTAX DisplayString (SIZE (0..255))
|
|
152
|
MAX-ACCESS read-write
|
|
153
|
STATUS current
|
|
154
|
DESCRIPTION
|
|
155
|
"The physical location of this node (e.g., 'telephone
|
|
156
|
closet, 3rd floor'). If the location is unknown, the
|
|
157
|
value is the zero-length string."
|
|
158
|
::= { system 6 }
|
|
159
|
|
|
160
|
sysServices OBJECT-TYPE
|
|
161
|
SYNTAX INTEGER (0..127)
|
|
162
|
MAX-ACCESS read-only
|
|
163
|
STATUS current
|
|
164
|
DESCRIPTION
|
|
165
|
"A value which indicates the set of services that this
|
|
166
|
entity may potentially offer. The value is a sum.
|
|
167
|
This sum initially takes the value zero. Then, for
|
|
168
|
each layer, L, in the range 1 through 7, that this node
|
|
169
|
performs transactions for, 2 raised to (L - 1) is added
|
|
170
|
to the sum. For example, a node which performs only
|
|
171
|
routing functions would have a value of 4 (2^(3-1)).
|
|
172
|
In contrast, a node which is a host offering application
|
|
173
|
services would have a value of 72 (2^(4-1) + 2^(7-1)).
|
|
174
|
Note that in the context of the Internet suite of
|
|
175
|
protocols, values should be calculated accordingly:
|
|
176
|
|
|
177
|
layer functionality
|
|
178
|
1 physical (e.g., repeaters)
|
|
179
|
2 datalink/subnetwork (e.g., bridges)
|
|
180
|
3 internet (e.g., supports the IP)
|
|
181
|
4 end-to-end (e.g., supports the TCP)
|
|
182
|
7 applications (e.g., supports the SMTP)
|
|
183
|
|
|
184
|
For systems including OSI protocols, layers 5 and 6
|
|
185
|
may also be counted."
|
|
186
|
::= { system 7 }
|
|
187
|
|
|
188
|
-- object resource information
|
|
189
|
--
|
|
190
|
-- a collection of objects which describe the SNMP entity's
|
|
191
|
-- (statically and dynamically configurable) support of
|
|
192
|
-- various MIB modules.
|
|
193
|
|
|
194
|
sysORLastChange OBJECT-TYPE
|
|
195
|
SYNTAX TimeStamp
|
|
196
|
MAX-ACCESS read-only
|
|
197
|
STATUS current
|
|
198
|
DESCRIPTION
|
|
199
|
"The value of sysUpTime at the time of the most recent
|
|
200
|
change in state or value of any instance of sysORID."
|
|
201
|
::= { system 8 }
|
|
202
|
|
|
203
|
sysORTable OBJECT-TYPE
|
|
204
|
SYNTAX SEQUENCE OF SysOREntry
|
|
205
|
MAX-ACCESS not-accessible
|
|
206
|
STATUS current
|
|
207
|
DESCRIPTION
|
|
208
|
"The (conceptual) table listing the capabilities of
|
|
209
|
the local SNMP application acting as a command
|
|
210
|
responder with respect to various MIB modules.
|
|
211
|
SNMP entities having dynamically-configurable support
|
|
212
|
of MIB modules will have a dynamically-varying number
|
|
213
|
of conceptual rows."
|
|
214
|
::= { system 9 }
|
|
215
|
|
|
216
|
sysOREntry OBJECT-TYPE
|
|
217
|
SYNTAX SysOREntry
|
|
218
|
MAX-ACCESS not-accessible
|
|
219
|
STATUS current
|
|
220
|
DESCRIPTION
|
|
221
|
"An entry (conceptual row) in the sysORTable."
|
|
222
|
INDEX { sysORIndex }
|
|
223
|
::= { sysORTable 1 }
|
|
224
|
|
|
225
|
SysOREntry ::= SEQUENCE {
|
|
226
|
sysORIndex INTEGER,
|
|
227
|
sysORID OBJECT IDENTIFIER,
|
|
228
|
sysORDescr DisplayString,
|
|
229
|
sysORUpTime TimeStamp
|
|
230
|
}
|
|
231
|
|
|
232
|
sysORIndex OBJECT-TYPE
|
|
233
|
SYNTAX INTEGER (1..2147483647)
|
|
234
|
MAX-ACCESS not-accessible
|
|
235
|
STATUS current
|
|
236
|
DESCRIPTION
|
|
237
|
"The auxiliary variable used for identifying instances
|
|
238
|
of the columnar objects in the sysORTable."
|
|
239
|
::= { sysOREntry 1 }
|
|
240
|
|
|
241
|
sysORID OBJECT-TYPE
|
|
242
|
SYNTAX OBJECT IDENTIFIER
|
|
243
|
MAX-ACCESS read-only
|
|
244
|
STATUS current
|
|
245
|
DESCRIPTION
|
|
246
|
"An authoritative identification of a capabilities
|
|
247
|
statement with respect to various MIB modules supported
|
|
248
|
by the local SNMP application acting as a command
|
|
249
|
responder."
|
|
250
|
::= { sysOREntry 2 }
|
|
251
|
|
|
252
|
sysORDescr OBJECT-TYPE
|
|
253
|
SYNTAX DisplayString
|
|
254
|
MAX-ACCESS read-only
|
|
255
|
STATUS current
|
|
256
|
DESCRIPTION
|
|
257
|
"A textual description of the capabilities identified
|
|
258
|
by the corresponding instance of sysORID."
|
|
259
|
::= { sysOREntry 3 }
|
|
260
|
|
|
261
|
sysORUpTime OBJECT-TYPE
|
|
262
|
SYNTAX TimeStamp
|
|
263
|
MAX-ACCESS read-only
|
|
264
|
STATUS current
|
|
265
|
DESCRIPTION
|
|
266
|
"The value of sysUpTime at the time this conceptual
|
|
267
|
row was last instantiated."
|
|
268
|
::= { sysOREntry 4 }
|
|
269
|
|
|
270
|
-- the SNMP group
|
|
271
|
--
|
|
272
|
-- a collection of objects providing basic instrumentation and
|
|
273
|
-- control of an SNMP entity.
|
|
274
|
|
|
275
|
snmp OBJECT IDENTIFIER ::= { mib-2 11 }
|
|
276
|
|
|
277
|
snmpInPkts OBJECT-TYPE
|
|
278
|
SYNTAX Counter32
|
|
279
|
MAX-ACCESS read-only
|
|
280
|
STATUS current
|
|
281
|
DESCRIPTION
|
|
282
|
"The total number of messages delivered to the SNMP
|
|
283
|
entity from the transport service."
|
|
284
|
::= { snmp 1 }
|
|
285
|
|
|
286
|
snmpInBadVersions OBJECT-TYPE
|
|
287
|
SYNTAX Counter32
|
|
288
|
MAX-ACCESS read-only
|
|
289
|
STATUS current
|
|
290
|
DESCRIPTION
|
|
291
|
"The total number of SNMP messages which were delivered
|
|
292
|
to the SNMP entity and were for an unsupported SNMP
|
|
293
|
version."
|
|
294
|
::= { snmp 3 }
|
|
295
|
|
|
296
|
snmpInBadCommunityNames OBJECT-TYPE
|
|
297
|
SYNTAX Counter32
|
|
298
|
MAX-ACCESS read-only
|
|
299
|
STATUS current
|
|
300
|
DESCRIPTION
|
|
301
|
"The total number of community-based SNMP messages (for
|
|
302
|
example, SNMPv1) delivered to the SNMP entity which
|
|
303
|
used an SNMP community name not known to said entity.
|
|
304
|
Also, implementations which authenticate community-based
|
|
305
|
SNMP messages using check(s) in addition to matching
|
|
306
|
the community name (for example, by also checking
|
|
307
|
whether the message originated from a transport address
|
|
308
|
allowed to use a specified community name) MAY include
|
|
309
|
in this value the number of messages which failed the
|
|
310
|
additional check(s). It is strongly RECOMMENDED that
|
|
311
|
the documentation for any security model which is used
|
|
312
|
to authenticate community-based SNMP messages specify
|
|
313
|
the precise conditions that contribute to this value."
|
|
314
|
::= { snmp 4 }
|
|
315
|
|
|
316
|
snmpInBadCommunityUses OBJECT-TYPE
|
|
317
|
SYNTAX Counter32
|
|
318
|
MAX-ACCESS read-only
|
|
319
|
STATUS current
|
|
320
|
DESCRIPTION
|
|
321
|
"The total number of community-based SNMP messages (for
|
|
322
|
example, SNMPv1) delivered to the SNMP entity which
|
|
323
|
represented an SNMP operation that was not allowed for
|
|
324
|
the SNMP community named in the message. The precise
|
|
325
|
conditions under which this counter is incremented
|
|
326
|
(if at all) depend on how the SNMP entity implements
|
|
327
|
its access control mechanism and how its applications
|
|
328
|
interact with that access control mechanism. It is
|
|
329
|
strongly RECOMMENDED that the documentation for any
|
|
330
|
access control mechanism which is used to control access
|
|
331
|
to and visibility of MIB instrumentation specify the
|
|
332
|
precise conditions that contribute to this value."
|
|
333
|
::= { snmp 5 }
|
|
334
|
|
|
335
|
snmpInASNParseErrs OBJECT-TYPE
|
|
336
|
SYNTAX Counter32
|
|
337
|
MAX-ACCESS read-only
|
|
338
|
STATUS current
|
|
339
|
DESCRIPTION
|
|
340
|
"The total number of ASN.1 or BER errors encountered by
|
|
341
|
the SNMP entity when decoding received SNMP messages."
|
|
342
|
::= { snmp 6 }
|
|
343
|
|
|
344
|
snmpEnableAuthenTraps OBJECT-TYPE
|
|
345
|
SYNTAX INTEGER { enabled(1), disabled(2) }
|
|
346
|
MAX-ACCESS read-write
|
|
347
|
STATUS current
|
|
348
|
DESCRIPTION
|
|
349
|
"Indicates whether the SNMP entity is permitted to
|
|
350
|
generate authenticationFailure traps. The value of this
|
|
351
|
object overrides any configuration information; as such,
|
|
352
|
it provides a means whereby all authenticationFailure
|
|
353
|
traps may be disabled.
|
|
354
|
|
|
355
|
Note that it is strongly recommended that this object
|
|
356
|
be stored in non-volatile memory so that it remains
|
|
357
|
constant across re-initializations of the network
|
|
358
|
management system."
|
|
359
|
::= { snmp 30 }
|
|
360
|
|
|
361
|
snmpSilentDrops OBJECT-TYPE
|
|
362
|
SYNTAX Counter32
|
|
363
|
MAX-ACCESS read-only
|
|
364
|
STATUS current
|
|
365
|
DESCRIPTION
|
|
366
|
"The total number of Confirmed Class PDUs (such as
|
|
367
|
GetRequest-PDUs, GetNextRequest-PDUs,
|
|
368
|
GetBulkRequest-PDUs, SetRequest-PDUs, and
|
|
369
|
InformRequest-PDUs) delivered to the SNMP entity which
|
|
370
|
were silently dropped because the size of a reply
|
|
371
|
containing an alternate Response Class PDU (such as a
|
|
372
|
Response-PDU) with an empty variable-bindings field
|
|
373
|
was greater than either a local constraint or the
|
|
374
|
maximum message size associated with the originator of
|
|
375
|
the request."
|
|
376
|
::= { snmp 31 }
|
|
377
|
|
|
378
|
snmpProxyDrops OBJECT-TYPE
|
|
379
|
SYNTAX Counter32
|
|
380
|
MAX-ACCESS read-only
|
|
381
|
STATUS current
|
|
382
|
DESCRIPTION
|
|
383
|
"The total number of Confirmed Class PDUs
|
|
384
|
(such as GetRequest-PDUs, GetNextRequest-PDUs,
|
|
385
|
GetBulkRequest-PDUs, SetRequest-PDUs, and
|
|
386
|
InformRequest-PDUs) delivered to the SNMP entity which
|
|
387
|
were silently dropped because the transmission of
|
|
388
|
the (possibly translated) message to a proxy target
|
|
389
|
failed in a manner (other than a time-out) such that
|
|
390
|
no Response Class PDU (such as a Response-PDU) could
|
|
391
|
be returned."
|
|
392
|
::= { snmp 32 }
|
|
393
|
|
|
394
|
-- information for notifications
|
|
395
|
--
|
|
396
|
-- a collection of objects which allow the SNMP entity, when
|
|
397
|
-- supporting a notification originator application,
|
|
398
|
-- to be configured to generate SNMPv2-Trap-PDUs.
|
|
399
|
|
|
400
|
snmpTrap OBJECT IDENTIFIER ::= { snmpMIBObjects 4 }
|
|
401
|
|
|
402
|
snmpTrapOID OBJECT-TYPE
|
|
403
|
SYNTAX OBJECT IDENTIFIER
|
|
404
|
MAX-ACCESS accessible-for-notify
|
|
405
|
STATUS current
|
|
406
|
DESCRIPTION
|
|
407
|
"The authoritative identification of the notification
|
|
408
|
currently being sent. This variable occurs as
|
|
409
|
the second varbind in every SNMPv2-Trap-PDU and
|
|
410
|
InformRequest-PDU."
|
|
411
|
::= { snmpTrap 1 }
|
|
412
|
|
|
413
|
-- ::= { snmpTrap 2 } this OID is obsolete
|
|
414
|
|
|
415
|
snmpTrapEnterprise OBJECT-TYPE
|
|
416
|
SYNTAX OBJECT IDENTIFIER
|
|
417
|
MAX-ACCESS accessible-for-notify
|
|
418
|
STATUS current
|
|
419
|
DESCRIPTION
|
|
420
|
"The authoritative identification of the enterprise
|
|
421
|
associated with the trap currently being sent. When an
|
|
422
|
SNMP proxy agent is mapping an RFC1157 Trap-PDU
|
|
423
|
into a SNMPv2-Trap-PDU, this variable occurs as the
|
|
424
|
last varbind."
|
|
425
|
::= { snmpTrap 3 }
|
|
426
|
|
|
427
|
-- ::= { snmpTrap 4 } this OID is obsolete
|
|
428
|
|
|
429
|
-- well-known traps
|
|
430
|
|
|
431
|
snmpTraps OBJECT IDENTIFIER ::= { snmpMIBObjects 5 }
|
|
432
|
|
|
433
|
coldStart NOTIFICATION-TYPE
|
|
434
|
STATUS current
|
|
435
|
DESCRIPTION
|
|
436
|
"A coldStart trap signifies that the SNMP entity,
|
|
437
|
supporting a notification originator application, is
|
|
438
|
reinitializing itself and that its configuration may
|
|
439
|
have been altered."
|
|
440
|
::= { snmpTraps 1 }
|
|
441
|
|
|
442
|
warmStart NOTIFICATION-TYPE
|
|
443
|
STATUS current
|
|
444
|
DESCRIPTION
|
|
445
|
"A warmStart trap signifies that the SNMP entity,
|
|
446
|
supporting a notification originator application,
|
|
447
|
is reinitializing itself such that its configuration
|
|
448
|
is unaltered."
|
|
449
|
::= { snmpTraps 2 }
|
|
450
|
|
|
451
|
-- Note the linkDown NOTIFICATION-TYPE ::= { snmpTraps 3 }
|
|
452
|
-- and the linkUp NOTIFICATION-TYPE ::= { snmpTraps 4 }
|
|
453
|
-- are defined in RFC 2863 [RFC2863]
|
|
454
|
|
|
455
|
authenticationFailure NOTIFICATION-TYPE
|
|
456
|
STATUS current
|
|
457
|
DESCRIPTION
|
|
458
|
"An authenticationFailure trap signifies that the SNMP
|
|
459
|
entity has received a protocol message that is not
|
|
460
|
properly authenticated. While all implementations
|
|
461
|
of SNMP entities MAY be capable of generating this
|
|
462
|
trap, the snmpEnableAuthenTraps object indicates
|
|
463
|
whether this trap will be generated."
|
|
464
|
::= { snmpTraps 5 }
|
|
465
|
|
|
466
|
-- Note the egpNeighborLoss notification is defined
|
|
467
|
-- as { snmpTraps 6 } in RFC 1213
|
|
468
|
|
|
469
|
-- the set group
|
|
470
|
--
|
|
471
|
-- a collection of objects which allow several cooperating
|
|
472
|
-- command generator applications to coordinate their use of the
|
|
473
|
-- set operation.
|
|
474
|
|
|
475
|
snmpSet OBJECT IDENTIFIER ::= { snmpMIBObjects 6 }
|
|
476
|
|
|
477
|
snmpSetSerialNo OBJECT-TYPE
|
|
478
|
SYNTAX TestAndIncr
|
|
479
|
MAX-ACCESS read-write
|
|
480
|
STATUS current
|
|
481
|
DESCRIPTION
|
|
482
|
"An advisory lock used to allow several cooperating
|
|
483
|
command generator applications to coordinate their
|
|
484
|
use of the SNMP set operation.
|
|
485
|
|
|
486
|
This object is used for coarse-grain coordination.
|
|
487
|
To achieve fine-grain coordination, one or more similar
|
|
488
|
objects might be defined within each MIB group, as
|
|
489
|
appropriate."
|
|
490
|
::= { snmpSet 1 }
|
|
491
|
|
|
492
|
-- conformance information
|
|
493
|
|
|
494
|
snmpMIBConformance
|
|
495
|
OBJECT IDENTIFIER ::= { snmpMIB 2 }
|
|
496
|
|
|
497
|
snmpMIBCompliances
|
|
498
|
OBJECT IDENTIFIER ::= { snmpMIBConformance 1 }
|
|
499
|
snmpMIBGroups OBJECT IDENTIFIER ::= { snmpMIBConformance 2 }
|
|
500
|
|
|
501
|
-- compliance statements
|
|
502
|
-- ::= { snmpMIBCompliances 1 } this OID is obsolete
|
|
503
|
snmpBasicCompliance MODULE-COMPLIANCE
|
|
504
|
STATUS deprecated
|
|
505
|
DESCRIPTION
|
|
506
|
"The compliance statement for SNMPv2 entities which
|
|
507
|
implement the SNMPv2 MIB.
|
|
508
|
|
|
509
|
This compliance statement is replaced by
|
|
510
|
snmpBasicComplianceRev2."
|
|
511
|
MODULE -- this module
|
|
512
|
MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup,
|
|
513
|
snmpBasicNotificationsGroup }
|
|
514
|
|
|
515
|
GROUP snmpCommunityGroup1
|
|
516
|
DESCRIPTION
|
|
517
|
"This group is mandatory for SNMPv2 entities which
|
|
518
|
support community-based authentication."
|
|
519
|
|
|
520
|
::= { snmpMIBCompliances 2 }
|
|
521
|
|
|
522
|
snmpBasicComplianceRev2 MODULE-COMPLIANCE
|
|
523
|
STATUS current
|
|
524
|
DESCRIPTION
|
|
525
|
"The compliance statement for SNMP entities which
|
|
526
|
implement this MIB module."
|
|
527
|
MODULE -- this module
|
|
528
|
MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup,
|
|
529
|
snmpBasicNotificationsGroup }
|
|
530
|
|
|
531
|
GROUP snmpCommunityGroup1
|
|
532
|
DESCRIPTION
|
|
533
|
"This group is mandatory for SNMP entities which
|
|
534
|
support community-based authentication."
|
|
535
|
|
|
536
|
GROUP snmpWarmStartNotificationGroup
|
|
537
|
DESCRIPTION
|
|
538
|
"This group is mandatory for an SNMP entity which
|
|
539
|
supports command responder applications, and is
|
|
540
|
able to reinitialize itself such that its
|
|
541
|
configuration is unaltered."
|
|
542
|
|
|
543
|
::= { snmpMIBCompliances 3 }
|
|
544
|
|
|
545
|
-- units of conformance
|
|
546
|
|
|
547
|
-- ::= { snmpMIBGroups 1 } this OID is obsolete
|
|
548
|
-- ::= { snmpMIBGroups 2 } this OID is obsolete
|
|
549
|
-- ::= { snmpMIBGroups 3 } this OID is obsolete
|
|
550
|
-- ::= { snmpMIBGroups 4 } this OID is obsolete
|
|
551
|
|
|
552
|
snmpGroup OBJECT-GROUP
|
|
553
|
OBJECTS { snmpInPkts,
|
|
554
|
snmpInBadVersions,
|
|
555
|
snmpInASNParseErrs,
|
|
556
|
snmpSilentDrops,
|
|
557
|
snmpProxyDrops,
|
|
558
|
snmpEnableAuthenTraps }
|
|
559
|
STATUS current
|
|
560
|
DESCRIPTION
|
|
561
|
"A collection of objects providing basic instrumentation
|
|
562
|
and control of an SNMP entity."
|
|
563
|
::= { snmpMIBGroups 8 }
|
|
564
|
|
|
565
|
snmpCommunityGroup1 OBJECT-GROUP
|
|
566
|
OBJECTS { snmpInBadCommunityNames,
|
|
567
|
snmpInBadCommunityUses }
|
|
568
|
STATUS current
|
|
569
|
DESCRIPTION
|
|
570
|
"A collection of objects providing basic instrumentation
|
|
571
|
of a SNMP entity which supports community-based
|
|
572
|
authentication."
|
|
573
|
::= { snmpMIBGroups 9 }
|
|
574
|
|
|
575
|
snmpSetGroup OBJECT-GROUP
|
|
576
|
OBJECTS { snmpSetSerialNo }
|
|
577
|
STATUS current
|
|
578
|
DESCRIPTION
|
|
579
|
"A collection of objects which allow several cooperating
|
|
580
|
command generator applications to coordinate their
|
|
581
|
use of the set operation."
|
|
582
|
::= { snmpMIBGroups 5 }
|
|
583
|
|
|
584
|
systemGroup OBJECT-GROUP
|
|
585
|
OBJECTS { sysDescr, sysObjectID, sysUpTime,
|
|
586
|
sysContact, sysName, sysLocation,
|
|
587
|
sysServices,
|
|
588
|
sysORLastChange, sysORID,
|
|
589
|
sysORUpTime, sysORDescr }
|
|
590
|
STATUS current
|
|
591
|
DESCRIPTION
|
|
592
|
"The system group defines objects which are common to all
|
|
593
|
managed systems."
|
|
594
|
::= { snmpMIBGroups 6 }
|
|
595
|
|
|
596
|
snmpBasicNotificationsGroup NOTIFICATION-GROUP
|
|
597
|
NOTIFICATIONS { coldStart, authenticationFailure }
|
|
598
|
STATUS current
|
|
599
|
DESCRIPTION
|
|
600
|
"The basic notifications implemented by an SNMP entity
|
|
601
|
supporting command responder applications."
|
|
602
|
::= { snmpMIBGroups 7 }
|
|
603
|
|
|
604
|
snmpWarmStartNotificationGroup NOTIFICATION-GROUP
|
|
605
|
NOTIFICATIONS { warmStart }
|
|
606
|
STATUS current
|
|
607
|
DESCRIPTION
|
|
608
|
"An additional notification for an SNMP entity supporting
|
|
609
|
command responder applications, if it is able to reinitialize
|
|
610
|
itself such that its configuration is unaltered."
|
|
611
|
::= { snmpMIBGroups 11 }
|
|
612
|
|
|
613
|
snmpNotificationGroup OBJECT-GROUP
|
|
614
|
OBJECTS { snmpTrapOID, snmpTrapEnterprise }
|
|
615
|
STATUS current
|
|
616
|
DESCRIPTION
|
|
617
|
"These objects are required for entities
|
|
618
|
which support notification originator applications."
|
|
619
|
::= { snmpMIBGroups 12 }
|
|
620
|
|
|
621
|
-- definitions in RFC 1213 made obsolete by the inclusion of a
|
|
622
|
-- subset of the snmp group in this MIB
|
|
623
|
|
|
624
|
snmpOutPkts OBJECT-TYPE
|
|
625
|
SYNTAX Counter32
|
|
626
|
MAX-ACCESS read-only
|
|
627
|
STATUS obsolete
|
|
628
|
DESCRIPTION
|
|
629
|
"The total number of SNMP Messages which were
|
|
630
|
passed from the SNMP protocol entity to the
|
|
631
|
transport service."
|
|
632
|
::= { snmp 2 }
|
|
633
|
|
|
634
|
-- { snmp 7 } is not used
|
|
635
|
|
|
636
|
snmpInTooBigs OBJECT-TYPE
|
|
637
|
SYNTAX Counter32
|
|
638
|
MAX-ACCESS read-only
|
|
639
|
STATUS obsolete
|
|
640
|
DESCRIPTION
|
|
641
|
"The total number of SNMP PDUs which were
|
|
642
|
delivered to the SNMP protocol entity and for
|
|
643
|
which the value of the error-status field was
|
|
644
|
`tooBig'."
|
|
645
|
::= { snmp 8 }
|
|
646
|
|
|
647
|
snmpInNoSuchNames OBJECT-TYPE
|
|
648
|
SYNTAX Counter32
|
|
649
|
MAX-ACCESS read-only
|
|
650
|
STATUS obsolete
|
|
651
|
DESCRIPTION
|
|
652
|
"The total number of SNMP PDUs which were
|
|
653
|
delivered to the SNMP protocol entity and for
|
|
654
|
which the value of the error-status field was
|
|
655
|
`noSuchName'."
|
|
656
|
::= { snmp 9 }
|
|
657
|
|
|
658
|
snmpInBadValues OBJECT-TYPE
|
|
659
|
SYNTAX Counter32
|
|
660
|
MAX-ACCESS read-only
|
|
661
|
STATUS obsolete
|
|
662
|
DESCRIPTION
|
|
663
|
"The total number of SNMP PDUs which were
|
|
664
|
delivered to the SNMP protocol entity and for
|
|
665
|
which the value of the error-status field was
|
|
666
|
`badValue'."
|
|
667
|
::= { snmp 10 }
|
|
668
|
|
|
669
|
snmpInReadOnlys OBJECT-TYPE
|
|
670
|
SYNTAX Counter32
|
|
671
|
MAX-ACCESS read-only
|
|
672
|
STATUS obsolete
|
|
673
|
DESCRIPTION
|
|
674
|
"The total number valid SNMP PDUs which were delivered
|
|
675
|
to the SNMP protocol entity and for which the value
|
|
676
|
of the error-status field was `readOnly'. It should
|
|
677
|
be noted that it is a protocol error to generate an
|
|
678
|
SNMP PDU which contains the value `readOnly' in the
|
|
679
|
error-status field, as such this object is provided
|
|
680
|
as a means of detecting incorrect implementations of
|
|
681
|
the SNMP."
|
|
682
|
::= { snmp 11 }
|
|
683
|
|
|
684
|
snmpInGenErrs OBJECT-TYPE
|
|
685
|
SYNTAX Counter32
|
|
686
|
MAX-ACCESS read-only
|
|
687
|
STATUS obsolete
|
|
688
|
DESCRIPTION
|
|
689
|
"The total number of SNMP PDUs which were delivered
|
|
690
|
to the SNMP protocol entity and for which the value
|
|
691
|
of the error-status field was `genErr'."
|
|
692
|
::= { snmp 12 }
|
|
693
|
|
|
694
|
snmpInTotalReqVars OBJECT-TYPE
|
|
695
|
SYNTAX Counter32
|
|
696
|
MAX-ACCESS read-only
|
|
697
|
STATUS obsolete
|
|
698
|
DESCRIPTION
|
|
699
|
"The total number of MIB objects which have been
|
|
700
|
retrieved successfully by the SNMP protocol entity
|
|
701
|
as the result of receiving valid SNMP Get-Request
|
|
702
|
and Get-Next PDUs."
|
|
703
|
::= { snmp 13 }
|
|
704
|
|
|
705
|
snmpInTotalSetVars OBJECT-TYPE
|
|
706
|
SYNTAX Counter32
|
|
707
|
MAX-ACCESS read-only
|
|
708
|
STATUS obsolete
|
|
709
|
DESCRIPTION
|
|
710
|
"The total number of MIB objects which have been
|
|
711
|
altered successfully by the SNMP protocol entity as
|
|
712
|
the result of receiving valid SNMP Set-Request PDUs."
|
|
713
|
::= { snmp 14 }
|
|
714
|
|
|
715
|
snmpInGetRequests OBJECT-TYPE
|
|
716
|
SYNTAX Counter32
|
|
717
|
MAX-ACCESS read-only
|
|
718
|
STATUS obsolete
|
|
719
|
DESCRIPTION
|
|
720
|
"The total number of SNMP Get-Request PDUs which
|
|
721
|
have been accepted and processed by the SNMP
|
|
722
|
protocol entity."
|
|
723
|
::= { snmp 15 }
|
|
724
|
|
|
725
|
snmpInGetNexts OBJECT-TYPE
|
|
726
|
SYNTAX Counter32
|
|
727
|
MAX-ACCESS read-only
|
|
728
|
STATUS obsolete
|
|
729
|
DESCRIPTION
|
|
730
|
"The total number of SNMP Get-Next PDUs which have been
|
|
731
|
accepted and processed by the SNMP protocol entity."
|
|
732
|
::= { snmp 16 }
|
|
733
|
|
|
734
|
snmpInSetRequests OBJECT-TYPE
|
|
735
|
SYNTAX Counter32
|
|
736
|
MAX-ACCESS read-only
|
|
737
|
STATUS obsolete
|
|
738
|
DESCRIPTION
|
|
739
|
"The total number of SNMP Set-Request PDUs which
|
|
740
|
have been accepted and processed by the SNMP protocol
|
|
741
|
entity."
|
|
742
|
::= { snmp 17 }
|
|
743
|
|
|
744
|
snmpInGetResponses OBJECT-TYPE
|
|
745
|
SYNTAX Counter32
|
|
746
|
MAX-ACCESS read-only
|
|
747
|
STATUS obsolete
|
|
748
|
DESCRIPTION
|
|
749
|
"The total number of SNMP Get-Response PDUs which
|
|
750
|
have been accepted and processed by the SNMP protocol
|
|
751
|
entity."
|
|
752
|
::= { snmp 18 }
|
|
753
|
|
|
754
|
snmpInTraps OBJECT-TYPE
|
|
755
|
SYNTAX Counter32
|
|
756
|
MAX-ACCESS read-only
|
|
757
|
STATUS obsolete
|
|
758
|
DESCRIPTION
|
|
759
|
"The total number of SNMP Trap PDUs which have been
|
|
760
|
accepted and processed by the SNMP protocol entity."
|
|
761
|
::= { snmp 19 }
|
|
762
|
|
|
763
|
snmpOutTooBigs OBJECT-TYPE
|
|
764
|
SYNTAX Counter32
|
|
765
|
MAX-ACCESS read-only
|
|
766
|
STATUS obsolete
|
|
767
|
DESCRIPTION
|
|
768
|
"The total number of SNMP PDUs which were generated
|
|
769
|
by the SNMP protocol entity and for which the value
|
|
770
|
of the error-status field was `tooBig.'"
|
|
771
|
::= { snmp 20 }
|
|
772
|
|
|
773
|
snmpOutNoSuchNames OBJECT-TYPE
|
|
774
|
SYNTAX Counter32
|
|
775
|
MAX-ACCESS read-only
|
|
776
|
STATUS obsolete
|
|
777
|
DESCRIPTION
|
|
778
|
"The total number of SNMP PDUs which were generated
|
|
779
|
by the SNMP protocol entity and for which the value
|
|
780
|
of the error-status was `noSuchName'."
|
|
781
|
::= { snmp 21 }
|
|
782
|
|
|
783
|
snmpOutBadValues OBJECT-TYPE
|
|
784
|
SYNTAX Counter32
|
|
785
|
MAX-ACCESS read-only
|
|
786
|
STATUS obsolete
|
|
787
|
DESCRIPTION
|
|
788
|
"The total number of SNMP PDUs which were generated
|
|
789
|
by the SNMP protocol entity and for which the value
|
|
790
|
of the error-status field was `badValue'."
|
|
791
|
::= { snmp 22 }
|
|
792
|
|
|
793
|
-- { snmp 23 } is not used
|
|
794
|
|
|
795
|
snmpOutGenErrs OBJECT-TYPE
|
|
796
|
SYNTAX Counter32
|
|
797
|
MAX-ACCESS read-only
|
|
798
|
STATUS obsolete
|
|
799
|
DESCRIPTION
|
|
800
|
"The total number of SNMP PDUs which were generated
|
|
801
|
by the SNMP protocol entity and for which the value
|
|
802
|
of the error-status field was `genErr'."
|
|
803
|
::= { snmp 24 }
|
|
804
|
|
|
805
|
snmpOutGetRequests OBJECT-TYPE
|
|
806
|
SYNTAX Counter32
|
|
807
|
MAX-ACCESS read-only
|
|
808
|
STATUS obsolete
|
|
809
|
DESCRIPTION
|
|
810
|
"The total number of SNMP Get-Request PDUs which
|
|
811
|
have been generated by the SNMP protocol entity."
|
|
812
|
::= { snmp 25 }
|
|
813
|
|
|
814
|
snmpOutGetNexts OBJECT-TYPE
|
|
815
|
SYNTAX Counter32
|
|
816
|
MAX-ACCESS read-only
|
|
817
|
STATUS obsolete
|
|
818
|
DESCRIPTION
|
|
819
|
"The total number of SNMP Get-Next PDUs which have
|
|
820
|
been generated by the SNMP protocol entity."
|
|
821
|
::= { snmp 26 }
|
|
822
|
|
|
823
|
snmpOutSetRequests OBJECT-TYPE
|
|
824
|
SYNTAX Counter32
|
|
825
|
MAX-ACCESS read-only
|
|
826
|
STATUS obsolete
|
|
827
|
DESCRIPTION
|
|
828
|
"The total number of SNMP Set-Request PDUs which
|
|
829
|
have been generated by the SNMP protocol entity."
|
|
830
|
::= { snmp 27 }
|
|
831
|
|
|
832
|
snmpOutGetResponses OBJECT-TYPE
|
|
833
|
SYNTAX Counter32
|
|
834
|
MAX-ACCESS read-only
|
|
835
|
STATUS obsolete
|
|
836
|
DESCRIPTION
|
|
837
|
"The total number of SNMP Get-Response PDUs which
|
|
838
|
have been generated by the SNMP protocol entity."
|
|
839
|
::= { snmp 28 }
|
|
840
|
|
|
841
|
snmpOutTraps OBJECT-TYPE
|
|
842
|
SYNTAX Counter32
|
|
843
|
MAX-ACCESS read-only
|
|
844
|
STATUS obsolete
|
|
845
|
DESCRIPTION
|
|
846
|
"The total number of SNMP Trap PDUs which have
|
|
847
|
been generated by the SNMP protocol entity."
|
|
848
|
::= { snmp 29 }
|
|
849
|
|
|
850
|
snmpObsoleteGroup OBJECT-GROUP
|
|
851
|
OBJECTS { snmpOutPkts, snmpInTooBigs, snmpInNoSuchNames,
|
|
852
|
snmpInBadValues, snmpInReadOnlys, snmpInGenErrs,
|
|
853
|
snmpInTotalReqVars, snmpInTotalSetVars,
|
|
854
|
snmpInGetRequests, snmpInGetNexts, snmpInSetRequests,
|
|
855
|
snmpInGetResponses, snmpInTraps, snmpOutTooBigs,
|
|
856
|
snmpOutNoSuchNames, snmpOutBadValues,
|
|
857
|
snmpOutGenErrs, snmpOutGetRequests, snmpOutGetNexts,
|
|
858
|
snmpOutSetRequests, snmpOutGetResponses, snmpOutTraps
|
|
859
|
}
|
|
860
|
STATUS obsolete
|
|
861
|
DESCRIPTION
|
|
862
|
"A collection of objects from RFC 1213 made obsolete
|
|
863
|
by this MIB module."
|
|
864
|
::= { snmpMIBGroups 10 }
|
|
865
|
|
|
866
|
END
|