2 <!DOCTYPE smi SYSTEM "http://www.ibr.cs.tu-bs.de/projects/nmrg/smi.dtd">
4 <!-- This module has been generated by smidump 0.4.5. Do not edit. -->
6 <smi xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
7 xsi:noNamespaceSchemaLocation="http://www.ibr.cs.tu-bs.de/projects/nmrg/smi.xsd">
8 <module name="SNMPv2-MIB" language="SMIv2">
10 IETF SNMPv3 Working Group
13 WG-EMail: snmpv3@lists.tislabs.com
14 Subscribe: snmpv3-request@lists.tislabs.com
17 Network Associates Laboratories
18 postal: 15204 Omega Drive, Suite 300
19 Rockville, MD 20850-4601
21 EMail: mundy@tislabs.com
22 phone: +1 301 947-7107
24 Co-Chair: David Harrington
26 postal: 35 Industrial Way
28 Rochester, NH 03866-5005
30 EMail: dbh@enterasys.com
31 phone: +1 603 337-2614
35 postal: 2141 North First Street
38 EMail: randy_presuhn@bmc.com
39 phone: +1 408 546-1006
42 The MIB module for SNMP entities.
44 Copyright (C) The Internet Society (2002). This
45 version of this MIB module is part of RFC 3418;
46 see the RFC itself for full legal notices.
48 <revision date="2002-10-16 00:00">
50 This revision of this MIB module was published as
54 <revision date="1995-11-09 00:00">
56 This revision of this MIB module was published as
60 <revision date="1993-04-01 00:00">
62 The initial revision of this MIB module was published
66 <identity node="snmpMIB"/>
70 <import module="SNMPv2-SMI" name="MODULE-IDENTITY"/>
71 <import module="SNMPv2-SMI" name="OBJECT-TYPE"/>
72 <import module="SNMPv2-SMI" name="NOTIFICATION-TYPE"/>
73 <import module="SNMPv2-SMI" name="TimeTicks"/>
74 <import module="SNMPv2-SMI" name="Counter32"/>
75 <import module="SNMPv2-SMI" name="snmpModules"/>
76 <import module="SNMPv2-SMI" name="mib-2"/>
77 <import module="SNMPv2-TC" name="DisplayString"/>
78 <import module="SNMPv2-TC" name="TestAndIncr"/>
79 <import module="SNMPv2-TC" name="TimeStamp"/>
80 <import module="SNMPv2-CONF" name="MODULE-COMPLIANCE"/>
81 <import module="SNMPv2-CONF" name="OBJECT-GROUP"/>
82 <import module="SNMPv2-CONF" name="NOTIFICATION-GROUP"/>
86 <node name="system" oid="1.3.6.1.2.1.1">
88 <scalar name="sysDescr" oid="1.3.6.1.2.1.1.1" status="current">
90 <typedef basetype="OctetString">
91 <parent module="SNMPv2-TC" name="DisplayString"/>
92 <range min="0" max="255"/>
95 <access>readonly</access>
97 A textual description of the entity. This value should
98 include the full name and version identification of
99 the system's hardware type, software operating-system,
100 and networking software.
103 <scalar name="sysObjectID" oid="1.3.6.1.2.1.1.2" status="current">
105 <type module="" name="ObjectIdentifier"/>
107 <access>readonly</access>
109 The vendor's authoritative identification of the
110 network management subsystem contained in the entity.
111 This value is allocated within the SMI enterprises
112 subtree (1.3.6.1.4.1) and provides an easy and
113 unambiguous means for determining `what kind of box' is
114 being managed. For example, if vendor `Flintstones,
115 Inc.' was assigned the subtree 1.3.6.1.4.1.424242,
116 it could assign the identifier 1.3.6.1.4.1.424242.1.1
117 to its `Fred Router'.
120 <scalar name="sysUpTime" oid="1.3.6.1.2.1.1.3" status="current">
122 <type module="SNMPv2-SMI" name="TimeTicks"/>
124 <access>readonly</access>
126 The time (in hundredths of a second) since the
127 network management portion of the system was last
131 <scalar name="sysContact" oid="1.3.6.1.2.1.1.4" status="current">
133 <typedef basetype="OctetString">
134 <parent module="SNMPv2-TC" name="DisplayString"/>
135 <range min="0" max="255"/>
138 <access>readwrite</access>
140 The textual identification of the contact person for
141 this managed node, together with information on how
142 to contact this person. If no contact information is
143 known, the value is the zero-length string.
146 <scalar name="sysName" oid="1.3.6.1.2.1.1.5" status="current">
148 <typedef basetype="OctetString">
149 <parent module="SNMPv2-TC" name="DisplayString"/>
150 <range min="0" max="255"/>
153 <access>readwrite</access>
155 An administratively-assigned name for this managed
156 node. By convention, this is the node's fully-qualified
157 domain name. If the name is unknown, the value is
158 the zero-length string.
161 <scalar name="sysLocation" oid="1.3.6.1.2.1.1.6" status="current">
163 <typedef basetype="OctetString">
164 <parent module="SNMPv2-TC" name="DisplayString"/>
165 <range min="0" max="255"/>
168 <access>readwrite</access>
170 The physical location of this node (e.g., 'telephone
171 closet, 3rd floor'). If the location is unknown, the
172 value is the zero-length string.
175 <scalar name="sysServices" oid="1.3.6.1.2.1.1.7" status="current">
177 <typedef basetype="Integer32">
178 <range min="0" max="127"/>
181 <access>readonly</access>
183 A value which indicates the set of services that this
184 entity may potentially offer. The value is a sum.
188 This sum initially takes the value zero. Then, for
189 each layer, L, in the range 1 through 7, that this node
190 performs transactions for, 2 raised to (L - 1) is added
191 to the sum. For example, a node which performs only
192 routing functions would have a value of 4 (2^(3-1)).
193 In contrast, a node which is a host offering application
194 services would have a value of 72 (2^(4-1) + 2^(7-1)).
195 Note that in the context of the Internet suite of
196 protocols, values should be calculated accordingly:
199 1 physical (e.g., repeaters)
200 2 datalink/subnetwork (e.g., bridges)
201 3 internet (e.g., supports the IP)
202 4 end-to-end (e.g., supports the TCP)
203 7 applications (e.g., supports the SMTP)
205 For systems including OSI protocols, layers 5 and 6
209 <scalar name="sysORLastChange" oid="1.3.6.1.2.1.1.8" status="current">
211 <type module="SNMPv2-TC" name="TimeStamp"/>
213 <access>readonly</access>
215 The value of sysUpTime at the time of the most recent
216 change in state or value of any instance of sysORID.
219 <table name="sysORTable" oid="1.3.6.1.2.1.1.9" status="current">
221 The (conceptual) table listing the capabilities of
222 the local SNMP application acting as a command
223 responder with respect to various MIB modules.
224 SNMP entities having dynamically-configurable support
225 of MIB modules will have a dynamically-varying number
228 <row name="sysOREntry" oid="1.3.6.1.2.1.1.9.1" status="current">
230 <index module="SNMPv2-MIB" name="sysORIndex"/>
233 An entry (conceptual row) in the sysORTable.
235 <column name="sysORIndex" oid="1.3.6.1.2.1.1.9.1.1" status="current">
237 <typedef basetype="Integer32">
238 <range min="1" max="2147483647"/>
241 <access>noaccess</access>
243 The auxiliary variable used for identifying instances
244 of the columnar objects in the sysORTable.
247 <column name="sysORID" oid="1.3.6.1.2.1.1.9.1.2" status="current">
249 <type module="" name="ObjectIdentifier"/>
251 <access>readonly</access>
253 An authoritative identification of a capabilities
254 statement with respect to various MIB modules supported
255 by the local SNMP application acting as a command
259 <column name="sysORDescr" oid="1.3.6.1.2.1.1.9.1.3" status="current">
261 <type module="SNMPv2-TC" name="DisplayString"/>
263 <access>readonly</access>
265 A textual description of the capabilities identified
266 by the corresponding instance of sysORID.
269 <column name="sysORUpTime" oid="1.3.6.1.2.1.1.9.1.4" status="current">
271 <type module="SNMPv2-TC" name="TimeStamp"/>
273 <access>readonly</access>
275 The value of sysUpTime at the time this conceptual
276 row was last instantiated.
281 <node name="snmp" oid="1.3.6.1.2.1.11">
283 <scalar name="snmpInPkts" oid="1.3.6.1.2.1.11.1" status="current">
285 <type module="SNMPv2-SMI" name="Counter32"/>
287 <access>readonly</access>
289 The total number of messages delivered to the SNMP
290 entity from the transport service.
293 <scalar name="snmpOutPkts" oid="1.3.6.1.2.1.11.2" status="obsolete">
295 <type module="SNMPv2-SMI" name="Counter32"/>
297 <access>readonly</access>
299 The total number of SNMP Messages which were
300 passed from the SNMP protocol entity to the
304 <scalar name="snmpInBadVersions" oid="1.3.6.1.2.1.11.3" status="current">
306 <type module="SNMPv2-SMI" name="Counter32"/>
308 <access>readonly</access>
310 The total number of SNMP messages which were delivered
311 to the SNMP entity and were for an unsupported SNMP
315 <scalar name="snmpInBadCommunityNames" oid="1.3.6.1.2.1.11.4" status="current">
317 <type module="SNMPv2-SMI" name="Counter32"/>
319 <access>readonly</access>
321 The total number of community-based SNMP messages (for
322 example, SNMPv1) delivered to the SNMP entity which
323 used an SNMP community name not known to said entity.
324 Also, implementations which authenticate community-based
325 SNMP messages using check(s) in addition to matching
326 the community name (for example, by also checking
327 whether the message originated from a transport address
328 allowed to use a specified community name) MAY include
329 in this value the number of messages which failed the
330 additional check(s). It is strongly RECOMMENDED that
334 the documentation for any security model which is used
335 to authenticate community-based SNMP messages specify
336 the precise conditions that contribute to this value.
339 <scalar name="snmpInBadCommunityUses" oid="1.3.6.1.2.1.11.5" status="current">
341 <type module="SNMPv2-SMI" name="Counter32"/>
343 <access>readonly</access>
345 The total number of community-based SNMP messages (for
346 example, SNMPv1) delivered to the SNMP entity which
347 represented an SNMP operation that was not allowed for
348 the SNMP community named in the message. The precise
349 conditions under which this counter is incremented
350 (if at all) depend on how the SNMP entity implements
351 its access control mechanism and how its applications
352 interact with that access control mechanism. It is
353 strongly RECOMMENDED that the documentation for any
354 access control mechanism which is used to control access
355 to and visibility of MIB instrumentation specify the
356 precise conditions that contribute to this value.
359 <scalar name="snmpInASNParseErrs" oid="1.3.6.1.2.1.11.6" status="current">
361 <type module="SNMPv2-SMI" name="Counter32"/>
363 <access>readonly</access>
365 The total number of ASN.1 or BER errors encountered by
366 the SNMP entity when decoding received SNMP messages.
369 <scalar name="snmpInTooBigs" oid="1.3.6.1.2.1.11.8" status="obsolete">
371 <type module="SNMPv2-SMI" name="Counter32"/>
373 <access>readonly</access>
375 The total number of SNMP PDUs which were
376 delivered to the SNMP protocol entity and for
377 which the value of the error-status field was
381 <scalar name="snmpInNoSuchNames" oid="1.3.6.1.2.1.11.9" status="obsolete">
383 <type module="SNMPv2-SMI" name="Counter32"/>
385 <access>readonly</access>
387 The total number of SNMP PDUs which were
388 delivered to the SNMP protocol entity and for
389 which the value of the error-status field was
393 <scalar name="snmpInBadValues" oid="1.3.6.1.2.1.11.10" status="obsolete">
395 <type module="SNMPv2-SMI" name="Counter32"/>
397 <access>readonly</access>
399 The total number of SNMP PDUs which were
400 delivered to the SNMP protocol entity and for
401 which the value of the error-status field was
405 <scalar name="snmpInReadOnlys" oid="1.3.6.1.2.1.11.11" status="obsolete">
407 <type module="SNMPv2-SMI" name="Counter32"/>
409 <access>readonly</access>
411 The total number valid SNMP PDUs which were delivered
412 to the SNMP protocol entity and for which the value
413 of the error-status field was `readOnly'. It should
414 be noted that it is a protocol error to generate an
415 SNMP PDU which contains the value `readOnly' in the
416 error-status field, as such this object is provided
417 as a means of detecting incorrect implementations of
421 <scalar name="snmpInGenErrs" oid="1.3.6.1.2.1.11.12" status="obsolete">
423 <type module="SNMPv2-SMI" name="Counter32"/>
425 <access>readonly</access>
427 The total number of SNMP PDUs which were delivered
428 to the SNMP protocol entity and for which the value
429 of the error-status field was `genErr'.
432 <scalar name="snmpInTotalReqVars" oid="1.3.6.1.2.1.11.13" status="obsolete">
434 <type module="SNMPv2-SMI" name="Counter32"/>
436 <access>readonly</access>
438 The total number of MIB objects which have been
439 retrieved successfully by the SNMP protocol entity
440 as the result of receiving valid SNMP Get-Request
444 <scalar name="snmpInTotalSetVars" oid="1.3.6.1.2.1.11.14" status="obsolete">
446 <type module="SNMPv2-SMI" name="Counter32"/>
448 <access>readonly</access>
450 The total number of MIB objects which have been
451 altered successfully by the SNMP protocol entity as
452 the result of receiving valid SNMP Set-Request PDUs.
455 <scalar name="snmpInGetRequests" oid="1.3.6.1.2.1.11.15" status="obsolete">
457 <type module="SNMPv2-SMI" name="Counter32"/>
459 <access>readonly</access>
461 The total number of SNMP Get-Request PDUs which
462 have been accepted and processed by the SNMP
466 <scalar name="snmpInGetNexts" oid="1.3.6.1.2.1.11.16" status="obsolete">
468 <type module="SNMPv2-SMI" name="Counter32"/>
470 <access>readonly</access>
472 The total number of SNMP Get-Next PDUs which have been
473 accepted and processed by the SNMP protocol entity.
476 <scalar name="snmpInSetRequests" oid="1.3.6.1.2.1.11.17" status="obsolete">
478 <type module="SNMPv2-SMI" name="Counter32"/>
480 <access>readonly</access>
482 The total number of SNMP Set-Request PDUs which
483 have been accepted and processed by the SNMP protocol
487 <scalar name="snmpInGetResponses" oid="1.3.6.1.2.1.11.18" status="obsolete">
489 <type module="SNMPv2-SMI" name="Counter32"/>
491 <access>readonly</access>
493 The total number of SNMP Get-Response PDUs which
494 have been accepted and processed by the SNMP protocol
498 <scalar name="snmpInTraps" oid="1.3.6.1.2.1.11.19" status="obsolete">
500 <type module="SNMPv2-SMI" name="Counter32"/>
502 <access>readonly</access>
504 The total number of SNMP Trap PDUs which have been
505 accepted and processed by the SNMP protocol entity.
508 <scalar name="snmpOutTooBigs" oid="1.3.6.1.2.1.11.20" status="obsolete">
510 <type module="SNMPv2-SMI" name="Counter32"/>
512 <access>readonly</access>
514 The total number of SNMP PDUs which were generated
515 by the SNMP protocol entity and for which the value
516 of the error-status field was `tooBig.'
519 <scalar name="snmpOutNoSuchNames" oid="1.3.6.1.2.1.11.21" status="obsolete">
521 <type module="SNMPv2-SMI" name="Counter32"/>
523 <access>readonly</access>
525 The total number of SNMP PDUs which were generated
526 by the SNMP protocol entity and for which the value
527 of the error-status was `noSuchName'.
530 <scalar name="snmpOutBadValues" oid="1.3.6.1.2.1.11.22" status="obsolete">
532 <type module="SNMPv2-SMI" name="Counter32"/>
534 <access>readonly</access>
536 The total number of SNMP PDUs which were generated
537 by the SNMP protocol entity and for which the value
538 of the error-status field was `badValue'.
541 <scalar name="snmpOutGenErrs" oid="1.3.6.1.2.1.11.24" status="obsolete">
543 <type module="SNMPv2-SMI" name="Counter32"/>
545 <access>readonly</access>
547 The total number of SNMP PDUs which were generated
548 by the SNMP protocol entity and for which the value
549 of the error-status field was `genErr'.
552 <scalar name="snmpOutGetRequests" oid="1.3.6.1.2.1.11.25" status="obsolete">
554 <type module="SNMPv2-SMI" name="Counter32"/>
556 <access>readonly</access>
558 The total number of SNMP Get-Request PDUs which
559 have been generated by the SNMP protocol entity.
562 <scalar name="snmpOutGetNexts" oid="1.3.6.1.2.1.11.26" status="obsolete">
564 <type module="SNMPv2-SMI" name="Counter32"/>
566 <access>readonly</access>
568 The total number of SNMP Get-Next PDUs which have
569 been generated by the SNMP protocol entity.
572 <scalar name="snmpOutSetRequests" oid="1.3.6.1.2.1.11.27" status="obsolete">
574 <type module="SNMPv2-SMI" name="Counter32"/>
576 <access>readonly</access>
578 The total number of SNMP Set-Request PDUs which
579 have been generated by the SNMP protocol entity.
582 <scalar name="snmpOutGetResponses" oid="1.3.6.1.2.1.11.28" status="obsolete">
584 <type module="SNMPv2-SMI" name="Counter32"/>
586 <access>readonly</access>
588 The total number of SNMP Get-Response PDUs which
589 have been generated by the SNMP protocol entity.
592 <scalar name="snmpOutTraps" oid="1.3.6.1.2.1.11.29" status="obsolete">
594 <type module="SNMPv2-SMI" name="Counter32"/>
596 <access>readonly</access>
598 The total number of SNMP Trap PDUs which have
599 been generated by the SNMP protocol entity.
602 <scalar name="snmpEnableAuthenTraps" oid="1.3.6.1.2.1.11.30" status="current">
604 <typedef basetype="Enumeration">
605 <namednumber name="enabled" number="1"/>
606 <namednumber name="disabled" number="2"/>
609 <access>readwrite</access>
611 Indicates whether the SNMP entity is permitted to
612 generate authenticationFailure traps. The value of this
613 object overrides any configuration information; as such,
614 it provides a means whereby all authenticationFailure
615 traps may be disabled.
617 Note that it is strongly recommended that this object
618 be stored in non-volatile memory so that it remains
619 constant across re-initializations of the network
623 <scalar name="snmpSilentDrops" oid="1.3.6.1.2.1.11.31" status="current">
625 <type module="SNMPv2-SMI" name="Counter32"/>
627 <access>readonly</access>
629 The total number of Confirmed Class PDUs (such as
630 GetRequest-PDUs, GetNextRequest-PDUs,
631 GetBulkRequest-PDUs, SetRequest-PDUs, and
632 InformRequest-PDUs) delivered to the SNMP entity which
633 were silently dropped because the size of a reply
634 containing an alternate Response Class PDU (such as a
635 Response-PDU) with an empty variable-bindings field
636 was greater than either a local constraint or the
637 maximum message size associated with the originator of
641 <scalar name="snmpProxyDrops" oid="1.3.6.1.2.1.11.32" status="current">
643 <type module="SNMPv2-SMI" name="Counter32"/>
645 <access>readonly</access>
647 The total number of Confirmed Class PDUs
648 (such as GetRequest-PDUs, GetNextRequest-PDUs,
649 GetBulkRequest-PDUs, SetRequest-PDUs, and
650 InformRequest-PDUs) delivered to the SNMP entity which
651 were silently dropped because the transmission of
652 the (possibly translated) message to a proxy target
653 failed in a manner (other than a time-out) such that
654 no Response Class PDU (such as a Response-PDU) could
658 <node name="snmpMIB" oid="1.3.6.1.6.3.1" status="current">
660 <node name="snmpMIBObjects" oid="1.3.6.1.6.3.1.1">
662 <node name="snmpTrap" oid="1.3.6.1.6.3.1.1.4">
664 <scalar name="snmpTrapOID" oid="1.3.6.1.6.3.1.1.4.1" status="current">
666 <type module="" name="ObjectIdentifier"/>
668 <access>notifyonly</access>
670 The authoritative identification of the notification
671 currently being sent. This variable occurs as
672 the second varbind in every SNMPv2-Trap-PDU and
676 <scalar name="snmpTrapEnterprise" oid="1.3.6.1.6.3.1.1.4.3" status="current">
678 <type module="" name="ObjectIdentifier"/>
680 <access>notifyonly</access>
682 The authoritative identification of the enterprise
683 associated with the trap currently being sent. When an
684 SNMP proxy agent is mapping an RFC1157 Trap-PDU
685 into a SNMPv2-Trap-PDU, this variable occurs as the
689 <node name="snmpTraps" oid="1.3.6.1.6.3.1.1.5">
691 <node name="snmpSet" oid="1.3.6.1.6.3.1.1.6">
693 <scalar name="snmpSetSerialNo" oid="1.3.6.1.6.3.1.1.6.1" status="current">
695 <type module="SNMPv2-TC" name="TestAndIncr"/>
697 <access>readwrite</access>
699 An advisory lock used to allow several cooperating
700 command generator applications to coordinate their
701 use of the SNMP set operation.
703 This object is used for coarse-grain coordination.
704 To achieve fine-grain coordination, one or more similar
705 objects might be defined within each MIB group, as
709 <node name="snmpMIBConformance" oid="1.3.6.1.6.3.1.2">
711 <node name="snmpMIBCompliances" oid="1.3.6.1.6.3.1.2.1">
713 <node name="snmpMIBGroups" oid="1.3.6.1.6.3.1.2.2">
718 <notification name="coldStart" oid="1.3.6.1.6.3.1.1.5.1" status="current">
722 A coldStart trap signifies that the SNMP entity,
723 supporting a notification originator application, is
724 reinitializing itself and that its configuration may
728 <notification name="warmStart" oid="1.3.6.1.6.3.1.1.5.2" status="current">
732 A warmStart trap signifies that the SNMP entity,
733 supporting a notification originator application,
734 is reinitializing itself such that its configuration
738 <notification name="authenticationFailure" oid="1.3.6.1.6.3.1.1.5.5" status="current">
742 An authenticationFailure trap signifies that the SNMP
743 entity has received a protocol message that is not
744 properly authenticated. While all implementations
745 of SNMP entities MAY be capable of generating this
746 trap, the snmpEnableAuthenTraps object indicates
747 whether this trap will be generated.
753 <group name="snmpSetGroup" oid="1.3.6.1.6.3.1.2.2.5" status="current">
755 <member module="SNMPv2-MIB" name="snmpSetSerialNo"/>
758 A collection of objects which allow several cooperating
759 command generator applications to coordinate their
760 use of the set operation.
763 <group name="systemGroup" oid="1.3.6.1.6.3.1.2.2.6" status="current">
765 <member module="SNMPv2-MIB" name="sysDescr"/>
766 <member module="SNMPv2-MIB" name="sysObjectID"/>
767 <member module="SNMPv2-MIB" name="sysUpTime"/>
768 <member module="SNMPv2-MIB" name="sysContact"/>
769 <member module="SNMPv2-MIB" name="sysName"/>
770 <member module="SNMPv2-MIB" name="sysLocation"/>
771 <member module="SNMPv2-MIB" name="sysServices"/>
772 <member module="SNMPv2-MIB" name="sysORLastChange"/>
773 <member module="SNMPv2-MIB" name="sysORID"/>
774 <member module="SNMPv2-MIB" name="sysORUpTime"/>
775 <member module="SNMPv2-MIB" name="sysORDescr"/>
778 The system group defines objects which are common to all
782 <group name="snmpBasicNotificationsGroup" oid="1.3.6.1.6.3.1.2.2.7" status="current">
784 <member module="SNMPv2-MIB" name="coldStart"/>
785 <member module="SNMPv2-MIB" name="authenticationFailure"/>
788 The basic notifications implemented by an SNMP entity
789 supporting command responder applications.
792 <group name="snmpGroup" oid="1.3.6.1.6.3.1.2.2.8" status="current">
794 <member module="SNMPv2-MIB" name="snmpInPkts"/>
795 <member module="SNMPv2-MIB" name="snmpInBadVersions"/>
796 <member module="SNMPv2-MIB" name="snmpInASNParseErrs"/>
797 <member module="SNMPv2-MIB" name="snmpSilentDrops"/>
798 <member module="SNMPv2-MIB" name="snmpProxyDrops"/>
799 <member module="SNMPv2-MIB" name="snmpEnableAuthenTraps"/>
802 A collection of objects providing basic instrumentation
803 and control of an SNMP entity.
806 <group name="snmpCommunityGroup" oid="1.3.6.1.6.3.1.2.2.9" status="current">
808 <member module="SNMPv2-MIB" name="snmpInBadCommunityNames"/>
809 <member module="SNMPv2-MIB" name="snmpInBadCommunityUses"/>
812 A collection of objects providing basic instrumentation
813 of a SNMP entity which supports community-based
817 <group name="snmpObsoleteGroup" oid="1.3.6.1.6.3.1.2.2.10" status="obsolete">
819 <member module="SNMPv2-MIB" name="snmpOutPkts"/>
820 <member module="SNMPv2-MIB" name="snmpInTooBigs"/>
821 <member module="SNMPv2-MIB" name="snmpInNoSuchNames"/>
822 <member module="SNMPv2-MIB" name="snmpInBadValues"/>
823 <member module="SNMPv2-MIB" name="snmpInReadOnlys"/>
824 <member module="SNMPv2-MIB" name="snmpInGenErrs"/>
825 <member module="SNMPv2-MIB" name="snmpInTotalReqVars"/>
826 <member module="SNMPv2-MIB" name="snmpInTotalSetVars"/>
827 <member module="SNMPv2-MIB" name="snmpInGetRequests"/>
828 <member module="SNMPv2-MIB" name="snmpInGetNexts"/>
829 <member module="SNMPv2-MIB" name="snmpInSetRequests"/>
830 <member module="SNMPv2-MIB" name="snmpInGetResponses"/>
831 <member module="SNMPv2-MIB" name="snmpInTraps"/>
832 <member module="SNMPv2-MIB" name="snmpOutTooBigs"/>
833 <member module="SNMPv2-MIB" name="snmpOutNoSuchNames"/>
834 <member module="SNMPv2-MIB" name="snmpOutBadValues"/>
835 <member module="SNMPv2-MIB" name="snmpOutGenErrs"/>
836 <member module="SNMPv2-MIB" name="snmpOutGetRequests"/>
837 <member module="SNMPv2-MIB" name="snmpOutGetNexts"/>
838 <member module="SNMPv2-MIB" name="snmpOutSetRequests"/>
839 <member module="SNMPv2-MIB" name="snmpOutGetResponses"/>
840 <member module="SNMPv2-MIB" name="snmpOutTraps"/>
843 A collection of objects from RFC 1213 made obsolete
847 <group name="snmpWarmStartNotificationGroup" oid="1.3.6.1.6.3.1.2.2.11" status="current">
849 <member module="SNMPv2-MIB" name="warmStart"/>
852 An additional notification for an SNMP entity supporting
853 command responder applications, if it is able to reinitialize
854 itself such that its configuration is unaltered.
857 <group name="snmpNotificationGroup" oid="1.3.6.1.6.3.1.2.2.12" status="current">
859 <member module="SNMPv2-MIB" name="snmpTrapOID"/>
860 <member module="SNMPv2-MIB" name="snmpTrapEnterprise"/>
863 These objects are required for entities
864 which support notification originator applications.
870 <compliance name="snmpBasicCompliance" oid="1.3.6.1.6.3.1.2.1.2" status="deprecated">
872 The compliance statement for SNMPv2 entities which
873 implement the SNMPv2 MIB.
875 This compliance statement is replaced by
876 snmpBasicComplianceRev2.
879 <mandatory module="SNMPv2-MIB" name="snmpGroup"/>
880 <mandatory module="SNMPv2-MIB" name="snmpSetGroup"/>
881 <mandatory module="SNMPv2-MIB" name="systemGroup"/>
882 <mandatory module="SNMPv2-MIB" name="snmpBasicNotificationsGroup"/>
883 <option module="SNMPv2-MIB" name="snmpCommunityGroup">
885 This group is mandatory for SNMPv2 entities which
886 support community-based authentication.
891 <compliance name="snmpBasicComplianceRev2" oid="1.3.6.1.6.3.1.2.1.3" status="current">
893 The compliance statement for SNMP entities which
894 implement this MIB module.
897 <mandatory module="SNMPv2-MIB" name="snmpGroup"/>
898 <mandatory module="SNMPv2-MIB" name="snmpSetGroup"/>
899 <mandatory module="SNMPv2-MIB" name="systemGroup"/>
900 <mandatory module="SNMPv2-MIB" name="snmpBasicNotificationsGroup"/>
901 <option module="SNMPv2-MIB" name="snmpCommunityGroup">
903 This group is mandatory for SNMP entities which
904 support community-based authentication.
907 <option module="SNMPv2-MIB" name="snmpWarmStartNotificationGroup">
909 This group is mandatory for an SNMP entity which
910 supports command responder applications, and is
911 able to reinitialize itself such that its
912 configuration is unaltered.