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