idnits 2.17.1 draft-ietf-disman-notif-log-mib-02.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. Expected boilerplate is as follows today (2024-04-27) 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 14 longer pages, the longest (page 11) being 61 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 15 pages 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 4 instances of too long lines in the document, the longest one being 5 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 73 has weird spacing: '...form of a loc...' -- 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 (13 March 1998) is 9542 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 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) Summary: 14 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Expires in 6 months 3 Notification Log MIB 5 13 March 1998 7 draft-ietf-disman-notif-log-mib-02.txt 9 Bob Stewart 10 Cisco Systems, Inc. 11 bstewart@cisco.com 13 Status of this Memo 15 This document is an Internet-Draft. Internet-Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its areas, and 17 its working groups. Note that other groups may also distribute working 18 documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet- Drafts as reference material 23 or to cite them other than as ``work in progress.'' 25 To learn the current status of any Internet-Draft, please check the 26 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 27 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 28 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 30 1. Abstract 32 This memo defines an experimental portion of the Management Information 33 Base (MIB) for use with network management protocols in the Internet 34 community. In particular, it describes managed objects used for logging 35 SNMP notifications. 37 2. The SNMP Network Management Framework 39 {The following boilerplate is out of date and will be replaced when 40 SNMPv3 boilerplate is available.} 42 The SNMP Network Management Framework presently consists of three major 43 components. They are: 45 the SMI, described in RFC 1902 [1] - the mechanisms used for 46 describing and naming objects for the purpose of management. 48 the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects for 49 the Internet suite of protocols. 51 the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for 52 accessing managed objects. 54 The Framework permits new objects to be defined for the purpose of 55 experimentation and evaluation. 57 2.1. Object Definitions 59 Managed objects are accessed via a virtual information store, termed the 60 Management Information Base or MIB. Objects in the MIB are defined 61 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 62 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 63 an administratively assigned name. The object type together with an 64 object instance serves to uniquely identify a specific instantiation of 65 the object. For human convenience, we often use a textual string, 66 termed the descriptor, to refer to the object type. 68 3. Overview 70 Systems that support SNMP need a common mechanism for recording 71 notification information as a hedge against lost Traps. 73 This MIB provides infrastructure for other MIBs in the form of a local 74 logging function. It is intended strictly for senders of notifications. 76 4. Definitions 78 NOTIFICATION-LOG-MIB DEFINITIONS ::= BEGIN 80 IMPORTS 81 MODULE-IDENTITY, OBJECT-TYPE, 82 experimental, Integer32, Unsigned32 83 Counter32, Counter64 FROM SNMPv2-SMI 84 TimeStamp, TruthValue FROM SNMPv2-TC 85 snmpNotifyTable FROM SNMP-NOTIFICATION-MIB 86 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 88 notificationLogMIB MODULE-IDENTITY 89 LAST-UPDATED "9703131700Z" 90 ORGANIZATION "IETF Distributed Management Working Group" 91 CONTACT-INFO "Bob Stewart 92 Cisco Systems, Inc. 93 170 West Tasman Drive, 94 San Jose CA 95134-1706. 95 Phone: +1 408 526 4527 96 Email: bstewart@cisco.com" 97 DESCRIPTION 98 "The MIB module for logging SNMP notifications, that is, Traps 99 and Informs." 100 ::= { experimental xx } 102 notificationLogMIBObjects OBJECT IDENTIFIER ::= { notificationLogMIB 1 } 104 nlmConfig OBJECT IDENTIFIER ::= { notificationLogMIBObjects 1 } 105 nlmStats OBJECT IDENTIFIER ::= { notificationLogMIBObjects 2 } 106 nlmLog OBJECT IDENTIFIER ::= { notificationLogMIBObjects 3 } 108 - -- 109 - -- Configuration Section 110 - -- 112 nlmConfigEntryLimit OBJECT-TYPE 113 SYNTAX Integer32 {-1..2147483647) 114 UNITS "entries" 115 MAX-ACCESS read-write 116 STATUS current 117 DESCRIPTION 118 "The maximum number of entries that can be held in nlmLogTable. 119 A value of -1 indicates no limit." 121 ::= { nlmConfig 1 } 123 - -- 124 - -- Notify Table Logging Control Column 125 - -- 127 nlmConfigNotifyTable OBJECT-TYPE 128 SYNTAX SEQUENCE OF nlmConfigNotifyEntry 129 MAX-ACCESS not-accessible 130 STATUS current 131 DESCRIPTION 132 "A column of logging control entries." 133 ::= { nlmLog 1 } 135 nlmConfigNotifyEntry OBJECT-TYPE 136 SYNTAX NlmConfigNotifyEntry 137 MAX-ACCESS not-accessible 138 STATUS current 139 DESCRIPTION 140 "A logging control entry." 141 AUGMENTS { snmpNotifyTable } 142 ::= { nlmLogTable 1 } 144 NlmConfigNotifyEntry ::= SEQUENCE { 145 nlmConfigNotifyLog TruthValue 146 } 148 nlmConfigNotifyLog OBJECT-TYPE 149 SYNTAX TruthValue 150 MAX-ACCESS read-create 151 STATUS current 152 DESCRIPTION 153 "Control for whether this notification is logged in nlmLogTable." 154 DEFVAL { false } 155 ::= { nlmConfigNotifyEntry 1 } 157 - -- 158 - -- Statisitics Section 159 - -- 161 nlmStatsNotificationsLogged OBJECT-TYPE 162 SYNTAX Counter32 163 UNITS "entries" 164 MAX-ACCESS read-only 165 STATUS current 166 DESCRIPTION 167 "The number of notifications put in the log." 168 ::= { nlmStats 1 } 170 nlmStatsEntriesDiscarded OBJECT-TYPE 171 SYNTAX Counter32 172 UNITS "entries" 173 MAX-ACCESS read-only 174 STATUS current 175 DESCRIPTION 176 "The number of times the oldest log entry was discarded to 177 make room for a new entry." 178 ::= { nlmStats 2 } 180 - -- 181 - -- Log Section 182 - -- 184 - -- 185 - -- Log Table 186 - -- 188 nlmLogTable OBJECT-TYPE 189 SYNTAX SEQUENCE OF nlmLogEntry 190 MAX-ACCESS not-accessible 191 STATUS current 192 DESCRIPTION 193 "A table of notification log entries." 194 ::= { nlmLog 1 } 196 nlmLogEntry OBJECT-TYPE 197 SYNTAX NlmLogEntry 198 MAX-ACCESS not-accessible 199 STATUS current 200 DESCRIPTION 201 "A notification log entry. 203 Entries appear in this table when notifications occur." 204 INDEX { nlmLogIndex } 205 ::= { nlmLogTable 1 } 207 NlmLogEntry ::= SEQUENCE { 208 nlmLogIndex Unsigned32, 209 nlmLogTime TimeStamp, 210 nlmLogNotificationID OBJECT IDENTIFIER 211 } 213 nlmLogIndex OBJECT-TYPE 214 SYNTAX Unsigned32 (1..4294967295) 215 MAX-ACCESS not-accessible 216 STATUS current 217 DESCRIPTION 218 "A monotonically increasing integer for the sole purpose of 219 indexing entries. When it reaches the maximum value, an 220 extremely unlikely event, the agent wraps the value back 221 to 1 and may flush existing entries." 222 ::= { nlmLogEntry 1 } 224 nlmLogTime OBJECT-TYPE 225 SYNTAX TimeTicks 226 MAX-ACCESS read-only 227 STATUS current 228 DESCRIPTION 229 "The value of sysUpTime when the entry occurred." 230 ::= { nlmLogEntry 2 } 232 nlmNotificationID OBJECT-TYPE 233 SYNTAX OCTET STRING 234 MAX-ACCESS not-accessible 235 STATUS current 236 DESCRIPTION 237 "The NOTIFICATION-TYPE object identifer of the notification that 238 occurred." 239 ::= { nlmLogEntry 3 } 241 - -- 242 - -- Log Variable Table 243 - -- 245 nlmLogVariableTable OBJECT-TYPE 246 SYNTAX SEQUENCE OF nlmLogVariableEntry 247 MAX-ACCESS not-accessible 248 STATUS current 249 DESCRIPTION 250 "A table of variables to go with notification log entries." 251 ::= { nlmLog 2 } 253 nlmLogVariableEntry OBJECT-TYPE 254 SYNTAX NlmLogVariableEntry 255 MAX-ACCESS not-accessible 256 STATUS current 257 DESCRIPTION 258 "A notification log entry variable. 260 Entries appear in this table when there are variables in 261 the varbind list of a notification in nlmLogTable." 262 INDEX { nlmLogIndex, nlmLogVariableIndex } 263 ::= { nlmLogVariableTable 1 } 265 NlmLogVariableEntry ::= SEQUENCE { 266 nlmLogVariableIndex Unsigned32, 267 nlmLogVariableID OBJECT IDENTIFIER, 268 nlmLogVariableType INTEGER, 269 nlmLogVariableCounter32Val Counter32, 270 nlmLogVariableUnsigned32Val Unsigned32, 271 nlmLogVariableInteger32Val Integer32, 272 nlmLogVariableOctetStringVal OCTET STRING, 273 nlmLogVariableOidVal OBJECT IDENTIFIER, 274 nlmLogVariableCounter64Val Counter64 275 } 277 nlmLogVariableIndex OBJECT-TYPE 278 SYNTAX Unsigned32 (1..4294967295) 279 MAX-ACCESS not-accessible 280 STATUS current 281 DESCRIPTION 282 "A arbitrary integer for the sole purpose of indexing entries." 283 ::= { nlmLogVariableEntry 1 } 285 nlmLogVariableID OBJECT-TYPE 286 SYNTAX OBJECT IDENTIFIER 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The variable's object identifier." 291 ::= { nlmLogVariableEntry 2 } 293 nlmLogVariableValueType OBJECT-TYPE 294 SYNTAX INTEGER { counter32(1), unsignedOrGauge32(2), 295 timeTicks(3), integer32(4), ipAddress(5), 296 octetString(6), objectId(7), counter64(8) } 297 MAX-ACCESS read-only 298 STATUS current 299 DESCRIPTION 300 "The type of the value. One and only one of the value 301 objects that follow will be valid based on this type." 302 ::= { nlmLogVariableEntry 3 } 304 nlmLogVariableCounter32Val OBJECT-TYPE 305 SYNTAX Counter32 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION 309 "The value when nlmLogVariableType is of 'counter32'." 310 ::= { nlmLogVariableEntry 4 } 312 nlmLogVariableUnsigned32Val OBJECT-TYPE 313 SYNTAX Unsigned32 314 MAX-ACCESS read-only 315 STATUS current 316 DESCRIPTION 317 "The value when nlmLogVariableType is one of 'unsignedOrGauge32' 318 or 'timeTicks'." 319 ::= { nlmLogVariableEntry 5 } 321 nlmLogVariableInteger32Val OBJECT-TYPE 322 SYNTAX Integer32 323 MAX-ACCESS read-only 324 STATUS current 325 DESCRIPTION 326 "The value when nlmLogVariableType is 'integer32'." 327 ::= { nlmLogVariableEntry 6 } 329 nlmLogVariableOctetStringVal OBJECT-TYPE 330 SYNTAX OCTET STRING 331 MAX-ACCESS read-only 332 STATUS current 333 DESCRIPTION 334 "The value when nlmLogVariableType is 'ipAddress' or 335 'octetString'." 336 ::= { nlmLogVariableEntry 7 } 338 nlmLogVariableOidVal OBJECT-TYPE 339 SYNTAX OBJECT IDENTIFIER 340 MAX-ACCESS read-only 341 STATUS current 342 DESCRIPTION 343 "The value when nlmLogVariableType is 'objectId'." 344 ::= { nlmLogVariableEntry 8 } 346 nlmLogVariableCounter64Val OBJECT-TYPE 347 SYNTAX Counter64 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The value when nlmLogVariableType is 'counter64'." 352 ::= { nlmLogVariableEntry 9 } 354 - -- 355 - -- Conformance 356 - -- 358 notificationLogMIBConformance OBJECT IDENTIFIER ::= { notificationLogMIB 3 } 359 notificationLogMIBCompliances OBJECT IDENTIFIER ::= { 360 notificationLogMIBConformance 1 } 361 notificationLogMIBGroups OBJECT IDENTIFIER ::= { 362 notificationLogMIBConformance 2 } 364 - -- Compliance 366 notificationLogMIBCompliance MODULE-COMPLIANCE 367 STATUS current 368 DESCRIPTION 369 "The compliance statement for entities which implement 370 the Expression MIB." 371 MODULE -- this module 372 MANDATORY-GROUPS { 373 notificationLogConfigGroup, 374 notificationLogStatsGroup, 375 notificationLogLogGroup 376 } 377 ::= { notificationLogMIBCompliances 1 } 379 - -- Units of Conformance 381 notificationLogConfigGroup OBJECT-GROUP 382 OBJECTS { 383 nlmConfigEntryLimit, 384 nlmConfigNotifyLog 385 } 386 STATUS current 387 DESCRIPTION 388 "Nofication log configuration management." 389 ::= { notificationLogMIBGroups 1 } 391 notificationLogStatsGroup OBJECT-GROUP 392 OBJECTS { 393 nlmStatsNotificationsLogged, 394 nlmStatsEntriesDiscarded 395 } 396 STATUS current 397 DESCRIPTION 398 "Nofication log statistics." 399 ::= { notificationLogMIBGroups 2 } 401 notificationLogLogGroup OBJECT-GROUP 402 OBJECTS { 403 nlmLogTime, 404 nlmLogNotificationID, 406 nlmLogVariableID, 407 nlmLogVariableType, 408 nlmLogVariableCounter32Val, 409 nlmLogVariableUnsigned32Val, 410 nlmLogVariableInteger32Val, 411 nlmLogVariableOctetStringVal, 412 nlmLogVariableOidVal, 413 nlmLogVariableCounter64Val 414 } 415 STATUS current 416 DESCRIPTION 417 "Nofication log data." 418 ::= { notificationLogMIBGroups 3 } 420 END 421 5. References 423 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 424 S. Waldbusser, "Structure of Management Information for version 2 425 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 426 January 1996. 428 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 429 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 430 RFC 1213, March 1991. 432 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 433 Management Protocol", RFC 1157, May 1990. 435 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 436 S. Waldbusser, "Protocol Operations for version 2 of the Simple 437 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 439 6. Security Considerations 441 Security issues are not discussed in this memo. 443 7. Author's Address 445 Bob Stewart 446 Cisco Systems, Inc. 447 170 West Tasman Drive 448 San Jose, CA 95134-1706 450 Phone: 408-526-4527 451 Email: bstewart@cisco.com 453 Table of Contents 455 1 Abstract ........................................................ 2 456 2 The SNMP Network Management Framework ........................... 3 457 2.1 Object Definitions ............................................ 3 458 3 Overview ........................................................ 4 459 4 Definitions ..................................................... 5 460 5 References ...................................................... 13 461 6 Security Considerations ......................................... 14 462 7 Author's Address ................................................ 14