idnits 2.17.1 draft-ietf-disman-event-mib-02.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-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. ** 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 2 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** There are 530 instances of lines with control characters in the document. 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 (21 November 1997) is 9652 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') -- Possible downref: Non-RFC (?) normative reference: ref. '4' Summary: 13 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Event MIB 21 November 1997 3 Event MIB 4 draft-ietf-disman-event-mib-02.txt 6 21 November 1997 8 Bob Stewart 9 Cisco Systems, Inc. 10 bstewart@cisco.com 12 Status of this Memo 14 This document is an Internet-Draft. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its areas, and 16 its working groups. Note that other groups may also distribute working 17 documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet- Drafts as reference material 22 or to cite them other than as ``work in progress.'' 24 To learn the current status of any Internet-Draft, please check the 25 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 26 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 27 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 29 9 30 1. Abstract 32 This memo defines an experimental portion of the Management Information 33 Base (MIB) for use with network management protocols in the Internet 34 community. In particular, it describes managed objects used for 35 managing monitoring of MIB objects and taking action through events. 37 9 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 9 67 3. Overview 69 This MIB is based heavily on the RMON and Manager-to-Manager MIBs. It 70 depends on the services of the Target, Notification, and Expression 71 MIBs. 73 All of this must suit either a relatively powerful manager or mid-level 74 manager, as well as a somewhat more limited self-managing system. 76 4. Known Problems 78 The error code for a failure comes from a now non-existent MIB. I 79 suppose those codes will need to be transplanted here. 81 The error handling depeds somewhat on notifications and had assumed the 82 existence of a logging MIB, which evaporated as did the above-mentioned 83 error codes. 85 The description of RMON-like threshold operation is broken and needs to 86 be changed to be like RMON. 88 The compliance section is missing. 90 9 91 5. Definitions 93 EVENT-MIB DEFINITIONS ::= BEGIN 95 IMPORTS 96 MODULE-IDENTITY, OBJECT-TYPE, 97 experimental, Integer32, Unsigned32 98 NOTIFICATION-TYPE FROM SNMPv2-SMI 99 TEXTUAL-CONVENTION, RowStatus, 100 TimeStamp, DisplayString, 101 AutonomousType, DateAndTime FROM SNMPv2-TC 102 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 103 FailureReason FROM NOTIFICATION-MIB 104 SnmpTagValue FROM SNMP-TARGET-MIB 105 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 107 eventMIB MODULE-IDENTITY 108 LAST-UPDATED "9703241700Z" 109 ORGANIZATION "IETF Distributed Management Working Group" 110 CONTACT-INFO "Bob Stewart 111 Cisco Systems, Inc. 112 170 West Tasman Drive, 113 San Jose CA 95134-1706. 114 Phone: +1 408 526 4527 115 Email: bstewart@cisco.com" 116 DESCRIPTION 117 "The MIB module for defining event triggers and actions 118 for network management purposes." 119 ::= { experimental xx } 121 eventMIBObjects OBJECT IDENTIFIER ::= { eventMIB 1 } 123 mteTrigger OBJECT IDENTIFIER ::= { eventMIBObjects 1 } 124 mteEvent OBJECT IDENTIFIER ::= { eventMIBObjects 2 } 126 -- 127 -- Textual Conventions 128 -- 130 EntryName ::= TEXTUAL-CONVENTION 131 STATUS current 132 DESCRIPTION 133 "An identification for an entry. An EntryName corresponds 134 one-to-one to an EntryIndex. 136 This identification of an entry is subject to change 137 only by administrative request." 138 SYNTAX SnmpAdminString 140 EntryIndex ::= TEXTUAL-CONVENTION 141 STATUS current 142 DESCRIPTION 143 "An integer shorthand identification for an entry. 144 An EntryIndex corresponds one-to-one to an EntryName. 146 Once assigned an EntryIndex may not be changed." 147 SYNTAX Unsigned32 (1..4294967295) 149 EntryIndexOrZero ::= TEXTUAL-CONVENTION 150 STATUS current 151 DESCRIPTION 152 "Either an EntryIndex or zero. The meaning of zero 153 depends on the DESCRIPTION of the object." 154 SYNTAX Unsigned32 (0..4294967295) 156 -- 157 -- Trigger Section 158 -- 160 mteTriggerLastChange OBJECT-TYPE 161 SYNTAX TimeStamp 162 MAX-ACCESS read-only 163 STATUS current 164 DESCRIPTION 165 "The value of sysUpTime at the most recent addition or 166 deletion of a trigger or a trigger name change. 168 A management application can monitor this object to 169 know that the trigger list has changed in a way 170 requiring reloading of the trigger names." 171 ::= { mteTrigger 1 } 173 mteTriggerFailures OBJECT-TYPE 174 SYNTAX Counter32 175 MAX-ACCESS read-only 176 STATUS current 177 DESCRIPTION 178 "The number of times an attempt to check for a trigger 179 condition has failed. This counts individually for each 180 attempt in a group of targets or each attempt for a 181 wildcarded object." 182 ::= { mteTrigger 2 } 184 mteTriggerLastFailedTrigger OBJECT-TYPE 185 SYNTAX triggerIndex 186 MAX-ACCESS read-only 187 STATUS current 188 DESCRIPTION 189 "The trigger that last failed an attempt to check for a 190 trigger condition." 191 ::= { mteTrigger 3 } 193 mteTriggerLastFailedReason OBJECT-TYPE 194 SYNTAX FailureReason 195 MAX-ACCESS read-only 196 STATUS current 197 DESCRIPTION 198 "The reason for the last failure of an attempt to check 199 for a trigger condition." 200 ::= { mteTrigger 4 } 202 mteTriggerLastFailedTargetTag OBJECT-TYPE 203 SYNTAX SnmpTagValue 204 MAX-ACCESS read-only 205 STATUS current 206 DESCRIPTION 207 "The target group of the last failed attempt to check a 208 trigger condition. The length 0 means this does not apply." 209 ::= { mteTrigger 5 } 211 mteTriggerLastFailedTargetName OBJECT-TYPE 212 SYNTAX SnmpAdminString 213 MAX-ACCESS read-only 214 STATUS current 215 DESCRIPTION 216 "The target name of the last failed attempt to check a 217 trigger condition. The length 0 means this does not apply" 218 ::= { mteTrigger 6 } 220 mteTriggerLastValueID OBJECT-TYPE 221 SYNTAX OBJECT IDENTIFIER 222 MAX-ACCESS read-only 223 STATUS current 224 DESCRIPTION 225 "The object identifier from mteTriggerValueID from the last 226 attempt to check a trigger condition. This must 227 be as full-qualified as possible, including filling in 228 wild-card information determined in processing." 229 ::= { mteTrigger 7 } 231 mteTriggerLastValue OBJECT-TYPE 232 SYNTAX Integer32 233 MAX-ACCESS notification-only 234 STATUS current 235 DESCRIPTION 236 "The value of the object at mteTriggerValueID when a 237 trigger fires." 238 ::= { mteTrigger 8 } 240 mteTriggerTargetName OBJECT-TYPE 241 SYNTAX SnmpAdminString 242 MAX-ACCESS notification-only 243 STATUS current 244 DESCRIPTION 245 "The target name for which the trigger fired or for which a 246 check was attempted." 247 ::= { mteTrigger 9 } 249 -- 250 -- Trigger Creation Table 251 -- 253 mteTriggerCreationTable OBJECT-TYPE 254 SYNTAX SEQUENCE OF MteTriggerCreationEntry 255 MAX-ACCESS not-accessible 256 STATUS current 257 DESCRIPTION 258 "A table of triggers for network management events." 259 ::= { mteTrigger 10 } 261 mteTriggerCreationEntry OBJECT-TYPE 262 SYNTAX MteTriggerCreationEntry 263 MAX-ACCESS not-accessible 264 STATUS current 265 DESCRIPTION 266 "Information about a single trigger. 268 To create an entry create the named entry in this 269 table and activate it with mteTriggerCreationStatus. Then use 270 mteTriggerIndex to populate mteTriggerTable. 272 Deleting an entry deletes the related entry in 273 mteTriggerTable." 274 INDEX { IMPLIED mteTriggerCreationName } 275 ::= { mteTriggerCreationTable 1 } 277 MteTriggerCreationEntry ::= SEQUENCE { 278 mteTriggerCreationName EntryName, 279 mteTriggerIndex EntryIndex, 280 mteTriggerCreationStatus RowStatus 281 } 283 mteTriggerCreationName OBJECT-TYPE 284 SYNTAX EntryName 285 MAX-ACCESS not-accessible 286 STATUS current 287 DESCRIPTION 288 "A locally-unique, administratively assigned name for the trigger." 289 ::= { mteTriggerCreationEntry 1 } 291 mteTriggerIndex OBJECT-TYPE 292 SYNTAX EntryIndex 293 MAX-ACCESS read-only 294 STATUS current 295 DESCRIPTION 296 "The numeric identification of the trigger." 297 ::= { mteTriggerCreationEntry 2 } 299 mteTriggerCreationStatus OBJECT-TYPE 300 SYNTAX RowStatus 301 MAX-ACCESS read-create 302 STATUS current 303 DESCRIPTION 304 "The control that allows creation/deletion of entries. 305 Once made active an entry may not be modified except to 306 delete it or change its name via mteTriggerName." 307 ::= { mteTriggerCreationEntry 3 } 309 -- 310 -- Trigger Table 311 -- 313 mteTriggerTable OBJECT-TYPE 314 SYNTAX SEQUENCE OF MteTriggerEntry 315 MAX-ACCESS not-accessible 316 STATUS current 317 DESCRIPTION 318 "A table of management event trigger information." 319 ::= { mteTrigger 11 } 321 mteTriggerEntry OBJECT-TYPE 322 SYNTAX MteTriggerEntry 323 MAX-ACCESS not-accessible 324 STATUS current 325 DESCRIPTION 326 "Information about a single management event trigger. 328 An entry appears in this table when an mteTriggerCreationEntry 329 is activated. Deleting the matching mteTriggerCreationEntry 330 deletes this entry." 331 INDEX { mteTriggerIndex } 332 ::= { mteTriggerteble 1 } 334 MteTriggerEntry ::= SEQUENCE { 335 mteTriggerName EntryName, 336 mteTriggerComment DisplayString, 337 mteTriggerTest INTEGER, 338 mteTriggerValueID Integer32, 339 mteTriggerValueIDWildcard TruthValue, 340 mteTriggerFrequency Integer32, 341 mteTriggerTargetTag SnmpTagValue, 342 mteTriggerRisingThreshold Integer32, 343 mteTriggerFallingThreshold Integer32, 344 mteTriggerEvent EntryIndexOrZero, 345 mteTriggerRisingEvent EntryIndexOrZero, 346 mteTriggerFallingEvent EntryIndexOrZero 347 } 349 mteTriggerName OBJECT-TYPE 350 SYNTAX EntryName 351 MAX-ACCESS read-write 352 STATUS current 353 DESCRIPTION 354 "The unique name of the target trigger, identical to 355 mteTriggerCreationName. 357 Use this object to change the trigger's mteTriggerCreationName 358 without changing its mteTriggerIndex." 359 ::= { mteTriggerEntry 1 } 361 mteTriggerComment OBJECT-TYPE 362 SYNTAX DisplayString 363 MAX-ACCESS read-write 364 STATUS current 365 DESCRIPTION 366 "A description of the trigger's function and use." 367 DEFVAL { ''H } 368 ::= { mteTriggerEntry 2 } 370 mteTriggerTest OBJECT-TYPE 371 SYNTAX INTEGER { boolean(1), threshold(2) } 372 MAX-ACCESS read-write 373 STATUS current 374 DESCRIPTION 375 "The type of trigger test to perform. For all tests, 376 mteTriggerValue must evaluate to an integer. 378 For 'boolean', a value of 0 is false. A non-zero value 379 is true and fires the trigger. 381 For 'threshold' it works like RMON and the text needs to 382 be copied into this MIB." 383 DEFVAL { boolean } 384 ::= { mteTriggerEntry 3 } 386 mteTriggerValueID OBJECT-TYPE 387 SYNTAX OBJECT IDENTIFIER 388 MAX-ACCESS read-write 389 STATUS current 390 DESCRIPTION 391 "The object identifier of the MIB object to check to see 392 if the trigger should fire. 394 This may be wildcarded by truncating all or part of the 395 instance portion, in which case the condition is obtained 396 as if with a GetNext function, checking multiple values 397 if they exist. If such wildcarding is applied, 398 mteTriggerIDWildcard must be 'true' and if not it must 399 be 'false'." 400 DEFVAL { 0 0 } 401 ::= { mteTriggerEntry 4 } 403 mteTriggerValueIDWildcard OBJECT-TYPE 404 SYNTAX TruthValue 405 MAX-ACCESS read-write 406 STATUS current 407 DESCRIPTION 408 "Control over which mteTriggerValueID is to be treated as 409 fully-specified or wildcarded, with 'true' indicating wildcard. 410 DEFVAL { false } 411 ::= { mteTriggerEntry 5 } 413 mteTriggerFrequency OBJECT-TYPE 414 SYNTAX Integer32 (0..65535) 415 UNITS "seconds" 416 MAX-ACCESS read-write 417 STATUS current 418 DESCRIPTION 419 "The number of seconds to wait between trigger condition 420 checks. To encourage consistency in sampling, the 421 interval is measured from the beginning of one check to 422 the beginning of the next and the timer is restarted immediately 423 when it expires, not when the check completes. 425 If the next check begins before the previous one completed the 426 system may either attempt to make the check or treat this as an 427 error condition. 429 A frequency of 0 indicates instantaneous recognition of the 430 condition. This is not possible in many cases, but such may 431 be supported in cases where it makes sense and the system is 432 able to do so." 433 DEFVAL { 600 } 434 ::= { mteTriggerEntry 6 } 436 mteTriggerTargetTag OBJECT-TYPE 437 SYNTAX SnmpTagValue 438 MAX-ACCESS read-write 439 STATUS current 440 DESCRIPTION 441 "The tag for the target(s) from which to obtain the condition 442 for a trigger check. 444 A length of 0 indicates the local system." 445 DEFVAL { ''H } 446 ::= { mteTriggerEntry 7 } 448 mteTriggerRisingThreshold OBJECT-TYPE 449 SYNTAX Integer32 450 MAX-ACCESS read-write 451 STATUS current 452 DESCRIPTION 453 "A threshold value to check against if mteTriggerType is 454 'threshold'. In this case if the value of the object at 455 mteTriggerValueID is greater than or equal to this threshold 456 and the value at the last sampling interval was less than 457 this threshold, one mteTriggerRisingEvent is triggered. 459 If mteTriggerType is not 'threshold', this object is not 460 instantiated." 461 DEFVAL { 0 } 462 ::= { mteTriggerEntry 8 } 464 mteTriggerFallingThreshold OBJECT-TYPE 465 SYNTAX Integer32 466 MAX-ACCESS read-write 467 STATUS current 468 DESCRIPTION 469 "A threshold value to check against if mteTriggerType is 470 'threshold'. In this case if the value of the object at 471 mteTriggerValueID is less than or equal to this threshold 472 and the value at the last sampling interval was greater than 473 this threshold, one mteTriggerFallingEvent is triggered. 475 If mteTriggerType is not 'threshold', this object is not 476 instantiated." 477 DEFVAL { 0 } 478 ::= { mteTriggerEntry 9 } 480 mteTriggerEvent OBJECT-TYPE 481 SYNTAX EntryIndexOrZero 482 MAX-ACCESS read-write 483 STATUS current 484 DESCRIPTION 485 "The event to invoke when mteTriggerType is 'boolean' and 486 this trigger fires. A value of 0 indicates no event. 488 If mteTriggerType is not 'boolean', this object is not 489 instantiated." 490 DEFVAL { 0 } 491 ::= { mteTriggerEntry 10 } 493 mteTriggerRisingEvent OBJECT-TYPE 494 SYNTAX EntryIndexOrZero 495 MAX-ACCESS read-write 496 STATUS current 497 DESCRIPTION 498 "The event to invoke when mteTriggerType is 'threshold' and 499 this trigger fires based on mteTriggerRisingThreshold. A 500 value of 0 indicates no event. 502 If mteTriggerType is not 'threshold', this object is not 503 instantiated." 504 DEFVAL { 0 } 505 ::= { mteTriggerEntry 11 } 507 mteTriggerFallingEvent OBJECT-TYPE 508 SYNTAX EntryIndexOrZero 509 MAX-ACCESS read-write 510 STATUS current 511 DESCRIPTION 512 "The event to invoke when mteTriggerType is 'threshold' and 513 this trigger fires based on mteTriggerFallingThreshold. A 514 value of 0 indicates no event. 516 If mteTriggerType is not 'threshold', this object is not 517 instantiated." 518 DEFVAL { 0 } 519 ::= { mteTriggerEntry 12 } 521 -- 522 -- Event Section 523 -- 525 mteEventLastChange OBJECT-TYPE 526 SYNTAX TimeStamp 527 MAX-ACCESS read-only 528 STATUS current 529 DESCRIPTION 530 "The value of sysUpTime at the most recent addition or 531 deletion of an event or an event name change. 533 A management application can monitor this object to 534 know that the event list has changed in a way 535 requiring reloading of the event names." 536 ::= { mteEvent 1 } 538 mteEventFailures OBJECT-TYPE 539 SYNTAX Counter32 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION 543 "The number of times an attempt to invoke an event 544 has failed. This counts individually for each 545 attempt in a group of targets or each attempt for a 546 wildcarded trigger object." 547 ::= { mteEvent 2 } 549 mteEventLastFailedEvent OBJECT-TYPE 550 SYNTAX eventIndex 551 MAX-ACCESS read-only 552 STATUS current 553 DESCRIPTION 554 "The event that last failed an attempted invocation." 555 ::= { mteEvent 3 } 557 mteEventLastFailedReason OBJECT-TYPE 558 SYNTAX FailureReason 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "The reason for the last failure of an attempted event 563 invocation." 564 ::= { mteEvent 4 } 566 mteEventLastFailedTargetTag OBJECT-TYPE 567 SYNTAX SnmpTagValue 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "The target tag of the last failed attempt to invoke an 572 event. The length 0 means this does not apply." 573 ::= { mteEvent 5 } 575 mteEventLastFailedTargetName OBJECT-TYPE 576 SYNTAX SnmpAdminString 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "The target name of the last failed attempt to invoke an 581 event. The length 0 means this does not apply" 582 ::= { mteEvent 6 } 583 9 584 -- 585 -- Event Creation Table 586 -- 588 mteEventCreationTable OBJECT-TYPE 589 SYNTAX SEQUENCE OF MteEventCreationEntry 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "A table of events for network management action." 594 ::= { mteEvent 7 } 596 mteEventCreationEntry OBJECT-TYPE 597 SYNTAX MteEventCreationEntry 598 MAX-ACCESS not-accessible 599 STATUS current 600 DESCRIPTION 601 "Information about a single event. 603 To create an entry create the named entry in this 604 table and activate it with mteEventCreationStatus. Then use 605 mteEventIndex to populate mteEventTable. 607 Deleting an entry deletes the related entry in 608 mteEventTable." 609 INDEX { IMPLIED mteEventCreationName } 610 ::= { mteEventCreationTable 1 } 612 MteEventCreationEntry ::= SEQUENCE { 613 mteEventCreationName EntryName, 614 mteEventIndex EntryIndex, 615 mteEventCreationStatus RowStatus 616 } 618 mteEventCreationName OBJECT-TYPE 619 SYNTAX EntryName 620 MAX-ACCESS not-accessible 621 STATUS current 622 DESCRIPTION 623 "A locally-unique, administratively assigned name for the event." 624 ::= { mteEventCreationEntry 1 } 626 mteEventIndex OBJECT-TYPE 627 SYNTAX EntryIndex 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "The numeric identification of the event." 632 ::= { mteEventCreationEntry 2 } 634 mteEventCreationStatus OBJECT-TYPE 635 SYNTAX RowStatus 636 MAX-ACCESS read-create 637 STATUS current 638 DESCRIPTION 639 "The control that allows creation/deletion of entries. 640 Once made active an entry may not be modified except to 641 delete it or change its name via mteEventName." 642 ::= { mteEventCreationEntry 3 } 644 -- 645 -- Event Table 646 -- 648 mteEventTable OBJECT-TYPE 649 SYNTAX SEQUENCE OF MteEventEntry 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "A table of management event action information." 654 ::= { mteEvent 3 } 656 mteEventEntry OBJECT-TYPE 657 SYNTAX MteEventEntry 658 MAX-ACCESS not-accessible 659 STATUS current 660 DESCRIPTION 661 "Information about a single management event's actions. 663 An entry appears in this table when an mteEventCreationEntry 664 is activated. Deleting the matching mteEventCreationEntry 665 deletes this entry." 666 INDEX { mteEventIndex } 667 ::= { mteEventTable 1 } 669 MteEventEntry ::= SEQUENCE { 670 mteEventName EntryName, 671 mteEventComment DisplayString, 672 mteEventActions BITS, 673 mteEventNotification OBJECT IDENTIFIER, 674 mteEventSetObject OBJECT IDENTIFIER, 675 mteEventSetValue Integer32, 676 mteEventSetTargetTag SnmpTagValue 677 } 679 mteEventName OBJECT-TYPE 680 SYNTAX EntryName 681 MAX-ACCESS read-write 682 STATUS current 683 DESCRIPTION 684 "The unique name of the event, identical to 685 mteEventCreationName. 687 Use this object to change the event's mteEventCreationName 688 without changing its mteEventIndex." 689 ::= { mteEventEntry 1 } 691 mteEventComment OBJECT-TYPE 692 SYNTAX DisplayString 693 MAX-ACCESS read-write 694 STATUS current 695 DESCRIPTION 696 "A description of the event's function and use." 697 DEFVAL { ''H } 698 ::= { mteEventEntry 2 } 700 mteEventActions OBJECT-TYPE 701 SYNTAX BITS { notification, set } 702 MAX-ACCESS read-write 703 STATUS current 704 DESCRIPTION 705 "The actions to peform when this event occurs. 707 For 'notification', Traps and/or Informs are sent according 708 to the configuration in the SNMP-NOTIFICATION-MIB. 710 For 'set', an SNMP Set operation is performed according to 711 control values in this entry." 712 DEFVAL { 0 } 713 ::= { mteEventEntry 3 } 715 mteEventNotification OBJECT-TYPE 716 SYNTAX OBJECT IDENTIFIER 717 MAX-ACCESS read-write 718 STATUS current 719 DESCRIPTION 720 "The object identifier from the NOTIFICATION-TYPE for the 721 notification to use if metEventActions has 'notification' set. 723 If none of the above bits are set, this object is not 724 instantiated." 725 DEFVAL { 0 0 } 726 ::= { mteEventEntry 4 } 728 mteEventSetObject OBJECT-TYPE 729 SYNTAX OBJECT IDENTIFIER 730 MAX-ACCESS read-write 731 STATUS current 732 DESCRIPTION 733 "The object identifier from the MIB object to set if 734 metEventActions has 'set' set. 736 If 'set' is not set, this object is not instantiated." 737 DEFVAL { 0 0 } 738 ::= { mteEventEntry 5 } 740 mteEventSetValue OBJECT-TYPE 741 SYNTAX Integer32 742 MAX-ACCESS read-write 743 STATUS current 744 DESCRIPTION 745 "The value to which to set the object at mteEventSetObect." 746 DEFVAL { 0 } 747 ::= { mteEventEntry 6 } 749 mteEventSetTargetTag OBJECT-TYPE 750 SYNTAX SnmpTagValue 751 MAX-ACCESS read-write 752 STATUS current 753 DESCRIPTION 754 "The tag for the target(s) at which to set the object at 755 mteEventSetObject to mteEventSetValue. A length of 0 756 indicates the local system." 757 DEFVAL { ''H } 758 ::= { mteEventEntry 7 } 760 -- 761 -- Notifications 762 -- 763 eventMIBNotificationPrefix OBJECT IDENTIFIER ::= { eventMIB 2 } 764 eventMIBNotifications OBJECT IDENTIFIER ::= { eventMIBNotificationPrefix 0 } 766 mteTriggerSenseAlarm NOTIFICATION-TYPE 767 OBJECTS { mteTriggerName, 768 mteTriggerTargetName, 769 mteTriggerLastValueID, 770 mteTriggerLastValue } 771 STATUS current 772 DESCRIPTION 773 "Notification that the trigger indicated by the object 774 instances has fired, for triggers with mteTriggerType 775 'boolean'." 776 ::= { eventMIBNotifications 1 } 778 mteTriggerRisingAlarm NOTIFICATION-TYPE 779 OBJECTS { mteTriggerName, 780 mteTriggerTargetName, 781 mteTriggerLastValueID, 782 mteTriggerLastValue } 783 STATUS current 784 DESCRIPTION 785 "Notification that the rising threshold was met for triggers 786 with mteTriggerType 'threshold'." 787 ::= { eventMIBNotifications 2 } 789 mteTriggerFallingAlarm NOTIFICATION-TYPE 790 OBJECTS { mteTriggerName, 791 mteTriggerTargetName, 792 mteTriggerLastValueID, 793 mteTriggerLastValue } 794 STATUS current 795 DESCRIPTION 796 "Notification that the falling threshold was met for triggers 797 with mteTriggerType 'threshold'." 798 ::= { eventMIBNotifications 3 } 800 mteTriggerFailureAlarm NOTIFICATION-TYPE 801 OBJECTS { mteTriggerName, 802 mteTriggerLastFailedReason, 803 mteTriggerLastFailedTargetTag, 804 mteTriggerLastFailedTargetName, 805 mteTriggerLastFailedValueID } 806 STATUS current 807 DESCRIPTION 808 "Notification that an attempt to check a trigger has failed. 810 The network manager must enable this notification only with 811 a certain fear and trembling, as it can easily crowd out more 812 important information. It should be used only to help diagnose 813 a problem that has appeared in the error counters and can not 814 be found otherwise." 815 ::= { eventMIBNotifications 4 } 817 mteEventFailureAlarm NOTIFICATION-TYPE 818 OBJECTS { mteTriggerName, 819 mteTriggerTargetName, 820 mteTriggerLastValueID, 821 mteTriggerLastValue, 822 mteEventLastFailedReason, 823 mteEventLastFailedTargetTag, 824 mteEventLastFailedTargetName } 825 STATUS current 826 DESCRIPTION 827 "Notification that an attempt to check a trigger has failed. 829 The network manager must enable this notification only with 830 a certain fear and trembling, as it can easily crowd out more 831 important information. It should be used only to help diagnose 832 a problem that has appeared in the error counters and can not 833 be found otherwise." 834 ::= { eventMIBNotifications 5 } 836 -- The compliance statements have yet to be written. The intent is 837 -- that all objects are required except where otherwise mentioned above 838 -- and that a self-managing system need not support groups, remote checking, 839 -- or wildcarding. 841 END 843 9 844 6. Acknowledgements 846 This MIB contains considerable contributions from the RMON MIB, the 847 Distributed Management Design Team (Andy Bierman, Maria Greene, Bob 848 Stewart, and Steve Waldbusser), and colleagues at Cisco. 850 9 851 7. References 853 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 854 S. Waldbusser, "Structure of Management Information for version 2 855 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 856 January 1996. 858 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 859 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 860 RFC 1213, March 1991. 862 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 863 Management Protocol", RFC 1157, May 1990. 865 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 866 S. Waldbusser, "Protocol Operations for version 2 of the Simple 867 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 869 9 870 8. Security Considerations 871 Security issues are not discussed in this memo. 873 9. Author's Address 875 Bob Stewart 876 Cisco Systems, Inc. 877 170 West Tasman Drive 878 San Jose, CA 95134-1706 880 Phone: 408-526-4527 881 Email: bstewart@cisco.com 883 9 884 Table of Contents 885 1 Abstract ........................................................ 2 886 2 The SNMP Network Management Framework ........................... 3 887 2.1 Object Definitions ............................................ 3 888 3 Overview ........................................................ 4 889 4 Known Problems .................................................. 4 890 5 Definitions ..................................................... 5 891 6 Acknowledgements ................................................ 22 892 7 References ...................................................... 23 893 8 Security Considerations ......................................... 24 894 9 Author's Address ................................................ 24 896 9