idnits 2.17.1 draft-ietf-disman-notif-log-mib-03.txt: ** The Abstract section seems to be numbered 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. Found some kind of copyright notice around line 34 but it does not match any copyright boilerplate known by this tool. Expected boilerplate is as follows today (2024-04-26) 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 15) being 60 lines 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 7 instances of too long lines in the document, the longest one being 5 characters in excess of 72. 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 (31 July 1998) is 9401 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 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '15') (Obsoleted by RFC 2575) Summary: 24 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Notification Log MIB 3 31 July 1998 5 draft-ietf-disman-notif-log-mib-03.txt 7 Bob Stewart 8 Cisco Systems, Inc. 9 bstewart@cisco.com 11 Status of this Memo 13 This document is an Internet-Draft. Internet-Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its areas, and 15 its working groups. Note that other groups may also distribute working 16 documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet- Drafts as reference material 21 or to cite them other than as ``work in progress.'' 23 To view the entire list of current Internet-Drafts, please check the 24 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 25 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern Europe), 26 ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific Rim), 27 ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 29 Distribution of this document is unlimited. Please send comments to the 30 Distributed Management Working Group, . 32 Copyright Notice 34 Copyright (C) The Internet Society (1998). All Rights Reserved. 36 1. Abstract 38 This memo defines an experimental portion of the Management Information 39 Base (MIB) for use with network management protocols in the Internet 40 community. In particular, it describes managed objects used for logging 41 SNMP Notifications. 43 2. The SNMP Management Framework 45 The SNMP Management Framework presently consists of five major 46 components: 48 o An overall architecture, described in RFC 2271 [1]. 50 o Mechanisms for describing and naming objects and events for the 51 purpose of management. The first version of this Structure of 52 Management Information (SMI) is called SMIv1 and described in 53 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 54 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 55 1904 [7]. 57 o Message protocols for transferring management information. The 58 first version of the SNMP message protocol is called SNMPv1 and 59 described in RFC 1157 [8]. A second version of the SNMP message 60 protocol, which is not an Internet standards track protocol, is 61 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 62 The third version of the message protocol is called SNMPv3 and 63 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 65 o Protocol operations for accessing management information. The 66 first set of protocol operations and associated PDU formats is 67 described in RFC 1157 [8]. A second set of protocol operations 68 and associated PDU formats is described in RFC 1905 [13]. 70 o A set of fundamental applications described in RFC 2273 [14] and 71 the view-based access control mechanism described in RFC 2275 72 [15]. 74 Managed objects are accessed via a virtual information store, termed the 75 Management Information Base or MIB. Objects in the MIB are defined 76 using the mechanisms defined in the SMI. 78 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 79 conforming to the SMIv1 can be produced through the appropriate 80 translations. The resulting translated MIB must be semantically 81 equivalent, except where objects or events are omitted because no 82 translation is possible (use of Counter64). Some machine readable 83 information in SMIv2 will be converted into textual descriptions in 84 SMIv1 during the translation process. However, this loss of machine 85 readable information is not considered to change the semantics of the 86 MIB. 88 3. Overview 90 Systems that support SNMP often need a mechanism for recording 91 Notification information as a hedge against lost Notifications, whether 92 those are Traps or Informs that exceed retransmission limits. This MIB 93 therefore provides common infrastructure for other MIBs in the form of a 94 local logging function. It is intended primarily for senders of 95 Notifications but could be used also by receivers. 97 Given the Notification Log MIB, individual MIBs bear less responsibility 98 to record the transient information associated with an event against the 99 possibility that the Notification message is lost, and applications can 100 poll the log to know that they have not missed important Notifications 101 or to suspect that they might have. 103 3.1. Environment 105 The overall environmental concerns for the MIB are: 107 o SNMP Engines and Contexts 109 o Security 111 3.1.1. SNMP Engines and Contexts 113 As described in the SNMPv3 architecture [1], a given system may support 114 multiple SNMP engines operating independently of one another, each with 115 its own SNMP engine identification. Furthermore, within the perview of 116 a given engine there may be multiple named management contexts 117 supporting overlapping or disjoint sets of MIB objects and 118 Notifications. Thus understanding a particular Notification requires 119 knowing the SNMP engine and management context from whence it came. 121 The simplest system may have only one SNMP engine, and the simplest 122 engine may support only one context. In these cases, knowledge of the 123 engine ID and context name can be assumed and need not be explicit. 125 In a given implementation, an instance of the Notification Log MIB may 126 be confined to a single engine or context or may combine information 127 from multiple engines or contexts, allowing for the full range of 128 exclusive or inclusive contents. 130 To provide the necessary source information for a logged Notification, 131 the MIB includes objects to record that Notification's source SNMP 132 engine ID and management context name. In the case where such 133 information can be assumed, the related object need not be instantiated, 134 thus allowing the simplest implemenetation for the simplest system. 136 3.1.2. Security 138 Except for the log itself security of this MIB falls under normal SNMP 139 security policies. 141 For the log, Notifications containing objects not within a requester's 142 authorized view will appear not to exist, thus causing apparent holes in 143 the log index space. 145 If the log contains Notifications from SNMP engines not part of the 146 local system, those Notifications fall under the overall local access 147 policy for the log. 149 3.2. Structure 151 The MIB has the following sections: 153 o Configuration -- control over how much the log can hold and what 154 Notifications are to be logged. 156 o Statistics -- indications of logging activity. 158 o Log -- the Notifications themselves. 160 3.2.1. Configuration 162 The configuration section contains objects to manage resource use by the 163 MIB in units of either bytes or entries. 165 This section also contains a table that uses the initial index 166 (snmpNotifyFilterName) from the snmpNotifyFilterTable in the standard 167 SNMP Notification MIB, using those filters to provide a means of 168 deciding which Notifications are to be logged. 170 3.2.2. Statistics 172 The statistics section contains counters for Notifications logged and 173 discarded, supplying a means to understand the results of log capacity 174 configuration. 176 3.2.3. Log 178 The log contains the Notifications and the objects that came in their 179 variable binding list, indexed by an integer that reflects when the 180 entry was made. An application that wants to collect all logged 181 Notifications or to know if it may have missed any can keep track of the 182 highest index it has retrieved and start from there on its next poll, 183 checking sysUpTime for a discontinuity that would have reset the index 184 and perhaps have lost entries. 186 Variables are in a table indexed by Notification index and variable 187 index within that Notification. The values are kept as a "discriminated 188 union," with one value object per variable. Exactly which value object 189 is instantiated depends on the SNMP data type of the variable, with a 190 separate object of appropriate type for each distinct SNMP data type. 192 An application can thus reconstruct the information from the 193 Notification PDU from what is recorded in the log. 195 4. Definitions 197 NOTIFICATION-LOG-MIB DEFINITIONS ::= BEGIN 199 IMPORTS 200 MODULE-IDENTITY, OBJECT-TYPE, 201 experimental, Integer32, Unsigned32, 202 TimeTicks, Counter32, Counter64, 203 IpAddress FROM SNMPv2-SMI 204 TimeStamp, TruthValue, 205 StorageType FROM SNMPv2-TC 206 SnmpAdminString, SnmpEngineID FROM SNMP-FRAMEWORK-MIB 207 snmpNotifyFilterProfileName FROM SNMP-NOTIFICATION-MIB 208 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 210 notificationLogMIB MODULE-IDENTITY 211 LAST-UPDATED "9807311700Z" 212 ORGANIZATION "IETF Distributed Management Working Group" 213 CONTACT-INFO "Bob Stewart 214 Cisco Systems, Inc. 215 170 West Tasman Drive, 216 San Jose CA 95134-1706. 217 Phone: +1 408 526 4527 218 Email: bstewart@cisco.com" 219 DESCRIPTION 220 "The MIB module for logging SNMP Notifications, that is, Traps 221 and Informs." 222 ::= { experimental xx } 224 notificationLogMIBObjects OBJECT IDENTIFIER ::= { notificationLogMIB 1 } 226 nlmConfig OBJECT IDENTIFIER ::= { notificationLogMIBObjects 1 } 227 nlmStats OBJECT IDENTIFIER ::= { notificationLogMIBObjects 2 } 228 nlmLog OBJECT IDENTIFIER ::= { notificationLogMIBObjects 3 } 230 -- 231 -- Configuration Section 232 -- 234 nlmConfigEntryLimitUnits OBJECT-TYPE 235 SYNTAX INTEGER { entries(1), bytes(2) } 236 MAX-ACCESS read-write 237 STATUS current 238 DESCRIPTION 239 "The units for nlmConfigEntryLimit. See nlmConfigEntryLimit for 240 further details. 242 Implementations may allow choice of unit types or may chose 243 either unit type and not allow it to be changed." 244 ::= { nlmConfig 1 } 246 nlmConfigEntryLimit OBJECT-TYPE 247 SYNTAX Unsigned32 248 MAX-ACCESS read-write 249 STATUS current 250 DESCRIPTION 251 "The maximum number of entries or bytes that can be held in 252 nlmLogTable. 254 If an application changes the limit while there are Notifications 255 in the log, the oldest Notifications are discarded to bring the 256 log down to the new limit. 258 Measuring in bytes is not necessarily subject to exact external 259 calculations as to what will fit, as the implementation may or 260 may not include internal overhead and is free to use any internal 261 incoding. 263 Implementations may choose a limit and not allow it to be 264 changed or may enforce an upper bound on the limit." 265 ::= { nlmConfig 2 } 267 -- 268 -- Notify Table Logging Control Table 269 -- 271 nlmConfigLogControlTable OBJECT-TYPE 272 SYNTAX SEQUENCE OF NlmConfigLogControlEntry 273 MAX-ACCESS not-accessible 274 STATUS current 275 DESCRIPTION 276 "A table of logging control entries, related to filter profiles 277 from the SNMP Notification MIB." 278 ::= { nlmConfig 3 } 280 nlmConfigLogControlEntry OBJECT-TYPE 281 SYNTAX NlmConfigLogControlEntry 282 MAX-ACCESS not-accessible 283 STATUS current 284 DESCRIPTION 285 "A logging control entry. Depending on the entry's storage type 286 entries may be supplied by the system or created and deleted by 287 applications using nlmConfigLogControlStatus." 288 INDEX { snmpNotifyFilterProfileName } 289 ::= { nlmConfigNotifyTable 1 } 291 NlmConfigLogControlEntry ::= SEQUENCE { 292 nlmConfigLogControlLog TruthValue, 293 nlmConfigLogControlStorageType StorageType, 294 nlmConfigLogControlStatus RowStatus 295 } 297 nlmConfigLogControlLog OBJECT-TYPE 298 SYNTAX TruthValue 299 MAX-ACCESS read-create 300 STATUS current 301 DESCRIPTION 302 "Control for whether this set of Notifications is logged in 303 nlmLogTable." 304 DEFVAL { false } 305 ::= { nlmConfigLogControlEntry 1 } 307 nlmConfigLogControlStorageType OBJECT-TYPE 308 SYNTAX StorageType 309 MAX-ACCESS read-create 310 STATUS current 311 DESCRIPTION 312 "The storage type of this conceptual row." 313 DEFVAL { false } 314 ::= { nlmConfigLogControlEntry 2 } 316 nlmConfigLogControlStatus OBJECT-TYPE 317 SYNTAX RowStatus 318 MAX-ACCESS read-create 319 STATUS current 320 DESCRIPTION 321 "Control for creating and deleting entries. Entries may be 322 modified while active." 323 DEFVAL { createAndWait } 324 ::= { nlmConfigLogControlEntry 3 } 326 -- 327 -- Statisitics Section 328 -- 329 nlmStatsNotificationsLogged OBJECT-TYPE 330 SYNTAX Counter32 331 UNITS "entries" 332 MAX-ACCESS read-only 333 STATUS current 334 DESCRIPTION 335 "The number of Notifications put in the nlmLogTable." 336 ::= { nlmStats 1 } 338 nlmStatsEntriesDiscarded OBJECT-TYPE 339 SYNTAX Counter32 340 UNITS "entries" 341 MAX-ACCESS read-only 342 STATUS current 343 DESCRIPTION 344 "The number of log entries discarded to make room for a new 345 entry or because of a change in nlmConfigEntryLimitUnits or 346 nlmConfigEntryLimit." 347 ::= { nlmStats 2 } 349 -- 350 -- Log Section 351 -- 353 -- 354 -- Log Table 355 -- 357 nlmLogTable OBJECT-TYPE 358 SYNTAX SEQUENCE OF NlmLogEntry 359 MAX-ACCESS not-accessible 360 STATUS current 361 DESCRIPTION 362 "A table of Notification log entries. 364 It is an implementation-specific matter whether entries in this 365 table are preserved across initializations of the management 366 system. In general one would expect that they are not." 367 ::= { nlmLog 1 } 369 nlmLogEntry OBJECT-TYPE 370 SYNTAX NlmLogEntry 371 MAX-ACCESS not-accessible 372 STATUS current 373 DESCRIPTION 374 "A Notification log entry. 376 Entries appear in this table when Notifications occur and are 377 enabled for logging by nlmConfigNotifyLog. They are removed to 378 make way for new entries or in response to an application 379 setting nlmConfigEntryLimit or nlmConfigEntryLimitUnits to 380 reduce capacity." 381 INDEX { nlmLogIndex } 382 ::= { nlmLogTable 1 } 384 NlmLogEntry ::= SEQUENCE { 385 nlmLogIndex Unsigned32, 386 nlmLogTime TimeStamp, 387 nlmLogEngineID SnmpEngineID, 388 nlmLogContextName SnmpAdminString, 389 nlmLogVariables Unsigned32, 390 nlmLogNotificationID OBJECT IDENTIFIER 391 } 393 nlmLogIndex OBJECT-TYPE 394 SYNTAX Unsigned32 (1..4294967295) 395 MAX-ACCESS not-accessible 396 STATUS current 397 DESCRIPTION 398 "A monotonically increasing integer for the sole purpose of 399 indexing entries. When it reaches the maximum value, an 400 extremely unlikely event, the agent wraps the value back 401 to 1 and may flush existing entries." 402 ::= { nlmLogEntry 1 } 404 nlmLogTime OBJECT-TYPE 405 SYNTAX TimeStamp 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "The value of sysUpTime when the entry occurred." 410 ::= { nlmLogEntry 2 } 412 nlmLogEngineID OBJECT-TYPE 413 SYNTAX SnmpEngineID 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The identification of the SNMP engine at which the Notification 418 originated. 420 If the log can contain Notifications from only one engine this 421 object need not be instantiated." 422 ::= { nlmLogEntry 3 } 424 nlmLogContextName OBJECT-TYPE 425 SYNTAX SnmpAdminString 426 MAX-ACCESS read-only 427 STATUS current 428 DESCRIPTION 429 "The name of the SNMP MIB context from which the Notification 430 came. 432 If the Notification's source SNMP engine does not support 433 multiple contexts, this object need not be instantiated." 434 ::= { nlmLogEntry 4 } 436 nlmLogVariables OBJECT-TYPE 437 SYNTAX Unsigned32 438 MAX-ACCESS read-only 439 STATUS current 440 DESCRIPTION 441 "The number of variables in nlmLogVariableTable for this 442 Notification." 443 ::= { nlmLogEntry 5 } 445 nlmLogNotificationID OBJECT-TYPE 446 SYNTAX OBJECT IDENTIFIER 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "The NOTIFICATION-TYPE object identifer of the Notification that 451 occurred." 452 ::= { nlmLogEntry 6 } 454 -- 455 -- Log Variable Table 456 -- 458 nlmLogVariableTable OBJECT-TYPE 459 SYNTAX SEQUENCE OF NlmLogVariableEntry 460 MAX-ACCESS not-accessible 461 STATUS current 462 DESCRIPTION 463 "A table of variables to go with Notification log entries." 464 ::= { nlmLog 2 } 466 nlmLogVariableEntry OBJECT-TYPE 467 SYNTAX NlmLogVariableEntry 468 MAX-ACCESS not-accessible 469 STATUS current 470 DESCRIPTION 471 "A Notification log entry variable. 473 Entries appear in this table when there are variables in 474 the varbind list of a Notification in nlmLogTable." 475 INDEX { nlmLogIndex, nlmLogVariableIndex } 476 ::= { nlmLogVariableTable 1 } 478 NlmLogVariableEntry ::= SEQUENCE { 479 nlmLogVariableIndex Unsigned32, 480 nlmLogVariableID OBJECT IDENTIFIER, 481 nlmLogVariableValueType INTEGER, 482 nlmLogVariableCounter32Val Counter32, 483 nlmLogVariableUnsigned32Val Unsigned32, 484 nlmLogVariableTimeTicksVal TimeTicks, 485 nlmLogVariableInteger32Val Integer32, 486 nlmLogVariableOctetStringVal OCTET STRING, 487 nlmLogVariableIpAddressVal IpAddress, 488 nlmLogVariableOidVal OBJECT IDENTIFIER, 489 nlmLogVariableCounter64Val Counter64 490 } 492 nlmLogVariableIndex OBJECT-TYPE 493 SYNTAX Unsigned32 (1..4294967295) 494 MAX-ACCESS not-accessible 495 STATUS current 496 DESCRIPTION 497 "A monotonically increasing integer, starting at 1 for a given 498 nlmLogIndex, for indexing variables within the logged Notification." 499 ::= { nlmLogVariableEntry 1 } 501 nlmLogVariableID OBJECT-TYPE 502 SYNTAX OBJECT IDENTIFIER 503 MAX-ACCESS read-only 504 STATUS current 505 DESCRIPTION 506 "The variable's object identifier." 507 ::= { nlmLogVariableEntry 2 } 509 nlmLogVariableValueType OBJECT-TYPE 510 SYNTAX INTEGER { counter32(1), unsignedOrGauge32(2), 511 timeTicks(3), integer32(4), ipAddress(5), 512 octetString(6), objectId(7), counter64(8) } 513 MAX-ACCESS read-only 514 STATUS current 515 DESCRIPTION 516 "The type of the value. One and only one of the value 517 objects that follow is instantiated, based on this type." 518 ::= { nlmLogVariableEntry 3 } 520 nlmLogVariableCounter32Val OBJECT-TYPE 521 SYNTAX Counter32 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "The value when nlmLogVariableType is 'counter32'." 526 ::= { nlmLogVariableEntry 4 } 528 nlmLogVariableUnsigned32Val OBJECT-TYPE 529 SYNTAX Unsigned32 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION 533 "The value when nlmLogVariableType is 'unsignedOrGauge32'." 534 ::= { nlmLogVariableEntry 5 } 536 nlmLogVariableTimeTicksVal OBJECT-TYPE 537 SYNTAX TimeTicks 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "The value when nlmLogVariableType is 'timeTicks'." 542 ::= { nlmLogVariableEntry 6 } 544 nlmLogVariableInteger32Val OBJECT-TYPE 545 SYNTAX Integer32 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "The value when nlmLogVariableType is 'integer32'." 550 ::= { nlmLogVariableEntry 7 } 552 nlmLogVariableOctetStringVal OBJECT-TYPE 553 SYNTAX OCTET STRING 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "The value when nlmLogVariableType is 'octetString'." 558 ::= { nlmLogVariableEntry 8 } 560 nlmLogVariableIpAddressVal OBJECT-TYPE 561 SYNTAX IpAddress 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "The value when nlmLogVariableType is 'ipAddress'." 566 ::= { nlmLogVariableEntry 9 } 568 nlmLogVariableOidVal OBJECT-TYPE 569 SYNTAX OBJECT IDENTIFIER 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "The value when nlmLogVariableType is 'objectId'." 574 ::= { nlmLogVariableEntry 10 } 576 nlmLogVariableCounter64Val OBJECT-TYPE 577 SYNTAX Counter64 578 MAX-ACCESS read-only 579 STATUS current 580 DESCRIPTION 581 "The value when nlmLogVariableType is 'counter64'." 582 ::= { nlmLogVariableEntry 11 } 584 -- 585 -- Conformance 586 -- 588 notificationLogMIBConformance OBJECT IDENTIFIER ::= { notificationLogMIB 3 } 589 notificationLogMIBCompliances OBJECT IDENTIFIER ::= { 590 notificationLogMIBConformance 1 } 591 notificationLogMIBGroups OBJECT IDENTIFIER ::= { 592 notificationLogMIBConformance 2 } 594 -- Compliance 596 notificationLogMIBCompliance MODULE-COMPLIANCE 597 STATUS current 598 DESCRIPTION 599 "The compliance statement for entities which implement 600 the Notification Log MIB." 601 MODULE -- this module 602 MANDATORY-GROUPS { 603 notificationLogConfigGroup, 604 notificationLogStatsGroup, 605 notificationLogLogGroup 606 } 607 ::= { notificationLogMIBCompliances 1 } 609 -- Units of Conformance 611 notificationLogConfigGroup OBJECT-GROUP 612 OBJECTS { 613 nlmConfigEntryLimitUnits, 614 nlmConfigEntryLimit, 615 nlmConfigNotifyLog 616 } 617 STATUS current 618 DESCRIPTION 619 "Notification log configuration management." 620 ::= { notificationLogMIBGroups 1 } 622 notificationLogStatsGroup OBJECT-GROUP 623 OBJECTS { 624 nlmStatsNotificationsLogged, 625 nlmStatsEntriesDiscarded 626 } 627 STATUS current 628 DESCRIPTION 629 "Notification log statistics." 630 ::= { notificationLogMIBGroups 2 } 632 notificationLogLogGroup OBJECT-GROUP 633 OBJECTS { 634 nlmLogTime, 635 nlmLogEngineID, 636 nlmLogContextName, 637 nlmLogVariables, 638 nlmLogNotificationID, 640 nlmLogVariableID, 641 nlmLogVariableValueType, 642 nlmLogVariableCounter32Val, 643 nlmLogVariableUnsigned32Val, 644 nlmLogVariableTimeTicksVal, 645 nlmLogVariableInteger32Val, 646 nlmLogVariableOctetStringVal, 647 nlmLogVariableIpAddressVal, 648 nlmLogVariableOidVal, 649 nlmLogVariableCounter64Val 650 } 651 STATUS current 652 DESCRIPTION 653 "Notification log data." 654 ::= { notificationLogMIBGroups 3 } 656 END 657 5. References 659 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 660 Describing SNMP Management Frameworks", RFC 2271, Cabletron 661 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 662 January 1998 664 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 665 Management Information for TCP/IP-based Internets", RFC 1155, 666 Performance Systems International, Hughes LAN Systems, May 1990 668 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 669 Performance Systems International, Hughes LAN Systems, March 1991 671 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 672 RFC 1215, Performance Systems International, March 1991 674 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 675 of Management Information for Version 2 of the Simple Network 676 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 677 Systems, Inc., Dover Beach Consulting, Inc., International Network 678 Services, January 1996. 680 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 681 Conventions for Version 2 of the Simple Network Management Protocol 682 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 683 Dover Beach Consulting, Inc., International Network Services, 684 January 1996. 686 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance 687 Statements for Version 2 of the Simple Network Management Protocol 688 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 689 Dover Beach Consulting, Inc., International Network Services, 690 January 1996. 692 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 693 Management Protocol", RFC 1157, SNMP Research, Performance Systems 694 International, Performance Systems International, MIT Laboratory 695 for Computer Science, May 1990. 697 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 698 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 699 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 700 International Network Services, January 1996. 702 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 703 Mappings for Version 2 of the Simple Network Management Protocol 704 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 705 Dover Beach Consulting, Inc., International Network Services, 706 January 1996. 708 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 709 Processing and Dispatching for the Simple Network Management 710 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 711 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 713 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 714 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 715 2274, IBM T. J. Watson Research, January 1998. 717 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 718 Operations for Version 2 of the Simple Network Management Protocol 719 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 720 Dover Beach Consulting, Inc., International Network Services, 721 January 1996. 723 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 724 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 725 Systems, January 1998 727 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 728 Control Model (VACM) for the Simple Network Management Protocol 729 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 730 Cisco Systems, Inc., January 1998 732 6. Security Considerations 734 Security issues are discussed in the overview. 736 7. Author's Address 738 Bob Stewart 739 Cisco Systems, Inc. 740 170 West Tasman Drive 741 San Jose, CA 95134-1706 743 Phone: 408-526-4527 744 Email: bstewart@cisco.com 746 Table of Contents 748 1 Abstract ........................................................ 2 749 2 The SNMP Management Framework ................................... 2 750 3 Overview ........................................................ 4 751 3.1 Environment ................................................... 4 752 3.1.1 SNMP Engines and Contexts ................................... 4 753 3.1.2 Security .................................................... 5 754 3.2 Structure ..................................................... 5 755 3.2.1 Configuration ............................................... 5 756 3.2.2 Statistics .................................................. 6 757 3.2.3 Log ......................................................... 6 758 4 Definitions ..................................................... 7 759 5 References ...................................................... 18 760 6 Security Considerations ......................................... 20 761 7 Author's Address ................................................ 20