2 -- This SMIv2 module has been generated by smidump 0.4.5. Do not edit.
5 SNMPv2-MIB DEFINITIONS ::= BEGIN
8 MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
10 Counter32, Integer32, MODULE-IDENTITY, NOTIFICATION-TYPE,
11 OBJECT-TYPE, TimeTicks, mib-2, snmpModules
13 DisplayString, TestAndIncr, TimeStamp
16 snmpMIB MODULE-IDENTITY
17 LAST-UPDATED "200210160000Z"
19 "IETF SNMPv3 Working Group"
21 "WG-EMail: snmpv3@lists.tislabs.com
22 Subscribe: snmpv3-request@lists.tislabs.com
25 Network Associates Laboratories
26 postal: 15204 Omega Drive, Suite 300
27 Rockville, MD 20850-4601
29 EMail: mundy@tislabs.com
30 phone: +1 301 947-7107
32 Co-Chair: David Harrington
34 postal: 35 Industrial Way
36 Rochester, NH 03866-5005
38 EMail: dbh@enterasys.com
39 phone: +1 603 337-2614
43 postal: 2141 North First Street
46 EMail: randy_presuhn@bmc.com
47 phone: +1 408 546-1006"
49 "The MIB module for SNMP entities.
51 Copyright (C) The Internet Society (2002). This
52 version of this MIB module is part of RFC 3418;
53 see the RFC itself for full legal notices."
54 REVISION "200210160000Z"
56 "This revision of this MIB module was published as
58 REVISION "199511090000Z"
60 "This revision of this MIB module was published as
62 REVISION "199304010000Z"
64 "The initial revision of this MIB module was published
69 system OBJECT IDENTIFIER
73 SYNTAX DisplayString (SIZE(0..255))
77 "A textual description of the entity. This value should
78 include the full name and version identification of
79 the system's hardware type, software operating-system,
80 and networking software."
83 sysObjectID OBJECT-TYPE
84 SYNTAX OBJECT IDENTIFIER
88 "The vendor's authoritative identification of the
89 network management subsystem contained in the entity.
90 This value is allocated within the SMI enterprises
91 subtree (1.3.6.1.4.1) and provides an easy and
92 unambiguous means for determining `what kind of box' is
93 being managed. For example, if vendor `Flintstones,
94 Inc.' was assigned the subtree 1.3.6.1.4.1.424242,
95 it could assign the identifier 1.3.6.1.4.1.424242.1.1
96 to its `Fred Router'."
104 "The time (in hundredths of a second) since the
105 network management portion of the system was last
109 sysContact OBJECT-TYPE
110 SYNTAX DisplayString (SIZE(0..255))
111 MAX-ACCESS read-write
114 "The textual identification of the contact person for
115 this managed node, together with information on how
116 to contact this person. If no contact information is
117 known, the value is the zero-length string."
121 SYNTAX DisplayString (SIZE(0..255))
122 MAX-ACCESS read-write
125 "An administratively-assigned name for this managed
126 node. By convention, this is the node's fully-qualified
127 domain name. If the name is unknown, the value is
128 the zero-length string."
131 sysLocation OBJECT-TYPE
132 SYNTAX DisplayString (SIZE(0..255))
133 MAX-ACCESS read-write
136 "The physical location of this node (e.g., 'telephone
137 closet, 3rd floor'). If the location is unknown, the
138 value is the zero-length string."
141 sysServices OBJECT-TYPE
142 SYNTAX Integer32 (0..127)
146 "A value which indicates the set of services that this
147 entity may potentially offer. The value is a sum.
151 This sum initially takes the value zero. Then, for
152 each layer, L, in the range 1 through 7, that this node
153 performs transactions for, 2 raised to (L - 1) is added
154 to the sum. For example, a node which performs only
155 routing functions would have a value of 4 (2^(3-1)).
156 In contrast, a node which is a host offering application
157 services would have a value of 72 (2^(4-1) + 2^(7-1)).
158 Note that in the context of the Internet suite of
159 protocols, values should be calculated accordingly:
162 1 physical (e.g., repeaters)
163 2 datalink/subnetwork (e.g., bridges)
164 3 internet (e.g., supports the IP)
165 4 end-to-end (e.g., supports the TCP)
166 7 applications (e.g., supports the SMTP)
168 For systems including OSI protocols, layers 5 and 6
169 may also be counted."
172 sysORLastChange OBJECT-TYPE
177 "The value of sysUpTime at the time of the most recent
178 change in state or value of any instance of sysORID."
181 sysORTable OBJECT-TYPE
182 SYNTAX SEQUENCE OF SysOREntry
183 MAX-ACCESS not-accessible
186 "The (conceptual) table listing the capabilities of
187 the local SNMP application acting as a command
188 responder with respect to various MIB modules.
189 SNMP entities having dynamically-configurable support
190 of MIB modules will have a dynamically-varying number
194 sysOREntry OBJECT-TYPE
196 MAX-ACCESS not-accessible
199 "An entry (conceptual row) in the sysORTable."
203 SysOREntry ::= SEQUENCE {
204 sysORIndex Integer32,
205 sysORID OBJECT IDENTIFIER,
206 sysORDescr DisplayString,
207 sysORUpTime TimeStamp
210 sysORIndex OBJECT-TYPE
211 SYNTAX Integer32 (1..2147483647)
212 MAX-ACCESS not-accessible
215 "The auxiliary variable used for identifying instances
216 of the columnar objects in the sysORTable."
220 SYNTAX OBJECT IDENTIFIER
224 "An authoritative identification of a capabilities
225 statement with respect to various MIB modules supported
226 by the local SNMP application acting as a command
230 sysORDescr OBJECT-TYPE
235 "A textual description of the capabilities identified
236 by the corresponding instance of sysORID."
239 sysORUpTime OBJECT-TYPE
244 "The value of sysUpTime at the time this conceptual
245 row was last instantiated."
248 snmp OBJECT IDENTIFIER
251 snmpInPkts OBJECT-TYPE
256 "The total number of messages delivered to the SNMP
257 entity from the transport service."
260 snmpOutPkts OBJECT-TYPE
265 "The total number of SNMP Messages which were
266 passed from the SNMP protocol entity to the
270 snmpInBadVersions OBJECT-TYPE
275 "The total number of SNMP messages which were delivered
276 to the SNMP entity and were for an unsupported SNMP
280 snmpInBadCommunityNames OBJECT-TYPE
285 "The total number of community-based SNMP messages (for
286 example, SNMPv1) delivered to the SNMP entity which
287 used an SNMP community name not known to said entity.
288 Also, implementations which authenticate community-based
289 SNMP messages using check(s) in addition to matching
290 the community name (for example, by also checking
291 whether the message originated from a transport address
292 allowed to use a specified community name) MAY include
293 in this value the number of messages which failed the
294 additional check(s). It is strongly RECOMMENDED that
298 the documentation for any security model which is used
299 to authenticate community-based SNMP messages specify
300 the precise conditions that contribute to this value."
303 snmpInBadCommunityUses OBJECT-TYPE
308 "The total number of community-based SNMP messages (for
309 example, SNMPv1) delivered to the SNMP entity which
310 represented an SNMP operation that was not allowed for
311 the SNMP community named in the message. The precise
312 conditions under which this counter is incremented
313 (if at all) depend on how the SNMP entity implements
314 its access control mechanism and how its applications
315 interact with that access control mechanism. It is
316 strongly RECOMMENDED that the documentation for any
317 access control mechanism which is used to control access
318 to and visibility of MIB instrumentation specify the
319 precise conditions that contribute to this value."
322 snmpInASNParseErrs OBJECT-TYPE
327 "The total number of ASN.1 or BER errors encountered by
328 the SNMP entity when decoding received SNMP messages."
331 snmpInTooBigs OBJECT-TYPE
336 "The total number of SNMP PDUs which were
337 delivered to the SNMP protocol entity and for
338 which the value of the error-status field was
342 snmpInNoSuchNames OBJECT-TYPE
347 "The total number of SNMP PDUs which were
348 delivered to the SNMP protocol entity and for
349 which the value of the error-status field was
353 snmpInBadValues OBJECT-TYPE
358 "The total number of SNMP PDUs which were
359 delivered to the SNMP protocol entity and for
360 which the value of the error-status field was
364 snmpInReadOnlys OBJECT-TYPE
369 "The total number valid SNMP PDUs which were delivered
370 to the SNMP protocol entity and for which the value
371 of the error-status field was `readOnly'. It should
372 be noted that it is a protocol error to generate an
373 SNMP PDU which contains the value `readOnly' in the
374 error-status field, as such this object is provided
375 as a means of detecting incorrect implementations of
379 snmpInGenErrs OBJECT-TYPE
384 "The total number of SNMP PDUs which were delivered
385 to the SNMP protocol entity and for which the value
386 of the error-status field was `genErr'."
389 snmpInTotalReqVars OBJECT-TYPE
394 "The total number of MIB objects which have been
395 retrieved successfully by the SNMP protocol entity
396 as the result of receiving valid SNMP Get-Request
400 snmpInTotalSetVars OBJECT-TYPE
405 "The total number of MIB objects which have been
406 altered successfully by the SNMP protocol entity as
407 the result of receiving valid SNMP Set-Request PDUs."
410 snmpInGetRequests OBJECT-TYPE
415 "The total number of SNMP Get-Request PDUs which
416 have been accepted and processed by the SNMP
420 snmpInGetNexts OBJECT-TYPE
425 "The total number of SNMP Get-Next PDUs which have been
426 accepted and processed by the SNMP protocol entity."
429 snmpInSetRequests OBJECT-TYPE
434 "The total number of SNMP Set-Request PDUs which
435 have been accepted and processed by the SNMP protocol
439 snmpInGetResponses OBJECT-TYPE
444 "The total number of SNMP Get-Response PDUs which
445 have been accepted and processed by the SNMP protocol
449 snmpInTraps OBJECT-TYPE
454 "The total number of SNMP Trap PDUs which have been
455 accepted and processed by the SNMP protocol entity."
458 snmpOutTooBigs OBJECT-TYPE
463 "The total number of SNMP PDUs which were generated
464 by the SNMP protocol entity and for which the value
465 of the error-status field was `tooBig.'"
468 snmpOutNoSuchNames OBJECT-TYPE
473 "The total number of SNMP PDUs which were generated
474 by the SNMP protocol entity and for which the value
475 of the error-status was `noSuchName'."
478 snmpOutBadValues OBJECT-TYPE
483 "The total number of SNMP PDUs which were generated
484 by the SNMP protocol entity and for which the value
485 of the error-status field was `badValue'."
488 snmpOutGenErrs OBJECT-TYPE
493 "The total number of SNMP PDUs which were generated
494 by the SNMP protocol entity and for which the value
495 of the error-status field was `genErr'."
498 snmpOutGetRequests OBJECT-TYPE
503 "The total number of SNMP Get-Request PDUs which
504 have been generated by the SNMP protocol entity."
507 snmpOutGetNexts OBJECT-TYPE
512 "The total number of SNMP Get-Next PDUs which have
513 been generated by the SNMP protocol entity."
516 snmpOutSetRequests OBJECT-TYPE
521 "The total number of SNMP Set-Request PDUs which
522 have been generated by the SNMP protocol entity."
525 snmpOutGetResponses OBJECT-TYPE
530 "The total number of SNMP Get-Response PDUs which
531 have been generated by the SNMP protocol entity."
534 snmpOutTraps OBJECT-TYPE
539 "The total number of SNMP Trap PDUs which have
540 been generated by the SNMP protocol entity."
543 snmpEnableAuthenTraps OBJECT-TYPE
544 SYNTAX INTEGER { enabled(1), disabled(2) }
545 MAX-ACCESS read-write
548 "Indicates whether the SNMP entity is permitted to
549 generate authenticationFailure traps. The value of this
550 object overrides any configuration information; as such,
551 it provides a means whereby all authenticationFailure
552 traps may be disabled.
554 Note that it is strongly recommended that this object
555 be stored in non-volatile memory so that it remains
556 constant across re-initializations of the network
560 snmpSilentDrops OBJECT-TYPE
565 "The total number of Confirmed Class PDUs (such as
566 GetRequest-PDUs, GetNextRequest-PDUs,
567 GetBulkRequest-PDUs, SetRequest-PDUs, and
568 InformRequest-PDUs) delivered to the SNMP entity which
569 were silently dropped because the size of a reply
570 containing an alternate Response Class PDU (such as a
571 Response-PDU) with an empty variable-bindings field
572 was greater than either a local constraint or the
573 maximum message size associated with the originator of
577 snmpProxyDrops OBJECT-TYPE
582 "The total number of Confirmed Class PDUs
583 (such as GetRequest-PDUs, GetNextRequest-PDUs,
584 GetBulkRequest-PDUs, SetRequest-PDUs, and
585 InformRequest-PDUs) delivered to the SNMP entity which
586 were silently dropped because the transmission of
587 the (possibly translated) message to a proxy target
588 failed in a manner (other than a time-out) such that
589 no Response Class PDU (such as a Response-PDU) could
593 snmpMIBObjects OBJECT IDENTIFIER
596 snmpTrap OBJECT IDENTIFIER
597 ::= { snmpMIBObjects 4 }
599 snmpTrapOID OBJECT-TYPE
600 SYNTAX OBJECT IDENTIFIER
601 MAX-ACCESS accessible-for-notify
604 "The authoritative identification of the notification
605 currently being sent. This variable occurs as
606 the second varbind in every SNMPv2-Trap-PDU and
610 snmpTrapEnterprise OBJECT-TYPE
611 SYNTAX OBJECT IDENTIFIER
612 MAX-ACCESS accessible-for-notify
615 "The authoritative identification of the enterprise
616 associated with the trap currently being sent. When an
617 SNMP proxy agent is mapping an RFC1157 Trap-PDU
618 into a SNMPv2-Trap-PDU, this variable occurs as the
622 snmpTraps OBJECT IDENTIFIER
623 ::= { snmpMIBObjects 5 }
625 snmpSet OBJECT IDENTIFIER
626 ::= { snmpMIBObjects 6 }
628 snmpSetSerialNo OBJECT-TYPE
630 MAX-ACCESS read-write
633 "An advisory lock used to allow several cooperating
634 command generator applications to coordinate their
635 use of the SNMP set operation.
637 This object is used for coarse-grain coordination.
638 To achieve fine-grain coordination, one or more similar
639 objects might be defined within each MIB group, as
643 snmpMIBConformance OBJECT IDENTIFIER
646 snmpMIBCompliances OBJECT IDENTIFIER
647 ::= { snmpMIBConformance 1 }
649 snmpMIBGroups OBJECT IDENTIFIER
650 ::= { snmpMIBConformance 2 }
652 coldStart NOTIFICATION-TYPE
655 "A coldStart trap signifies that the SNMP entity,
656 supporting a notification originator application, is
657 reinitializing itself and that its configuration may
661 warmStart NOTIFICATION-TYPE
664 "A warmStart trap signifies that the SNMP entity,
665 supporting a notification originator application,
666 is reinitializing itself such that its configuration
670 authenticationFailure NOTIFICATION-TYPE
673 "An authenticationFailure trap signifies that the SNMP
674 entity has received a protocol message that is not
675 properly authenticated. While all implementations
676 of SNMP entities MAY be capable of generating this
677 trap, the snmpEnableAuthenTraps object indicates
678 whether this trap will be generated."
681 snmpSetGroup OBJECT-GROUP
682 OBJECTS { snmpSetSerialNo }
685 "A collection of objects which allow several cooperating
686 command generator applications to coordinate their
687 use of the set operation."
688 ::= { snmpMIBGroups 5 }
690 systemGroup OBJECT-GROUP
691 OBJECTS { sysDescr, sysObjectID, sysUpTime, sysContact, sysName,
692 sysLocation, sysServices, sysORLastChange, sysORID,
693 sysORUpTime, sysORDescr }
696 "The system group defines objects which are common to all
698 ::= { snmpMIBGroups 6 }
700 snmpBasicNotificationsGroup NOTIFICATION-GROUP
701 NOTIFICATIONS { coldStart, authenticationFailure }
704 "The basic notifications implemented by an SNMP entity
705 supporting command responder applications."
706 ::= { snmpMIBGroups 7 }
708 snmpGroup OBJECT-GROUP
709 OBJECTS { snmpInPkts, snmpInBadVersions, snmpInASNParseErrs,
710 snmpSilentDrops, snmpProxyDrops, snmpEnableAuthenTraps }
713 "A collection of objects providing basic instrumentation
714 and control of an SNMP entity."
715 ::= { snmpMIBGroups 8 }
717 snmpCommunityGroup OBJECT-GROUP
718 OBJECTS { snmpInBadCommunityNames, snmpInBadCommunityUses }
721 "A collection of objects providing basic instrumentation
722 of a SNMP entity which supports community-based
724 ::= { snmpMIBGroups 9 }
726 snmpObsoleteGroup OBJECT-GROUP
727 OBJECTS { snmpOutPkts, snmpInTooBigs, snmpInNoSuchNames,
728 snmpInBadValues, snmpInReadOnlys, snmpInGenErrs,
729 snmpInTotalReqVars, snmpInTotalSetVars,
730 snmpInGetRequests, snmpInGetNexts, snmpInSetRequests,
731 snmpInGetResponses, snmpInTraps, snmpOutTooBigs,
732 snmpOutNoSuchNames, snmpOutBadValues, snmpOutGenErrs,
733 snmpOutGetRequests, snmpOutGetNexts,
734 snmpOutSetRequests, snmpOutGetResponses, snmpOutTraps }
737 "A collection of objects from RFC 1213 made obsolete
739 ::= { snmpMIBGroups 10 }
741 snmpWarmStartNotificationGroup NOTIFICATION-GROUP
742 NOTIFICATIONS { warmStart }
745 "An additional notification for an SNMP entity supporting
746 command responder applications, if it is able to reinitialize
747 itself such that its configuration is unaltered."
748 ::= { snmpMIBGroups 11 }
750 snmpNotificationGroup OBJECT-GROUP
751 OBJECTS { snmpTrapOID, snmpTrapEnterprise }
754 "These objects are required for entities
755 which support notification originator applications."
756 ::= { snmpMIBGroups 12 }
758 snmpBasicCompliance MODULE-COMPLIANCE
761 "The compliance statement for SNMPv2 entities which
762 implement the SNMPv2 MIB.
764 This compliance statement is replaced by
765 snmpBasicComplianceRev2."
767 MODULE -- this module
769 MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup,
770 snmpBasicNotificationsGroup }
772 GROUP snmpCommunityGroup
774 "This group is mandatory for SNMPv2 entities which
775 support community-based authentication."
777 ::= { snmpMIBCompliances 2 }
779 snmpBasicComplianceRev2 MODULE-COMPLIANCE
782 "The compliance statement for SNMP entities which
783 implement this MIB module."
785 MODULE -- this module
787 MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup,
788 snmpBasicNotificationsGroup }
790 GROUP snmpCommunityGroup
792 "This group is mandatory for SNMP entities which
793 support community-based authentication."
795 GROUP snmpWarmStartNotificationGroup
797 "This group is mandatory for an SNMP entity which
798 supports command responder applications, and is
799 able to reinitialize itself such that its
800 configuration is unaltered."
802 ::= { snmpMIBCompliances 3 }
804 END -- end of module SNMPv2-MIB.