idnits 2.17.1 draft-ietf-snmpv2-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == 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 Abstract section. ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1. Introduction' ) ** The document seems to lack a Security Considerations section. ** 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 an Authors' Addresses Section. ** There are 33 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 863 looks like a reference -- Missing reference section? '2' on line 869 looks like a reference -- Missing reference section? '3' on line 874 looks like a reference -- Missing reference section? '4' on line 879 looks like a reference -- Missing reference section? '5' on line 884 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 2 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Draft Management Information Base for SNMPv2 Dec 92 4 Management Information Base 5 for version 2 of the 6 Simple Network Management Protocol (SNMPv2) 8 Tue Dec 22 13:43:46 1992 | 10 Jeffrey D. Case 11 SNMP Research, Inc. 12 University of Tennessee, Knoxville 13 case@cs.utk.edu 15 Keith McCloghrie 16 Hughes LAN Systems 17 kzm@hls.com 19 Marshall T. Rose 20 Dover Beach Consulting, Inc. 21 mrose@dbc.mtview.ca.us 23 Steven L. Waldbusser 24 Carnegie Mellon University 25 waldbusser@andrew.cmu.edu 27 Status of this Memo 29 This document is an Internet Draft. Internet Drafts are 30 working documents of the Internet Engineering Task Force 31 (IETF), its Areas, and its Working Groups. Note that other 32 groups may also distribute working documents as Internet 33 Drafts. 35 Internet Drafts are valid for a maximum of six months and may 36 be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet Drafts as reference 38 material or to cite them other than as a "work in progress". 40 Draft Management Information Base for SNMPv2 Dec 92 42 1. Introduction 44 A network management system contains: several (potentially 45 many) nodes, each with a processing entity, termed an agent, 46 which has access to management instrumentation; at least one 47 management station; and, a management protocol, used to convey 48 management information between the agents and management 49 stations. Operations of the protocol are carried out under an 50 administrative framework which defines both authentication and 51 authorization policies. 53 Network management stations execute management applications 54 which monitor and control network elements. Network elements 55 are devices such as hosts, routers, terminal servers, etc., 56 which are monitored and controlled through access to their 57 management information. 59 Management information is viewed as a collection of managed 60 objects, residing in a virtual information store, termed the 61 Management Information Base (MIB). Collections of related 62 objects are defined in MIB modules. These modules are written 63 using a subset of OSI's Abstract Syntax Notation One (ASN.1) 64 [1], termed the Structure of Management Information (SMI) [2]. 66 The management protocol, SNMPv2 [3], provides for the exchange 67 of messages which convey management information between the 68 agents and the management stations. It is the purpose of this 69 document to define managed objects which describe the behavior 70 of a SNMPv2 entity. 72 1.1. A Note on Terminology 74 For the purpose of exposition, the original Internet-standard 75 Network Management Framework, as described in RFCs 1155, 1157, 76 and 1212, is termed the SNMP version 1 framework (SNMPv1). 77 The current framework is termed the SNMP version 2 framework 78 (SNMPv2). 80 Draft Management Information Base for SNMPv2 Dec 92 82 2. Definitions 84 SNMPv2-MIB DEFINITIONS ::= BEGIN 86 IMPORTS 87 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 88 ObjectName, Integer32, Counter32, snmpModules 89 FROM SNMPv2-SMI 90 TruthValue, DisplayString, TestAndIncr, TimeStamp 91 FROM SNMPv2-TC 92 MODULE-COMPLIANCE, OBJECT-GROUP 93 FROM SNMPv2-CONF 94 system, ifIndex, egpNeighAddr 95 FROM RFC1213-MIB 96 partyEntry 97 FROM SNMPv2-PARTY-MIB; 99 snmpMIB MODULE-IDENTITY 100 LAST-UPDATED "9212222143Z" | 101 ORGANIZATION "IETF SNMPv2 Working Group" 102 CONTACT-INFO 103 " Marshall T. Rose 105 Postal: Dover Beach Consulting, Inc. 106 420 Whisman Court 107 Mountain View, CA 94043-2186 108 US 110 Tel: +1 415 968 1052 111 Fax: +1 415 968 2510 113 E-mail: mrose@dbc.mtview.ca.us" 114 DESCRIPTION 115 "The MIB module for SNMPv2 entities." 116 ::= { snmpModules 1 } 118 snmpMIBObjects OBJECT IDENTIFIER ::= { snmpMIB 1 } 119 Draft Management Information Base for SNMPv2 Dec 92 121 -- the SNMPv2 statistics group 122 -- 123 -- a collection of objects providing basic instrumentation of 124 -- the SNMPv2 entity. 126 -- A Case diagram[4] relating these objects is: 127 -- 128 -- \v/ transport service 129 -- | 130 -- ==+== snmpStatsPackets 131 -- | 132 -- +==> snmpStats30Something 133 -- | 134 -- +==> snmpStatsEncodingErrors 135 -- | 136 -- +==> snmpStatsUnknownDstParties 137 -- | 138 -- +==> snmpStatsDstPartyMismatches + 139 -- | + 140 -- +==> snmpStatsUnknownSrcParties 141 -- | 142 -- +==> snmpStatsBadAuths 143 -- | 144 -- +==> snmpStatsNotInLifeTimes 145 -- | 146 -- +==> snmpStatsWrongDigestValues 147 -- | 148 -- +==> snmpStatsBadOperations 149 -- | 150 -- +==> snmpStatsSilentDrops 151 -- | 152 -- ===== sink 154 snmpStats OBJECT IDENTIFIER ::= { snmpMIBObjects 1 } 155 Draft Management Information Base for SNMPv2 Dec 92 157 snmpStatsPackets OBJECT-TYPE 158 SYNTAX Counter32 159 MAX-ACCESS read-only 160 STATUS current 161 DESCRIPTION 162 "The total number of packets received by the 163 SNMPv2 entity from the transport service." 164 REFERENCE 165 "Derived from RFC1213-MIB.snmpInPkts." 166 ::= { snmpStats 1 } 168 snmpStats30Something OBJECT-TYPE 169 SYNTAX Counter32 170 MAX-ACCESS read-only 171 STATUS current 172 DESCRIPTION 173 "The total number of packets which had an initial 174 octet with a value of 30 hexadecimal received by a 175 SNMPv2 entity which does not support SNMPv1. 176 (Such packets are possibly misdirected SNMPv1 177 Messages.)" 178 REFERENCE 179 "Derived from RFC1213-MIB.snmpInASNParseErrs." 180 ::= { snmpStats 2 } 182 snmpStatsEncodingErrors OBJECT-TYPE 183 SYNTAX Counter32 184 MAX-ACCESS read-only 185 STATUS current 186 DESCRIPTION 187 "The total number of packets received by the 188 SNMPv2 entity which were improperly encoded or had 189 invalid syntax." 190 REFERENCE 191 "Derived from RFC1213-MIB.snmpInASNParseErrs." 192 ::= { snmpStats 3 } 194 Draft Management Information Base for SNMPv2 Dec 92 196 snmpStatsUnknownDstParties OBJECT-TYPE 197 SYNTAX Counter32 198 MAX-ACCESS read-only 199 STATUS current 200 DESCRIPTION 201 "The total number of SnmpPrivMsgs delivered to the | 202 SNMPv2 entity for which the privDst field was not | 203 a known local party." | 204 ::= { snmpStats 4 } 206 snmpStatsDstPartyMismatches OBJECT-TYPE + 207 SYNTAX Counter32 + 208 MAX-ACCESS read-only + 209 STATUS current + 210 DESCRIPTION + 211 "The total number of SnmpPrivMsgs delivered to the + 212 SNMPv2 entity which contained a SnmpAuthMsg for + 213 which the authData.dstParty field did not match + 214 the privDst field in the SnmpPrivMsg." + 215 ::= { snmpStats 5 } + 217 snmpStatsUnknownSrcParties OBJECT-TYPE 218 SYNTAX Counter32 219 MAX-ACCESS read-only 220 STATUS current 221 DESCRIPTION 222 "The total number of SnmpAuthMsgs delivered to the 223 SNMPv2 entity for which the authData.srcParty 224 field was not a known remote party." 225 ::= { snmpStats 6 } | 227 snmpStatsBadAuths OBJECT-TYPE 228 SYNTAX Counter32 229 MAX-ACCESS read-only 230 STATUS current 231 DESCRIPTION 232 "The total number of SnmpAuthMsgs delivered to the 233 SNMPv2 entity which contained an authInfo field 234 which was inconsistent with the authentication 235 protocol associated with the source party." 236 ::= { snmpStats 7 } | 238 Draft Management Information Base for SNMPv2 Dec 92 240 snmpStatsNotInLifetimes OBJECT-TYPE 241 SYNTAX Counter32 242 MAX-ACCESS read-only 243 STATUS current 244 DESCRIPTION 245 "The total number of SnmpAuthMsgs delivered to the 246 SNMPv2 entity which were deemed unauthentic due to 247 their authInfo.authSrcTimestamp field being less 248 than the source party's clock plus lifetime." 249 ::= { snmpStats 8 } | 251 snmpStatsWrongDigestValues OBJECT-TYPE 252 SYNTAX Counter32 253 MAX-ACCESS read-only 254 STATUS current 255 DESCRIPTION 256 "The total number of SnmpAuthMsgs delivered to the 257 SNMPv2 entity which were deemed unauthentic due to 258 their authInfo.authDigest field being unequal to 259 the expected digest value." 260 ::= { snmpStats 9 } | 262 snmpStatsBadOperations OBJECT-TYPE 263 SYNTAX Counter32 264 MAX-ACCESS read-only 265 STATUS current 266 DESCRIPTION 267 "The total number of messages delivered to the 268 SNMPv2 entity which were silently dropped because 269 the PDU type referred to an operation not allowed 270 in the aclTable[5]." 271 ::= { snmpStats 10 } | 273 Draft Management Information Base for SNMPv2 Dec 92 275 snmpStatsSilentDrops OBJECT-TYPE 276 SYNTAX Counter32 277 MAX-ACCESS read-only 278 STATUS current 279 DESCRIPTION 280 "The total number of GetRequest-PDUs, 281 GetNextRequest-PDUs, GetBulkRequest-PDUs, 282 SetRequest-PDUs, and InformRequest-PDUs delivered 283 to the SNMPv2 entity which were silently dropped 284 because the size of an reply containing an 285 alternate Response-PDU with an empty variable- 286 bindings field was greater than either a local 287 constraint or the maximum message size of the 288 request's source party." 289 ::= { snmpStats 11 } | 291 Draft Management Information Base for SNMPv2 Dec 92 293 -- the SNMPv1 statistics group 294 -- 295 -- a collection of objects providing basic instrumentation of 296 -- a SNMPv2 entity which also implements SNMPv1. | 298 -- A Case diagram[4] relating these objects 299 -- (and those applicable objects in the snmpStats group) 300 -- is: 301 -- 302 -- \v/ transport service 303 -- | 304 -- ==+== snmpStatsPackets 305 -- | 306 -- +==> snmpStatsEncodingErrors 307 -- | 308 -- +==> snmpV1BadCommunityNames 309 -- | 310 -- +==> snmpV1BadCommunityUses 311 -- | 312 -- ===== sink 314 snmpV1 OBJECT IDENTIFIER ::= { snmpMIBObjects 2 } 316 snmpV1BadCommunityNames OBJECT-TYPE 317 SYNTAX Counter32 318 MAX-ACCESS read-only 319 STATUS current 320 DESCRIPTION 321 "The total number of SNMPv1 Messages delivered to 322 the SNMPv2 entity which used a community name not 323 known to the SNMPv2 entity." 324 REFERENCE 325 "Derived from RFC1213- 326 MIB.snmpInBadCommunityNames." 327 ::= { snmpV1 1 } 329 Draft Management Information Base for SNMPv2 Dec 92 331 snmpV1BadCommunityUses OBJECT-TYPE 332 SYNTAX Counter32 333 MAX-ACCESS read-only 334 STATUS current 335 DESCRIPTION 336 "The total number of SNMPv1 Messages delivered to 337 SNMPv2 entity containing an operation which was 338 not allowed for the community named in the 339 Message." 340 REFERENCE 341 "Derived from RFC1213-MIB.snmpInBadCommunityUses." 342 ::= { snmpV1 2 } 344 Draft Management Information Base for SNMPv2 Dec 92 346 -- the object resource group 347 -- 348 -- a collection of objects allowing a SNMPv2 entity acting in 349 -- an agent role to describe its dynamically-configurable 350 -- object resources. 352 snmpOR OBJECT IDENTIFIER ::= { snmpMIBObjects 3 } 354 snmpORLastChange OBJECT-TYPE 355 SYNTAX TimeStamp 356 MAX-ACCESS read-only 357 STATUS current 358 DESCRIPTION 359 "The value of sysUpTime at the time of the most 360 recent change in state or value of any instance of 361 snmpORID." 362 ::= { snmpOR 1 } 364 snmpORTable OBJECT-TYPE 365 SYNTAX SEQUENCE OF SnmpOREntry 366 MAX-ACCESS not-accessible 367 STATUS current 368 DESCRIPTION 369 "The (conceptual) table listing the dynamically- 370 configurable object resources in a SNMPv2 entity 371 acting in an agent role. SNMPv2 entities which do 372 not support dynamically-configurable object 373 resources will never have any instances of the 374 columnar objects in this table." 375 ::= { snmpOR 2 } 377 snmpOREntry OBJECT-TYPE 378 SYNTAX SnmpOREntry 379 MAX-ACCESS not-accessible 380 STATUS current 381 DESCRIPTION 382 "An entry (conceptual row) in the snmpORTable." 383 INDEX { snmpORIndex } 384 ::= { snmpORTable 1 } 386 Draft Management Information Base for SNMPv2 Dec 92 388 SnmpOREntry ::= SEQUENCE { 389 snmpORIndex Integer32, 390 snmpORID OBJECT IDENTIFIER, 391 snmpORDescr DisplayString 392 } 394 snmpORIndex OBJECT-TYPE 395 SYNTAX Integer32 396 MAX-ACCESS not-accessible 397 STATUS current 398 DESCRIPTION 399 "The auxiliary variable used for identifying 400 instances of the columnar objects in the 401 snmpORTable." 402 ::= { snmpOREntry 1 } 404 snmpORID OBJECT-TYPE 405 SYNTAX OBJECT IDENTIFIER 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "An authoritative identification of one of the 410 dynamically-configurable object resources in a 411 SNMPv2 entity acting in an agent role. This is 412 analogous to the sysObjectID object in MIB-II." 413 ::= { snmpOREntry 2 } 415 snmpORDescr OBJECT-TYPE 416 SYNTAX DisplayString 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "A textual description of one of the dynamically- 421 configurable object resources in a SNMPv2 entity 422 acting in an agent role. This is analogous to the 423 sysDescr object in MIB-II." 424 ::= { snmpOREntry 3 } 426 Draft Management Information Base for SNMPv2 Dec 92 428 -- the traps group 429 -- 430 -- a collection of objects which allow the SNMPv2 entity, when 431 -- acting in an agent role, to be configured to generate 432 -- SNMPv2-Trap-PDUs. 434 snmpTrap OBJECT IDENTIFIER ::= { snmpMIBObjects 4 } 436 snmpTrapOID OBJECT-TYPE 437 SYNTAX OBJECT IDENTIFIER 438 MAX-ACCESS not-accessible 439 STATUS current 440 DESCRIPTION 441 "The authoritative identification of the trap 442 currently being sent. This variable occurs as the 443 second varbind of a SNMPv2-Trap-PDU." 444 ::= { snmpTrap 1 } 446 snmpTrapTable OBJECT-TYPE 447 SYNTAX SEQUENCE OF SnmpTrapEntry 448 MAX-ACCESS not-accessible 449 STATUS current 450 DESCRIPTION 451 "A table which keeps track of how many traps have 452 been sent to each SNMPv2 entity." 453 ::= { snmpTrap 2 } 455 snmpTrapEntry OBJECT-TYPE 456 SYNTAX SnmpTrapEntry 457 MAX-ACCESS not-accessible 458 STATUS current 459 DESCRIPTION 460 "An entry which keeps track of how many traps have 461 been sent to a particular SNMPv2 entity." 462 AUGMENTS { partyEntry } 463 ::= { snmpTrapTable 1 } 465 SnmpTrapEntry ::= SEQUENCE { 466 snmpTrapNumbers Counter32 467 } 468 Draft Management Information Base for SNMPv2 Dec 92 470 snmpTrapNumbers OBJECT-TYPE 471 SYNTAX Counter32 472 MAX-ACCESS read-only 473 STATUS current 474 DESCRIPTION 475 "The number of traps which have been sent to a 476 particular SNMPv2 party, since the last 477 initialization of the SNMPv2 entity, or the 478 creation of the SNMPv2 party, whichever occurred 479 most recently." 480 ::= { snmpTrapEntry 1 } 482 snmpTrapEnterprise OBJECT-TYPE 483 SYNTAX OBJECT IDENTIFIER 484 MAX-ACCESS not-accessible 485 STATUS current 486 DESCRIPTION 487 "The authoritative identification of the 488 enterprise associated with the trap currently 489 being sent. When a SNMPv2 proxy agent is mapping 490 an RFC1157 Trap-PDU into a SNMPv2-Trap-PDU, this 491 variable occurs as the last varbind." 492 ::= { snmpTrap 3 } 494 Draft Management Information Base for SNMPv2 Dec 92 496 snmpV2EnableAuthenTraps OBJECT-TYPE 497 SYNTAX TruthValue 498 MAX-ACCESS read-write 499 STATUS current 500 DESCRIPTION 501 "Indicates whether the SNMPv2 entity, when acting 502 in an agent role, is permitted to generate 503 authenticationFailure traps. The value of this 504 object overrides any configuration information; as 505 such, it provides a means whereby all 506 authenticationFailure traps may be disabled. 508 Note that it is strongly recommended that this 509 object be stored in non-volatile memory so that it 510 remains constant between re-initializations of the 511 network management system." 512 REFERENCE 513 "Derived from RFC1213-MIB.snmpEnableAuthenTraps." 514 ::= { snmpTrap 4 } 516 Draft Management Information Base for SNMPv2 Dec 92 518 -- well-known traps 520 snmpTraps OBJECT IDENTIFIER ::= { snmpMIBObjects 5 } 522 coldStart NOTIFICATION-TYPE 523 STATUS current 524 DESCRIPTION 525 "A coldStart trap signifies that the SNMPv2 526 entity, acting in an agent role, is reinitializing 527 itself such that its configuration may be 528 altered." 529 ::= { snmpTraps 1 } 531 warmStart NOTIFICATION-TYPE 532 STATUS current 533 DESCRIPTION 534 "A warmStart trap signifies that the SNMPv2 535 entity, acting in an agent role, is reinitializing 536 itself such that its configuration is unaltered." 537 ::= { snmpTraps 2 } 539 linkDown NOTIFICATION-TYPE 540 OBJECTS { ifIndex } 541 STATUS current 542 DESCRIPTION 543 "A linkDown trap signifies that the SNMPv2 entity, 544 acting in an agent role, recognizes a failure in 545 one of the communication links represented in its 546 configuration." 547 ::= { snmpTraps 3 } 549 linkUp NOTIFICATION-TYPE 550 OBJECTS { ifIndex } 551 STATUS current 552 DESCRIPTION 553 "A linkUp trap signifies that the SNMPv2 entity, 554 acting in an agent role, recognizes that one of 555 the communication links represented in its 556 configuration has come up." 557 ::= { snmpTraps 4 } 559 Draft Management Information Base for SNMPv2 Dec 92 561 authenticationFailure NOTIFICATION-TYPE 562 STATUS current 563 DESCRIPTION 564 "An authenticationFailure trap signifies that the 565 SNMPv2 entity, acting in an agent role, has 566 received a protocol message that is not properly 567 authenticated. While all implementations of the 568 SNMPv2 must be capable of generating this trap, 569 the snmpV2EnableAuthenTraps object indicates 570 whether this trap will be generated." 571 ::= { snmpTraps 5 } 573 egpNeighborLoss NOTIFICATION-TYPE 574 OBJECTS { egpNeighAddr } 575 STATUS current 576 DESCRIPTION 577 "An egpNeighborLoss trap signifies that an EGP 578 neighbor has been marked down and the EGP peer 579 relationship no longer obtains." 580 ::= { snmpTraps 6 } 582 Draft Management Information Base for SNMPv2 Dec 92 584 -- the set group 585 -- 586 -- a collection of objects which allow several cooperating SNMPv2 587 -- SNMPv2 entities, all acting in a manager role, to 588 -- coordinate their use of the SNMPv2 set operation. 590 snmpSet OBJECT IDENTIFIER ::= { snmpMIBObjects 6 } 592 snmpSetSerialNo OBJECT-TYPE 593 SYNTAX TestAndIncr 594 MAX-ACCESS read-write 595 STATUS current 596 DESCRIPTION 597 "An advisory lock used to allow several 598 cooperating SNMPv2 entities, all acting in a 599 manager role, to coordinate their use of the 600 SNMPv2 set operation. 602 This object is used for coarse-grain coordination. 603 To achieve fine-grain coordination, one or more 604 similar objects might be defined within each MIB 605 group, as appropriate." 606 ::= { snmpSet 1 } 608 Draft Management Information Base for SNMPv2 Dec 92 610 -- conformance information 612 snmpMIBConformance OBJECT IDENTIFIER ::= { snmpMIB 2 } 614 snmpMIBCompliances OBJECT IDENTIFIER ::= { snmpMIBConformance 1 } 615 snmpMIBGroups OBJECT IDENTIFIER ::= { snmpMIBConformance 2 } 617 -- compliance statements 619 snmpMIBCompliance MODULE-COMPLIANCE 620 STATUS current 621 DESCRIPTION 622 "The compliance statement for SNMPv2 entities 623 which implement the SNMPv2 MIB." 624 MODULE RFC1213-MIB 625 MANDATORY-GROUPS { system } 627 MODULE -- this module 628 MANDATORY-GROUPS { snmpStatsGroup, snmpORGroup, 629 snmpTrapGroup, snmpSetGroup } 631 GROUP snmpV1Group 632 DESCRIPTION 633 "The snmpV1 group is mandatory only for those 634 SNMPv2 entities which also implement SNMPv1." 635 ::= { snmpMIBCompliances 1 } 637 Draft Management Information Base for SNMPv2 Dec 92 639 -- units of conformance 641 snmpStatsGroup OBJECT-GROUP 642 OBJECTS { snmpStatsPackets, snmpStats30Something, 643 snmpStatsEncodingErrors, 644 snmpStatsUnknownDstParties, 645 snmpStatsDstPartyMismatches, + 646 snmpStatsUnknownSrcParties, snmpStatsBadAuths, 647 snmpStatsNotInLifetimes, 648 snmpStatsWrongDigestValues, 649 snmpStatsBadOperations, snmpStatsSilentDrops } 650 STATUS current 651 DESCRIPTION 652 "A collection of objects providing basic 653 instrumentation of the SNMPv2 entity." 654 ::= { snmpMIBGroups 1 } 656 snmpV1Group OBJECT-GROUP 657 OBJECTS { snmpV1BadCommunityNames, snmpV1BadCommunityUses } 658 STATUS current 659 DESCRIPTION 660 "A collection of objects providing basic 661 instrumentation of a SNMPv2 entity which also 662 implements SNMPv1." 663 ::= { snmpMIBGroups 2 } 665 snmpORGroup OBJECT-GROUP 666 OBJECTS { snmpORLastChange, snmpORID, snmpORDescr } 667 STATUS current 668 DESCRIPTION 669 "A collection of objects allowing a SNMPv2 entity 670 acting in an agent role to describe its 671 dynamically-configurable object resources." 672 ::= { snmpMIBGroups 3 } 674 Draft Management Information Base for SNMPv2 Dec 92 676 snmpTrapGroup OBJECT-GROUP 677 OBJECTS { snmpTrapNumbers, snmpV2EnableAuthenTraps } 678 STATUS current 679 DESCRIPTION 680 "A collection of objects which allow the SNMPv2 681 entity, when acting in an agent role, to be 682 configured to generate SNMPv2-Trap-PDUs." 683 ::= { snmpMIBGroups 4 } 685 snmpSetGroup OBJECT-GROUP 686 OBJECTS { snmpSetSerialNo } 687 STATUS current 688 DESCRIPTION 689 "A collection of objects which allow several 690 cooperating SNMPv2 entities, all acting in a 691 manager role, to coordinate their use of the 692 SNMPv2 set operation." 693 ::= { snmpMIBGroups 5 } 695 END 696 Draft Management Information Base for SNMPv2 Dec 92 698 3. Acknowledgements 700 The objects in the snmpStats and snmpV1 groups are based, in 701 part, on RFC 1213. 703 Finally, the comments of the SNMP version 2 working group are 704 gratefully acknowledged: 706 Beth Adams, Network Management Forum 707 Steve Alexander, INTERACTIVE Systems Corporation 708 David Arneson, Cabletron Systems 709 Toshiya Asaba, 710 Fred Baker, ACC 711 Jim Barnes, Xylogics, Inc. 712 Brian Bataille 713 Andy Bierman, SynOptics Communications, Inc. 714 Uri Blumenthal, IBM Corporation 715 Fred Bohle, Interlink 716 Jack Brown 717 Theodore Brunner, Bellcore 718 Stephen F. Bush, GE Information Services 719 Deirdre C. Kostik, Bellcore 720 Jeff Case, University of Tennessee, Knoxville 721 John Chang, IBM Corporation 722 Szusin Chen, Sun Microsystems 723 Robert Ching 724 Chris Chiotasso, Ungermann-Bass 725 Bobby A. Clay, NASA/Boeing 726 John Cooke, Chipcom 727 Tracy Cox, Bellcore 728 Juan Cruz, Datability, Inc. 729 David Cullerot, Cabletron Systems 730 Cathy Cunningham, Microcom 731 James R. (Chuck) Davin, Bellcore 732 Michael Davis, Clearpoint 733 Mike Davison, FiberCom 734 Cynthia DellaTorre, MITRE 735 Taso N. Devetzis, Bellcore 736 Manual Diaz, DAVID Systems, Inc. 737 Jon Dreyer, Sun Microsystems 738 Susan E. Hicks, Martin Marietta Energy Systems 739 David Engel, Optical Data Systems 740 Mike Erlinger, Lexcel 741 Roger Fajman, NIH 742 Daniel Fauvarque, Sun Microsystems 744 Draft Management Information Base for SNMPv2 Dec 92 746 Karen Frisa, CMU 747 Shari Galitzer, MITRE 748 Shawn Gallagher, Digital Equipment Corporation 749 Richard Graveman, Bellcore 750 Maria Greene, Xyplex, Inc. 751 Michel Guittet, Apple 752 Robert Gutierrez, NASA 753 Bill Hagerty, Cabletron Systems 754 Gary W. Haney, Martin Marietta Energy Systems 755 Patrick Hanil, Nokia Telecommunications 756 Matt Hecht, SNMP Research, Inc. 757 Edward A. Heiner, Jr., Synernetics Inc. 758 Geral Holzhauer, Apple 759 John Hopprich, DAVID Systems, Inc. 760 Jeff Hughes, Hewlett-Packard 761 Robin Iddon, Axon Networks, Inc. 762 David Itusak 763 Kevin M. Jackson, Concord Communications, Inc. 764 Ole J. Jacobsen, Interop Company 765 Ronald Jacoby, Silicon Graphics, Inc. 766 Satish Joshi, SynOptics Communications, Inc. 767 Frank Kastenholz, FTP Software 768 Mark Kepke, Hewlett-Packard 769 Ken Key, SNMP Research, Inc. 770 Zbiginew Kielczewski, Eicon 771 Jongyeoi Kim 772 Andrew Knutsen, The Santa Cruz Operation 773 Michael L Kornegay, VisiSoft 774 Cheryl Krupczak, Georgia Tech 775 Steven L. Waldbusser, Carnegie Mellon Universitty 776 Mark S. Lewis, Telebit 777 David Lin 778 David Lindemulder, AT&T/NCR 779 Ben Lisowski, Sprint 780 David Liu, Bell-Northern Research 781 John Lunny, The Wollongong Group 782 Robert C. Lushbaugh Martin, Marietta Energy Systems 783 Michael Luufer, BBN 784 Carl Madison, Star-Tek, Inc. 785 Keith McCloghrie, Hughes LAN Systems 786 Evan McGinnis, 3Com Corporation 787 Bill McKenzie, IBM Corporation 788 Donna McMaster, SynOptics Communications, Inc. 789 John Medicke, IBM Corporation 790 Doug Miller, Telebit 792 Draft Management Information Base for SNMPv2 Dec 92 794 Dave Minnich, FiberCom 795 Mohammad Mirhakkak, MITRE 796 Rohit Mital, Protools 797 George Mouradian, AT&T Bell Labs 798 Patrick Mullaney, Cabletron Systems 799 Dan Myers, 3Com Corporation 800 Rina Nathaniel, Rad Network Devices Ltd. 801 Hien V. Nguyen, Sprint 802 Mo Nikain 803 Tom Nisbet 804 William B. Norton, MERIT 805 Steve Onishi, Wellfleet Communications, Inc. 806 David T. Perkins, SynOptics Communications, Inc. 807 Carl Powell, BBN 808 Ilan Raab, SynOptics Communications, Inc. 809 RIchard Ramons, AT&T 810 Venkat D. Rangan, Metric Network Systems, Inc. 811 Louise Reingold, Sprint 812 Sam Roberts, Farallon Computing, Inc. 813 Kary Robertson, Concord Communications, Inc. 814 Dan Romascanu, Lannet Data Communications Ltd. 815 Marshall T. Rose, Dover Beach Consulting, Inc. 816 Shawn A. Routhier, Epilogue Technology Corporation 817 Chris Rozman 818 Asaf Rubissa, Fibronics 819 Jon Saperia, Digital Equipment Corporation 820 Michael Sapich 821 Mike Scanlon, Interlan 822 Sam Schaen, MITRE 823 John Seligson, Ultra Network Technologies 824 Paul A. Serice, Corporation for Open Systems 825 Chris Shaw, Banyan Systems 826 Timon Sloane 827 Robert Snyder, Cisco Systems 828 Joo Young Song 829 Roy Spitier, Sprint 830 Einar Stefferud, Network Management Associates 831 John Stephens, Cayman Systems, Inc. 832 Bob Stewart, Xyplex, Inc. (chair) 833 Kaj Tesink, Bellcore 834 Dean Throop, Data General 835 Ahmet Tuncay, France Telecom-CNET 836 Maurice Turcotte, Racal Datacom 837 Warren Vik, INTERACTIVE Systems Corporation 838 Yannis Viniotis 840 Draft Management Information Base for SNMPv2 Dec 92 842 Steve Waldbusser, CMU 843 Timothy M. Walden, ACC 844 Alice Wang, Sun Microsystems 845 James Watt, Newbridge 846 Luanne Waul, Timeplex 847 Donald E. Westlake III, Digital Equipment Corporation 848 Gerry White 849 Bert Wijnen, IBM Corporation 850 Peter Wilson, 3Com Corporation 851 Steven Wong, Digital Equipment Corporation 852 Randy Worzella, IBM Corporation 853 Daniel Woycke, MITRE 854 Honda Wu 855 Jeff Yarnell, Protools 856 Chris Young, Cabletron 857 Kiho Yum, 3Com Corporation 859 Draft Management Information Base for SNMPv2 Dec 92 861 4. References 863 [1] Information processing systems - Open Systems 864 Interconnection - Specification of Abstract Syntax 865 Notation One (ASN.1), International Organization for 866 Standardization. International Standard 8824, (December, 867 1987). 869 [2] J.D. Case, K. McCloghrie, M.T. Rose, S.L. Waldbusser, 870 Structure of Management Information for version 2 of the 871 Simple Network Management Protocol (SNMPv2). Internet- 872 Draft, (December 22, 1992). | 874 [3] J.D. Case, K. McCloghrie, M.T. Rose, S.L. Waldbusser, 875 Protocol Operations for version 2 of the Simple Network 876 Management Protocol (SNMPv2). Internet-Draft, (December | 877 22, 1992). | 879 [4] J.D. Case, C. Partridge, Case Diagrams: A First Step to 880 Diagramed Management Information Bases. Computer 881 Communications Review, Volume 19, Number 1, (January, 882 1989). 884 [5] K. McCloghrie, J.R. Davin, J.M. Galvin, Party MIB for 885 version 2 of the Simple Network Management Protocol 886 (SNMPv2). Internet-Draft, (December 22, 1992). | 888 Draft Management Information Base for SNMPv2 Dec 92 890 Table of Contents 892 1 Introduction .......................................... 2 893 1.1 A Note on Terminology ............................... 2 894 2 Definitions ........................................... 3 895 3.1 The SNMPv2 Statistics Group ......................... 4 896 3.2 The SNMPv1 Statistics Group ......................... 9 897 3.3 The Object Resource Group ........................... 11 898 3.4 The Traps Group ..................................... 13 899 3.4.1 Well-known Traps .................................. 16 900 3.5 The Set Group ....................................... 18 901 3.6 Conformance Information ............................. 19 902 3.6.1 Compliance Statements ............................. 19 903 3.6.2 Units of Conformance .............................. 20 904 3 Acknowledgements ...................................... 22 905 4 References ............................................ 26