1 SNMPv2-MIB DEFINITIONS ::= BEGIN
4 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
5 TimeTicks, Counter32, snmpModules, mib-2
7 DisplayString, TestAndIncr, TimeStamp
12 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
15 snmpMIB MODULE-IDENTITY
16 LAST-UPDATED "200210160000Z"
17 ORGANIZATION "IETF SNMPv3 Working Group"
19 "WG-EMail: snmpv3@lists.tislabs.com
20 Subscribe: snmpv3-request@lists.tislabs.com
23 Network Associates Laboratories
24 postal: 15204 Omega Drive, Suite 300
25 Rockville, MD 20850-4601
27 EMail: mundy@tislabs.com
28 phone: +1 301 947-7107
30 Co-Chair: David Harrington
32 postal: 35 Industrial Way
34 Rochester, NH 03866-5005
36 EMail: dbh@enterasys.com
37 phone: +1 603 337-2614
41 postal: 2141 North First Street
44 EMail: randy_presuhn@bmc.com
45 phone: +1 408 546-1006"
47 "The MIB module for SNMP entities.
49 Copyright (C) The Internet Society (2002). This
50 version of this MIB module is part of RFC 3418;
51 see the RFC itself for full legal notices.
53 REVISION "200210160000Z"
55 "This revision of this MIB module was published as
57 REVISION "199511090000Z"
62 "This revision of this MIB module was published as
64 REVISION "199304010000Z"
66 "The initial revision of this MIB module was published
70 snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 }
72 -- ::= { snmpMIBObjects 1 } this OID is obsolete
73 -- ::= { snmpMIBObjects 2 } this OID is obsolete
74 -- ::= { snmpMIBObjects 3 } this OID is obsolete
78 -- a collection of objects common to all managed systems.
80 system OBJECT IDENTIFIER ::= { mib-2 1 }
83 SYNTAX DisplayString (SIZE (0..255))
87 "A textual description of the entity. This value should
88 include the full name and version identification of
89 the system's hardware type, software operating-system,
90 and networking software."
93 sysObjectID OBJECT-TYPE
94 SYNTAX OBJECT IDENTIFIER
98 "The vendor's authoritative identification of the
99 network management subsystem contained in the entity.
100 This value is allocated within the SMI enterprises
101 subtree (1.3.6.1.4.1) and provides an easy and
102 unambiguous means for determining `what kind of box' is
103 being managed. For example, if vendor `Flintstones,
104 Inc.' was assigned the subtree 1.3.6.1.4.1.424242,
105 it could assign the identifier 1.3.6.1.4.1.424242.1.1
106 to its `Fred Router'."
109 sysUpTime OBJECT-TYPE
117 "The time (in hundredths of a second) since the
118 network management portion of the system was last
122 sysContact OBJECT-TYPE
123 SYNTAX DisplayString (SIZE (0..255))
124 MAX-ACCESS read-write
127 "The textual identification of the contact person for
128 this managed node, together with information on how
129 to contact this person. If no contact information is
130 known, the value is the zero-length string."
134 SYNTAX DisplayString (SIZE (0..255))
135 MAX-ACCESS read-write
138 "An administratively-assigned name for this managed
139 node. By convention, this is the node's fully-qualified
140 domain name. If the name is unknown, the value is
141 the zero-length string."
144 sysLocation OBJECT-TYPE
145 SYNTAX DisplayString (SIZE (0..255))
146 MAX-ACCESS read-write
149 "The physical location of this node (e.g., 'telephone
150 closet, 3rd floor'). If the location is unknown, the
151 value is the zero-length string."
154 sysServices OBJECT-TYPE
155 SYNTAX INTEGER (0..127)
159 "A value which indicates the set of services that this
160 entity may potentially offer. The value is a sum.
164 This sum initially takes the value zero. Then, for
165 each layer, L, in the range 1 through 7, that this node
166 performs transactions for, 2 raised to (L - 1) is added
167 to the sum. For example, a node which performs only
168 routing functions would have a value of 4 (2^(3-1)).
169 In contrast, a node which is a host offering application
170 services would have a value of 72 (2^(4-1) + 2^(7-1)).
171 Note that in the context of the Internet suite of
172 protocols, values should be calculated accordingly:
175 1 physical (e.g., repeaters)
176 2 datalink/subnetwork (e.g., bridges)
177 3 internet (e.g., supports the IP)
178 4 end-to-end (e.g., supports the TCP)
179 7 applications (e.g., supports the SMTP)
181 For systems including OSI protocols, layers 5 and 6
182 may also be counted."
185 -- object resource information
187 -- a collection of objects which describe the SNMP entity's
188 -- (statically and dynamically configurable) support of
189 -- various MIB modules.
191 sysORLastChange OBJECT-TYPE
196 "The value of sysUpTime at the time of the most recent
197 change in state or value of any instance of sysORID."
200 sysORTable OBJECT-TYPE
201 SYNTAX SEQUENCE OF SysOREntry
202 MAX-ACCESS not-accessible
205 "The (conceptual) table listing the capabilities of
206 the local SNMP application acting as a command
207 responder with respect to various MIB modules.
208 SNMP entities having dynamically-configurable support
209 of MIB modules will have a dynamically-varying number
215 sysOREntry OBJECT-TYPE
217 MAX-ACCESS not-accessible
220 "An entry (conceptual row) in the sysORTable."
224 SysOREntry ::= SEQUENCE {
226 sysORID OBJECT IDENTIFIER,
227 sysORDescr DisplayString,
228 sysORUpTime TimeStamp
231 sysORIndex OBJECT-TYPE
232 SYNTAX INTEGER (1..2147483647)
233 MAX-ACCESS not-accessible
236 "The auxiliary variable used for identifying instances
237 of the columnar objects in the sysORTable."
241 SYNTAX OBJECT IDENTIFIER
245 "An authoritative identification of a capabilities
246 statement with respect to various MIB modules supported
247 by the local SNMP application acting as a command
251 sysORDescr OBJECT-TYPE
256 "A textual description of the capabilities identified
257 by the corresponding instance of sysORID."
260 sysORUpTime OBJECT-TYPE
268 "The value of sysUpTime at the time this conceptual
269 row was last instantiated."
275 -- a collection of objects providing basic instrumentation and
276 -- control of an SNMP entity.
278 snmp OBJECT IDENTIFIER ::= { mib-2 11 }
280 snmpInPkts OBJECT-TYPE
285 "The total number of messages delivered to the SNMP
286 entity from the transport service."
289 snmpInBadVersions OBJECT-TYPE
294 "The total number of SNMP messages which were delivered
295 to the SNMP entity and were for an unsupported SNMP
299 snmpInBadCommunityNames OBJECT-TYPE
304 "The total number of community-based SNMP messages (for
305 example, SNMPv1) delivered to the SNMP entity which
306 used an SNMP community name not known to said entity.
307 Also, implementations which authenticate community-based
308 SNMP messages using check(s) in addition to matching
309 the community name (for example, by also checking
310 whether the message originated from a transport address
311 allowed to use a specified community name) MAY include
312 in this value the number of messages which failed the
313 additional check(s). It is strongly RECOMMENDED that
317 the documentation for any security model which is used
318 to authenticate community-based SNMP messages specify
319 the precise conditions that contribute to this value."
322 snmpInBadCommunityUses OBJECT-TYPE
327 "The total number of community-based SNMP messages (for
328 example, SNMPv1) delivered to the SNMP entity which
329 represented an SNMP operation that was not allowed for
330 the SNMP community named in the message. The precise
331 conditions under which this counter is incremented
332 (if at all) depend on how the SNMP entity implements
333 its access control mechanism and how its applications
334 interact with that access control mechanism. It is
335 strongly RECOMMENDED that the documentation for any
336 access control mechanism which is used to control access
337 to and visibility of MIB instrumentation specify the
338 precise conditions that contribute to this value."
341 snmpInASNParseErrs OBJECT-TYPE
346 "The total number of ASN.1 or BER errors encountered by
347 the SNMP entity when decoding received SNMP messages."
350 snmpEnableAuthenTraps OBJECT-TYPE
351 SYNTAX INTEGER { enabled(1), disabled(2) }
352 MAX-ACCESS read-write
355 "Indicates whether the SNMP entity is permitted to
356 generate authenticationFailure traps. The value of this
357 object overrides any configuration information; as such,
358 it provides a means whereby all authenticationFailure
359 traps may be disabled.
361 Note that it is strongly recommended that this object
362 be stored in non-volatile memory so that it remains
363 constant across re-initializations of the network
370 snmpSilentDrops OBJECT-TYPE
375 "The total number of Confirmed Class PDUs (such as
376 GetRequest-PDUs, GetNextRequest-PDUs,
377 GetBulkRequest-PDUs, SetRequest-PDUs, and
378 InformRequest-PDUs) delivered to the SNMP entity which
379 were silently dropped because the size of a reply
380 containing an alternate Response Class PDU (such as a
381 Response-PDU) with an empty variable-bindings field
382 was greater than either a local constraint or the
383 maximum message size associated with the originator of
387 snmpProxyDrops OBJECT-TYPE
392 "The total number of Confirmed Class PDUs
393 (such as GetRequest-PDUs, GetNextRequest-PDUs,
394 GetBulkRequest-PDUs, SetRequest-PDUs, and
395 InformRequest-PDUs) delivered to the SNMP entity which
396 were silently dropped because the transmission of
397 the (possibly translated) message to a proxy target
398 failed in a manner (other than a time-out) such that
399 no Response Class PDU (such as a Response-PDU) could
403 -- information for notifications
405 -- a collection of objects which allow the SNMP entity, when
406 -- supporting a notification originator application,
407 -- to be configured to generate SNMPv2-Trap-PDUs.
409 snmpTrap OBJECT IDENTIFIER ::= { snmpMIBObjects 4 }
411 snmpTrapOID OBJECT-TYPE
412 SYNTAX OBJECT IDENTIFIER
413 MAX-ACCESS accessible-for-notify
419 "The authoritative identification of the notification
420 currently being sent. This variable occurs as
421 the second varbind in every SNMPv2-Trap-PDU and
425 -- ::= { snmpTrap 2 } this OID is obsolete
427 snmpTrapEnterprise OBJECT-TYPE
428 SYNTAX OBJECT IDENTIFIER
429 MAX-ACCESS accessible-for-notify
432 "The authoritative identification of the enterprise
433 associated with the trap currently being sent. When an
434 SNMP proxy agent is mapping an RFC1157 Trap-PDU
435 into a SNMPv2-Trap-PDU, this variable occurs as the
439 -- ::= { snmpTrap 4 } this OID is obsolete
444 snmpTraps OBJECT IDENTIFIER ::= { snmpMIBObjects 5 }
446 coldStart NOTIFICATION-TYPE
449 "A coldStart trap signifies that the SNMP entity,
450 supporting a notification originator application, is
451 reinitializing itself and that its configuration may
455 warmStart NOTIFICATION-TYPE
458 "A warmStart trap signifies that the SNMP entity,
459 supporting a notification originator application,
460 is reinitializing itself such that its configuration
464 -- Note the linkDown NOTIFICATION-TYPE ::= { snmpTraps 3 }
465 -- and the linkUp NOTIFICATION-TYPE ::= { snmpTraps 4 }
466 -- are defined in RFC 2863 [RFC2863]
470 authenticationFailure NOTIFICATION-TYPE
473 "An authenticationFailure trap signifies that the SNMP
474 entity has received a protocol message that is not
475 properly authenticated. While all implementations
476 of SNMP entities MAY be capable of generating this
477 trap, the snmpEnableAuthenTraps object indicates
478 whether this trap will be generated."
481 -- Note the egpNeighborLoss notification is defined
482 -- as { snmpTraps 6 } in RFC 1213
486 -- a collection of objects which allow several cooperating
487 -- command generator applications to coordinate their use of the
490 snmpSet OBJECT IDENTIFIER ::= { snmpMIBObjects 6 }
492 snmpSetSerialNo OBJECT-TYPE
494 MAX-ACCESS read-write
497 "An advisory lock used to allow several cooperating
498 command generator applications to coordinate their
499 use of the SNMP set operation.
501 This object is used for coarse-grain coordination.
502 To achieve fine-grain coordination, one or more similar
503 objects might be defined within each MIB group, as
507 -- conformance information
510 OBJECT IDENTIFIER ::= { snmpMIB 2 }
513 OBJECT IDENTIFIER ::= { snmpMIBConformance 1 }
514 snmpMIBGroups OBJECT IDENTIFIER ::= { snmpMIBConformance 2 }
516 -- compliance statements
521 -- ::= { snmpMIBCompliances 1 } this OID is obsolete
522 snmpBasicCompliance MODULE-COMPLIANCE
525 "The compliance statement for SNMPv2 entities which
526 implement the SNMPv2 MIB.
528 This compliance statement is replaced by
529 snmpBasicComplianceRev2."
530 MODULE -- this module
531 MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup,
532 snmpBasicNotificationsGroup }
534 GROUP snmpCommunityGroup
536 "This group is mandatory for SNMPv2 entities which
537 support community-based authentication."
539 ::= { snmpMIBCompliances 2 }
541 snmpBasicComplianceRev2 MODULE-COMPLIANCE
544 "The compliance statement for SNMP entities which
545 implement this MIB module."
546 MODULE -- this module
547 MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup,
548 snmpBasicNotificationsGroup }
550 GROUP snmpCommunityGroup
552 "This group is mandatory for SNMP entities which
553 support community-based authentication."
555 GROUP snmpWarmStartNotificationGroup
557 "This group is mandatory for an SNMP entity which
558 supports command responder applications, and is
559 able to reinitialize itself such that its
560 configuration is unaltered."
562 ::= { snmpMIBCompliances 3 }
564 -- units of conformance
566 -- ::= { snmpMIBGroups 1 } this OID is obsolete
567 -- ::= { snmpMIBGroups 2 } this OID is obsolete
568 -- ::= { snmpMIBGroups 3 } this OID is obsolete
572 -- ::= { snmpMIBGroups 4 } this OID is obsolete
574 snmpGroup OBJECT-GROUP
575 OBJECTS { snmpInPkts,
580 snmpEnableAuthenTraps }
583 "A collection of objects providing basic instrumentation
584 and control of an SNMP entity."
585 ::= { snmpMIBGroups 8 }
587 snmpCommunityGroup OBJECT-GROUP
588 OBJECTS { snmpInBadCommunityNames,
589 snmpInBadCommunityUses }
592 "A collection of objects providing basic instrumentation
593 of a SNMP entity which supports community-based
595 ::= { snmpMIBGroups 9 }
597 snmpSetGroup OBJECT-GROUP
598 OBJECTS { snmpSetSerialNo }
601 "A collection of objects which allow several cooperating
602 command generator applications to coordinate their
603 use of the set operation."
604 ::= { snmpMIBGroups 5 }
606 systemGroup OBJECT-GROUP
607 OBJECTS { sysDescr, sysObjectID, sysUpTime,
608 sysContact, sysName, sysLocation,
610 sysORLastChange, sysORID,
611 sysORUpTime, sysORDescr }
614 "The system group defines objects which are common to all
616 ::= { snmpMIBGroups 6 }
618 snmpBasicNotificationsGroup NOTIFICATION-GROUP
619 NOTIFICATIONS { coldStart, authenticationFailure }
625 "The basic notifications implemented by an SNMP entity
626 supporting command responder applications."
627 ::= { snmpMIBGroups 7 }
629 snmpWarmStartNotificationGroup NOTIFICATION-GROUP
630 NOTIFICATIONS { warmStart }
633 "An additional notification for an SNMP entity supporting
634 command responder applications, if it is able to reinitialize
635 itself such that its configuration is unaltered."
636 ::= { snmpMIBGroups 11 }
638 snmpNotificationGroup OBJECT-GROUP
639 OBJECTS { snmpTrapOID, snmpTrapEnterprise }
642 "These objects are required for entities
643 which support notification originator applications."
644 ::= { snmpMIBGroups 12 }
646 -- definitions in RFC 1213 made obsolete by the inclusion of a
647 -- subset of the snmp group in this MIB
649 snmpOutPkts OBJECT-TYPE
654 "The total number of SNMP Messages which were
655 passed from the SNMP protocol entity to the
659 -- { snmp 7 } is not used
661 snmpInTooBigs OBJECT-TYPE
666 "The total number of SNMP PDUs which were
667 delivered to the SNMP protocol entity and for
668 which the value of the error-status field was
674 snmpInNoSuchNames OBJECT-TYPE
679 "The total number of SNMP PDUs which were
680 delivered to the SNMP protocol entity and for
681 which the value of the error-status field was
685 snmpInBadValues OBJECT-TYPE
690 "The total number of SNMP PDUs which were
691 delivered to the SNMP protocol entity and for
692 which the value of the error-status field was
696 snmpInReadOnlys OBJECT-TYPE
701 "The total number valid SNMP PDUs which were delivered
702 to the SNMP protocol entity and for which the value
703 of the error-status field was `readOnly'. It should
704 be noted that it is a protocol error to generate an
705 SNMP PDU which contains the value `readOnly' in the
706 error-status field, as such this object is provided
707 as a means of detecting incorrect implementations of
711 snmpInGenErrs OBJECT-TYPE
716 "The total number of SNMP PDUs which were delivered
717 to the SNMP protocol entity and for which the value
718 of the error-status field was `genErr'."
721 snmpInTotalReqVars OBJECT-TYPE
729 "The total number of MIB objects which have been
730 retrieved successfully by the SNMP protocol entity
731 as the result of receiving valid SNMP Get-Request
735 snmpInTotalSetVars OBJECT-TYPE
740 "The total number of MIB objects which have been
741 altered successfully by the SNMP protocol entity as
742 the result of receiving valid SNMP Set-Request PDUs."
745 snmpInGetRequests OBJECT-TYPE
750 "The total number of SNMP Get-Request PDUs which
751 have been accepted and processed by the SNMP
755 snmpInGetNexts OBJECT-TYPE
760 "The total number of SNMP Get-Next PDUs which have been
761 accepted and processed by the SNMP protocol entity."
764 snmpInSetRequests OBJECT-TYPE
769 "The total number of SNMP Set-Request PDUs which
770 have been accepted and processed by the SNMP protocol
776 snmpInGetResponses OBJECT-TYPE
781 "The total number of SNMP Get-Response PDUs which
782 have been accepted and processed by the SNMP protocol
786 snmpInTraps OBJECT-TYPE
791 "The total number of SNMP Trap PDUs which have been
792 accepted and processed by the SNMP protocol entity."
795 snmpOutTooBigs OBJECT-TYPE
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 `tooBig.'"
805 snmpOutNoSuchNames OBJECT-TYPE
810 "The total number of SNMP PDUs which were generated
811 by the SNMP protocol entity and for which the value
812 of the error-status was `noSuchName'."
815 snmpOutBadValues OBJECT-TYPE
820 "The total number of SNMP PDUs which were generated
821 by the SNMP protocol entity and for which the value
822 of the error-status field was `badValue'."
827 -- { snmp 23 } is not used
829 snmpOutGenErrs OBJECT-TYPE
834 "The total number of SNMP PDUs which were generated
835 by the SNMP protocol entity and for which the value
836 of the error-status field was `genErr'."
839 snmpOutGetRequests OBJECT-TYPE
844 "The total number of SNMP Get-Request PDUs which
845 have been generated by the SNMP protocol entity."
848 snmpOutGetNexts OBJECT-TYPE
853 "The total number of SNMP Get-Next PDUs which have
854 been generated by the SNMP protocol entity."
857 snmpOutSetRequests OBJECT-TYPE
862 "The total number of SNMP Set-Request PDUs which
863 have been generated by the SNMP protocol entity."
866 snmpOutGetResponses OBJECT-TYPE
871 "The total number of SNMP Get-Response PDUs which
872 have been generated by the SNMP protocol entity."
878 snmpOutTraps OBJECT-TYPE
883 "The total number of SNMP Trap PDUs which have
884 been generated by the SNMP protocol entity."
887 snmpObsoleteGroup OBJECT-GROUP
888 OBJECTS { snmpOutPkts, snmpInTooBigs, snmpInNoSuchNames,
889 snmpInBadValues, snmpInReadOnlys, snmpInGenErrs,
890 snmpInTotalReqVars, snmpInTotalSetVars,
891 snmpInGetRequests, snmpInGetNexts, snmpInSetRequests,
892 snmpInGetResponses, snmpInTraps, snmpOutTooBigs,
893 snmpOutNoSuchNames, snmpOutBadValues,
894 snmpOutGenErrs, snmpOutGetRequests, snmpOutGetNexts,
895 snmpOutSetRequests, snmpOutGetResponses, snmpOutTraps
899 "A collection of objects from RFC 1213 made obsolete
901 ::= { snmpMIBGroups 10 }