idnits 2.17.1 draft-ietf-disman-event-mib-09.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? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 58 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 59 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 10 instances of too long lines in the document, the longest one being 7 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 400 has weird spacing: '...achable can't...' == Line 2359 has weird spacing: '...for the purpo...' -- 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 (6 January 2000) is 8877 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) == Missing Reference: 'SNMP-TARGET-MIB' is mentioned on line 276, but not defined == Unused Reference: 'RFC1903' is defined on line 2301, but no explicit reference was found in the text == Unused Reference: 'RFCEventMIB' is defined on line 2306, but no explicit reference was found in the text == Unused Reference: 'RFCNotificationLogMIB' is defined on line 2320, 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: 20 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 6 January 2000 3 Event MIB 5 6 January 2000 7 draft-ietf-disman-event-mib-09.txt 9 Bob Stewart 10 Cisco Systems, Inc. 12 Ramanathan R. Kavasseri 13 Cisco Systems, Inc. 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance with all 18 provisions of Section 10 of RFC2026. 20 Internet-Drafts are working documents of the Internet Engineering Task 21 Force (IETF), its areas, and its working groups. Note that other groups 22 may also distribute working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet- Drafts as reference material 27 or to cite them other than as ``work in progress.'' 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 Distribution of this document is unlimited. Please send comments to the 36 Distributed Management Working Group, . 38 Copyright Notice 40 Copyright (C) The Internet Society (2000). All Rights Reserved. 42 1. Abstract 44 This memo defines an experimental portion of the Management Information 45 Base (MIB) for use with network management protocols in the Internet 46 community. In particular, it describes managed objects that can be used 47 to manage and monitor MIB objects and take action through events. 49 The Event MIB provides the ability to monitor MIB objects on the local 50 system or on a remote system and take simple action when a trigger 51 condition is met. 53 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 54 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 55 document are to be interpreted as described in RFC 2119. 57 2. The SNMP Management Framework 59 The SNMP Management Framework presently consists of five major 60 components: 62 o An overall architecture, described in RFC 2571 [RFC2571]. 64 o Mechanisms for describing and naming objects and events for the 65 purpose of management. The first version of this Structure of 66 Management Information (SMI) is called SMIv1 and described in 67 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 68 1215 [RFC1215]. The second version, called SMIv2, is described 69 in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 70 [RFC2580]. 72 o Message protocols for transferring management information. The 73 first version of the SNMP message protocol is called SNMPv1 and 74 described in STD 15, RFC 1157 [RFC1157]. A second version of the 75 SNMP message protocol, which is not an Internet standards track 76 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 77 and RFC 1906 [RFC1906]. The third version of the message 78 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 79 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 81 o Protocol operations for accessing management information. The 82 first set of protocol operations and associated PDU formats is 83 described in STD 15, RFC 1157 [RFC1157]. A second set of 84 protocol operations and associated PDU formats is described in 85 RFC 1905 [RFC1905]. 87 o A set of fundamental applications described in RFC 2573 88 [RFC2573] and the view-based access control mechanism described 89 in RFC 2575 [RFC2575]. 91 A more detailed introduction to the current SNMP Management Framework 92 can be found in RFC 2570 [RFC2570]. 94 Managed objects are accessed via a virtual information store, termed 95 the Management Information Base or MIB. Objects in the MIB are 96 defined using the mechanisms defined in the SMI. 98 This memo specifies a MIB module that is compliant to the SMIv2. A 99 MIB conforming to the SMIv1 can be produced through the appropriate 100 translations. The resulting translated MIB must be semantically 101 equivalent, except where objects or events are omitted because no 102 translation is possible (use of Counter64). Some machine readable 103 information in SMIv2 will be converted into textual descriptions in 104 SMIv1 during the translation process. However, this loss of machine 105 readable information is not considered to change the semantics of the 106 MIB. It may not be possible to meaningfully monitor Counter64 objects 107 using an SMIv1 version of the MIB. 109 3. Overview 111 With network sizes well beyond the ability of people to manage them 112 directly, automated, distributed management is vital. An important 113 aspect of such management is the ability of a system to monitor itself 114 or for some other system to monitor it. 116 The Event MIB provides the ability to monitor MIB objects on the local 117 system or on a remote system and take simple action when a trigger 118 condition is met. 120 The MIB is intended to suit either a relatively powerful manager or mid- 121 level manager, as well as a somewhat more limited self-managing system. 123 4. Relationship to Other MIBs 125 The Event MIB is based on extensive experience with the RMON MIB 126 [RFC1757] and provides a superset of the capabilities of the RMON alarm 127 and event groups. Conceptually, the key extension is the ability to 128 allow alarms to be generated for MIB objects that are on another network 129 element. The Event MIB calls "triggers" what the RMON MIB called 130 "alarms," but the concepts are the same. Event MIB triggers maintain 131 the RMON handling of thresholds and add the concept of booleans. Event 132 MIB events maintain the RMON concept of sending an SNMP notification in 133 response to a trigger and add the concept of setting a MIB object. 135 The Event MIB is the successor and update to SNMPv2's Manager-to-Manager 136 MIB [RFC1451] which was declared Historic pending this work. 138 The Event MIB depends on the services of the SNMPv3 Management Target 139 and Notification MIBs [RFC2573]. 141 The Event MIB is nicely complemented by the Distributed Management 142 Expression MIB [RFCExpressionMIB], which is the expected source of 143 boolean objects to monitor. Note that there is considerable overlap 144 between the wildcard and delta sample capabilities of the Event and 145 Expression MIBs. A carefully-planned implementation might well use 146 common code to provide the overlapping functions. 148 5. MIB Sections 150 The MIB has four sections: triggers, objects, events, and notifications. 151 Triggers define the conditions that lead to events. Events may cause 152 notifications. 154 The trigger table lists what objects are to be monitored and how and 155 relates each trigger to an event. It has supplementary, companion 156 tables for additional objects that depend on the type of test done for 157 the trigger. 159 The objects table lists objects that can be added to notifications based 160 on the trigger, the trigger test type, or the event that resulted in the 161 notification. 163 The event table defines what happens when an event is triggered: sending 164 a notification, setting a MIB object or both. It has supplementary, 165 companion tables for additional objects that depend on the action taken. 167 The notification section defines a set of generic notifications to go 168 with the events and for Event MIB error handling, and it defines a set 169 of objects to put in those notifications. 171 The following diagram describes the relationships between the tables 172 in the Event MIB. 174 +--------------------------------+ 175 | mteTriggerEntry | subclassed by: 176 | { mteOwner, |---+ 177 | IMPLIED mteTriggerName } | +-- mteTriggerDeltaEntry 178 | | | 179 | | +-- mteTriggerExistenceEntry 180 | | | 181 | | +-- mteTriggerBooleanEntry 182 | | | 183 | | +-- mteTriggerThresholdEntry 184 | | 185 | | 186 | | 187 | | 188 | mteTrigger*Event ----------------------------->+ 189 | | | 190 | mteTriggerObjects --------------->+ | 191 | | | | 192 +--------------------------------+ | | 193 | | 194 V | 195 +<--------------------------------------------+ | 196 | | 197 V | 198 +--------------------------------+ | 199 | | | 200 | mteObjectsEntry | | 201 | { mteOwner, | | 202 | mteObjectsName, | | 203 | mteObjectsIndex } | | 204 | | | 205 +--------------------------------+ | 206 | 207 V 208 +<---------------------------------------------------------+ 209 | 210 V 211 +---------------------------------+ 212 | | 213 | mteEventEntry | 214 | { mteOwner, | 215 | IMPLIED mteEventName } | 216 | | 217 | mteEventAction - - - - - - > + (condition) 218 | | | 219 +---------------------------------+ | 220 | 221 + < - - - + < - - - - - - - - - - - - - - + 222 | | 223 | | 224 | | 225 | V 226 | +---------------------------------+ 227 | | | 228 | | mteEventNotificationEntry | 229 | | { mteOwner, | 230 | | IMPLIED mteEventName } | 231 | | | 232 | +---------------------------------+ 233 | 234 | 235 | 236 V 237 +---------------------------------+ 238 | | 239 | mteEventSetEntry | 240 | { mteOwner, | 241 | IMPLIED mteEventName } | 242 | | 243 +---------------------------------+ 245 6. Operation 247 The Event MIB is instrumentation for a distributed management 248 application that monitors MIB objects. In its simplest form this 249 application monitors individual, local MIB objects, just as an RMON 250 probe fulfills the functions implied by RMON's alarm and event 251 operation. Additionally the application can monitor remote objects and 252 wildcarded groups of objects. 254 Remote monitoring uses the tag service of the Management Target MIB 255 [RFC2573] to select and access remote systems as an ordinary SNMP-based 256 management application. Local monitoring may be via a more intimate, 257 local interface which may, for example, bypass SNMP encoding but 258 otherwise is functionally identical to remote SNMP operation, including 259 the application of access control. A self-management only system MAY 260 not implement remote monitoring. 262 Wildcards indicate that the application SHOULD use a GetNext-type 263 operation to find the zero or more instances implied by a truncated 264 object identifier, just like an ordinary SNMP-based management 265 application. Each instance of a wildcard is treated as if it were a 266 separate entry, that is the instances of a wildcarded object are 267 independent of one another. For example, a wild-carded object may 268 trigger an event, and result in the setting of another wildcarded 269 object. The instance that satisfied the trigger function is used to 270 perform the set function. All of this takes place independently of any 271 additional instances that may fill the wildcard. 273 Error handling is by notification. These error notifications SHOULD be 274 enabled only for the diagnosis of problems indicated by error counters. 275 If minimizing the probability of notification loss is a concern they 276 SHOULD be transmitted as Inform PDUs as described in the [SNMP-TARGET- 277 MIB] or directed to a log as described in the Notification Log MIB 278 [rfcNotificationLogMIB]. Note that this does not mean the Notification 279 Log MIB is REQUIRED, since in fact notifications usually are not lost, 280 but that the Notification Log MIB can be helpful with this as well as 281 other MIBs that include notifications. 283 Although like most MIBs this one has no explicit controls for the 284 persistence of the values set in configuring events, a robust, polite 285 implementation would certainly not force its managing applications to 286 reconfigure it whenever it resets. 288 Again, as with most MIBs, it is implementation-specific how a system 289 provides and manages such persistence. To speculate, one could imagine, 290 for example, that persistence depended on the context in which the 291 expression was configured, or perhaps system-specific characteristics of 292 the expression's owner. Or perhaps everything in a MIB such as this 293 one, which is clearly aimed at persistent configuration, is 294 automatically part of a system's other persistent configuration. 296 7. Security 298 Security of Event MIB entries depends on SNMPv3 access control for the 299 entire MIB or for subsets based on entry owner names. 301 Security of monitored objects for remote access depends on the 302 Management Target MIB [RFC2573]. Security for local access can depend 303 on the Management Target MIB or on recording appropriate security 304 credentials of the creator of an entry and using those to access the 305 local objects. These security credentials are the parameters necessary 306 as inputs to isAccessAllowed from the Architecture for Describing SNMP 307 Management Frameworks. When accessing local objects without using a 308 local target tag, the system MUST (conceptually) use isAccessAllowed to 309 ensure that it does not violate security. 311 To facilitate the provisioning of access control by a security 312 administrator for this MIB itself using the View-Based Access Control 313 Model (VACM) defined in RFC 2275 [RFC2575] for tables in which multiple 314 users may need to independently create or modify entries, the initial 315 index is used as an "owner index". Such an initial index has a syntax of 316 SnmpAdminString, and can thus be trivially mapped to a securityName or 317 groupName as defined in VACM, in accordance with a security policy. 319 All entries in related tables belonging to a particular user will have 320 the same value for this initial index. For a given user's entries in a 321 particular table, the object identifiers for the information in these 322 entries will have the same sub-identifiers (except for the "column" sub- 323 identifier) up to the end of the encoded owner index. To configure VACM 324 to permit access to this portion of the table, one would create 325 vacmViewTreeFamilyTable entries with the value of 326 vacmViewTreeFamilySubtree including the owner index portion, and 327 vacmViewTreeFamilyMask "wildcarding" the column sub-identifier. More 328 elaborate configurations are possible. 330 8. Definitions 332 DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN 334 IMPORTS 335 MODULE-IDENTITY, OBJECT-TYPE, 336 Integer32, Unsigned32, 337 NOTIFICATION-TYPE, Counter32, 338 Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI 339 TEXTUAL-CONVENTION, RowStatus, 340 TruthValue FROM SNMPv2-TC 341 MODULE-COMPLIANCE, OBJECT-GROUP, 342 NOTIFICATION-GROUP FROM SNMPv2-CONF 343 sysUpTime FROM SNMPv2-MIB 344 SnmpTagValue FROM SNMP-TARGET-MIB 345 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 347 dismanEventMIB MODULE-IDENTITY 348 LAST-UPDATED "200001060000Z" -- 6 January 2000 349 ORGANIZATION "IETF Distributed Management Working Group" 350 CONTACT-INFO "Ramanathan Kavasseri 351 Cisco Systems, Inc. 352 170 West Tasman Drive, 353 San Jose CA 95134-1706. 354 Phone: +1 408 526 4527 355 Email: ramk@cisco.com" 356 DESCRIPTION 357 "The MIB module for defining event triggers and actions 358 for network management purposes." 359 -- Revision History 361 REVISION "200001060000Z" -- 6 January 2000 362 DESCRIPTION "This is the initial version of this MIB. 363 Published as RFC xxxxx" 364 ::= { mib-2 xx } - final assignment by IANA at publication time 366 dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 } 368 -- Management Triggered Event (MTE) objects 370 mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 } 371 mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 } 372 mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 } 373 mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 } 374 -- 375 -- Textual Conventions 376 -- 378 FailureReason ::= TEXTUAL-CONVENTION 379 STATUS current 380 DESCRIPTION 381 "Reasons for failures in an attempt to perform a management 382 request. 384 The first group of errors, numbered less than 0, are related 385 to problems in sending the request. The existence of a 386 particular error code here does not imply that all 387 implementations are capable of sensing that error and 388 returning that code. 390 The second group, numbered greater than 0, are copied 391 directly from SNMP protocol operations and are intended to 392 carry exactly the meanings defined for the protocol as returned 393 in an SNMP response. 395 localResourceLack some local resource such as memory lacking 396 or mteResourceSampleInstanceMaximum 397 exceeded 398 badDestination unrecognized domain name or otherwise 399 invalid destination address 400 destinationUnreachable can't get to destination address 401 noResponse no response to SNMP request 402 badType the data syntax of a retrieved object 403 as not as expected 404 sampleOverrun another sample attempt occurred before 405 the previous one completed" 407 SYNTAX INTEGER { localResourceLack(-1), 408 badDestination(-2), 409 destinationUnreachable(-3), 410 noResponse(-4), 411 badType(-5), 412 sampleOverrun(-6), 414 noError(0), 416 tooBig(1), 417 noSuchName(2), 418 badValue(3), 419 readOnly(4), 420 genErr(5), 421 noAccess(6), 422 wrongType(7), 423 wrongLength(8), 424 wrongEncoding(9), 425 wrongValue(10), 426 noCreation(11), 427 inconsistentValue(12), 428 resourceUnavailable(13), 429 commitFailed(14), 430 undoFailed(15), 431 authorizationError(16), 432 notWritable(17), 433 inconsistentName(18) } 434 -- 435 -- Resource Control Section 436 -- 438 mteResourceSampleMinimum OBJECT-TYPE 439 SYNTAX Integer32 (1..2147483647) 440 UNITS "seconds" 441 MAX-ACCESS read-write 442 STATUS current 443 DESCRIPTION 444 "The minimum mteTriggerFrequency this system will 445 accept. A system may use the larger values of this minimum to 446 lessen the impact of constant sampling. For larger 447 sampling intervals the system samples less often and 448 suffers less overhead. This object provides a way to enforce 449 such lower overhead for all triggers created after it is 450 set. 452 Unless explicitly resource limited, a system's value for 453 this object SHOULD be 1, allowing as small as a 1 second 454 interval for ongoing trigger sampling. 456 Changing this value will not invalidate an existing setting 457 of mteTriggerFrequency." 458 ::= { mteResource 1 } 460 mteResourceSampleInstanceMaximum OBJECT-TYPE 461 SYNTAX Unsigned32 462 UNITS "instances" 463 MAX-ACCESS read-write 464 STATUS current 465 DESCRIPTION 466 "The maximum number of instance entries this system will 467 support for sampling. 469 These are the entries that maintain state, one for each 470 instance of each sampled object as selected by 471 mteTriggerValueID. Note that wildcarded objects result 472 in multiple instances of this state. 474 A value of 0 indicates no preset limit, that is, the limit 475 is dynamic based on system operation and resources. 477 Unless explicitly resource limited, a system's value for 478 this object SHOULD be 0. 480 Changing this value will not eliminate or inhibit existing 481 sample state but could prevent allocation of additional state 482 information." 483 ::= { mteResource 2 } 485 mteResourceSampleInstances OBJECT-TYPE 486 SYNTAX Gauge32 487 UNITS "instances" 488 MAX-ACCESS read-only 489 STATUS current 490 DESCRIPTION 491 "The number of currently active instance entries as 492 defined for mteResourceSampleInstanceMaximum." 493 ::= { mteResource 3 } 495 mteResourceSampleInstancesHigh OBJECT-TYPE 496 SYNTAX Gauge32 497 UNITS "instances" 498 MAX-ACCESS read-only 499 STATUS current 500 DESCRIPTION 501 "The highest value of mteResourceSampleInstances that has 502 occurred since initialization of the management system." 503 ::= { mteResource 4 } 505 mteResourceSampleInstanceLacks OBJECT-TYPE 506 SYNTAX Counter32 507 UNITS "instances" 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION 511 "The number of times this system could not take a new sample 512 because that allocation would have exceeded the limit set by 513 mteResourceSampleInstanceMaximum." 514 ::= { mteResource 5 } 516 -- 517 -- Trigger Section 518 -- 520 -- Counters 522 mteTriggerFailures OBJECT-TYPE 523 SYNTAX Counter32 524 UNITS "failures" 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "The number of times an attempt to check for a trigger 529 condition has failed. This counts individually for each 530 attempt in a group of targets or each attempt for a 531 wildcarded object." 532 ::= { mteTrigger 1 } 534 -- 535 -- Trigger Table 536 -- 538 mteTriggerTable OBJECT-TYPE 539 SYNTAX SEQUENCE OF MteTriggerEntry 540 MAX-ACCESS not-accessible 541 STATUS current 542 DESCRIPTION 543 "A table of management event trigger information." 544 ::= { mteTrigger 2 } 546 mteTriggerEntry OBJECT-TYPE 547 SYNTAX MteTriggerEntry 548 MAX-ACCESS not-accessible 549 STATUS current 550 DESCRIPTION 551 "Information about a single trigger. Applications create and 552 delete entries using mteTriggerEntryStatus." 553 INDEX { mteOwner, IMPLIED mteTriggerName } 554 ::= { mteTriggerTable 1 } 556 MteTriggerEntry ::= SEQUENCE { 557 mteOwner SnmpAdminString, 558 mteTriggerName SnmpAdminString, 559 mteTriggerComment SnmpAdminString, 560 mteTriggerTest BITS, 561 mteTriggerSampleType INTEGER, 562 mteTriggerValueID OBJECT IDENTIFIER, 563 mteTriggerValueIDWildcard TruthValue, 564 mteTriggerTargetTag SnmpTagValue, 565 mteTriggerContextName SnmpAdminString, 566 mteTriggerContextNameWildcard TruthValue, 567 mteTriggerFrequency Unsigned32, 568 mteTriggerObjectsOwner SnmpAdminString, 569 mteTriggerObjects SnmpAdminString, 570 mteTriggerEnabled TruthValue, 571 mteTriggerEntryStatus RowStatus 572 } 574 mteOwner OBJECT-TYPE 575 SYNTAX SnmpAdminString (SIZE(0..32)) 576 MAX-ACCESS not-accessible 577 STATUS current 578 DESCRIPTION 579 "The owner of this entry. The exact semantics of this 580 string are subject to the security policy defined by the 581 security administrator." 582 ::= { mteTriggerEntry 1 } 584 mteTriggerName OBJECT-TYPE 585 SYNTAX SnmpAdminString (SIZE (1..32)) 586 MAX-ACCESS not-accessible 587 STATUS current 588 DESCRIPTION 589 "A locally-unique, administratively assigned name for the 590 trigger within the scope of mteOwner." 591 ::= { mteTriggerEntry 2 } 593 mteTriggerComment OBJECT-TYPE 594 SYNTAX SnmpAdminString 595 MAX-ACCESS read-create 596 STATUS current 597 DESCRIPTION 598 "A description of the trigger's function and use." 599 DEFVAL { ''H } 600 ::= { mteTriggerEntry 3 } 602 mteTriggerTest OBJECT-TYPE 603 SYNTAX BITS { existence(0), boolean(1), threshold(2) } 604 MAX-ACCESS read-create 605 STATUS current 606 DESCRIPTION 607 "The type of trigger test to perform. For 'boolean' and 608 'threshold' tests, the object at mteTriggerValueID MUST 609 evaluate to an integer, that is, anything that ends up encoded 610 for transmission (that is, in BER, not ASN.1) as an integer. 612 For 'existence', the specific test is as selected by 613 mteTriggerExistenceTest. When an object appears, vanishes 614 or changes value, the trigger fires. If the object's 615 appearance caused the trigger firing, the object MUST 616 vanish before the trigger can be fired again for it, and 617 vice versa. If the trigger fired due to a change in the 618 object's value, it will be fired again on every successive 619 value change for that object. 621 For 'boolean', the specific test is as selected by 622 mteTriggerBooleanTest. If the test result is true the trigger 623 fires. The trigger will not fire again until the value has 624 become false and come back to true. 626 For 'threshold' the test works as described below for 627 mteTriggerThresholdStartup, mteTriggerThresholdRising, and 628 mteTriggerThresholdFalling. 630 Note that combining 'boolean' and 'threshold' tests on the 631 same object may be somewhat redundant." 632 DEFVAL { boolean } 633 ::= { mteTriggerEntry 4 } 635 mteTriggerSampleType OBJECT-TYPE 636 SYNTAX INTEGER { absoluteValue(1), deltaValue(2) } 637 MAX-ACCESS read-create 638 STATUS current 639 DESCRIPTION 640 "The type of sampling to perform. 642 An 'absoluteValue' sample requires only a single sample to be 643 meaningful, and is exactly the value of the object at 644 mteTriggerValueID at the sample time. 646 A 'deltaValue' requires two samples to be meaningful and is 647 thus not available for testing until the second and subsequent 648 samples after the object at mteTriggerValueID is first found 649 to exist. It is the difference between the two samples. For 650 unsigned values it is always positive, based on unsigned 651 arithmetic. For signed values it can be positive or negative. 653 For SNMP counters to be meaningful they MUST be sampled as a 654 'deltaValue'. 656 For 'deltaValue' mteTriggerDeltaTable contains further 657 parameters. 659 If only 'existence' is set in mteTriggerTest this object has 660 no meaning." 661 DEFVAL { absoluteValue } 662 ::= { mteTriggerEntry 5 } 664 mteTriggerValueID OBJECT-TYPE 665 SYNTAX OBJECT IDENTIFIER 666 MAX-ACCESS read-create 667 STATUS current 668 DESCRIPTION 669 "The object identifier of the MIB object to sample to see 670 if the trigger should fire. 672 This may be wildcarded by truncating all or part of the 673 instance portion, in which case the value is obtained 674 as if with a GetNext function, checking multiple values 675 if they exist. If such wildcarding is applied, 676 mteTriggerValueIDWildcard must be 'true' and if not it must 677 be 'false'. 679 Bad object identifiers or a mismatch between truncating the 680 identifier and the value of mteTriggerValueIDWildcard result 681 in operation as one would expect when providing the wrong 682 identifier to a Get or GetNext operation. The Get will fail 683 or get the wrong object. The GetNext will indeed get whatever 684 is next, proceeding until it runs past the initial part of the 685 identifier and perhaps many unintended objects for confusing 686 results. If the value syntax of those objects is not usable, 687 that results in a 'badType' error that terminates the scan. 689 Each instance that fills the wildcard is independent of any 690 additional instances, that is, wildcarded objects operate 691 as if there were a separate table entry for each instance 692 that fills the wildcard without having to actually predict 693 all possible instances ahead of time." 694 DEFVAL { zeroDotZero } 695 ::= { mteTriggerEntry 6 } 697 mteTriggerValueIDWildcard OBJECT-TYPE 698 SYNTAX TruthValue 699 MAX-ACCESS read-create 700 STATUS current 701 DESCRIPTION 702 "Control for whether mteTriggerValueID is to be treated as 703 fully-specified or wildcarded, with 'true' indicating wildcard." 704 DEFVAL { false } 705 ::= { mteTriggerEntry 7 } 707 mteTriggerTargetTag OBJECT-TYPE 708 SYNTAX SnmpTagValue 709 MAX-ACCESS read-create 710 STATUS current 711 DESCRIPTION 712 "The tag for the target(s) from which to obtain the condition 713 for a trigger check. 715 A length of 0 indicates the local system. In this case, 716 access to the objects indicated by mteTriggerValueID is under 717 the security credentials of the requester that set 718 mteTriggerEntryStatus to 'active'. Those credentials are the 719 input parameters for isAccessAllowed from the Architecture for 720 Describing SNMP Management Frameworks. 722 Otherwise access rights are checked according to the security 723 parameters resulting from the tag." 724 DEFVAL { ''H } 725 ::= { mteTriggerEntry 8 } 727 mteTriggerContextName OBJECT-TYPE 728 SYNTAX SnmpAdminString 729 MAX-ACCESS read-create 730 STATUS current 731 DESCRIPTION 732 "The management context from which to obtain mteTriggerValueID. 734 This may be wildcarded by leaving characters off the end. For 735 example use 'Repeater' to wildcard to 'Repeater1', 736 'Repeater2', 'Repeater-999.87b', and so on. To indicate such 737 wildcarding is intended, mteTriggerContextNameWildcard must 738 be 'true'. 740 Each instance that fills the wildcard is independent of any 741 additional instances, that is, wildcarded objects operate 742 as if there were a separate table entry for each instance 743 that fills the wildcard without having to actually predict 744 all possible instances ahead of time. 746 Operation of this feature assumes that the local system has a 747 list of available contexts against which to apply the 748 wildcard. If the objects are being read from the local 749 system, this is clearly the system's own list of contexts. 750 For a remote system a local version of such a list is not 751 defined by any current standard and may not be available, so 752 this function MAY not be supported." 753 DEFVAL { ''H } 754 ::= { mteTriggerEntry 9 } 756 mteTriggerContextNameWildcard OBJECT-TYPE 757 SYNTAX TruthValue 758 MAX-ACCESS read-create 759 STATUS current 760 DESCRIPTION 761 "Control for whether mteTriggerContextName is to be treated as 762 fully-specified or wildcarded, with 'true' indicating wildcard." 763 DEFVAL { false } 764 ::= { mteTriggerEntry 10 } 766 mteTriggerFrequency OBJECT-TYPE 767 SYNTAX Unsigned32 768 UNITS "seconds" 769 MAX-ACCESS read-create 770 STATUS current 771 DESCRIPTION 772 "The number of seconds to wait between trigger samples. To 773 encourage consistency in sampling, the interval is measured 774 from the beginning of one check to the beginning of the next 775 and the timer is restarted immediately when it expires, not 776 when the check completes. 778 If the next sample begins before the previous one completed the 779 system may either attempt to make the check or treat this as an 780 error condition with the error 'sampleOverrun'. 782 A frequency of 0 indicates instantaneous recognition of the 783 condition. This is not possible in many cases, but may 784 be supported in cases where it makes sense and the system is 785 able to do so. This feature allows the MIB to be used in 786 implementations where such interrupt-driven behavior is 787 possible and is not likely to be supported for all MIB objects 788 even then since such sampling generally has to be tightly 789 integrated into low-level code. 791 Systems that can support this SHOULD document those cases 792 where it can be used. In cases where it can not, setting this 793 object to 0 should be disallowed." 794 DEFVAL { 600 } 795 ::= { mteTriggerEntry 11 } 797 mteTriggerObjectsOwner OBJECT-TYPE 798 SYNTAX SnmpAdminString (SIZE (0..32)) 799 MAX-ACCESS read-create 800 STATUS current 801 DESCRIPTION 802 "To go with mteTriggerObjects, the mteOwner of a group of 803 objects from mteObjectsTable." 804 DEFVAL { ''H } 805 ::= { mteTriggerEntry 12 } 807 mteTriggerObjects OBJECT-TYPE 808 SYNTAX SnmpAdminString (SIZE (0..32)) 809 MAX-ACCESS read-create 810 STATUS current 811 DESCRIPTION 812 "The mteObjectsName of a group of objects from 813 mteObjectsTable. These objects are to be added to any 814 Notification resulting from the firing of this trigger. 816 A list of objects may also be added based on the event or on 817 the value of mteTriggerTest. 819 A length of 0 indicates no additional objects." 820 DEFVAL { ''H } 821 ::= { mteTriggerEntry 13 } 823 mteTriggerEnabled OBJECT-TYPE 824 SYNTAX TruthValue 825 MAX-ACCESS read-create 826 STATUS current 827 DESCRIPTION 828 "A control to allow a trigger to be configured but not used. 829 When the value is 'false' the trigger is not sampled." 830 DEFVAL { false } 831 ::= { mteTriggerEntry 14 } 833 mteTriggerEntryStatus OBJECT-TYPE 834 SYNTAX RowStatus 835 MAX-ACCESS read-create 836 STATUS current 837 DESCRIPTION 838 "The control that allows creation and deletion of entries. 839 Once made active an entry may not be modified except to 840 delete it." 841 ::= { mteTriggerEntry 15 } 843 -- 844 -- Trigger Delta Table 845 -- 847 mteTriggerDeltaTable OBJECT-TYPE 848 SYNTAX SEQUENCE OF MteTriggerDeltaEntry 849 MAX-ACCESS not-accessible 850 STATUS current 851 DESCRIPTION 852 "A table of management event trigger information for delta 853 sampling." 854 ::= { mteTrigger 3 } 856 mteTriggerDeltaEntry OBJECT-TYPE 857 SYNTAX MteTriggerDeltaEntry 858 MAX-ACCESS not-accessible 859 STATUS current 860 DESCRIPTION 861 "Information about a single trigger's delta sampling. Entries 862 automatically exist in this this table for each mteTriggerEntry 863 that has mteTriggerSampleType set to 'deltaValue'." 864 INDEX { mteOwner, IMPLIED mteTriggerName } 865 ::= { mteTriggerDeltaTable 1 } 867 MteTriggerDeltaEntry ::= SEQUENCE { 868 mteTriggerDeltaDiscontinuityID OBJECT IDENTIFIER, 869 mteTriggerDeltaDiscontinuityIDWildcard TruthValue, 870 mteTriggerDeltaDiscontinuityIDType INTEGER 871 } 873 sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 } 875 mteTriggerDeltaDiscontinuityID OBJECT-TYPE 876 SYNTAX OBJECT IDENTIFIER 877 MAX-ACCESS read-write 878 STATUS current 879 DESCRIPTION 880 "The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or 881 DateAndTime object that indicates a discontinuity in the value 882 at mteTriggerValueID. 884 The OID may be for a leaf object (e.g. sysUpTime.0) or may 885 be wildcarded to match mteTriggerValueID. 887 This object supports normal checking for a discontinuity in a 888 counter. Note that if this object does not point to sysUpTime 889 discontinuity checking MUST still check sysUpTime for an overall 890 discontinuity. 892 If the object identified is not accessible the sample attempt 893 is in error, with the error code as from an SNMP request. 895 Bad object identifiers or a mismatch between truncating the 896 identifier and the value of mteDeltaDiscontinuityIDWildcard 897 result in operation as one would expect when providing the 898 wrong identifier to a Get operation. The Get will fail or get 899 the wrong object. If the value syntax of those objects is not 900 usable, that results in an error that terminates the sample 901 with a 'badType' error code." 902 DEFVAL { sysUpTimeInstance } 903 ::= { mteTriggerDeltaEntry 1 } 905 mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE 906 SYNTAX TruthValue 907 MAX-ACCESS read-write 908 STATUS current 909 DESCRIPTION 910 "Control for whether mteTriggerDeltaDiscontinuityID is to be 911 treated as fully-specified or wildcarded, with 'true' 912 indicating wildcard. Note that the value of this object will 913 be the same as that of the corresponding instance of 914 mteTriggerValueIDWildcard when the corresponding 915 mteTriggerSampleType is 'deltaValue'." 916 DEFVAL { false } 917 ::= { mteTriggerDeltaEntry 2 } 919 mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE 920 SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) } 921 MAX-ACCESS read-write 922 STATUS current 923 DESCRIPTION 924 "The value 'timeTicks' indicates the 925 mteTriggerDeltaDiscontinuityID of this row is of syntax 926 TimeTicks. The value 'timeStamp' indicates syntax TimeStamp. 927 The value 'dateAndTime' indicates syntax DateAndTime." 928 DEFVAL { timeTicks } 929 ::= { mteTriggerDeltaEntry 3 } 931 -- 932 -- Trigger Existence Table 933 -- 935 mteTriggerExistenceTable OBJECT-TYPE 936 SYNTAX SEQUENCE OF MteTriggerExistenceEntry 937 MAX-ACCESS not-accessible 938 STATUS current 939 DESCRIPTION 940 "A table of management event trigger information for existence 941 triggers." 942 ::= { mteTrigger 4 } 944 mteTriggerExistenceEntry OBJECT-TYPE 945 SYNTAX MteTriggerExistenceEntry 946 MAX-ACCESS not-accessible 947 STATUS current 948 DESCRIPTION 949 "Information about a single existence trigger. Entries 950 automatically exist in this this table for each mteTriggerEntry 951 that has 'existence' set in mteTriggerTest." 952 INDEX { mteOwner, IMPLIED mteTriggerName } 953 ::= { mteTriggerExistenceTable 1 } 955 MteTriggerExistenceEntry ::= SEQUENCE { 956 mteTriggerExistenceTest BITS, 957 mteTriggerExistenceStartup BITS, 958 mteTriggerExistenceObjectsOwner SnmpAdminString, 959 mteTriggerExistenceObjects SnmpAdminString, 960 mteTriggerExistenceEventOwner SnmpAdminString, 961 mteTriggerExistenceEvent SnmpAdminString 962 } 964 mteTriggerExistenceTest OBJECT-TYPE 965 SYNTAX BITS { present(0), absent(1), changed(2) } 966 MAX-ACCESS read-write 967 STATUS current 968 DESCRIPTION 969 "The type of existence test to perform. The trigger fires 970 when the object at mteTriggerValueID is seen to go from 971 present to absent, from absent to present, or to have it's 972 value changed, depending on which tests are selected: 974 present(0) - when this test is selected, the trigger fires 975 when the mteTriggerValueID object goes from absent to present. 977 absent(1) - when this test is selected, the trigger fires 978 when the mteTriggerValueID object goes from present to absent. 979 changed(2) - when this test is selected, the trigger fires 980 the mteTriggerValueID object value changes. 982 Once the trigger has fired for either presence or absence it 983 will not fire again for that state until the object has been 984 to the other state. " 985 DEFVAL { { present, absent } } 986 ::= { mteTriggerExistenceEntry 1 } 988 mteTriggerExistenceStartup OBJECT-TYPE 989 SYNTAX BITS { present(0), absent(1) } 990 MAX-ACCESS read-write 991 STATUS current 992 DESCRIPTION 993 "Control for whether an event may be triggered when this entry 994 is first set to 'active' and the test specified by 995 mteTriggerExistenceTest is true. Setting an option causes 996 that trigger to fire when its test is true." 997 DEFVAL { { present, absent } } 998 ::= { mteTriggerExistenceEntry 2 } 1000 mteTriggerExistenceObjectsOwner OBJECT-TYPE 1001 SYNTAX SnmpAdminString (SIZE (0..32)) 1002 MAX-ACCESS read-write 1003 STATUS current 1004 DESCRIPTION 1005 "To go with mteTriggerExistenceObjects, the mteOwner of a 1006 group of objects from mteObjectsTable." 1007 DEFVAL { ''H } 1008 ::= { mteTriggerExistenceEntry 3 } 1010 mteTriggerExistenceObjects OBJECT-TYPE 1011 SYNTAX SnmpAdminString (SIZE (0..32)) 1012 MAX-ACCESS read-write 1013 STATUS current 1014 DESCRIPTION 1015 "The mteObjectsName of a group of objects from 1016 mteObjectsTable. These objects are to be added to any 1017 Notification resulting from the firing of this trigger for 1018 this test. 1020 A list of objects may also be added based on the overall 1021 trigger, the event or other settings in mteTriggerTest. 1023 A length of 0 indicates no additional objects." 1024 DEFVAL { ''H } 1025 ::= { mteTriggerExistenceEntry 4 } 1027 mteTriggerExistenceEventOwner OBJECT-TYPE 1028 SYNTAX SnmpAdminString (SIZE (0..32)) 1029 MAX-ACCESS read-write 1030 STATUS current 1031 DESCRIPTION 1032 "To go with mteTriggerExistenceEvent, the mteOwner of an event 1033 entry from the mteEventTable." 1034 DEFVAL { ''H } 1035 ::= { mteTriggerExistenceEntry 5 } 1037 mteTriggerExistenceEvent OBJECT-TYPE 1038 SYNTAX SnmpAdminString (SIZE (0..32)) 1039 MAX-ACCESS read-write 1040 STATUS current 1041 DESCRIPTION 1042 "The mteEventName of the event to invoke when mteTriggerType is 1043 'existence' and this trigger fires. A length of 0 indicates no 1044 event." 1046 DEFVAL { ''H } 1047 ::= { mteTriggerExistenceEntry 6 } 1049 -- 1050 -- Trigger Boolean Table 1051 -- 1053 mteTriggerBooleanTable OBJECT-TYPE 1054 SYNTAX SEQUENCE OF MteTriggerBooleanEntry 1055 MAX-ACCESS not-accessible 1056 STATUS current 1057 DESCRIPTION 1058 "A table of management event trigger information for boolean 1059 triggers." 1060 ::= { mteTrigger 5 } 1062 mteTriggerBooleanEntry OBJECT-TYPE 1063 SYNTAX MteTriggerBooleanEntry 1064 MAX-ACCESS not-accessible 1065 STATUS current 1066 DESCRIPTION 1067 "Information about a single boolean trigger. Entries 1068 automatically exist in this this table for each mteTriggerEntry 1069 that has 'boolean' set in mteTriggerTest." 1070 INDEX { mteOwner, IMPLIED mteTriggerName } 1071 ::= { mteTriggerBooleanTable 1 } 1073 MteTriggerBooleanEntry ::= SEQUENCE { 1074 mteTriggerBooleanComparison INTEGER, 1075 mteTriggerBooleanValue Integer32, 1076 mteTriggerBooleanStartup TruthValue, 1077 mteTriggerBooleanObjectsOwner SnmpAdminString, 1078 mteTriggerBooleanObjects SnmpAdminString, 1079 mteTriggerBooleanEventOwner SnmpAdminString, 1080 mteTriggerBooleanEvent SnmpAdminString 1081 } 1083 mteTriggerBooleanComparison OBJECT-TYPE 1084 SYNTAX INTEGER { unequal(1), equal(2), 1085 less(3), lessOrEqual(4), 1086 greater(5), greaterOrEqual(6) } 1087 MAX-ACCESS read-write 1088 STATUS current 1089 DESCRIPTION 1090 "The type of boolean comparison to perform. 1092 The value at mteTriggerValueID is compared to 1093 mteTriggerBooleanValue, so for example if 1094 mteTriggerBooleanComparison is 'less' the result would be true 1095 if the value at mteTriggerValueID is less than the value of 1096 mteTriggerBooleanValue." 1097 DEFVAL { unequal } 1098 ::= { mteTriggerBooleanEntry 1 } 1100 mteTriggerBooleanValue OBJECT-TYPE 1101 SYNTAX Integer32 1102 MAX-ACCESS read-write 1103 STATUS current 1104 DESCRIPTION 1105 "The value to use for the test specified by 1106 mteTriggerBooleanTest." 1107 DEFVAL { 0 } 1108 ::= { mteTriggerBooleanEntry 2 } 1110 mteTriggerBooleanStartup OBJECT-TYPE 1111 SYNTAX TruthValue 1112 MAX-ACCESS read-write 1113 STATUS current 1114 DESCRIPTION 1115 "Control for whether an event may be triggered when this entry 1116 is first set to 'active' or a new instance of the object at 1117 mteTriggerValueID is found and the test specified by 1118 mteTriggerBooleanComparison is true. In that case an event is 1119 triggered if mteTriggerBooleanStartup is 'true'." 1120 DEFVAL { true } 1121 ::= { mteTriggerBooleanEntry 3 } 1123 mteTriggerBooleanObjectsOwner OBJECT-TYPE 1124 SYNTAX SnmpAdminString (SIZE (0..32)) 1125 MAX-ACCESS read-write 1126 STATUS current 1127 DESCRIPTION 1128 "To go with mteTriggerBooleanObjects, the mteOwner of a group 1129 of objects from mteObjectsTable." 1130 DEFVAL { ''H } 1131 ::= { mteTriggerBooleanEntry 4 } 1133 mteTriggerBooleanObjects OBJECT-TYPE 1134 SYNTAX SnmpAdminString (SIZE (0..32)) 1135 MAX-ACCESS read-write 1136 STATUS current 1137 DESCRIPTION 1138 "The mteObjectsName of a group of objects from 1139 mteObjectsTable. These objects are to be added to any 1140 Notification resulting from the firing of this trigger for 1141 this test. 1143 A list of objects may also be added based on the overall 1144 trigger, the event or other settings in mteTriggerTest. 1146 A length of 0 indicates no additional objects." 1147 DEFVAL { ''H } 1148 ::= { mteTriggerBooleanEntry 5 } 1150 mteTriggerBooleanEventOwner OBJECT-TYPE 1151 SYNTAX SnmpAdminString (SIZE (0..32)) 1152 MAX-ACCESS read-write 1153 STATUS current 1154 DESCRIPTION 1155 "To go with mteTriggerBooleanEvent, the mteOwner of an event 1156 entry from mteEventTable." 1157 DEFVAL { ''H } 1158 ::= { mteTriggerBooleanEntry 6 } 1160 mteTriggerBooleanEvent OBJECT-TYPE 1161 SYNTAX SnmpAdminString (SIZE (0..32)) 1162 MAX-ACCESS read-write 1163 STATUS current 1164 DESCRIPTION 1165 "The mteEventName of the event to invoke when mteTriggerType is 1166 'boolean' and this trigger fires. A length of 0 indicates no 1167 event." 1168 DEFVAL { ''H } 1169 ::= { mteTriggerBooleanEntry 7 } 1171 -- 1172 -- Trigger Threshold Table 1173 -- 1175 mteTriggerThresholdTable OBJECT-TYPE 1176 SYNTAX SEQUENCE OF MteTriggerThresholdEntry 1177 MAX-ACCESS not-accessible 1178 STATUS current 1179 DESCRIPTION 1180 "A table of management event trigger information for threshold 1181 triggers." 1182 ::= { mteTrigger 6 } 1184 mteTriggerThresholdEntry OBJECT-TYPE 1185 SYNTAX MteTriggerThresholdEntry 1186 MAX-ACCESS not-accessible 1187 STATUS current 1188 DESCRIPTION 1189 "Information about a single threshold trigger. Entries 1190 automatically exist in this table for each mteTriggerEntry 1191 that has 'threshold' set in mteTriggerTest." 1192 INDEX { mteOwner, IMPLIED mteTriggerName } 1193 ::= { mteTriggerThresholdTable 1 } 1195 MteTriggerThresholdEntry ::= SEQUENCE { 1196 mteTriggerThresholdStartup INTEGER, 1197 mteTriggerThresholdRising Integer32, 1198 mteTriggerThresholdFalling Integer32, 1199 mteTriggerThresholdDeltaRising Integer32, 1200 mteTriggerThresholdDeltaFalling Integer32, 1201 mteTriggerThresholdObjectsOwner SnmpAdminString, 1202 mteTriggerThresholdObjects SnmpAdminString, 1203 mteTriggerThresholdRisingEventOwner SnmpAdminString, 1204 mteTriggerThresholdRisingEvent SnmpAdminString, 1205 mteTriggerThresholdFallingEventOwner SnmpAdminString, 1206 mteTriggerThresholdFallingEvent SnmpAdminString 1207 mteTriggerThresholdDeltaRisingEventOwner SnmpAdminString, 1208 mteTriggerThresholdDeltaRisingEvent SnmpAdminString, 1209 mteTriggerThresholdDeltaFallingEventOwner SnmpAdminString, 1210 mteTriggerThresholdDeltaFallingEvent SnmpAdminString 1211 } 1213 mteTriggerThresholdStartup OBJECT-TYPE 1214 SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } 1215 MAX-ACCESS read-write 1216 STATUS current 1217 DESCRIPTION 1218 "The event that may be triggered when this entry is first 1219 set to 'active' and a new instance of the object at 1220 mteTriggerValueID is found. If the first sample after this 1221 instance becomes active is greater than or equal to 1222 mteTriggerThresholdRising and mteTriggerThresholdStartup is 1223 equal to 'rising' or 'risingOrFalling', then one 1224 mteTriggerThresholdRisingEvent is triggered for that instance. 1225 If the first sample after this entry becomes active is less 1226 than or equal to mteTriggerThresholdFalling and 1227 mteTriggerThresholdStartup is equal to 'falling' or 1228 'risingOrFalling', then one mteTriggerThresholdRisingEvent is 1229 triggered for that instance." 1230 DEFVAL { risingOrFalling } 1231 ::= { mteTriggerThresholdEntry 1 } 1233 mteTriggerThresholdRising OBJECT-TYPE 1234 SYNTAX Integer32 1235 MAX-ACCESS read-write 1236 STATUS current 1237 DESCRIPTION 1238 "A threshold value to check against if mteTriggerType is 1239 'threshold'. 1241 When the current sampled value is greater than or equal to 1242 this threshold, and the value at the last sampling interval 1243 was less than this threshold, one 1244 mteTriggerThresholdRisingEvent is triggered. That event is 1245 also triggered if the first sample after this entry becomes 1246 active is greater than or equal to this threshold and 1247 mteTriggerThresholdStartup is equal to 'rising' or 1248 'risingOrFalling'. 1250 After a rising event is generated, another such event is not 1251 triggered until the sampled value falls below this threshold 1252 and reaches mteTriggerThresholdFalling." 1253 DEFVAL { 0 } 1254 ::= { mteTriggerThresholdEntry 2 } 1256 mteTriggerThresholdFalling OBJECT-TYPE 1257 SYNTAX Integer32 1258 MAX-ACCESS read-write 1259 STATUS current 1260 DESCRIPTION 1261 "A threshold value to check against if mteTriggerType is 1262 'threshold'. 1264 When the current sampled value is less than or equal to this 1265 threshold, and the value at the last sampling interval was 1266 greater than this threshold, one 1267 mteTriggerThresholdFallingEvent is triggered. That event is 1268 also triggered if the first sample afer this entry bcomes 1269 active is less than or equal to this threshold and 1270 mteTriggerThresholdStartup is equal to 'falling' or 1271 'risingOrFalling'. 1273 After a falling event is generated, another such event is not 1274 triggered until the sampled value rises above this threshold 1275 and reaches mteTriggerThresholdRising." 1276 DEFVAL { 0 } 1277 ::= { mteTriggerThresholdEntry 3 } 1279 mteTriggerThresholdDeltaRising OBJECT-TYPE 1280 SYNTAX Integer32 1281 MAX-ACCESS read-write 1282 STATUS current 1283 DESCRIPTION 1284 "A threshold value to check against if mteTriggerType is 1285 'threshold'. 1287 When the delta value (difference) between the current sampled 1288 value (value(n)) and the previous sampled value (value(n-1)) 1289 is greater than or equal to this threshold, 1290 and the delta value calculated at the last sampling interval 1291 (i.e. value(n-1) - value(n-2)) was less than this threshold, 1292 one mteTriggerThresholdDeltaRisingEvent is triggered. That event is 1293 also triggered if the first delta value calculated after this 1294 entry becomes active, i.e. value(2) - value(1), where value(1) 1295 is the first sample taken of that instance, is greater than or 1296 equal to this threshold. 1298 After a rising event is generated, another such event is not 1299 triggered until the delta value falls below this threshold and 1300 reaches mteTriggerThresholdDeltaFalling." 1301 DEFVAL { 0 } 1302 ::= { mteTriggerThresholdEntry 4 } 1304 mteTriggerThresholdDeltaFalling OBJECT-TYPE 1305 SYNTAX Integer32 1306 MAX-ACCESS read-write 1307 STATUS current 1308 DESCRIPTION 1309 "A threshold value to check against if mteTriggerType is 1310 'threshold'. 1312 When the delta value (difference) between the current sampled 1313 value (value(n)) and the previous sampled value (value(n-1)) 1314 is less than or equal to this threshold, 1315 and the delta value calculated at the last sampling interval 1316 (i.e. value(n-1) - value(n-2)) was greater than this threshold, 1317 one mteTriggerThresholdDeltaFallingEvent is triggered. That event is 1318 also triggered if the first delta value calculated after this 1319 entry becomes active, i.e. value(2) - value(1), where value(1) 1320 is the first sample taken of that instance, is less than or 1321 equal to this threshold. 1323 After a falling event is generated, another such event is not 1324 triggered until the delta value falls below this threshold and 1325 reaches mteTriggerThresholdDeltaRising." 1326 DEFVAL { 0 } 1327 ::= { mteTriggerThresholdEntry 5 } 1329 mteTriggerThresholdObjectsOwner OBJECT-TYPE 1330 SYNTAX SnmpAdminString (SIZE (0..32)) 1331 MAX-ACCESS read-write 1332 STATUS current 1333 DESCRIPTION 1334 "To go with mteTriggerThresholdObjects, the mteOwner of a group 1335 of objects from mteObjectsTable." 1336 DEFVAL { ''H } 1337 ::= { mteTriggerThresholdEntry 6 } 1339 mteTriggerThresholdObjects OBJECT-TYPE 1340 SYNTAX SnmpAdminString (SIZE (0..32)) 1341 MAX-ACCESS read-write 1342 STATUS current 1343 DESCRIPTION 1344 "The mteObjectsName of a group of objects from 1345 mteObjectsTable. These objects are to be added to any 1346 Notification resulting from the firing of this trigger for 1347 this test. 1349 A list of objects may also be added based on the overall 1350 trigger, the event or other settings in mteTriggerTest. 1352 A length of 0 indicates no additional objects." 1353 DEFVAL { ''H } 1354 ::= { mteTriggerThresholdEntry 7 } 1356 mteTriggerThresholdRisingEventOwner OBJECT-TYPE 1357 SYNTAX SnmpAdminString (SIZE (0..32)) 1358 MAX-ACCESS read-write 1359 STATUS current 1360 DESCRIPTION 1361 "To go with mteTriggerThresholdRisingEvent, the mteOwner of an 1362 event entry from mteEventTable." 1363 DEFVAL { ''H } 1364 ::= { mteTriggerThresholdEntry 8 } 1366 mteTriggerThresholdRisingEvent OBJECT-TYPE 1367 SYNTAX SnmpAdminString (SIZE (0..32)) 1368 MAX-ACCESS read-write 1369 STATUS current 1370 DESCRIPTION 1371 "The mteEventName of the event to invoke when mteTriggerType is 1372 'threshold' and this trigger fires based on 1373 mteTriggerThresholdRising. A length of 0 indicates no event." 1374 DEFVAL { ''H } 1375 ::= { mteTriggerThresholdEntry 9 } 1377 mteTriggerThresholdFallingEventOwner OBJECT-TYPE 1378 SYNTAX SnmpAdminString (SIZE (0..32)) 1379 MAX-ACCESS read-write 1380 STATUS current 1381 DESCRIPTION 1382 "To go with mteTriggerThresholdFallingEvent, the mteOwner of an 1383 event entry from mteEventTable." 1384 DEFVAL { ''H } 1385 ::= { mteTriggerThresholdEntry 10 } 1387 mteTriggerThresholdFallingEvent OBJECT-TYPE 1388 SYNTAX SnmpAdminString (SIZE (0..32)) 1389 MAX-ACCESS read-write 1390 STATUS current 1391 DESCRIPTION 1392 "The mteEventName of the event to invoke when mteTriggerType is 1393 'threshold' and this trigger fires based on 1394 mteTriggerThresholdFalling. A length of 0 indicates no event." 1395 DEFVAL { ''H } 1396 ::= { mteTriggerThresholdEntry 11 } 1398 mteTriggerThresholdDeltaRisingEventOwner OBJECT-TYPE 1399 SYNTAX SnmpAdminString (SIZE (0..32)) 1400 MAX-ACCESS read-write 1401 STATUS current 1402 DESCRIPTION 1403 "To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner of an 1404 event entry from mteEventTable." 1405 DEFVAL { ''H } 1406 ::= { mteTriggerThresholdEntry 12 } 1408 mteTriggerThresholdDeltaRisingEvent OBJECT-TYPE 1409 SYNTAX SnmpAdminString (SIZE (0..32)) 1410 MAX-ACCESS read-write 1411 STATUS current 1412 DESCRIPTION 1413 "The mteEventName of the event to invoke when mteTriggerType is 1414 'threshold' and this trigger fires based on 1415 mteTriggerThresholdDeltaRising. A length of 0 indicates no event." 1416 DEFVAL { ''H } 1417 ::= { mteTriggerThresholdEntry 13 } 1419 mteTriggerThresholdDeltaFallingEventOwner OBJECT-TYPE 1420 SYNTAX SnmpAdminString (SIZE (0..32)) 1421 MAX-ACCESS read-write 1422 STATUS current 1423 DESCRIPTION 1424 "To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner of an 1425 event entry from mteEventTable." 1426 DEFVAL { ''H } 1427 ::= { mteTriggerThresholdEntry 14 } 1429 mteTriggerThresholdDeltaFallingEvent OBJECT-TYPE 1430 SYNTAX SnmpAdminString (SIZE (0..32)) 1431 MAX-ACCESS read-write 1432 STATUS current 1433 DESCRIPTION 1434 "The mteEventName of the event to invoke when mteTriggerType is 1435 'threshold' and this trigger fires based on 1436 mteTriggerThresholdDeltaFalling. A length of 0 indicates no event." 1437 DEFVAL { ''H } 1438 ::= { mteTriggerThresholdEntry 15 } 1440 -- 1441 -- Objects Table 1442 -- 1444 mteObjectsTable OBJECT-TYPE 1445 SYNTAX SEQUENCE OF MteObjectsEntry 1446 MAX-ACCESS not-accessible 1447 STATUS current 1448 DESCRIPTION 1449 "A table of objects that can be added to notifications based 1450 on the trigger, trigger test, or event, as pointed to by 1451 entries in those tables." 1452 ::= { mteObjects 1 } 1454 mteObjectsEntry OBJECT-TYPE 1455 SYNTAX MteObjectsEntry 1456 MAX-ACCESS not-accessible 1457 STATUS current 1458 DESCRIPTION 1459 "A group of objects. Applications create and delete entries 1460 using mteObjectsEntryStatus. 1462 When adding objects to a notification they are added in the 1463 lexical order of their index in this table. Those associated 1464 with a trigger come first, then trigger test, then event." 1465 INDEX { mteOwner, mteObjectsName, mteObjectsIndex } 1466 ::= { mteObjectsTable 1 } 1468 MteObjectsEntry ::= SEQUENCE { 1469 mteObjectsName SnmpAdminString, 1470 mteObjectsIndex Unsigned32, 1471 mteObjectsID OBJECT IDENTIFIER, 1472 mteObjectsIDWildcard TruthValue, 1473 mteObjectsEntryStatus RowStatus 1474 } 1476 mteObjectsName OBJECT-TYPE 1477 SYNTAX SnmpAdminString (SIZE (1..32)) 1478 MAX-ACCESS not-accessible 1479 STATUS current 1480 DESCRIPTION 1481 "A locally-unique, administratively assigned name for a group 1482 of objects." 1483 ::= { mteObjectsEntry 1 } 1485 mteObjectsIndex OBJECT-TYPE 1486 SYNTAX Unsigned32 (1..4294967295) 1487 MAX-ACCESS not-accessible 1488 STATUS current 1489 DESCRIPTION 1490 "An arbitrary small integer for the purpose of identifying 1491 individual objects within a mteObjectsName group. 1493 Objects within a group are placed in the notification in the 1494 numerical order of this index. 1496 Groups are placed in the notification in the order of the 1497 selections for overall trigger, trigger test, and event. 1498 Within trigger test they are in the same order as the 1499 numerical values of the bits defined for mteTriggerTest. 1501 Bad object identifiers or a mismatch between truncating the 1502 identifier and the value of mteDeltaDiscontinuityIDWildcard 1503 result in operation as one would expect when providing the 1504 wrong identifier to a Get operation. The Get will fail or get 1505 the wrong object. If the object is not available it is omitted 1506 from the notification." 1507 ::= { mteObjectsEntry 2 } 1509 mteObjectsID OBJECT-TYPE 1510 SYNTAX OBJECT IDENTIFIER 1511 MAX-ACCESS read-create 1512 STATUS current 1513 DESCRIPTION 1514 "The object identifier of a MIB object to add to a 1515 Notification that results from the firing of a trigger. 1517 This may be wildcarded by truncating all or part of the 1518 instance portion, in which case the instance portion of the 1519 OID for obtaining this object will be the same as that used 1520 in obtaining the mteTriggerValueID that fired. If such 1521 wildcarding is applied, mteObjectsIDWildcard must be 1522 'true' and if not it must be 'false'. 1524 Each instance that fills the wildcard is independent of any 1525 additional instances, that is, wildcarded objects operate 1526 as if there were a separate table entry for each instance 1527 that fills the wildcard without having to actually predict 1528 all possible instances ahead of time." 1529 DEFVAL { zeroDotZero } 1530 ::= { mteObjectsEntry 3 } 1532 mteObjectsIDWildcard OBJECT-TYPE 1533 SYNTAX TruthValue 1534 MAX-ACCESS read-create 1535 STATUS current 1536 DESCRIPTION 1537 "Control for whether mteObjectsID is to be treated as 1538 fully-specified or wildcarded, with 'true' indicating wildcard." 1539 DEFVAL { false } 1540 ::= { mteObjectsEntry 4 } 1542 mteObjectsEntryStatus OBJECT-TYPE 1543 SYNTAX RowStatus 1544 MAX-ACCESS read-create 1545 STATUS current 1546 DESCRIPTION 1547 "The control that allows creation and deletion of entries. 1548 Once made active an entry MAY not be modified except to 1549 delete it." 1550 ::= { mteObjectsEntry 5 } 1552 -- 1553 -- Event Section 1554 -- 1556 -- Counters 1558 mteEventFailures OBJECT-TYPE 1559 SYNTAX Counter32 1560 MAX-ACCESS read-only 1561 STATUS current 1562 DESCRIPTION 1563 "The number of times an attempt to invoke an event 1564 has failed. This counts individually for each 1565 attempt in a group of targets or each attempt for a 1566 wildcarded trigger object." 1567 ::= { mteEvent 1 } 1569 -- 1570 -- Event Table 1571 -- 1573 mteEventTable OBJECT-TYPE 1574 SYNTAX SEQUENCE OF MteEventEntry 1575 MAX-ACCESS not-accessible 1576 STATUS current 1577 DESCRIPTION 1578 "A table of management event action information." 1579 ::= { mteEvent 2 } 1581 mteEventEntry OBJECT-TYPE 1582 SYNTAX MteEventEntry 1583 MAX-ACCESS not-accessible 1584 STATUS current 1585 DESCRIPTION 1586 "Information about a single event. Applications create and 1587 delete entries using mteEventEntryStatus." 1588 INDEX { mteOwner, IMPLIED mteEventName } 1589 ::= { mteEventTable 1 } 1591 MteEventEntry ::= SEQUENCE { 1592 mteEventName SnmpAdminString, 1593 mteEventComment SnmpAdminString, 1594 mteEventActions BITS, 1595 mteEventEnabled TruthValue, 1596 mteEventEntryStatus RowStatus 1597 } 1599 mteEventName OBJECT-TYPE 1600 SYNTAX SnmpAdminString (SIZE (1..32)) 1601 MAX-ACCESS not-accessible 1602 STATUS current 1603 DESCRIPTION 1604 "A locally-unique, administratively assigned name for the 1605 event." 1606 ::= { mteEventEntry 1 } 1608 mteEventComment OBJECT-TYPE 1609 SYNTAX SnmpAdminString 1610 MAX-ACCESS read-create 1611 STATUS current 1612 DESCRIPTION 1613 "A description of the event's function and use." 1614 DEFVAL { ''H } 1615 ::= { mteEventEntry 2 } 1617 mteEventActions OBJECT-TYPE 1618 SYNTAX BITS { notification(0), set(1) } 1619 MAX-ACCESS read-create 1620 STATUS current 1621 DESCRIPTION 1622 "The actions to perform when this event occurs. 1624 For 'notification', Traps and/or Informs are sent according 1625 to the configuration in the SNMP Notification MIB. 1627 For 'set', an SNMP Set operation is performed according to 1628 control values in this entry." 1629 DEFVAL { '0'H } -- No bits set. 1630 ::= { mteEventEntry 3 } 1632 mteEventEnabled OBJECT-TYPE 1633 SYNTAX TruthValue 1634 MAX-ACCESS read-create 1635 STATUS current 1636 DESCRIPTION 1637 "A control to allow an event to be configured but not used. 1638 When the value is 'false' the event does not execute even if 1639 triggered." 1640 DEFVAL { false } 1641 ::= { mteEventEntry 4 } 1643 mteEventEntryStatus OBJECT-TYPE 1644 SYNTAX RowStatus 1645 MAX-ACCESS read-create 1646 STATUS current 1647 DESCRIPTION 1648 "The control that allows creation and deletion of entries. 1649 Once made active an entry MAY not be modified except to 1650 delete it." 1651 ::= { mteEventEntry 5 } 1653 -- 1654 -- Event Notification Table 1655 -- 1657 mteEventNotificationTable OBJECT-TYPE 1658 SYNTAX SEQUENCE OF MteEventNotificationEntry 1659 MAX-ACCESS not-accessible 1660 STATUS current 1661 DESCRIPTION 1662 "A table of information about notifications to be sent as a 1663 consequence of management events." 1664 ::= { mteEvent 3 } 1666 mteEventNotificationEntry OBJECT-TYPE 1667 SYNTAX MteEventNotificationEntry 1668 MAX-ACCESS not-accessible 1669 STATUS current 1670 DESCRIPTION 1671 "Information about a single event's notification. Entries 1672 automatically exist in this this table for each mteEventEntry 1673 that has 'notification' set in mteEventActions." 1674 INDEX { mteOwner, IMPLIED mteEventName } 1675 ::= { mteEventNotificationTable 1 } 1677 MteEventNotificationEntry ::= SEQUENCE { 1678 mteEventNotification OBJECT IDENTIFIER, 1679 mteEventNotificationObjectsOwner SnmpAdminString, 1680 mteEventNotificationObjects SnmpAdminString 1681 } 1683 mteEventNotification OBJECT-TYPE 1684 SYNTAX OBJECT IDENTIFIER 1685 MAX-ACCESS read-write 1686 STATUS current 1687 DESCRIPTION 1688 "The object identifier from the NOTIFICATION-TYPE for the 1689 notification to use if metEventActions has 'notification' set." 1690 DEFVAL { zeroDotZero } 1691 ::= { mteEventNotificationEntry 1 } 1693 mteEventNotificationObjectsOwner OBJECT-TYPE 1694 SYNTAX SnmpAdminString (SIZE (0..32)) 1695 MAX-ACCESS read-write 1696 STATUS current 1697 DESCRIPTION 1698 "To go with mteEventNotificationObjects, the mteOwner of a 1699 group of objects from mteObjectsTable." 1700 DEFVAL { ''H } 1701 ::= { mteEventNotificationEntry 2 } 1703 mteEventNotificationObjects OBJECT-TYPE 1704 SYNTAX SnmpAdminString (SIZE (0..32)) 1705 MAX-ACCESS read-write 1706 STATUS current 1707 DESCRIPTION 1708 "The mteObjectsName of a group of objects from 1709 mteObjectsTable if mteEventActions has 'notification' set. 1710 These objects are to be added to any Notification generated by 1711 this event. 1713 Objects may also be added based on the trigger that stimulated 1714 the event. 1716 A length of 0 indicates no additional objects." 1717 DEFVAL { ''H } 1718 ::= { mteEventNotificationEntry 3 } 1720 -- 1721 -- Event Set Table 1722 -- 1724 mteEventSetTable OBJECT-TYPE 1725 SYNTAX SEQUENCE OF MteEventSetEntry 1726 MAX-ACCESS not-accessible 1727 STATUS current 1728 DESCRIPTION 1729 "A table of management event action information." 1730 ::= { mteEvent 4 } 1732 mteEventSetEntry OBJECT-TYPE 1733 SYNTAX MteEventSetEntry 1734 MAX-ACCESS not-accessible 1735 STATUS current 1736 DESCRIPTION 1737 "Information about a single event's set option. Entries 1738 automatically exist in this this table for each mteEventEntry 1739 that has 'set' set in mteEventActions." 1740 INDEX { mteOwner, IMPLIED mteEventName } 1741 ::= { mteEventSetTable 1 } 1743 MteEventSetEntry ::= SEQUENCE { 1744 mteEventSetObject OBJECT IDENTIFIER, 1745 mteEventSetObjectWildcard TruthValue, 1746 mteEventSetValue Integer32, 1747 mteEventSetTargetTag SnmpTagValue, 1748 mteEventSetContextName SnmpAdminString, 1749 mteEventSetContextNameWildcard TruthValue 1750 } 1752 mteEventSetObject OBJECT-TYPE 1753 SYNTAX OBJECT IDENTIFIER 1754 MAX-ACCESS read-write 1755 STATUS current 1756 DESCRIPTION 1757 "The object identifier from the MIB object to set if 1758 mteEventActions has 'set' set. 1760 This object identifier may be wildcarded by leaving 1761 sub-identifiers off the end, in which case 1762 nteEventSetObjectWildCard must be 'true'. 1764 If mteEventSetObject is wildcarded the instance used to set the 1765 object to which it points is the same as the instance from the 1766 value of mteTriggerValueID that triggered the event. 1768 Each instance that fills the wildcard is independent of any 1769 additional instances, that is, wildcarded objects operate 1770 as if there were a separate table entry for each instance 1771 that fills the wildcard without having to actually predict 1772 all possible instances ahead of time. 1774 Bad object identifiers or a mismatch between truncating the 1775 identifier and the value of mteSetObjectWildcard 1776 result in operation as one would expect when providing the 1777 wrong identifier to a Set operation. The Set will fail or set 1778 the wrong object. If the value syntax of the destination 1779 object is not correct, the Set fails with the normal SNMP 1780 error code." 1781 DEFVAL { zeroDotZero } 1782 ::= { mteEventSetEntry 1 } 1784 mteEventSetObjectWildcard OBJECT-TYPE 1785 SYNTAX TruthValue 1786 MAX-ACCESS read-write 1787 STATUS current 1788 DESCRIPTION 1789 "Control over whether mteEventSetObject is to be treated as 1790 fully-specified or wildcarded, with 'true' indicating wildcard 1791 if mteEventActions has 'set' set." 1792 DEFVAL { false } 1793 ::= { mteEventSetEntry 2 } 1795 mteEventSetValue OBJECT-TYPE 1796 SYNTAX Integer32 1797 MAX-ACCESS read-write 1798 STATUS current 1799 DESCRIPTION 1800 "The value to which to set the object at mteEventSetObject 1801 if mteEventActions has 'set' set." 1802 DEFVAL { 0 } 1803 ::= { mteEventSetEntry 3 } 1805 mteEventSetTargetTag OBJECT-TYPE 1806 SYNTAX SnmpTagValue 1807 MAX-ACCESS read-write 1808 STATUS current 1809 DESCRIPTION 1810 "The tag for the target(s) at which to set the object at 1811 mteEventSetObject to mteEventSetValue if mteEventActions 1812 has 'set' set. 1814 Systems limited to self management MAY not accept a non-zero 1815 length for the value of this object. 1817 A length of 0 indicates the local system. In this case, 1818 access to the objects indicated by mteEventSetObject is under 1819 the security credentials of the requester that set 1820 mteTriggerEntryStatus to 'active'. Those credentials are the 1821 input parameters for isAccessAllowed from the Architecture for 1822 Describing SNMP Management Frameworks. 1824 Otherwise access rights are checked according to the security 1825 parameters resulting from the tag." 1826 DEFVAL { ''H } 1827 ::= { mteEventSetEntry 4 } 1829 mteEventSetContextName OBJECT-TYPE 1830 SYNTAX SnmpAdminString 1831 MAX-ACCESS read-write 1832 STATUS current 1833 DESCRIPTION 1834 "The management context in which to set mteEventObjectID. 1835 if mteEventActions has 'set' set. 1837 This may be wildcarded by leaving characters off the end. To 1838 indicate such wildcarding mteEventSetContextNameWildcard must 1839 be 'true'. 1841 If this context name is wildcarded the value used to complete 1842 the wildcarding of mteTriggerContextName will be appended." 1843 DEFVAL { ''H } 1844 ::= { mteEventSetEntry 5 } 1846 mteEventSetContextNameWildcard OBJECT-TYPE 1847 SYNTAX TruthValue 1848 MAX-ACCESS read-write 1849 STATUS current 1850 DESCRIPTION 1851 "Control for whether mteEventSetContextName is to be treated as 1852 fully-specified or wildcarded, with 'true' indicating wildcard 1853 if mteEventActions has 'set' set." 1854 DEFVAL { false } 1855 ::= { mteEventSetEntry 6 } 1857 -- 1858 -- Notifications 1859 -- 1861 dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::= { dismanEventMIB 2 } 1862 dismanEventMIBNotifications OBJECT IDENTIFIER ::= 1863 { dismanEventMIBNotificationPrefix 0 } 1864 dismanEventMIBNotificationObjects OBJECT IDENTIFIER 1865 ::= { dismanEventMIBNotificationPrefix 1 } 1867 -- 1868 -- Notification Objects 1869 -- 1871 mteHotTrigger OBJECT-TYPE 1872 SYNTAX SnmpAdminString 1873 MAX-ACCESS accessible-for-notify 1874 STATUS current 1875 DESCRIPTION 1876 "The name of the trigger causing the notification." 1877 ::= { dismanEventMIBNotificationObjects 1 } 1879 mteHotTargetName OBJECT-TYPE 1880 SYNTAX SnmpAdminString 1881 MAX-ACCESS accessible-for-notify 1882 STATUS current 1883 DESCRIPTION 1884 "The SNMP Target MIB's snmpTargetAddrName related to the 1885 notification." 1886 ::= { dismanEventMIBNotificationObjects 2 } 1888 mteHotContextName OBJECT-TYPE 1889 SYNTAX SnmpAdminString 1890 MAX-ACCESS accessible-for-notify 1891 STATUS current 1892 DESCRIPTION 1893 "The context name related to the notification. This MUST be as 1894 fully-qualified as possible, including filling in wildcard 1895 information determined in processing." 1896 ::= { dismanEventMIBNotificationObjects 3 } 1898 mteHotOID OBJECT-TYPE 1899 SYNTAX OBJECT IDENTIFIER 1900 MAX-ACCESS accessible-for-notify 1901 STATUS current 1902 DESCRIPTION 1903 "The object identifier of the destination object related to the 1904 notification. This MUST be as fully-qualified as possible, 1905 inluding filling in wildcard information determined in 1906 processing. 1908 For a trigger-related notification this is from 1909 mteTriggerValueID. 1911 For a set failure this is from mteEventSetObject." 1912 ::= { dismanEventMIBNotificationObjects 4 } 1914 mteHotValue OBJECT-TYPE 1915 SYNTAX Integer32 1916 MAX-ACCESS accessible-for-notify 1917 STATUS current 1918 DESCRIPTION 1919 "The value of the object at mteTriggerValueID when a 1920 trigger fired." 1921 ::= { dismanEventMIBNotificationObjects 5 } 1923 mteFailedReason OBJECT-TYPE 1924 SYNTAX FailureReason 1925 MAX-ACCESS accessible-for-notify 1926 STATUS current 1927 DESCRIPTION 1928 "The reason for the failure of an attempt to check for a 1929 trigger condition or set an object in response to an event." 1930 ::= { dismanEventMIBNotificationObjects 6 } 1932 -- 1933 -- Notifications 1934 -- 1936 mteTriggerFired NOTIFICATION-TYPE 1937 OBJECTS { mteHotTrigger, 1938 mteHotTargetName, 1939 mteHotContextName, 1940 mteHotOID, 1941 mteHotValue } 1942 STATUS current 1943 DESCRIPTION 1944 "Notification that the trigger indicated by the object 1945 instances has fired, for triggers with mteTriggerType 1946 'boolean' or 'existence'." 1947 ::= { dismanEventMIBNotifications 1 } 1949 mteTriggerRising NOTIFICATION-TYPE 1950 OBJECTS { mteHotTrigger, 1951 mteHotTargetName, 1952 mteHotContextName, 1953 mteHotOID, 1954 mteHotValue } 1955 STATUS current 1956 DESCRIPTION 1957 "Notification that the rising threshold was met for triggers 1958 with mteTriggerType 'threshold'." 1959 ::= { dismanEventMIBNotifications 2 } 1961 mteTriggerFalling NOTIFICATION-TYPE 1962 OBJECTS { mteHotTrigger, 1963 mteHotTargetName, 1964 mteHotContextName, 1965 mteHotOID, 1966 mteHotValue } 1967 STATUS current 1968 DESCRIPTION 1969 "Notification that the falling threshold was met for triggers 1970 with mteTriggerType 'threshold'." 1971 ::= { dismanEventMIBNotifications 3 } 1973 mteTriggerFailure NOTIFICATION-TYPE 1974 OBJECTS { mteHotTrigger, 1975 mteHotTargetName, 1976 mteHotContextName, 1977 mteHotOID, 1978 mteFailedReason } 1979 STATUS current 1980 DESCRIPTION 1981 "Notification that an attempt to check a trigger has failed. 1983 The network manager must enable this notification only with 1984 a certain fear and trembling, as it can easily crowd out more 1985 important information. It should be used only to help diagnose 1986 a problem that has appeared in the error counters and can not 1987 be found otherwise." 1988 ::= { dismanEventMIBNotifications 4 } 1990 mteEventSetFailure NOTIFICATION-TYPE 1991 OBJECTS { mteHotTrigger, 1992 mteHotTargetName, 1993 mteHotContextName, 1994 mteHotOID, 1995 mteFailedReason } 1996 STATUS current 1997 DESCRIPTION 1998 "Notification that an attempt to do a set in response to an 1999 event has failed. 2001 The network manager must enable this notification only with 2002 a certain fear and trembling, as it can easily crowd out more 2003 important information. It should be used only to help diagnose 2004 a problem that has appeared in the error counters and can not 2005 be found otherwise." 2006 ::= { dismanEventMIBNotifications 5 } 2008 -- 2009 -- Conformance 2010 -- 2012 dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 } 2013 dismanEventMIBCompliances OBJECT IDENTIFIER ::= { dismanEventMIBConformance 1 } 2014 dismanEventMIBGroups OBJECT IDENTIFIER ::= { dismanEventMIBConformance 2 } 2016 -- Compliance 2018 dismanEventMIBCompliance MODULE-COMPLIANCE 2019 STATUS current 2020 DESCRIPTION 2021 "The compliance statement for entities which implement 2022 the Event MIB." 2023 MODULE -- this module 2024 MANDATORY-GROUPS { 2025 dismanEventResourceGroup, 2026 dismanEventTriggerGroup, 2027 dismanEventObjectsGroup, 2028 dismanEventEventGroup, 2029 dismanEventNotificationObjectGroup, 2030 dismanEventNotificationGroup 2031 } 2033 OBJECT mteTriggerTargetTag 2034 MIN-ACCESS read-only 2035 DESCRIPTION 2036 "Write access is not required, thus limiting 2037 monitoring to the local system or pre-configured 2038 remote systems." 2040 OBJECT mteEventSetTargetTag 2041 MIN-ACCESS read-only 2042 DESCRIPTION 2043 "Write access is not required, thus limiting 2044 setting to the local system or pre-configured 2045 remote systems." 2047 OBJECT mteTriggerValueIDWildcard 2048 MIN-ACCESS read-only 2049 DESCRIPTION 2050 "Write access is not required, thus allowing 2051 the system not to implement wildcarding." 2053 OBJECT mteTriggerContextNameWildcard 2054 MIN-ACCESS read-only 2055 DESCRIPTION 2056 "Write access is not required, thus allowing 2057 the system not to implement wildcarding." 2059 OBJECT mteObjectsIDWildcard 2060 MIN-ACCESS read-only 2061 DESCRIPTION 2062 "Write access is not required, thus allowing 2063 the system not to implement wildcarding." 2065 OBJECT mteEventSetContextNameWildcard 2066 MIN-ACCESS read-only 2067 DESCRIPTION 2068 "Write access is not required, thus allowing 2069 the system not to implement wildcarding." 2071 ::= { dismanEventMIBCompliances 1 } 2073 -- Units of Conformance 2075 dismanEventResourceGroup OBJECT-GROUP 2076 OBJECTS { 2077 mteResourceSampleMinimum, 2078 mteResourceSampleInstanceMaximum, 2079 mteResourceSampleInstances, 2080 mteResourceSampleInstancesHigh, 2081 mteResourceSampleInstanceLacks 2082 } 2083 STATUS current 2084 DESCRIPTION 2085 "Event resource status and control objects." 2086 ::= { dismanEventMIBGroups 1 } 2088 dismanEventTriggerGroup OBJECT-GROUP 2089 OBJECTS { 2090 mteTriggerFailures, 2092 mteTriggerComment, 2093 mteTriggerTest, 2094 mteTriggerSampleType, 2095 mteTriggerValueID, 2096 mteTriggerValueIDWildcard, 2097 mteTriggerTargetTag, 2098 mteTriggerContextName, 2099 mteTriggerContextNameWildcard, 2100 mteTriggerFrequency, 2101 mteTriggerObjectsOwner, 2102 mteTriggerObjects, 2103 mteTriggerEnabled, 2104 mteTriggerEntryStatus, 2106 mteTriggerDeltaDiscontinuityID, 2107 mteTriggerDeltaDiscontinuityIDWildcard, 2108 mteTriggerDeltaDiscontinuityIDType, 2110 mteTriggerExistenceTest, 2111 mteTriggerExistenceStartup, 2112 mteTriggerExistenceObjectsOwner, 2113 mteTriggerExistenceObjects, 2114 mteTriggerExistenceEventOwner, 2115 mteTriggerExistenceEvent, 2116 mteTriggerBooleanComparison, 2117 mteTriggerBooleanValue, 2118 mteTriggerBooleanStartup, 2119 mteTriggerBooleanObjectsOwner, 2120 mteTriggerBooleanObjects, 2121 mteTriggerBooleanEventOwner, 2122 mteTriggerBooleanEvent, 2124 mteTriggerThresholdStartup, 2125 mteTriggerThresholdObjectsOwner, 2126 mteTriggerThresholdObjects, 2127 mteTriggerThresholdRising, 2128 mteTriggerThresholdFalling, 2129 mteTriggerThresholdDeltaRising, 2130 mteTriggerThresholdDeltaFalling, 2131 mteTriggerThresholdRisingEventOwner, 2132 mteTriggerThresholdRisingEvent, 2133 mteTriggerThresholdFallingEventOwner, 2134 mteTriggerThresholdFallingEvent 2135 mteTriggerThresholdDeltaRisingEventOwner, 2136 mteTriggerThresholdDeltaRisingEvent, 2137 mteTriggerThresholdDeltaFallingEventOwner, 2138 mteTriggerThresholdDeltaFallingEvent 2139 } 2140 STATUS current 2141 DESCRIPTION 2142 "Event triggers." 2143 ::= { dismanEventMIBGroups 2 } 2145 dismanEventObjectsGroup OBJECT-GROUP 2146 OBJECTS { 2147 mteObjectsID, 2148 mteObjectsIDWildcard, 2149 mteObjectsEntryStatus 2150 } 2151 STATUS current 2152 DESCRIPTION 2153 "Supplemental objects." 2154 ::= { dismanEventMIBGroups 3 } 2156 dismanEventEventGroup OBJECT-GROUP 2157 OBJECTS { 2158 mteEventFailures, 2160 mteEventComment, 2161 mteEventActions, 2162 mteEventEnabled, 2163 mteEventEntryStatus, 2165 mteEventNotification, 2166 mteEventNotificationObjectsOwner, 2167 mteEventNotificationObjects, 2169 mteEventSetObject, 2170 mteEventSetObjectWildcard, 2171 mteEventSetValue, 2172 mteEventSetTargetTag, 2173 mteEventSetContextName, 2174 mteEventSetContextNameWildcard 2175 } 2176 STATUS current 2177 DESCRIPTION 2178 "Events." 2179 ::= { dismanEventMIBGroups 4 } 2181 dismanEventNotificationObjectGroup OBJECT-GROUP 2182 OBJECTS { 2183 mteHotTrigger, 2184 mteHotTargetName, 2185 mteHotContextName, 2186 mteHotOID, 2187 mteHotValue, 2188 mteFailedReason 2189 } 2190 STATUS current 2191 DESCRIPTION 2192 "Notification objects." 2193 ::= { dismanEventMIBGroups 5 } 2195 dismanEventNotificationGroup NOTIFICATION-GROUP 2196 NOTIFICATIONS { 2197 mteTriggerFired, 2198 mteTriggerRising, 2199 mteTriggerFalling, 2200 mteTriggerFailure, 2201 mteEventSetFailure 2202 } 2203 STATUS current 2204 DESCRIPTION 2205 "Notifications." 2207 ::= { dismanEventMIBGroups 6 } 2209 END 2210 9. Intellectual Property 2212 The IETF takes no position regarding the validity or scope of any 2213 intellectual property or other rights that might be claimed to pertain 2214 to the implementation or use of the technology described in this 2215 document or the extent to which any license under such rights might or 2216 might not be available; neither does it represent that it has made any 2217 effort to identify any such rights. Information on the IETF's 2218 procedures with respect to rights in standards-track and standards- 2219 related documentation can be found in BCP-11. Copies of claims of 2220 rights made available for publication and any assurances of licenses to 2221 be made available, or the result of an attempt made to obtain a general 2222 license or permission for the use of such proprietary rights by 2223 implementors or users of this specification can be obtained from the 2224 IETF Secretariat. 2226 The IETF invites any interested party to bring to its attention any 2227 copyrights, patents or patent applications, or other proprietary rights 2228 which may cover technology that may be required to practice this 2229 standard. Please address the information to the IETF Executive 2230 Director. 2232 10. Acknowledgements 2234 This MIB contains considerable contributions from the RMON MIB, the 2235 Distributed Management Design Team (Andy Bierman, Maria Greene, Bob 2236 Stewart, and Steve Waldbusser), the Distributed Management Working 2237 Group, and colleagues at Cisco. 2239 11. References 2241 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 2242 for Describing SNMP Management Frameworks", RFC 2571, April 2243 1999 2245 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 2246 of Management Information for TCP/IP-based Internets", STD 2247 16, RFC 1155, May 1990 2249 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 2250 16, RFC 1212, March 1991 2252 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 2253 SNMP", RFC 1215, March 1991 2255 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2256 Rose, M., and S. Waldbusser, "Structure of Management 2257 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 2259 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2260 Rose, M., and S. Waldbusser, "Textual Conventions for 2261 SMIv2", STD 58, RFC 2579, April 1999 2263 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 2264 Rose, M., and S. Waldbusser, "Conformance Statements for 2265 SMIv2", STD 58, RFC 2580, April 1999 2267 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2268 Network Management Protocol", STD 15, RFC 1157, May 1990. 2270 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2271 "Introduction to Community-based SNMPv2", RFC 1901, January 2272 1996. 2274 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2275 "Transport Mappings for Version 2 of the Simple Network 2276 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2278 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2279 Processing and Dispatching for the Simple Network Management 2280 Protocol (SNMP)", RFC 2572, April 1999 2282 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 2283 (USM) for version 3 of the Simple Network Management 2284 Protocol (SNMPv3)", RFC 2574, April 1999 2286 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2287 "Protocol Operations for Version 2 of the Simple Network 2288 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2290 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 2291 RFC 2573, April 1999 2293 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2294 Access Control Model (VACM) for the Simple Network 2295 Management Protocol (SNMP)", RFC 2575, April 1999 2297 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2298 "Introduction to Version 3 of the Internet-standard Network 2299 Management Framework", RFC 2570, April 1999 2301 [RFC1903] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 2302 "Coexistence between Version 1 and version 2 of the 2303 Internet-standard Network Management Framework", RFC 1903, 2304 January 1996. 2306 [RFCEventMIB] 2307 Stewart, B., "Event MIB", RFC ????, ?Month? 1999. 2309 [RFC1757] 2310 Waldbusser, S., "Remote Network Monitoring Management Information 2311 Base", RFC 1757, February 1995. 2313 [RFC1451] 2314 Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to- 2315 Manager Management Information Base", RFC 1451, April 1993. 2317 [RFCExpressionMIB] 2318 Stewart, B., "Expression MIB", RFC ????, ?Month? 1999. 2320 [RFCNotificationLogMIB] 2321 Stewart, B., "Notification Log MIB", RFC ????, ?Month? 1999. 2323 12. Security Considerations 2325 Security issues are discussed in the Security section and in the 2326 DESCRIPTION clauses of relevant objects. 2328 13. Author's Address 2330 Bob Stewart 2331 Cisco Systems, Inc. 2332 170 West Tasman Drive 2333 San Jose, CA 95134-1706 2334 U.S.A. 2336 14. Editor's Address 2338 Ramanathan Kavasseri 2339 Cisco Systems, Inc. 2340 170 West Tasman Drive 2341 San Jose, CA 95134-1706 2342 U.S.A. 2344 Phone: +1 408 527 2446 2345 Email: ramk@cisco.com 2347 15. Full Copyright Statement 2349 Copyright (C) The Internet Society (1999). All Rights Reserved. 2351 This document and translations of it may be copied and furnished to 2352 others, and derivative works that comment on or otherwise explain it or 2353 assist in its implementation may be prepared, copied, published and 2354 distributed, in whole or in part, without restriction of any kind, 2355 provided that the above copyright notice and this paragraph are included 2356 on all such copies and derivative works. However, this document itself 2357 may not be modified in any way, such as by removing the copyright notice 2358 or references to the Internet Society or other Internet organizations, 2359 except as needed for the purpose of developing Internet standards in 2360 which case the procedures for copyrights defined in the Internet 2361 Standards process must be followed, or as required to translate it into 2362 languages other than English. 2364 The limited permissions granted above are perpetual and will not be 2365 revoked by the Internet Society or its successors or assigns. 2367 This document and the information contained herein is provided on an "AS 2368 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2369 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2370 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 2371 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 2372 FITNESS FOR A PARTICULAR PURPOSE. 2374 Table of Contents 2376 1 Abstract ........................................................ 2 2377 2 The SNMP Management Framework ................................... 2 2378 3 Overview ........................................................ 4 2379 4 Relationship to Other MIBs ...................................... 4 2380 5 MIB Sections .................................................... 4 2381 6 Operation ....................................................... 7 2382 7 Security ........................................................ 8 2383 8 Definitions ..................................................... 10 2384 9 Intellectual Property ........................................... 53 2385 10 Acknowledgements ............................................... 54 2386 11 References ..................................................... 55 2387 12 Security Considerations ........................................ 57 2388 13 Author's Address ............................................... 57 2389 14 Editor's Address ............................................... 57 2390 15 Full Copyright Statement ....................................... 58