idnits 2.17.1 draft-ietf-disman-event-mib-01.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-25) 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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 8) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 7 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 (26 March 1997) is 9892 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: 13 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Event MIB 26 March 1997 4 Event MIB 6 26 March 1997 8 draft-ietf-disman-event-mib-01.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 learn the current status of any Internet-Draft, please check the 27 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 28 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 29 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 31 1. Abstract 33 This memo defines an experimental portion of the Management Information 34 Base (MIB) for use with network management protocols in the Internet 35 community. In particular, it describes managed objects used for 36 managing monitoring of MIB objects and taking action through events. 38 2. The SNMP Network Management Framework 40 They are: The SNMP Network Management Framework presently consists of 41 three major 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 Target, Notification, and Expression 70 MIBs. 72 All of this must suit either a relatively powerful manager or mid-level 73 manager, as well as a somewhat more limited self-managing system. 75 4. Definitions 77 EVENT-MIB DEFINITIONS ::= BEGIN 79 IMPORTS 80 MODULE-IDENTITY, OBJECT-TYPE, 81 experimental, Integer32, Unsigned32 82 NOTIFICATION-TYPE FROM SNMPv2-SMI 83 TEXTUAL-CONVENTION, RowStatus, 84 TimeStamp, DisplayString, 85 AutonomousType, DateAndTime FROM SNMPv2-TC 86 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 87 EntryIndex, EntryName, 88 EntryIndexOrZero FROM MANAGEMENT-TARGET-MIB 89 FailureReason FROM NOTIFICATION-MIB 91 eventMIB MODULE-IDENTITY 92 LAST-UPDATED "9703241700Z" 93 ORGANIZATION "IETF Distributed Management Working Group" 94 CONTACT-INFO "Bob Stewart 95 Cisco Systems, Inc. 96 170 West Tasman Drive, 97 San Jose CA 95134-1706. 98 Phone: +1 408 526 4527 99 Email: bstewart@cisco.com" 100 DESCRIPTION 101 "The MIB module for defining event triggers and actions 102 for network management purposes." 103 ::= { experimental xx } 105 eventMIBObjects OBJECT IDENTIFIER ::= { eventMIB 1 } 107 mteTrigger OBJECT IDENTIFIER ::= { eventMIBObjects 1 } 108 mteEvent OBJECT IDENTIFIER ::= { eventMIBObjects 2 } 110 -- 111 -- Trigger Section 112 -- 114 mteTriggerLastChange OBJECT-TYPE 115 SYNTAX TimeStamp 116 MAX-ACCESS read-only 117 STATUS current 118 DESCRIPTION 119 "The value of sysUpTime at the most recent addition or 120 deletion of a trigger or a trigger name change. 122 A management application can monitor this object to 123 know that the trigger list has changed in a way 124 requiring reloading of the trigger names." 125 ::= { mteTrigger 1 } 127 mteTriggerFailures OBJECT-TYPE 128 SYNTAX Counter32 129 MAX-ACCESS read-only 130 STATUS current 131 DESCRIPTION 132 "The number of times an attempt to check for a trigger 133 condition has failed. This counts individually for each 134 attempt in a group of targets or each attempt for a 135 wildcarded object." 136 ::= { mteTrigger 2 } 138 mteTriggerLastFailedTrigger OBJECT-TYPE 139 SYNTAX triggerIndex 140 MAX-ACCESS read-only 141 STATUS current 142 DESCRIPTION 143 "The trigger that last failed an attempt to check for a 144 trigger condition." 145 ::= { mteTrigger 3 } 147 mteTriggerLastFailedReason OBJECT-TYPE 148 SYNTAX FailureReason 149 MAX-ACCESS read-only 150 STATUS current 151 DESCRIPTION 152 "The reason for the last failure of an attempt to check 153 for a trigger condition." 154 ::= { mteTrigger 4 } 156 mteTriggerLastFailedTargetGroup OBJECT-TYPE 157 SYNTAX EntryIndexOrZero 158 MAX-ACCESS read-only 159 STATUS current 160 DESCRIPTION 161 "The target group of the last failed attempt to check a 162 trigger condition. The value 0 means this does not apply." 163 ::= { mteTrigger 5 } 165 mteTriggerLastFailedTargetScope OBJECT-TYPE 166 SYNTAX EntryIndexOrZero 167 MAX-ACCESS read-only 168 STATUS current 169 DESCRIPTION 170 "The target scope of the last failed attempt to check a 171 trigger condition. The value 0 means this does not apply" 172 ::= { mteTrigger 6 } 174 mteTriggerLastValueID OBJECT-TYPE 175 SYNTAX OBJECT IDENTIFIER 176 MAX-ACCESS read-only 177 STATUS current 178 DESCRIPTION 179 "The object identifier from mteTriggerValueID from the last 180 attempt to check a trigger condition. This must 181 be as full-qualified as possible, including filling in 182 wild-card information determined in processing." 183 ::= { mteTrigger 7 } 185 mteTriggerLastValue OBJECT-TYPE 186 SYNTAX Integer32 187 MAX-ACCESS notification-only 188 STATUS current 189 DESCRIPTION 190 "The value of the object at mteTriggerValueID when a 191 trigger fires." 192 ::= { mteTrigger 8 } 194 mteTriggerTargetScope OBJECT-TYPE 195 SYNTAX EntryIndexOrZero 196 MAX-ACCESS notification-only 197 STATUS current 198 DESCRIPTION 199 "The targetIndex of the scope for which the trigger fires 200 or for which a check was attempted." 201 ::= { mteTrigger 9 } 203 -- 204 -- Trigger Creation Table 205 -- 207 mteTriggerCreationTable OBJECT-TYPE 208 SYNTAX SEQUENCE OF MteTriggerCreationEntry 209 MAX-ACCESS not-accessible 210 STATUS current 211 DESCRIPTION 212 "A table of triggers for network management events." 213 ::= { mteTrigger 10 } 215 mteTriggerCreationEntry OBJECT-TYPE 216 SYNTAX MteTriggerCreationEntry 217 MAX-ACCESS not-accessible 218 STATUS current 219 DESCRIPTION 220 "Information about a single trigger. 222 To create an entry create the named entry in this 223 table and activate it with mteTriggerCreationStatus. Then use 224 mteTriggerIndex to populate mteTriggerTable. 226 Deleting an entry deletes the related entry in 227 mteTriggerTable." 228 INDEX { IMPLIED mteTriggerCreationName } 229 ::= { mteTriggerCreationTable 1 } 231 MteTriggerCreationEntry ::= SEQUENCE { 232 mteTriggerCreationName EntryName, 233 mteTriggerIndex EntryIndex, 234 mteTriggerCreationStatus RowStatus 235 } 237 mteTriggerCreationName OBJECT-TYPE 238 SYNTAX EntryName 239 MAX-ACCESS not-accessible 240 STATUS current 241 DESCRIPTION 242 "A locally-unique, administratively assigned name for the 243 trigger." 244 ::= { mteTriggerCreationEntry 1 } 246 mteTriggerIndex OBJECT-TYPE 247 SYNTAX EntryIndex 248 MAX-ACCESS read-only 249 STATUS current 250 DESCRIPTION 251 "The numeric identification of the trigger." 252 ::= { mteTriggerCreationEntry 2 } 254 mteTriggerCreationStatus OBJECT-TYPE 255 SYNTAX RowStatus 256 MAX-ACCESS read-create 257 STATUS current 258 DESCRIPTION 259 "The control that allows creation/deletion of entries. 260 Once made active an entry may not be modified except to 261 delete it or change its name via mteTriggerName." 262 ::= { mteTriggerCreationEntry 3 } 264 -- 265 -- Trigger Table 266 -- 268 mteTriggerTable OBJECT-TYPE 269 SYNTAX SEQUENCE OF MteTriggerEntry 270 MAX-ACCESS not-accessible 271 STATUS current 272 DESCRIPTION 273 "A table of management event trigger information." 274 ::= { mteTrigger 11 } 276 mteTriggerEntry OBJECT-TYPE 277 SYNTAX MteTriggerEntry 278 MAX-ACCESS not-accessible 279 STATUS current 280 DESCRIPTION 281 "Information about a single management event trigger. 283 An entry appears in this table when an mteTriggerCreationEntry 284 is activated. Deleting the matching mteTriggerCreationEntry 285 deletes this entry." 286 INDEX { mteTriggerIndex } 287 ::= { mteTriggerteble 1 } 289 MteTriggerEntry ::= SEQUENCE { 290 mteTriggerName EntryName, 291 mteTriggerComment DisplayString, 292 mteTriggerTest INTEGER, 293 mteTriggerValueID Integer32, 294 mteTriggerFrequency Integer32, 295 mteTriggerTarget EntryIndexOrZero, 296 mteTriggerRisingThreshold Integer32, 297 mteTriggerFallingThreshold Integer32, 298 mteTriggerEvent EntryIndexOrZero, 299 mteTriggerRisingEvent EntryIndexOrZero, 300 mteTriggerFallingEvent EntryIndexOrZero 301 } 303 mteTriggerName OBJECT-TYPE 304 SYNTAX EntryName 305 MAX-ACCESS read-write 306 STATUS current 307 DESCRIPTION 308 "The unique name of the target trigger, identical to 309 mteTriggerCreationName. 311 Use this object to change the trigger's mteTriggerCreationName 312 without changing its mteTriggerIndex." 313 ::= { mteTriggerEntry 1 } 315 mteTriggerComment OBJECT-TYPE 316 SYNTAX DisplayString 317 MAX-ACCESS read-write 318 STATUS current 319 DESCRIPTION 320 "A description of the trigger's function and use." 321 DEFVAL { ''H } 322 ::= { mteTriggerEntry 2 } 324 mteTriggerTest OBJECT-TYPE 325 SYNTAX INTEGER { boolean(1), threshold(2) } 326 MAX-ACCESS read-write 327 STATUS current 328 DESCRIPTION 329 "The type of trigger test to perform. For all tests, 330 mteTriggerValue must evaluate to an integer. 332 For 'boolean', a value of 0 is false. A non-zero value 333 is true and fires the trigger. 335 For 'threshold' it works like RMON and the text needs to 336 be copied into this MIB." 337 DEFVAL { boolean } 338 ::= { mteTriggerEntry 3 } 340 mteTriggerValueID OBJECT-TYPE 341 SYNTAX OBJECT IDENTIFIER 342 MAX-ACCESS read-write 343 STATUS current 344 DESCRIPTION 345 "The object identifier of the MIB object to check to see 346 if the trigger should fire. 348 This may be wildcarded by truncating all or part of the 349 instance portion, in which case the condition is obtained 350 as if with a GetNext function, checking multiple values 351 if they exist." 352 DEFVAL { 0 0 } 353 ::= { mteTriggerEntry 4 } 355 mteTriggerFrequency OBJECT-TYPE 356 SYNTAX Integer32 (1..65535) 357 UNITS "seconds" 358 MAX-ACCESS read-write 359 STATUS current 360 DESCRIPTION 361 "The number of seconds to wait between trigger condition 362 checks. To encourage consistency in sampling, the 363 interval is measured from the beginning of one check to 364 the beginning of the next." 365 DEFVAL { 600 } 366 ::= { mteTriggerEntry 5 } 368 mteTriggerTarget OBJECT-TYPE 369 SYNTAX EntryIndexOrZero 370 MAX-ACCESS read-write 371 STATUS current 372 DESCRIPTION 373 "The targetIndex of the scope or group of scopes from 374 which to obtain the condition for a trigger check. 376 A value of 0 indicates the local system." 377 DEFVAL { 0 } 378 ::= { mteTriggerEntry 6 } 380 mteTriggerRisingThreshold OBJECT-TYPE 381 SYNTAX Integer32 382 MAX-ACCESS read-write 383 STATUS current 384 DESCRIPTION 385 "A threshold value to check against if mteTriggerType is 386 'threshold'. In this case if the value of the object at 387 mteTriggerValueID is greater than or equal to this threshold 388 and the value at the last sampling interval was less than 389 this threshold, one mteTriggerRisingEvent is triggered. 391 If mteTriggerType is not 'threshold', this object is not 392 instantiated." 393 DEFVAL { 0 } 394 ::= { mteTriggerEntry 7 } 396 mteTriggerFallingThreshold OBJECT-TYPE 397 SYNTAX Integer32 398 MAX-ACCESS read-write 399 STATUS current 400 DESCRIPTION 401 "A threshold value to check against if mteTriggerType is 402 'threshold'. In this case if the value of the object at 403 mteTriggerValueID is less than or equal to this threshold 404 and the value at the last sampling interval was greater than 405 this threshold, one mteTriggerFallingEvent is triggered. 407 If mteTriggerType is not 'threshold', this object is not 408 instantiated." 409 DEFVAL { 0 } 410 ::= { mteTriggerEntry 8 } 412 mteTriggerEvent OBJECT-TYPE 413 SYNTAX EntryIndexOrZero 414 MAX-ACCESS read-write 415 STATUS current 416 DESCRIPTION 417 "The event to invoke when mteTriggerType is 'boolean' and 418 this trigger fires. A value of 0 indicates no event. 420 If mteTriggerType is not 'boolean', this object is not 421 instantiated." 422 DEFVAL { 0 } 423 ::= { mteTriggerEntry 9 } 425 mteTriggerRisingEvent OBJECT-TYPE 426 SYNTAX EntryIndexOrZero 427 MAX-ACCESS read-write 428 STATUS current 429 DESCRIPTION 430 "The event to invoke when mteTriggerType is 'threshold' and 431 this trigger fires based on mteTriggerRisingThreshold. A 432 value of 0 indicates no event. 434 If mteTriggerType is not 'threshold', this object is not 435 instantiated." 437 DEFVAL { 0 } 438 ::= { mteTriggerEntry 10 } 440 mteTriggerFallingEvent OBJECT-TYPE 441 SYNTAX EntryIndexOrZero 442 MAX-ACCESS read-write 443 STATUS current 444 DESCRIPTION 445 "The event to invoke when mteTriggerType is 'threshold' and 446 this trigger fires based on mteTriggerFallingThreshold. A 447 value of 0 indicates no event. 449 If mteTriggerType is not 'threshold', this object is not 450 instantiated." 451 DEFVAL { 0 } 452 ::= { mteTriggerEntry 11 } 454 -- 455 -- Event Section 456 -- 458 mteEventLastChange OBJECT-TYPE 459 SYNTAX TimeStamp 460 MAX-ACCESS read-only 461 STATUS current 462 DESCRIPTION 463 "The value of sysUpTime at the most recent addition or 464 deletion of an event or an event name change. 466 A management application can monitor this object to 467 know that the event list has changed in a way 468 requiring reloading of the event names." 469 ::= { mteEvent 1 } 471 mteEventFailures OBJECT-TYPE 472 SYNTAX Counter32 473 MAX-ACCESS read-only 474 STATUS current 475 DESCRIPTION 476 "The number of times an attempt to invoke an event 477 has failed. This counts individually for each 478 attempt in a group of targets or each attempt for a 479 wildcarded trigger object." 480 ::= { mteEvent 2 } 482 mteEventLastFailedEvent OBJECT-TYPE 483 SYNTAX eventIndex 484 MAX-ACCESS read-only 485 STATUS current 486 DESCRIPTION 487 "The event that last failed an attempted invocation." 488 ::= { mteEvent 3 } 490 mteEventLastFailedReason OBJECT-TYPE 491 SYNTAX FailureReason 492 MAX-ACCESS read-only 493 STATUS current 494 DESCRIPTION 495 "The reason for the last failure of an attempted event 496 invocation." 497 ::= { mteEvent 4 } 499 mteEventLastFailedTargetGroup OBJECT-TYPE 500 SYNTAX EntryIndexOrZero 501 MAX-ACCESS read-only 502 STATUS current 503 DESCRIPTION 504 "The target group of the last failed attempt to invoke an 505 event. The value 0 means this does not apply." 506 ::= { mteEvent 5 } 508 mteEventLastFailedTargetScope OBJECT-TYPE 509 SYNTAX EntryIndexOrZero 510 MAX-ACCESS read-only 511 STATUS current 512 DESCRIPTION 513 "The target scope of the last failed attempt to invoke an 514 event. The value 0 means this does not apply" 515 ::= { mteEvent 6 } 517 -- 518 -- Event Creation Table 519 -- 521 mteEventCreationTable OBJECT-TYPE 522 SYNTAX SEQUENCE OF MteEventCreationEntry 523 MAX-ACCESS not-accessible 524 STATUS current 525 DESCRIPTION 526 "A table of events for network management action." 528 ::= { mteEvent 7 } 530 mteEventCreationEntry OBJECT-TYPE 531 SYNTAX MteEventCreationEntry 532 MAX-ACCESS not-accessible 533 STATUS current 534 DESCRIPTION 535 "Information about a single event. 537 To create an entry create the named entry in this 538 table and activate it with mteEventCreationStatus. Then use 539 mteEventIndex to populate mteEventTable. 541 Deleting an entry deletes the related entry in 542 mteEventTable." 543 INDEX { IMPLIED mteEventCreationName } 544 ::= { mteEventCreationTable 1 } 546 MteEventCreationEntry ::= SEQUENCE { 547 mteEventCreationName EntryName, 548 mteEventIndex EntryIndex, 549 mteEventCreationStatus RowStatus 550 } 552 mteEventCreationName OBJECT-TYPE 553 SYNTAX EntryName 554 MAX-ACCESS not-accessible 555 STATUS current 556 DESCRIPTION 557 "A locally-unique, administratively assigned name for the event." 558 ::= { mteEventCreationEntry 1 } 560 mteEventIndex OBJECT-TYPE 561 SYNTAX EntryIndex 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "The numeric identification of the event." 566 ::= { mteEventCreationEntry 2 } 568 mteEventCreationStatus OBJECT-TYPE 569 SYNTAX RowStatus 570 MAX-ACCESS read-create 571 STATUS current 572 DESCRIPTION 573 "The control that allows creation/deletion of entries. 574 Once made active an entry may not be modified except to 575 delete it or change its name via mteEventName." 576 ::= { mteEventCreationEntry 3 } 578 -- 579 -- Event Table 580 -- 582 mteEventTable OBJECT-TYPE 583 SYNTAX SEQUENCE OF MteEventEntry 584 MAX-ACCESS not-accessible 585 STATUS current 586 DESCRIPTION 587 "A table of management event action information." 588 ::= { mteEvent 3 } 590 mteEventEntry OBJECT-TYPE 591 SYNTAX MteEventEntry 592 MAX-ACCESS not-accessible 593 STATUS current 594 DESCRIPTION 595 "Information about a single management event's actions. 597 An entry appears in this table when an mteEventCreationEntry 598 is activated. Deleting the matching mteEventCreationEntry 599 deletes this entry." 600 INDEX { mteEventIndex } 601 ::= { mteEventTable 1 } 603 MteEventEntry ::= SEQUENCE { 604 mteEventName EntryName, 605 mteEventComment DisplayString, 606 mteEventActions BITS, 607 mteEventNotification OBJECT IDENTIFIER, 608 mteEventSetObject OBJECT IDENTIFIER, 609 mteEventSetValue Integer32, 610 mteEventTarget EntryIndexOrZero 611 } 613 mteEventName OBJECT-TYPE 614 SYNTAX EntryName 615 MAX-ACCESS read-write 616 STATUS current 617 DESCRIPTION 618 "The unique name of the event, identical to 619 mteEventCreationName. 621 Use this object to change the event's mteEventCreationName 622 without changing its mteEventIndex." 623 ::= { mteEventEntry 1 } 625 mteEventComment OBJECT-TYPE 626 SYNTAX DisplayString 627 MAX-ACCESS read-write 628 STATUS current 629 DESCRIPTION 630 "A description of the event's function and use." 631 DEFVAL { ''H } 632 ::= { mteEventEntry 2 } 634 mteEventActions OBJECT-TYPE 635 SYNTAX BITS { notification, trap, inform, set } 636 MAX-ACCESS read-write 637 STATUS current 638 DESCRIPTION 639 "The actions to peform when this event occurs. 641 For 'notification', Traps and/or Informs are sent according 642 to the configuration in the Notification MIB.. 644 For 'trap', Traps are sent unless the Notification MIB 645 has the Trap 'hardDisabled' or there are no targets for it. 647 For 'inform', Informs are sent unless the Notification MIB 648 has the Inform 'hardDisabled' or there are no targets for it. 650 For 'set', an SNMP Set operation is performed according to 651 control values in this entry." 652 DEFVAL { 0 } 653 ::= { mteEventEntry 3 } 655 mteEventNotification OBJECT-TYPE 656 SYNTAX OBJECT IDENTIFIER 657 MAX-ACCESS read-write 658 STATUS current 659 DESCRIPTION 660 "The object identifier from the NOTIFICATION-TYPE for the 661 notification to use if metEventActions has 'notification', 662 'trap', or 'inform' set. 664 If none of the above bits are set, this object is not 665 instantiated." 666 DEFVAL { 0 0 } 667 ::= { mteEventEntry 4 } 669 mteEventSetObject OBJECT-TYPE 670 SYNTAX OBJECT IDENTIFIER 671 MAX-ACCESS read-write 672 STATUS current 673 DESCRIPTION 674 "The object identifier from the MIB object to set if 675 metEventActions has 'set' set. 677 If 'set' is not set, this object is not instantiated." 678 DEFVAL { 0 0 } 679 ::= { mteEventEntry 5 } 681 mteEventSetValue OBJECT-TYPE 682 SYNTAX Integer32 683 MAX-ACCESS read-write 684 STATUS current 685 DESCRIPTION 686 "The value to which to set the object at mteEventSetObect." 687 DEFVAL { 0 } 688 ::= { mteEventEntry 6 } 690 mteEventSetTarget OBJECT-TYPE 691 SYNTAX EntryIndexOrZero 692 MAX-ACCESS read-write 693 STATUS current 694 DESCRIPTION 695 "A scope or group of scopes in which to the object at 696 mteEventSetObject to mteEventSetValue. A value of 0 697 indicates the local system." 698 DEFVAL { 0 } 699 ::= { mteEventEntry 7 } 701 -- 702 -- Notifications 703 -- 705 eventMIBNotificationPrefix OBJECT IDENTIFIER ::= { eventMIB 2 } 706 eventMIBNotifications OBJECT IDENTIFIER ::= { eventMIBNotificationPrefix 0 } 707 mteTriggerSenseAlarm NOTIFICATION-TYPE 708 OBJECTS { mteTriggerName, 709 mteTriggerTargetScope, 710 mteTriggerLastValueID, 711 mteTriggerLastValue } 712 STATUS current 713 DESCRIPTION 714 "Notification that the trigger indicated by the object 715 instances has fired, for triggers with mteTriggerType 716 'boolean'." 717 ::= { eventMIBNotifications 1 } 719 mteTriggerRisingAlarm NOTIFICATION-TYPE 720 OBJECTS { mteTriggerName, 721 mteTriggerTargetScope, 722 mteTriggerLastValueID, 723 mteTriggerLastValue } 724 STATUS current 725 DESCRIPTION 726 "Notification that the rising threshold was met for triggers 727 with mteTriggerType 'threshold'." 728 ::= { eventMIBNotifications 2 } 730 mteTriggerFallingAlarm NOTIFICATION-TYPE 731 OBJECTS { mteTriggerName, 732 mteTriggerTargetScope, 733 mteTriggerLastValueID, 734 mteTriggerLastValue } 735 STATUS current 736 DESCRIPTION 737 "Notification that the falling threshold was met for triggers 738 with mteTriggerType 'threshold'." 739 ::= { eventMIBNotifications 3 } 741 mteTriggerFailureAlarm NOTIFICATION-TYPE 742 OBJECTS { mteTriggerName, 743 mteTriggerLastFailedReason, 744 mteTriggerLastFailedTargetGroup, 745 mteTriggerLastFailedTargetScope, 746 mteTriggerLastFailedValueID } 747 STATUS current 748 DESCRIPTION 749 "Notification that an attempt to check a trigger has failed. 751 The network manager must enable this notification only with 752 a certain fear and trembling, as it can easily crowd out more 753 important information. It should be used only to help diagnose 754 a problem that has appeared in the error counters and can not 755 be found otherwise." 756 ::= { eventMIBNotifications 4 } 758 mteEventFailureAlarm NOTIFICATION-TYPE 759 OBJECTS { mteTriggerName, 760 mteTriggerTargetScope, 761 mteTriggerLastValueID, 762 mteTriggerLastValue, 763 mteEventLastFailedReason, 764 mteEventLastFailedTargetGroup, 765 mteEventLastFailedTargetScope } 766 STATUS current 767 DESCRIPTION 768 "Notification that an attempt to check a trigger has failed. 770 The network manager must enable this notification only with 771 a certain fear and trembling, as it can easily crowd out more 772 important information. It should be used only to help diagnose 773 a problem that has appeared in the error counters and can not 774 be found otherwise." 775 ::= { eventMIBNotifications 5 } 777 -- The compliance statements have yet to be written. The intent is 778 -- that all objects are required except where otherwise mentioned above 779 -- and that a self-managing system need not support groups, remote checking, 780 -- or wildcarding. 782 END 783 5. Acknowledgements 785 This MIB contains considerable contributions from the RMON MIB, the 786 Distributed Management Design Team (Andy Bierman, Maria Greene, Bob 787 Stewart, and Steve Waldbusser), and colleagues at Cisco. 789 6. References 791 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 792 S. Waldbusser, "Structure of Management Information for version 2 793 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 794 January 1996. 796 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 797 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 798 RFC 1213, March 1991. 800 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 801 Management Protocol", RFC 1157, May 1990. 803 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 804 S. Waldbusser, "Protocol Operations for version 2 of the Simple 805 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 807 7. Security Considerations 809 Security issues are not discussed in this memo. 811 8. Author's Address 813 Bob Stewart 814 Cisco Systems, Inc. 815 170 West Tasman Drive 816 San Jose, CA 95134-1706 818 Phone: 408-526-4527 819 Email: bstewart@cisco.com 821 Table of Contents 823 1 Abstract ........................................................ 2 824 2 The SNMP Network Management Framework ........................... 3 825 2.1 Object Definitions ............................................ 3 826 3 Overview ........................................................ 4 827 4 Definitions ..................................................... 5 828 5 Acknowledgements ................................................ 21 829 6 References ...................................................... 22 830 7 Security Considerations ......................................... 23 831 8 Author's Address ................................................ 23