1
SNMPv2-MIB DEFINITIONS ::= BEGIN
4
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
5
TimeTicks, Counter32, snmpModules, mib-2
7
DisplayString, TestAndIncr, TimeStamp
10
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
13
snmpMIB MODULE-IDENTITY
14
LAST-UPDATED "200210160000Z"
15
ORGANIZATION "IETF SNMPv3 Working Group"
17
"WG-EMail: snmpv3@lists.tislabs.com
18
Subscribe: snmpv3-request@lists.tislabs.com
21
Network Associates Laboratories
22
postal: 15204 Omega Drive, Suite 300
23
Rockville, MD 20850-4601
25
EMail: mundy@tislabs.com
26
phone: +1 301 947-7107
28
Co-Chair: David Harrington
30
postal: 35 Industrial Way
32
Rochester, NH 03866-5005
34
EMail: dbh@enterasys.com
35
phone: +1 603 337-2614
39
postal: 2141 North First Street
42
EMail: randy_presuhn@bmc.com
43
phone: +1 408 546-1006"
45
"The MIB module for SNMP entities.
47
Copyright (C) The Internet Society (2002). This
48
version of this MIB module is part of RFC 3418;
49
see the RFC itself for full legal notices.
51
REVISION "200210160000Z"
53
"This revision of this MIB module was published as
55
REVISION "199511090000Z"
57
"This revision of this MIB module was published as
59
REVISION "199304010000Z"
61
"The initial revision of this MIB module was published
65
snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 }
67
-- ::= { snmpMIBObjects 1 } this OID is obsolete
68
-- ::= { snmpMIBObjects 2 } this OID is obsolete
69
-- ::= { snmpMIBObjects 3 } this OID is obsolete
73
-- a collection of objects common to all managed systems.
75
system OBJECT IDENTIFIER ::= { mib-2 1 }
78
SYNTAX DisplayString (SIZE (0..255))
82
"A textual description of the entity. This value should
83
include the full name and version identification of
84
the system's hardware type, software operating-system,
85
and networking software."
88
sysObjectID OBJECT-TYPE
89
SYNTAX OBJECT IDENTIFIER
93
"The vendor's authoritative identification of the
94
network management subsystem contained in the entity.
95
This value is allocated within the SMI enterprises
96
subtree (1.3.6.1.4.1) and provides an easy and
97
unambiguous means for determining `what kind of box' is
98
being managed. For example, if vendor `Flintstones,
99
Inc.' was assigned the subtree 1.3.6.1.4.1.424242,
100
it could assign the identifier 1.3.6.1.4.1.424242.1.1
101
to its `Fred Router'."
104
sysUpTime OBJECT-TYPE
109
"The time (in hundredths of a second) since the
110
network management portion of the system was last
114
sysContact OBJECT-TYPE
115
SYNTAX DisplayString (SIZE (0..255))
116
MAX-ACCESS read-write
119
"The textual identification of the contact person for
120
this managed node, together with information on how
121
to contact this person. If no contact information is
122
known, the value is the zero-length string."
126
SYNTAX DisplayString (SIZE (0..255))
127
MAX-ACCESS read-write
130
"An administratively-assigned name for this managed
131
node. By convention, this is the node's fully-qualified
132
domain name. If the name is unknown, the value is
133
the zero-length string."
136
sysLocation OBJECT-TYPE
137
SYNTAX DisplayString (SIZE (0..255))
138
MAX-ACCESS read-write
141
"The physical location of this node (e.g., 'telephone
142
closet, 3rd floor'). If the location is unknown, the
143
value is the zero-length string."
146
sysServices OBJECT-TYPE
147
SYNTAX INTEGER (0..127)
151
"A value which indicates the set of services that this
152
entity may potentially offer. The value is a sum.
154
This sum initially takes the value zero. Then, for
155
each layer, L, in the range 1 through 7, that this node
156
performs transactions for, 2 raised to (L - 1) is added
157
to the sum. For example, a node which performs only
158
routing functions would have a value of 4 (2^(3-1)).
159
In contrast, a node which is a host offering application
160
services would have a value of 72 (2^(4-1) + 2^(7-1)).
161
Note that in the context of the Internet suite of
162
protocols, values should be calculated accordingly:
165
1 physical (e.g., repeaters)
166
2 datalink/subnetwork (e.g., bridges)
167
3 internet (e.g., supports the IP)
168
4 end-to-end (e.g., supports the TCP)
169
7 applications (e.g., supports the SMTP)
171
For systems including OSI protocols, layers 5 and 6
172
may also be counted."
175
-- object resource information
177
-- a collection of objects which describe the SNMP entity's
178
-- (statically and dynamically configurable) support of
179
-- various MIB modules.
181
sysORLastChange OBJECT-TYPE
186
"The value of sysUpTime at the time of the most recent
187
change in state or value of any instance of sysORID."
190
sysORTable OBJECT-TYPE
191
SYNTAX SEQUENCE OF SysOREntry
192
MAX-ACCESS not-accessible
195
"The (conceptual) table listing the capabilities of
196
the local SNMP application acting as a command
197
responder with respect to various MIB modules.
198
SNMP entities having dynamically-configurable support
199
of MIB modules will have a dynamically-varying number
203
sysOREntry OBJECT-TYPE
205
MAX-ACCESS not-accessible
208
"An entry (conceptual row) in the sysORTable."
212
SysOREntry ::= SEQUENCE {
214
sysORID OBJECT IDENTIFIER,
215
sysORDescr DisplayString,
216
sysORUpTime TimeStamp
219
sysORIndex OBJECT-TYPE
220
SYNTAX INTEGER (1..2147483647)
221
MAX-ACCESS not-accessible
224
"The auxiliary variable used for identifying instances
225
of the columnar objects in the sysORTable."
229
SYNTAX OBJECT IDENTIFIER
233
"An authoritative identification of a capabilities
234
statement with respect to various MIB modules supported
235
by the local SNMP application acting as a command
239
sysORDescr OBJECT-TYPE
244
"A textual description of the capabilities identified
245
by the corresponding instance of sysORID."
248
sysORUpTime OBJECT-TYPE
253
"The value of sysUpTime at the time this conceptual
254
row was last instantiated."
259
-- a collection of objects providing basic instrumentation and
260
-- control of an SNMP entity.
262
snmp OBJECT IDENTIFIER ::= { mib-2 11 }
264
snmpInPkts OBJECT-TYPE
269
"The total number of messages delivered to the SNMP
270
entity from the transport service."
273
snmpInBadVersions OBJECT-TYPE
278
"The total number of SNMP messages which were delivered
279
to the SNMP entity and were for an unsupported SNMP
283
snmpInBadCommunityNames OBJECT-TYPE
288
"The total number of community-based SNMP messages (for
289
example, SNMPv1) delivered to the SNMP entity which
290
used an SNMP community name not known to said entity.
291
Also, implementations which authenticate community-based
292
SNMP messages using check(s) in addition to matching
293
the community name (for example, by also checking
294
whether the message originated from a transport address
295
allowed to use a specified community name) MAY include
296
in this value the number of messages which failed the
297
additional check(s). It is strongly RECOMMENDED that
299
the documentation for any security model which is used
300
to authenticate community-based SNMP messages specify
301
the precise conditions that contribute to this value."
304
snmpInBadCommunityUses OBJECT-TYPE
309
"The total number of community-based SNMP messages (for
310
example, SNMPv1) delivered to the SNMP entity which
311
represented an SNMP operation that was not allowed for
312
the SNMP community named in the message. The precise
313
conditions under which this counter is incremented
314
(if at all) depend on how the SNMP entity implements
315
its access control mechanism and how its applications
316
interact with that access control mechanism. It is
317
strongly RECOMMENDED that the documentation for any
318
access control mechanism which is used to control access
319
to and visibility of MIB instrumentation specify the
320
precise conditions that contribute to this value."
323
snmpInASNParseErrs OBJECT-TYPE
328
"The total number of ASN.1 or BER errors encountered by
329
the SNMP entity when decoding received SNMP messages."
332
snmpEnableAuthenTraps OBJECT-TYPE
333
SYNTAX INTEGER { enabled(1), disabled(2) }
334
MAX-ACCESS read-write
337
"Indicates whether the SNMP entity is permitted to
338
generate authenticationFailure traps. The value of this
339
object overrides any configuration information; as such,
340
it provides a means whereby all authenticationFailure
341
traps may be disabled.
343
Note that it is strongly recommended that this object
344
be stored in non-volatile memory so that it remains
345
constant across re-initializations of the network
349
snmpSilentDrops OBJECT-TYPE
354
"The total number of Confirmed Class PDUs (such as
355
GetRequest-PDUs, GetNextRequest-PDUs,
356
GetBulkRequest-PDUs, SetRequest-PDUs, and
357
InformRequest-PDUs) delivered to the SNMP entity which
358
were silently dropped because the size of a reply
359
containing an alternate Response Class PDU (such as a
360
Response-PDU) with an empty variable-bindings field
361
was greater than either a local constraint or the
362
maximum message size associated with the originator of
366
snmpProxyDrops OBJECT-TYPE
371
"The total number of Confirmed Class PDUs
372
(such as GetRequest-PDUs, GetNextRequest-PDUs,
373
GetBulkRequest-PDUs, SetRequest-PDUs, and
374
InformRequest-PDUs) delivered to the SNMP entity which
375
were silently dropped because the transmission of
376
the (possibly translated) message to a proxy target
377
failed in a manner (other than a time-out) such that
378
no Response Class PDU (such as a Response-PDU) could
382
-- information for notifications
384
-- a collection of objects which allow the SNMP entity, when
385
-- supporting a notification originator application,
386
-- to be configured to generate SNMPv2-Trap-PDUs.
388
snmpTrap OBJECT IDENTIFIER ::= { snmpMIBObjects 4 }
390
snmpTrapOID OBJECT-TYPE
391
SYNTAX OBJECT IDENTIFIER
392
MAX-ACCESS accessible-for-notify
395
"The authoritative identification of the notification
396
currently being sent. This variable occurs as
397
the second varbind in every SNMPv2-Trap-PDU and
401
-- ::= { snmpTrap 2 } this OID is obsolete
403
snmpTrapEnterprise OBJECT-TYPE
404
SYNTAX OBJECT IDENTIFIER
405
MAX-ACCESS accessible-for-notify
408
"The authoritative identification of the enterprise
409
associated with the trap currently being sent. When an
410
SNMP proxy agent is mapping an RFC1157 Trap-PDU
411
into a SNMPv2-Trap-PDU, this variable occurs as the
415
-- ::= { snmpTrap 4 } this OID is obsolete
419
snmpTraps OBJECT IDENTIFIER ::= { snmpMIBObjects 5 }
421
coldStart NOTIFICATION-TYPE
424
"A coldStart trap signifies that the SNMP entity,
425
supporting a notification originator application, is
426
reinitializing itself and that its configuration may
430
warmStart NOTIFICATION-TYPE
433
"A warmStart trap signifies that the SNMP entity,
434
supporting a notification originator application,
435
is reinitializing itself such that its configuration
439
-- Note the linkDown NOTIFICATION-TYPE ::= { snmpTraps 3 }
440
-- and the linkUp NOTIFICATION-TYPE ::= { snmpTraps 4 }
441
-- are defined in RFC 2863 [RFC2863]
443
authenticationFailure NOTIFICATION-TYPE
446
"An authenticationFailure trap signifies that the SNMP
447
entity has received a protocol message that is not
448
properly authenticated. While all implementations
449
of SNMP entities MAY be capable of generating this
450
trap, the snmpEnableAuthenTraps object indicates
451
whether this trap will be generated."
454
-- Note the egpNeighborLoss notification is defined
455
-- as { snmpTraps 6 } in RFC 1213
459
-- a collection of objects which allow several cooperating
460
-- command generator applications to coordinate their use of the
463
snmpSet OBJECT IDENTIFIER ::= { snmpMIBObjects 6 }
465
snmpSetSerialNo OBJECT-TYPE
467
MAX-ACCESS read-write
470
"An advisory lock used to allow several cooperating
471
command generator applications to coordinate their
472
use of the SNMP set operation.
474
This object is used for coarse-grain coordination.
475
To achieve fine-grain coordination, one or more similar
476
objects might be defined within each MIB group, as
480
-- conformance information
483
OBJECT IDENTIFIER ::= { snmpMIB 2 }
486
OBJECT IDENTIFIER ::= { snmpMIBConformance 1 }
487
snmpMIBGroups OBJECT IDENTIFIER ::= { snmpMIBConformance 2 }
489
-- compliance statements
491
-- ::= { snmpMIBCompliances 1 } this OID is obsolete
492
snmpBasicCompliance MODULE-COMPLIANCE
495
"The compliance statement for SNMPv2 entities which
496
implement the SNMPv2 MIB.
498
This compliance statement is replaced by
499
snmpBasicComplianceRev2."
500
MODULE -- this module
501
MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup,
502
snmpBasicNotificationsGroup }
504
GROUP snmpCommunityGroup
506
"This group is mandatory for SNMPv2 entities which
507
support community-based authentication."
508
::= { snmpMIBCompliances 2 }
510
snmpBasicComplianceRev2 MODULE-COMPLIANCE
513
"The compliance statement for SNMP entities which
514
implement this MIB module."
515
MODULE -- this module
516
MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup,
517
snmpBasicNotificationsGroup }
519
GROUP snmpCommunityGroup
521
"This group is mandatory for SNMP entities which
522
support community-based authentication."
524
GROUP snmpWarmStartNotificationGroup
526
"This group is mandatory for an SNMP entity which
527
supports command responder applications, and is
528
able to reinitialize itself such that its
529
configuration is unaltered."
530
::= { snmpMIBCompliances 3 }
532
-- units of conformance
534
-- ::= { snmpMIBGroups 1 } this OID is obsolete
535
-- ::= { snmpMIBGroups 2 } this OID is obsolete
536
-- ::= { snmpMIBGroups 3 } this OID is obsolete
538
-- ::= { snmpMIBGroups 4 } this OID is obsolete
540
snmpGroup OBJECT-GROUP
541
OBJECTS { snmpInPkts,
546
snmpEnableAuthenTraps }
549
"A collection of objects providing basic instrumentation
550
and control of an SNMP entity."
551
::= { snmpMIBGroups 8 }
553
snmpCommunityGroup OBJECT-GROUP
554
OBJECTS { snmpInBadCommunityNames,
555
snmpInBadCommunityUses }
558
"A collection of objects providing basic instrumentation
559
of a SNMP entity which supports community-based
561
::= { snmpMIBGroups 9 }
563
snmpSetGroup OBJECT-GROUP
564
OBJECTS { snmpSetSerialNo }
567
"A collection of objects which allow several cooperating
568
command generator applications to coordinate their
569
use of the set operation."
570
::= { snmpMIBGroups 5 }
572
systemGroup OBJECT-GROUP
573
OBJECTS { sysDescr, sysObjectID, sysUpTime,
574
sysContact, sysName, sysLocation,
576
sysORLastChange, sysORID,
577
sysORUpTime, sysORDescr }
580
"The system group defines objects which are common to all
582
::= { snmpMIBGroups 6 }
584
snmpBasicNotificationsGroup NOTIFICATION-GROUP
585
NOTIFICATIONS { coldStart, authenticationFailure }
588
"The basic notifications implemented by an SNMP entity
589
supporting command responder applications."
590
::= { snmpMIBGroups 7 }
592
snmpWarmStartNotificationGroup NOTIFICATION-GROUP
593
NOTIFICATIONS { warmStart }
596
"An additional notification for an SNMP entity supporting
597
command responder applications, if it is able to reinitialize
598
itself such that its configuration is unaltered."
599
::= { snmpMIBGroups 11 }
601
snmpNotificationGroup OBJECT-GROUP
602
OBJECTS { snmpTrapOID, snmpTrapEnterprise }
605
"These objects are required for entities
606
which support notification originator applications."
607
::= { snmpMIBGroups 12 }
609
-- definitions in RFC 1213 made obsolete by the inclusion of a
610
-- subset of the snmp group in this MIB
612
snmpOutPkts OBJECT-TYPE
617
"The total number of SNMP Messages which were
618
passed from the SNMP protocol entity to the
622
-- { snmp 7 } is not used
624
snmpInTooBigs OBJECT-TYPE
629
"The total number of SNMP PDUs which were
630
delivered to the SNMP protocol entity and for
631
which the value of the error-status field was
635
snmpInNoSuchNames OBJECT-TYPE
640
"The total number of SNMP PDUs which were
641
delivered to the SNMP protocol entity and for
642
which the value of the error-status field was
646
snmpInBadValues OBJECT-TYPE
651
"The total number of SNMP PDUs which were
652
delivered to the SNMP protocol entity and for
653
which the value of the error-status field was
657
snmpInReadOnlys OBJECT-TYPE
662
"The total number valid SNMP PDUs which were delivered
663
to the SNMP protocol entity and for which the value
664
of the error-status field was `readOnly'. It should
665
be noted that it is a protocol error to generate an
666
SNMP PDU which contains the value `readOnly' in the
667
error-status field, as such this object is provided
668
as a means of detecting incorrect implementations of
672
snmpInGenErrs OBJECT-TYPE
677
"The total number of SNMP PDUs which were delivered
678
to the SNMP protocol entity and for which the value
679
of the error-status field was `genErr'."
682
snmpInTotalReqVars OBJECT-TYPE
687
"The total number of MIB objects which have been
688
retrieved successfully by the SNMP protocol entity
689
as the result of receiving valid SNMP Get-Request
693
snmpInTotalSetVars OBJECT-TYPE
698
"The total number of MIB objects which have been
699
altered successfully by the SNMP protocol entity as
700
the result of receiving valid SNMP Set-Request PDUs."
703
snmpInGetRequests OBJECT-TYPE
708
"The total number of SNMP Get-Request PDUs which
709
have been accepted and processed by the SNMP
713
snmpInGetNexts OBJECT-TYPE
718
"The total number of SNMP Get-Next PDUs which have been
719
accepted and processed by the SNMP protocol entity."
722
snmpInSetRequests OBJECT-TYPE
727
"The total number of SNMP Set-Request PDUs which
728
have been accepted and processed by the SNMP protocol
732
snmpInGetResponses OBJECT-TYPE
737
"The total number of SNMP Get-Response PDUs which
738
have been accepted and processed by the SNMP protocol
742
snmpInTraps OBJECT-TYPE
747
"The total number of SNMP Trap PDUs which have been
748
accepted and processed by the SNMP protocol entity."
751
snmpOutTooBigs OBJECT-TYPE
756
"The total number of SNMP PDUs which were generated
757
by the SNMP protocol entity and for which the value
758
of the error-status field was `tooBig.'"
761
snmpOutNoSuchNames OBJECT-TYPE
766
"The total number of SNMP PDUs which were generated
767
by the SNMP protocol entity and for which the value
768
of the error-status was `noSuchName'."
771
snmpOutBadValues OBJECT-TYPE
776
"The total number of SNMP PDUs which were generated
777
by the SNMP protocol entity and for which the value
778
of the error-status field was `badValue'."
781
-- { snmp 23 } is not used
783
snmpOutGenErrs OBJECT-TYPE
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 `genErr'."
793
snmpOutGetRequests OBJECT-TYPE
798
"The total number of SNMP Get-Request PDUs which
799
have been generated by the SNMP protocol entity."
802
snmpOutGetNexts OBJECT-TYPE
807
"The total number of SNMP Get-Next PDUs which have
808
been generated by the SNMP protocol entity."
811
snmpOutSetRequests OBJECT-TYPE
816
"The total number of SNMP Set-Request PDUs which
817
have been generated by the SNMP protocol entity."
820
snmpOutGetResponses OBJECT-TYPE
825
"The total number of SNMP Get-Response PDUs which
826
have been generated by the SNMP protocol entity."
829
snmpOutTraps OBJECT-TYPE
834
"The total number of SNMP Trap PDUs which have
835
been generated by the SNMP protocol entity."
838
snmpObsoleteGroup OBJECT-GROUP
839
OBJECTS { snmpOutPkts, snmpInTooBigs, snmpInNoSuchNames,
840
snmpInBadValues, snmpInReadOnlys, snmpInGenErrs,
841
snmpInTotalReqVars, snmpInTotalSetVars,
842
snmpInGetRequests, snmpInGetNexts, snmpInSetRequests,
843
snmpInGetResponses, snmpInTraps, snmpOutTooBigs,
844
snmpOutNoSuchNames, snmpOutBadValues,
845
snmpOutGenErrs, snmpOutGetRequests, snmpOutGetNexts,
846
snmpOutSetRequests, snmpOutGetResponses, snmpOutTraps
850
"A collection of objects from RFC 1213 made obsolete
852
::= { snmpMIBGroups 10 }
added
removed
mibs/SNMPv2-MIB.txt
