idnits 2.17.1 draft-ietf-disman-event-mib-03.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard 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 5 instances of too long lines in the document, the longest one being 5 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (13 March 1998) is 9541 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) Summary: 14 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Event MIB 3 13 March 1998 5 draft-ietf-disman-event-mib-03.txt 7 Bob Stewart 8 Cisco Systems, Inc. 9 bstewart@cisco.com 11 Status of this Memo 13 This document is an Internet-Draft. Internet-Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its areas, and 15 its working groups. Note that other groups may also distribute working 16 documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet- Drafts as reference material 21 or to cite them other than as ``work in progress.'' 23 To learn the current status of any Internet-Draft, please check the 24 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 25 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 26 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 28 1. Abstract 30 This memo defines an experimental portion of the Management Information 31 Base (MIB) for use with network management protocols in the Internet 32 community. In particular, it describes managed objects used for 33 managing monitoring of MIB objects and taking action through events. 35 2. The SNMP Network Management Framework 37 {The following boilerplate is out of date. It will be replaced when 38 SNMPv3 boilerplate is available.} 40 The SNMP Network Management Framework presently consists of three major 41 components. They are: 43 the SMI, described in RFC 1902 [1] - the mechanisms used for 44 describing and naming objects for the purpose of management. 46 the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects for 47 the Internet suite of protocols. 49 the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for 50 accessing managed objects. 52 The Framework permits new objects to be defined for the purpose of 53 experimentation and evaluation. 55 2.1. Object Definitions 57 Managed objects are accessed via a virtual information store, termed the 58 Management Information Base or MIB. Objects in the MIB are defined 59 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 60 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 61 an administratively assigned name. The object type together with an 62 object instance serves to uniquely identify a specific instantiation of 63 the object. For human convenience, we often use a textual string, 64 termed the descriptor, to refer to the object type. 66 3. Overview 68 This MIB is based heavily on the RMON and Manager-to-Manager MIBs. It 69 depends on the services of the SNMPv3 Management Target and Notification 70 MIBs and is nicely complemented by the Distributed Management Expression 71 MIB. 73 All of these components must suit either a relatively powerful manager 74 or mid-level manager, as well as a somewhat more limited self-managing 75 system. 77 4. Known Problems 79 The compliance section is missing. 81 5. Definitions 83 EVENT-MIB DEFINITIONS ::= BEGIN 85 IMPORTS 86 MODULE-IDENTITY, OBJECT-TYPE, 87 experimental, Integer32, Unsigned32 88 NOTIFICATION-TYPE FROM SNMPv2-SMI 89 TEXTUAL-CONVENTION, RowStatus, 90 TimeStamp, DisplayString FROM SNMPv2-TC 91 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 92 SnmpTagValue FROM SNMP-TARGET-MIB 93 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 95 eventMIB MODULE-IDENTITY 96 LAST-UPDATED "9803131700Z" 97 ORGANIZATION "IETF Distributed Management Working Group" 98 CONTACT-INFO "Bob Stewart 99 Cisco Systems, Inc. 100 170 West Tasman Drive, 101 San Jose CA 95134-1706. 102 Phone: +1 408 526 4527 103 Email: bstewart@cisco.com" 104 DESCRIPTION 105 "The MIB module for defining event triggers and actions 106 for network management purposes." 107 ::= { experimental xx } 109 eventMIBObjects OBJECT IDENTIFIER ::= { eventMIB 1 } 111 mteTrigger OBJECT IDENTIFIER ::= { eventMIBObjects 1 } 112 mteEvent OBJECT IDENTIFIER ::= { eventMIBObjects 2 } 114 -- 115 -- Textual Conventions 116 -- 118 FailureReason ::= TEXTUAL-CONVENTION 119 STATUS current 120 DESCRIPTION 121 "Reasons for failures in an attempt to send a 122 management message." 123 SYNTAX INTEGER { localResourceLack(1), badDestination(2), 124 tooBig(3), badAccessControl(4), 125 noAck(5) } 127 -- 128 -- Trigger Section 129 -- 131 mteTriggerFailures OBJECT-TYPE 132 SYNTAX Counter32 133 MAX-ACCESS read-only 134 STATUS current 135 DESCRIPTION 136 "The number of times an attempt to check for a trigger 137 condition has failed. This counts individually for each 138 attempt in a group of targets or each attempt for a 139 wildcarded object." 140 ::= { mteTrigger 1 } 142 mteTriggerLastFailedTrigger OBJECT-TYPE 143 SYNTAX SnmpAdminString 144 MAX-ACCESS read-only 145 STATUS current 146 DESCRIPTION 147 "The trigger that last failed an attempt to check for a 148 trigger condition." 149 ::= { mteTrigger 2 } 151 mteTriggerLastFailedReason OBJECT-TYPE 152 SYNTAX FailureReason 153 MAX-ACCESS read-only 154 STATUS current 155 DESCRIPTION 156 "The reason for the last failure of an attempt to check 157 for a trigger condition." 158 ::= { mteTrigger 3 } 160 mteTriggerLastFailedTargetTag OBJECT-TYPE 161 SYNTAX SnmpTagValue 162 MAX-ACCESS read-only 163 STATUS current 164 DESCRIPTION 165 "The mteTriggerTargetTag of the last failed attempt to check a 166 trigger condition. The length 0 means this does not apply." 167 ::= { mteTrigger 4 } 169 mteTriggerLastFailedTargetName OBJECT-TYPE 170 SYNTAX SnmpAdminString 171 MAX-ACCESS read-only 172 STATUS current 173 DESCRIPTION 174 "The target name of the last failed attempt to check a 175 trigger condition. The length 0 means this does not apply" 176 ::= { mteTrigger 5 } 178 mteTriggerLastValueID OBJECT-TYPE 179 SYNTAX OBJECT IDENTIFIER 180 MAX-ACCESS read-only 181 STATUS current 182 DESCRIPTION 183 "The object identifier from mteTriggerValueID from the last 184 attempt to check a trigger condition. This must 185 be as full-qualified as possible, including filling in 186 wild-card information determined in processing." 187 ::= { mteTrigger 6 } 189 mteTriggerLastValue OBJECT-TYPE 190 SYNTAX Integer32 191 MAX-ACCESS notification-only 192 STATUS current 193 DESCRIPTION 194 "The value of the object at mteTriggerValueID when a 195 trigger fires." 196 ::= { mteTrigger 7 } 198 mteTriggerTargetName OBJECT-TYPE 199 SYNTAX SnmpAdminString 200 MAX-ACCESS notification-only 201 STATUS current 202 DESCRIPTION 203 "The target name for which the trigger fired or for which a 204 check was attempted." 205 ::= { mteTrigger 8 } 207 -- 208 -- Trigger Table 209 -- 211 mteTriggerTable OBJECT-TYPE 212 SYNTAX SEQUENCE OF MteTriggerEntry 213 MAX-ACCESS not-accessible 214 STATUS current 215 DESCRIPTION 216 "A table of management event trigger information." 217 ::= { mteTrigger 9 } 219 mteTriggerEntry OBJECT-TYPE 220 SYNTAX MteTriggerEntry 221 MAX-ACCESS not-accessible 222 STATUS current 223 "Information about a single trigger, created using mteTriggerStatus." 224 INDEX { IMPLIED mteTriggerName } 225 ::= { mteTriggerteble 1 } 227 MteTriggerEntry ::= SEQUENCE { 228 mteTriggerName SnmpAdminString, 229 mteTriggerComment DisplayString, 230 mteTriggerTest INTEGER, 231 mteTriggerValueID Integer32, 232 mteTriggerValueIDWildcard TruthValue, 233 mteTriggerFrequency Integer32, 234 mteTriggerTargetTag SnmpTagValue, 235 mteTriggerRisingThreshold Integer32, 236 mteTriggerFallingThreshold Integer32, 237 mteTriggerEvent SnmpAdminString, 238 mteTriggerRisingEvent SnmpAdminString, 239 mteTriggerFallingEvent SnmpAdminString, 240 mteTriggerStatus RowStatus 241 } 243 mteTriggerName OBJECT-TYPE 244 SYNTAX SnmpAdminString (SIZE (1..64)) 245 MAX-ACCESS not-accessible 246 STATUS current 247 DESCRIPTION 248 "A locally-unique, administratively assigned name for the trigger." 249 ::= { mteTriggerEntry 1 } 251 mteTriggerComment OBJECT-TYPE 252 SYNTAX DisplayString 253 MAX-ACCESS read-create 254 STATUS current 255 DESCRIPTION 256 "A description of the trigger's function and use." 257 DEFVAL { ''H } 258 ::= { mteTriggerEntry 2 } 260 mteTriggerTest OBJECT-TYPE 261 SYNTAX INTEGER { boolean(1), threshold(2) } 262 MAX-ACCESS read-create 263 STATUS current 264 DESCRIPTION 265 "The type of trigger test to perform. For all tests, 266 mteTriggerValue must evaluate to an integer. 268 For 'boolean', a value of 0 is false. A non-zero value 269 is true and fires the trigger. The trigger will not fire 270 again until the value has become false and come back to 271 true. 273 For 'threshold' it works as described below for 274 mteTriggerThresholdStartup, mteTriggerRisingThreshold, and 275 mteTriggerFallingThreshold." 276 DEFVAL { boolean } 277 ::= { mteTriggerEntry 3 } 279 mteTriggerValueID OBJECT-TYPE 280 SYNTAX OBJECT IDENTIFIER 281 MAX-ACCESS read-create 282 STATUS current 283 DESCRIPTION 284 "The object identifier of the MIB object to check to see 285 if the trigger should fire. 287 This may be wildcarded by truncating all or part of the 288 instance portion, in which case the condition is obtained 289 as if with a GetNext function, checking multiple values 290 if they exist. If such wildcarding is applied, 291 mteTriggerIDWildcard must be 'true' and if not it must 292 be 'false'." 293 DEFVAL { 0 0 } 294 ::= { mteTriggerEntry 4 } 296 mteTriggerValueIDWildcard OBJECT-TYPE 297 SYNTAX TruthValue 298 MAX-ACCESS read-create 299 STATUS current 300 DESCRIPTION 301 "Control over which mteTriggerValueID is to be treated as 302 fully-specified or wildcarded, with 'true' indicating wildcard. 303 DEFVAL { false } 304 ::= { mteTriggerEntry 5 } 306 mteTriggerFrequency OBJECT-TYPE 307 SYNTAX Integer32 (0..65535) 308 UNITS "seconds" 309 MAX-ACCESS read-create 310 STATUS current 311 DESCRIPTION 312 "The number of seconds to wait between trigger condition 313 checks. To encourage consistency in sampling, the 314 interval is measured from the beginning of one check to 315 the beginning of the next and the timer is restarted immediately 316 when it expires, not when the check completes. 318 If the next check begins before the previous one completed the 319 system may either attempt to make the check or treat this as an 320 error condition. 322 A frequency of 0 indicates instantaneous recognition of the 323 condition. This is not possible in many cases, but such may 324 be supported in cases where it makes sense and the system is 325 able to do so." 326 DEFVAL { 600 } 327 ::= { mteTriggerEntry 6 } 329 mteTriggerTargetTag OBJECT-TYPE 330 SYNTAX SnmpTagValue 331 MAX-ACCESS read-create 332 STATUS current 333 DESCRIPTION 334 "The tag for the target(s) from which to obtain the condition 335 for a trigger check. 337 A length of 0 indicates the local system." 338 DEFVAL { ''H } 339 ::= { mteTriggerEntry 7 } 341 mteTriggerBooleanStartup OBJECT-TYPE 342 SYNTAX TruthValue 343 MAX-ACCESS read-create 344 STATUS current 345 DESCRIPTION 346 "Control for whether an event may be triggered when this entry 347 is first set to 'active'. If the value mteTriggerBooleanStartup 348 is 'true' and the first sample after this entry becomes active is 349 true then one mteTriggerEvent is triggered. 351 If mteTriggerType is not 'boolean', this object is not 352 instantiated." 353 DEFVAL { true } 354 ::= { mteTriggerEntry 6 } 356 mteTriggerThresholdStartup OBJECT-TYPE 357 SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } 358 MAX-ACCESS read-create 359 STATUS current 360 DESCRIPTION 361 "The event that may be triggered when this entry is first 362 set to 'active'. If the first sample after this entry 363 becomes active is greater than or equal to 364 mteTriggerRisingThreshold and mteTriggerThresholdStartup is 365 equal to 'rising' or 'risingOrFalling', then one 366 mteTriggerRisingEvent is triggered. If the first 367 sample after this entry becomes active is less than 368 or equal to mteTriggerFallingThreshold and 369 mteTriggerThresholdStartup is equal to 'falling' or 370 'risingOrFalling', then one mteTriggerRisingEvent is triggered. 372 If mteTriggerType is not 'threshold', this object is not 373 instantiated." 374 DEFVAL { risingOrFalling } 375 ::= { mteTriggerEntry 6 } 377 mteTriggerRisingThreshold OBJECT-TYPE 378 SYNTAX Integer32 379 MAX-ACCESS read-create 380 STATUS current 381 DESCRIPTION 382 "A threshold value to check against if mteTriggerType is 383 'threshold'. 385 When the current sampled value is greater than or equal to 386 this threshold, and the value at the last sampling 387 interval was less than this threshold, one mteTriggerRisingEvent 388 is triggered. That event is also triggered if the first sample 389 afer this entry bcomes active is greater than or equal to this 390 threshold and mteTriggerThresholdStartup is equal to 'rising' 391 or 'risingOrFalling'. 393 After a rising event is generated, another such event is not 394 triggered until the sampled value falls below this threshold and 395 reaches mteTriggerFallingThreshold. 397 If mteTriggerType is not 'threshold', this object is not 398 instantiated." 399 DEFVAL { 0 } 400 ::= { mteTriggerEntry 8 } 402 mteTriggerFallingThreshold OBJECT-TYPE 403 SYNTAX Integer32 404 MAX-ACCESS read-create 405 STATUS current 406 DESCRIPTION 407 "A threshold value to check against if mteTriggerType is 408 'threshold'. 410 When the current sampled value is less than or equal to 411 this threshold, and the value at the last sampling interval 412 was greater than this threshold, one mteTriggerFallingEvent 413 is triggered. That event is also triggered if the first sample 414 afer this entry bcomes active is less than or equal to this 415 threshold and mteTriggerThresholdStartup is equal to 'falling' 416 or 'risingOrFalling'. 418 After a falling event is generated, another such event is not 419 triggered until the sampled value rises above this threshold and 420 reaches mteTriggerRisingThreshold. 422 If mteTriggerType is not 'threshold', this object is not 423 instantiated." 424 DEFVAL { 0 } 425 ::= { mteTriggerEntry 9 } 427 mteTriggerEvent OBJECT-TYPE 428 SYNTAX SnmpAdminString (SIZE (0..64)) 429 MAX-ACCESS read-create 430 STATUS current 431 DESCRIPTION 432 "The event to invoke when mteTriggerType is 'boolean' and 433 this trigger fires. A length of 0 indicates no event. 435 If mteTriggerType is not 'boolean', this object is not 436 instantiated." 437 DEFVAL { ''H } 438 ::= { mteTriggerEntry 10 } 440 mteTriggerRisingEvent OBJECT-TYPE 441 SYNTAX SnmpAdminString (SIZE (0..64)) 442 MAX-ACCESS read-create 443 STATUS current 444 DESCRIPTION 445 "The event to invoke when mteTriggerType is 'threshold' and 446 this trigger fires based on mteTriggerRisingThreshold. A 447 value of 0 indicates no event. 449 If mteTriggerType is not 'threshold', this object is not 450 instantiated." 451 DEFVAL { ''H } 452 ::= { mteTriggerEntry 11 } 454 mteTriggerFallingEvent OBJECT-TYPE 455 SYNTAX SnmpAdminString (SIZE (0..64)) 456 MAX-ACCESS read-create 457 STATUS current 458 DESCRIPTION 459 "The event to invoke when mteTriggerType is 'threshold' and 460 this trigger fires based on mteTriggerFallingThreshold. A 461 value of 0 indicates no event. 463 If mteTriggerType is not 'threshold', this object is not 464 instantiated." 465 DEFVAL { ''H } 466 ::= { mteTriggerEntry 12 } 468 mteTriggerStatus OBJECT-TYPE 469 SYNTAX RowStatus 470 MAX-ACCESS read-create 471 STATUS current 472 DESCRIPTION 473 "The control that allows creation and deletion of entries. 474 Once made active an entry may not be modified except to 475 delete it." 476 ::= { mteTriggerEntry 13 } 478 -- 479 -- Event Section 480 -- 482 mteEventFailures OBJECT-TYPE 483 SYNTAX Counter32 484 MAX-ACCESS read-only 485 STATUS current 486 DESCRIPTION 487 "The number of times an attempt to invoke an event 488 has failed. This counts individually for each 489 attempt in a group of targets or each attempt for a 490 wildcarded trigger object." 491 ::= { mteEvent 1 } 493 mteEventLastFailedEvent OBJECT-TYPE 494 SYNTAX SnmpAdminString 495 MAX-ACCESS read-only 496 STATUS current 497 DESCRIPTION 498 "The event that last failed an attempted invocation." 499 ::= { mteEvent 2 } 501 mteEventLastFailedReason OBJECT-TYPE 502 SYNTAX FailureReason 503 MAX-ACCESS read-only 504 STATUS current 505 DESCRIPTION 506 "The reason for the last failure of an attempted event 507 invocation." 508 ::= { mteEvent 3 } 510 mteEventLastFailedTargetTag OBJECT-TYPE 511 SYNTAX SnmpTagValue 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "The target tag of the last failed attempt to invoke an 516 event. The length 0 means this does not apply." 517 ::= { mteEvent 4 } 519 mteEventLastFailedTargetName OBJECT-TYPE 520 SYNTAX SnmpAdminString 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The target name of the last failed attempt to invoke an 525 event. The length 0 means this does not apply" 526 ::= { mteEvent 5 } 528 -- 529 -- Event Table 530 -- 531 mteEventTable OBJECT-TYPE 532 SYNTAX SEQUENCE OF MteEventEntry 533 MAX-ACCESS not-accessible 534 STATUS current 535 DESCRIPTION 536 "A table of management event action information." 537 ::= { mteEvent 6 } 539 mteEventEntry OBJECT-TYPE 540 SYNTAX MteEventEntry 541 MAX-ACCESS not-accessible 542 STATUS current 543 DESCRIPTION 544 "Information about a single event. 546 To create an entry create the named entry in this 547 table use mteEventStatus." 548 INDEX { IMPLIED mteEventName } 549 ::= { mteEventTable 1 } 551 MteEventEntry ::= SEQUENCE { 552 mteEventName SnmpAdminString, 553 mteEventComment DisplayString, 554 mteEventActions BITS, 555 mteEventNotification OBJECT IDENTIFIER, 556 mteEventSetObject OBJECT IDENTIFIER, 557 mteEventSetValue Integer32, 558 mteEventSetTargetTag SnmpTagValue, 559 mteEventCreationStatus RowStatus 560 } 562 mteEventName OBJECT-TYPE 563 SYNTAX SnmpAdminString (SIZE (1..64)) 564 MAX-ACCESS not-accessible 565 STATUS current 566 DESCRIPTION 567 "A locally-unique, administratively assigned name for the event." 568 ::= { mteEventCreationEntry 1 } 570 mteEventComment OBJECT-TYPE 571 SYNTAX DisplayString 572 MAX-ACCESS read-create 573 STATUS current 574 DESCRIPTION 575 "A description of the event's function and use." 577 DEFVAL { ''H } 578 ::= { mteEventEntry 2 } 580 mteEventActions OBJECT-TYPE 581 SYNTAX BITS { notification, set } 582 MAX-ACCESS read-create 583 STATUS current 584 DESCRIPTION 585 "The actions to peform when this event occurs. 587 For 'notification', Traps and/or Informs are sent according 588 to the configuration in the SNMP-NOTIFICATION-MIB. 590 For 'set', an SNMP Set operation is performed according to 591 control values in this entry." 592 DEFVAL { 0 } 593 ::= { mteEventEntry 3 } 595 mteEventNotification OBJECT-TYPE 596 SYNTAX OBJECT IDENTIFIER 597 MAX-ACCESS read-create 598 STATUS current 599 DESCRIPTION 600 "The object identifier from the NOTIFICATION-TYPE for the 601 notification to use if metEventActions has 'notification' set. 603 If 'notification' is not set, this object is not instantiated." 604 DEFVAL { 0 0 } 605 ::= { mteEventEntry 4 } 607 mteEventSetObject OBJECT-TYPE 608 SYNTAX OBJECT IDENTIFIER 609 MAX-ACCESS read-create 610 STATUS current 611 DESCRIPTION 612 "The object identifier from the MIB object to set if 613 metEventActions has 'set' set. 615 If 'set' is not set, this object is not instantiated." 616 DEFVAL { 0 0 } 617 ::= { mteEventEntry 5 } 619 mteEventSetObjectWildcard OBJECT-TYPE 620 SYNTAX TruthValue 621 MAX-ACCESS read-create 622 STATUS current 623 DESCRIPTION 624 "Control over whether mteEventSetObject is to be treated as 625 fully-specified or wildcarded, with 'true' indicating wildcard. 627 If mteEventSetObject is wildcarded the instance used to set it 628 is the same as the instance for the value of mteTriggerValueID 629 that triggered the event." 630 DEFVAL { false } 631 ::= { mteEventEntry 6 } 633 mteEventSetValue OBJECT-TYPE 634 SYNTAX Integer32 635 MAX-ACCESS read-create 636 STATUS current 637 DESCRIPTION 638 "The value to which to set the object at mteEventSetObject." 639 DEFVAL { 0 } 640 ::= { mteEventEntry 7 } 642 mteEventSetTargetTag OBJECT-TYPE 643 SYNTAX SnmpTagValue 644 MAX-ACCESS read-create 645 STATUS current 646 DESCRIPTION 647 "The tag for the target(s) at which to set the object at 648 mteEventSetObject to mteEventSetValue. A length of 0 649 indicates the local system." 650 DEFVAL { ''H } 651 ::= { mteEventEntry 8 } 653 mteEventStatus OBJECT-TYPE 654 SYNTAX RowStatus 655 MAX-ACCESS read-create 656 STATUS current 657 DESCRIPTION 658 "The control that allows creation and deletion of entries. 659 Once made active an entry may not be modified except to 660 delete it." 661 ::= { mteEventEntry 9 } 663 -- 664 -- Notifications 665 -- 666 eventMIBNotificationPrefix OBJECT IDENTIFIER ::= { eventMIB 2 } 667 eventMIBNotifications OBJECT IDENTIFIER ::= { eventMIBNotificationPrefix 0 } 669 mteTriggerSenseAlarm NOTIFICATION-TYPE 670 OBJECTS { mteTriggerTargetName, 671 mteTriggerLastValueID, 672 mteTriggerLastValue } 673 STATUS current 674 DESCRIPTION 675 "Notification that the trigger indicated by the object 676 instances has fired, for triggers with mteTriggerType 677 'boolean'." 678 ::= { eventMIBNotifications 1 } 680 mteTriggerRisingAlarm NOTIFICATION-TYPE 681 OBJECTS { mteTriggerTargetName, 682 mteTriggerLastValueID, 683 mteTriggerLastValue } 684 STATUS current 685 DESCRIPTION 686 "Notification that the rising threshold was met for triggers 687 with mteTriggerType 'threshold'." 688 ::= { eventMIBNotifications 2 } 690 mteTriggerFallingAlarm NOTIFICATION-TYPE 691 OBJECTS { mteTriggerTargetName, 692 mteTriggerLastValueID, 693 mteTriggerLastValue } 694 STATUS current 695 DESCRIPTION 696 "Notification that the falling threshold was met for triggers 697 with mteTriggerType 'threshold'." 698 ::= { eventMIBNotifications 3 } 700 mteTriggerFailureAlarm NOTIFICATION-TYPE 701 OBJECTS { mteTriggerLastFailedReason, 702 mteTriggerLastFailedTargetTag, 703 mteTriggerLastFailedTargetName, 704 mteTriggerLastFailedValueID } 705 STATUS current 706 DESCRIPTION 707 "Notification that an attempt to check a trigger has failed. 709 The network manager must enable this notification only with 710 a certain fear and trembling, as it can easily crowd out more 711 important information. It should be used only to help diagnose 712 a problem that has appeared in the error counters and can not 713 be found otherwise." 714 ::= { eventMIBNotifications 4 } 716 mteEventFailureAlarm NOTIFICATION-TYPE 717 OBJECTS { mteTriggerTargetName, 718 mteTriggerLastValueID, 719 mteTriggerLastValue, 720 mteEventLastFailedReason, 721 mteEventLastFailedTargetTag, 722 mteEventLastFailedTargetName } 723 STATUS current 724 DESCRIPTION 725 "Notification that an attempt to check a trigger has failed. 727 The network manager must enable this notification only with 728 a certain fear and trembling, as it can easily crowd out more 729 important information. It should be used only to help diagnose 730 a problem that has appeared in the error counters and can not 731 be found otherwise." 732 ::= { eventMIBNotifications 5 } 734 -- The compliance statements have yet to be written. The intent is 735 -- that all objects are required except where otherwise mentioned above 736 -- and that a self-managing system need not support remote checking, 737 -- or wildcarding. 739 END 740 6. Acknowledgements 742 This MIB contains considerable contributions from the RMON MIB, the 743 Distributed Management Design Team (Andy Bierman, Maria Greene, Bob 744 Stewart, and Steve Waldbusser), and colleagues at Cisco. 746 7. References 748 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 749 S. Waldbusser, "Structure of Management Information for version 2 750 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 751 January 1996. 753 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 754 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 755 RFC 1213, March 1991. 757 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 758 Management Protocol", RFC 1157, May 1990. 760 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 761 S. Waldbusser, "Protocol Operations for version 2 of the Simple 762 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 764 8. Security Considerations 766 Security issues are not discussed in this memo. 768 9. Author's Address 770 Bob Stewart 771 Cisco Systems, Inc. 772 170 West Tasman Drive 773 San Jose, CA 95134-1706 775 Phone: 408-526-4527 776 Email: bstewart@cisco.com 778 Table of Contents 780 1 Abstract ........................................................ 2 781 2 The SNMP Network Management Framework ........................... 3 782 2.1 Object Definitions ............................................ 3 783 3 Overview ........................................................ 4 784 4 Known Problems .................................................. 4 785 5 Definitions ..................................................... 5 786 6 Acknowledgements ................................................ 20 787 7 References ...................................................... 21 788 8 Security Considerations ......................................... 22 789 9 Author's Address ................................................ 22