idnits 2.17.1 draft-ietf-disman-event-mib-07.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 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 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == 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 54 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. ** There are 9 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 315 has weird spacing: '...achable can't...' == Line 2150 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 (25 June 1999) is 9066 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) == Unused Reference: 'RFC1903' is defined on line 2100, but no explicit reference was found in the text == Unused Reference: 'RFCEventMIB' is defined on line 2105, but no explicit reference was found in the text == Unused Reference: 'RFCNotificationLogMIB' is defined on line 2119, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 1903 (Obsoleted by RFC 2579) -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCEventMIB' ** Obsolete normative reference: RFC 1757 (Obsoleted by RFC 2819) ** Downref: Normative reference to an Historic RFC: RFC 1451 -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCExpressionMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'RFCNotificationLogMIB' Summary: 22 errors (**), 0 flaws (~~), 9 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Event MIB 3 25 June 1999 5 draft-ietf-disman-event-mib-07.txt 7 Bob Stewart 8 Cisco Systems, Inc. 9 bstewart@cisco.com 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with all 14 provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering Task 17 Force (IETF), its areas, and its working groups. Note that other groups 18 may also distribute working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet- Drafts as reference material 23 or to cite them other than as ``work in progress.'' 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 Distribution of this document is unlimited. Please send comments to the 32 Distributed Management Working Group, . 34 Copyright Notice 36 Copyright (C) The Internet Society (1999). All Rights Reserved. 38 1. Abstract 40 This memo defines an experimental portion of the Management Information 41 Base (MIB) for use with network management protocols in the Internet 42 community. In particular, it describes managed objects used for 43 managing monitoring of MIB objects and taking action through events. 45 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 46 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 47 document are to be interpreted as described in RFC 2119. 49 2. The SNMP Management Framework 51 The SNMP Management Framework presently consists of five major 52 components: 54 o An overall architecture, described in RFC 2571 [RFC2571]. 56 o Mechanisms for describing and naming objects and events for the 57 purpose of management. The first version of this Structure of 58 Management Information (SMI) is called SMIv1 and described in 59 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 60 1215 [RFC1215]. The second version, called SMIv2, is described 61 in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 62 [RFC2580]. 64 o Message protocols for transferring management information. The 65 first version of the SNMP message protocol is called SNMPv1 and 66 described in STD 15, RFC 1157 [RFC1157]. A second version of the 67 SNMP message protocol, which is not an Internet standards track 68 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 69 and RFC 1906 [RFC1906]. The third version of the message 70 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 71 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 73 o Protocol operations for accessing management information. The 74 first set of protocol operations and associated PDU formats is 75 described in STD 15, RFC 1157 [RFC1157]. A second set of 76 protocol operations and associated PDU formats is described in 77 RFC 1905 [RFC1905]. 79 o A set of fundamental applications described in RFC 2573 80 [RFC2573] and the view-based access control mechanism described 81 in RFC 2575 [RFC2575]. 83 A more detailed introduction to the current SNMP Management Framework 84 can be found in RFC 2570 [RFC2570]. 86 Managed objects are accessed via a virtual information store, termed 87 the Management Information Base or MIB. Objects in the MIB are 88 defined using the mechanisms defined in the SMI. 90 This memo specifies a MIB module that is compliant to the SMIv2. A 91 MIB conforming to the SMIv1 can be produced through the appropriate 92 translations. The resulting translated MIB must be semantically 93 equivalent, except where objects or events are omitted because no 94 translation is possible (use of Counter64). Some machine readable 95 information in SMIv2 will be converted into textual descriptions in 96 SMIv1 during the translation process. However, this loss of machine 97 readable information is not considered to change the semantics of the 98 MIB. 100 3. Overview 102 With network sizes well beyond the ability of people to management them 103 directly, automated, distributed management is vital. An important 104 aspect of such management is the ability of a system to monitor itself 105 or for some other system to monitor it. 107 The Event MIB provides the ability to monitor MIB objects on the local 108 system or on a remote system and take simple action when a trigger 109 condition is met. 111 The MIB is intended to suit either a relatively powerful manager or 112 mid-level manager, as well as a somewhat more limited self-managing 113 system. 115 4. Relationship to Other MIBs 117 The Event MIB is based on extensive experience with the RMON MIB 118 [RFC1757] and its alarm and event groups and is intended as a 119 replacement for those groups. The Event MIB calls "triggers" what the 120 RMON MIB called "alarms," but the concepts are the same. Event MIB 121 triggers maintain the RMON handling of thresholds and add the concept of 122 booleans. Event MIB events maintain the RMON concept of sending an SNMP 123 notification in response to a trigger and add the concept of setting a 124 MIB object. 126 The Event MIB is the successor and update to SNMPv2's Manager-to-Manager 127 MIB [RFC1451] which was declared Historic pending this work. 129 The Event MIB depends on the services of the SNMPv3 Management Target 130 and Notification MIBs [RFC2573]. 132 The Event MIB is nicely complemented by the Distributed Management 133 Expression MIB [RFCExpressionMIB], which is the expected source of 134 boolean objects to monitor. Note that there is considerable overlap 135 between the wildcard and delta sample capabilities of the Event and 136 Expression MIBs. A carefully-planned implementation might well use 137 common code to provide the overlapping functions. 139 5. MIB Sections 141 The MIB has four sections: triggers, objects, events, and notifications. 142 Triggers define the conditions that lead to events. Events may cause 143 notifications. 145 The trigger table lists what objects are to be monitored and how and 146 relates each trigger to an event. It has supplementary, companion 147 tables for additional objects that depend on the type of test done for 148 the trigger. 150 The objects table lists objects that can be added to notifications based 151 on the trigger, the trigger test type, or the event that resulted in the 152 notification. 154 The event table defines what happens when an event is triggered, sending 155 a notification, setting a MIB object or both. It has supplementary, 156 companion tables for additional objects that depend on the action taken. 157 82 The notification section defines a set of generic notifications to go 158 with the events and for Event MIB error handling, and it defines a set 159 of objects to put in those notifications. 161 6. Operation 163 The Event MIB is instrumentation for a distributed management 164 application that monitors MIB objects. In its simplest form this 165 application monitors individual, local MIB objects, just as an RMON 166 probe fulfills the functions implied by RMON's alarm and event 167 operation. Additionally the application can monitor remote objects and 168 wildcarded groups of objects. 170 Remote monitoring uses the tag service of the Management Target MIB to 171 select and access remote systems as an ordinary SNMP-based management 172 application. Local monitoring may be via a more intimate, local 173 interface which may, for example, bypass SNMP encoding but otherwise is 174 functionally identical to remote SNMP operation, including the 175 application of access control. A self-management only system may not 176 implement remote monitoring. 178 Wildcards indicate that the application should use a GetNext-type 179 operation to find the zero or more instances implied by a truncated 180 object identifier, just like an ordinary SNMP-based management 181 application. Each instance of a wildcard is treated as if it were a 182 separate entry, that is the instances of a wildcarded object are 183 independent of one another. For example, a wild-carded object may 184 trigger an event and result in the setting of another wildcarded object. 185 The instance that satisfied the trigger function is used to perform the 186 set function. All of this takes place independently of any additional 187 instances that may fill the wildcard. 189 Error handling is by notification, which at first thought violates the 190 principle that notifications may be lost or become a crippling burden, 191 but the intent is that such error notifications be enabled only for the 192 diagnosis of problems indicated by error counters and if the 193 notifications are being lost they be directed to the log as described in 194 the Notification Log MIB [rfcNotificationLogMIB]. Note that this does 195 not mean the Notification Log MIB is required, since in fact 196 notifications usually are not lost, but that the Notification Log MIB 197 can be helpful with this as well as other MIBs that include 198 notifications. 200 Although like most MIBs this one has no explicit controls for the 201 persistance of the values set in configuring events, a robust, polite 202 implementation would certainly not force its managing applications to 203 reconfigure it whenever it resets. 205 Again, as with most MIBs, it is implementation specific how a system 206 provides and manages such persistance. To speculate, one could imagine, 207 for example, that persistance depended on the context in which the 208 expression was configured, or perhaps system-specific characteristics of 209 the expression's owner. Or perhaps everything in a MIB such as this 210 one, which is clearly aimed at persistant configuration, is 211 automatically part of a system's other persistant configuration. 213 7. Security 215 Security of Event MIB entries depends on SNMPv3 access control for the 216 entire MIB or for subsets based on entry owner names. 218 Security of monitored objects for remote access depends on the 219 Management Target MIB. Security for local access can depend on the 220 Management Target MIB or on recording appropriate security credentials 221 of the creator of an entry and using those to access the local objects. 222 These security credentials are the parameters necessary as inputs to 223 isAccessAllowed from the Architecture for Describing SNMP Management 224 Frameworks. When accessing local objects without using a local target 225 tag, the system must (conceptually) use isAccessAllowed to ensure that 226 it does not violate security. 228 To facilitate the provisioning of access control by a security 229 administrator for this MIB itself using the View-Based Access Control 230 Model (VACM) defined in RFC 2275 [RFC2575] for tables in which multiple 231 users may need to independently create or modify entries, the initial 232 index is used as an "owner index". Such an initial index has a syntax of 233 SnmpAdminString, and can thus be trivially mapped to a securityName or 234 groupName as defined in VACM, in accordance with a security policy. 236 All entries in related tables belonging to a particular user will have 237 the same value for this initial index. For a given user's entries in a 238 particular table, the object identifiers for the information in these 239 entries will have the same subidentifiers (except for the "column" 240 subidentifier) up to the end of the encoded owner index. To configure 241 VACM to permit access to this portion of the table, one would create 242 vacmViewTreeFamilyTable entries with the value of 243 vacmViewTreeFamilySubtree including the owner index portion, and 244 vacmViewTreeFamilyMask "wildcarding" the column subidentifier. More 245 elaborate configurations are possible. 247 8. Definitions 249 DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN 251 IMPORTS 252 MODULE-IDENTITY, OBJECT-TYPE, 253 experimental, Integer32, Unsigned32, 254 NOTIFICATION-TYPE, Counter32, 255 Gauge32 FROM SNMPv2-SMI 256 TEXTUAL-CONVENTION, RowStatus, 257 TruthValue FROM SNMPv2-TC 258 MODULE-COMPLIANCE, OBJECT-GROUP, 259 NOTIFICATION-GROUP FROM SNMPv2-CONF 260 sysUpTime FROM SNMPv2-MIB 261 SnmpTagValue FROM SNMP-TARGET-MIB 262 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 264 dismanEventMIB MODULE-IDENTITY 265 LAST-UPDATED "9906241700Z" 266 ORGANIZATION "IETF Distributed Management Working Group" 267 CONTACT-INFO "Bob Stewart 268 Cisco Systems, Inc. 269 170 West Tasman Drive, 270 San Jose CA 95134-1706. 271 Phone: +1 408 526 4527 272 Email: bstewart@cisco.com" 273 DESCRIPTION 274 "The MIB module for defining event triggers and actions 275 for network management purposes." 276 ::= { experimental xx } 278 dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 } 280 mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 } 281 mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 } 282 mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 } 283 mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 } 285 -- For use as a default OID: 287 zeroDotZero OBJECT IDENTIFIER ::= { 0 0 } 289 -- 290 -- Textual Conventions 291 -- 293 FailureReason ::= TEXTUAL-CONVENTION 294 STATUS current 295 DESCRIPTION 296 "Reasons for failures in an attempt to perform a management 297 request. 299 The first group of errors, numbered less than 0, are related 300 to problems in sending the request. The existence of a 301 particular error code here does not imply that all 302 implementations are capable of sensing that error and 303 returning that code. 305 The second group, numbered greater than 0, are copied 306 directly from SNMP protocol operations and are intended to carry 307 exactly the meanings defined for the protocol as returned in 308 an SNMP response. 310 localResourceLack some local resource such as memory lacking 311 or mteResourceSampleInstanceMaximum 312 exceeded 313 badDestination unrecognized domain name or otherwise 314 invalid destination address 315 destinationUnreachable can't get to destination address 316 noResponse no response to SNMP request 317 badType the data syntax of a retrieved object 318 as not as expected 319 sampleOverrun another sample attempt occurred before 320 the previous one completed" 322 SYNTAX INTEGER { localResourceLack(-1), 323 badDestination(-2), 324 destinationUnreachable(-3), 325 noResponse(-4), 326 badType(-5), 327 sampleOverrun(-6), 329 noError(0), 331 tooBig(1), 332 noSuchName(2), 333 badValue(3), 334 readOnly(4), 335 genErr(5), 336 noAccess(6), 337 wrongType(7), 338 wrongLength(8), 339 wrongEncoding(9), 340 wrongValue(10), 341 noCreation(11), 342 inconsistentValue(12), 343 resourceUnavailable(13), 344 commitFailed(14), 345 undoFailed(15), 346 authorizationError(16), 347 notWritable(17), 348 inconsistentName(18) } 349 -- 350 -- Resource Control Section 351 -- 353 mteResourceSampleMinimum OBJECT-TYPE 354 SYNTAX Integer32 (1..600) 355 UNITS "seconds" 356 MAX-ACCESS read-write 357 STATUS current 358 DESCRIPTION 359 "The minimum mteTriggerFrequency this system will 360 accept. A system may use the larger values of this minimum to 361 lessen the impact of constant sampling. For larger 362 sampling intervals the system samples less often and 363 suffers less overhead. This object provides a way to enforce 364 such lower overhead for all triggers created after it is 365 set. 367 Unless explicitly resource limited, a system's value for 368 this object should be 1, allowing as small as a 1 second 369 interval for ongoing trigger sampling. 371 Changing this value will not invalidate an existing setting 372 of mteTriggerFrequency." 373 ::= { mteResource 1 } 375 mteResourceSampleInstanceMaximum OBJECT-TYPE 376 SYNTAX Unsigned32 377 UNITS "instances" 378 MAX-ACCESS read-write 379 STATUS current 380 DESCRIPTION 381 "The maximum number of instance entries this system will 382 support for sampling. 384 These are the entries that maintain state, one for each 385 instance of each sampled object as selected by 386 mteTriggerValueID. Note that wildcarded objects result 387 in multiple instances of this state. 389 A value of 0 indicates no preset limit, that is, the limit 390 is dynamic based on system operation and resources. 392 Unless explicitly resource limited, a system's value for 393 this object should be 0. 395 Changing this value will not eliminate or inhibit existing sample 396 state but could prevent allocation of additional state 397 information." 398 ::= { mteResource 2 } 400 mteResourceSampleInstances OBJECT-TYPE 401 SYNTAX Gauge32 402 UNITS "instances" 403 MAX-ACCESS read-only 404 STATUS current 405 DESCRIPTION 406 "The number of currently active instance entries as 407 defined for mteResourceSampleInstanceMaximum." 408 ::= { mteResource 3 } 410 mteResourceSampleInstancesHigh OBJECT-TYPE 411 SYNTAX Gauge32 412 UNITS "instances" 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "The highest value of mteResourceSampleInstances that has 417 occurred since initialization of the management system." 418 ::= { mteResource 4 } 420 mteResourceSampleInstanceLacks OBJECT-TYPE 421 SYNTAX Counter32 422 UNITS "instances" 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The number of times this system could not take a new sample 427 because that allocation would have exceeded the limit set by 428 mteResourceSampleInstanceMaximum." 429 ::= { mteResource 5 } 431 -- 432 -- Trigger Section 433 -- 435 -- Counters 437 mteTriggerFailures OBJECT-TYPE 438 SYNTAX Counter32 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "The number of times an attempt to check for a trigger 443 condition has failed. This counts individually for each 444 attempt in a group of targets or each attempt for a 445 wildcarded object." 446 ::= { mteTrigger 1 } 448 -- 449 -- Trigger Table 450 -- 452 mteTriggerTable OBJECT-TYPE 453 SYNTAX SEQUENCE OF MteTriggerEntry 454 MAX-ACCESS not-accessible 455 STATUS current 456 DESCRIPTION 457 "A table of management event trigger information." 458 ::= { mteTrigger 2 } 460 mteTriggerEntry OBJECT-TYPE 461 SYNTAX MteTriggerEntry 462 MAX-ACCESS not-accessible 463 STATUS current 464 DESCRIPTION 465 "Information about a single trigger. Applications create and 466 delete entries using mteTriggerEntryStatus." 467 INDEX { mteOwner, IMPLIED mteTriggerName } 468 ::= { mteTriggerTable 1 } 470 MteTriggerEntry ::= SEQUENCE { 471 mteOwner SnmpAdminString, 472 mteTriggerName SnmpAdminString, 473 mteTriggerComment SnmpAdminString, 474 mteTriggerTest BITS, 475 mteTriggerSampleType INTEGER, 476 mteTriggerValueID OBJECT IDENTIFIER, 477 mteTriggerValueIDWildcard TruthValue, 478 mteTriggerTargetTag SnmpTagValue, 479 mteTriggerContextName SnmpAdminString, 480 mteTriggerContextNameWildcard TruthValue, 481 mteTriggerFrequency Unsigned32, 482 mteTriggerObjectsOwner SnmpAdminString, 483 mteTriggerObjects SnmpAdminString, 484 mteTriggerEnabled TruthValue, 485 mteTriggerEntryStatus RowStatus 486 } 488 mteOwner OBJECT-TYPE 489 SYNTAX SnmpAdminString (SIZE(0..32)) 490 MAX-ACCESS not-accessible 491 STATUS current 492 DESCRIPTION 493 "The owner of this entry. The exact semantics of this 494 string are subject to the security policy defined by the 495 security administrator." 496 ::= { mteTriggerEntry 1 } 498 mteTriggerName OBJECT-TYPE 499 SYNTAX SnmpAdminString (SIZE (1..32)) 500 MAX-ACCESS not-accessible 501 STATUS current 502 DESCRIPTION 503 "A locally-unique, administratively assigned name for the 504 trigger within the scope of mteOwner." 505 ::= { mteTriggerEntry 2 } 507 mteTriggerComment OBJECT-TYPE 508 SYNTAX SnmpAdminString 509 MAX-ACCESS read-create 510 STATUS current 511 DESCRIPTION 512 "A description of the trigger's function and use." 513 DEFVAL { ''H } 514 ::= { mteTriggerEntry 3 } 516 mteTriggerTest OBJECT-TYPE 517 SYNTAX BITS { existence(0), boolean(1), threshold(2) } 518 MAX-ACCESS read-create 519 STATUS current 520 DESCRIPTION 521 "The type of trigger test to perform. For 'boolean' and 522 'threshold' tests, the object at mteTriggerValueID must 523 evaluate to an integer, that is, anything that ends up encoded 524 for transmission (that is, in BER, not ASN.1) as an integer. 526 For 'existence', the specific test is as selected by 527 mteTriggerExistenceTest. When an object appears or vanishes 528 the trigger fires. The trigger will not fire again until the 529 object has changed states. 531 For 'boolean', the specific test is as selected by 532 mteTriggerBooleanTest. If the test result is true the trigger 533 fires. The trigger will not fire again until the value has 534 become false and come back to true. 536 For 'threshold' the test works as described below for 537 mteTriggerThresholdStartup, mteTriggerThresholdRising, and 538 mteTriggerThresholdFalling. 540 Note that combining 'boolean' and 'threshold' tests on the 541 same object may be somewhat redundant." 542 DEFVAL { boolean } 543 ::= { mteTriggerEntry 4 } 545 mteTriggerSampleType OBJECT-TYPE 546 SYNTAX INTEGER { absoluteValue(1), deltaValue(2) } 547 MAX-ACCESS read-create 548 STATUS current 549 DESCRIPTION 550 "The type of sampling to perform. 552 An 'absoluteValue' sample requires only a single sample to be 553 meaningful, and is exactly the value of the object at 554 mteTriggerValueID at the sample time. 556 A 'deltaValue' requires two samples to be meaningful and is 557 thus not available for testing until the second and subsequent 558 samples after the object at mteTriggerValueID is first found 559 to exist. It is the difference between the two samples. For 560 unsigned values it is always positive, based on unsigned 561 arithmetic. For signed values it can be positive or negative. 563 For SNMP counters to be meaningful they must be sampled as a 564 'deltaValue'. 566 For 'deltaValue' mteTriggerDeltaTable contains further 567 parameters. 569 If only 'existence' is set in mteTriggerTest this object has 570 no meaning." 571 DEFVAL { absoluteValue } 572 ::= { mteTriggerEntry 5 } 574 mteTriggerValueID OBJECT-TYPE 575 SYNTAX OBJECT IDENTIFIER 576 MAX-ACCESS read-create 577 STATUS current 578 DESCRIPTION 579 "The object identifier of the MIB object to sample to see 580 if the trigger should fire. 582 This may be wildcarded by truncating all or part of the 583 instance portion, in which case the value is obtained 584 as if with a GetNext function, checking multiple values 585 if they exist. If such wildcarding is applied, 586 mteTriggerValueIDWildcard must be 'true' and if not it must 587 be 'false'. 589 Bad object identifiers or a mismatch between truncating the 590 identifier and the value of mteTriggerValueIDWildcard result 591 in operation as one would expect when providing the wrong 592 identifier to a Get or GetNext operation. The Get will fail 593 or get the wrong object. The GetNext will indeed get whatever 594 is next, proceeding until it runs past the initial part of the 595 identifier and perhaps many unintended objects for confusing 596 results. If the value syntax of those objects is not usable, 597 that results in a 'badType' error that terminates the scan. 599 Each instance that fills the wildcard is independent of any 600 additional instances, that is, wildcarded objects operate 601 as if there were a separate table entry for each instance 602 that fills the wildcard without having to actually predict 603 all possible instances ahead of time." 604 DEFVAL { zeroDotZero } 605 ::= { mteTriggerEntry 6 } 607 mteTriggerValueIDWildcard OBJECT-TYPE 608 SYNTAX TruthValue 609 MAX-ACCESS read-create 610 STATUS current 611 DESCRIPTION 612 "Control for whether mteTriggerValueID is to be treated as 613 fully-specified or wildcarded, with 'true' indicating wildcard." 614 DEFVAL { false } 615 ::= { mteTriggerEntry 7 } 617 mteTriggerTargetTag OBJECT-TYPE 618 SYNTAX SnmpTagValue 619 MAX-ACCESS read-create 620 STATUS current 621 DESCRIPTION 622 "The tag for the target(s) from which to obtain the condition 623 for a trigger check. 625 A length of 0 indicates the local system. In this case, 626 access to the objects indicated by mteTriggerValueID is under 627 the security credentials of the requester that set 628 mteTriggerEntryStatus to 'active'. Those credentials are the 629 input parameters for isAccessAllowed from the Architecture for 630 Describing SNMP Management Frameworks. 632 Otherwise access rights are checked according to the security 633 parameters resulting from the tag." 634 DEFVAL { ''H } 635 ::= { mteTriggerEntry 8 } 637 mteTriggerContextName OBJECT-TYPE 638 SYNTAX SnmpAdminString 639 MAX-ACCESS read-create 640 STATUS current 641 DESCRIPTION 642 "The management context from which to obtain mteTriggerValueID. 644 This may be wildcarded by leaving characters off the end. For 645 example use 'Repeater' to wildcard to 'Repeater1', 646 'Repeater2', 'Repeater-999.87b', and so on. To indicate such 647 wildcarding is intended, mteTriggerContextNameWildcard must 648 be 'true'. 650 Each instance that fills the wildcard is independent of any 651 additional instances, that is, wildcarded objects operate 652 as if there were a separate table entry for each instance 653 that fills the wildcard without having to actually predict 654 all possible instances ahead of time. 656 Operation of this feature assumes that the local system has a 657 list of available contexts against which to apply the 658 wildcard. If the objects are being read from the local 659 system, this is clearly the system's own list of contexts. 660 For a remote system a local version of such a list is not 661 defined by any current standard and may not be available, so 662 this function may not be supported." 663 DEFVAL { ''H } 664 ::= { mteTriggerEntry 9 } 666 mteTriggerContextNameWildcard OBJECT-TYPE 667 SYNTAX TruthValue 668 MAX-ACCESS read-create 669 STATUS current 670 DESCRIPTION 671 "Control for whether mteTriggerContextName is to be treated as 672 fully-specified or wildcarded, with 'true' indicating wildcard." 673 DEFVAL { false } 674 ::= { mteTriggerEntry 10 } 676 mteTriggerFrequency OBJECT-TYPE 677 SYNTAX Unsigned32 678 UNITS "seconds" 679 MAX-ACCESS read-create 680 STATUS current 681 DESCRIPTION 682 "The number of seconds to wait between trigger samples. To 683 encourage consistency in sampling, the interval is measured 684 from the beginning of one check to the beginning of the next 685 and the timer is restarted immediately when it expires, not 686 when the check completes. 688 If the next sample begins before the previous one completed the 689 system may either attempt to make the check or treat this as an 690 error condition with the error 'sampleOverrun'. 692 A frequency of 0 indicates instantaneous recognition of the 693 condition. This is not possible in many cases, but may 694 be supported in cases where it makes sense and the system is 695 able to do so. This feature allows the MIB to be used in 696 implementations where such interrupt-driven behavior is 697 possible and is not likely to be supported for all MIB objects 698 even then since such sampling generally has to be tightly 699 integrated into low-level code. 701 Systems that can support this should document those cases 702 where it can be used. In cases where it can not, setting this 703 object to 0 simply returns a bad value error." 704 DEFVAL { 600 } 705 ::= { mteTriggerEntry 11 } 707 mteTriggerObjectsOwner OBJECT-TYPE 708 SYNTAX SnmpAdminString (SIZE (0..32)) 709 MAX-ACCESS read-create 710 STATUS current 711 DESCRIPTION 712 "To go with mteTriggerObjects, the mteOwner of a group of 713 objects from mteObjectsTable." 714 DEFVAL { ''H } 715 ::= { mteTriggerEntry 12 } 717 mteTriggerObjects OBJECT-TYPE 718 SYNTAX SnmpAdminString (SIZE (0..32)) 719 MAX-ACCESS read-create 720 STATUS current 721 DESCRIPTION 722 "The mteObjectsName of a group of objects from 723 mteObjectsTable. These objects are to be added to any 724 Notification resulting from the firing of this trigger. 726 A list of objects may also be added based on the event or on 727 the value of mteTriggerTest. 729 A length of 0 indicates no additional objects." 730 DEFVAL { ''H } 731 ::= { mteTriggerEntry 13 } 733 mteTriggerEnabled OBJECT-TYPE 734 SYNTAX TruthValue 735 MAX-ACCESS read-create 736 STATUS current 737 DESCRIPTION 738 "A control to allow a trigger to be configured but not used. 739 When the value is 'false' the trigger is not sampled." 740 DEFVAL { false } 741 ::= { mteTriggerEntry 14 } 743 mteTriggerEntryStatus OBJECT-TYPE 744 SYNTAX RowStatus 745 MAX-ACCESS read-create 746 STATUS current 747 DESCRIPTION 748 "The control that allows creation and deletion of entries. 749 Once made active an entry may not be modified except to 750 delete it." 751 ::= { mteTriggerEntry 15 } 753 -- 754 -- Trigger Delta Table 755 -- 757 mteTriggerDeltaTable OBJECT-TYPE 758 SYNTAX SEQUENCE OF MteTriggerDeltaEntry 759 MAX-ACCESS not-accessible 760 STATUS current 761 DESCRIPTION 762 "A table of management event trigger information for delta 763 sampling." 764 ::= { mteTrigger 3 } 766 mteTriggerDeltaEntry OBJECT-TYPE 767 SYNTAX MteTriggerDeltaEntry 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "Information about a single trigger's delta sampling. Entries 772 automatically exist in this this table for each mteTriggerEntry 773 that has mteTriggerSampleType set to 'deltaValue'." 774 INDEX { mteOwner, IMPLIED mteTriggerName } 775 ::= { mteTriggerDeltaTable 1 } 777 MteTriggerDeltaEntry ::= SEQUENCE { 778 mteTriggerDeltaDiscontinuityID OBJECT IDENTIFIER, 779 mteTriggerDeltaDiscontinuityIDWildcard TruthValue, 780 mteTriggerDeltaDiscontinuityIDType INTEGER 781 } 783 sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 } 785 mteTriggerDeltaDiscontinuityID OBJECT-TYPE 786 SYNTAX OBJECT IDENTIFIER 787 MAX-ACCESS read-write 788 STATUS current 789 DESCRIPTION 790 "The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or 791 DateAndTime object that indicates a discontinuity in the value 792 at mteTriggerValueID. 794 The OID may be for a leaf object (e.g. sysUpTime.0) or may 795 be wildcarded to match mteTriggerValueID. 797 This object supports normal checking for a discontinuity in a 798 counter. Note that if this object does not point to sysUpTime 799 discontinuity checking must still check sysUpTime for an overall 800 discontinuity. 802 If the object identified is not accessible the sample attempt 803 is in error, with the error code as from an SNMP request. 805 Bad object identifiers or a mismatch between truncating the 806 identifier and the value of mteDeltaDiscontinuityIDWildcard 807 result in operation as one would expect when providing the 808 wrong identifier to a Get operation. The Get will fail or get 809 the wrong object. If the value syntax of those objects is not 810 usable, that results in an error that terminates the sample 811 with a 'badType' error code." 812 DEFVAL { sysUpTimeInstance } 813 ::= { mteTriggerDeltaEntry 1 } 815 mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE 816 SYNTAX TruthValue 817 MAX-ACCESS read-write 818 STATUS current 819 DESCRIPTION 820 "Control for whether mteTriggerDeltaDiscontinuityID is to be 821 treated as fully-specified or wildcarded, with 'true' 822 indicating wildcard." 823 DEFVAL { false } 824 ::= { mteTriggerDeltaEntry 2 } 826 mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE 827 SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) } 828 MAX-ACCESS read-write 829 STATUS current 830 DESCRIPTION 831 "The value 'timeTicks' indicates the 832 mteTriggerDeltaDiscontinuityID of this row is of syntax 833 TimeTicks. The value 'timeStamp' indicates syntax TimeStamp. 834 The value 'dateAndTime' indicates syntax DateAndTime." 835 DEFVAL { timeTicks } 836 ::= { mteTriggerDeltaEntry 3 } 838 -- 839 -- Trigger Existence Table 840 -- 842 mteTriggerExistenceTable OBJECT-TYPE 843 SYNTAX SEQUENCE OF MteTriggerExistenceEntry 844 MAX-ACCESS not-accessible 845 STATUS current 846 DESCRIPTION 847 "A table of management event trigger information for existence 848 triggers." 849 ::= { mteTrigger 4 } 851 mteTriggerExistenceEntry OBJECT-TYPE 852 SYNTAX MteTriggerExistenceEntry 853 MAX-ACCESS not-accessible 854 STATUS current 855 DESCRIPTION 856 "Information about a single existence trigger. Entries 857 automatically exist in this this table for each mteTriggerEntry 858 that has 'existence' set in mteTriggerTest." 859 INDEX { mteOwner, IMPLIED mteTriggerName } 860 ::= { mteTriggerExistenceTable 1 } 862 MteTriggerExistenceEntry ::= SEQUENCE { 863 mteTriggerExistenceTest INTEGER, 864 mteTriggerExistenceStartup TruthValue, 865 mteTriggerExistenceObjectsOwner SnmpAdminString, 866 mteTriggerExistenceObjects SnmpAdminString, 867 mteTriggerExistenceEventOwner SnmpAdminString, 868 mteTriggerExistenceEvent SnmpAdminString 869 } 871 mteTriggerExistenceTest OBJECT-TYPE 872 SYNTAX BITS { present(0), absent(1), changed(2) } 873 MAX-ACCESS read-write 874 STATUS current 875 DESCRIPTION 876 "The type of existence test to perform. The trigger fires 877 when the object at mteTriggerValueID is seen to go from 878 present to absent, from absent to present, or to have it's 879 value changed, depending on which tests are selected. 881 Once the trigger has fired for either presence or absence it 882 will not fire again for that state until the object has been 883 to the other state." 884 DEFVAL { { present, absent } } 885 ::= { mteTriggerExistenceEntry 1 } 887 mteTriggerExistenceStartup OBJECT-TYPE 888 SYNTAX BITS { present(0), absent(1), changed(2) } 889 MAX-ACCESS read-write 890 STATUS current 891 DESCRIPTION 892 "Control for whether an event may be triggered when this entry 893 is first set to 'active' and the test specified by 894 mteTriggerExistenceTest is true. Setting an option causes 895 that trigger to fire when its test is true." 896 DEFVAL { { present, absent } } 897 ::= { mteTriggerExistenceEntry 2 } 899 mteTriggerExistenceObjectsOwner OBJECT-TYPE 900 SYNTAX SnmpAdminString (SIZE (0..32)) 901 MAX-ACCESS read-write 902 STATUS current 903 DESCRIPTION 904 "To go with mteTriggerExistenceObjects, the mteOwner of a 905 group of objects from mteObjectsTable." 906 DEFVAL { ''H } 907 ::= { mteTriggerExistenceEntry 3 } 909 mteTriggerExistenceObjects OBJECT-TYPE 910 SYNTAX SnmpAdminString (SIZE (0..32)) 911 MAX-ACCESS read-write 912 STATUS current 913 DESCRIPTION 914 "The mteObjectsName of a group of objects from 915 mteObjectsTable. These objects are to be added to any 916 Notification resulting from the firing of this trigger for 917 this test. 919 A list of objects may also be added based on the overall 920 trigger, the event or other settings in mteTriggerTest. 922 A length of 0 indicates no additional objects." 923 DEFVAL { ''H } 924 ::= { mteTriggerExistenceEntry 4 } 926 mteTriggerExistenceEventOwner OBJECT-TYPE 927 SYNTAX SnmpAdminString (SIZE (0..32)) 928 MAX-ACCESS read-write 929 STATUS current 930 DESCRIPTION 931 "To go with mteTriggerExistenceEvent, the mteOwner of a group 932 of objects from mteObjectsTable." 933 DEFVAL { ''H } 934 ::= { mteTriggerExistenceEntry 5 } 936 mteTriggerExistenceEvent OBJECT-TYPE 937 SYNTAX SnmpAdminString (SIZE (0..32)) 938 MAX-ACCESS read-write 939 STATUS current 940 DESCRIPTION 941 "The mteEventName of the event to invoke when mteTriggerType is 942 'existence' and this trigger fires. A length of 0 indicates no 943 event." 944 DEFVAL { ''H } 945 ::= { mteTriggerExistenceEntry 6 } 947 -- 948 -- Trigger Boolean Table 949 -- 951 mteTriggerBooleanTable OBJECT-TYPE 952 SYNTAX SEQUENCE OF MteTriggerBooleanEntry 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "A table of management event trigger information for boolean 957 triggers." 958 ::= { mteTrigger 5 } 960 mteTriggerBooleanEntry OBJECT-TYPE 961 SYNTAX MteTriggerBooleanEntry 962 MAX-ACCESS not-accessible 963 STATUS current 964 DESCRIPTION 965 "Information about a single boolean trigger. Entries 966 automatically exist in this this table for each mteTriggerEntry 967 that has 'boolean' set in mteTriggerTest." 968 INDEX { mteOwner, IMPLIED mteTriggerName } 969 ::= { mteTriggerBooleanTable 1 } 971 MteTriggerBooleanEntry ::= SEQUENCE { 972 mteTriggerBooleanComparison INTEGER, 973 mteTriggerBooleanValue Integer32, 974 mteTriggerBooleanStartup TruthValue, 975 mteTriggerBooleanObjectsOwner SnmpAdminString, 976 mteTriggerBooleanObjects SnmpAdminString, 977 mteTriggerBooleanEventOwner SnmpAdminString, 978 mteTriggerBooleanEvent SnmpAdminString 979 } 981 mteTriggerBooleanComparison OBJECT-TYPE 982 SYNTAX INTEGER { unequal(1), equal(2), 983 less(3), lessOrEqual(4), 984 greater(5), greaterOrEqual(6) } 985 MAX-ACCESS read-write 986 STATUS current 987 DESCRIPTION 988 "The type of boolean comparison to perform. 990 The value at mteTriggerValueID is compared to 991 mteTriggerBooleanValue, so for example if 992 mteTriggerBooleanComparison is 'less' the result would be true 993 if the value at mteTriggerValueID is less than the value of 994 mteTriggerBooleanValue." 995 DEFVAL { unequal } 996 ::= { mteTriggerBooleanEntry 1 } 998 mteTriggerBooleanValue OBJECT-TYPE 999 SYNTAX Integer32 1000 MAX-ACCESS read-write 1001 STATUS current 1002 DESCRIPTION 1003 "The value to use for the test specified by 1004 mteTriggerBooleanTest." 1005 DEFVAL { 0 } 1006 ::= { mteTriggerBooleanEntry 2 } 1008 mteTriggerBooleanStartup OBJECT-TYPE 1009 SYNTAX TruthValue 1010 MAX-ACCESS read-write 1011 STATUS current 1012 DESCRIPTION 1013 "Control for whether an event may be triggered when this entry 1014 is first set to 'active' or a new instance of the object at 1015 mteTriggerValueID is found and the test specified by 1016 mteTriggerBooleanComparison is true. In that case an event is 1017 triggered if mteTriggerBooleanStartup is 'true'." 1018 DEFVAL { true } 1019 ::= { mteTriggerBooleanEntry 3 } 1021 mteTriggerBooleanObjectsOwner OBJECT-TYPE 1022 SYNTAX SnmpAdminString (SIZE (0..32)) 1023 MAX-ACCESS read-write 1024 STATUS current 1025 DESCRIPTION 1026 "To go with mteTriggerBooleanObjects, the mteOwner of a group 1027 of objects from mteObjectsTable." 1028 DEFVAL { ''H } 1029 ::= { mteTriggerBooleanEntry 4 } 1031 mteTriggerBooleanObjects OBJECT-TYPE 1032 SYNTAX SnmpAdminString (SIZE (0..32)) 1033 MAX-ACCESS read-write 1034 STATUS current 1035 DESCRIPTION 1036 "The mteObjectsName of a group of objects from 1037 mteObjectsTable. These objects are to be added to any 1038 Notification resulting from the firing of this trigger for 1039 this test. 1041 A list of objects may also be added based on the overall 1042 trigger, the event or other settings in mteTriggerTest. 1044 A length of 0 indicates no additional objects." 1045 DEFVAL { ''H } 1046 ::= { mteTriggerBooleanEntry 5 } 1048 mteTriggerBooleanEventOwner OBJECT-TYPE 1049 SYNTAX SnmpAdminString (SIZE (0..32)) 1050 MAX-ACCESS read-write 1051 STATUS current 1052 DESCRIPTION 1053 "To go with mteTriggerBooleanEvent, the mteOwner of an event 1054 entry from mteEventTable." 1055 DEFVAL { ''H } 1056 ::= { mteTriggerBooleanEntry 6 } 1058 mteTriggerBooleanEvent OBJECT-TYPE 1059 SYNTAX SnmpAdminString (SIZE (0..32)) 1060 MAX-ACCESS read-write 1061 STATUS current 1062 DESCRIPTION 1063 "The mteEventName of the event to invoke when mteTriggerType is 1064 'boolean' and this trigger fires. A length of 0 indicates no 1065 event." 1066 DEFVAL { ''H } 1067 ::= { mteTriggerBooleanEntry 7 } 1069 -- 1070 -- Trigger Threshold Table 1071 -- 1073 mteTriggerThresholdTable OBJECT-TYPE 1074 SYNTAX SEQUENCE OF MteTriggerThresholdEntry 1075 MAX-ACCESS not-accessible 1076 STATUS current 1077 DESCRIPTION 1078 "A table of management event trigger information for threshold 1079 triggers." 1080 ::= { mteTrigger 6 } 1082 mteTriggerThresholdEntry OBJECT-TYPE 1083 SYNTAX MteTriggerThresholdEntry 1084 MAX-ACCESS not-accessible 1085 STATUS current 1086 DESCRIPTION 1087 "Information about a single threshold trigger. Entries 1088 automatically exist in this table for each mteTriggerEntry 1089 that has 'threshold' set in mteTriggerTest." 1090 INDEX { mteOwner, IMPLIED mteTriggerName } 1091 ::= { mteTriggerThresholdTable 1 } 1093 MteTriggerThresholdEntry ::= SEQUENCE { 1094 mteTriggerThresholdValue Integer32, 1095 mteTriggerThresholdStartup INTEGER, 1096 mteTriggerThresholdRising Integer32, 1097 mteTriggerThresholdFalling Integer32, 1098 mteTriggerThresholdObjectsOwner SnmpAdminString, 1099 mteTriggerThresholdObjects SnmpAdminString, 1100 mteTriggerThresholdRisingEventOwner SnmpAdminString, 1101 mteTriggerThresholdRisingEvent SnmpAdminString, 1102 mteTriggerThresholdFallingEventOwner SnmpAdminString, 1103 mteTriggerThresholdFallingEvent SnmpAdminString 1104 } 1106 mteTriggerThresholdValue OBJECT-TYPE 1107 SYNTAX Integer32 1108 MAX-ACCESS read-write 1109 STATUS current 1110 DESCRIPTION 1111 "The value to use for the threshold test." 1112 DEFVAL { 0 } 1113 ::= { mteTriggerThresholdEntry 1 } 1115 mteTriggerThresholdStartup OBJECT-TYPE 1116 SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } 1117 MAX-ACCESS read-write 1118 STATUS current 1119 DESCRIPTION 1120 "The event that may be triggered when this entry is first 1121 set to 'active' and a new instance of the object at 1122 mteTriggerValueID is found. If the first sample after this 1123 instance becomes active is greater than or equal to 1124 mteTriggerThresholdRising and mteTriggerThresholdStartup is 1125 equal to 'rising' or 'risingOrFalling', then one 1126 mteTriggerThresholdRisingEvent is triggered for that instance. 1127 If the first sample after this entry becomes active is less than 1128 or equal to mteTriggerThresholdFalling and 1129 mteTriggerThresholdStartup is equal to 'falling' or 1130 'risingOrFalling', then one mteTriggerThresholdRisingEvent is 1131 triggered for that instance." 1132 DEFVAL { risingOrFalling } 1133 ::= { mteTriggerThresholdEntry 2 } 1135 mteTriggerThresholdRising OBJECT-TYPE 1136 SYNTAX Integer32 1137 MAX-ACCESS read-write 1138 STATUS current 1139 DESCRIPTION 1140 "A threshold value to check against if mteTriggerType is 1141 'threshold'. 1143 When the current sampled value is greater than or equal to 1144 this threshold, and the value at the last sampling interval 1145 was less than this threshold, one 1146 mteTriggerThresholdRisingEvent is triggered. That event is 1147 also triggered if the first sample afer this entry bcomes 1148 active is greater than or equal to this threshold and 1149 mteTriggerThresholdStartup is equal to 'rising' or 1150 'risingOrFalling'. 1152 After a rising event is generated, another such event is not 1153 triggered until the sampled value falls below this threshold and 1154 reaches mteTriggerThresholdFalling." 1155 DEFVAL { 0 } 1156 ::= { mteTriggerThresholdEntry 3 } 1158 mteTriggerThresholdFalling OBJECT-TYPE 1159 SYNTAX Integer32 1160 MAX-ACCESS read-write 1161 STATUS current 1162 DESCRIPTION 1163 "A threshold value to check against if mteTriggerType is 1164 'threshold'. 1166 When the current sampled value is less than or equal to this 1167 threshold, and the value at the last sampling interval was 1168 greater than this threshold, one 1169 mteTriggerThresholdFallingEvent is triggered. That event is 1170 also triggered if the first sample afer this entry bcomes 1171 active is less than or equal to this threshold and 1172 mteTriggerThresholdStartup is equal to 'falling' or 1173 'risingOrFalling'. 1175 After a falling event is generated, another such event is not 1176 triggered until the sampled value rises above this threshold and 1177 reaches mteTriggerThresholdRising." 1178 DEFVAL { 0 } 1179 ::= { mteTriggerThresholdEntry 4 } 1181 mteTriggerThresholdObjectsOwner OBJECT-TYPE 1182 SYNTAX SnmpAdminString (SIZE (0..32)) 1183 MAX-ACCESS read-write 1184 STATUS current 1185 DESCRIPTION 1186 "To go with mteTriggerThresholdObjects, the mteOwner of a group 1187 of objects from mteObjectsTable." 1189 DEFVAL { ''H } 1190 ::= { mteTriggerThresholdEntry 5 } 1192 mteTriggerThresholdObjects OBJECT-TYPE 1193 SYNTAX SnmpAdminString (SIZE (0..32)) 1194 MAX-ACCESS read-write 1195 STATUS current 1196 DESCRIPTION 1197 "The mteObjectsName of a group of objects from 1198 mteObjectsTable. These objects are to be added to any 1199 Notification resulting from the firing of this trigger for 1200 this test. 1202 A list of objects may also be added based on the overall 1203 trigger, the event or other settings in mteTriggerTest. 1205 A length of 0 indicates no additional objects." 1206 DEFVAL { ''H } 1207 ::= { mteTriggerThresholdEntry 6 } 1209 mteTriggerThresholdRisingEventOwner OBJECT-TYPE 1210 SYNTAX SnmpAdminString (SIZE (0..32)) 1211 MAX-ACCESS read-write 1212 STATUS current 1213 DESCRIPTION 1214 "To go with mteTriggerThresholdRisingEvent, the mteOwner of an 1215 event entry from mteEventTable." 1216 DEFVAL { ''H } 1217 ::= { mteTriggerThresholdEntry 7 } 1219 mteTriggerThresholdRisingEvent OBJECT-TYPE 1220 SYNTAX SnmpAdminString (SIZE (0..32)) 1221 MAX-ACCESS read-write 1222 STATUS current 1223 DESCRIPTION 1224 "The mteEventName of the event to invoke when mteTriggerType is 1225 'threshold' and this trigger fires based on 1226 mteTriggerThresholdRising. A length of 0 indicates no event." 1227 DEFVAL { ''H } 1228 ::= { mteTriggerThresholdEntry 8 } 1230 mteTriggerThresholdFallingEventOwner OBJECT-TYPE 1231 SYNTAX SnmpAdminString (SIZE (0..32)) 1232 MAX-ACCESS read-write 1233 STATUS current 1234 DESCRIPTION 1235 "To go with mteTriggerThresholdFallingEvent, the mteOwner of an 1236 event entry from mteEventTable." 1237 DEFVAL { ''H } 1238 ::= { mteTriggerThresholdEntry 9 } 1240 mteTriggerThresholdFallingEvent OBJECT-TYPE 1241 SYNTAX SnmpAdminString (SIZE (0..32)) 1242 MAX-ACCESS read-write 1243 STATUS current 1244 DESCRIPTION 1245 "The mteEventName of the event to invoke when mteTriggerType is 1246 'threshold' and this trigger fires based on 1247 mteTriggerThresholdFalling. A length of 0 indicates no event." 1248 DEFVAL { ''H } 1249 ::= { mteTriggerThresholdEntry 10 } 1251 -- 1252 -- Objects Table 1253 -- 1255 mteObjectsTable OBJECT-TYPE 1256 SYNTAX SEQUENCE OF MteObjectsEntry 1257 MAX-ACCESS not-accessible 1258 STATUS current 1259 DESCRIPTION 1260 "A table of objects that can be added to notifications based 1261 on the trigger, trigger test, or event, as pointed to by 1262 entries in those tables." 1263 ::= { mteObjects 1 } 1265 mteObjectsEntry OBJECT-TYPE 1266 SYNTAX MteObjectsEntry 1267 MAX-ACCESS not-accessible 1268 STATUS current 1269 DESCRIPTION 1270 "A group of objects. Applications create and delete entries 1271 using mteObjectsEntryStatus. 1273 When adding objects to a notification they are added in the 1274 lexical order of their index in this table. Those associated 1275 with a trigger come first, then trigger test, then event." 1276 INDEX { mteOwner, mteObjectsName, mteObjectsIndex } 1277 ::= { mteObjectsTable 1 } 1279 MteObjectsEntry ::= SEQUENCE { 1280 mteObjectsName SnmpAdminString, 1281 mteObjectsIndex Unsigned32, 1282 mteObjectsID OBJECT IDENTIFIER, 1283 mteObjectsIDWildcard TruthValue, 1284 mteObjectsEntryStatus RowStatus 1285 } 1287 mteObjectsName OBJECT-TYPE 1288 SYNTAX SnmpAdminString (SIZE (1..32)) 1289 MAX-ACCESS not-accessible 1290 STATUS current 1291 DESCRIPTION 1292 "A locally-unique, administratively assigned name for a group of 1293 objects." 1294 ::= { mteObjectsEntry 1 } 1296 mteObjectsIndex OBJECT-TYPE 1297 SYNTAX Unsigned32 (1..4294967295) 1298 MAX-ACCESS not-accessible 1299 STATUS current 1300 DESCRIPTION 1301 "An arbitrary small integer for the purpose of identifying 1302 individual objects within a mteObjectsName group. 1304 Objects within a group are placed in the notification in the 1305 numerical order of this index. 1307 Groups are placed in the notification in the order of the 1308 selections for overall trigger, trigger test, and event. 1309 Within trigger test they are in the same order as the 1310 numerical values of the bits defined for mteTriggerTest. 1312 Bad object identifiers or a mismatch between truncating the 1313 identifier and the value of mteDeltaDiscontinuityIDWildcard 1314 result in operation as one would expect when providing the 1315 wrong identifier to a Get operation. The Get will fail or get 1316 the wrong object. If the object is not available it is omitted 1317 from the notification." 1318 ::= { mteObjectsEntry 2 } 1320 mteObjectsID OBJECT-TYPE 1321 SYNTAX OBJECT IDENTIFIER 1322 MAX-ACCESS read-create 1323 STATUS current 1324 DESCRIPTION 1325 "The object identifier of a MIB object to add to a 1326 Notification that results from the firing of a trigger. 1328 This may be wildcarded by truncating all or part of the 1329 instance portion, in which case the instance portion of the 1330 OID for obtaining this object will be the same as that used 1331 in obtaining the mteTriggerValueID that fired. If such 1332 wildcarding is applied, mteObjectsIDWildcard must be 1333 'true' and if not it must be 'false'. 1335 Each instance that fills the wildcard is independent of any 1336 additional instances, that is, wildcarded objects operate 1337 as if there were a separate table entry for each instance 1338 that fills the wildcard without having to actually predict 1339 all possible instances ahead of time." 1340 DEFVAL { zeroDotZero } 1341 ::= { mteObjectsEntry 3 } 1343 mteObjectsIDWildcard OBJECT-TYPE 1344 SYNTAX TruthValue 1345 MAX-ACCESS read-create 1346 STATUS current 1347 DESCRIPTION 1348 "Control for whether mteObjectsID is to be treated as 1349 fully-specified or wildcarded, with 'true' indicating wildcard." 1350 DEFVAL { false } 1351 ::= { mteObjectsEntry 4 } 1353 mteObjectsEntryStatus OBJECT-TYPE 1354 SYNTAX RowStatus 1355 MAX-ACCESS read-create 1356 STATUS current 1357 DESCRIPTION 1358 "The control that allows creation and deletion of entries. 1359 Once made active an entry may not be modified except to 1360 delete it." 1361 ::= { mteObjectsEntry 5 } 1363 -- 1364 -- Event Section 1365 -- 1367 -- Counters 1368 mteEventFailures OBJECT-TYPE 1369 SYNTAX Counter32 1370 MAX-ACCESS read-only 1371 STATUS current 1372 DESCRIPTION 1373 "The number of times an attempt to invoke an event 1374 has failed. This counts individually for each 1375 attempt in a group of targets or each attempt for a 1376 wildcarded trigger object." 1377 ::= { mteEvent 1 } 1379 -- 1380 -- Event Table 1381 -- 1383 mteEventTable OBJECT-TYPE 1384 SYNTAX SEQUENCE OF MteEventEntry 1385 MAX-ACCESS not-accessible 1386 STATUS current 1387 DESCRIPTION 1388 "A table of management event action information." 1389 ::= { mteEvent 2 } 1391 mteEventEntry OBJECT-TYPE 1392 SYNTAX MteEventEntry 1393 MAX-ACCESS not-accessible 1394 STATUS current 1395 DESCRIPTION 1396 "Information about a single event. Applications create and 1397 delete entries using mteEventEntryStatus." 1398 INDEX { mteOwner, IMPLIED mteEventName } 1399 ::= { mteEventTable 1 } 1401 MteEventEntry ::= SEQUENCE { 1402 mteEventName SnmpAdminString, 1403 mteEventComment SnmpAdminString, 1404 mteEventActions BITS, 1405 mteEventEnabled TruthValue, 1406 mteEventEntryStatus RowStatus 1407 } 1409 mteEventName OBJECT-TYPE 1410 SYNTAX SnmpAdminString (SIZE (1..32)) 1411 MAX-ACCESS not-accessible 1412 STATUS current 1413 DESCRIPTION 1414 "A locally-unique, administratively assigned name for the 1415 event." 1416 ::= { mteEventEntry 1 } 1418 mteEventComment OBJECT-TYPE 1419 SYNTAX SnmpAdminString 1420 MAX-ACCESS read-create 1421 STATUS current 1422 DESCRIPTION 1423 "A description of the event's function and use." 1424 DEFVAL { ''H } 1425 ::= { mteEventEntry 2 } 1427 mteEventActions OBJECT-TYPE 1428 SYNTAX BITS { notification(0), set(1) } 1429 MAX-ACCESS read-create 1430 STATUS current 1431 DESCRIPTION 1432 "The actions to perform when this event occurs. 1434 For 'notification', Traps and/or Informs are sent according 1435 to the configuration in the SNMP Notification MIB. 1437 For 'set', an SNMP Set operation is performed according to 1438 control values in this entry." 1439 DEFVAL { { } } -- No bits set. 1440 ::= { mteEventEntry 3 } 1442 mteEventEnabled OBJECT-TYPE 1443 SYNTAX TruthValue 1444 MAX-ACCESS read-create 1445 STATUS current 1446 DESCRIPTION 1447 "A control to allow an event to be configured but not used. 1448 When the value is 'false' the event does not execute even if 1449 triggered." 1450 DEFVAL { false } 1451 ::= { mteEventEntry 4 } 1453 mteEventEntryStatus OBJECT-TYPE 1454 SYNTAX RowStatus 1455 MAX-ACCESS read-create 1456 STATUS current 1457 DESCRIPTION 1458 "The control that allows creation and deletion of entries. 1459 Once made active an entry may not be modified except to 1460 delete it." 1461 ::= { mteEventEntry 5 } 1463 -- 1464 -- Event Notification Table 1465 -- 1467 mteEventNotificationTable OBJECT-TYPE 1468 SYNTAX SEQUENCE OF MteEventNotificationEntry 1469 MAX-ACCESS not-accessible 1470 STATUS current 1471 DESCRIPTION 1472 "A table of management event action notification information." 1473 ::= { mteEvent 3 } 1475 mteEventNotificationEntry OBJECT-TYPE 1476 SYNTAX MteEventNotificationEntry 1477 MAX-ACCESS not-accessible 1478 STATUS current 1479 DESCRIPTION 1480 "Information about a single event's notification. Entries 1481 automatically exist in this this table for each mteTriggerEntry 1482 that has 'notification' set in mteEventAction." 1483 INDEX { mteOwner, IMPLIED mteTriggerName } 1484 ::= { mteEventNotificationTable 1 } 1486 MteEventNotificationEntry ::= SEQUENCE { 1487 mteEventNotification OBJECT IDENTIFIER, 1488 mteEventNotificationObjectsOwner SnmpAdminString, 1489 mteEventNotificationObjects SnmpAdminString 1490 } 1492 mteEventNotification OBJECT-TYPE 1493 SYNTAX OBJECT IDENTIFIER 1494 MAX-ACCESS read-write 1495 STATUS current 1496 DESCRIPTION 1497 "The object identifier from the NOTIFICATION-TYPE for the 1498 notification to use if metEventActions has 'notification' set." 1499 DEFVAL { zeroDotZero } 1500 ::= { mteEventNotificationEntry 1 } 1502 mteEventNotificationObjectsOwner OBJECT-TYPE 1503 SYNTAX SnmpAdminString (SIZE (0..32)) 1504 MAX-ACCESS read-write 1505 STATUS current 1506 DESCRIPTION 1507 "To go with mteEventNotificationObjects, the mteOwner of a 1508 group of objects from mteObjectsTable." 1509 DEFVAL { ''H } 1510 ::= { mteEventNotificationEntry 2 } 1512 mteEventNotificationObjects OBJECT-TYPE 1513 SYNTAX SnmpAdminString (SIZE (0..32)) 1514 MAX-ACCESS read-write 1515 STATUS current 1516 DESCRIPTION 1517 "The mteObjectsName of a group of objects from 1518 mteObjectsTable if mteEventActions has 'notification' set. 1519 These objects are to be added to any Notification generated by 1520 this event. 1522 Objects may also be added based on the trigger that stimulated 1523 the event. 1525 A length of 0 indicates no additional objects." 1526 DEFVAL { ''H } 1527 ::= { mteEventNotificationEntry 3 } 1529 -- 1530 -- Event Set Table 1531 -- 1533 mteEventSetTable OBJECT-TYPE 1534 SYNTAX SEQUENCE OF MteEventSetEntry 1535 MAX-ACCESS not-accessible 1536 STATUS current 1537 DESCRIPTION 1538 "A table of management event action information." 1539 ::= { mteEvent 4 } 1541 mteEventSetEntry OBJECT-TYPE 1542 SYNTAX MteEventSetEntry 1543 MAX-ACCESS not-accessible 1544 STATUS current 1545 DESCRIPTION 1546 "Information about a single event's set option. Entries 1547 automatically exist in this this table for each mteTriggerEntry 1548 that has 'set' set in mteEventAction." 1549 INDEX { mteOwner, IMPLIED mteTriggerName } 1550 ::= { mteEventSetTable 1 } 1552 MteEventSetEntry ::= SEQUENCE { 1553 mteEventSetObject OBJECT IDENTIFIER, 1554 mteEventSetObjectWildcard TruthValue, 1555 mteEventSetValue Integer32, 1556 mteEventSetTargetTag SnmpTagValue, 1557 mteEventSetContextName SnmpAdminString, 1558 mteEventSetContextNameWildcard TruthValue 1559 } 1561 mteEventSetObject OBJECT-TYPE 1562 SYNTAX OBJECT IDENTIFIER 1563 MAX-ACCESS read-write 1564 STATUS current 1565 DESCRIPTION 1566 "The object identifier from the MIB object to set if 1567 mteEventActions has 'set' set. 1569 This object identifier may be wildcarded by leaving 1570 sub-identifiers off the end, in which case 1571 nteEventSetObjectWildCard must be 'true'. 1573 If mteEventSetObject is wildcarded the instance used to set the 1574 object to which it points is the same as the instance from the 1575 value of mteTriggerValueID that triggered the event. 1577 Each instance that fills the wildcard is independent of any 1578 additional instances, that is, wildcarded objects operate 1579 as if there were a separate table entry for each instance 1580 that fills the wildcard without having to actually predict 1581 all possible instances ahead of time. 1583 Bad object identifiers or a mismatch between truncating the 1584 identifier and the value of mteSetObjectWildcard 1585 result in operation as one would expect when providing the 1586 wrong identifier to a Set operation. The Set will fail or set 1587 the wrong object. If the value syntax of the destination 1588 object is not correct, the Set fails with the normal SNMP 1589 error code." 1590 DEFVAL { zeroDotZero } 1591 ::= { mteEventSetEntry 1 } 1593 mteEventSetObjectWildcard OBJECT-TYPE 1594 SYNTAX TruthValue 1595 MAX-ACCESS read-write 1596 STATUS current 1597 DESCRIPTION 1598 "Control over whether mteEventSetObject is to be treated as 1599 fully-specified or wildcarded, with 'true' indicating wildcard 1600 if mteEventActions has 'set' set." 1601 DEFVAL { false } 1602 ::= { mteEventSetEntry 2 } 1604 mteEventSetValue OBJECT-TYPE 1605 SYNTAX Integer32 1606 MAX-ACCESS read-write 1607 STATUS current 1608 DESCRIPTION 1609 "The value to which to set the object at mteEventSetObject 1610 if mteEventActions has 'set' set." 1611 DEFVAL { 0 } 1612 ::= { mteEventSetEntry 3 } 1614 mteEventSetTargetTag OBJECT-TYPE 1615 SYNTAX SnmpTagValue 1616 MAX-ACCESS read-write 1617 STATUS current 1618 DESCRIPTION 1619 "The tag for the target(s) at which to set the object at 1620 mteEventSetObject to mteEventSetValue if mteEventActions 1621 has 'set' set. 1623 Systems limited to self management may not accept a non-zero 1624 length for the value of this object. 1626 A length of 0 indicates the local system. In this case, 1627 access to the objects indicated by mteEventSetObject is under 1628 the security credentials of the requester that set 1629 mteTriggerEntryStatus to 'active'. Those credentials are the 1630 input parameters for isAccessAllowed from the Architecture for 1631 Describing SNMP Management Frameworks. 1633 Otherwise access rights are checked according to the security 1634 parameters resulting from the tag." 1635 DEFVAL { ''H } 1636 ::= { mteEventSetEntry 4 } 1638 mteEventSetContextName OBJECT-TYPE 1639 SYNTAX SnmpAdminString 1640 MAX-ACCESS read-write 1641 STATUS current 1642 DESCRIPTION 1643 "The management context in which to set mteEventObjectID. 1644 if mteEventActions has 'set' set. 1646 This may be wildcarded by leaving characters off the end. To 1647 indicate such wildcarding mteEventSetContextNameWildcard must 1648 be 'true'. 1650 If this context name is wildcarded the value used to complete 1651 the wildcarding of mteTriggerContextName will be appended." 1652 DEFVAL { ''H } 1653 ::= { mteEventSetEntry 5 } 1655 mteEventSetContextNameWildcard OBJECT-TYPE 1656 SYNTAX TruthValue 1657 MAX-ACCESS read-write 1658 STATUS current 1659 DESCRIPTION 1660 "Control for whether mteEventSetContextName is to be treated as 1661 fully-specified or wildcarded, with 'true' indicating wildcard 1662 if mteEventActions has 'set' set." 1663 DEFVAL { false } 1664 ::= { mteEventSetEntry 6 } 1666 -- 1667 -- Notifications 1668 -- 1670 dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::= { dismanEventMIB 2 } 1671 dismanEventMIBNotifications OBJECT IDENTIFIER ::= 1672 { dismanEventMIBNotificationPrefix 0 } 1673 dismanEventMIBNotificationObjects OBJECT IDENTIFIER 1674 ::= { dismanEventMIBNotificationPrefix 1 } 1676 -- 1677 -- Notification Objects 1678 -- 1679 mteHotTrigger OBJECT-TYPE 1680 SYNTAX SnmpAdminString 1681 MAX-ACCESS accessible-for-notify 1682 STATUS current 1683 DESCRIPTION 1684 "The name of the trigger causing the notification." 1685 ::= { dismanEventMIBNotificationObjects 1 } 1687 mteHotTargetName OBJECT-TYPE 1688 SYNTAX SnmpAdminString 1689 MAX-ACCESS accessible-for-notify 1690 STATUS current 1691 DESCRIPTION 1692 "The SNMP Target MIB's snmpTargetAddrName related to the 1693 notification." 1694 ::= { dismanEventMIBNotificationObjects 2 } 1696 mteHotContextName OBJECT-TYPE 1697 SYNTAX SnmpAdminString 1698 MAX-ACCESS accessible-for-notify 1699 STATUS current 1700 DESCRIPTION 1701 "The context name related to the notification. This must be as 1702 fully-qualified as possible, including filling in wildcard 1703 information determined in processing." 1704 ::= { dismanEventMIBNotificationObjects 3 } 1706 mteHotOID OBJECT-TYPE 1707 SYNTAX OBJECT IDENTIFIER 1708 MAX-ACCESS accessible-for-notify 1709 STATUS current 1710 DESCRIPTION 1711 "The object identifier of the destination object related to the 1712 notification. This must be as fully-qualified as possible, 1713 inluding filling in wildcard informaation determined in 1714 processing. 1716 For a trigger-related notification this is from 1717 mteTriggerValueID. 1719 For a set failure this is from mteEventSetObject." 1720 ::= { dismanEventMIBNotificationObjects 4 } 1722 mteHotValue OBJECT-TYPE 1723 SYNTAX Integer32 1724 MAX-ACCESS accessible-for-notify 1725 STATUS current 1726 DESCRIPTION 1727 "The value of the object at mteTriggerValueID when a 1728 trigger fired." 1729 ::= { dismanEventMIBNotificationObjects 5 } 1731 mteFailedReason OBJECT-TYPE 1732 SYNTAX FailureReason 1733 MAX-ACCESS accessible-for-notify 1734 STATUS current 1735 DESCRIPTION 1736 "The reason for the failure of an attempt to check for a 1737 trigger condition or set an object in response to an event." 1738 ::= { dismanEventMIBNotificationObjects 6 } 1740 -- 1741 -- Notifications 1742 -- 1744 mteTriggerFired NOTIFICATION-TYPE 1745 OBJECTS { mteHotTrigger, 1746 mteHotTargetName, 1747 mteHotContextName, 1748 mteHotOID, 1749 mteHotValue } 1750 STATUS current 1751 DESCRIPTION 1752 "Notification that the trigger indicated by the object 1753 instances has fired, for triggers with mteTriggerType 1754 'boolean' or 'existence'." 1755 ::= { dismanEventMIBNotifications 1 } 1757 mteTriggerRising NOTIFICATION-TYPE 1758 OBJECTS { mteHotTrigger, 1759 mteHotTargetName, 1760 mteHotContextName, 1761 mteHotOID, 1762 mteHotValue } 1763 STATUS current 1764 DESCRIPTION 1765 "Notification that the rising threshold was met for triggers 1766 with mteTriggerType 'threshold'." 1767 ::= { dismanEventMIBNotifications 2 } 1769 mteTriggerFalling NOTIFICATION-TYPE 1770 OBJECTS { mteHotTrigger, 1771 mteHotTargetName, 1772 mteHotContextName, 1773 mteHotOID, 1774 mteHotValue } 1775 STATUS current 1776 DESCRIPTION 1777 "Notification that the falling threshold was met for triggers 1778 with mteTriggerType 'threshold'." 1779 ::= { dismanEventMIBNotifications 3 } 1781 mteTriggerFailure NOTIFICATION-TYPE 1782 OBJECTS { mteHotTrigger, 1783 mteHotTargetName, 1784 mteHotContextName, 1785 mteHotOID, 1786 mteFailedReason } 1787 STATUS current 1788 DESCRIPTION 1789 "Notification that an attempt to check a trigger has failed. 1791 The network manager must enable this notification only with 1792 a certain fear and trembling, as it can easily crowd out more 1793 important information. It should be used only to help diagnose 1794 a problem that has appeared in the error counters and can not 1795 be found otherwise." 1796 ::= { dismanEventMIBNotifications 4 } 1798 mteEventSetFailure NOTIFICATION-TYPE 1799 OBJECTS { mteHotTrigger, 1800 mteHotTargetName, 1801 mteHotContextName, 1802 mteHotOID, 1803 mteFailedReason } 1804 STATUS current 1805 DESCRIPTION 1806 "Notification that an attempt to do a set in response to an 1807 event has failed. 1809 The network manager must enable this notification only with 1810 a certain fear and trembling, as it can easily crowd out more 1811 important information. It should be used only to help diagnose 1812 a problem that has appeared in the error counters and can not 1813 be found otherwise." 1815 ::= { dismanEventMIBNotifications 5 } 1817 -- 1818 -- Conformance 1819 -- 1821 dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 } 1822 dismanEventMIBCompliances OBJECT IDENTIFIER ::= { dismanEventMIBConformance 1823 1 } 1824 dismanEventMIBGroups OBJECT IDENTIFIER ::= { dismanEventMIBConformance 1825 2 } 1827 -- Compliance 1829 dismanEventMIBCompliance MODULE-COMPLIANCE 1830 STATUS current 1831 DESCRIPTION 1832 "The compliance statement for entities which implement 1833 the Event MIB." 1834 MODULE -- this module 1835 MANDATORY-GROUPS { 1836 dismanEventResourceGroup, 1837 dismanEventTriggerGroup, 1838 dismanEventObjectsGroup, 1839 dismanEventEventGroup, 1840 dismanEventNotificationObjectGroup, 1841 dismanEventNotificationGroup 1842 } 1844 OBJECT mteTriggerTargetTag 1845 MIN-ACCESS read-only 1846 DESCRIPTION 1847 "Write access is not required, thus limiting 1848 monitoring to the local system or preconfigured 1849 remote systems." 1851 OBJECT mteEventSetTargetTag 1852 MIN-ACCESS read-only 1853 DESCRIPTION 1854 "Write access is not required, thus limiting 1855 setting to the local system or preconfigured 1856 remote systems." 1858 OBJECT mteTriggerValueIDWildcard 1859 MIN-ACCESS read-only 1860 DESCRIPTION 1861 "Write access is not required, thus allowing 1862 the system not to implement wildcarding." 1864 OBJECT mteTriggerContextNameWildcard 1865 MIN-ACCESS read-only 1866 DESCRIPTION 1867 "Write access is not required, thus allowing 1868 the system not to implement wildcarding." 1870 OBJECT mteObjectsIDWildcard 1871 MIN-ACCESS read-only 1872 DESCRIPTION 1873 "Write access is not required, thus allowing 1874 the system not to implement wildcarding." 1876 OBJECT mteEventSetContextNameWildcard 1877 MIN-ACCESS read-only 1878 DESCRIPTION 1879 "Write access is not required, thus allowing 1880 the system not to implement wildcarding." 1882 ::= { dismanEventMIBCompliances 1 } 1884 -- Units of Conformance 1886 dismanEventResourceGroup OBJECT-GROUP 1887 OBJECTS { 1888 mteResourceSampleMinimum, 1889 mteResourceSampleInstanceMaximum, 1890 mteResourceSampleInstances, 1891 mteResourceSampleInstancesHigh, 1892 mteResourceSampleInstanceLacks 1893 } 1894 STATUS current 1895 DESCRIPTION 1896 "Event resource status and control objects." 1897 ::= { dismanEventMIBGroups 1 } 1899 dismanEventTriggerGroup OBJECT-GROUP 1900 OBJECTS { 1901 mteTriggerFailures, 1902 mteTriggerComment, 1903 mteTriggerTest, 1904 mteTriggerSampleType, 1905 mteTriggerValueID, 1906 mteTriggerValueIDWildcard, 1907 mteTriggerTargetTag, 1908 mteTriggerContextName, 1909 mteTriggerContextNameWildcard, 1910 mteTriggerFrequency, 1911 mteTriggerObjectsOwner, 1912 mteTriggerObjects, 1913 mteTriggerEnabled, 1914 mteTriggerEntryStatus, 1916 mteTriggerDeltaDiscontinuityID, 1917 mteTriggerDeltaDiscontinuityIDWildcard, 1918 mteTriggerDeltaDiscontinuityIDType, 1920 mteTriggerExistenceTest, 1921 mteTriggerExistenceStartup, 1922 mteTriggerExistenceObjectsOwner, 1923 mteTriggerExistenceObjects, 1924 mteTriggerExistenceEventOwner, 1925 mteTriggerExistenceEvent, 1927 mteTriggerBooleanComparison, 1928 mteTriggerBooleanValue, 1929 mteTriggerBooleanStartup, 1930 mteTriggerBooleanObjectsOwner, 1931 mteTriggerBooleanObjects, 1932 mteTriggerBooleanEventOwner, 1933 mteTriggerBooleanEvent, 1935 mteTriggerThresholdValue, 1936 mteTriggerThresholdStartup, 1937 mteTriggerThresholdObjectsOwner, 1938 mteTriggerThresholdObjects, 1939 mteTriggerThresholdRising, 1940 mteTriggerThresholdFalling, 1941 mteTriggerThresholdRisingEventOwner, 1942 mteTriggerThresholdRisingEvent, 1943 mteTriggerThresholdFallingEventOwner, 1944 mteTriggerThresholdFallingEvent 1945 } 1946 STATUS current 1947 DESCRIPTION 1948 "Event triggers." 1949 ::= { dismanEventMIBGroups 2 } 1951 dismanEventObjectsGroup OBJECT-GROUP 1952 OBJECTS { 1953 mteObjectsID, 1954 mteObjectsIDWildcard, 1955 mteObjectsEntryStatus 1956 } 1957 STATUS current 1958 DESCRIPTION 1959 "Supplemental objects." 1960 ::= { dismanEventMIBGroups 3 } 1962 dismanEventEventGroup OBJECT-GROUP 1963 OBJECTS { 1964 mteEventFailures, 1966 mteEventComment, 1967 mteEventActions, 1968 mteEventEnabled, 1969 mteEventEntryStatus, 1971 mteEventNotification, 1972 mteEventNotificationObjectsOwner, 1973 mteEventNotificationObjects, 1975 mteEventSetObject, 1976 mteEventSetObjectWildcard, 1977 mteEventSetValue, 1978 mteEventSetTargetTag, 1979 mteEventSetContextName, 1980 mteEventSetContextNameWildcard 1981 } 1982 STATUS current 1983 DESCRIPTION 1984 "Events." 1985 ::= { dismanEventMIBGroups 4 } 1987 dismanEventNotificationObjectGroup OBJECT-GROUP 1988 OBJECTS { 1989 mteHotTrigger, 1990 mteHotTargetName, 1991 mteHotContextName, 1992 mteHotOID, 1993 mteHotValue, 1994 mteFailedReason 1995 } 1996 STATUS current 1997 DESCRIPTION 1998 "Notification objects." 1999 ::= { dismanEventMIBGroups 5 } 2001 dismanEventNotificationGroup NOTIFICATION-GROUP 2002 NOTIFICATIONS { 2003 mteTriggerFired, 2004 mteTriggerRising, 2005 mteTriggerFalling, 2006 mteTriggerFailure, 2007 mteEventSetFailure 2008 } 2009 STATUS current 2010 DESCRIPTION 2011 "Notifications." 2012 ::= { dismanEventMIBGroups 6 } 2014 END 2015 9. Intellectual Property 2017 The IETF takes no position regarding the validity or scope of any 2018 intellectual property or other rights that might be claimed to pertain 2019 to the implementation or use of the technology described in this 2020 document or the extent to which any license under such rights might or 2021 might not be available; neither does it represent that it has made any 2022 effort to identify any such rights. Information on the IETF's 2023 procedures with respect to rights in standards-track and standards- 2024 related documentation can be found in BCP-11. Copies of claims of 2025 rights made available for publication and any assurances of licenses to 2026 be made available, or the result of an attempt made to obtain a general 2027 license or permission for the use of such proprietary rights by 2028 implementors or users of this specification can be obtained from the 2029 IETF Secretariat. 2031 10. Acknowledgements 2033 This MIB contains considerable contributions from the RMON MIB, the 2034 Distributed Management Design Team (Andy Bierman, Maria Greene, Bob 2035 Stewart, and Steve Waldbusser), the Distributed Management Working 2036 Group, and colleagues at Cisco. 2038 11. References 2040 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 2041 for Describing SNMP Management Frameworks", RFC 2571, April 2042 1999 2044 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 2045 of Management Information for TCP/IP-based Internets", STD 2046 16, RFC 1155, May 1990 2048 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 2049 16, RFC 1212, March 1991 2051 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 2052 SNMP", RFC 1215, March 1991 2054 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2055 Rose, M., and S. Waldbusser, "Structure of Management 2056 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 2058 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2059 Rose, M., and S. Waldbusser, "Textual Conventions for 2060 SMIv2", STD 58, RFC 2579, April 1999 2062 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2063 Rose, M., and S. Waldbusser, "Conformance Statements for 2064 SMIv2", STD 58, RFC 2580, April 1999 2066 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2067 Network Management Protocol", STD 15, RFC 1157, May 1990. 2069 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2070 "Introduction to Community-based SNMPv2", RFC 1901, January 2071 1996. 2073 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2074 "Transport Mappings for Version 2 of the Simple Network 2075 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2077 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2078 Processing and Dispatching for the Simple Network Management 2079 Protocol (SNMP)", RFC 2572, April 1999 2081 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 2082 (USM) for version 3 of the Simple Network Management 2083 Protocol (SNMPv3)", RFC 2574, April 1999 2085 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2086 "Protocol Operations for Version 2 of the Simple Network 2087 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2089 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 2090 RFC 2573, April 1999 2092 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2093 Access Control Model (VACM) for the Simple Network 2094 Management Protocol (SNMP)", RFC 2575, April 1999 2096 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2097 "Introduction to Version 3 of the Internet-standard Network 2098 Management Framework", RFC 2570, April 1999 2100 [RFC1903] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 2101 "Coexistence between Version 1 and version 2 of the 2102 Internet-standard Network Management Framework", RFC 1903, 2103 January 1996. 2105 [RFCEventMIB] 2106 Stewart, B., "Event MIB", RFC ????, ?Month? 1999. 2108 [RFC1757] 2109 Waldbusser, S., "Remote Network Monitoring Management Information 2110 Base", RFC 1757, February 1995. 2112 [RFC1451] 2113 Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to- 2114 Manager Management Information Base", RFC 1451, April 1993. 2116 [RFCExpressionMIB] 2117 Stewart, B., "Expression MIB", RFC ????, ?Month? 1999. 2119 [RFCNotificationLogMIB] 2120 Stewart, B., "Notification Log MIB", RFC ????, ?Month? 1999. 2122 12. Security Considerations 2124 Security issues are discussed in the Security section and in the 2125 DESCRIPTION clauses of relevant objects. 2127 13. Author's Address 2129 Bob Stewart 2130 Cisco Systems, Inc. 2131 170 West Tasman Drive 2132 San Jose, CA 95134-1706 2133 U.S.A. 2135 Phone: +1 408 526 4527 2136 Email: bstewart@cisco.com 2138 14. Full Copyright Statement 2140 Copyright (C) The Internet Society (1999). All Rights Reserved. 2142 This document and translations of it may be copied and furnished to 2143 others, and derivative works that comment on or otherwise explain it or 2144 assist in its implementation may be prepared, copied, published and 2145 distributed, in whole or in part, without restriction of any kind, 2146 provided that the above copyright notice and this paragraph are included 2147 on all such copies and derivative works. However, this document itself 2148 may not be modified in any way, such as by removing the copyright notice 2149 or references to the Internet Society or other Internet organizations, 2150 except as needed for the purpose of developing Internet standards in 2151 which case the procedures for copyrights defined in the Internet 2152 Standards process must be followed, or as required to translate it into 2153 languages other than English. 2155 The limited permissions granted above are perpetual and will not be 2156 revoked by the Internet Society or its successors or assigns. 2158 This document and the information contained herein is provided on an "AS 2159 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2160 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2161 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 2162 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 2163 FITNESS FOR A PARTICULAR PURPOSE. 2165 Table of Contents 2167 1 Abstract ........................................................ 2 2168 2 The SNMP Management Framework ................................... 2 2169 3 Overview ........................................................ 4 2170 4 Relationship to Other MIBs ...................................... 4 2171 5 MIB Sections .................................................... 4 2172 6 Operation ....................................................... 5 2173 7 Security ........................................................ 6 2174 8 Definitions ..................................................... 8 2175 9 Intellectual Property ........................................... 48 2176 10 Acknowledgements ............................................... 49 2177 11 References ..................................................... 50 2178 12 Security Considerations ........................................ 52 2179 13 Author's Address ............................................... 52 2180 14 Full Copyright Statement ....................................... 53