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