idnits 2.17.1 draft-ietf-snmpv3-update-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 404: '... specified community name) MAY include...' RFC 2119 keyword, line 406: '...k(s). It is strongly RECOMMENDED that...' RFC 2119 keyword, line 425: '... strongly RECOMMENDED that the ...' RFC 2119 keyword, line 557: '...of SNMP entities MAY be capable of gen...' RFC 2119 keyword, line 1166: '...cationFailure description from MUST to...' (2 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 991 has weird spacing: '... The previo...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (14 July 2000) is 8681 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC1213' is defined on line 1069, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 2233 (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) -- Possible downref: Non-RFC (?) normative reference: ref. 'RFC-TM' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFC-PROTO' Summary: 15 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Editor of this version: 2 Request for Comments: -MIB R. Presuhn 3 STD: XXX BMC Software, Inc. 4 Obsoletes: 1907 Authors of previous version: 5 Category: Standards Track J. Case 6 SNMP Research, Inc. 7 K. McCloghrie 8 Cisco Systems, Inc. 9 M. Rose 10 Dover Beach Consulting, Inc. 11 S. Waldbusser 12 International Network Services 13 14 July 2000 15 Management Information Base 16 for the 17 Simple Network Management Protocol 18 20 Status of this Memo 22 This document is an Internet-Draft and is in full conformance with 23 all provisions of Section 10 of RFC2026. Internet-Drafts are working 24 documents of the Internet Engineering Task Force (IETF), its areas, 25 and its working groups. Note that other groups may also distribute 26 working documents as Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html 39 Copyright Notice 41 Copyright (C) The Internet Society (2000). All Rights Reserved. 43 Abstract 45 This document defines managed objects which describe the behavior of 46 an SNMP entity. This document obsoletes RFC 1907, Management 47 Information Base for Version 2 of the Simple Network Management 48 Protocol (SNMPv2). 50 Table of Contents 52 1. Introduction ................................................ 3 53 2. The SNMP Management Framework ............................... 3 54 3. Definitions ................................................. 4 55 4. Notice on Intellectual Property ............................. 22 56 5. Acknowledgments ............................................. 22 57 6. Security Considerations ..................................... 24 58 7. References .................................................. 24 59 8. Editor's Address ............................................ 26 60 9. Changes from RFC 1907 ....................................... 26 61 10. Issues ..................................................... 27 62 11. Full Copyright Statement ................................... 28 64 1. Introduction 66 It is the purpose of this document to define managed objects which 67 describe the behavior of an SNMP entity, as defined in the SNMP 68 architecture [RFC2571]. 70 2. The SNMP Management Framework 72 The SNMP Management Framework at the time of this writing consists of 73 five major components: 75 - An overall architecture, described in RFC 2571 [RFC2571]. 77 - Mechanisms for describing and naming objects and events for 78 the purpose of management. The first version of this 79 Structure of Management Information (SMI) is called SMIv1 80 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 81 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, 82 called SMIv2, is described in STD 58, RFC 2578 [RFC2578], 83 STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 85 - Message protocols for transferring management information. 86 The first version of the SNMP message protocol is called 87 SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A 88 second version of the SNMP message protocol, which is not 89 an Internet standards track protocol, is called SNMPv2c and 90 described in RFC 1901 [RFC1901] and RFC -TM [RFC-TM]. The 91 third version of the message protocol is called SNMPv3 and 92 described in RFC -TM [RFC-TM], RFC 2572 [RFC2572] and RFC 93 2574 [RFC2574]. 95 - Protocol operations for accessing management information. 96 The first set of protocol operations and associated PDU 97 formats is described in STD 15, RFC 1157 [RFC1157]. A 98 second set of protocol operations and associated PDU 99 formats is described in RFC -PROTO [RFC-PROTO]. 101 - A set of fundamental applications described in RFC 2573 102 [RFC2573] and the view-based access control mechanism 103 described in RFC 2575 [RFC2575]. 105 A more detailed introduction to the current SNMP Management 106 Framework can be found in RFC 2570 [RFC2570]. 108 Managed objects are accessed via a virtual information store, 109 termed the Management Information Base or MIB. Objects in the 110 MIB are defined using the mechanisms defined in the SMI. 112 This memo specifies a MIB module that is compliant to the SMIv2. 113 A MIB conforming to the SMIv1 can be produced through the 114 appropriate translations. The resulting translated MIB must be 115 semantically equivalent, except where objects or events are 116 omitted because no translation is possible (use of Counter64). 117 Some machine readable information in SMIv2 will be converted 118 into textual descriptions in SMIv1 during the translation 119 process. However, this loss of machine readable information is 120 not considered to change the semantics of the MIB. 122 3. Definitions 124 SNMPv2-MIB DEFINITIONS ::= BEGIN 126 IMPORTS 127 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 128 TimeTicks, Counter32, snmpModules, mib-2 129 FROM SNMPv2-SMI 130 DisplayString, TestAndIncr, TimeStamp 131 FROM SNMPv2-TC 132 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 133 FROM SNMPv2-CONF; 135 snmpMIB MODULE-IDENTITY 136 LAST-UPDATED "200007141730Z" 137 ORGANIZATION "IETF SNMPv3 Working Group" 138 CONTACT-INFO 139 "WG-EMail: snmpv3@tis.com 140 Subscribe: majordomo@tis.com 141 In message body: subscribe snmpv3 143 Chair: Russ Mundy 144 TIS Labs at Network Associates 145 postal: 3060 Washington Rd 146 Glenwood MD 21738 147 USA 148 EMail: mundy@tislabs.com 149 phone: +1 301 854-6889 151 Editor: Randy Presuhn 152 BMC Software, Inc. 153 postal: 2141 North First Street 154 San Jose, CA 95131 155 USA 156 EMail: randy_presuhn@bmc.com 157 phone: +1 408 546-1006" 158 DESCRIPTION 159 "The MIB module for SNMP entities." 161 REVISION "200007141730Z" 162 DESCRIPTION 163 "This revision of this MIB module was published as 164 ." 165 REVISION "199511090000Z" 166 DESCRIPTION 167 "This revision of this MIB module was published as 168 RFC 1907." 169 REVISION "199304010000Z" 170 DESCRIPTION 171 "The initial revision of this MIB module was published 172 as RFC 1450." 173 ::= { snmpModules 1 } 175 snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 } 177 -- ::= { snmpMIBObjects 1 } this OID is obsolete 178 -- ::= { snmpMIBObjects 2 } this OID is obsolete 179 -- ::= { snmpMIBObjects 3 } this OID is obsolete 181 -- the System group 182 -- 183 -- a collection of objects common to all managed systems. 185 system OBJECT IDENTIFIER ::= { mib-2 1 } 187 sysDescr OBJECT-TYPE 188 SYNTAX DisplayString (SIZE (0..255)) 189 MAX-ACCESS read-only 190 STATUS current 191 DESCRIPTION 192 "A textual description of the entity. This value should 193 include the full name and version identification of 194 the system's hardware type, software operating-system, 195 and networking software." 196 ::= { system 1 } 198 sysObjectID OBJECT-TYPE 199 SYNTAX OBJECT IDENTIFIER 200 MAX-ACCESS read-only 201 STATUS current 202 DESCRIPTION 203 "The vendor's authoritative identification of the 204 network management subsystem contained in the entity. 205 This value is allocated within the SMI enterprises 206 subtree (1.3.6.1.4.1) and provides an easy and 207 unambiguous means for determining `what kind of box' is 208 being managed. For example, if vendor `Flintstones, 209 Inc.' was assigned the subtree 1.3.6.1.4.1.424242, 210 it could assign the identifier 1.3.6.1.4.1.424242.1.1 211 to its `Fred Router'." 212 ::= { system 2 } 214 sysUpTime OBJECT-TYPE 215 SYNTAX TimeTicks 216 MAX-ACCESS read-only 217 STATUS current 218 DESCRIPTION 219 "The time (in hundredths of a second) since the 220 network management portion of the system was last 221 re-initialized." 222 ::= { system 3 } 224 sysContact OBJECT-TYPE 225 SYNTAX DisplayString (SIZE (0..255)) 226 MAX-ACCESS read-write 227 STATUS current 228 DESCRIPTION 229 "The textual identification of the contact person for 230 this managed node, together with information on how 231 to contact this person. If no contact information is 232 known, the value is the zero-length string." 233 ::= { system 4 } 235 sysName OBJECT-TYPE 236 SYNTAX DisplayString (SIZE (0..255)) 237 MAX-ACCESS read-write 238 STATUS current 239 DESCRIPTION 240 "An administratively-assigned name for this managed 241 node. By convention, this is the node's fully-qualified 242 domain name. If the name is unknown, the value is 243 the zero-length string." 244 ::= { system 5 } 246 sysLocation OBJECT-TYPE 247 SYNTAX DisplayString (SIZE (0..255)) 248 MAX-ACCESS read-write 249 STATUS current 250 DESCRIPTION 251 "The physical location of this node (e.g., 'telephone 252 closet, 3rd floor'). If the location is unknown, the 253 value is the zero-length string." 254 ::= { system 6 } 256 sysServices OBJECT-TYPE 257 SYNTAX INTEGER (0..127) 258 MAX-ACCESS read-only 259 STATUS current 260 DESCRIPTION 261 "A value which indicates the set of services that this 262 entity may potentially offer. The value is a sum. 263 This sum initially takes the value zero. Then, for 264 each layer, L, in the range 1 through 7, that this node 265 performs transactions for, 2 raised to (L - 1) is added 266 to the sum. For example, a node which performs only 267 routing functions would have a value of 4 (2^(3-1)). 268 In contrast, a node which is a host offering application 269 services would have a value of 72 (2^(4-1) + 2^(7-1)). 270 Note that in the context of the Internet suite of 271 protocols, values should be calculated accordingly: 273 layer functionality 274 1 physical (e.g., repeaters) 275 2 datalink/subnetwork (e.g., bridges) 276 3 internet (e.g., supports the IP) 277 4 end-to-end (e.g., supports the TCP) 278 7 applications (e.g., supports the SMTP) 280 For systems including OSI protocols, layers 5 and 6 281 may also be counted." 282 ::= { system 7 } 284 -- object resource information 285 -- 286 -- a collection of objects which describe the SNMP entity's 287 -- (statically and dynamically configurable) support of 288 -- various MIB modules. 290 sysORLastChange OBJECT-TYPE 291 SYNTAX TimeStamp 292 MAX-ACCESS read-only 293 STATUS current 294 DESCRIPTION 295 "The value of sysUpTime at the time of the most recent 296 change in state or value of any instance of sysORID." 297 ::= { system 8 } 299 sysORTable OBJECT-TYPE 300 SYNTAX SEQUENCE OF SysOREntry 301 MAX-ACCESS not-accessible 302 STATUS current 303 DESCRIPTION 304 "The (conceptual) table listing the capabilities of 305 the local SNMP application acting as a command 306 responder with respect to various MIB modules. 307 SNMP entities having dynamically-configurable support 308 of MIB modules will have a dynamically-varying number 309 of conceptual rows." 310 ::= { system 9 } 312 sysOREntry OBJECT-TYPE 313 SYNTAX SysOREntry 314 MAX-ACCESS not-accessible 315 STATUS current 316 DESCRIPTION 317 "An entry (conceptual row) in the sysORTable." 318 INDEX { sysORIndex } 319 ::= { sysORTable 1 } 321 SysOREntry ::= SEQUENCE { 322 sysORIndex INTEGER, 323 sysORID OBJECT IDENTIFIER, 324 sysORDescr DisplayString, 325 sysORUpTime TimeStamp 326 } 328 sysORIndex OBJECT-TYPE 329 SYNTAX INTEGER (1..2147483647) 330 MAX-ACCESS not-accessible 331 STATUS current 332 DESCRIPTION 333 "The auxiliary variable used for identifying instances 334 of the columnar objects in the sysORTable." 335 ::= { sysOREntry 1 } 337 sysORID OBJECT-TYPE 338 SYNTAX OBJECT IDENTIFIER 339 MAX-ACCESS read-only 340 STATUS current 341 DESCRIPTION 342 "An authoritative identification of a capabilities 343 statement with respect to various MIB modules supported 344 by the local SNMP application acting as a command 345 responder." 346 ::= { sysOREntry 2 } 348 sysORDescr OBJECT-TYPE 349 SYNTAX DisplayString 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "A textual description of the capabilities identified 354 by the corresponding instance of sysORID." 355 ::= { sysOREntry 3 } 357 sysORUpTime OBJECT-TYPE 358 SYNTAX TimeStamp 359 MAX-ACCESS read-only 360 STATUS current 361 DESCRIPTION 362 "The value of sysUpTime at the time this conceptual 363 row was last instantiated." 364 ::= { sysOREntry 4 } 366 -- the SNMP group 367 -- 368 -- a collection of objects providing basic instrumentation and 369 -- control of an SNMP entity. 371 snmp OBJECT IDENTIFIER ::= { mib-2 11 } 373 snmpInPkts OBJECT-TYPE 374 SYNTAX Counter32 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The total number of messages delivered to the SNMP 379 entity from the transport service." 380 ::= { snmp 1 } 382 snmpInBadVersions OBJECT-TYPE 383 SYNTAX Counter32 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The total number of SNMP messages which were delivered 388 to the SNMP entity and were for an unsupported SNMP 389 version." 390 ::= { snmp 3 } 392 snmpInBadCommunityNames OBJECT-TYPE 393 SYNTAX Counter32 394 MAX-ACCESS read-only 395 STATUS current 396 DESCRIPTION 397 "The total number of community-based SNMP messages (for 398 example, SNMPv1) delivered to the SNMP entity which 399 used an SNMP community name not known to said entity. 400 Also, implementations which authenticate community-based 401 SNMP messages using check(s) in addition to matching 402 the community name (for example, by also checking 403 whether the message originated from a transport address 404 allowed to use a specified community name) MAY include 405 in this value the number of messages which failed the 406 additional check(s). It is strongly RECOMMENDED that 407 the documentation for any security model which is used 408 to authenticate community-based SNMP messages specify 409 the precise conditions that contribute to this value." 410 ::= { snmp 4 } 412 snmpInBadCommunityUses OBJECT-TYPE 413 SYNTAX Counter32 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The total number of community-based SNMP messages (for 418 example, SNMPv1) delivered to the SNMP entity which 419 represented an SNMP operation that was not allowed for 420 the SNMP community named in the message. The precise 421 conditions under which this counter is incremented 422 (if at all) depend on how the SNMP entity implements 423 its access control mechanism and how its applications 424 interact with that access control mechanism. It is 425 strongly RECOMMENDED that the documentation for any 426 access control mechanism which is used to control access 427 to and visibility of MIB instrumentation specify the 428 precise conditions that contribute to this value." 429 ::= { snmp 5 } 431 snmpInASNParseErrs OBJECT-TYPE 432 SYNTAX Counter32 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "The total number of ASN.1 or BER errors encountered by 437 the SNMP entity when decoding received SNMP messages." 438 ::= { snmp 6 } 440 snmpEnableAuthenTraps OBJECT-TYPE 441 SYNTAX INTEGER { enabled(1), disabled(2) } 442 MAX-ACCESS read-write 443 STATUS current 444 DESCRIPTION 445 "Indicates whether the SNMP entity is permitted to 446 generate authenticationFailure traps. The value of this 447 object overrides any configuration information; as such, 448 it provides a means whereby all authenticationFailure 449 traps may be disabled. 451 Note that it is strongly recommended that this object 452 be stored in non-volatile memory so that it remains 453 constant across re-initializations of the network 454 management system." 455 ::= { snmp 30 } 457 snmpSilentDrops OBJECT-TYPE 458 SYNTAX Counter32 459 MAX-ACCESS read-only 460 STATUS current 461 DESCRIPTION 462 "The total number of Confirmed Class PDUs (such as 463 GetRequest-PDUs, GetNextRequest-PDUs, 464 GetBulkRequest-PDUs, SetRequest-PDUs, and 465 InformRequest-PDUs) delivered to the SNMP entity which 466 were silently dropped because the size of a reply 467 containing an alternate Response Class PDU (such as a 468 Response-PDU) with an empty variable-bindings field 469 was greater than either a local constraint or the 470 maximum message size associated with the originator of 471 the request." 472 ::= { snmp 31 } 474 snmpProxyDrops OBJECT-TYPE 475 SYNTAX Counter32 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "The total number of Confirmed Class PDUs 480 (such as GetRequest-PDUs, GetNextRequest-PDUs, 481 GetBulkRequest-PDUs, SetRequest-PDUs, and 482 InformRequest-PDUs) delivered to the SNMP entity which 483 were silently dropped because the transmission of 484 the (possibly translated) message to a proxy target 485 failed in a manner (other than a time-out) such that 486 no Response Class PDU (such as a Response-PDU) could 487 be returned." 488 ::= { snmp 32 } 490 -- information for notifications 491 -- 492 -- a collection of objects which allow the SNMP entity, when 493 -- supporting a notification originator application, 494 -- to be configured to generate SNMPv2-Trap-PDUs. 496 snmpTrap OBJECT IDENTIFIER ::= { snmpMIBObjects 4 } 498 snmpTrapOID OBJECT-TYPE 499 SYNTAX OBJECT IDENTIFIER 500 MAX-ACCESS accessible-for-notify 501 STATUS current 502 DESCRIPTION 503 "The authoritative identification of the notification 504 currently being sent. This variable occurs as 505 the second varbind in every SNMPv2-Trap-PDU and 506 InformRequest-PDU." 507 ::= { snmpTrap 1 } 509 -- ::= { snmpTrap 2 } this OID is obsolete 511 snmpTrapEnterprise OBJECT-TYPE 512 SYNTAX OBJECT IDENTIFIER 513 MAX-ACCESS accessible-for-notify 514 STATUS current 515 DESCRIPTION 516 "The authoritative identification of the enterprise 517 associated with the trap currently being sent. When an 518 SNMP proxy agent is mapping an RFC1157 Trap-PDU 519 into a SNMPv2-Trap-PDU, this variable occurs as the 520 last varbind." 521 ::= { snmpTrap 3 } 523 -- ::= { snmpTrap 4 } this OID is obsolete 525 -- well-known traps 527 snmpTraps OBJECT IDENTIFIER ::= { snmpMIBObjects 5 } 529 coldStart NOTIFICATION-TYPE 530 STATUS current 531 DESCRIPTION 532 "A coldStart trap signifies that the SNMP entity, 533 supporting a notification originator application, is 534 reinitializing itself and that its configuration may 535 have been altered." 536 ::= { snmpTraps 1 } 538 warmStart NOTIFICATION-TYPE 539 STATUS current 540 DESCRIPTION 541 "A warmStart trap signifies that the SNMP entity, 542 supporting a notification originator application, 543 is reinitializing itself such that its configuration 544 is unaltered." 545 ::= { snmpTraps 2 } 547 -- Note the linkDown NOTIFICATION-TYPE ::= { snmpTraps 3 } 548 -- and the linkUp NOTIFICATION-TYPE ::= { snmpTraps 4 } 549 -- are defined in RFC 2233 [RFC2233] 551 authenticationFailure NOTIFICATION-TYPE 552 STATUS current 553 DESCRIPTION 554 "An authenticationFailure trap signifies that the SNMP 555 entity has received a protocol message that is not 556 properly authenticated. While all implementations 557 of SNMP entities MAY be capable of generating this 558 trap, the snmpEnableAuthenTraps object indicates 559 whether this trap will be generated." 560 ::= { snmpTraps 5 } 562 -- Note the egpNeighborLoss notification is defined 563 -- as { snmpTraps 6 } in RFC 1213 565 -- the set group 566 -- 567 -- a collection of objects which allow several cooperating 568 -- command generator applications to coordinate their use of the 569 -- set operation. 571 snmpSet OBJECT IDENTIFIER ::= { snmpMIBObjects 6 } 573 snmpSetSerialNo OBJECT-TYPE 574 SYNTAX TestAndIncr 575 MAX-ACCESS read-write 576 STATUS current 577 DESCRIPTION 578 "An advisory lock used to allow several cooperating 579 command generator applications to coordinate their 580 use of the SNMP set operation. 582 This object is used for coarse-grain coordination. 583 To achieve fine-grain coordination, one or more similar 584 objects might be defined within each MIB group, as 585 appropriate." 586 ::= { snmpSet 1 } 588 -- conformance information 590 snmpMIBConformance 591 OBJECT IDENTIFIER ::= { snmpMIB 2 } 593 snmpMIBCompliances 594 OBJECT IDENTIFIER ::= { snmpMIBConformance 1 } 595 snmpMIBGroups OBJECT IDENTIFIER ::= { snmpMIBConformance 2 } 597 -- compliance statements 599 -- ::= { snmpMIBCompliances 1 } this OID is obsolete 601 snmpBasicCompliance MODULE-COMPLIANCE 602 STATUS current 603 DESCRIPTION 604 "The compliance statement for SNMP entities which 605 implement this MIB module." 606 MODULE -- this module 607 MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup, 608 snmpBasicNotificationsGroup } 610 GROUP snmpCommunityGroup 611 DESCRIPTION 612 "This group is mandatory for SNMP entities which 613 support community-based authentication." 615 ::= { snmpMIBCompliances 2 } 617 -- units of conformance 619 -- ::= { snmpMIBGroups 1 } this OID is obsolete 620 -- ::= { snmpMIBGroups 2 } this OID is obsolete 621 -- ::= { snmpMIBGroups 3 } this OID is obsolete 622 -- ::= { snmpMIBGroups 4 } this OID is obsolete 624 snmpGroup OBJECT-GROUP 625 OBJECTS { snmpInPkts, 626 snmpInBadVersions, 627 snmpInASNParseErrs, 628 snmpSilentDrops, 629 snmpProxyDrops, 630 snmpEnableAuthenTraps } 631 STATUS current 632 DESCRIPTION 633 "A collection of objects providing basic instrumentation 634 and control of an SNMP entity." 635 ::= { snmpMIBGroups 8 } 637 snmpCommunityGroup OBJECT-GROUP 638 OBJECTS { snmpInBadCommunityNames, 639 snmpInBadCommunityUses } 640 STATUS current 641 DESCRIPTION 642 "A collection of objects providing basic instrumentation 643 of a SNMP entity which supports community-based 644 authentication." 645 ::= { snmpMIBGroups 9 } 647 snmpSetGroup OBJECT-GROUP 648 OBJECTS { snmpSetSerialNo } 649 STATUS current 650 DESCRIPTION 651 "A collection of objects which allow several cooperating 652 command generator applications to coordinate their 653 use of the set operation." 654 ::= { snmpMIBGroups 5 } 656 systemGroup OBJECT-GROUP 657 OBJECTS { sysDescr, sysObjectID, sysUpTime, 658 sysContact, sysName, sysLocation, 659 sysServices, 660 sysORLastChange, sysORID, 661 sysORUpTime, sysORDescr } 662 STATUS current 663 DESCRIPTION 664 "The system group defines objects which are common to all 665 managed systems." 666 ::= { snmpMIBGroups 6 } 668 snmpBasicNotificationsGroup NOTIFICATION-GROUP 669 NOTIFICATIONS { coldStart, authenticationFailure } 670 STATUS current 671 DESCRIPTION 672 "The two notifications which an SNMP entity 673 supporting notification originator applications 674 is required to implement." 675 ::= { snmpMIBGroups 7 } 677 snmpAdditionalNotificationsGroup NOTIFICATION-GROUP 678 NOTIFICATIONS { warmStart } 679 STATUS current 680 DESCRIPTION 681 "The notifications which an SNMP entity 682 supporting notification originator applications 683 is required to implement if it is able to 684 reinitialize itself such that its configuration 685 is unaltered." 686 ::= { snmpMIBGroups 11 } 688 notificationGroup OBJECT-GROUP 689 OBJECTS { snmpTrapOID, snmpTrapEnterprise } 690 STATUS current 691 DESCRIPTION 692 "These objects are required for entities 693 which support notification originator applications." 694 ::= { snmpMIBGroups 12 } 696 -- definitions in RFC 1213 made obsolete by the inclusion of a 697 -- subset of the snmp group in this MIB 698 snmpOutPkts OBJECT-TYPE 699 SYNTAX Counter32 700 MAX-ACCESS read-only 701 STATUS obsolete 702 DESCRIPTION 703 "The total number of SNMP Messages which were 704 passed from the SNMP protocol entity to the 705 transport service." 706 ::= { snmp 2 } 708 -- { snmp 7 } is not used 710 snmpInTooBigs OBJECT-TYPE 711 SYNTAX Counter32 712 MAX-ACCESS read-only 713 STATUS obsolete 714 DESCRIPTION 715 "The total number of SNMP PDUs which were 716 delivered to the SNMP protocol entity and for 717 which the value of the error-status field was 718 `tooBig'." 719 ::= { snmp 8 } 721 snmpInNoSuchNames OBJECT-TYPE 722 SYNTAX Counter32 723 MAX-ACCESS read-only 724 STATUS obsolete 725 DESCRIPTION 726 "The total number of SNMP PDUs which were 727 delivered to the SNMP protocol entity and for 728 which the value of the error-status field was 729 `noSuchName'." 730 ::= { snmp 9 } 732 snmpInBadValues OBJECT-TYPE 733 SYNTAX Counter32 734 MAX-ACCESS read-only 735 STATUS obsolete 736 DESCRIPTION 737 "The total number of SNMP PDUs which were 738 delivered to the SNMP protocol entity and for 739 which the value of the error-status field was 740 `badValue'." 741 ::= { snmp 10 } 743 snmpInReadOnlys OBJECT-TYPE 744 SYNTAX Counter32 745 MAX-ACCESS read-only 746 STATUS obsolete 747 DESCRIPTION 748 "The total number valid SNMP PDUs which were delivered 749 to the SNMP protocol entity and for which the value 750 of the error-status field was `readOnly'. It should 751 be noted that it is a protocol error to generate an 752 SNMP PDU which contains the value `readOnly' in the 753 error-status field, as such this object is provided 754 as a means of detecting incorrect implementations of 755 the SNMP." 756 ::= { snmp 11 } 758 snmpInGenErrs OBJECT-TYPE 759 SYNTAX Counter32 760 MAX-ACCESS read-only 761 STATUS obsolete 762 DESCRIPTION 763 "The total number of SNMP PDUs which were delivered 764 to the SNMP protocol entity and for which the value 765 of the error-status field was `genErr'." 766 ::= { snmp 12 } 768 snmpInTotalReqVars OBJECT-TYPE 769 SYNTAX Counter32 770 MAX-ACCESS read-only 771 STATUS obsolete 772 DESCRIPTION 773 "The total number of MIB objects which have been 774 retrieved successfully by the SNMP protocol entity 775 as the result of receiving valid SNMP Get-Request 776 and Get-Next PDUs." 777 ::= { snmp 13 } 779 snmpInTotalSetVars OBJECT-TYPE 780 SYNTAX Counter32 781 MAX-ACCESS read-only 782 STATUS obsolete 783 DESCRIPTION 784 "The total number of MIB objects which have been 785 altered successfully by the SNMP protocol entity as 786 the result of receiving valid SNMP Set-Request PDUs." 787 ::= { snmp 14 } 789 snmpInGetRequests OBJECT-TYPE 790 SYNTAX Counter32 791 MAX-ACCESS read-only 792 STATUS obsolete 793 DESCRIPTION 794 "The total number of SNMP Get-Request PDUs which 795 have been accepted and processed by the SNMP 796 protocol entity." 797 ::= { snmp 15 } 799 snmpInGetNexts OBJECT-TYPE 800 SYNTAX Counter32 801 MAX-ACCESS read-only 802 STATUS obsolete 803 DESCRIPTION 804 "The total number of SNMP Get-Next PDUs which have been 805 accepted and processed by the SNMP protocol entity." 806 ::= { snmp 16 } 808 snmpInSetRequests OBJECT-TYPE 809 SYNTAX Counter32 810 MAX-ACCESS read-only 811 STATUS obsolete 812 DESCRIPTION 813 "The total number of SNMP Set-Request PDUs which 814 have been accepted and processed by the SNMP protocol 815 entity." 816 ::= { snmp 17 } 818 snmpInGetResponses OBJECT-TYPE 819 SYNTAX Counter32 820 MAX-ACCESS read-only 821 STATUS obsolete 822 DESCRIPTION 823 "The total number of SNMP Get-Response PDUs which 824 have been accepted and processed by the SNMP protocol 825 entity." 826 ::= { snmp 18 } 828 snmpInTraps OBJECT-TYPE 829 SYNTAX Counter32 830 MAX-ACCESS read-only 831 STATUS obsolete 832 DESCRIPTION 833 "The total number of SNMP Trap PDUs which have been 834 accepted and processed by the SNMP protocol entity." 835 ::= { snmp 19 } 837 snmpOutTooBigs OBJECT-TYPE 838 SYNTAX Counter32 839 MAX-ACCESS read-only 840 STATUS obsolete 841 DESCRIPTION 842 "The total number of SNMP PDUs which were generated 843 by the SNMP protocol entity and for which the value 844 of the error-status field was `tooBig.'" 845 ::= { snmp 20 } 847 snmpOutNoSuchNames OBJECT-TYPE 848 SYNTAX Counter32 849 MAX-ACCESS read-only 850 STATUS obsolete 851 DESCRIPTION 852 "The total number of SNMP PDUs which were generated 853 by the SNMP protocol entity and for which the value 854 of the error-status was `noSuchName'." 855 ::= { snmp 21 } 857 snmpOutBadValues OBJECT-TYPE 858 SYNTAX Counter32 859 MAX-ACCESS read-only 860 STATUS obsolete 861 DESCRIPTION 862 "The total number of SNMP PDUs which were generated 863 by the SNMP protocol entity and for which the value 864 of the error-status field was `badValue'." 865 ::= { snmp 22 } 867 -- { snmp 23 } is not used 869 snmpOutGenErrs OBJECT-TYPE 870 SYNTAX Counter32 871 MAX-ACCESS read-only 872 STATUS obsolete 873 DESCRIPTION 874 "The total number of SNMP PDUs which were generated 875 by the SNMP protocol entity and for which the value 876 of the error-status field was `genErr'." 877 ::= { snmp 24 } 879 snmpOutGetRequests OBJECT-TYPE 880 SYNTAX Counter32 881 MAX-ACCESS read-only 882 STATUS obsolete 883 DESCRIPTION 884 "The total number of SNMP Get-Request PDUs which 885 have been generated by the SNMP protocol entity." 886 ::= { snmp 25 } 888 snmpOutGetNexts OBJECT-TYPE 889 SYNTAX Counter32 890 MAX-ACCESS read-only 891 STATUS obsolete 892 DESCRIPTION 893 "The total number of SNMP Get-Next PDUs which have 894 been generated by the SNMP protocol entity." 895 ::= { snmp 26 } 897 snmpOutSetRequests OBJECT-TYPE 898 SYNTAX Counter32 899 MAX-ACCESS read-only 900 STATUS obsolete 901 DESCRIPTION 902 "The total number of SNMP Set-Request PDUs which 903 have been generated by the SNMP protocol entity." 904 ::= { snmp 27 } 906 snmpOutGetResponses OBJECT-TYPE 907 SYNTAX Counter32 908 MAX-ACCESS read-only 909 STATUS obsolete 910 DESCRIPTION 911 "The total number of SNMP Get-Response PDUs which 912 have been generated by the SNMP protocol entity." 913 ::= { snmp 28 } 915 snmpOutTraps OBJECT-TYPE 916 SYNTAX Counter32 917 MAX-ACCESS read-only 918 STATUS obsolete 919 DESCRIPTION 920 "The total number of SNMP Trap PDUs which have 921 been generated by the SNMP protocol entity." 922 ::= { snmp 29 } 924 snmpObsoleteGroup OBJECT-GROUP 925 OBJECTS { snmpOutPkts, snmpInTooBigs, snmpInNoSuchNames, 926 snmpInBadValues, snmpInReadOnlys, snmpInGenErrs, 927 snmpInTotalReqVars, snmpInTotalSetVars, 928 snmpInGetRequests, snmpInGetNexts, snmpInSetRequests, 929 snmpInGetResponses, snmpInTraps, snmpOutTooBigs, 930 snmpOutNoSuchNames, snmpOutBadValues, 931 snmpOutGenErrs, snmpOutGetRequests, snmpOutGetNexts, 932 snmpOutSetRequests, snmpOutGetResponses, snmpOutTraps 933 } 934 STATUS obsolete 935 DESCRIPTION 936 "A collection of objects from RFC 1213 made obsolete 937 by this MIB module." 938 ::= { snmpMIBGroups 10 } 940 END 942 4. Notice on Intellectual Property 944 The IETF takes no position regarding the validity or scope of any 945 intellectual property or other rights that might be claimed to 946 pertain to the implementation or use of the technology described in 947 this document or the extent to which any license under such rights 948 might or might not be available; neither does it represent that it 949 has made any effort to identify any such rights. Information on the 950 IETF's procedures with respect to rights in standards-track and 951 standards-related documentation can be found in BCP-11. Copies of 952 claims of rights made available for publication and any assurances of 953 licenses to be made available, or the result of an attempt made to 954 obtain a general license or permission for the use of such 955 proprietary rights by implementors or users of this specification can 956 be obtained from the IETF Secretariat. 958 The IETF invites any interested party to bring to its attention any 959 copyrights, patents or patent applications, or other proprietary 960 rights which may cover technology that may be required to practice 961 this standard. Please address the information to the IETF Executive 962 Director. 964 5. Acknowledgments 966 This document is the product of the SNMPv3 Working Group. Some 967 special thanks are in order to the following Working Group members: 969 Randy Bush 970 Jeffrey D. Case 971 Mike Daniele 972 Rob Frye 973 Lauren Heintz 974 Keith McCloghrie 975 Russ Mundy 976 David T. Perkins 977 Randy Presuhn 978 Aleksey Romanov 979 Juergen Schoenwaelder 980 Bert Wijnen 982 This version of the document, edited by Randy Presuhn, was initially 983 based on the work of a design team whose members were: 985 Jeffrey D. Case 986 Keith McCloghrie 987 David T. Perkins 988 Randy Presuhn 989 Juergen Schoenwaelder 991 The previous versions of this document, edited by Keith McCloghrie, 992 was the result of significant work by four major contributors: 994 Jeffrey D. Case 995 Keith McCloghrie 996 Marshall T. Rose 997 Steven Waldbusser 999 Additionally, the contributions of the SNMPv2 Working Group to the 1000 previous versions are also acknowledged. In particular, a special 1001 thanks is extended for the contributions of: 1003 Alexander I. Alten 1004 Dave Arneson 1005 Uri Blumenthal 1006 Doug Book 1007 Kim Curran 1008 Jim Galvin 1009 Maria Greene 1010 Iain Hanson 1011 Dave Harrington 1012 Nguyen Hien 1013 Jeff Johnson 1014 Michael Kornegay 1015 Deirdre Kostick 1016 David Levi 1017 Daniel Mahoney 1018 Bob Natale 1019 Brian O'Keefe 1020 Andrew Pearson 1021 Dave Perkins 1022 Randy Presuhn 1023 Aleksey Romanov 1024 Shawn Routhier 1025 Jon Saperia 1026 Juergen Schoenwaelder 1027 Bob Stewart 1028 Kaj Tesink 1029 Glenn Waters 1030 Bert Wijnen 1032 6. Security Considerations 1034 There are a number of management objects defined in this MIB that 1035 have a MAX-ACCESS clause of read-write. Such objects may be 1036 considered sensitive or vulnerable in some network environments. The 1037 support for SET operations in a non-secure environment without proper 1038 protection can have a negative effect on network operations. 1040 SNMPv1 by itself is not a secure environment. Even if the network 1041 itself is secure (for example by using IPSec), even then, there is no 1042 control as to who on the secure network is allowed to access and 1043 GET/SET (read/change) the objects in this MIB. 1045 It is recommended that the implementors consider the security 1046 features as provided by the SNMPv3 framework. Specifically, the use 1047 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1048 based Access Control Model RFC 2575 [RFC2575] is recommended. 1050 It is then a customer/user responsibility to ensure that the SNMP 1051 entity giving access to an instance of this MIB, is properly 1052 configured to give access to the objects only to those principals 1053 (users) that have legitimate rights to indeed GET or SET (change) 1054 them. 1056 7. References 1058 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 1059 Identification of Management Information for TCP/IP-based 1060 Internets", STD 16, RFC 1155, May 1990. 1062 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1063 "Simple Network Management Protocol", STD 15, RFC 1157, 1064 May 1990. 1066 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 1067 STD 16, RFC 1212, March 1991. 1069 [RFC1213] McCloghrie, K., and M. Rose, "Management Information Base 1070 for Network Management of TCP/IP-based internets: MIB- 1071 II", STD 16, RFC 1213, March 1991. 1073 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 1074 the SNMP", RFC 1215, March 1991. 1076 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1077 "Introduction to Community-based SNMPv2", RFC 1901, 1078 January 1996. 1080 [RFC2233] McCloghrie, K., and F. Kastenholz, "The Interfaces Group 1081 MIB using SMIv2", RFC 2233, November 1997. 1083 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1084 "Introduction to Version 3 of the Internet-standard 1085 Network Management Framework", RFC 2570, April 1999. 1087 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1088 Architecture for Describing SNMP Management Frameworks", 1089 RFC 2571, April 1999. 1091 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1092 "Message Processing and Dispatching for the Simple 1093 Network Management Protocol (SNMP)", RFC 2572, April 1094 1999. 1096 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1097 Applications", RFC 2573, April 1999. 1099 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1100 (USM) for version 3 of the Simple Network Management 1101 Protocol (SNMPv3)", RFC 2574, April 1999. 1103 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1104 Access Control Model (VACM) for the Simple Network 1105 Management Protocol (SNMP)", RFC 2575, April 1999. 1107 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1108 Rose, M., and S. Waldbusser, "Structure of Management 1109 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1110 1999. 1112 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1113 Rose, M., and S. Waldbusser, "Textual Conventions for 1114 SMIv2", STD 58, RFC 2579, April 1999. 1116 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1117 Rose, M., and S. Waldbusser, "Conformance Statements for 1118 SMIv2", STD 58, RFC 2580, April 1999. 1120 [RFC-TM] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. 1121 Waldbusser, "Transport Mappings for the Simple Network 1122 Management Protocol", 1123 , July 2000. 1125 [RFC-PROTO] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. 1126 Waldbusser, "Protocol Operations for the Simple Network 1127 Management Protocol", 1128 , July 2000. 1130 8. Editor's Address 1132 Randy Presuhn 1133 BMC Software, Inc. 1134 2141 North First Street 1135 San Jose, CA 95131 1136 USA 1138 Phone: +1 408 546 1006 1139 EMail: randy_presuhn@bmc.com 1141 9. Changes from RFC 1907 1143 These are the changes from RFC 1907: 1145 - Corrected typo in copyright statement; 1147 - Updated copyright date; 1149 - Updated with new editor's name and contact information; 1151 - Cosmetic fixes to layout and typography; 1153 - Changed title; 1155 - Replace introduction with current MIB boilerplate; 1157 - Updated references; 1159 - Fixed typo in sysORUpTime; 1161 - Re-worded description of snmpSilentDrops; 1163 - Updated reference to RFC 1573 to 2233; 1164 - Added IPR boilerplate as required by RFC 2026; 1166 - Weakened authenticationFailure description from MUST to 1167 MAY, clarified that it pertains to all SNMP entities; 1169 - Clarified descriptions of snmpInBadCommunityNames and 1170 snmpInBadCommunityUses; 1172 - Updated module-identity and contact information; 1174 - Updated the acknowledgements section; 1176 - Replaced references to "manager role", "agent role" and 1177 "SNMPv2 entity" with appropriate terms from RFC 2571; 1179 - Updated document headers and footers; 1181 - Added security considerations, based on current 1182 recommendations for MIB modules. 1184 - Added NOTIFICATION-GROUP and OBJECT-GROUP constructs for 1185 NOTIFICATION-TYPEs and OBJECT-TYPEs that were left 1186 unreferenced in RFC 1907. 1188 - Fixed typos in sysServices DESCRIPTION. 1190 - Changed description of snmpProxyDrops to use terms from 1191 architecture. 1193 - Changed value used in example for sysObjectID. 1195 - Added an abstract. 1197 10. Issues 1199 This section is to be deleted when it is time to publish this 1200 document as an RFC. The issue labels are the same as those used in 1201 the on-line issues list at 1202 ftp://amethyst.bmc.com/pub/snmpv3/Update567/rfc1907/index.html 1204 1907-01 Done; title changed. 1206 1907-02 Done; replaced introduction with current MIB 1207 boilerplate. 1209 1907-03 Done; resolution was to make no change. 1211 1907-04 Done; replaced occurrences of "SNMPv2 entity", 1212 "manager role", and "agent role" with appropriate 1213 terms from architecture. 1215 1907-05 Done; typo fixed. 1217 1907-06 Done; resolution was to make no change. 1219 1907-07 Done; description of snmpSilentDrops updated. 1221 1907-08 Done; reference to RFC 1573 replaced with reference to 1222 RFC 2233. 1224 1907-09 Done; resolution was to make no change. 1226 1907-10 Done; resolution was to make no change. 1228 1907-11 Done; resolution was to make no change. 1230 1907-12 Done; added security considerations based on 1231 recommended text from http://www.ops.ietf.org/ 1233 1907-13 Done; references and acknowledgements updated. 1235 1907-14 Done; IPR boilerplate aligned with RFC 2026. 1237 1907-15 Done; authenticationFailure weakened to MAY but 1238 permitted for all protocol versions. 1240 1907-16 Done; resolution was to make no change. 1242 1907-17 Done; clarified descriptions of 1243 snmpInBadCommunityNames and snmpInBadCommunityUses. 1245 1907-18 Done; resolution was to make no change. 1247 1907-19 Done; conformance material added. 1249 1907-20 Done; resolution was to make no change. 1251 11. Full Copyright Statement 1253 Copyright (C) The Internet Society (2000). All Rights Reserved. 1255 This document and translations of it may be copied and furnished to 1256 others, and derivative works that comment on or otherwise explain it 1257 or assist in its implementation may be prepared, copied, published 1258 and distributed, in whole or in part, without restriction of any 1259 kind, provided that the above copyright notice and this paragraph are 1260 included on all such copies and derivative works. However, this 1261 document itself may not be modified in any way, such as by removing 1262 the copyright notice or references to the Internet Society or other 1263 Internet organizations, except as needed for the purpose of 1264 developing Internet standards in which case the procedures for 1265 copyrights defined in the Internet Standards process must be 1266 followed, or as required to translate it into languages other than 1267 English. 1269 The limited permissions granted above are perpetual and will not be 1270 revoked by the Internet Society or its successors or assigns. 1272 This document and the information contained herein is provided on an 1273 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1274 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1275 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1276 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1277 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.