idnits 2.17.1 draft-ietf-disman-event-mib-04.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 37 but it does not match any copyright boilerplate known by this tool. 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 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 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 8 instances of too long lines in the document, the longest one being 4 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 (5 August 1998) is 9397 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) ** Obsolete normative reference: RFC 1757 (ref. '16') (Obsoleted by RFC 2819) ** Downref: Normative reference to an Historic RFC: RFC 1451 (ref. '17') -- Possible downref: Non-RFC (?) normative reference: ref. '18' -- Possible downref: Non-RFC (?) normative reference: ref. '19' Summary: 25 errors (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Event MIB 5 August 1998 4 Event MIB 6 5 August 1998 8 draft-ietf-disman-event-mib-04.txt 10 Bob Stewart 11 Cisco Systems, Inc. 12 bstewart@cisco.com 14 Status of this Memo 16 This document is an Internet-Draft. Internet-Drafts are working 17 documents of the Internet Engineering Task Force (IETF), its areas, and 18 its working groups. Note that other groups may also distribute working 19 documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet- Drafts as reference material 24 or to cite them other than as ``work in progress.'' 26 To view the entire list of current Internet-Drafts, please check the 27 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 28 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern Europe), 29 ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific Rim), 30 ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 32 Distribution of this document is unlimited. Please send comments to the 33 Distributed Management Working Group, . 35 Copyright Notice 37 Copyright (C) The Internet Society (1998). All Rights Reserved. 39 1. Abstract 41 This memo defines an experimental portion of the Management Information 42 Base (MIB) for use with network management protocols in the Internet 43 community. In particular, it describes managed objects used for 44 managing monitoring of MIB objects and taking action through events. 46 2. The SNMP Management Framework 48 The SNMP Management Framework presently consists of five major 49 components: 51 o An overall architecture, described in RFC 2271 [1]. 53 o Mechanisms for describing and naming objects and events for the 54 purpose of management. The first version of this Structure of 55 Management Information (SMI) is called SMIv1 and described in 56 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 57 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 58 1904 [7]. 60 o Message protocols for transferring management information. The 61 first version of the SNMP message protocol is called SNMPv1 and 62 described in RFC 1157 [8]. A second version of the SNMP message 63 protocol, which is not an Internet standards track protocol, is 64 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 65 The third version of the message protocol is called SNMPv3 and 66 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 68 o Protocol operations for accessing management information. The 69 first set of protocol operations and associated PDU formats is 70 described in RFC 1157 [8]. A second set of protocol operations 71 and associated PDU formats is described in RFC 1905 [13]. 73 o A set of fundamental applications described in RFC 2273 [14] and 74 the view-based access control mechanism described in RFC 2275 75 [15]. 77 Managed objects are accessed via a virtual information store, termed the 78 Management Information Base or MIB. Objects in the MIB are defined 79 using the mechanisms defined in the SMI. 81 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 82 conforming to the SMIv1 can be produced through the appropriate 83 translations. The resulting translated MIB must be semantically 84 equivalent, except where objects or events are omitted because no 85 translation is possible (use of Counter64). Some machine readable 86 information in SMIv2 will be converted into textual descriptions in 87 SMIv1 during the translation process. However, this loss of machine 88 readable information is not considered to change the semantics of the 89 MIB. 91 3. Overview 93 With network sizes well beyond the ability of people to management their 94 networks directly automated, distributed management is vital. An 95 important aspect of such management is the ability of a system to 96 monitor itself or for some other system to monitor it. 98 The Event MIB provides the ability to monitor MIB objects on the local 99 system or on a remote system and take simple action when a trigger 100 condition is met. 102 All of these components must suit either a relatively powerful manager 103 or mid-level manager, as well as a somewhat more limited self-managing 104 system. 106 4. Relationship to Other MIBs 108 The Event MIB is based on extensive experience with the RMON MIB [16] 109 and its alarm and event groups and is intended as a replacement for 110 those groups. The Event MIB calls "triggers" what the RMON MIB called 111 "alarms," but the concepts are the same. Event MIB triggers maintain 112 the RMON handling of thresholds and add the concept of booleans. Event 113 MIB events maintain the RMON concept of sending an SNMP notification in 114 response to a trigger and add the concept of setting a MIB object. 116 The Event MIB is the successor and update to SNMPv2's Manager-to-Manager 117 MIB [17] which was declared Historic pending this work. 119 The Event MIB depends on the services of the SNMPv3 Management Target 120 and Notification MIBs [14]. 122 The Event MIB is nicely complemented by the Distributed Management 123 Expression MIB [18], which is the expected source of boolean objects to 124 monitor. 126 5. MIB Sections 128 The MIB has three sections, triggers, events, and notifications. 129 Triggers define the conditions that lead to events. Events may cause 130 notifications. 132 The trigger table lists what objects are to be monitored and how and 133 relates each trigger to an event. In the same section the trigger 134 object table lists trigger-related objects that can be added to 135 notifications either for a trigger or for an event. 137 The event table defines what happens when an event is triggered, sending 138 a notificaiton, setting a MIB object or both. 140 The notification section defines a set of generic notifications to go 141 with the events and for Event MIB error handlling, and it defines a set 142 of objects to put in those notifications. 144 6. Operation 146 The Event MIB is instrumentation for a distributed management 147 application that monitors MIB objects. In its simplest form this 148 application monitors individual, local MIB objects, just as an RMON 149 probe fulfills the functions implied by RMON's alarm and event 150 operation. Additionally the application can monitor remote objects and 151 wildcarded groups of objects. 153 Remote monitoring uses the tag service of the Management Target MIB to 154 select and access remote systems as an ordinary SNMP-based management 155 application. Local monitoring may be be a more intimate, local 156 interface which may, for example, bypass SNMP formatting but otherwise 157 is functionally identical to remote SNMP operation. A self-management 158 only system may not implemenet remote monitoring. 160 Wildcards indicate that the application should use a GetNext-type 161 operation to find the zero or more instances implied by a truncated 162 object identifier, just like an ordinary SNMP-based management 163 application. 165 Error handling is by notification, which at first thought violates the 166 principle that notifications may be lost or become a crippling burden, 167 but the intent is that such error notifications be enabled only for the 168 diagnosis of problems indicated by error counters and if the 169 notifications are being lost they be directed to the log as described in 170 the Notification Log MIB [19]. 172 7. Security 174 Security of Event MIB entries depends on SNMPv3 access control for the 175 entire MIB or for subsets based on substrings of trigger and event 176 names. 178 Security of monitored objects for remote access depends on the 179 Management Target MIB. Security for local access can depend on the 180 Management Target MIB or on recording appropriate security credentials 181 of the creator of an entry and using those to access the local objects. 183 8. Definitions 185 EVENT-MIB DEFINITIONS ::= BEGIN 187 IMPORTS 188 MODULE-IDENTITY, OBJECT-TYPE, 189 experimental, Integer32, Unsigned32 190 NOTIFICATION-TYPE FROM SNMPv2-SMI 191 TEXTUAL-CONVENTION, RowStatus, 192 TimeStamp, DisplayString FROM SNMPv2-TC 193 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 194 SnmpTagValue FROM SNMP-TARGET-MIB 195 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 197 eventMIB MODULE-IDENTITY 198 LAST-UPDATED "9808051700Z" 199 ORGANIZATION "IETF Distributed Management Working Group" 200 CONTACT-INFO "Bob Stewart 201 Cisco Systems, Inc. 202 170 West Tasman Drive, 203 San Jose CA 95134-1706. 204 Phone: +1 408 526 4527 205 Email: bstewart@cisco.com" 206 DESCRIPTION 207 "The MIB module for defining event triggers and actions 208 for network management purposes." 209 ::= { experimental xx } 211 eventMIBObjects OBJECT IDENTIFIER ::= { eventMIB 1 } 213 mteTrigger OBJECT IDENTIFIER ::= { eventMIBObjects 1 } 214 mteEvent OBJECT IDENTIFIER ::= { eventMIBObjects 2 } 216 -- 217 -- Textual Conventions 218 -- 220 FailureReason ::= TEXTUAL-CONVENTION 221 STATUS current 222 DESCRIPTION 223 "Reasons for failures in an attempt to send a management message. 225 The first group of errors, numbered less than 100, are copied 226 directly from SNMP protocol operations and are intended to carry 227 exactly the meanings defined for the protocol as returned in 228 an SNMP response. Those numbered 100 or greater are related 229 to problems in sending the request." 230 SYNTAX INTEGER { tooBig(1), 231 noSuchName(2), 232 badValue(3), 233 readOnly(4), 234 genErr(5), 235 noAccess(6), 236 wrongType(7), 237 wrongLength(8), 238 wrongEncoding(9), 239 wrongValue(10), 240 noCreation(11), 241 inconsistentValue(12), 242 resourceUnavailable(13), 243 commitFailed(14), 244 undoFailed(15), 245 authorizationError(16), 246 notWritable(17), 247 inconsistentName(18), 249 localResourceLack(101), 250 badDestination(102), 251 noAck(103) } 253 -- 254 -- Trigger Section 255 -- 257 -- Counters 259 mteTriggerFailures OBJECT-TYPE 260 SYNTAX Counter32 261 MAX-ACCESS read-only 262 STATUS current 263 DESCRIPTION 264 "The number of times an attempt to check for a trigger 265 condition has failed. This counts individually for each 266 attempt in a group of targets or each attempt for a 267 wildcarded object." 268 ::= { mteTrigger 1 } 270 -- 271 -- Trigger Table 272 -- 274 mteTriggerTable OBJECT-TYPE 275 SYNTAX SEQUENCE OF MteTriggerEntry 276 MAX-ACCESS not-accessible 277 STATUS current 278 DESCRIPTION 279 "A table of management event trigger information." 280 ::= { mteTrigger 2 } 282 mteTriggerEntry OBJECT-TYPE 283 SYNTAX MteTriggerEntry 284 MAX-ACCESS not-accessible 285 STATUS current 286 "Information about a single trigger. Applications create and 287 delete entries using mteTriggerStatus." 288 INDEX { IMPLIED mteTriggerName } 289 ::= { mteTriggerteble 1 } 291 MteTriggerEntry ::= SEQUENCE { 292 mteTriggerName SnmpAdminString, 293 mteTriggerComment DisplayString, 294 mteTriggerTest INTEGER, 295 mteTriggerValueID Integer32, 296 mteTriggerValueIDWildcard TruthValue, 297 mteTriggerTargetTag SnmpTagValue, 298 mteTriggerContextName SnmpAdminString, 299 mteTriggerContextNameWildcard TruthValue, 300 mteTriggerFrequency Integer32, 301 mteTriggerBooleanStartup INTEGER, 302 mteTriggerThresholdStartup INTEGER, 303 mteTriggerRisingThreshold Integer32, 304 mteTriggerFallingThreshold Integer32, 305 mteTriggerEvent SnmpAdminString, 306 mteTriggerRisingEvent SnmpAdminString, 307 mteTriggerFallingEvent SnmpAdminString, 308 mteTriggerObjects SnmpAdminString, 309 mteTriggerStatus RowStatus 310 } 312 mteTriggerName OBJECT-TYPE 313 SYNTAX SnmpAdminString (SIZE (1..64)) 314 MAX-ACCESS not-accessible 315 STATUS current 316 DESCRIPTION 317 "A locally-unique, administratively assigned name for the trigger." 318 ::= { mteTriggerEntry 1 } 320 mteTriggerComment OBJECT-TYPE 321 SYNTAX DisplayString 322 MAX-ACCESS read-create 323 STATUS current 324 DESCRIPTION 325 "A description of the trigger's function and use." 326 DEFVAL { ''H } 327 ::= { mteTriggerEntry 2 } 329 mteTriggerTest OBJECT-TYPE 330 SYNTAX INTEGER { boolean(1), threshold(2) } 331 MAX-ACCESS read-create 332 STATUS current 333 DESCRIPTION 334 "The type of trigger test to perform. For all tests, 335 mteTriggerValue must evaluate to an integer. 337 For 'boolean', a value of 0 is false. A non-zero value 338 is true and fires the trigger. The trigger will not fire 339 again until the value has become false and come back to 340 true. 342 For 'threshold' it works as described below for 343 mteTriggerThresholdStartup, mteTriggerRisingThreshold, and 344 mteTriggerFallingThreshold." 345 DEFVAL { boolean } 346 ::= { mteTriggerEntry 3 } 348 mteTriggerValueID OBJECT-TYPE 349 SYNTAX OBJECT IDENTIFIER 350 MAX-ACCESS read-create 351 STATUS current 352 DESCRIPTION 353 "The object identifier of the MIB object to check to see 354 if the trigger should fire. 356 This may be wildcarded by truncating all or part of the 357 instance portion, in which case the condition is obtained 358 as if with a GetNext function, checking multiple values 359 if they exist. If such wildcarding is applied, 360 mteTriggerIDWildcard must be 'true' and if not it must 361 be 'false'." 362 DEFVAL { 0 0 } 363 ::= { mteTriggerEntry 4 } 365 mteTriggerValueIDWildcard OBJECT-TYPE 366 SYNTAX TruthValue 367 MAX-ACCESS read-create 368 STATUS current 369 DESCRIPTION 370 "Control for whether mteTriggerValueID is to be treated as 371 fully-specified or wildcarded, with 'true' indicating wildcard. 372 DEFVAL { false } 373 ::= { mteTriggerEntry 5 } 375 mteTriggerTargetTag OBJECT-TYPE 376 SYNTAX SnmpTagValue 377 MAX-ACCESS read-create 378 STATUS current 379 DESCRIPTION 380 "The tag for the target(s) from which to obtain the condition 381 for a trigger check. 383 Systems limited to self management may not accept a non-zero 384 length for the value of this object. 386 A length of 0 indicates the local system. In this case, 387 access to the objects indicated by mteTriggerValueID is under 388 the security credentials of the requester that set 389 mteTriggerStatus to 'active'." 390 DEFVAL { ''H } 391 ::= { mteTriggerEntry 6 } 393 mteTriggerContextName OBJECT-TYPE 394 SYNTAX SnmpAdminString 395 MAX-ACCESS read-create 396 STATUS current 397 DESCRIPTION 398 "The management context from which to obtain mteTriggerValueID. 400 This may be wildcarded by leaving characters off the end. To 401 indicate such wildcarding mteTriggerContextNameWildcard must 402 be 'true'." 403 DEFVAL { ''H } 404 ::= { mteTriggerEntry 7 } 406 mteTriggerContextNameWildcard OBJECT-TYPE 407 SYNTAX TruthValue 408 MAX-ACCESS read-create 409 STATUS current 410 DESCRIPTION 411 "Control for whether mteTriggerContextName is to be treated as 412 fully-specified or wildcarded, with 'true' indicating wildcard. 413 DEFVAL { false } 414 ::= { mteTriggerEntry 8 } 416 mteTriggerFrequency OBJECT-TYPE 417 SYNTAX Integer32 (0..65535) 418 UNITS "seconds" 419 MAX-ACCESS read-create 420 STATUS current 421 DESCRIPTION 422 "The number of seconds to wait between trigger condition 423 checks. To encourage consistency in sampling, the 424 interval is measured from the beginning of one check to 425 the beginning of the next and the timer is restarted immediately 426 when it expires, not when the check completes. 428 If the next check begins before the previous one completed the 429 system may either attempt to make the check or treat this as an 430 error condition. 432 A frequency of 0 indicates instantaneous recognition of the 433 condition. This is not possible in many cases, but such may 434 be supported in cases where it makes sense and the system is 435 able to do so." 436 DEFVAL { 600 } 437 ::= { mteTriggerEntry 9 } 439 mteTriggerBooleanStartup OBJECT-TYPE 440 SYNTAX TruthValue 441 MAX-ACCESS read-create 442 STATUS current 443 DESCRIPTION 444 "Control for whether an event may be triggered when this entry 445 is first set to 'active'. If the value mteTriggerBooleanStartup 446 is 'true' and the first sample after this entry becomes active is 447 true then one mteTriggerEvent is triggered. 449 If mteTriggerType is not 'boolean', this object is not 450 instantiated." 452 DEFVAL { true } 453 ::= { mteTriggerEntry 10 } 455 mteTriggerThresholdStartup OBJECT-TYPE 456 SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } 457 MAX-ACCESS read-create 458 STATUS current 459 DESCRIPTION 460 "The event that may be triggered when this entry is first 461 set to 'active'. If the first sample after this entry 462 becomes active is greater than or equal to 463 mteTriggerRisingThreshold and mteTriggerThresholdStartup is 464 equal to 'rising' or 'risingOrFalling', then one 465 mteTriggerRisingEvent is triggered. If the first 466 sample after this entry becomes active is less than 467 or equal to mteTriggerFallingThreshold and 468 mteTriggerThresholdStartup is equal to 'falling' or 469 'risingOrFalling', then one mteTriggerRisingEvent is triggered. 471 If mteTriggerType is not 'threshold', this object is not 472 instantiated." 473 DEFVAL { risingOrFalling } 474 ::= { mteTriggerEntry 11 } 476 mteTriggerRisingThreshold OBJECT-TYPE 477 SYNTAX Integer32 478 MAX-ACCESS read-create 479 STATUS current 480 DESCRIPTION 481 "A threshold value to check against if mteTriggerType is 482 'threshold'. 484 When the current sampled value is greater than or equal to 485 this threshold, and the value at the last sampling 486 interval was less than this threshold, one mteTriggerRisingEvent 487 is triggered. That event is also triggered if the first sample 488 afer this entry bcomes active is greater than or equal to this 489 threshold and mteTriggerThresholdStartup is equal to 'rising' 490 or 'risingOrFalling'. 492 After a rising event is generated, another such event is not 493 triggered until the sampled value falls below this threshold and 494 reaches mteTriggerFallingThreshold. 496 If mteTriggerType is not 'threshold', this object is not 497 instantiated." 498 DEFVAL { 0 } 499 ::= { mteTriggerEntry 12 } 501 mteTriggerFallingThreshold OBJECT-TYPE 502 SYNTAX Integer32 503 MAX-ACCESS read-create 504 STATUS current 505 DESCRIPTION 506 "A threshold value to check against if mteTriggerType is 507 'threshold'. 509 When the current sampled value is less than or equal to 510 this threshold, and the value at the last sampling interval 511 was greater than this threshold, one mteTriggerFallingEvent 512 is triggered. That event is also triggered if the first sample 513 afer this entry bcomes active is less than or equal to this 514 threshold and mteTriggerThresholdStartup is equal to 'falling' 515 or 'risingOrFalling'. 517 After a falling event is generated, another such event is not 518 triggered until the sampled value rises above this threshold and 519 reaches mteTriggerRisingThreshold. 521 If mteTriggerType is not 'threshold', this object is not 522 instantiated." 523 DEFVAL { 0 } 524 ::= { mteTriggerEntry 13 } 526 mteTriggerEvent OBJECT-TYPE 527 SYNTAX SnmpAdminString (SIZE (0..64)) 528 MAX-ACCESS read-create 529 STATUS current 530 DESCRIPTION 531 "The event to invoke when mteTriggerType is 'boolean' and 532 this trigger fires. A length of 0 indicates no event. 534 If mteTriggerType is not 'boolean', this object is not 535 instantiated." 536 DEFVAL { ''H } 537 ::= { mteTriggerEntry 14 } 539 mteTriggerRisingEvent OBJECT-TYPE 540 SYNTAX SnmpAdminString (SIZE (0..64)) 541 MAX-ACCESS read-create 542 STATUS current 543 DESCRIPTION 544 "The event to invoke when mteTriggerType is 'threshold' and 545 this trigger fires based on mteTriggerRisingThreshold. A 546 value of 0 indicates no event. 548 If mteTriggerType is not 'threshold', this object is not 549 instantiated." 550 DEFVAL { ''H } 551 ::= { mteTriggerEntry 15 } 553 mteTriggerFallingEvent OBJECT-TYPE 554 SYNTAX SnmpAdminString (SIZE (0..64)) 555 MAX-ACCESS read-create 556 STATUS current 557 DESCRIPTION 558 "The event to invoke when mteTriggerType is 'threshold' and 559 this trigger fires based on mteTriggerFallingThreshold. A 560 value of 0 indicates no event. 562 If mteTriggerType is not 'threshold', this object is not 563 instantiated." 564 DEFVAL { ''H } 565 ::= { mteTriggerEntry 16 } 567 mteTriggerObjects OBJECT-TYPE 568 SYNTAX SnmpAdminString (SIZE (0..64)) 569 MAX-ACCESS read-create 570 STATUS current 571 DESCRIPTION 572 "The mteTriggerObjectNName of a group of objects from 573 mteTriggerObjectTable. These objects are to be added to any 574 Notification resulting from the firing of this trigger. 576 A length of 0 indicates no additional objects." 577 DEFVAL { ''H } 578 ::= { mteTriggerEntry 17 } 580 mteTriggerStatus OBJECT-TYPE 581 SYNTAX RowStatus 582 MAX-ACCESS read-create 583 STATUS current 584 DESCRIPTION 585 "The control that allows creation and deletion of entries. 586 Once made active an entry may not be modified except to 587 delete it." 588 DEFVAL { createAndWait } 589 ::= { mteTriggerEntry 18 } 591 -- 592 -- Trigger Object Table 593 -- 595 mteTriggerObjectTable OBJECT-TYPE 596 SYNTAX SEQUENCE OF mteTriggerObjectEntry 597 MAX-ACCESS not-accessible 598 STATUS current 599 DESCRIPTION 600 "A table of objects related to a trigger and to be added to 601 Notifications resulting from that trigger." 602 ::= { mteTrigger 3 } 604 mteTriggerObjectEntry OBJECT-TYPE 605 SYNTAX mteTriggerObjectEntry 606 MAX-ACCESS not-accessible 607 STATUS current 608 "Objects for a single trigger. Applications create and 609 delete entries using mteTriggerObjectStatus." 610 INDEX { mteTriggerObjectName, mteTriggerObjectIndex } 611 ::= { mteTriggerObjectteble 1 } 613 mteTriggerObjectEntry ::= SEQUENCE { 614 mteTriggerObjectName SnmpAdminString, 615 mteTriggerObjectIndex Unsigned32, 616 mteTriggerObjectID Integer32, 617 mteTriggerObjectIDWildcard TruthValue, 618 mteTriggerObjectStatus RowStatus 619 } 621 mteTriggerObjectName OBJECT-TYPE 622 SYNTAX SnmpAdminString (SIZE (1..64)) 623 MAX-ACCESS not-accessible 624 STATUS current 625 DESCRIPTION 626 "A locally-unique, administratively assigned name for a group 627 of objects to associate with a trigger." 628 ::= { mteTriggerObjectEntry 1 } 630 mteTriggerObjectIndex OBJECT-TYPE 631 SYNTAX Unsigned32 (1..4294967295) 632 MAX-ACCESS not-accessible 633 STATUS current 634 DESCRIPTION 635 "An arbitrary small integer for the purpose of identifying 636 individual objects with a mteTriggerObjectName group." 637 ::= { mteTriggerObjectEntry 2 } 639 mteTriggerObjectID OBJECT-TYPE 640 SYNTAX OBJECT IDENTIFIER 641 MAX-ACCESS read-create 642 STATUS current 643 DESCRIPTION 644 "The object identifier of a MIB object to add to a Notification 645 that results from the firing of a trigger. 647 This may be wildcarded by truncating all or part of the 648 instance portion, in which case the instance portion of the 649 OID for obtaining this object will be the same as that used 650 in obtaining the mteTriggerObjectValueID that fired. 651 If such wildcarding is applied, mteTriggerObjectIDWildcard 652 must be 'true' and if not it must be 'false'." 653 DEFVAL { 0 0 } 654 ::= { mteTriggerObjectEntry 3 } 656 mteTriggerObjectValueIDWildcard OBJECT-TYPE 657 SYNTAX TruthValue 658 MAX-ACCESS read-create 659 STATUS current 660 DESCRIPTION 661 "Control for whether mteTriggerObjectValueID is to be treated as 662 fully-specified or wildcarded, with 'true' indicating wildcard. 663 DEFVAL { false } 664 ::= { mteTriggerObjectEntry 4 } 666 mteTriggerObjectStatus OBJECT-TYPE 667 SYNTAX RowStatus 668 MAX-ACCESS read-create 669 STATUS current 670 DESCRIPTION 671 "The control that allows creation and deletion of entries. 672 Once made active an entry may not be modified except to 673 delete it." 674 DEFVAL { createAndWait } 675 ::= { mteTriggerObjectEntry 5 } 677 -- 678 -- Event Section 679 -- 681 -- Counters 683 mteEventFailures OBJECT-TYPE 684 SYNTAX Counter32 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "The number of times an attempt to invoke an event 689 has failed. This counts individually for each 690 attempt in a group of targets or each attempt for a 691 wildcarded trigger object." 692 ::= { mteEvent 1 } 694 -- 695 -- Event Table 696 -- 698 mteEventTable OBJECT-TYPE 699 SYNTAX SEQUENCE OF MteEventEntry 700 MAX-ACCESS not-accessible 701 STATUS current 702 DESCRIPTION 703 "A table of management event action information." 704 ::= { mteEvent 2 } 706 mteEventEntry OBJECT-TYPE 707 SYNTAX MteEventEntry 708 MAX-ACCESS not-accessible 709 STATUS current 710 DESCRIPTION 711 "Information about a single event. Applications create and 712 delete entries using mteEventStatus." 713 INDEX { IMPLIED mteEventName } 714 ::= { mteEventTable 1 } 716 MteEventEntry ::= SEQUENCE { 717 mteEventName SnmpAdminString, 718 mteEventComment DisplayString, 719 mteEventActions BITS, 720 mteEventNotification OBJECT IDENTIFIER, 721 mteEventObjects SnmpAdminString, 722 mteEventSetObject OBJECT IDENTIFIER, 723 mteEventSetObjectWildcard TruthValue, 724 mteEventSetValue Integer32, 725 mteEventSetTargetTag SnmpTagValue, 726 mteEventSetContextName SnmpAdminString, 727 mteEventSetContextNameWildcard TruthValue, 728 mteEventStatus RowStatus 729 } 731 mteEventName OBJECT-TYPE 732 SYNTAX SnmpAdminString (SIZE (1..64)) 733 MAX-ACCESS not-accessible 734 STATUS current 735 DESCRIPTION 736 "A locally-unique, administratively assigned name for the event." 737 ::= { mteEventCreationEntry 1 } 739 mteEventComment OBJECT-TYPE 740 SYNTAX DisplayString 741 MAX-ACCESS read-create 742 STATUS current 743 DESCRIPTION 744 "A description of the event's function and use." 745 DEFVAL { ''H } 746 ::= { mteEventEntry 2 } 748 mteEventActions OBJECT-TYPE 749 SYNTAX BITS { notification, set } 750 MAX-ACCESS read-create 751 STATUS current 752 DESCRIPTION 753 "The actions to peform when this event occurs. 755 For 'notification', Traps and/or Informs are sent according 756 to the configuration in the SNMP Notification MIB. 758 For 'set', an SNMP Set operation is performed according to 759 control values in this entry." 760 DEFVAL { 0 } 761 ::= { mteEventEntry 3 } 763 mteEventNotification OBJECT-TYPE 764 SYNTAX OBJECT IDENTIFIER 765 MAX-ACCESS read-create 766 STATUS current 767 DESCRIPTION 768 "The object identifier from the NOTIFICATION-TYPE for the 769 notification to use if metEventActions has 'notification' set. 771 If 'notification' is not set, this object is not instantiated." 772 DEFVAL { 0 0 } 773 ::= { mteEventEntry 4 } 775 mteEventObjects OBJECT-TYPE 776 SYNTAX SnmpAdminString (SIZE (0..64)) 777 MAX-ACCESS read-create 778 STATUS current 779 DESCRIPTION 780 "The mteTriggerObjectName of a group of objects from 781 mteTriggerObjectTable if mteEventActions has 'notification' set. 782 These objects are to be added to any Notification generated by 783 this event. 785 If 'notification' is not set, this object is not instantiated. 787 A length of 0 indicates no additional objects." 788 DEFVAL { ''H } 789 ::= { mteEventEntry 5 } 791 mteEventSetObject OBJECT-TYPE 792 SYNTAX OBJECT IDENTIFIER 793 MAX-ACCESS read-create 794 STATUS current 795 DESCRIPTION 796 "The object identifier from the MIB object to set if 797 mteEventActions has 'set' set. 799 This object identifier may be wildcarded by leaving sub-identifiers 800 off the end, in which case nteEventSetObjectWildCard must be 801 'true'. 803 If mteEventSetObject is wildcarded the instance used to set it 804 is the same as the instance for the value of mteTriggerValueID 805 that triggered the event." 807 If 'set' is not set, this object is not instantiated." 808 DEFVAL { 0 0 } 809 ::= { mteEventEntry 6 } 811 mteEventSetObjectWildcard OBJECT-TYPE 812 SYNTAX TruthValue 813 MAX-ACCESS read-create 814 STATUS current 815 DESCRIPTION 816 "Control over whether mteEventSetObject is to be treated as 817 fully-specified or wildcarded, with 'true' indicating wildcard 818 if mteEventActions has 'set' set. 820 If 'set' is not set, this object is not instantiated." 821 DEFVAL { false } 822 ::= { mteEventEntry 7 } 824 mteEventSetValue OBJECT-TYPE 825 SYNTAX Integer32 826 MAX-ACCESS read-create 827 STATUS current 828 DESCRIPTION 829 "The value to which to set the object at mteEventSetObject 830 if mteEventActions has 'set' set. 832 If 'set' is not set, this object is not instantiated." 833 DEFVAL { 0 } 834 ::= { mteEventEntry 8 } 836 mteEventSetTargetTag OBJECT-TYPE 837 SYNTAX SnmpTagValue 838 MAX-ACCESS read-create 839 STATUS current 840 DESCRIPTION 841 "The tag for the target(s) at which to set the object at 842 mteEventSetObject to mteEventSetValue if mteEventActions 843 has 'set' set. 845 If 'set' is not set, this object is not instantiated." 847 Systems limited to self management may not accept a non-zero 848 length for the value of this object. 850 A length of 0 indicates the local system. In this case, 851 access to the objects indicated by mteEventObjectID is under 852 the security credentials of the requester that set 853 mteEventStatus to 'active'." 854 DEFVAL { ''H } 855 ::= { mteEventEntry 9 } 857 mteEventSetContextName OBJECT-TYPE 858 SYNTAX SnmpAdminString 859 MAX-ACCESS read-create 860 STATUS current 861 DESCRIPTION 862 "The management context in which to set mteEventObjectID. 863 if mteEventActions has 'set' set. 865 If 'set' is not set, this object is not instantiated." 867 This may be wildcarded by leaving characters off the end. To 868 indicate such wildcarding mteEventSetContextNameWildcard must 869 be 'true'. 871 If this context name is wildcarded the value used to complete 872 the wildcarding of mteTriggerContextName will be appended." 873 DEFVAL { ''H } 874 ::= { mteEventEntry 10 } 876 mteEventSetContextNameWildcard OBJECT-TYPE 877 SYNTAX TruthValue 878 MAX-ACCESS read-create 879 STATUS current 880 DESCRIPTION 881 "Control for whether mteEventSetContextName is to be treated as 882 fully-specified or wildcarded, with 'true' indicating wildcard 883 if mteEventActions has 'set' set. 885 If 'set' is not set, this object is not instantiated." 886 DEFVAL { false } 887 ::= { mteTriggerEntry 10 } 889 mteEventStatus OBJECT-TYPE 890 SYNTAX RowStatus 891 MAX-ACCESS read-create 892 STATUS current 893 DESCRIPTION 894 "The control that allows creation and deletion of entries. 895 Once made active an entry may not be modified except to 896 delete it." 897 DEFVAL { createAndWait } 898 ::= { mteEventEntry 12 } 900 -- 901 -- Notifications 902 -- 904 eventMIBNotificationPrefix OBJECT IDENTIFIER ::= { eventMIB 2 } 905 eventMIBNotifications OBJECT IDENTIFIER ::= { eventMIBNotificationPrefix 0 } 906 eventMIBNotificationObjectss OBJECT IDENTIFIER 907 ::= { eventMIBNotificationPrefix 1 } 909 -- 910 -- Notification Objects 911 -- 913 mteHotTrigger OBJECT-TYPE 914 SYNTAX SnmpAdminString 915 MAX-ACCESS accessible-for-notify 916 STATUS current 917 DESCRIPTION 918 "The name of the trigger causing the notification. 919 ::= { mteTrigger 1 } 921 mteHotTargetName OBJECT-TYPE 922 SYNTAX SnmpAdminString 923 MAX-ACCESS accessible-for-notify 924 STATUS current 925 DESCRIPTION 926 "The SNMP Target MIB's snmpTargetAddrName related to the 927 notification. 928 ::= { mteTrigger 2 } 930 mteHotContextName OBJECT-TYPE 931 SYNTAX SnmpAdminString 932 MAX-ACCESS accessible-for-notify 933 STATUS current 934 DESCRIPTION 935 "The context name related to the notification. This must be as 936 fully-qualified as possible, inluding filling in wildcard 937 informaation determined in processing." 938 ::= { mteTrigger 3 } 940 mteHotOID OBJECT-TYPE 941 SYNTAX OBJECT IDENTIFIER 942 MAX-ACCESS accessible-for-notify 943 STATUS current 944 DESCRIPTION 945 "The object identifier of the destination object related to the 946 notification. This must be as fully-qualified as possible, 947 inluding filling in wildcard informaation determined in processing. 949 For a trigger-related notification this is from mteTriggerValueID. 951 For a set failure this is from mteEventSetObject." 952 ::= { mteTrigger 3 } 954 mterHotValue OBJECT-TYPE 955 SYNTAX Integer32 956 MAX-ACCESS accessible-for-notify 957 STATUS current 958 DESCRIPTION 959 "The value of the object at mteTriggerValueID when a 960 trigger fired." 961 ::= { mteTrigger 5 } 963 mteFailedReason OBJECT-TYPE 964 SYNTAX FailureReason 965 MAX-ACCESS accessible-for-notify 966 STATUS current 967 DESCRIPTION 968 "The reason for the failure of an attempt to check for a 969 trigger condition or set an object in response to an event. 970 ::= { mteTrigger 6 } 972 -- 973 -- Notifications 974 -- 976 mteTriggerSenseAlarm NOTIFICATION-TYPE 977 OBJECTS { mteHotTrigger, 978 mteHotTargetName, 979 mteHotContextName, 980 mteHotOID, 981 mteHotValue } 982 STATUS current 983 DESCRIPTION 984 "Notification that the trigger indicated by the object 985 instances has fired, for triggers with mteTriggerType 986 'boolean'." 987 ::= { eventMIBNotifications 1 } 989 mteTriggerRisingAlarm NOTIFICATION-TYPE 990 OBJECTS { mteHotTrigger, 991 mteHotTargetName, 992 mteHotContextName, 993 mteHotOID, 994 mteHotValue } 995 STATUS current 996 DESCRIPTION 997 "Notification that the rising threshold was met for triggers 998 with mteTriggerType 'threshold'." 999 ::= { eventMIBNotifications 2 } 1001 mteTriggerFallingAlarm NOTIFICATION-TYPE 1002 OBJECTS { mteHotTrigger, 1003 mteHotTargetName, 1004 mteHotContextName, 1005 mteHotOID, 1006 mteHotValue } 1007 STATUS current 1008 DESCRIPTION 1009 "Notification that the falling threshold was met for triggers 1010 with mteTriggerType 'threshold'." 1011 ::= { eventMIBNotifications 3 } 1013 mteTriggerFailureAlarm NOTIFICATION-TYPE 1014 OBJECTS { mteHotTrigger, 1015 mteHotTargetName, 1016 mteHotContextName, 1017 mteHotOID, 1018 mteFailedReason } 1019 STATUS current 1020 DESCRIPTION 1021 "Notification that an attempt to check a trigger has failed. 1023 The network manager must enable this notification only with 1024 a certain fear and trembling, as it can easily crowd out more 1025 important information. It should be used only to help diagnose 1026 a problem that has appeared in the error counters and can not 1027 be found otherwise." 1028 ::= { eventMIBNotifications 4 } 1030 mteEventSetFailureAlarm NOTIFICATION-TYPE 1031 OBJECTS { mteHotTrigger, 1032 mteHotTargetName, 1033 mteHotContextName, 1034 mteHotOID, 1035 mteFailedReason } 1037 STATUS current 1038 DESCRIPTION 1039 "Notification that an attempt to do a set in response to an 1040 event has failed. 1042 The network manager must enable this notification only with 1043 a certain fear and trembling, as it can easily crowd out more 1044 important information. It should be used only to help diagnose 1045 a problem that has appeared in the error counters and can not 1046 be found otherwise." 1047 ::= { eventMIBNotifications 5 } 1049 -- 1050 -- Conformance 1051 -- 1053 eventMIBConformance OBJECT IDENTIFIER ::= { eventMIB 3 } 1054 eventMIBCompliances OBJECT IDENTIFIER ::= { eventMIBConformance 1 } 1055 eventMIBGroups OBJECT IDENTIFIER ::= { eventMIBConformance 2 } 1057 -- Compliance 1059 eventMIBCompliance MODULE-COMPLIANCE 1060 STATUS current 1061 DESCRIPTION 1062 "The compliance statement for entities which implement 1063 the Event MIB." 1064 MODULE -- this module 1065 MANDATORY-GROUPS { 1066 eventTriggerGroup, 1067 eventEventGroup, 1068 eventNotificationObjectGroup, 1069 eventNotificationGroup 1070 } 1072 OBJECT mteTriggerTargetTag 1073 MIN-ACCESS read-only 1074 DESCRIPTION 1075 "Write access is not required, thus limiting 1076 monitoring to the local system or preconfigured 1077 remote systems."" 1079 OBJECT mteEventSetTargetTag 1080 MIN-ACCESS read-only 1081 DESCRIPTION 1082 "Write access is not required, thus limiting 1083 setting to the local system or preconfigured 1084 remote systems."" 1086 OBJECT mteTriggerValueIDWildcard 1087 MIN-ACCESS read-only 1088 DESCRIPTION 1089 "Write access is not required, thus allowing 1090 the system not to implement wildcarding." 1092 OBJECT mteTriggerContextNameWildcard 1093 MIN-ACCESS read-only 1094 DESCRIPTION 1095 "Write access is not required, thus allowing 1096 the system not to implement wildcarding." 1098 OBJECT mteTriggerObjectValueIDWildcard 1099 MIN-ACCESS read-only 1100 DESCRIPTION 1101 "Write access is not required, thus allowing 1102 the system not to implement wildcarding." 1104 OBJECT mteEventSetContextNameWildcard 1105 MIN-ACCESS read-only 1106 DESCRIPTION 1107 "Write access is not required, thus allowing 1108 the system not to implement wildcarding." 1110 ::= { eventMIBCompliances 1 } 1112 -- Units of Conformance 1114 eventTriggerGroup OBJECT-GROUP 1115 OBJECTS { 1116 mteTriggerFailures, 1118 mteTriggerComment, 1119 mteTriggerTest, 1120 mteTriggerValueID, 1121 mteTriggerValueIDWildcard, 1122 mteTriggerTargetTag, 1123 mteTriggerContextName, 1124 mteTriggerContextNameWildcard, 1125 mteTriggerFrequency, 1126 mteTriggerBooleanStartup, 1127 mteTriggerThresholdStartup, 1128 mteTriggerRisingThreshold, 1129 mteTriggerFallingThreshold, 1130 mteTriggerEvent, 1131 mteTriggerRisingEvent, 1132 mteTriggerFallingEvent, 1133 mteTriggerObjects, 1134 mteTriggerStatus, 1136 mteTriggerObjectID, 1137 mteTriggerObjectIDWildcard, 1138 mteTriggerObjectStatus 1139 } 1140 STATUS current 1141 DESCRIPTION 1142 "Event triggers and supplemental objects." 1143 ::= { eventMIBGroups 1 } 1145 eventEventGroup OBJECT-GROUP 1146 OBJECTS { 1147 mteEventComment, 1148 mteEventActions, 1149 mteEventNotification, 1150 mteEventObjects, 1151 mteEventSetObject, 1152 mteEventSetObjectWildcard, 1153 mteEventSetValue, 1154 mteEventSetTargetTag, 1155 mteEventSetContextName, 1156 mteEventSetContextNameWildcard, 1157 mteEventStatus 1158 } 1159 STATUS current 1160 DESCRIPTION 1161 "Events." 1162 ::= { eventMIBGroups 2 } 1164 eventNotificationObjectGroup OBJECT-GROUP 1165 OBJECTS { 1166 mteHotTrigger, 1167 mteHotTargetName, 1168 mteHotContextName, 1169 mteHotOID, 1170 mterHotValue, 1171 mteFailedReason 1172 } 1173 STATUS current 1174 DESCRIPTION 1175 "Notification objects." 1176 ::= { eventMIBGroups 3 } 1178 eventNotificationGroup OBJECT-GROUP 1179 OBJECTS { 1180 mteTriggerSenseAlarm, 1181 mteTriggerRisingAlarm, 1182 mteTriggerFallingAlarm, 1183 mteTriggerFailureAlarm, 1184 mteEventSetFailureAlarm 1185 } 1186 STATUS current 1187 DESCRIPTION 1188 "Notifications." 1189 ::= { eventMIBGroups 4 } 1191 END 1192 9. Acknowledgements 1194 This MIB contains considerable contributions from the RMON MIB, the 1195 Distributed Management Design Team (Andy Bierman, Maria Greene, Bob 1196 Stewart, and Steve Waldbusser), and colleagues at Cisco. 1198 10. References 1200 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1201 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1202 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1203 January 1998 1205 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1206 Management Information for TCP/IP-based Internets", RFC 1155, 1207 Performance Systems International, Hughes LAN Systems, May 1990 1209 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1210 Performance Systems International, Hughes LAN Systems, March 1991 1212 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1213 RFC 1215, Performance Systems International, March 1991 1215 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 1216 of Management Information for Version 2 of the Simple Network 1217 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 1218 Systems, Inc., Dover Beach Consulting, Inc., International Network 1219 Services, January 1996. 1221 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 1222 Conventions for Version 2 of the Simple Network Management Protocol 1223 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 1224 Dover Beach Consulting, Inc., International Network Services, 1225 January 1996. 1227 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance 1228 Statements for Version 2 of the Simple Network Management Protocol 1229 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 1230 Dover Beach Consulting, Inc., International Network Services, 1231 January 1996. 1233 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1234 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1235 International, Performance Systems International, MIT Laboratory 1236 for Computer Science, May 1990. 1238 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1239 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1240 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1241 International Network Services, January 1996. 1243 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1244 Mappings for Version 2 of the Simple Network Management Protocol 1245 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1246 Dover Beach Consulting, Inc., International Network Services, 1247 January 1996. 1249 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1250 Processing and Dispatching for the Simple Network Management 1251 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 1252 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 1254 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1255 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1256 2274, IBM T. J. Watson Research, January 1998. 1258 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1259 Operations for Version 2 of the Simple Network Management Protocol 1260 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1261 Dover Beach Consulting, Inc., International Network Services, 1262 January 1996. 1264 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1265 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1266 Systems, January 1998 1268 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1269 Control Model (VACM) for the Simple Network Management Protocol 1270 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 1271 Cisco Systems, Inc., January 1998 1273 [16] Waldbusser, S., "Remote Network Monitoring Management Information 1274 Base", RFC 1757, International Network Services, February 1995 1276 [17] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to- 1277 Manager Management Information Base", RFC 1451, SNMP Research, 1278 Inc., Cisco SYSTEMS< Inc., Dover Beach Consulting, Inc., 1279 International Network Services, April 1993 1281 [18] Stewart, B., "Expression MIB", RFC ????, Cisco Systems, Inc., 1282 ?Month? 1998 1284 [19] Stewart, B., "Notification Log MIB", RFC ????, Cisco Systems, Inc., 1285 ?Month? 1998 1287 11. Security Considerations 1289 Security issues are discussed in the Overview section and in the 1290 DESCRIPTION clauses of relevant objects. 1292 12. Author's Address 1294 Bob Stewart 1295 Cisco Systems, Inc. 1296 170 West Tasman Drive 1297 San Jose, CA 95134-1706 1299 Phone: 408-526-4527 1300 Email: bstewart@cisco.com 1302 Table of Contents 1304 1 Abstract ........................................................ 2 1305 2 The SNMP Management Framework ................................... 2 1306 3 Overview ........................................................ 4 1307 4 Relationship to Other MIBs ...................................... 4 1308 5 MIB Sections .................................................... 4 1309 6 Operation ....................................................... 5 1310 7 Security ........................................................ 5 1311 8 Definitions ..................................................... 7 1312 9 Acknowledgements ................................................ 30 1313 10 References ..................................................... 31 1314 11 Security Considerations ........................................ 33 1315 12 Author's Address ............................................... 33