idnits 2.17.1 draft-ietf-snmpv3-update-mib-03.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 403: '... specified community name) MAY include...' RFC 2119 keyword, line 405: '...k(s). It is strongly RECOMMENDED that...' RFC 2119 keyword, line 424: '... strongly RECOMMENDED that the ...' RFC 2119 keyword, line 556: '...of SNMP entities MAY be capable of gen...' RFC 2119 keyword, line 1165: '...cationFailure description from MUST to...' (2 more instances...) -- The draft header indicates that this document obsoletes RFC1907, but the abstract doesn't seem to directly say this. It does mention RFC1907 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 990 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 (2 June 2000) is 8727 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 1068, 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 (==), 5 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 2 June 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 internet-draft, a work item of the SNMPv3 working group, is 46 intended to obsolete RFC 1907, Management Information Base for 47 Version 2 of the Simple Network Management Protocol (SNMPv2). 49 Table of Contents 51 1. Introduction ................................................ 3 52 2. The SNMP Management Framework ............................... 3 53 3. Definitions ................................................. 4 54 4. Notice on Intellectual Property ............................. 22 55 5. Acknowledgments ............................................. 22 56 6. Security Considerations ..................................... 24 57 7. References .................................................. 24 58 8. Editor's Address ............................................ 26 59 9. Changes from RFC 1907 ....................................... 26 60 10. Issues ..................................................... 27 61 11. Full Copyright Statement ................................... 28 63 1. Introduction 65 It is the purpose of this document to define managed objects which 66 describe the behavior of an SNMP entity, as defined in the SNMP 67 architecture [RFC2571]. 69 2. The SNMP Management Framework 71 The SNMP Management Framework at the time of this writing consists of 72 five major components: 74 - An overall architecture, described in RFC 2571 [RFC2571]. 76 - Mechanisms for describing and naming objects and events for 77 the purpose of management. The first version of this 78 Structure of Management Information (SMI) is called SMIv1 79 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 80 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, 81 called SMIv2, is described in STD 58, RFC 2578 [RFC2578], 82 STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 84 - Message protocols for transferring management information. 85 The first version of the SNMP message protocol is called 86 SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A 87 second version of the SNMP message protocol, which is not 88 an Internet standards track protocol, is called SNMPv2c and 89 described in RFC 1901 [RFC1901] and RFC -TM [RFC-TM]. The 90 third version of the message protocol is called SNMPv3 and 91 described in RFC -TM [RFC-TM], RFC 2572 [RFC2572] and RFC 92 2574 [RFC2574]. 94 - Protocol operations for accessing management information. 95 The first set of protocol operations and associated PDU 96 formats is described in STD 15, RFC 1157 [RFC1157]. A 97 second set of protocol operations and associated PDU 98 formats is described in RFC -PROTO [RFC-PROTO]. 100 - A set of fundamental applications described in RFC 2573 101 [RFC2573] and the view-based access control mechanism 102 described in RFC 2575 [RFC2575]. 104 A more detailed introduction to the current SNMP Management 105 Framework can be found in RFC 2570 [RFC2570]. 107 Managed objects are accessed via a virtual information store, 108 termed the Management Information Base or MIB. Objects in the 109 MIB are defined using the mechanisms defined in the SMI. 111 This memo specifies a MIB module that is compliant to the SMIv2. 112 A MIB conforming to the SMIv1 can be produced through the 113 appropriate translations. The resulting translated MIB must be 114 semantically equivalent, except where objects or events are 115 omitted because no translation is possible (use of Counter64). 116 Some machine readable information in SMIv2 will be converted 117 into textual descriptions in SMIv1 during the translation 118 process. However, this loss of machine readable information is 119 not considered to change the semantics of the MIB. 121 3. Definitions 123 SNMPv2-MIB DEFINITIONS ::= BEGIN 125 IMPORTS 126 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 127 TimeTicks, Counter32, snmpModules, mib-2 128 FROM SNMPv2-SMI 129 DisplayString, TestAndIncr, TimeStamp 130 FROM SNMPv2-TC 131 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 132 FROM SNMPv2-CONF; 134 snmpMIB MODULE-IDENTITY 135 LAST-UPDATED "200006030101Z" 136 ORGANIZATION "IETF SNMPv3 Working Group" 137 CONTACT-INFO 138 "WG-EMail: snmpv3@tis.com 139 Subscribe: majordomo@tis.com 140 In message body: subscribe snmpv3 142 Chair: Russ Mundy 143 TIS Labs at Network Associates 144 postal: 3060 Washington Rd 145 Glenwood MD 21738 146 USA 147 EMail: mundy@tislabs.com 148 phone: +1 301 854-6889 150 Editor: Randy Presuhn 151 BMC Software, Inc. 152 postal: 2141 North First Street 153 San Jose, CA 95131 154 USA 155 EMail: randy_presuhn@bmc.com 156 phone: +1 408 546-1006" 157 DESCRIPTION 158 "The MIB module for SNMP entities." 160 REVISION "200006030101Z" 161 DESCRIPTION 162 "This revision of this MIB module was published as 163 ." 164 REVISION "199511090000Z" 165 DESCRIPTION 166 "This revision of this MIB module was published as 167 RFC 1907." 168 REVISION "199304010000Z" 169 DESCRIPTION 170 "The initial revision of this MIB module was published 171 as RFC 1450." 172 ::= { snmpModules 1 } 174 snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 } 176 -- ::= { snmpMIBObjects 1 } this OID is obsolete 177 -- ::= { snmpMIBObjects 2 } this OID is obsolete 178 -- ::= { snmpMIBObjects 3 } this OID is obsolete 180 -- the System group 181 -- 182 -- a collection of objects common to all managed systems. 184 system OBJECT IDENTIFIER ::= { mib-2 1 } 186 sysDescr OBJECT-TYPE 187 SYNTAX DisplayString (SIZE (0..255)) 188 MAX-ACCESS read-only 189 STATUS current 190 DESCRIPTION 191 "A textual description of the entity. This value should 192 include the full name and version identification of 193 the system's hardware type, software operating-system, 194 and networking software." 195 ::= { system 1 } 197 sysObjectID OBJECT-TYPE 198 SYNTAX OBJECT IDENTIFIER 199 MAX-ACCESS read-only 200 STATUS current 201 DESCRIPTION 202 "The vendor's authoritative identification of the 203 network management subsystem contained in the entity. 204 This value is allocated within the SMI enterprises 205 subtree (1.3.6.1.4.1) and provides an easy and 206 unambiguous means for determining `what kind of box' is 207 being managed. For example, if vendor `Flintstones, 208 Inc.' was assigned the subtree 1.3.6.1.4.1.424242, 209 it could assign the identifier 1.3.6.1.4.1.424242.1.1 210 to its `Fred Router'." 211 ::= { system 2 } 213 sysUpTime OBJECT-TYPE 214 SYNTAX TimeTicks 215 MAX-ACCESS read-only 216 STATUS current 217 DESCRIPTION 218 "The time (in hundredths of a second) since the 219 network management portion of the system was last 220 re-initialized." 221 ::= { system 3 } 223 sysContact OBJECT-TYPE 224 SYNTAX DisplayString (SIZE (0..255)) 225 MAX-ACCESS read-write 226 STATUS current 227 DESCRIPTION 228 "The textual identification of the contact person for 229 this managed node, together with information on how 230 to contact this person. If no contact information is 231 known, the value is the zero-length string." 232 ::= { system 4 } 234 sysName OBJECT-TYPE 235 SYNTAX DisplayString (SIZE (0..255)) 236 MAX-ACCESS read-write 237 STATUS current 238 DESCRIPTION 239 "An administratively-assigned name for this managed 240 node. By convention, this is the node's fully-qualified 241 domain name. If the name is unknown, the value is 242 the zero-length string." 243 ::= { system 5 } 245 sysLocation OBJECT-TYPE 246 SYNTAX DisplayString (SIZE (0..255)) 247 MAX-ACCESS read-write 248 STATUS current 249 DESCRIPTION 250 "The physical location of this node (e.g., 'telephone 251 closet, 3rd floor'). If the location is unknown, the 252 value is the zero-length string." 253 ::= { system 6 } 255 sysServices OBJECT-TYPE 256 SYNTAX INTEGER (0..127) 257 MAX-ACCESS read-only 258 STATUS current 259 DESCRIPTION 260 "A value which indicates the set of services that this 261 entity may potentially offer. The value is a sum. 262 This sum initially takes the value zero. Then, for 263 each layer, L, in the range 1 through 7, that this node 264 performs transactions for, 2 raised to (L - 1) is added 265 to the sum. For example, a node which performs only 266 routing functions would have a value of 4 (2^(3-1)). 267 In contrast, a node which is a host offering application 268 services would have a value of 72 (2^(4-1) + 2^(7-1)). 269 Note that in the context of the Internet suite of 270 protocols, values should be calculated accordingly: 272 layer functionality 273 1 physical (e.g., repeaters) 274 2 datalink/subnetwork (e.g., bridges) 275 3 internet (e.g., supports the IP) 276 4 end-to-end (e.g., supports the TCP) 277 7 applications (e.g., supports the SMTP) 279 For systems including OSI protocols, layers 5 and 6 280 may also be counted." 281 ::= { system 7 } 283 -- object resource information 284 -- 285 -- a collection of objects which describe the SNMP entity's 286 -- (statically and dynamically configurable) support of 287 -- various MIB modules. 289 sysORLastChange OBJECT-TYPE 290 SYNTAX TimeStamp 291 MAX-ACCESS read-only 292 STATUS current 293 DESCRIPTION 294 "The value of sysUpTime at the time of the most recent 295 change in state or value of any instance of sysORID." 296 ::= { system 8 } 298 sysORTable OBJECT-TYPE 299 SYNTAX SEQUENCE OF SysOREntry 300 MAX-ACCESS not-accessible 301 STATUS current 302 DESCRIPTION 303 "The (conceptual) table listing the capabilities of 304 the local SNMP application acting as a command 305 responder with respect to various MIB modules. 306 SNMP entities having dynamically-configurable support 307 of MIB modules will have a dynamically-varying number 308 of conceptual rows." 309 ::= { system 9 } 311 sysOREntry OBJECT-TYPE 312 SYNTAX SysOREntry 313 MAX-ACCESS not-accessible 314 STATUS current 315 DESCRIPTION 316 "An entry (conceptual row) in the sysORTable." 317 INDEX { sysORIndex } 318 ::= { sysORTable 1 } 320 SysOREntry ::= SEQUENCE { 321 sysORIndex INTEGER, 322 sysORID OBJECT IDENTIFIER, 323 sysORDescr DisplayString, 324 sysORUpTime TimeStamp 325 } 327 sysORIndex OBJECT-TYPE 328 SYNTAX INTEGER (1..2147483647) 329 MAX-ACCESS not-accessible 330 STATUS current 331 DESCRIPTION 332 "The auxiliary variable used for identifying instances 333 of the columnar objects in the sysORTable." 334 ::= { sysOREntry 1 } 336 sysORID OBJECT-TYPE 337 SYNTAX OBJECT IDENTIFIER 338 MAX-ACCESS read-only 339 STATUS current 340 DESCRIPTION 341 "An authoritative identification of a capabilities 342 statement with respect to various MIB modules supported 343 by the local SNMP application acting as a command 344 responder." 345 ::= { sysOREntry 2 } 347 sysORDescr OBJECT-TYPE 348 SYNTAX DisplayString 349 MAX-ACCESS read-only 350 STATUS current 351 DESCRIPTION 352 "A textual description of the capabilities identified 353 by the corresponding instance of sysORID." 354 ::= { sysOREntry 3 } 356 sysORUpTime OBJECT-TYPE 357 SYNTAX TimeStamp 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "The value of sysUpTime at the time this conceptual 362 row was last instantiated." 363 ::= { sysOREntry 4 } 365 -- the SNMP group 366 -- 367 -- a collection of objects providing basic instrumentation and 368 -- control of an SNMP entity. 370 snmp OBJECT IDENTIFIER ::= { mib-2 11 } 372 snmpInPkts OBJECT-TYPE 373 SYNTAX Counter32 374 MAX-ACCESS read-only 375 STATUS current 376 DESCRIPTION 377 "The total number of messages delivered to the SNMP 378 entity from the transport service." 379 ::= { snmp 1 } 381 snmpInBadVersions OBJECT-TYPE 382 SYNTAX Counter32 383 MAX-ACCESS read-only 384 STATUS current 385 DESCRIPTION 386 "The total number of SNMP messages which were delivered 387 to the SNMP entity and were for an unsupported SNMP 388 version." 389 ::= { snmp 3 } 391 snmpInBadCommunityNames OBJECT-TYPE 392 SYNTAX Counter32 393 MAX-ACCESS read-only 394 STATUS current 395 DESCRIPTION 396 "The total number of community-based SNMP messages (for 397 example, SNMPv1) delivered to the SNMP entity which 398 used an SNMP community name not known to said entity. 399 Also, implementations which authenticate community-based 400 SNMP messages using check(s) in addition to matching 401 the community name (for example, by also checking 402 whether the message originated from a transport address 403 allowed to use a specified community name) MAY include 404 in this value the number of messages which failed the 405 additional check(s). It is strongly RECOMMENDED that 406 the documentation for any security model which is used 407 to authenticate community-based SNMP messages specify 408 the precise conditions that contribute to this value." 409 ::= { snmp 4 } 411 snmpInBadCommunityUses OBJECT-TYPE 412 SYNTAX Counter32 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "The total number of community-based SNMP messages (for 417 example, SNMPv1) delivered to the SNMP entity which 418 represented an SNMP operation that was not allowed for 419 the SNMP community named in the message. The precise 420 conditions under which this counter is incremented 421 (if at all) depend on how the SNMP entity implements 422 its access control mechanism and how its applications 423 interact with that access control mechanism. It is 424 strongly RECOMMENDED that the documentation for any 425 access control mechanism which is used to control access 426 to and visibility of MIB instrumentation specify the 427 precise conditions that contribute to this value." 428 ::= { snmp 5 } 430 snmpInASNParseErrs OBJECT-TYPE 431 SYNTAX Counter32 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "The total number of ASN.1 or BER errors encountered by 436 the SNMP entity when decoding received SNMP messages." 437 ::= { snmp 6 } 439 snmpEnableAuthenTraps OBJECT-TYPE 440 SYNTAX INTEGER { enabled(1), disabled(2) } 441 MAX-ACCESS read-write 442 STATUS current 443 DESCRIPTION 444 "Indicates whether the SNMP entity is permitted to 445 generate authenticationFailure traps. The value of this 446 object overrides any configuration information; as such, 447 it provides a means whereby all authenticationFailure 448 traps may be disabled. 450 Note that it is strongly recommended that this object 451 be stored in non-volatile memory so that it remains 452 constant across re-initializations of the network 453 management system." 454 ::= { snmp 30 } 456 snmpSilentDrops OBJECT-TYPE 457 SYNTAX Counter32 458 MAX-ACCESS read-only 459 STATUS current 460 DESCRIPTION 461 "The total number of Confirmed Class PDUs (such as 462 GetRequest-PDUs, GetNextRequest-PDUs, 463 GetBulkRequest-PDUs, SetRequest-PDUs, and 464 InformRequest-PDUs) delivered to the SNMP entity which 465 were silently dropped because the size of a reply 466 containing an alternate Response Class PDU (such as a 467 Response-PDU) with an empty variable-bindings field 468 was greater than either a local constraint or the 469 maximum message size associated with the originator of 470 the request." 471 ::= { snmp 31 } 473 snmpProxyDrops OBJECT-TYPE 474 SYNTAX Counter32 475 MAX-ACCESS read-only 476 STATUS current 477 DESCRIPTION 478 "The total number of Confirmed Class PDUs 479 (such as GetRequest-PDUs, GetNextRequest-PDUs, 480 GetBulkRequest-PDUs, SetRequest-PDUs, and 481 InformRequest-PDUs) delivered to the SNMP entity which 482 were silently dropped because the transmission of 483 the (possibly translated) message to a proxy target 484 failed in a manner (other than a time-out) such that 485 no Response Class PDU (such as a Response-PDU) could 486 be returned." 487 ::= { snmp 32 } 489 -- information for notifications 490 -- 491 -- a collection of objects which allow the SNMP entity, when 492 -- supporting a notification originator application, 493 -- to be configured to generate SNMPv2-Trap-PDUs. 495 snmpTrap OBJECT IDENTIFIER ::= { snmpMIBObjects 4 } 497 snmpTrapOID OBJECT-TYPE 498 SYNTAX OBJECT IDENTIFIER 499 MAX-ACCESS accessible-for-notify 500 STATUS current 501 DESCRIPTION 502 "The authoritative identification of the notification 503 currently being sent. This variable occurs as 504 the second varbind in every SNMPv2-Trap-PDU and 505 InformRequest-PDU." 506 ::= { snmpTrap 1 } 508 -- ::= { snmpTrap 2 } this OID is obsolete 510 snmpTrapEnterprise OBJECT-TYPE 511 SYNTAX OBJECT IDENTIFIER 512 MAX-ACCESS accessible-for-notify 513 STATUS current 514 DESCRIPTION 515 "The authoritative identification of the enterprise 516 associated with the trap currently being sent. When an 517 SNMP proxy agent is mapping an RFC1157 Trap-PDU 518 into a SNMPv2-Trap-PDU, this variable occurs as the 519 last varbind." 520 ::= { snmpTrap 3 } 522 -- ::= { snmpTrap 4 } this OID is obsolete 524 -- well-known traps 526 snmpTraps OBJECT IDENTIFIER ::= { snmpMIBObjects 5 } 528 coldStart NOTIFICATION-TYPE 529 STATUS current 530 DESCRIPTION 531 "A coldStart trap signifies that the SNMP entity, 532 supporting a notification originator application, is 533 reinitializing itself and that its configuration may 534 have been altered." 535 ::= { snmpTraps 1 } 537 warmStart NOTIFICATION-TYPE 538 STATUS current 539 DESCRIPTION 540 "A warmStart trap signifies that the SNMP entity, 541 supporting a notification originator application, 542 is reinitializing itself such that its configuration 543 is unaltered." 544 ::= { snmpTraps 2 } 546 -- Note the linkDown NOTIFICATION-TYPE ::= { snmpTraps 3 } 547 -- and the linkUp NOTIFICATION-TYPE ::= { snmpTraps 4 } 548 -- are defined in RFC 2233 [RFC2233] 550 authenticationFailure NOTIFICATION-TYPE 551 STATUS current 552 DESCRIPTION 553 "An authenticationFailure trap signifies that the SNMP 554 entity has received a protocol message that is not 555 properly authenticated. While all implementations 556 of SNMP entities MAY be capable of generating this 557 trap, the snmpEnableAuthenTraps object indicates 558 whether this trap will be generated." 559 ::= { snmpTraps 5 } 561 -- Note the egpNeighborLoss notification is defined 562 -- as { snmpTraps 6 } in RFC 1213 564 -- the set group 565 -- 566 -- a collection of objects which allow several cooperating 567 -- command generator applications to coordinate their use of the 568 -- set operation. 570 snmpSet OBJECT IDENTIFIER ::= { snmpMIBObjects 6 } 572 snmpSetSerialNo OBJECT-TYPE 573 SYNTAX TestAndIncr 574 MAX-ACCESS read-write 575 STATUS current 576 DESCRIPTION 577 "An advisory lock used to allow several cooperating 578 command generator applications to coordinate their 579 use of the SNMP set operation. 581 This object is used for coarse-grain coordination. 582 To achieve fine-grain coordination, one or more similar 583 objects might be defined within each MIB group, as 584 appropriate." 585 ::= { snmpSet 1 } 587 -- conformance information 589 snmpMIBConformance 590 OBJECT IDENTIFIER ::= { snmpMIB 2 } 592 snmpMIBCompliances 593 OBJECT IDENTIFIER ::= { snmpMIBConformance 1 } 594 snmpMIBGroups OBJECT IDENTIFIER ::= { snmpMIBConformance 2 } 596 -- compliance statements 598 -- ::= { snmpMIBCompliances 1 } this OID is obsolete 600 snmpBasicCompliance MODULE-COMPLIANCE 601 STATUS current 602 DESCRIPTION 603 "The compliance statement for SNMP entities which 604 implement this MIB module." 605 MODULE -- this module 606 MANDATORY-GROUPS { snmpGroup, snmpSetGroup, systemGroup, 607 snmpBasicNotificationsGroup } 609 GROUP snmpCommunityGroup 610 DESCRIPTION 611 "This group is mandatory for SNMP entities which 612 support community-based authentication." 614 ::= { snmpMIBCompliances 2 } 616 -- units of conformance 618 -- ::= { snmpMIBGroups 1 } this OID is obsolete 619 -- ::= { snmpMIBGroups 2 } this OID is obsolete 620 -- ::= { snmpMIBGroups 3 } this OID is obsolete 621 -- ::= { snmpMIBGroups 4 } this OID is obsolete 623 snmpGroup OBJECT-GROUP 624 OBJECTS { snmpInPkts, 625 snmpInBadVersions, 626 snmpInASNParseErrs, 627 snmpSilentDrops, 628 snmpProxyDrops, 629 snmpEnableAuthenTraps } 630 STATUS current 631 DESCRIPTION 632 "A collection of objects providing basic instrumentation 633 and control of an SNMP entity." 634 ::= { snmpMIBGroups 8 } 636 snmpCommunityGroup OBJECT-GROUP 637 OBJECTS { snmpInBadCommunityNames, 638 snmpInBadCommunityUses } 639 STATUS current 640 DESCRIPTION 641 "A collection of objects providing basic instrumentation 642 of a SNMP entity which supports community-based 643 authentication." 644 ::= { snmpMIBGroups 9 } 646 snmpSetGroup OBJECT-GROUP 647 OBJECTS { snmpSetSerialNo } 648 STATUS current 649 DESCRIPTION 650 "A collection of objects which allow several cooperating 651 command generator applications to coordinate their 652 use of the set operation." 653 ::= { snmpMIBGroups 5 } 655 systemGroup OBJECT-GROUP 656 OBJECTS { sysDescr, sysObjectID, sysUpTime, 657 sysContact, sysName, sysLocation, 658 sysServices, 659 sysORLastChange, sysORID, 660 sysORUpTime, sysORDescr } 661 STATUS current 662 DESCRIPTION 663 "The system group defines objects which are common to all 664 managed systems." 665 ::= { snmpMIBGroups 6 } 667 snmpBasicNotificationsGroup NOTIFICATION-GROUP 668 NOTIFICATIONS { coldStart, authenticationFailure } 669 STATUS current 670 DESCRIPTION 671 "The two notifications which an SNMP entity 672 supporting notification originator applications 673 is required to implement." 674 ::= { snmpMIBGroups 7 } 676 snmpAdditionalNotificationsGroup NOTIFICATION-GROUP 677 NOTIFICATIONS { warmStart } 678 STATUS current 679 DESCRIPTION 680 "The notifications which an SNMP entity 681 supporting notification originator applications 682 is required to implement if it is able to 683 reinitialize itself such that its configuration 684 is unaltered." 685 ::= { snmpMIBGroups 11 } 687 notificationGroup OBJECT-GROUP 688 OBJECTS { snmpTrapOID, snmpTrapEnterprise } 689 STATUS current 690 DESCRIPTION 691 "These objects are required for entities 692 which support notification originator applications." 693 ::= { snmpMIBGroups 12 } 695 -- definitions in RFC 1213 made obsolete by the inclusion of a 696 -- subset of the snmp group in this MIB 697 snmpOutPkts OBJECT-TYPE 698 SYNTAX Counter32 699 MAX-ACCESS read-only 700 STATUS obsolete 701 DESCRIPTION 702 "The total number of SNMP Messages which were 703 passed from the SNMP protocol entity to the 704 transport service." 705 ::= { snmp 2 } 707 -- { snmp 7 } is not used 709 snmpInTooBigs OBJECT-TYPE 710 SYNTAX Counter32 711 MAX-ACCESS read-only 712 STATUS obsolete 713 DESCRIPTION 714 "The total number of SNMP PDUs which were 715 delivered to the SNMP protocol entity and for 716 which the value of the error-status field was 717 `tooBig'." 718 ::= { snmp 8 } 720 snmpInNoSuchNames OBJECT-TYPE 721 SYNTAX Counter32 722 MAX-ACCESS read-only 723 STATUS obsolete 724 DESCRIPTION 725 "The total number of SNMP PDUs which were 726 delivered to the SNMP protocol entity and for 727 which the value of the error-status field was 728 `noSuchName'." 729 ::= { snmp 9 } 731 snmpInBadValues OBJECT-TYPE 732 SYNTAX Counter32 733 MAX-ACCESS read-only 734 STATUS obsolete 735 DESCRIPTION 736 "The total number of SNMP PDUs which were 737 delivered to the SNMP protocol entity and for 738 which the value of the error-status field was 739 `badValue'." 740 ::= { snmp 10 } 742 snmpInReadOnlys OBJECT-TYPE 743 SYNTAX Counter32 744 MAX-ACCESS read-only 745 STATUS obsolete 746 DESCRIPTION 747 "The total number valid SNMP PDUs which were delivered 748 to the SNMP protocol entity and for which the value 749 of the error-status field was `readOnly'. It should 750 be noted that it is a protocol error to generate an 751 SNMP PDU which contains the value `readOnly' in the 752 error-status field, as such this object is provided 753 as a means of detecting incorrect implementations of 754 the SNMP." 755 ::= { snmp 11 } 757 snmpInGenErrs OBJECT-TYPE 758 SYNTAX Counter32 759 MAX-ACCESS read-only 760 STATUS obsolete 761 DESCRIPTION 762 "The total number of SNMP PDUs which were delivered 763 to the SNMP protocol entity and for which the value 764 of the error-status field was `genErr'." 765 ::= { snmp 12 } 767 snmpInTotalReqVars OBJECT-TYPE 768 SYNTAX Counter32 769 MAX-ACCESS read-only 770 STATUS obsolete 771 DESCRIPTION 772 "The total number of MIB objects which have been 773 retrieved successfully by the SNMP protocol entity 774 as the result of receiving valid SNMP Get-Request 775 and Get-Next PDUs." 776 ::= { snmp 13 } 778 snmpInTotalSetVars OBJECT-TYPE 779 SYNTAX Counter32 780 MAX-ACCESS read-only 781 STATUS obsolete 782 DESCRIPTION 783 "The total number of MIB objects which have been 784 altered successfully by the SNMP protocol entity as 785 the result of receiving valid SNMP Set-Request PDUs." 786 ::= { snmp 14 } 788 snmpInGetRequests OBJECT-TYPE 789 SYNTAX Counter32 790 MAX-ACCESS read-only 791 STATUS obsolete 792 DESCRIPTION 793 "The total number of SNMP Get-Request PDUs which 794 have been accepted and processed by the SNMP 795 protocol entity." 796 ::= { snmp 15 } 798 snmpInGetNexts OBJECT-TYPE 799 SYNTAX Counter32 800 MAX-ACCESS read-only 801 STATUS obsolete 802 DESCRIPTION 803 "The total number of SNMP Get-Next PDUs which have been 804 accepted and processed by the SNMP protocol entity." 805 ::= { snmp 16 } 807 snmpInSetRequests OBJECT-TYPE 808 SYNTAX Counter32 809 MAX-ACCESS read-only 810 STATUS obsolete 811 DESCRIPTION 812 "The total number of SNMP Set-Request PDUs which 813 have been accepted and processed by the SNMP protocol 814 entity." 815 ::= { snmp 17 } 817 snmpInGetResponses OBJECT-TYPE 818 SYNTAX Counter32 819 MAX-ACCESS read-only 820 STATUS obsolete 821 DESCRIPTION 822 "The total number of SNMP Get-Response PDUs which 823 have been accepted and processed by the SNMP protocol 824 entity." 825 ::= { snmp 18 } 827 snmpInTraps OBJECT-TYPE 828 SYNTAX Counter32 829 MAX-ACCESS read-only 830 STATUS obsolete 831 DESCRIPTION 832 "The total number of SNMP Trap PDUs which have been 833 accepted and processed by the SNMP protocol entity." 834 ::= { snmp 19 } 836 snmpOutTooBigs OBJECT-TYPE 837 SYNTAX Counter32 838 MAX-ACCESS read-only 839 STATUS obsolete 840 DESCRIPTION 841 "The total number of SNMP PDUs which were generated 842 by the SNMP protocol entity and for which the value 843 of the error-status field was `tooBig.'" 844 ::= { snmp 20 } 846 snmpOutNoSuchNames OBJECT-TYPE 847 SYNTAX Counter32 848 MAX-ACCESS read-only 849 STATUS obsolete 850 DESCRIPTION 851 "The total number of SNMP PDUs which were generated 852 by the SNMP protocol entity and for which the value 853 of the error-status was `noSuchName'." 854 ::= { snmp 21 } 856 snmpOutBadValues OBJECT-TYPE 857 SYNTAX Counter32 858 MAX-ACCESS read-only 859 STATUS obsolete 860 DESCRIPTION 861 "The total number of SNMP PDUs which were generated 862 by the SNMP protocol entity and for which the value 863 of the error-status field was `badValue'." 864 ::= { snmp 22 } 866 -- { snmp 23 } is not used 868 snmpOutGenErrs OBJECT-TYPE 869 SYNTAX Counter32 870 MAX-ACCESS read-only 871 STATUS obsolete 872 DESCRIPTION 873 "The total number of SNMP PDUs which were generated 874 by the SNMP protocol entity and for which the value 875 of the error-status field was `genErr'." 876 ::= { snmp 24 } 878 snmpOutGetRequests OBJECT-TYPE 879 SYNTAX Counter32 880 MAX-ACCESS read-only 881 STATUS obsolete 882 DESCRIPTION 883 "The total number of SNMP Get-Request PDUs which 884 have been generated by the SNMP protocol entity." 885 ::= { snmp 25 } 887 snmpOutGetNexts OBJECT-TYPE 888 SYNTAX Counter32 889 MAX-ACCESS read-only 890 STATUS obsolete 891 DESCRIPTION 892 "The total number of SNMP Get-Next PDUs which have 893 been generated by the SNMP protocol entity." 894 ::= { snmp 26 } 896 snmpOutSetRequests OBJECT-TYPE 897 SYNTAX Counter32 898 MAX-ACCESS read-only 899 STATUS obsolete 900 DESCRIPTION 901 "The total number of SNMP Set-Request PDUs which 902 have been generated by the SNMP protocol entity." 903 ::= { snmp 27 } 905 snmpOutGetResponses OBJECT-TYPE 906 SYNTAX Counter32 907 MAX-ACCESS read-only 908 STATUS obsolete 909 DESCRIPTION 910 "The total number of SNMP Get-Response PDUs which 911 have been generated by the SNMP protocol entity." 912 ::= { snmp 28 } 914 snmpOutTraps OBJECT-TYPE 915 SYNTAX Counter32 916 MAX-ACCESS read-only 917 STATUS obsolete 918 DESCRIPTION 919 "The total number of SNMP Trap PDUs which have 920 been generated by the SNMP protocol entity." 921 ::= { snmp 29 } 923 snmpObsoleteGroup OBJECT-GROUP 924 OBJECTS { snmpOutPkts, snmpInTooBigs, snmpInNoSuchNames, 925 snmpInBadValues, snmpInReadOnlys, snmpInGenErrs, 926 snmpInTotalReqVars, snmpInTotalSetVars, 927 snmpInGetRequests, snmpInGetNexts, snmpInSetRequests, 928 snmpInGetResponses, snmpInTraps, snmpOutTooBigs, 929 snmpOutNoSuchNames, snmpOutBadValues, 930 snmpOutGenErrs, snmpOutGetRequests, snmpOutGetNexts, 931 snmpOutSetRequests, snmpOutGetResponses, snmpOutTraps 932 } 933 STATUS obsolete 934 DESCRIPTION 935 "A collection of objects from RFC 1213 made obsolete 936 by this MIB module." 937 ::= { snmpMIBGroups 10 } 939 END 941 4. Notice on Intellectual Property 943 The IETF takes no position regarding the validity or scope of any 944 intellectual property or other rights that might be claimed to 945 pertain to the implementation or use of the technology described in 946 this document or the extent to which any license under such rights 947 might or might not be available; neither does it represent that it 948 has made any effort to identify any such rights. Information on the 949 IETF's procedures with respect to rights in standards-track and 950 standards-related documentation can be found in BCP-11. Copies of 951 claims of rights made available for publication and any assurances of 952 licenses to be made available, or the result of an attempt made to 953 obtain a general license or permission for the use of such 954 proprietary rights by implementors or users of this specification can 955 be obtained from the IETF Secretariat. 957 The IETF invites any interested party to bring to its attention any 958 copyrights, patents or patent applications, or other proprietary 959 rights which may cover technology that may be required to practice 960 this standard. Please address the information to the IETF Executive 961 Director. 963 5. Acknowledgments 965 This document is the product of the SNMPv3 Working Group. Some 966 special thanks are in order to the following Working Group members: 968 Randy Bush 969 Jeffrey D. Case 970 Mike Daniele 971 Rob Frye 972 Lauren Heintz 973 Keith McCloghrie 974 Russ Mundy 975 David T. Perkins 976 Randy Presuhn 977 Aleksey Romanov 978 Juergen Schoenwaelder 979 Bert Wijnen 981 This version of the document, edited by Randy Presuhn, was initially 982 based on the work of a design team whose members were: 984 Jeffrey D. Case 985 Keith McCloghrie 986 David T. Perkins 987 Randy Presuhn 988 Juergen Schoenwaelder 990 The previous versions of this document, edited by Keith McCloghrie, 991 was the result of significant work by four major contributors: 993 Jeffrey D. Case 994 Keith McCloghrie 995 Marshall T. Rose 996 Steven Waldbusser 998 Additionally, the contributions of the SNMPv2 Working Group to the 999 previous versions are also acknowledged. In particular, a special 1000 thanks is extended for the contributions of: 1002 Alexander I. Alten 1003 Dave Arneson 1004 Uri Blumenthal 1005 Doug Book 1006 Kim Curran 1007 Jim Galvin 1008 Maria Greene 1009 Iain Hanson 1010 Dave Harrington 1011 Nguyen Hien 1012 Jeff Johnson 1013 Michael Kornegay 1014 Deirdre Kostick 1015 David Levi 1016 Daniel Mahoney 1017 Bob Natale 1018 Brian O'Keefe 1019 Andrew Pearson 1020 Dave Perkins 1021 Randy Presuhn 1022 Aleksey Romanov 1023 Shawn Routhier 1024 Jon Saperia 1025 Juergen Schoenwaelder 1026 Bob Stewart 1027 Kaj Tesink 1028 Glenn Waters 1029 Bert Wijnen 1031 6. Security Considerations 1033 There are a number of management objects defined in this MIB that 1034 have a MAX-ACCESS clause of read-write. Such objects may be 1035 considered sensitive or vulnerable in some network environments. The 1036 support for SET operations in a non-secure environment without proper 1037 protection can have a negative effect on network operations. 1039 SNMPv1 by itself is not a secure environment. Even if the network 1040 itself is secure (for example by using IPSec), even then, there is no 1041 control as to who on the secure network is allowed to access and 1042 GET/SET (read/change) the objects in this MIB. 1044 It is recommended that the implementors consider the security 1045 features as provided by the SNMPv3 framework. Specifically, the use 1046 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1047 based Access Control Model RFC 2575 [RFC2575] is recommended. 1049 It is then a customer/user responsibility to ensure that the SNMP 1050 entity giving access to an instance of this MIB, is properly 1051 configured to give access to the objects only to those principals 1052 (users) that have legitimate rights to indeed GET or SET (change) 1053 them. 1055 7. References 1057 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 1058 Identification of Management Information for TCP/IP-based 1059 Internets", STD 16, RFC 1155, May 1990. 1061 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1062 "Simple Network Management Protocol", STD 15, RFC 1157, 1063 May 1990. 1065 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 1066 STD 16, RFC 1212, March 1991. 1068 [RFC1213] McCloghrie, K., and M. Rose, "Management Information Base 1069 for Network Management of TCP/IP-based internets: MIB- 1070 II", STD 16, RFC 1213, March 1991. 1072 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 1073 the SNMP", RFC 1215, March 1991. 1075 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1076 "Introduction to Community-based SNMPv2", RFC 1901, 1077 January 1996. 1079 [RFC2233] McCloghrie, K., and F. Kastenholz, "The Interfaces Group 1080 MIB using SMIv2", RFC 2233, November 1997. 1082 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1083 "Introduction to Version 3 of the Internet-standard 1084 Network Management Framework", RFC 2570, April 1999. 1086 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1087 Architecture for Describing SNMP Management Frameworks", 1088 RFC 2571, April 1999. 1090 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1091 "Message Processing and Dispatching for the Simple 1092 Network Management Protocol (SNMP)", RFC 2572, April 1093 1999. 1095 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1096 Applications", RFC 2573, April 1999. 1098 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1099 (USM) for version 3 of the Simple Network Management 1100 Protocol (SNMPv3)", RFC 2574, April 1999. 1102 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1103 Access Control Model (VACM) for the Simple Network 1104 Management Protocol (SNMP)", RFC 2575, April 1999. 1106 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1107 Rose, M., and S. Waldbusser, "Structure of Management 1108 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1109 1999. 1111 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1112 Rose, M., and S. Waldbusser, "Textual Conventions for 1113 SMIv2", STD 58, RFC 2579, April 1999. 1115 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1116 Rose, M., and S. Waldbusser, "Conformance Statements for 1117 SMIv2", STD 58, RFC 2580, April 1999. 1119 [RFC-TM] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. 1120 Waldbusser, "Transport Mappings for the Simple Network 1121 Management Protocol", 1122 , June 2000. 1124 [RFC-PROTO] Presuhn, R., Case, J., McCloghrie, K., Rose, M., and S. 1125 Waldbusser, "Protocol Operations for the Simple Network 1126 Management Protocol", 1127 , June 2000. 1129 8. Editor's Address 1131 Randy Presuhn 1132 BMC Software, Inc. 1133 2141 North First Street 1134 San Jose, CA 95131 1135 USA 1137 Phone: +1 408 546 1006 1138 EMail: randy_presuhn@bmc.com 1140 9. Changes from RFC 1907 1142 These are the changes from RFC 1907: 1144 - Corrected typo in copyright statement; 1146 - Updated copyright date; 1148 - Updated with new editor's name and contact information; 1150 - Cosmetic fixes to layout and typography; 1152 - Changed title; 1154 - Replace introduction with current MIB boilerplate; 1156 - Updated references; 1158 - Fixed typo in sysORUpTime; 1160 - Re-worded description of snmpSilentDrops; 1162 - Updated reference to RFC 1573 to 2233; 1163 - Added IPR boilerplate as required by RFC 2026; 1165 - Weakened authenticationFailure description from MUST to 1166 MAY, clarified that it pertains to all SNMP entities; 1168 - Clarified descriptions of snmpInBadCommunityNames and 1169 snmpInBadCommunityUses; 1171 - Updated module-identity and contact information; 1173 - Updated the acknowledgements section; 1175 - Replaced references to "manager role", "agent role" and 1176 "SNMPv2 entity" with appropriate terms from RFC 2571; 1178 - Updated document headers and footers; 1180 - Added security considerations, based on current 1181 recommendations for MIB modules. 1183 - Added NOTIFICATION-GROUP and OBJECT-GROUP constructs for 1184 NOTIFICATION-TYPEs and OBJECT-TYPEs that were left 1185 unreferenced in RFC 1907. 1187 - Fixed typos in sysServices DESCRIPTION. 1189 - Changed description of snmpProxyDrops to use terms from 1190 architecture. 1192 - Changed value used in example for sysObjectID. 1194 10. Issues 1196 This section is to be deleted when it is time to publish this 1197 document as an RFC. The issue labels are the same as those used in 1198 the on-line issues list at 1199 ftp://amethyst.bmc.com/pub/snmpv3/Update567/rfc1907/index.html 1201 1907-01 Done; title changed. 1203 1907-02 Done; replaced introduction with current MIB 1204 boilerplate. 1206 1907-03 Done; resolution was to make no change. 1208 1907-04 Done; replaced occurrences of "SNMPv2 entity", 1209 "manager role", and "agent role" with appropriate 1210 terms from architecture. 1212 1907-05 Done; typo fixed. 1214 1907-06 Done; resolution was to make no change. 1216 1907-07 Done; description of snmpSilentDrops updated. 1218 1907-08 Done; reference to RFC 1573 replaced with reference to 1219 RFC 2233. 1221 1907-09 Done; resolution was to make no change. 1223 1907-10 Done; resolution was to make no change. 1225 1907-11 Done; resolution was to make no change. 1227 1907-12 Done; added security considerations based on 1228 recommended text from http://www.ops.ietf.org/ 1230 1907-13 Done; references and acknowledgements updated. 1232 1907-14 Done; IPR boilerplate aligned with RFC 2026. 1234 1907-15 Done; authenticationFailure weakened to MAY but 1235 permitted for all protocol versions. 1237 1907-16 Done; resolution was to make no change. 1239 1907-17 Done; clarified descriptions of 1240 snmpInBadCommunityNames and snmpInBadCommunityUses. 1242 1907-18 Done; resolution was to make no change. 1244 1907-19 Done; conformance material added. 1246 1907-20 Done; resolution was to make no change. 1248 11. Full Copyright Statement 1250 Copyright (C) The Internet Society (2000). All Rights Reserved. 1252 This document and translations of it may be copied and furnished to 1253 others, and derivative works that comment on or otherwise explain it 1254 or assist in its implementation may be prepared, copied, published 1255 and distributed, in whole or in part, without restriction of any 1256 kind, provided that the above copyright notice and this paragraph are 1257 included on all such copies and derivative works. However, this 1258 document itself may not be modified in any way, such as by removing 1259 the copyright notice or references to the Internet Society or other 1260 Internet organizations, except as needed for the purpose of 1261 developing Internet standards in which case the procedures for 1262 copyrights defined in the Internet Standards process must be 1263 followed, or as required to translate it into languages other than 1264 English. 1266 The limited permissions granted above are perpetual and will not be 1267 revoked by the Internet Society or its successors or assigns. 1269 This document and the information contained herein is provided on an 1270 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1271 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1272 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1273 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1274 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.