idnits 2.17.1 draft-ietf-disman-event-mib-08.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: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories -- 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 4 instances of too long lines in the document, the longest one being 8 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 311 has weird spacing: '...rceLack some...' == Line 316 has weird spacing: '...achable can'...' == Line 2165 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 (22 October 1999) is 8952 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 2107, but no explicit reference was found in the text == Unused Reference: 'RFCEventMIB' is defined on line 2112, but no explicit reference was found in the text == Unused Reference: 'RFCNotificationLogMIB' is defined on line 2126, 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: 21 errors (**), 0 flaws (~~), 10 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Distributed Management Event MIB 22 October 1999 3 Event MIB 5 22 October 1999 7 draft-ietf-disman-event-mib-08.txt 9 Bob Stewart 10 Cisco Systems, Inc. 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with all 15 provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering Task 18 Force (IETF), its areas, and its working groups. Note that other groups 19 may also distribute working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet- Drafts as reference material 24 or to cite them other than as ``work in progress.'' 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html.Distribution of this document is unlimited. 32 Please send comments to the 33 Distributed Management Working Group, . 35 Copyright Notice 37 Copyright (C) The Internet Society (1999). All Rights Reserved. 39 1. Abstract 41 This memo defines a portion of the Management Information Base (MIB) for 42 use with network management protocols in the Internet community. In 43 particular, it describes managed objects used for managing monitoring of 44 MIB objects and taking action through events. 46 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 47 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 48 document are to be interpreted as described in RFC 2119. 50 2. The SNMP Management Framework 52 The SNMP Management Framework presently consists of five major 53 components: 55 o An overall architecture, described in RFC 2571 [RFC2571]. 57 o Mechanisms for describing and naming objects and events for the 58 purpose of management. The first version of this Structure of 59 Management Information (SMI) is called SMIv1 and described in 60 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 61 1215 [RFC1215]. The second version, called SMIv2, is described 62 in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 63 [RFC2580]. 65 o Message protocols for transferring management information. The 66 first version of the SNMP message protocol is called SNMPv1 and 67 described in STD 15, RFC 1157 [RFC1157]. A second version of the 68 SNMP message protocol, which is not an Internet standards track 69 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 70 and RFC 1906 [RFC1906]. The third version of the message 71 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 72 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 74 o Protocol operations for accessing management information. The 75 first set of protocol operations and associated PDU formats is 76 described in STD 15, RFC 1157 [RFC1157]. A second set of 77 protocol operations and associated PDU formats is described in 78 RFC 1905 [RFC1905]. 80 o A set of fundamental applications described in RFC 2573 81 [RFC2573] and the view-based access control mechanism described 82 in RFC 2575 [RFC2575]. 84 A more detailed introduction to the current SNMP Management Framework 85 can be found in RFC 2570 [RFC2570]. 87 Managed objects are accessed via a virtual information store, termed 88 the Management Information Base or MIB. Objects in the MIB are 89 defined using the mechanisms defined in the SMI. 91 This memo specifies a MIB module that is compliant to the SMIv2. A 92 MIB conforming to the SMIv1 can be produced through the appropriate 93 translations. The resulting translated MIB must be semantically 94 equivalent, except where objects or events are omitted because no 95 translation is possible (use of Counter64). Some machine readable 96 information in SMIv2 will be converted into textual descriptions in 97 SMIv1 during the translation process. However, this loss of machine 98 readable information is not considered to change the semantics of the 99 MIB. 101 3. Overview 103 With network sizes well beyond the ability of people to management them 104 directly, automated, distributed management is vital. An important 105 aspect of such management is the ability of a system to monitor itself 106 or for some other system to monitor it. 108 The Event MIB provides the ability to monitor MIB objects on the local 109 system or on a remote system and take simple action when a trigger 110 condition is met. 112 The MIB is intended to suit either a relatively powerful manager or mid- 113 level manager, as well as a somewhat more limited self-managing 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 Integer32, Unsigned32, 254 NOTIFICATION-TYPE, Counter32, 255 Gauge32, mib-2, zeroDotZero 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 "9910220000Z" 266 ORGANIZATION "IETF Distributed Management Working Group" 267 CONTACT-INFO "Ramanathan Kavasseri 268 Cisco Systems, Inc. 269 170 West Tasman Drive, 270 San Jose CA 95134-1706. 271 Phone: +1 408 526 4527 272 Email: ramk@cisco.com" 273 DESCRIPTION 274 "The MIB module for defining event triggers and actions 275 for network management purposes." 276 -- Revision History 278 REVISION "9910220000Z" -- 22 October 1999 279 DESCRIPTION "This is the initial version of this MIB. 280 Published as RFC xxxxx" 281 ::= { mib-2 xx } -- final assignment by IANA at publication time 283 dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 } 285 mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 } 286 mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 } 287 mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 } 288 mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 } 290 -- 291 -- Textual Conventions 292 -- 294 FailureReason ::= TEXTUAL-CONVENTION 295 STATUS current 296 DESCRIPTION 297 "Reasons for failures in an attempt to perform a management 298 request. 300 The first group of errors, numbered less than 0, are related 301 to problems in sending the request. The existence of a 302 particular error code here does not imply that all 303 implementations are capable of sensing that error and 304 returning that code. 306 The second group, numbered greater than 0, are copied 307 directly from SNMP protocol operations and are intended to carry 308 exactly the meanings defined for the protocol as returned in 309 an SNMP response. 311 localResourceLack some local resource such as memory lacking 312 or mteResourceSampleInstanceMaximum 313 exceeded 314 badDestination unrecognized domain name or otherwise 315 invalid destination address 316 destinationUnreachable can't get to destination address 317 noResponse no response to SNMP request 318 badType the data syntax of a retrieved object 319 as not as expected 320 sampleOverrun another sample attempt occurred before 321 the previous one completed" 323 SYNTAX INTEGER { localResourceLack(-1), 324 badDestination(-2), 325 destinationUnreachable(-3), 326 noResponse(-4), 327 badType(-5), 328 sampleOverrun(-6), 330 noError(0), 332 tooBig(1), 333 noSuchName(2), 334 badValue(3), 335 readOnly(4), 336 genErr(5), 337 noAccess(6), 338 wrongType(7), 339 wrongLength(8), 340 wrongEncoding(9), 341 wrongValue(10), 342 noCreation(11), 343 inconsistentValue(12), 344 resourceUnavailable(13), 345 commitFailed(14), 346 undoFailed(15), 347 authorizationError(16), 348 notWritable(17), 349 inconsistentName(18) } 350 -- 351 -- Resource Control Section 352 -- 354 mteResourceSampleMinimum OBJECT-TYPE 355 SYNTAX Integer32 (1..600) 356 UNITS "seconds" 357 MAX-ACCESS read-write 358 STATUS current 359 DESCRIPTION 360 "The minimum mteTriggerFrequency this system will 361 accept. A system may use the larger values of this minimum to 362 lessen the impact of constant sampling. For larger 363 sampling intervals the system samples less often and 364 suffers less overhead. This object provides a way to enforce 365 such lower overhead for all triggers created after it is 366 set. 368 Unless explicitly resource limited, a system's value for 369 this object should be 1, allowing as small as a 1 second 370 interval for ongoing trigger sampling. 372 Changing this value will not invalidate an existing setting 373 of mteTriggerFrequency." 374 ::= { mteResource 1 } 376 mteResourceSampleInstanceMaximum OBJECT-TYPE 377 SYNTAX Unsigned32 378 UNITS "instances" 379 MAX-ACCESS read-write 380 STATUS current 381 DESCRIPTION 382 "The maximum number of instance entries this system will 383 support for sampling. 385 These are the entries that maintain state, one for each 386 instance of each sampled object as selected by 387 mteTriggerValueID. Note that wildcarded objects result 388 in multiple instances of this state. 390 A value of 0 indicates no preset limit, that is, the limit 391 is dynamic based on system operation and resources. 393 Unless explicitly resource limited, a system's value for 394 this object should be 0. 396 Changing this value will not eliminate or inhibit existing sample 397 state but could prevent allocation of additional state 398 information." 399 ::= { mteResource 2 } 401 mteResourceSampleInstances OBJECT-TYPE 402 SYNTAX Gauge32 403 UNITS "instances" 404 MAX-ACCESS read-only 405 STATUS current 406 DESCRIPTION 407 "The number of currently active instance entries as 408 defined for mteResourceSampleInstanceMaximum." 409 ::= { mteResource 3 } 411 mteResourceSampleInstancesHigh OBJECT-TYPE 412 SYNTAX Gauge32 413 UNITS "instances" 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The highest value of mteResourceSampleInstances that has 418 occurred since initialization of the management system." 419 ::= { mteResource 4 } 421 mteResourceSampleInstanceLacks OBJECT-TYPE 422 SYNTAX Counter32 423 UNITS "instances" 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The number of times this system could not take a new sample 428 because that allocation would have exceeded the limit set by 429 mteResourceSampleInstanceMaximum." 430 ::= { mteResource 5 } 432 -- 433 -- Trigger Section 434 -- 436 -- Counters 438 mteTriggerFailures OBJECT-TYPE 439 SYNTAX Counter32 440 MAX-ACCESS read-only 441 STATUS current 442 DESCRIPTION 443 "The number of times an attempt to check for a trigger 444 condition has failed. This counts individually for each 445 attempt in a group of targets or each attempt for a 446 wildcarded object." 447 ::= { mteTrigger 1 } 449 -- 450 -- Trigger Table 451 -- 453 mteTriggerTable OBJECT-TYPE 454 SYNTAX SEQUENCE OF MteTriggerEntry 455 MAX-ACCESS not-accessible 456 STATUS current 457 DESCRIPTION 458 "A table of management event trigger information." 459 ::= { mteTrigger 2 } 461 mteTriggerEntry OBJECT-TYPE 462 SYNTAX MteTriggerEntry 463 MAX-ACCESS not-accessible 464 STATUS current 465 DESCRIPTION 466 "Information about a single trigger. Applications create and 467 delete entries using mteTriggerEntryStatus." 468 INDEX { mteOwner, IMPLIED mteTriggerName } 469 ::= { mteTriggerTable 1 } 471 MteTriggerEntry ::= SEQUENCE { 472 mteOwner SnmpAdminString, 473 mteTriggerName SnmpAdminString, 474 mteTriggerComment SnmpAdminString, 475 mteTriggerTest BITS, 476 mteTriggerSampleType INTEGER, 477 mteTriggerValueID OBJECT IDENTIFIER, 478 mteTriggerValueIDWildcard TruthValue, 479 mteTriggerTargetTag SnmpTagValue, 480 mteTriggerContextName SnmpAdminString, 481 mteTriggerContextNameWildcard TruthValue, 482 mteTriggerFrequency Unsigned32, 483 mteTriggerObjectsOwner SnmpAdminString, 484 mteTriggerObjects SnmpAdminString, 485 mteTriggerEnabled TruthValue, 486 mteTriggerEntryStatus RowStatus 487 } 489 mteOwner OBJECT-TYPE 490 SYNTAX SnmpAdminString (SIZE(0..32)) 491 MAX-ACCESS not-accessible 492 STATUS current 493 DESCRIPTION 494 "The owner of this entry. The exact semantics of this 495 string are subject to the security policy defined by the 496 security administrator." 497 ::= { mteTriggerEntry 1 } 499 mteTriggerName OBJECT-TYPE 500 SYNTAX SnmpAdminString (SIZE (1..32)) 501 MAX-ACCESS not-accessible 502 STATUS current 503 DESCRIPTION 504 "A locally-unique, administratively assigned name for the 505 trigger within the scope of mteOwner." 506 ::= { mteTriggerEntry 2 } 508 mteTriggerComment OBJECT-TYPE 509 SYNTAX SnmpAdminString 510 MAX-ACCESS read-create 511 STATUS current 512 DESCRIPTION 513 "A description of the trigger's function and use." 514 DEFVAL { ''H } 515 ::= { mteTriggerEntry 3 } 517 mteTriggerTest OBJECT-TYPE 518 SYNTAX BITS { existence(0), boolean(1), threshold(2) } 519 MAX-ACCESS read-create 520 STATUS current 521 DESCRIPTION 522 "The type of trigger test to perform. For 'boolean' and 523 'threshold' tests, the object at mteTriggerValueID must 524 evaluate to an integer, that is, anything that ends up encoded 525 for transmission (that is, in BER, not ASN.1) as an integer. 527 For 'existence', the specific test is as selected by 528 mteTriggerExistenceTest. When an object appears or vanishes 529 the trigger fires. The trigger will not fire again until the 530 object has changed states. 532 For 'boolean', the specific test is as selected by 533 mteTriggerBooleanTest. If the test result is true the trigger 534 fires. The trigger will not fire again until the value has 535 become false and come back to true. 537 For 'threshold' the test works as described below for 538 mteTriggerThresholdStartup, mteTriggerThresholdRising, and 539 mteTriggerThresholdFalling. 541 Note that combining 'boolean' and 'threshold' tests on the 542 same object may be somewhat redundant." 543 DEFVAL { boolean } 544 ::= { mteTriggerEntry 4 } 546 mteTriggerSampleType OBJECT-TYPE 547 SYNTAX INTEGER { absoluteValue(1), deltaValue(2) } 548 MAX-ACCESS read-create 549 STATUS current 550 DESCRIPTION 551 "The type of sampling to perform. 553 An 'absoluteValue' sample requires only a single sample to be 554 meaningful, and is exactly the value of the object at 555 mteTriggerValueID at the sample time. 557 A 'deltaValue' requires two samples to be meaningful and is 558 thus not available for testing until the second and subsequent 559 samples after the object at mteTriggerValueID is first found 560 to exist. It is the difference between the two samples. For 561 unsigned values it is always positive, based on unsigned 562 arithmetic. For signed values it can be positive or negative. 564 For SNMP counters to be meaningful they must be sampled as a 565 'deltaValue'. 567 For 'deltaValue' mteTriggerDeltaTable contains further 568 parameters. 570 If only 'existence' is set in mteTriggerTest this object has 571 no meaning." 572 DEFVAL { absoluteValue } 573 ::= { mteTriggerEntry 5 } 575 mteTriggerValueID OBJECT-TYPE 576 SYNTAX OBJECT IDENTIFIER 577 MAX-ACCESS read-create 578 STATUS current 579 DESCRIPTION 580 "The object identifier of the MIB object to sample to see 581 if the trigger should fire. 583 This may be wildcarded by truncating all or part of the 584 instance portion, in which case the value is obtained 585 as if with a GetNext function, checking multiple values 586 if they exist. If such wildcarding is applied, 587 mteTriggerValueIDWildcard must be 'true' and if not it must 588 be 'false'. 590 Bad object identifiers or a mismatch between truncating the 591 identifier and the value of mteTriggerValueIDWildcard result 592 in operation as one would expect when providing the wrong 593 identifier to a Get or GetNext operation. The Get will fail 594 or get the wrong object. The GetNext will indeed get whatever 595 is next, proceeding until it runs past the initial part of the 596 identifier and perhaps many unintended objects for confusing 597 results. If the value syntax of those objects is not usable, 598 that results in a 'badType' error that terminates the scan. 600 Each instance that fills the wildcard is independent of any 601 additional instances, that is, wildcarded objects operate 602 as if there were a separate table entry for each instance 603 that fills the wildcard without having to actually predict 604 all possible instances ahead of time." 605 DEFVAL { zeroDotZero } 606 ::= { mteTriggerEntry 6 } 608 mteTriggerValueIDWildcard OBJECT-TYPE 609 SYNTAX TruthValue 610 MAX-ACCESS read-create 611 STATUS current 612 DESCRIPTION 613 "Control for whether mteTriggerValueID is to be treated as 614 fully-specified or wildcarded, with 'true' indicating wildcard." 615 DEFVAL { false } 616 ::= { mteTriggerEntry 7 } 618 mteTriggerTargetTag OBJECT-TYPE 619 SYNTAX SnmpTagValue 620 MAX-ACCESS read-create 621 STATUS current 622 DESCRIPTION 623 "The tag for the target(s) from which to obtain the condition 624 for a trigger check. 626 A length of 0 indicates the local system. In this case, 627 access to the objects indicated by mteTriggerValueID is under 628 the security credentials of the requester that set 629 mteTriggerEntryStatus to 'active'. Those credentials are the 630 input parameters for isAccessAllowed from the Architecture for 631 Describing SNMP Management Frameworks. 633 Otherwise access rights are checked according to the security 634 parameters resulting from the tag." 635 DEFVAL { ''H } 636 ::= { mteTriggerEntry 8 } 638 mteTriggerContextName OBJECT-TYPE 639 SYNTAX SnmpAdminString 640 MAX-ACCESS read-create 641 STATUS current 642 DESCRIPTION 643 "The management context from which to obtain mteTriggerValueID. 645 This may be wildcarded by leaving characters off the end. For 646 example use 'Repeater' to wildcard to 'Repeater1', 647 'Repeater2', 'Repeater-999.87b', and so on. To indicate such 648 wildcarding is intended, mteTriggerContextNameWildcard must 649 be 'true'. 651 Each instance that fills the wildcard is independent of any 652 additional instances, that is, wildcarded objects operate 653 as if there were a separate table entry for each instance 654 that fills the wildcard without having to actually predict 655 all possible instances ahead of time. 657 Operation of this feature assumes that the local system has a 658 list of available contexts against which to apply the 659 wildcard. If the objects are being read from the local 660 system, this is clearly the system's own list of contexts. 661 For a remote system a local version of such a list is not 662 defined by any current standard and may not be available, so 663 this function may not be supported." 664 DEFVAL { ''H } 665 ::= { mteTriggerEntry 9 } 667 mteTriggerContextNameWildcard OBJECT-TYPE 668 SYNTAX TruthValue 669 MAX-ACCESS read-create 670 STATUS current 671 DESCRIPTION 672 "Control for whether mteTriggerContextName is to be treated as 673 fully-specified or wildcarded, with 'true' indicating wildcard." 674 DEFVAL { false } 675 ::= { mteTriggerEntry 10 } 677 mteTriggerFrequency OBJECT-TYPE 678 SYNTAX Unsigned32 679 UNITS "seconds" 680 MAX-ACCESS read-create 681 STATUS current 682 DESCRIPTION 683 "The number of seconds to wait between trigger samples. To 684 encourage consistency in sampling, the interval is measured 685 from the beginning of one check to the beginning of the next 686 and the timer is restarted immediately when it expires, not 687 when the check completes. 689 If the next sample begins before the previous one completed the 690 system may either attempt to make the check or treat this as an 691 error condition with the error 'sampleOverrun'. 693 A frequency of 0 indicates instantaneous recognition of the 694 condition. This is not possible in many cases, but may 695 be supported in cases where it makes sense and the system is 696 able to do so. This feature allows the MIB to be used in 697 implementations where such interrupt-driven behavior is 698 possible and is not likely to be supported for all MIB objects 699 even then since such sampling generally has to be tightly 700 integrated into low-level code. 702 Systems that can support this should document those cases 703 where it can be used. In cases where it can not, setting this 704 object to 0 simply returns a bad value error." 705 DEFVAL { 600 } 706 ::= { mteTriggerEntry 11 } 708 mteTriggerObjectsOwner OBJECT-TYPE 709 SYNTAX SnmpAdminString (SIZE (0..32)) 710 MAX-ACCESS read-create 711 STATUS current 712 DESCRIPTION 713 "To go with mteTriggerObjects, the mteOwner of a group of 714 objects from mteObjectsTable." 715 DEFVAL { ''H } 716 ::= { mteTriggerEntry 12 } 718 mteTriggerObjects OBJECT-TYPE 719 SYNTAX SnmpAdminString (SIZE (0..32)) 720 MAX-ACCESS read-create 721 STATUS current 722 DESCRIPTION 723 "The mteObjectsName of a group of objects from 724 mteObjectsTable. These objects are to be added to any 725 Notification resulting from the firing of this trigger. 727 A list of objects may also be added based on the event or on 728 the value of mteTriggerTest. 730 A length of 0 indicates no additional objects." 731 DEFVAL { ''H } 732 ::= { mteTriggerEntry 13 } 734 mteTriggerEnabled OBJECT-TYPE 735 SYNTAX TruthValue 736 MAX-ACCESS read-create 737 STATUS current 738 DESCRIPTION 739 "A control to allow a trigger to be configured but not used. 740 When the value is 'false' the trigger is not sampled." 741 DEFVAL { false } 742 ::= { mteTriggerEntry 14 } 744 mteTriggerEntryStatus OBJECT-TYPE 745 SYNTAX RowStatus 746 MAX-ACCESS read-create 747 STATUS current 748 DESCRIPTION 749 "The control that allows creation and deletion of entries. 750 Once made active an entry may not be modified except to 751 delete it." 752 ::= { mteTriggerEntry 15 } 754 -- 755 -- Trigger Delta Table 756 -- 758 mteTriggerDeltaTable OBJECT-TYPE 759 SYNTAX SEQUENCE OF MteTriggerDeltaEntry 760 MAX-ACCESS not-accessible 761 STATUS current 762 DESCRIPTION 763 "A table of management event trigger information for delta 764 sampling." 765 ::= { mteTrigger 3 } 767 mteTriggerDeltaEntry OBJECT-TYPE 768 SYNTAX MteTriggerDeltaEntry 769 MAX-ACCESS not-accessible 770 STATUS current 771 DESCRIPTION 772 "Information about a single trigger's delta sampling. Entries 773 automatically exist in this this table for each mteTriggerEntry 774 that has mteTriggerSampleType set to 'deltaValue'." 775 INDEX { mteOwner, IMPLIED mteTriggerName } 776 ::= { mteTriggerDeltaTable 1 } 778 MteTriggerDeltaEntry ::= SEQUENCE { 779 mteTriggerDeltaDiscontinuityID OBJECT IDENTIFIER, 780 mteTriggerDeltaDiscontinuityIDWildcard TruthValue, 781 mteTriggerDeltaDiscontinuityIDType INTEGER 782 } 784 sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 } 786 mteTriggerDeltaDiscontinuityID OBJECT-TYPE 787 SYNTAX OBJECT IDENTIFIER 788 MAX-ACCESS read-write 789 STATUS current 790 DESCRIPTION 791 "The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or 792 DateAndTime object that indicates a discontinuity in the value 793 at mteTriggerValueID. 795 The OID may be for a leaf object (e.g. sysUpTime.0) or may 796 be wildcarded to match mteTriggerValueID. 798 This object supports normal checking for a discontinuity in a 799 counter. Note that if this object does not point to sysUpTime 800 discontinuity checking must still check sysUpTime for an overall 801 discontinuity. 803 If the object identified is not accessible the sample attempt 804 is in error, with the error code as from an SNMP request. 806 Bad object identifiers or a mismatch between truncating the 807 identifier and the value of mteDeltaDiscontinuityIDWildcard 808 result in operation as one would expect when providing the 809 wrong identifier to a Get operation. The Get will fail or get 810 the wrong object. If the value syntax of those objects is not 811 usable, that results in an error that terminates the sample 812 with a 'badType' error code." 813 DEFVAL { sysUpTimeInstance } 814 ::= { mteTriggerDeltaEntry 1 } 816 mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE 817 SYNTAX TruthValue 818 MAX-ACCESS read-write 819 STATUS current 820 DESCRIPTION 821 "Control for whether mteTriggerDeltaDiscontinuityID is to be 822 treated as fully-specified or wildcarded, with 'true' 823 indicating wildcard." 824 DEFVAL { false } 825 ::= { mteTriggerDeltaEntry 2 } 827 mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE 828 SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) } 829 MAX-ACCESS read-write 830 STATUS current 831 DESCRIPTION 832 "The value 'timeTicks' indicates the 833 mteTriggerDeltaDiscontinuityID of this row is of syntax 834 TimeTicks. The value 'timeStamp' indicates syntax TimeStamp. 835 The value 'dateAndTime' indicates syntax DateAndTime." 836 DEFVAL { timeTicks } 837 ::= { mteTriggerDeltaEntry 3 } 839 -- 840 -- Trigger Existence Table 841 -- 843 mteTriggerExistenceTable OBJECT-TYPE 844 SYNTAX SEQUENCE OF MteTriggerExistenceEntry 845 MAX-ACCESS not-accessible 846 STATUS current 847 DESCRIPTION 848 "A table of management event trigger information for existence 849 triggers." 850 ::= { mteTrigger 4 } 852 mteTriggerExistenceEntry OBJECT-TYPE 853 SYNTAX MteTriggerExistenceEntry 854 MAX-ACCESS not-accessible 855 STATUS current 856 DESCRIPTION 857 "Information about a single existence trigger. Entries 858 automatically exist in this this table for each mteTriggerEntry 859 that has 'existence' set in mteTriggerTest." 860 INDEX { mteOwner, IMPLIED mteTriggerName } 861 ::= { mteTriggerExistenceTable 1 } 863 MteTriggerExistenceEntry ::= SEQUENCE { 864 mteTriggerExistenceTest BITS, 865 mteTriggerExistenceStartup BITS, 866 mteTriggerExistenceObjectsOwner SnmpAdminString, 867 mteTriggerExistenceObjects SnmpAdminString, 868 mteTriggerExistenceEventOwner SnmpAdminString, 869 mteTriggerExistenceEvent SnmpAdminString 870 } 872 mteTriggerExistenceTest OBJECT-TYPE 873 SYNTAX BITS { present(0), absent(1), changed(2) } 874 MAX-ACCESS read-write 875 STATUS current 876 DESCRIPTION 877 "The type of existence test to perform. The trigger fires 878 when the object at mteTriggerValueID is seen to go from 879 present to absent, from absent to present, or to have it's 880 value changed, depending on which tests are selected. 882 Once the trigger has fired for either presence or absence it 883 will not fire again for that state until the object has been 884 to the other state." 885 DEFVAL { { present, absent } } 886 ::= { mteTriggerExistenceEntry 1 } 888 mteTriggerExistenceStartup OBJECT-TYPE 889 SYNTAX BITS { present(0), absent(1), changed(2) } 890 MAX-ACCESS read-write 891 STATUS current 892 DESCRIPTION 893 "Control for whether an event may be triggered when this entry 894 is first set to 'active' and the test specified by 895 mteTriggerExistenceTest is true. Setting an option causes 896 that trigger to fire when its test is true." 897 DEFVAL { { present, absent } } 898 ::= { mteTriggerExistenceEntry 2 } 900 mteTriggerExistenceObjectsOwner OBJECT-TYPE 901 SYNTAX SnmpAdminString (SIZE (0..32)) 902 MAX-ACCESS read-write 903 STATUS current 904 DESCRIPTION 905 "To go with mteTriggerExistenceObjects, the mteOwner of a 906 group of objects from mteObjectsTable." 907 DEFVAL { ''H } 908 ::= { mteTriggerExistenceEntry 3 } 910 mteTriggerExistenceObjects OBJECT-TYPE 911 SYNTAX SnmpAdminString (SIZE (0..32)) 912 MAX-ACCESS read-write 913 STATUS current 914 DESCRIPTION 915 "The mteObjectsName of a group of objects from 916 mteObjectsTable. These objects are to be added to any 917 Notification resulting from the firing of this trigger for 918 this test. 920 A list of objects may also be added based on the overall 921 trigger, the event or other settings in mteTriggerTest. 923 A length of 0 indicates no additional objects." 924 DEFVAL { ''H } 925 ::= { mteTriggerExistenceEntry 4 } 927 mteTriggerExistenceEventOwner OBJECT-TYPE 928 SYNTAX SnmpAdminString (SIZE (0..32)) 929 MAX-ACCESS read-write 930 STATUS current 931 DESCRIPTION 932 "To go with mteTriggerExistenceEvent, the mteOwner of a group 933 of objects from mteObjectsTable." 934 DEFVAL { ''H } 935 ::= { mteTriggerExistenceEntry 5 } 937 mteTriggerExistenceEvent OBJECT-TYPE 938 SYNTAX SnmpAdminString (SIZE (0..32)) 939 MAX-ACCESS read-write 940 STATUS current 941 DESCRIPTION 942 "The mteEventName of the event to invoke when mteTriggerType is 943 'existence' and this trigger fires. A length of 0 indicates no 944 event." 945 DEFVAL { ''H } 946 ::= { mteTriggerExistenceEntry 6 } 948 -- 949 -- Trigger Boolean Table 950 -- 952 mteTriggerBooleanTable OBJECT-TYPE 953 SYNTAX SEQUENCE OF MteTriggerBooleanEntry 954 MAX-ACCESS not-accessible 955 STATUS current 956 DESCRIPTION 957 "A table of management event trigger information for boolean 958 triggers." 959 ::= { mteTrigger 5 } 961 mteTriggerBooleanEntry OBJECT-TYPE 962 SYNTAX MteTriggerBooleanEntry 963 MAX-ACCESS not-accessible 964 STATUS current 965 DESCRIPTION 966 "Information about a single boolean trigger. Entries 967 automatically exist in this this table for each mteTriggerEntry 968 that has 'boolean' set in mteTriggerTest." 969 INDEX { mteOwner, IMPLIED mteTriggerName } 970 ::= { mteTriggerBooleanTable 1 } 972 MteTriggerBooleanEntry ::= SEQUENCE { 973 mteTriggerBooleanComparison INTEGER, 974 mteTriggerBooleanValue Integer32, 975 mteTriggerBooleanStartup TruthValue, 976 mteTriggerBooleanObjectsOwner SnmpAdminString, 977 mteTriggerBooleanObjects SnmpAdminString, 978 mteTriggerBooleanEventOwner SnmpAdminString, 979 mteTriggerBooleanEvent SnmpAdminString 980 } 982 mteTriggerBooleanComparison OBJECT-TYPE 983 SYNTAX INTEGER { unequal(1), equal(2), 984 less(3), lessOrEqual(4), 985 greater(5), greaterOrEqual(6) } 986 MAX-ACCESS read-write 987 STATUS current 988 DESCRIPTION 989 "The type of boolean comparison to perform. 991 The value at mteTriggerValueID is compared to 992 mteTriggerBooleanValue, so for example if 993 mteTriggerBooleanComparison is 'less' the result would be true 994 if the value at mteTriggerValueID is less than the value of 995 mteTriggerBooleanValue." 996 DEFVAL { unequal } 997 ::= { mteTriggerBooleanEntry 1 } 999 mteTriggerBooleanValue OBJECT-TYPE 1000 SYNTAX Integer32 1001 MAX-ACCESS read-write 1002 STATUS current 1003 DESCRIPTION 1004 "The value to use for the test specified by 1005 mteTriggerBooleanTest." 1006 DEFVAL { 0 } 1007 ::= { mteTriggerBooleanEntry 2 } 1009 mteTriggerBooleanStartup OBJECT-TYPE 1010 SYNTAX TruthValue 1011 MAX-ACCESS read-write 1012 STATUS current 1013 DESCRIPTION 1014 "Control for whether an event may be triggered when this entry 1015 is first set to 'active' or a new instance of the object at 1016 mteTriggerValueID is found and the test specified by 1017 mteTriggerBooleanComparison is true. In that case an event is 1018 triggered if mteTriggerBooleanStartup is 'true'." 1019 DEFVAL { true } 1020 ::= { mteTriggerBooleanEntry 3 } 1022 mteTriggerBooleanObjectsOwner OBJECT-TYPE 1023 SYNTAX SnmpAdminString (SIZE (0..32)) 1024 MAX-ACCESS read-write 1025 STATUS current 1026 DESCRIPTION 1027 "To go with mteTriggerBooleanObjects, the mteOwner of a group 1028 of objects from mteObjectsTable." 1029 DEFVAL { ''H } 1030 ::= { mteTriggerBooleanEntry 4 } 1032 mteTriggerBooleanObjects OBJECT-TYPE 1033 SYNTAX SnmpAdminString (SIZE (0..32)) 1034 MAX-ACCESS read-write 1035 STATUS current 1036 DESCRIPTION 1037 "The mteObjectsName of a group of objects from 1038 mteObjectsTable. These objects are to be added to any 1039 Notification resulting from the firing of this trigger for 1040 this test. 1042 A list of objects may also be added based on the overall 1043 trigger, the event or other settings in mteTriggerTest. 1045 A length of 0 indicates no additional objects." 1046 DEFVAL { ''H } 1047 ::= { mteTriggerBooleanEntry 5 } 1049 mteTriggerBooleanEventOwner OBJECT-TYPE 1050 SYNTAX SnmpAdminString (SIZE (0..32)) 1051 MAX-ACCESS read-write 1052 STATUS current 1053 DESCRIPTION 1054 "To go with mteTriggerBooleanEvent, the mteOwner of an event 1055 entry from mteEventTable." 1056 DEFVAL { ''H } 1057 ::= { mteTriggerBooleanEntry 6 } 1059 mteTriggerBooleanEvent OBJECT-TYPE 1060 SYNTAX SnmpAdminString (SIZE (0..32)) 1061 MAX-ACCESS read-write 1062 STATUS current 1063 DESCRIPTION 1064 "The mteEventName of the event to invoke when mteTriggerType is 1065 'boolean' and this trigger fires. A length of 0 indicates no 1066 event." 1067 DEFVAL { ''H } 1068 ::= { mteTriggerBooleanEntry 7 } 1070 -- 1071 -- Trigger Threshold Table 1072 -- 1074 mteTriggerThresholdTable OBJECT-TYPE 1075 SYNTAX SEQUENCE OF MteTriggerThresholdEntry 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "A table of management event trigger information for threshold 1080 triggers." 1081 ::= { mteTrigger 6 } 1083 mteTriggerThresholdEntry OBJECT-TYPE 1084 SYNTAX MteTriggerThresholdEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "Information about a single threshold trigger. Entries 1089 automatically exist in this table for each mteTriggerEntry 1090 that has 'threshold' set in mteTriggerTest." 1091 INDEX { mteOwner, IMPLIED mteTriggerName } 1092 ::= { mteTriggerThresholdTable 1 } 1094 MteTriggerThresholdEntry ::= SEQUENCE { 1095 mteTriggerThresholdValue Integer32, 1096 mteTriggerThresholdStartup INTEGER, 1097 mteTriggerThresholdRising Integer32, 1098 mteTriggerThresholdFalling Integer32, 1099 mteTriggerThresholdObjectsOwner SnmpAdminString, 1100 mteTriggerThresholdObjects SnmpAdminString, 1101 mteTriggerThresholdRisingEventOwner SnmpAdminString, 1102 mteTriggerThresholdRisingEvent SnmpAdminString, 1103 mteTriggerThresholdFallingEventOwner SnmpAdminString, 1104 mteTriggerThresholdFallingEvent SnmpAdminString 1105 } 1107 mteTriggerThresholdValue OBJECT-TYPE 1108 SYNTAX Integer32 1109 MAX-ACCESS read-write 1110 STATUS current 1111 DESCRIPTION 1112 "The value to use for the threshold test." 1113 DEFVAL { 0 } 1114 ::= { mteTriggerThresholdEntry 1 } 1116 mteTriggerThresholdStartup OBJECT-TYPE 1117 SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } 1118 MAX-ACCESS read-write 1119 STATUS current 1120 DESCRIPTION 1121 "The event that may be triggered when this entry is first 1122 set to 'active' and a new instance of the object at 1123 mteTriggerValueID is found. If the first sample after this 1124 instance becomes active is greater than or equal to 1125 mteTriggerThresholdRising and mteTriggerThresholdStartup is 1126 equal to 'rising' or 'risingOrFalling', then one 1127 mteTriggerThresholdRisingEvent is triggered for that instance. 1128 If the first sample after this entry becomes active is less than 1129 or equal to mteTriggerThresholdFalling and 1130 mteTriggerThresholdStartup is equal to 'falling' or 1131 'risingOrFalling', then one mteTriggerThresholdRisingEvent is 1132 triggered for that instance." 1133 DEFVAL { risingOrFalling } 1134 ::= { mteTriggerThresholdEntry 2 } 1136 mteTriggerThresholdRising OBJECT-TYPE 1137 SYNTAX Integer32 1138 MAX-ACCESS read-write 1139 STATUS current 1140 DESCRIPTION 1141 "A threshold value to check against if mteTriggerType is 1142 'threshold'. 1144 When the current sampled value is greater than or equal to 1145 this threshold, and the value at the last sampling interval 1146 was less than this threshold, one 1147 mteTriggerThresholdRisingEvent is triggered. That event is 1148 also triggered if the first sample afer this entry bcomes 1149 active is greater than or equal to this threshold and 1150 mteTriggerThresholdStartup is equal to 'rising' or 1151 'risingOrFalling'. 1153 After a rising event is generated, another such event is not 1154 triggered until the sampled value falls below this threshold and 1155 reaches mteTriggerThresholdFalling." 1156 DEFVAL { 0 } 1157 ::= { mteTriggerThresholdEntry 3 } 1159 mteTriggerThresholdFalling OBJECT-TYPE 1160 SYNTAX Integer32 1161 MAX-ACCESS read-write 1162 STATUS current 1163 DESCRIPTION 1164 "A threshold value to check against if mteTriggerType is 1165 'threshold'. 1167 When the current sampled value is less than or equal to this 1168 threshold, and the value at the last sampling interval was 1169 greater than this threshold, one 1170 mteTriggerThresholdFallingEvent is triggered. That event is 1171 also triggered if the first sample afer this entry bcomes 1172 active is less than or equal to this threshold and 1173 mteTriggerThresholdStartup is equal to 'falling' or 1174 'risingOrFalling'. 1176 After a falling event is generated, another such event is not 1177 triggered until the sampled value rises above this threshold and 1178 reaches mteTriggerThresholdRising." 1179 DEFVAL { 0 } 1180 ::= { mteTriggerThresholdEntry 4 } 1182 mteTriggerThresholdObjectsOwner OBJECT-TYPE 1183 SYNTAX SnmpAdminString (SIZE (0..32)) 1184 MAX-ACCESS read-write 1185 STATUS current 1186 DESCRIPTION 1187 "To go with mteTriggerThresholdObjects, the mteOwner of a group 1188 of objects from mteObjectsTable." 1190 DEFVAL { ''H } 1191 ::= { mteTriggerThresholdEntry 5 } 1193 mteTriggerThresholdObjects OBJECT-TYPE 1194 SYNTAX SnmpAdminString (SIZE (0..32)) 1195 MAX-ACCESS read-write 1196 STATUS current 1197 DESCRIPTION 1198 "The mteObjectsName of a group of objects from 1199 mteObjectsTable. These objects are to be added to any 1200 Notification resulting from the firing of this trigger for 1201 this test. 1203 A list of objects may also be added based on the overall 1204 trigger, the event or other settings in mteTriggerTest. 1206 A length of 0 indicates no additional objects." 1207 DEFVAL { ''H } 1208 ::= { mteTriggerThresholdEntry 6 } 1210 mteTriggerThresholdRisingEventOwner OBJECT-TYPE 1211 SYNTAX SnmpAdminString (SIZE (0..32)) 1212 MAX-ACCESS read-write 1213 STATUS current 1214 DESCRIPTION 1215 "To go with mteTriggerThresholdRisingEvent, the mteOwner of an 1216 event entry from mteEventTable." 1217 DEFVAL { ''H } 1218 ::= { mteTriggerThresholdEntry 7 } 1220 mteTriggerThresholdRisingEvent OBJECT-TYPE 1221 SYNTAX SnmpAdminString (SIZE (0..32)) 1222 MAX-ACCESS read-write 1223 STATUS current 1224 DESCRIPTION 1225 "The mteEventName of the event to invoke when mteTriggerType is 1226 'threshold' and this trigger fires based on 1227 mteTriggerThresholdRising. A length of 0 indicates no event." 1228 DEFVAL { ''H } 1229 ::= { mteTriggerThresholdEntry 8 } 1231 mteTriggerThresholdFallingEventOwner OBJECT-TYPE 1232 SYNTAX SnmpAdminString (SIZE (0..32)) 1233 MAX-ACCESS read-write 1234 STATUS current 1235 DESCRIPTION 1236 "To go with mteTriggerThresholdFallingEvent, the mteOwner of an 1237 event entry from mteEventTable." 1238 DEFVAL { ''H } 1239 ::= { mteTriggerThresholdEntry 9 } 1241 mteTriggerThresholdFallingEvent OBJECT-TYPE 1242 SYNTAX SnmpAdminString (SIZE (0..32)) 1243 MAX-ACCESS read-write 1244 STATUS current 1245 DESCRIPTION 1246 "The mteEventName of the event to invoke when mteTriggerType is 1247 'threshold' and this trigger fires based on 1248 mteTriggerThresholdFalling. A length of 0 indicates no event." 1249 DEFVAL { ''H } 1250 ::= { mteTriggerThresholdEntry 10 } 1252 -- 1253 -- Objects Table 1254 -- 1256 mteObjectsTable OBJECT-TYPE 1257 SYNTAX SEQUENCE OF MteObjectsEntry 1258 MAX-ACCESS not-accessible 1259 STATUS current 1260 DESCRIPTION 1261 "A table of objects that can be added to notifications based 1262 on the trigger, trigger test, or event, as pointed to by 1263 entries in those tables." 1264 ::= { mteObjects 1 } 1266 mteObjectsEntry OBJECT-TYPE 1267 SYNTAX MteObjectsEntry 1268 MAX-ACCESS not-accessible 1269 STATUS current 1270 DESCRIPTION 1271 "A group of objects. Applications create and delete entries 1272 using mteObjectsEntryStatus. 1274 When adding objects to a notification they are added in the 1275 lexical order of their index in this table. Those associated 1276 with a trigger come first, then trigger test, then event." 1277 INDEX { mteOwner, mteObjectsName, mteObjectsIndex } 1278 ::= { mteObjectsTable 1 } 1280 MteObjectsEntry ::= SEQUENCE { 1281 mteObjectsName SnmpAdminString, 1282 mteObjectsIndex Unsigned32, 1283 mteObjectsID OBJECT IDENTIFIER, 1284 mteObjectsIDWildcard TruthValue, 1285 mteObjectsEntryStatus RowStatus 1286 } 1288 mteObjectsName OBJECT-TYPE 1289 SYNTAX SnmpAdminString (SIZE (1..32)) 1290 MAX-ACCESS not-accessible 1291 STATUS current 1292 DESCRIPTION 1293 "A locally-unique, administratively assigned name for a group of 1294 objects." 1295 ::= { mteObjectsEntry 1 } 1297 mteObjectsIndex OBJECT-TYPE 1298 SYNTAX Unsigned32 (1..4294967295) 1299 MAX-ACCESS not-accessible 1300 STATUS current 1301 DESCRIPTION 1302 "An arbitrary small integer for the purpose of identifying 1303 individual objects within a mteObjectsName group. 1305 Objects within a group are placed in the notification in the 1306 numerical order of this index. 1308 Groups are placed in the notification in the order of the 1309 selections for overall trigger, trigger test, and event. 1310 Within trigger test they are in the same order as the 1311 numerical values of the bits defined for mteTriggerTest. 1313 Bad object identifiers or a mismatch between truncating the 1314 identifier and the value of mteDeltaDiscontinuityIDWildcard 1315 result in operation as one would expect when providing the 1316 wrong identifier to a Get operation. The Get will fail or get 1317 the wrong object. If the object is not available it is omitted 1318 from the notification." 1319 ::= { mteObjectsEntry 2 } 1321 mteObjectsID OBJECT-TYPE 1322 SYNTAX OBJECT IDENTIFIER 1323 MAX-ACCESS read-create 1324 STATUS current 1325 DESCRIPTION 1326 "The object identifier of a MIB object to add to a 1327 Notification that results from the firing of a trigger. 1329 This may be wildcarded by truncating all or part of the 1330 instance portion, in which case the instance portion of the 1331 OID for obtaining this object will be the same as that used 1332 in obtaining the mteTriggerValueID that fired. If such 1333 wildcarding is applied, mteObjectsIDWildcard must be 1334 'true' and if not it must be 'false'. 1336 Each instance that fills the wildcard is independent of any 1337 additional instances, that is, wildcarded objects operate 1338 as if there were a separate table entry for each instance 1339 that fills the wildcard without having to actually predict 1340 all possible instances ahead of time." 1341 DEFVAL { zeroDotZero } 1342 ::= { mteObjectsEntry 3 } 1344 mteObjectsIDWildcard OBJECT-TYPE 1345 SYNTAX TruthValue 1346 MAX-ACCESS read-create 1347 STATUS current 1348 DESCRIPTION 1349 "Control for whether mteObjectsID is to be treated as 1350 fully-specified or wildcarded, with 'true' indicating wildcard." 1351 DEFVAL { false } 1352 ::= { mteObjectsEntry 4 } 1354 mteObjectsEntryStatus OBJECT-TYPE 1355 SYNTAX RowStatus 1356 MAX-ACCESS read-create 1357 STATUS current 1358 DESCRIPTION 1359 "The control that allows creation and deletion of entries. 1360 Once made active an entry may not be modified except to 1361 delete it." 1362 ::= { mteObjectsEntry 5 } 1364 -- 1365 -- Event Section 1366 -- 1368 -- Counters 1369 mteEventFailures OBJECT-TYPE 1370 SYNTAX Counter32 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "The number of times an attempt to invoke an event 1375 has failed. This counts individually for each 1376 attempt in a group of targets or each attempt for a 1377 wildcarded trigger object." 1378 ::= { mteEvent 1 } 1380 -- 1381 -- Event Table 1382 -- 1384 mteEventTable OBJECT-TYPE 1385 SYNTAX SEQUENCE OF MteEventEntry 1386 MAX-ACCESS not-accessible 1387 STATUS current 1388 DESCRIPTION 1389 "A table of management event action information." 1390 ::= { mteEvent 2 } 1392 mteEventEntry OBJECT-TYPE 1393 SYNTAX MteEventEntry 1394 MAX-ACCESS not-accessible 1395 STATUS current 1396 DESCRIPTION 1397 "Information about a single event. Applications create and 1398 delete entries using mteEventEntryStatus." 1399 INDEX { mteOwner, IMPLIED mteEventName } 1400 ::= { mteEventTable 1 } 1402 MteEventEntry ::= SEQUENCE { 1403 mteEventName SnmpAdminString, 1404 mteEventComment SnmpAdminString, 1405 mteEventActions BITS, 1406 mteEventEnabled TruthValue, 1407 mteEventEntryStatus RowStatus 1408 } 1410 mteEventName OBJECT-TYPE 1411 SYNTAX SnmpAdminString (SIZE (1..32)) 1412 MAX-ACCESS not-accessible 1413 STATUS current 1414 DESCRIPTION 1415 "A locally-unique, administratively assigned name for the 1416 event." 1417 ::= { mteEventEntry 1 } 1419 mteEventComment OBJECT-TYPE 1420 SYNTAX SnmpAdminString 1421 MAX-ACCESS read-create 1422 STATUS current 1423 DESCRIPTION 1424 "A description of the event's function and use." 1425 DEFVAL { ''H } 1426 ::= { mteEventEntry 2 } 1428 mteEventActions OBJECT-TYPE 1429 SYNTAX BITS { notification(0), set(1) } 1430 MAX-ACCESS read-create 1431 STATUS current 1432 DESCRIPTION 1433 "The actions to perform when this event occurs. 1435 For 'notification', Traps and/or Informs are sent according 1436 to the configuration in the SNMP Notification MIB. 1438 For 'set', an SNMP Set operation is performed according to 1439 control values in this entry." 1440 DEFVAL { '0'H } -- No bits set. 1441 ::= { mteEventEntry 3 } 1443 mteEventEnabled OBJECT-TYPE 1444 SYNTAX TruthValue 1445 MAX-ACCESS read-create 1446 STATUS current 1447 DESCRIPTION 1448 "A control to allow an event to be configured but not used. 1449 When the value is 'false' the event does not execute even if 1450 triggered." 1451 DEFVAL { false } 1452 ::= { mteEventEntry 4 } 1454 mteEventEntryStatus OBJECT-TYPE 1455 SYNTAX RowStatus 1456 MAX-ACCESS read-create 1457 STATUS current 1458 DESCRIPTION 1459 "The control that allows creation and deletion of entries. 1460 Once made active an entry may not be modified except to 1461 delete it." 1462 ::= { mteEventEntry 5 } 1464 -- 1465 -- Event Notification Table 1466 -- 1468 mteEventNotificationTable OBJECT-TYPE 1469 SYNTAX SEQUENCE OF MteEventNotificationEntry 1470 MAX-ACCESS not-accessible 1471 STATUS current 1472 DESCRIPTION 1473 "A table of management event action notification information." 1474 ::= { mteEvent 3 } 1476 mteEventNotificationEntry OBJECT-TYPE 1477 SYNTAX MteEventNotificationEntry 1478 MAX-ACCESS not-accessible 1479 STATUS current 1480 DESCRIPTION 1481 "Information about a single event's notification. Entries 1482 automatically exist in this this table for each mteTriggerEntry 1483 that has 'notification' set in mteEventAction." 1484 INDEX { mteOwner, IMPLIED mteTriggerName } 1485 ::= { mteEventNotificationTable 1 } 1487 MteEventNotificationEntry ::= SEQUENCE { 1488 mteEventNotification OBJECT IDENTIFIER, 1489 mteEventNotificationObjectsOwner SnmpAdminString, 1490 mteEventNotificationObjects SnmpAdminString 1491 } 1493 mteEventNotification OBJECT-TYPE 1494 SYNTAX OBJECT IDENTIFIER 1495 MAX-ACCESS read-write 1496 STATUS current 1497 DESCRIPTION 1498 "The object identifier from the NOTIFICATION-TYPE for the 1499 notification to use if metEventActions has 'notification' set." 1500 DEFVAL { zeroDotZero } 1501 ::= { mteEventNotificationEntry 1 } 1503 mteEventNotificationObjectsOwner OBJECT-TYPE 1504 SYNTAX SnmpAdminString (SIZE (0..32)) 1505 MAX-ACCESS read-write 1506 STATUS current 1507 DESCRIPTION 1508 "To go with mteEventNotificationObjects, the mteOwner of a 1509 group of objects from mteObjectsTable." 1510 DEFVAL { ''H } 1511 ::= { mteEventNotificationEntry 2 } 1513 mteEventNotificationObjects OBJECT-TYPE 1514 SYNTAX SnmpAdminString (SIZE (0..32)) 1515 MAX-ACCESS read-write 1516 STATUS current 1517 DESCRIPTION 1518 "The mteObjectsName of a group of objects from 1519 mteObjectsTable if mteEventActions has 'notification' set. 1520 These objects are to be added to any Notification generated by 1521 this event. 1523 Objects may also be added based on the trigger that stimulated 1524 the event. 1526 A length of 0 indicates no additional objects." 1527 DEFVAL { ''H } 1528 ::= { mteEventNotificationEntry 3 } 1530 -- 1531 -- Event Set Table 1532 -- 1534 mteEventSetTable OBJECT-TYPE 1535 SYNTAX SEQUENCE OF MteEventSetEntry 1536 MAX-ACCESS not-accessible 1537 STATUS current 1538 DESCRIPTION 1539 "A table of management event action information." 1540 ::= { mteEvent 4 } 1542 mteEventSetEntry OBJECT-TYPE 1543 SYNTAX MteEventSetEntry 1544 MAX-ACCESS not-accessible 1545 STATUS current 1546 DESCRIPTION 1547 "Information about a single event's set option. Entries 1548 automatically exist in this this table for each mteTriggerEntry 1549 that has 'set' set in mteEventAction." 1550 INDEX { mteOwner, IMPLIED mteTriggerName } 1551 ::= { mteEventSetTable 1 } 1553 MteEventSetEntry ::= SEQUENCE { 1554 mteEventSetObject OBJECT IDENTIFIER, 1555 mteEventSetObjectWildcard TruthValue, 1556 mteEventSetValue Integer32, 1557 mteEventSetTargetTag SnmpTagValue, 1558 mteEventSetContextName SnmpAdminString, 1559 mteEventSetContextNameWildcard TruthValue 1560 } 1562 mteEventSetObject OBJECT-TYPE 1563 SYNTAX OBJECT IDENTIFIER 1564 MAX-ACCESS read-write 1565 STATUS current 1566 DESCRIPTION 1567 "The object identifier from the MIB object to set if 1568 mteEventActions has 'set' set. 1570 This object identifier may be wildcarded by leaving 1571 sub-identifiers off the end, in which case 1572 nteEventSetObjectWildCard must be 'true'. 1574 If mteEventSetObject is wildcarded the instance used to set the 1575 object to which it points is the same as the instance from the 1576 value of mteTriggerValueID that triggered the event. 1578 Each instance that fills the wildcard is independent of any 1579 additional instances, that is, wildcarded objects operate 1580 as if there were a separate table entry for each instance 1581 that fills the wildcard without having to actually predict 1582 all possible instances ahead of time. 1584 Bad object identifiers or a mismatch between truncating the 1585 identifier and the value of mteSetObjectWildcard 1586 result in operation as one would expect when providing the 1587 wrong identifier to a Set operation. The Set will fail or set 1588 the wrong object. If the value syntax of the destination 1589 object is not correct, the Set fails with the normal SNMP 1590 error code." 1591 DEFVAL { zeroDotZero } 1592 ::= { mteEventSetEntry 1 } 1594 mteEventSetObjectWildcard OBJECT-TYPE 1595 SYNTAX TruthValue 1596 MAX-ACCESS read-write 1597 STATUS current 1598 DESCRIPTION 1599 "Control over whether mteEventSetObject is to be treated as 1600 fully-specified or wildcarded, with 'true' indicating wildcard 1601 if mteEventActions has 'set' set." 1602 DEFVAL { false } 1603 ::= { mteEventSetEntry 2 } 1605 mteEventSetValue OBJECT-TYPE 1606 SYNTAX Integer32 1607 MAX-ACCESS read-write 1608 STATUS current 1609 DESCRIPTION 1610 "The value to which to set the object at mteEventSetObject 1611 if mteEventActions has 'set' set." 1612 DEFVAL { 0 } 1613 ::= { mteEventSetEntry 3 } 1615 mteEventSetTargetTag OBJECT-TYPE 1616 SYNTAX SnmpTagValue 1617 MAX-ACCESS read-write 1618 STATUS current 1619 DESCRIPTION 1620 "The tag for the target(s) at which to set the object at 1621 mteEventSetObject to mteEventSetValue if mteEventActions 1622 has 'set' set. 1624 Systems limited to self management may not accept a non-zero 1625 length for the value of this object. 1627 A length of 0 indicates the local system. In this case, 1628 access to the objects indicated by mteEventSetObject is under 1629 the security credentials of the requester that set 1630 mteTriggerEntryStatus to 'active'. Those credentials are the 1631 input parameters for isAccessAllowed from the Architecture for 1632 Describing SNMP Management Frameworks. 1634 Otherwise access rights are checked according to the security 1635 parameters resulting from the tag." 1636 DEFVAL { ''H } 1637 ::= { mteEventSetEntry 4 } 1639 mteEventSetContextName OBJECT-TYPE 1640 SYNTAX SnmpAdminString 1641 MAX-ACCESS read-write 1642 STATUS current 1643 DESCRIPTION 1644 "The management context in which to set mteEventObjectID. 1645 if mteEventActions has 'set' set. 1647 This may be wildcarded by leaving characters off the end. To 1648 indicate such wildcarding mteEventSetContextNameWildcard must 1649 be 'true'. 1651 If this context name is wildcarded the value used to complete 1652 the wildcarding of mteTriggerContextName will be appended." 1653 DEFVAL { ''H } 1654 ::= { mteEventSetEntry 5 } 1656 mteEventSetContextNameWildcard OBJECT-TYPE 1657 SYNTAX TruthValue 1658 MAX-ACCESS read-write 1659 STATUS current 1660 DESCRIPTION 1661 "Control for whether mteEventSetContextName is to be treated as 1662 fully-specified or wildcarded, with 'true' indicating wildcard 1663 if mteEventActions has 'set' set." 1664 DEFVAL { false } 1665 ::= { mteEventSetEntry 6 } 1667 -- 1668 -- Notifications 1669 -- 1671 dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::= { dismanEventMIB 2 } 1672 dismanEventMIBNotifications OBJECT IDENTIFIER ::= 1673 { dismanEventMIBNotificationPrefix 0 } 1674 dismanEventMIBNotificationObjects OBJECT IDENTIFIER 1675 ::= { dismanEventMIBNotificationPrefix 1 } 1677 -- 1678 -- Notification Objects 1679 -- 1680 mteHotTrigger OBJECT-TYPE 1681 SYNTAX SnmpAdminString 1682 MAX-ACCESS accessible-for-notify 1683 STATUS current 1684 DESCRIPTION 1685 "The name of the trigger causing the notification." 1686 ::= { dismanEventMIBNotificationObjects 1 } 1688 mteHotTargetName OBJECT-TYPE 1689 SYNTAX SnmpAdminString 1690 MAX-ACCESS accessible-for-notify 1691 STATUS current 1692 DESCRIPTION 1693 "The SNMP Target MIB's snmpTargetAddrName related to the 1694 notification." 1695 ::= { dismanEventMIBNotificationObjects 2 } 1697 mteHotContextName OBJECT-TYPE 1698 SYNTAX SnmpAdminString 1699 MAX-ACCESS accessible-for-notify 1700 STATUS current 1701 DESCRIPTION 1702 "The context name related to the notification. This must be as 1703 fully-qualified as possible, including filling in wildcard 1704 information determined in processing." 1705 ::= { dismanEventMIBNotificationObjects 3 } 1707 mteHotOID OBJECT-TYPE 1708 SYNTAX OBJECT IDENTIFIER 1709 MAX-ACCESS accessible-for-notify 1710 STATUS current 1711 DESCRIPTION 1712 "The object identifier of the destination object related to the 1713 notification. This must be as fully-qualified as possible, 1714 inluding filling in wildcard informaation determined in 1715 processing. 1717 For a trigger-related notification this is from 1718 mteTriggerValueID. 1720 For a set failure this is from mteEventSetObject." 1721 ::= { dismanEventMIBNotificationObjects 4 } 1723 mteHotValue OBJECT-TYPE 1724 SYNTAX Integer32 1725 MAX-ACCESS accessible-for-notify 1726 STATUS current 1727 DESCRIPTION 1728 "The value of the object at mteTriggerValueID when a 1729 trigger fired." 1730 ::= { dismanEventMIBNotificationObjects 5 } 1732 mteFailedReason OBJECT-TYPE 1733 SYNTAX FailureReason 1734 MAX-ACCESS accessible-for-notify 1735 STATUS current 1736 DESCRIPTION 1737 "The reason for the failure of an attempt to check for a 1738 trigger condition or set an object in response to an event." 1739 ::= { dismanEventMIBNotificationObjects 6 } 1741 -- 1742 -- Notifications 1743 -- 1745 mteTriggerFired NOTIFICATION-TYPE 1746 OBJECTS { mteHotTrigger, 1747 mteHotTargetName, 1748 mteHotContextName, 1749 mteHotOID, 1750 mteHotValue } 1751 STATUS current 1752 DESCRIPTION 1753 "Notification that the trigger indicated by the object 1754 instances has fired, for triggers with mteTriggerType 1755 'boolean' or 'existence'." 1756 ::= { dismanEventMIBNotifications 1 } 1758 mteTriggerRising NOTIFICATION-TYPE 1759 OBJECTS { mteHotTrigger, 1760 mteHotTargetName, 1761 mteHotContextName, 1762 mteHotOID, 1763 mteHotValue } 1764 STATUS current 1765 DESCRIPTION 1766 "Notification that the rising threshold was met for triggers 1767 with mteTriggerType 'threshold'." 1768 ::= { dismanEventMIBNotifications 2 } 1770 mteTriggerFalling NOTIFICATION-TYPE 1771 OBJECTS { mteHotTrigger, 1772 mteHotTargetName, 1773 mteHotContextName, 1774 mteHotOID, 1775 mteHotValue } 1776 STATUS current 1777 DESCRIPTION 1778 "Notification that the falling threshold was met for triggers 1779 with mteTriggerType 'threshold'." 1780 ::= { dismanEventMIBNotifications 3 } 1782 mteTriggerFailure NOTIFICATION-TYPE 1783 OBJECTS { mteHotTrigger, 1784 mteHotTargetName, 1785 mteHotContextName, 1786 mteHotOID, 1787 mteFailedReason } 1788 STATUS current 1789 DESCRIPTION 1790 "Notification that an attempt to check a trigger has failed. 1792 The network manager must enable this notification only with 1793 a certain fear and trembling, as it can easily crowd out more 1794 important information. It should be used only to help diagnose 1795 a problem that has appeared in the error counters and can not 1796 be found otherwise." 1797 ::= { dismanEventMIBNotifications 4 } 1799 mteEventSetFailure NOTIFICATION-TYPE 1800 OBJECTS { mteHotTrigger, 1801 mteHotTargetName, 1802 mteHotContextName, 1803 mteHotOID, 1804 mteFailedReason } 1805 STATUS current 1806 DESCRIPTION 1807 "Notification that an attempt to do a set in response to an 1808 event has failed. 1810 The network manager must enable this notification only with 1811 a certain fear and trembling, as it can easily crowd out more 1812 important information. It should be used only to help diagnose 1813 a problem that has appeared in the error counters and can not 1814 be found otherwise." 1816 ::= { dismanEventMIBNotifications 5 } 1818 -- 1819 -- Conformance 1820 -- 1822 dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 } 1823 dismanEventMIBCompliances OBJECT IDENTIFIER ::= { dismanEventMIBConformance 1824 1 } 1825 dismanEventMIBGroups OBJECT IDENTIFIER ::= { dismanEventMIBConformance 1826 2 } 1828 -- Compliance 1830 dismanEventMIBCompliance MODULE-COMPLIANCE 1831 STATUS current 1832 DESCRIPTION 1833 "The compliance statement for entities which implement 1834 the Event MIB." 1835 MODULE -- this module 1836 MANDATORY-GROUPS { 1837 dismanEventResourceGroup, 1838 dismanEventTriggerGroup, 1839 dismanEventObjectsGroup, 1840 dismanEventEventGroup, 1841 dismanEventNotificationObjectGroup, 1842 dismanEventNotificationGroup 1843 } 1845 OBJECT mteTriggerTargetTag 1846 MIN-ACCESS read-only 1847 DESCRIPTION 1848 "Write access is not required, thus limiting 1849 monitoring to the local system or preconfigured 1850 remote systems." 1852 OBJECT mteEventSetTargetTag 1853 MIN-ACCESS read-only 1854 DESCRIPTION 1855 "Write access is not required, thus limiting 1856 setting to the local system or preconfigured 1857 remote systems." 1859 OBJECT mteTriggerValueIDWildcard 1860 MIN-ACCESS read-only 1861 DESCRIPTION 1862 "Write access is not required, thus allowing 1863 the system not to implement wildcarding." 1865 OBJECT mteTriggerContextNameWildcard 1866 MIN-ACCESS read-only 1867 DESCRIPTION 1868 "Write access is not required, thus allowing 1869 the system not to implement wildcarding." 1871 OBJECT mteObjectsIDWildcard 1872 MIN-ACCESS read-only 1873 DESCRIPTION 1874 "Write access is not required, thus allowing 1875 the system not to implement wildcarding." 1877 OBJECT mteEventSetContextNameWildcard 1878 MIN-ACCESS read-only 1879 DESCRIPTION 1880 "Write access is not required, thus allowing 1881 the system not to implement wildcarding." 1883 ::= { dismanEventMIBCompliances 1 } 1885 -- Units of Conformance 1887 dismanEventResourceGroup OBJECT-GROUP 1888 OBJECTS { 1889 mteResourceSampleMinimum, 1890 mteResourceSampleInstanceMaximum, 1891 mteResourceSampleInstances, 1892 mteResourceSampleInstancesHigh, 1893 mteResourceSampleInstanceLacks 1894 } 1895 STATUS current 1896 DESCRIPTION 1897 "Event resource status and control objects." 1898 ::= { dismanEventMIBGroups 1 } 1900 dismanEventTriggerGroup OBJECT-GROUP 1901 OBJECTS { 1902 mteTriggerFailures, 1903 mteTriggerComment, 1904 mteTriggerTest, 1905 mteTriggerSampleType, 1906 mteTriggerValueID, 1907 mteTriggerValueIDWildcard, 1908 mteTriggerTargetTag, 1909 mteTriggerContextName, 1910 mteTriggerContextNameWildcard, 1911 mteTriggerFrequency, 1912 mteTriggerObjectsOwner, 1913 mteTriggerObjects, 1914 mteTriggerEnabled, 1915 mteTriggerEntryStatus, 1917 mteTriggerDeltaDiscontinuityID, 1918 mteTriggerDeltaDiscontinuityIDWildcard, 1919 mteTriggerDeltaDiscontinuityIDType, 1921 mteTriggerExistenceTest, 1922 mteTriggerExistenceStartup, 1923 mteTriggerExistenceObjectsOwner, 1924 mteTriggerExistenceObjects, 1925 mteTriggerExistenceEventOwner, 1926 mteTriggerExistenceEvent, 1928 mteTriggerBooleanComparison, 1929 mteTriggerBooleanValue, 1930 mteTriggerBooleanStartup, 1931 mteTriggerBooleanObjectsOwner, 1932 mteTriggerBooleanObjects, 1933 mteTriggerBooleanEventOwner, 1934 mteTriggerBooleanEvent, 1936 mteTriggerThresholdValue, 1937 mteTriggerThresholdStartup, 1938 mteTriggerThresholdObjectsOwner, 1939 mteTriggerThresholdObjects, 1940 mteTriggerThresholdRising, 1941 mteTriggerThresholdFalling, 1942 mteTriggerThresholdRisingEventOwner, 1943 mteTriggerThresholdRisingEvent, 1944 mteTriggerThresholdFallingEventOwner, 1945 mteTriggerThresholdFallingEvent 1946 } 1947 STATUS current 1948 DESCRIPTION 1949 "Event triggers." 1950 ::= { dismanEventMIBGroups 2 } 1952 dismanEventObjectsGroup OBJECT-GROUP 1953 OBJECTS { 1954 mteObjectsID, 1955 mteObjectsIDWildcard, 1956 mteObjectsEntryStatus 1957 } 1958 STATUS current 1959 DESCRIPTION 1960 "Supplemental objects." 1961 ::= { dismanEventMIBGroups 3 } 1963 dismanEventEventGroup OBJECT-GROUP 1964 OBJECTS { 1965 mteEventFailures, 1967 mteEventComment, 1968 mteEventActions, 1969 mteEventEnabled, 1970 mteEventEntryStatus, 1972 mteEventNotification, 1973 mteEventNotificationObjectsOwner, 1974 mteEventNotificationObjects, 1976 mteEventSetObject, 1977 mteEventSetObjectWildcard, 1978 mteEventSetValue, 1979 mteEventSetTargetTag, 1980 mteEventSetContextName, 1981 mteEventSetContextNameWildcard 1982 } 1983 STATUS current 1984 DESCRIPTION 1985 "Events." 1986 ::= { dismanEventMIBGroups 4 } 1988 dismanEventNotificationObjectGroup OBJECT-GROUP 1989 OBJECTS { 1990 mteHotTrigger, 1991 mteHotTargetName, 1992 mteHotContextName, 1993 mteHotOID, 1994 mteHotValue, 1995 mteFailedReason 1996 } 1997 STATUS current 1998 DESCRIPTION 1999 "Notification objects." 2000 ::= { dismanEventMIBGroups 5 } 2002 dismanEventNotificationGroup NOTIFICATION-GROUP 2003 NOTIFICATIONS { 2004 mteTriggerFired, 2005 mteTriggerRising, 2006 mteTriggerFalling, 2007 mteTriggerFailure, 2008 mteEventSetFailure 2009 } 2010 STATUS current 2011 DESCRIPTION 2012 "Notifications." 2013 ::= { dismanEventMIBGroups 6 } 2015 END 2016 9. Intellectual Property 2018 The IETF takes no position regarding the validity or scope of any 2019 intellectual property or other rights that might be claimed to pertain 2020 to the implementation or use of the technology described in this 2021 document or the extent to which any license under such rights might or 2022 might not be available; neither does it represent that it has made any 2023 effort to identify any such rights. Information on the IETF's 2024 procedures with respect to rights in standards-track and standards- 2025 related documentation can be found in BCP-11. Copies of claims of 2026 rights made available for publication and any assurances of licenses to 2027 be made available, or the result of an attempt made to obtain a general 2028 license or permission for the use of such proprietary rights by 2029 implementors or users of this specification can be obtained from the 2030 IETF Secretariat. 2032 The IETF invites any interested party to bring to its attention any 2033 copyrights, patents or patent applications, or other proprietary rights 2034 which may cover technology that may be required to practice this 2035 standard. Please address the information to the IETF Executive 2036 Director. 2038 10. Acknowledgements 2040 This MIB contains considerable contributions from the RMON MIB, the 2041 Distributed Management Design Team (Andy Bierman, Maria Greene, Bob 2042 Stewart, and Steve Waldbusser), the Distributed Management Working 2043 Group, and colleagues at Cisco. 2045 11. References 2047 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 2048 for Describing SNMP Management Frameworks", RFC 2571, April 2049 1999 2051 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 2052 of Management Information for TCP/IP-based Internets", STD 2053 16, RFC 1155, May 1990 2055 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 2056 16, RFC 1212, March 1991 2058 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 2059 SNMP", RFC 1215, March 1991 2061 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2062 Rose, M., and S. Waldbusser, "Structure of Management 2063 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 2065 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2066 Rose, M., and S. Waldbusser, "Textual Conventions for 2067 SMIv2", STD 58, RFC 2579, April 1999 2069 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2070 Rose, M., and S. Waldbusser, "Conformance Statements for 2071 SMIv2", STD 58, RFC 2580, April 1999 2073 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2074 Network Management Protocol", STD 15, RFC 1157, May 1990. 2076 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2077 "Introduction to Community-based SNMPv2", RFC 1901, January 2078 1996. 2080 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2081 "Transport Mappings for Version 2 of the Simple Network 2082 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2084 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2085 Processing and Dispatching for the Simple Network Management 2086 Protocol (SNMP)", RFC 2572, April 1999 2088 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 2089 (USM) for version 3 of the Simple Network Management 2090 Protocol (SNMPv3)", RFC 2574, April 1999 2092 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2093 "Protocol Operations for Version 2 of the Simple Network 2094 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2096 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 2097 RFC 2573, April 1999 2099 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2100 Access Control Model (VACM) for the Simple Network 2101 Management Protocol (SNMP)", RFC 2575, April 1999 2103 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2104 "Introduction to Version 3 of the Internet-standard Network 2105 Management Framework", RFC 2570, April 1999 2107 [RFC1903] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 2108 "Coexistence between Version 1 and version 2 of the 2109 Internet-standard Network Management Framework", RFC 1903, 2110 January 1996. 2112 [RFCEventMIB] 2113 Stewart, B., "Event MIB", RFC ????, ?Month? 1999. 2115 [RFC1757] 2116 Waldbusser, S., "Remote Network Monitoring Management Information 2117 Base", RFC 1757, February 1995. 2119 [RFC1451] 2120 Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to- 2121 Manager Management Information Base", RFC 1451, April 1993. 2123 [RFCExpressionMIB] 2124 Stewart, B., "Expression MIB", RFC ????, ?Month? 1999. 2126 [RFCNotificationLogMIB] 2127 Stewart, B., "Notification Log MIB", RFC ????, ?Month? 1999. 2129 12. Security Considerations 2131 Security issues are discussed in the Security section and in the 2132 DESCRIPTION clauses of relevant objects. 2134 13. Author's Address 2136 Bob Stewart 2137 Cisco Systems, Inc. 2138 170 West Tasman Drive 2139 San Jose, CA 95134-1706 2140 U.S.A. 2142 14. Editor's Address 2144 Ramanathan Kavasseri 2145 Cisco Systems, Inc. 2146 170 West Tasman Drive 2147 San Jose, CA 95134-1706 2148 U.S.A. 2150 Phone: +1 408 527 2446 2151 Email: ramk@cisco.com 2153 15. Full Copyright Statement 2155 Copyright (C) The Internet Society (1999). All Rights Reserved. 2157 This document and translations of it may be copied and furnished to 2158 others, and derivative works that comment on or otherwise explain it or 2159 assist in its implementation may be prepared, copied, published and 2160 distributed, in whole or in part, without restriction of any kind, 2161 provided that the above copyright notice and this paragraph are included 2162 on all such copies and derivative works. However, this document itself 2163 may not be modified in any way, such as by removing the copyright notice 2164 or references to the Internet Society or other Internet organizations, 2165 except as needed for the purpose of developing Internet standards in 2166 which case the procedures for copyrights defined in the Internet 2167 Standards process must be followed, or as required to translate it into 2168 languages other than English. 2170 The limited permissions granted above are perpetual and will not be 2171 revoked by the Internet Society or its successors or assigns. 2173 This document and the information contained herein is provided on an "AS 2174 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2175 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2176 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 2177 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 2178 FITNESS FOR A PARTICULAR PURPOSE. 2180 Table of Contents 2182 1 Abstract ........................................................ 2 2183 2 The SNMP Management Framework ................................... 2 2184 3 Overview ........................................................ 4 2185 4 Relationship to Other MIBs ...................................... 4 2186 5 MIB Sections .................................................... 4 2187 6 Operation ....................................................... 5 2188 7 Security ........................................................ 6 2189 8 Definitions ..................................................... 8 2190 9 Intellectual Property ........................................... 48 2191 10 Acknowledgements ............................................... 49 2192 11 References ..................................................... 50 2193 12 Security Considerations ........................................ 52 2194 13 Author's Address ............................................... 52 2195 14 Editor's Address ............................................... 52 2196 15 Full Copyright Statement ....................................... 53