idnits 2.17.1 draft-ietf-disman-event-mib-05.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): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 36 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1339 has weird spacing: '...for the purpo...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (7 October 1998) is 9330 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: 24 errors (**), 0 flaws (~~), 5 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Event MIB 7 October 1998 4 Event MIB 6 7 October 1998 8 draft-ietf-disman-event-mib-05.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 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 47 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 48 document are to be interpreted as described in RFC 2119. 50 2. The SNMP Management Framework 52 The SNMP Management Framework presently consists of five major 53 components: 55 o An overall architecture, described in RFC 2271 [1]. 57 o Mechanisms for describing and naming objects and events for the 58 purpose of management. The first version of this Structure of 59 Management Information (SMI) is called SMIv1 and described in 60 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 61 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 62 1904 [7]. 64 o Message protocols for transferring management information. The 65 first version of the SNMP message protocol is called SNMPv1 and 66 described in RFC 1157 [8]. A second version of the SNMP message 67 protocol, which is not an Internet standards track protocol, is 68 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 69 The third version of the message protocol is called SNMPv3 and 70 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 72 o Protocol operations for accessing management information. The 73 first set of protocol operations and associated PDU formats is 74 described in RFC 1157 [8]. A second set of protocol operations 75 and associated PDU formats is described in RFC 1905 [13]. 77 o A set of fundamental applications described in RFC 2273 [14] and 78 the view-based access control mechanism described in RFC 2275 79 [15]. 81 Managed objects are accessed via a virtual information store, termed the 82 Management Information Base or MIB. Objects in the MIB are defined 83 using the mechanisms defined in the SMI. 85 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 86 conforming to the SMIv1 can be produced through the appropriate 87 translations. The resulting translated MIB must be semantically 88 equivalent, except where objects or events are omitted because no 89 translation is possible (use of Counter64). Some machine readable 90 information in SMIv2 will be converted into textual descriptions in 91 SMIv1 during the translation process. However, this loss of machine 92 readable information is not considered to change the semantics of the 93 MIB. 95 3. Overview 97 With network sizes well beyond the ability of people to management their 98 networks directly automated, distributed management is vital. An 99 important aspect of such management is the ability of a system to 100 monitor itself or for some other system to monitor it. 102 The Event MIB provides the ability to monitor MIB objects on the local 103 system or on a remote system and take simple action when a trigger 104 condition is met. 106 All of these components must suit either a relatively powerful manager 107 or mid-level manager, as well as a somewhat more limited self-managing 108 system. 110 4. Relationship to Other MIBs 112 The Event MIB is based on extensive experience with the RMON MIB [16] 113 and its alarm and event groups and is intended as a replacement for 114 those groups. The Event MIB calls "triggers" what the RMON MIB called 115 "alarms," but the concepts are the same. Event MIB triggers maintain 116 the RMON handling of thresholds and add the concept of booleans. Event 117 MIB events maintain the RMON concept of sending an SNMP notification in 118 response to a trigger and add the concept of setting a MIB object. 120 The Event MIB is the successor and update to SNMPv2's Manager-to-Manager 121 MIB [17] which was declared Historic pending this work. 123 The Event MIB depends on the services of the SNMPv3 Management Target 124 and Notification MIBs [14]. 126 The Event MIB is nicely complemented by the Distributed Management 127 Expression MIB [18], which is the expected source of boolean objects to 128 monitor. 130 5. MIB Sections 132 The MIB has three sections, triggers, events, and notifications. 133 Triggers define the conditions that lead to events. Events may cause 134 notifications. 136 The trigger table lists what objects are to be monitored and how and 137 relates each trigger to an event. In the same section the trigger 138 object table lists trigger-related objects that can be added to 139 notifications either for a trigger or for an event. 141 The event table defines what happens when an event is triggered, sending 142 a notificaiton, setting a MIB object or both. 144 The notification section defines a set of generic notifications to go 145 with the events and for Event MIB error handlling, and it defines a set 146 of objects to put in those notifications. 148 6. Operation 150 The Event MIB is instrumentation for a distributed management 151 application that monitors MIB objects. In its simplest form this 152 application monitors individual, local MIB objects, just as an RMON 153 probe fulfills the functions implied by RMON's alarm and event 154 operation. Additionally the application can monitor remote objects and 155 wildcarded groups of objects. 157 Remote monitoring uses the tag service of the Management Target MIB to 158 select and access remote systems as an ordinary SNMP-based management 159 application. Local monitoring may be be a more intimate, local 160 interface which may, for example, bypass SNMP formatting but otherwise 161 is functionally identical to remote SNMP operation. A self-management 162 only system may not implemenet remote monitoring. 164 Wildcards indicate that the application should use a GetNext-type 165 operation to find the zero or more instances implied by a truncated 166 object identifier, just like an ordinary SNMP-based management 167 application. 169 Error handling is by notification, which at first thought violates the 170 principle that notifications may be lost or become a crippling burden, 171 but the intent is that such error notifications be enabled only for the 172 diagnosis of problems indicated by error counters and if the 173 notifications are being lost they be directed to the log as described in 174 the Notification Log MIB [19]. 176 7. Security 178 Security of Event MIB entries depends on SNMPv3 access control for the 179 entire MIB or for subsets based on substrings of trigger and event 180 names. 182 Security of monitored objects for remote access depends on the 183 Management Target MIB. Security for local access can depend on the 184 Management Target MIB or on recording appropriate security credentials 185 of the creator of an entry and using those to access the local objects. 187 8. Definitions 189 EVENT-MIB DEFINITIONS ::= BEGIN 191 IMPORTS 192 MODULE-IDENTITY, OBJECT-TYPE, 193 experimental, Integer32, Unsigned32 194 NOTIFICATION-TYPE FROM SNMPv2-SMI 195 TEXTUAL-CONVENTION, RowStatus, 196 TimeStamp, DisplayString FROM SNMPv2-TC 197 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 198 SnmpTagValue FROM SNMP-TARGET-MIB 199 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 201 eventMIB MODULE-IDENTITY 202 LAST-UPDATED "9810071700Z" 203 ORGANIZATION "IETF Distributed Management Working Group" 204 CONTACT-INFO "Bob Stewart 205 Cisco Systems, Inc. 206 170 West Tasman Drive, 207 San Jose CA 95134-1706. 208 Phone: +1 408 526 4527 209 Email: bstewart@cisco.com" 210 DESCRIPTION 211 "The MIB module for defining event triggers and actions 212 for network management purposes." 213 ::= { experimental xx } 215 eventMIBObjects OBJECT IDENTIFIER ::= { eventMIB 1 } 217 mteTrigger OBJECT IDENTIFIER ::= { eventMIBObjects 1 } 218 mteEvent OBJECT IDENTIFIER ::= { eventMIBObjects 2 } 220 -- 221 -- Textual Conventions 222 -- 224 FailureReason ::= TEXTUAL-CONVENTION 225 STATUS current 226 DESCRIPTION 227 "Reasons for failures in an attempt to send a management 228 message. 230 The first group of errors, numbered less than 100, are copied 231 directly from SNMP protocol operations and are intended to carry 232 exactly the meanings defined for the protocol as returned in 233 an SNMP response. Those numbered 100 or greater are related 234 to problems in sending the request." 235 SYNTAX INTEGER { tooBig(1), 236 noSuchName(2), 237 badValue(3), 238 readOnly(4), 239 genErr(5), 240 noAccess(6), 241 wrongType(7), 242 wrongLength(8), 243 wrongEncoding(9), 244 wrongValue(10), 245 noCreation(11), 246 inconsistentValue(12), 247 resourceUnavailable(13), 248 commitFailed(14), 249 undoFailed(15), 250 authorizationError(16), 251 notWritable(17), 252 inconsistentName(18), 254 localResourceLack(101), 255 badDestination(102), 256 noAck(103) } 258 -- 259 -- Trigger Section 260 -- 262 -- Counters 264 mteTriggerFailures OBJECT-TYPE 265 SYNTAX Counter32 266 MAX-ACCESS read-only 267 STATUS current 268 DESCRIPTION 269 "The number of times an attempt to check for a trigger 270 condition has failed. This counts individually for each 271 attempt in a group of targets or each attempt for a 272 wildcarded object." 273 ::= { mteTrigger 1 } 275 -- 276 -- Trigger Table 277 -- 279 mteTriggerTable OBJECT-TYPE 280 SYNTAX SEQUENCE OF MteTriggerEntry 281 MAX-ACCESS not-accessible 282 STATUS current 283 DESCRIPTION 284 "A table of management event trigger information." 285 ::= { mteTrigger 2 } 287 mteTriggerEntry OBJECT-TYPE 288 SYNTAX MteTriggerEntry 289 MAX-ACCESS not-accessible 290 STATUS current 291 "Information about a single trigger. Applications create and 292 delete entries using mteTriggerStatus." 293 INDEX { IMPLIED mteTriggerName } 294 ::= { mteTriggerteble 1 } 296 MteTriggerEntry ::= SEQUENCE { 297 mteTriggerName SnmpAdminString, 298 mteTriggerComment DisplayString, 299 mteTriggerTest INTEGER, 300 mteTriggerValueID Integer32, 301 mteTriggerValueIDWildcard TruthValue, 302 mteTriggerTargetTag SnmpTagValue, 303 mteTriggerContextName SnmpAdminString, 304 mteTriggerContextNameWildcard TruthValue, 305 mteTriggerFrequency Integer32, 306 mteTriggerBooleanStartup INTEGER, 307 mteTriggerThresholdStartup INTEGER, 308 mteTriggerRisingThreshold Integer32, 309 mteTriggerFallingThreshold Integer32, 310 mteTriggerEvent SnmpAdminString, 311 mteTriggerRisingEvent SnmpAdminString, 312 mteTriggerFallingEvent SnmpAdminString, 313 mteTriggerObjects SnmpAdminString, 314 mteTriggerStatus RowStatus 315 } 317 mteTriggerName OBJECT-TYPE 318 SYNTAX SnmpAdminString (SIZE (1..64)) 319 MAX-ACCESS not-accessible 320 STATUS current 321 DESCRIPTION 322 "A locally-unique, administratively assigned name for the 323 trigger." 324 ::= { mteTriggerEntry 1 } 326 mteTriggerComment OBJECT-TYPE 327 SYNTAX DisplayString 328 MAX-ACCESS read-create 329 STATUS current 330 DESCRIPTION 331 "A description of the trigger's function and use." 332 DEFVAL { ''H } 333 ::= { mteTriggerEntry 2 } 335 mteTriggerTest OBJECT-TYPE 336 SYNTAX INTEGER { boolean(1), threshold(2) } 337 MAX-ACCESS read-create 338 STATUS current 339 DESCRIPTION 340 "The type of trigger test to perform. For all tests, 341 mteTriggerValue must evaluate to an integer. 343 For 'boolean', a value of 0 is false. A non-zero value is true 344 and fires the trigger. The trigger will not fire again until 345 the value has become false and come back to true. 347 For 'threshold' it works as described below for 348 mteTriggerThresholdStartup, mteTriggerRisingThreshold, and 349 mteTriggerFallingThreshold." 350 DEFVAL { boolean } 351 ::= { mteTriggerEntry 3 } 353 mteTriggerValueID OBJECT-TYPE 354 SYNTAX OBJECT IDENTIFIER 355 MAX-ACCESS read-create 356 STATUS current 357 DESCRIPTION 358 "The object identifier of the MIB object to check to see 359 if the trigger should fire. 361 This may be wildcarded by truncating all or part of the 362 instance portion, in which case the condition is obtained 363 as if with a GetNext function, checking multiple values 364 if they exist. If such wildcarding is applied, 365 mteTriggerIDWildcard must be 'true' and if not it must 366 be 'false'." 367 DEFVAL { 0 0 } 368 ::= { mteTriggerEntry 4 } 370 mteTriggerValueIDWildcard OBJECT-TYPE 371 SYNTAX TruthValue 372 MAX-ACCESS read-create 373 STATUS current 374 DESCRIPTION 375 "Control for whether mteTriggerValueID is to be treated as 376 fully-specified or wildcarded, with 'true' indicating wildcard. 377 DEFVAL { false } 378 ::= { mteTriggerEntry 5 } 380 mteTriggerTargetTag OBJECT-TYPE 381 SYNTAX SnmpTagValue 382 MAX-ACCESS read-create 383 STATUS current 384 DESCRIPTION 385 "The tag for the target(s) from which to obtain the condition 386 for a trigger check. 388 Systems limited to self management may not accept a non-zero 389 length for the value of this object. 391 A length of 0 indicates the local system. In this case, 392 access to the objects indicated by mteTriggerValueID is under 393 the security credentials of the requester that set 394 mteTriggerStatus to 'active'." 395 DEFVAL { ''H } 396 ::= { mteTriggerEntry 6 } 398 mteTriggerContextName OBJECT-TYPE 399 SYNTAX SnmpAdminString 400 MAX-ACCESS read-create 401 STATUS current 402 DESCRIPTION 403 "The management context from which to obtain mteTriggerValueID. 405 This may be wildcarded by leaving characters off the end. To 406 indicate such wildcarding mteTriggerContextNameWildcard must 407 be 'true'." 408 DEFVAL { ''H } 409 ::= { mteTriggerEntry 7 } 411 mteTriggerContextNameWildcard OBJECT-TYPE 412 SYNTAX TruthValue 413 MAX-ACCESS read-create 414 STATUS current 415 DESCRIPTION 416 "Control for whether mteTriggerContextName is to be treated as 417 fully-specified or wildcarded, with 'true' indicating wildcard. 418 DEFVAL { false } 419 ::= { mteTriggerEntry 8 } 421 mteTriggerFrequency OBJECT-TYPE 422 SYNTAX Integer32 (0..65535) 423 UNITS "seconds" 424 MAX-ACCESS read-create 425 STATUS current 426 DESCRIPTION 427 "The number of seconds to wait between trigger condition 428 checks. To encourage consistency in sampling, the 429 interval is measured from the beginning of one check to 430 the beginning of the next and the timer is restarted immediately 431 when it expires, not when the check completes. 433 If the next check begins before the previous one completed the 434 system may either attempt to make the check or treat this as an 435 error condition. 437 A frequency of 0 indicates instantaneous recognition of the 438 condition. This is not possible in many cases, but such may 439 be supported in cases where it makes sense and the system is 440 able to do so." 441 DEFVAL { 600 } 442 ::= { mteTriggerEntry 9 } 444 mteTriggerBooleanStartup OBJECT-TYPE 445 SYNTAX TruthValue 446 MAX-ACCESS read-create 447 STATUS current 448 DESCRIPTION 449 "Control for whether an event may be triggered when this entry 450 is first set to 'active'. If the value mteTriggerBooleanStartup 451 is 'true' and the first sample after this entry becomes active 452 is true then one mteTriggerEvent is triggered. 454 If mteTriggerType is not 'boolean', this object is not 455 instantiated." 457 DEFVAL { true } 458 ::= { mteTriggerEntry 10 } 460 mteTriggerThresholdStartup OBJECT-TYPE 461 SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } 462 MAX-ACCESS read-create 463 STATUS current 464 DESCRIPTION 465 "The event that may be triggered when this entry is first 466 set to 'active'. If the first sample after this entry 467 becomes active is greater than or equal to 468 mteTriggerRisingThreshold and mteTriggerThresholdStartup is 469 equal to 'rising' or 'risingOrFalling', then one 470 mteTriggerRisingEvent is triggered. If the first 471 sample after this entry becomes active is less than 472 or equal to mteTriggerFallingThreshold and 473 mteTriggerThresholdStartup is equal to 'falling' or 474 'risingOrFalling', then one mteTriggerRisingEvent is triggered. 476 If mteTriggerType is not 'threshold', this object is not 477 instantiated." 478 DEFVAL { risingOrFalling } 479 ::= { mteTriggerEntry 11 } 481 mteTriggerRisingThreshold OBJECT-TYPE 482 SYNTAX Integer32 483 MAX-ACCESS read-create 484 STATUS current 485 DESCRIPTION 486 "A threshold value to check against if mteTriggerType is 487 'threshold'. 489 When the current sampled value is greater than or equal to 490 this threshold, and the value at the last sampling 491 interval was less than this threshold, one mteTriggerRisingEvent 492 is triggered. That event is also triggered if the first sample 493 afer this entry bcomes active is greater than or equal to this 494 threshold and mteTriggerThresholdStartup is equal to 'rising' 495 or 'risingOrFalling'. 497 After a rising event is generated, another such event is not 498 triggered until the sampled value falls below this threshold and 499 reaches mteTriggerFallingThreshold. 501 If mteTriggerType is not 'threshold', this object is not 502 instantiated." 503 DEFVAL { 0 } 504 ::= { mteTriggerEntry 12 } 506 mteTriggerFallingThreshold OBJECT-TYPE 507 SYNTAX Integer32 508 MAX-ACCESS read-create 509 STATUS current 510 DESCRIPTION 511 "A threshold value to check against if mteTriggerType is 512 'threshold'. 514 When the current sampled value is less than or equal to 515 this threshold, and the value at the last sampling interval 516 was greater than this threshold, one mteTriggerFallingEvent 517 is triggered. That event is also triggered if the first sample 518 afer this entry bcomes active is less than or equal to this 519 threshold and mteTriggerThresholdStartup is equal to 'falling' 520 or 'risingOrFalling'. 522 After a falling event is generated, another such event is not 523 triggered until the sampled value rises above this threshold and 524 reaches mteTriggerRisingThreshold. 526 If mteTriggerType is not 'threshold', this object is not 527 instantiated." 528 DEFVAL { 0 } 529 ::= { mteTriggerEntry 13 } 531 mteTriggerEvent OBJECT-TYPE 532 SYNTAX SnmpAdminString (SIZE (0..64)) 533 MAX-ACCESS read-create 534 STATUS current 535 DESCRIPTION 536 "The event to invoke when mteTriggerType is 'boolean' and 537 this trigger fires. A length of 0 indicates no event. 539 If mteTriggerType is not 'boolean', this object is not 540 instantiated." 541 DEFVAL { ''H } 542 ::= { mteTriggerEntry 14 } 544 mteTriggerRisingEvent OBJECT-TYPE 545 SYNTAX SnmpAdminString (SIZE (0..64)) 546 MAX-ACCESS read-create 547 STATUS current 548 DESCRIPTION 549 "The event to invoke when mteTriggerType is 'threshold' and 550 this trigger fires based on mteTriggerRisingThreshold. A 551 value of 0 indicates no event. 553 If mteTriggerType is not 'threshold', this object is not 554 instantiated." 555 DEFVAL { ''H } 556 ::= { mteTriggerEntry 15 } 558 mteTriggerFallingEvent OBJECT-TYPE 559 SYNTAX SnmpAdminString (SIZE (0..64)) 560 MAX-ACCESS read-create 561 STATUS current 562 DESCRIPTION 563 "The event to invoke when mteTriggerType is 'threshold' and 564 this trigger fires based on mteTriggerFallingThreshold. A 565 value of 0 indicates no event. 567 If mteTriggerType is not 'threshold', this object is not 568 instantiated." 569 DEFVAL { ''H } 570 ::= { mteTriggerEntry 16 } 572 mteTriggerObjects OBJECT-TYPE 573 SYNTAX SnmpAdminString (SIZE (0..64)) 574 MAX-ACCESS read-create 575 STATUS current 576 DESCRIPTION 577 "The mteTriggerObjectNName of a group of objects from 578 mteTriggerObjectTable. These objects are to be added to any 579 Notification resulting from the firing of this trigger. 581 A length of 0 indicates no additional objects." 582 DEFVAL { ''H } 583 ::= { mteTriggerEntry 17 } 585 mteTriggerStatus OBJECT-TYPE 586 SYNTAX RowStatus 587 MAX-ACCESS read-create 588 STATUS current 589 DESCRIPTION 590 "The control that allows creation and deletion of entries. 591 Once made active an entry may not be modified except to 592 delete it." 593 DEFVAL { createAndWait } 594 ::= { mteTriggerEntry 18 } 596 -- 597 -- Trigger Object Table 598 -- 600 mteTriggerObjectTable OBJECT-TYPE 601 SYNTAX SEQUENCE OF mteTriggerObjectEntry 602 MAX-ACCESS not-accessible 603 STATUS current 604 DESCRIPTION 605 "A table of objects related to a trigger and to be added to 606 Notifications resulting from that trigger." 607 ::= { mteTrigger 3 } 609 mteTriggerObjectEntry OBJECT-TYPE 610 SYNTAX mteTriggerObjectEntry 611 MAX-ACCESS not-accessible 612 STATUS current 613 "Objects for a single trigger. Applications create and 614 delete entries using mteTriggerObjectStatus." 615 INDEX { mteTriggerObjectName, mteTriggerObjectIndex } 616 ::= { mteTriggerObjectteble 1 } 618 mteTriggerObjectEntry ::= SEQUENCE { 619 mteTriggerObjectName SnmpAdminString, 620 mteTriggerObjectIndex Unsigned32, 621 mteTriggerObjectID Integer32, 622 mteTriggerObjectIDWildcard TruthValue, 623 mteTriggerObjectStatus RowStatus 624 } 626 mteTriggerObjectName OBJECT-TYPE 627 SYNTAX SnmpAdminString (SIZE (1..64)) 628 MAX-ACCESS not-accessible 629 STATUS current 630 DESCRIPTION 631 "A locally-unique, administratively assigned name for a group of 632 objects to associate with a trigger." 633 ::= { mteTriggerObjectEntry 1 } 635 mteTriggerObjectIndex OBJECT-TYPE 636 SYNTAX Unsigned32 (1..4294967295) 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "An arbitrary small integer for the purpose of identifying 641 individual objects with a mteTriggerObjectName group." 642 ::= { mteTriggerObjectEntry 2 } 644 mteTriggerObjectID OBJECT-TYPE 645 SYNTAX OBJECT IDENTIFIER 646 MAX-ACCESS read-create 647 STATUS current 648 DESCRIPTION 649 "The object identifier of a MIB object to add to a Notification 650 that results from the firing of a trigger. 652 This may be wildcarded by truncating all or part of the 653 instance portion, in which case the instance portion of the 654 OID for obtaining this object will be the same as that used 655 in obtaining the mteTriggerObjectValueID that fired. 656 If such wildcarding is applied, mteTriggerObjectIDWildcard 657 must be 'true' and if not it must be 'false'." 658 DEFVAL { 0 0 } 659 ::= { mteTriggerObjectEntry 3 } 661 mteTriggerObjectValueIDWildcard OBJECT-TYPE 662 SYNTAX TruthValue 663 MAX-ACCESS read-create 664 STATUS current 665 DESCRIPTION 666 "Control for whether mteTriggerObjectValueID is to be treated as 667 fully-specified or wildcarded, with 'true' indicating wildcard. 668 DEFVAL { false } 669 ::= { mteTriggerObjectEntry 4 } 671 mteTriggerObjectStatus OBJECT-TYPE 672 SYNTAX RowStatus 673 MAX-ACCESS read-create 674 STATUS current 675 DESCRIPTION 676 "The control that allows creation and deletion of entries. 677 Once made active an entry may not be modified except to 678 delete it." 679 DEFVAL { createAndWait } 680 ::= { mteTriggerObjectEntry 5 } 682 -- 683 -- Event Section 684 -- 686 -- Counters 688 mteEventFailures OBJECT-TYPE 689 SYNTAX Counter32 690 MAX-ACCESS read-only 691 STATUS current 692 DESCRIPTION 693 "The number of times an attempt to invoke an event 694 has failed. This counts individually for each 695 attempt in a group of targets or each attempt for a 696 wildcarded trigger object." 697 ::= { mteEvent 1 } 699 -- 700 -- Event Table 701 -- 703 mteEventTable OBJECT-TYPE 704 SYNTAX SEQUENCE OF MteEventEntry 705 MAX-ACCESS not-accessible 706 STATUS current 707 DESCRIPTION 708 "A table of management event action information." 709 ::= { mteEvent 2 } 711 mteEventEntry OBJECT-TYPE 712 SYNTAX MteEventEntry 713 MAX-ACCESS not-accessible 714 STATUS current 715 DESCRIPTION 716 "Information about a single event. Applications create and 717 delete entries using mteEventStatus." 718 INDEX { IMPLIED mteEventName } 719 ::= { mteEventTable 1 } 721 MteEventEntry ::= SEQUENCE { 722 mteEventName SnmpAdminString, 723 mteEventComment DisplayString, 724 mteEventActions BITS, 725 mteEventNotification OBJECT IDENTIFIER, 726 mteEventObjects SnmpAdminString, 727 mteEventSetObject OBJECT IDENTIFIER, 728 mteEventSetObjectWildcard TruthValue, 729 mteEventSetValue Integer32, 730 mteEventSetTargetTag SnmpTagValue, 731 mteEventSetContextName SnmpAdminString, 732 mteEventSetContextNameWildcard TruthValue, 733 mteEventStatus RowStatus 734 } 736 mteEventName OBJECT-TYPE 737 SYNTAX SnmpAdminString (SIZE (1..64)) 738 MAX-ACCESS not-accessible 739 STATUS current 740 DESCRIPTION 741 "A locally-unique, administratively assigned name for the 742 event." 743 ::= { mteEventCreationEntry 1 } 745 mteEventComment OBJECT-TYPE 746 SYNTAX DisplayString 747 MAX-ACCESS read-create 748 STATUS current 749 DESCRIPTION 750 "A description of the event's function and use." 751 DEFVAL { ''H } 752 ::= { mteEventEntry 2 } 754 mteEventActions OBJECT-TYPE 755 SYNTAX BITS { notification, set } 756 MAX-ACCESS read-create 757 STATUS current 758 DESCRIPTION 759 "The actions to peform when this event occurs. 761 For 'notification', Traps and/or Informs are sent according 762 to the configuration in the SNMP Notification MIB. 764 For 'set', an SNMP Set operation is performed according to 765 control values in this entry." 766 DEFVAL { 0 } 767 ::= { mteEventEntry 3 } 769 mteEventNotification OBJECT-TYPE 770 SYNTAX OBJECT IDENTIFIER 771 MAX-ACCESS read-create 772 STATUS current 773 DESCRIPTION 774 "The object identifier from the NOTIFICATION-TYPE for the 775 notification to use if metEventActions has 'notification' set. 777 If 'notification' is not set, this object is not instantiated." 778 DEFVAL { 0 0 } 779 ::= { mteEventEntry 4 } 781 mteEventObjects OBJECT-TYPE 782 SYNTAX SnmpAdminString (SIZE (0..64)) 783 MAX-ACCESS read-create 784 STATUS current 785 DESCRIPTION 786 "The mteTriggerObjectName of a group of objects from 787 mteTriggerObjectTable if mteEventActions has 'notification' set. 788 These objects are to be added to any Notification generated by 789 this event. 791 If 'notification' is not set, this object is not instantiated. 793 A length of 0 indicates no additional objects." 794 DEFVAL { ''H } 795 ::= { mteEventEntry 5 } 797 mteEventSetObject OBJECT-TYPE 798 SYNTAX OBJECT IDENTIFIER 799 MAX-ACCESS read-create 800 STATUS current 801 DESCRIPTION 802 "The object identifier from the MIB object to set if 803 mteEventActions has 'set' set. 805 This object identifier may be wildcarded by leaving 806 sub-identifiers off the end, in which case 807 nteEventSetObjectWildCard must be 'true'. 809 If mteEventSetObject is wildcarded the instance used to set it 810 is the same as the instance for the value of mteTriggerValueID 811 that triggered the event." 813 If 'set' is not set, this object is not instantiated." 814 DEFVAL { 0 0 } 815 ::= { mteEventEntry 6 } 817 mteEventSetObjectWildcard OBJECT-TYPE 818 SYNTAX TruthValue 819 MAX-ACCESS read-create 820 STATUS current 821 DESCRIPTION 822 "Control over whether mteEventSetObject is to be treated as 823 fully-specified or wildcarded, with 'true' indicating wildcard 824 if mteEventActions has 'set' set. 826 If 'set' is not set, this object is not instantiated." 827 DEFVAL { false } 828 ::= { mteEventEntry 7 } 830 mteEventSetValue OBJECT-TYPE 831 SYNTAX Integer32 832 MAX-ACCESS read-create 833 STATUS current 834 DESCRIPTION 835 "The value to which to set the object at mteEventSetObject 836 if mteEventActions has 'set' set. 838 If 'set' is not set, this object is not instantiated." 839 DEFVAL { 0 } 840 ::= { mteEventEntry 8 } 842 mteEventSetTargetTag OBJECT-TYPE 843 SYNTAX SnmpTagValue 844 MAX-ACCESS read-create 845 STATUS current 846 DESCRIPTION 847 "The tag for the target(s) at which to set the object at 848 mteEventSetObject to mteEventSetValue if mteEventActions 849 has 'set' set. 851 If 'set' is not set, this object is not instantiated." 853 Systems limited to self management may not accept a non-zero 854 length for the value of this object. 856 A length of 0 indicates the local system. In this case, 857 access to the objects indicated by mteEventObjectID is under 858 the security credentials of the requester that set 859 mteEventStatus to 'active'." 860 DEFVAL { ''H } 861 ::= { mteEventEntry 9 } 863 mteEventSetContextName OBJECT-TYPE 864 SYNTAX SnmpAdminString 865 MAX-ACCESS read-create 866 STATUS current 867 DESCRIPTION 868 "The management context in which to set mteEventObjectID. 869 if mteEventActions has 'set' set. 871 If 'set' is not set, this object is not instantiated." 873 This may be wildcarded by leaving characters off the end. To 874 indicate such wildcarding mteEventSetContextNameWildcard must 875 be 'true'. 877 If this context name is wildcarded the value used to complete 878 the wildcarding of mteTriggerContextName will be appended." 879 DEFVAL { ''H } 880 ::= { mteEventEntry 10 } 882 mteEventSetContextNameWildcard OBJECT-TYPE 883 SYNTAX TruthValue 884 MAX-ACCESS read-create 885 STATUS current 886 DESCRIPTION 887 "Control for whether mteEventSetContextName is to be treated as 888 fully-specified or wildcarded, with 'true' indicating wildcard 889 if mteEventActions has 'set' set. 891 If 'set' is not set, this object is not instantiated." 892 DEFVAL { false } 893 ::= { mteTriggerEntry 10 } 895 mteEventStatus OBJECT-TYPE 896 SYNTAX RowStatus 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "The control that allows creation and deletion of entries. 901 Once made active an entry may not be modified except to 902 delete it." 903 DEFVAL { createAndWait } 904 ::= { mteEventEntry 12 } 906 -- 907 -- Notifications 908 -- 910 eventMIBNotificationPrefix OBJECT IDENTIFIER ::= { eventMIB 2 } 911 eventMIBNotifications OBJECT IDENTIFIER ::= 912 { eventMIBNotificationPrefix 0 } 913 eventMIBNotificationObjectss OBJECT IDENTIFIER 914 ::= { eventMIBNotificationPrefix 1 } 916 -- 917 -- Notification Objects 918 -- 920 mteHotTrigger OBJECT-TYPE 921 SYNTAX SnmpAdminString 922 MAX-ACCESS accessible-for-notify 923 STATUS current 924 DESCRIPTION 925 "The name of the trigger causing the notification. 926 ::= { mteTrigger 1 } 928 mteHotTargetName OBJECT-TYPE 929 SYNTAX SnmpAdminString 930 MAX-ACCESS accessible-for-notify 931 STATUS current 932 DESCRIPTION 933 "The SNMP Target MIB's snmpTargetAddrName related to the 934 notification. 935 ::= { mteTrigger 2 } 937 mteHotContextName OBJECT-TYPE 938 SYNTAX SnmpAdminString 939 MAX-ACCESS accessible-for-notify 940 STATUS current 941 DESCRIPTION 942 "The context name related to the notification. This must be as 943 fully-qualified as possible, including filling in wildcard 944 informaation determined in processing." 945 ::= { mteTrigger 3 } 947 mteHotOID OBJECT-TYPE 948 SYNTAX OBJECT IDENTIFIER 949 MAX-ACCESS accessible-for-notify 950 STATUS current 951 DESCRIPTION 952 "The object identifier of the destination object related to the 953 notification. This must be as fully-qualified as possible, 954 inluding filling in wildcard informaation determined in 955 processing. 957 For a trigger-related notification this is from 958 mteTriggerValueID. 960 For a set failure this is from mteEventSetObject." 961 ::= { mteTrigger 3 } 963 mterHotValue OBJECT-TYPE 964 SYNTAX Integer32 965 MAX-ACCESS accessible-for-notify 966 STATUS current 967 DESCRIPTION 968 "The value of the object at mteTriggerValueID when a 969 trigger fired." 970 ::= { mteTrigger 5 } 972 mteFailedReason OBJECT-TYPE 973 SYNTAX FailureReason 974 MAX-ACCESS accessible-for-notify 975 STATUS current 976 DESCRIPTION 977 "The reason for the failure of an attempt to check for a 978 trigger condition or set an object in response to an event. 979 ::= { mteTrigger 6 } 981 -- 982 -- Notifications 983 -- 985 mteTriggerSenseAlarm NOTIFICATION-TYPE 986 OBJECTS { mteHotTrigger, 987 mteHotTargetName, 988 mteHotContextName, 989 mteHotOID, 990 mteHotValue } 991 STATUS current 992 DESCRIPTION 993 "Notification that the trigger indicated by the object 994 instances has fired, for triggers with mteTriggerType 995 'boolean'." 996 ::= { eventMIBNotifications 1 } 998 mteTriggerRisingAlarm NOTIFICATION-TYPE 999 OBJECTS { mteHotTrigger, 1000 mteHotTargetName, 1001 mteHotContextName, 1002 mteHotOID, 1003 mteHotValue } 1004 STATUS current 1005 DESCRIPTION 1006 "Notification that the rising threshold was met for triggers 1007 with mteTriggerType 'threshold'." 1008 ::= { eventMIBNotifications 2 } 1010 mteTriggerFallingAlarm NOTIFICATION-TYPE 1011 OBJECTS { mteHotTrigger, 1012 mteHotTargetName, 1013 mteHotContextName, 1014 mteHotOID, 1015 mteHotValue } 1016 STATUS current 1017 DESCRIPTION 1018 "Notification that the falling threshold was met for triggers 1019 with mteTriggerType 'threshold'." 1020 ::= { eventMIBNotifications 3 } 1022 mteTriggerFailureAlarm NOTIFICATION-TYPE 1023 OBJECTS { mteHotTrigger, 1024 mteHotTargetName, 1025 mteHotContextName, 1026 mteHotOID, 1027 mteFailedReason } 1028 STATUS current 1029 DESCRIPTION 1030 "Notification that an attempt to check a trigger has failed. 1032 The network manager must enable this notification only with 1033 a certain fear and trembling, as it can easily crowd out more 1034 important information. It should be used only to help diagnose 1035 a problem that has appeared in the error counters and can not 1036 be found otherwise." 1037 ::= { eventMIBNotifications 4 } 1039 mteEventSetFailureAlarm NOTIFICATION-TYPE 1040 OBJECTS { mteHotTrigger, 1041 mteHotTargetName, 1042 mteHotContextName, 1043 mteHotOID, 1044 mteFailedReason } 1045 STATUS current 1046 DESCRIPTION 1047 "Notification that an attempt to do a set in response to an 1048 event has failed. 1050 The network manager must enable this notification only with 1051 a certain fear and trembling, as it can easily crowd out more 1052 important information. It should be used only to help diagnose 1053 a problem that has appeared in the error counters and can not 1054 be found otherwise." 1055 ::= { eventMIBNotifications 5 } 1057 -- 1058 -- Conformance 1059 -- 1061 eventMIBConformance OBJECT IDENTIFIER ::= { eventMIB 3 } 1062 eventMIBCompliances OBJECT IDENTIFIER ::= { eventMIBConformance 1 } 1063 eventMIBGroups OBJECT IDENTIFIER ::= { eventMIBConformance 2 } 1065 -- Compliance 1067 eventMIBCompliance MODULE-COMPLIANCE 1068 STATUS current 1069 DESCRIPTION 1070 "The compliance statement for entities which implement 1071 the Event MIB." 1072 MODULE -- this module 1073 MANDATORY-GROUPS { 1074 eventTriggerGroup, 1075 eventEventGroup, 1076 eventNotificationObjectGroup, 1077 eventNotificationGroup 1078 } 1080 OBJECT mteTriggerTargetTag 1081 MIN-ACCESS read-only 1082 DESCRIPTION 1083 "Write access is not required, thus limiting 1084 monitoring to the local system or preconfigured 1085 remote systems."" 1087 OBJECT mteEventSetTargetTag 1088 MIN-ACCESS read-only 1089 DESCRIPTION 1090 "Write access is not required, thus limiting 1091 setting to the local system or preconfigured 1092 remote systems."" 1094 OBJECT mteTriggerValueIDWildcard 1095 MIN-ACCESS read-only 1096 DESCRIPTION 1097 "Write access is not required, thus allowing 1098 the system not to implement wildcarding." 1100 OBJECT mteTriggerContextNameWildcard 1101 MIN-ACCESS read-only 1102 DESCRIPTION 1103 "Write access is not required, thus allowing 1104 the system not to implement wildcarding." 1106 OBJECT mteTriggerObjectValueIDWildcard 1107 MIN-ACCESS read-only 1108 DESCRIPTION 1109 "Write access is not required, thus allowing 1110 the system not to implement wildcarding." 1112 OBJECT mteEventSetContextNameWildcard 1113 MIN-ACCESS read-only 1114 DESCRIPTION 1115 "Write access is not required, thus allowing 1116 the system not to implement wildcarding." 1118 ::= { eventMIBCompliances 1 } 1120 -- Units of Conformance 1122 eventTriggerGroup OBJECT-GROUP 1123 OBJECTS { 1124 mteTriggerFailures, 1126 mteTriggerComment, 1127 mteTriggerTest, 1128 mteTriggerValueID, 1129 mteTriggerValueIDWildcard, 1130 mteTriggerTargetTag, 1131 mteTriggerContextName, 1132 mteTriggerContextNameWildcard, 1133 mteTriggerFrequency, 1134 mteTriggerBooleanStartup, 1135 mteTriggerThresholdStartup, 1136 mteTriggerRisingThreshold, 1137 mteTriggerFallingThreshold, 1138 mteTriggerEvent, 1139 mteTriggerRisingEvent, 1140 mteTriggerFallingEvent, 1141 mteTriggerObjects, 1142 mteTriggerStatus, 1144 mteTriggerObjectID, 1145 mteTriggerObjectIDWildcard, 1146 mteTriggerObjectStatus 1147 } 1148 STATUS current 1149 DESCRIPTION 1150 "Event triggers and supplemental objects." 1151 ::= { eventMIBGroups 1 } 1153 eventEventGroup OBJECT-GROUP 1154 OBJECTS { 1155 mteEventComment, 1156 mteEventActions, 1157 mteEventNotification, 1158 mteEventObjects, 1159 mteEventSetObject, 1160 mteEventSetObjectWildcard, 1161 mteEventSetValue, 1162 mteEventSetTargetTag, 1163 mteEventSetContextName, 1164 mteEventSetContextNameWildcard, 1165 mteEventStatus 1166 } 1167 STATUS current 1168 DESCRIPTION 1169 "Events." 1170 ::= { eventMIBGroups 2 } 1172 eventNotificationObjectGroup OBJECT-GROUP 1173 OBJECTS { 1174 mteHotTrigger, 1175 mteHotTargetName, 1176 mteHotContextName, 1177 mteHotOID, 1178 mterHotValue, 1179 mteFailedReason 1180 } 1181 STATUS current 1182 DESCRIPTION 1183 "Notification objects." 1184 ::= { eventMIBGroups 3 } 1186 eventNotificationGroup OBJECT-GROUP 1187 OBJECTS { 1188 mteTriggerSenseAlarm, 1189 mteTriggerRisingAlarm, 1190 mteTriggerFallingAlarm, 1191 mteTriggerFailureAlarm, 1192 mteEventSetFailureAlarm 1193 } 1194 STATUS current 1195 DESCRIPTION 1196 "Notifications." 1197 ::= { eventMIBGroups 4 } 1199 END 1200 9. Intellectual Property 1202 The IETF takes no position regarding the validity or scope of any 1203 intellectual property or other rights that might be claimed to pertain 1204 to the implementation or use of the technology described in this 1205 document or the extent to which any license under such rights might or 1206 might not be available; neither does it represent that it has made any 1207 effort to identify any such rights. Information on the IETF's 1208 procedures with respect to rights in standards-track and standards- 1209 related documentation can be found in BCP-11. Copies of claims of 1210 rights made available for publication and any assurances of licenses to 1211 be made available, or the result of an attempt made to obtain a general 1212 license or permission for the use of such proprietary rights by 1213 implementors or users of this specification can be obtained from the 1214 IETF Secretariat. 1216 10. Acknowledgements 1218 This MIB contains considerable contributions from the RMON MIB, the 1219 Distributed Management Design Team (Andy Bierman, Maria Greene, Bob 1220 Stewart, and Steve Waldbusser), and colleagues at Cisco. 1222 11. References 1224 [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for 1225 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1226 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1227 January 1998. 1229 [2] Rose, M. and K. McCloghrie, "Structure and Identification of 1230 Management Information for TCP/IP-based Internets", RFC 1155, 1231 Performance Systems International, Hughes LAN Systems, May 1990. 1233 [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1234 Performance Systems International, Hughes LAN Systems, March 1991. 1236 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1237 RFC 1215, Performance Systems International, March 1991. 1239 [5] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of 1240 Management Information for Version 2 of the Simple Network 1241 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 1242 Systems, Inc., Dover Beach Consulting, Inc., International Network 1243 Services, January 1996. 1245 [6] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual 1246 Conventions for Version 2 of the Simple Network Management Protocol 1247 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 1248 Dover Beach Consulting, Inc., International Network Services, 1249 January 1996. 1251 [7] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Conformance 1252 Statements for Version 2 of the Simple Network Management Protocol 1253 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 1254 Dover Beach Consulting, Inc., International Network Services, 1255 January 1996. 1257 [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network 1258 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1259 International, Performance Systems International, MIT Laboratory 1260 for Computer Science, May 1990. 1262 [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction 1263 to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 1264 Systems, Inc., Dover Beach Consulting, Inc., International Network 1265 Services, January 1996. 1267 [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport 1268 Mappings for Version 2 of the Simple Network Management Protocol 1269 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1270 Dover Beach Consulting, Inc., International Network Services, 1271 January 1996. 1273 [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 1274 Processing and Dispatching for the Simple Network Management 1275 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 1276 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 1278 [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for 1279 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1280 2274, IBM T. J. Watson Research, January 1998. 1282 [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol 1283 Operations for Version 2 of the Simple Network Management Protocol 1284 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1285 Dover Beach Consulting, Inc., International Network Services, 1286 January 1996. 1288 [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 1289 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1290 Systems, January 1998. 1292 [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 1293 Control Model (VACM) for the Simple Network Management Protocol 1294 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 1295 Cisco Systems, Inc., January 1998. 1297 [16] Waldbusser, S., "Remote Network Monitoring Management Information 1298 Base", RFC 1757, International Network Services, February 1995. 1300 [17] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to- 1301 Manager Management Information Base", RFC 1451, SNMP Research, 1302 Inc., Cisco SYSTEMS< Inc., Dover Beach Consulting, Inc., 1303 International Network Services, April 1993. 1305 [18] Stewart, B., "Expression MIB", RFC ????, Cisco Systems, Inc., 1306 ?Month? 1998. 1308 [19] Stewart, B., "Notification Log MIB", RFC ????, Cisco Systems, Inc., 1309 ?Month? 1998. 1311 12. Security Considerations 1313 Security issues are discussed in the Overview section and in the 1314 DESCRIPTION clauses of relevant objects. 1316 13. Author's Address 1318 Bob Stewart 1319 Cisco Systems, Inc. 1320 170 West Tasman Drive 1321 San Jose, CA 95134-1706 1322 U.S.A. 1324 Phone: +1 408 526 4527 1325 Email: bstewart@cisco.com 1327 14. Full Copyright Statement 1329 Copyright (C) The Internet Society (1998). All Rights Reserved. 1331 This document and translations of it may be copied and furnished to 1332 others, and derivative works that comment on or otherwise explain it or 1333 assist in its implementation may be prepared, copied, published and 1334 distributed, in whole or in part, without restriction of any kind, 1335 provided that the above copyright notice and this paragraph are included 1336 on all such copies and derivative works. However, this document itself 1337 may not be modified in any way, such as by removing the copyright notice 1338 or references to the Internet Society or other Internet organizations, 1339 except as needed for the purpose of developing Internet standards in 1340 which case the procedures for copyrights defined in the Internet 1341 Standards process must be followed, or as required to translate it into 1342 languages other than English. 1344 The limited permissions granted above are perpetual and will not be 1345 revoked by the Internet Society or its successors or assigns. 1347 This document and the information contained herein is provided on an "AS 1348 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1349 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1350 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1351 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1352 FITNESS FOR A PARTICULAR PURPOSE. 1354 Table of Contents 1356 1 Abstract ........................................................ 2 1357 2 The SNMP Management Framework ................................... 2 1358 3 Overview ........................................................ 4 1359 4 Relationship to Other MIBs ...................................... 4 1360 5 MIB Sections .................................................... 4 1361 6 Operation ....................................................... 5 1362 7 Security ........................................................ 5 1363 8 Definitions ..................................................... 7 1364 9 Intellectual Property ........................................... 30 1365 10 Acknowledgements ............................................... 31 1366 11 References ..................................................... 32 1367 12 Security Considerations ........................................ 34 1368 13 Author's Address ............................................... 34 1369 14 Full Copyright Statement ....................................... 35