idnits 2.17.1 draft-ietf-disman-event-mib-v2-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2467. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2439. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2446. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2452. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 4 longer pages, the longest (page 3) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 8. Security Considerations' ) ** 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.) (A line matching the expected section header was found, but with an unexpected indentation: ' 9. IANA Considerations' ) ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 213: '...ment only system MAY not implement rem...' RFC 2119 keyword, line 215: '... the application SHOULD use a GetNext-...' RFC 2119 keyword, line 227: '...ion. These error notifications SHOULD...' RFC 2119 keyword, line 230: '... concern they SHOULD be transmitted ...' RFC 2119 keyword, line 233: '... Log MIB is REQUIRED, since in fact ...' (13 more instances...) -- The abstract seems to indicate that this document obsoletes RFC2981, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 393 has weird spacing: '...achable can't...' -- 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 (July 2005) is 6857 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 section? 'RFC2981' on line 2371 looks like a reference -- Missing reference section? 'RFC3410' on line 2381 looks like a reference -- Missing reference section? 'RFC2578' on line 2345 looks like a reference -- Missing reference section? 'RFC2579' on line 2350 looks like a reference -- Missing reference section? 'RFC2580' on line 2354 looks like a reference -- Missing reference section? 'RFC2819' on line 2368 looks like a reference -- Missing reference section? 'RFC1451' on line 2364 looks like a reference -- Missing reference section? 'RFC3413' on line 2385 looks like a reference -- Missing reference section? 'RFC3014' on line 2378 looks like a reference -- Missing reference section? 'RFC2982' on line 2373 looks like a reference -- Missing reference section? 'RFC3416' on line 2358 looks like a reference -- Missing reference section? 'RFC3415' on line 2389 looks like a reference Summary: 8 errors (**), 0 flaws (~~), 3 warnings (==), 20 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Disman Working Group R. Kavasseri 3 Internet Draft B. Claise 4 Category: Standards Track Cisco Systems 5 Obsolete: 2981 6 Document: draft-ietf-disman-event-mib-v2-06.txt 7 Expires: January 18, 2006 July 2005 9 Event MIB 11 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six 23 months and may be updated, replaced, or obsoleted by other documents 24 at any time. It is inappropriate to use Internet-Drafts as 25 reference material or to cite them other than as "work in progress". 27 The list of current Internet-Drafts can be accessed at 28 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 32 This Internet-Draft will expire on January 18, 2006. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). 38 Abstract 40 This memo defines a portion of the Management Information 41 Base (MIB) for use with network management protocols in the Internet 42 community. In particular, it describes managed objects that can be 43 used to manage and monitor MIB objects and take action through 44 events. This document obsoletes RFC 2981. 46 The Event MIB provides the ability to monitor MIB objects on the 47 local system or on a remote system and take simple action when a 48 trigger condition is met. 50 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 52 Kavasseri and Claise Standard Track 1 53 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 54 document are to be interpreted as described in RFC 2119. 56 Table of Contents 58 1. Introduction...................................................3 59 2. The Internet-Standard Management Framework.....................3 60 3. Relationship to Other MIBs.....................................3 61 4. MIB Sections...................................................4 62 5. Operation......................................................5 63 6. Security.......................................................6 64 7. Definitions....................................................7 65 8. Security Considerations.......................................51 66 9. IANA Considerations...........................................51 67 10. References..................................................51 68 10.1 Informative References.....................................51 69 10.2 Informative References.....................................51 70 11. Acknowledgements............................................52 72 Kavasseri and Claise Standard Track 2 73 1. Introduction 75 With network sizes well beyond the ability of people to manage them 76 directly, automated, distributed management is vital. An important 77 aspect of such management is the ability of a system to monitor 78 itself or for some other system to monitor it. 80 The Event MIB provides the ability to monitor MIB objects on the 81 local system or on a remote system and take simple action when a 82 trigger condition is met. 84 The MIB is intended to suit either a relatively powerful manager or 85 mid-level manager, as well as a somewhat more limited self-managing 86 system. 88 This document obsoletes RFC 2981 [RFC2981]. 90 2. The Internet-Standard Management Framework 92 For a detailed overview of the documents that describe the current 93 Internet-Standard Management Framework, please refer to section 7 of 94 RFC 3410 [RFC3410]. 96 Managed objects are accessed via a virtual information store, termed 97 the Management Information Base or MIB. MIB objects are generally 98 accessed through the Simple Network Management Protocol (SNMP). 99 Objects in the MIB are defined using the mechanisms defined in the 100 Structure of Management Information (SMI). This memo specifies a 101 MIB module that is compliant to the SMIv2, which is described in STD 102 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 103 2580 [RFC2580]. 105 3. Relationship to Other MIBs 107 The Event MIB is based on extensive experience with the RMON MIB 108 [RFC2819] and provides a superset of the capabilities of the RMON 109 alarm and event groups. Conceptually, the key extension is the 110 ability to allow alarms to be generated for MIB objects that are on 111 another network element. The Event MIB calls "triggers" what the 112 RMON MIB called "alarms," but the concepts are the same. Event MIB 113 triggers maintain the RMON handling of thresholds and add the 114 concept of booleans. Event MIB events maintain the RMON concept of 115 sending an SNMP notification in response to a trigger and add the 116 concept of setting a MIB object. 118 The Event MIB is the successor and update to SNMPv2's Manager-to- 119 Manager MIB [RFC1451] which was declared Historic pending this work. 121 Kavasseri and Claise Standard Track 3 122 The Event MIB depends on the services of the SNMPv3 Management 123 Target [RFC3413] and Notification MIBs [RFC3014]. 125 The Event MIB is nicely complemented by the Distributed Management 126 Expression MIB [RFC2982], which is the expected source of boolean 127 objects to monitor. Note that there is considerable overlap between 128 the wildcard and delta sample capabilities of the Event and 129 Expression MIBs. A carefully-planned implementation might well use 130 common code to provide the overlapping functions. 132 4. MIB Sections 134 The MIB has four sections: triggers, objects, events, and 135 notifications. Triggers define the conditions that lead to events. 136 Events may cause notifications, may set MIB objects, or both. 138 The trigger table lists what objects are to be monitored and how and 139 relates each trigger to an event. It has supplementary, companion 140 tables for additional objects that depend on the type of test done 141 for the trigger. 143 The objects table lists objects that can be added to notifications 144 based on the trigger, the trigger test type, or the event that 145 resulted in the notification. 147 The event table defines what happens when an event is triggered: 148 sending a notification, setting a MIB object or both. It has 149 supplementary, companion tables for additional objects that depend 150 on the action taken. 152 The notification section defines a set of generic notifications to 153 go with the events and for Event MIB error handling, and it defines 154 a set of objects to put in those notifications. 156 The following diagram describes the relationships between the tables 157 in the Event MIB. 159 +-----------------------------+ 160 | mteTriggerEntry | subclassed by: 161 | { mteOwner, |---+ 162 | IMPLIED mteTriggerName } | +-- mteTriggerDeltaEntry 163 | | | 164 | | +-- mteTriggerExistenceEntry 165 | | | 166 | | +-- mteTriggerBooleanEntry 167 | | | 168 | | +-- mteTriggerThresholdEntry 169 | | 170 | mteTrigger*Event -------------------------------->+ 171 | | | 172 | mteTrigger*Objects ----------------->+ | 174 Kavasseri and Claise Standard Track 4 175 +-----------------------------+ | | 176 | | 177 +-----------------------------+ V | 178 | mteObjectsEntry | | | 179 | { mteOwner, |<-------------+ | 180 | mteObjectsName, | | 181 | mteObjectsIndex } | | 182 +-----------------------------+ | 183 V 184 +---------------------------+ | 185 | mteEventEntry |<----------------------------+ 186 | { mteOwner, | 187 | IMPLIED mteEventName } | 188 | | 189 | mteEventAction---> + (condition) 190 +---------------------------+ | 191 V 192 +---------------------------+ | +--------------------------+ 193 | mteEventNotificationEntry | | | mteEventSetEntry | 194 | { mteOwner, |<--+-->| { mteOwner, | 195 | IMPLIED mteEventName } | | IMPLIED mteEventName } | 196 +---------------------------+ +---------------------------+ 198 5. Operation 200 The Event MIB is instrumentation for a distributed management 201 application that monitors MIB objects. In its simplest form this 202 application monitors individual, local MIB objects, just as an RMON 203 probe fulfills the functions implied by RMON's alarm and event 204 operation. Additionally the application can monitor remote objects 205 and wildcarded groups of objects. 207 Remote monitoring uses the tag service of the Management Target MIB 208 [RFC3413] to select and access remote systems as an ordinary SNMP- 209 based management application. Local monitoring may be via a more 210 intimate, local interface which may, for example, bypass SNMP 211 encoding but otherwise is functionally identical to remote SNMP 212 operation, including the application of access control. A self- 213 management only system MAY not implement remote monitoring. 215 Wildcards indicate that the application SHOULD use a GetNext-type 216 operation to find the zero or more instances implied by a truncated 217 object identifier, just like an ordinary SNMP-based management 218 application. Each instance of a wildcard is treated as if it were a 219 separate entry, that is the instances of a wildcarded object are 220 independent of one another. For example, a wild-carded object may 221 trigger an event, and result in the setting of another wildcarded 222 object. The instance that satisfied the trigger function is used to 223 perform the set function. All of this takes place independently of 224 any additional instances that may fill the wildcard. 226 Kavasseri and Claise Standard Track 5 227 Error handling is by notification. These error notifications SHOULD 228 be enabled only for the diagnosis of problems indicated by error 229 counters. If minimizing the probability of notification loss is a 230 concern they SHOULD be transmitted as Inform PDUs as described in 231 the [RFC3416] or directed to a log as described in the Notification 232 Log MIB [RFC3014]. Note that this does not mean the Notification 233 Log MIB is REQUIRED, since in fact notifications usually are not 234 lost, but that the Notification Log MIB can be helpful with this as 235 well as other MIBs that include notifications. 237 Although like most MIBs this one has no explicit controls for the 238 persistence of the values set in configuring events, a robust, 239 polite implementation would certainly not force its managing 240 applications to reconfigure it whenever it resets. 242 Again, as with most MIBs, it is implementation-specific how a system 243 provides and manages such persistence. To speculate, one could 244 imagine, for example, that persistence depended on the context in 245 which the expression was configured, or perhaps system-specific 246 characteristics of the expression's owner. Or perhaps everything in 247 a MIB such as this one, which is clearly aimed at persistent 248 configuration, is automatically part of a system's other persistent 249 configuration. 251 6. Security 253 Security of Event MIB entries depends on SNMPv3 access control for 254 the entire MIB or for subsets based on entry owner names. 256 Security of monitored objects for remote access depends on the 257 Management Target MIB [RFC3413]. Security for local access can 258 depend on the Management Target MIB or on recording appropriate 259 security credentials of the creator of an entry and using those to 260 access the local objects. These security credentials are the 261 parameters necessary as inputs to isAccessAllowed from the 262 Architecture for Describing SNMP Management Frameworks. When 263 accessing local objects without using a local target tag, the system 264 MUST (conceptually) use isAccessAllowed to ensure that it does not 265 violate security. 267 To facilitate the provisioning of access control by a security 268 administrator for this MIB itself using the View-Based Access 269 Control Model (VACM) defined in RFC 3415 [RFC3415] for tables in 270 which multiple users may need to independently create or modify 271 entries, the initial index is used as an "owner index". Such an 272 initial index has a syntax of SnmpAdminString, and can thus be 273 trivially mapped to a securityName or groupName as defined in VACM, 274 in accordance with a security policy. 276 Kavasseri and Claise Standard Track 6 277 If a security administrator were to employ such an approach, all 278 entries in related tables belonging to a particular user will have 279 the same value for this initial index. For a given user's entries 280 in a particular table, the object identifiers for the information in 281 these entries will have the same sub-identifiers (except for the 282 "column" sub-identifier) up to the end of the encoded owner index. 283 To configure VACM to permit access to this portion of the table, one 284 would create vacmViewTreeFamilyTable entries with the value of 285 vacmViewTreeFamilySubtree including the owner index portion, and 286 vacmViewTreeFamilyMask "wildcarding" the column sub-identifier. 287 More elaborate configurations are possible. 289 7. Definitions 291 DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN 293 IMPORTS 294 MODULE-IDENTITY, OBJECT-TYPE, 295 Integer32, Unsigned32, 296 NOTIFICATION-TYPE, Counter32, 297 Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI 298 TEXTUAL-CONVENTION, RowStatus, 299 TruthValue, StorageType FROM SNMPv2-TC 300 MODULE-COMPLIANCE, OBJECT-GROUP, 301 NOTIFICATION-GROUP FROM SNMPv2-CONF 302 sysUpTime FROM SNMPv2-MIB 303 SnmpTagValue FROM SNMP-TARGET-MIB 304 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 306 dismanEventMIB MODULE-IDENTITY 307 LAST-UPDATED "200506030000Z" -- 03 June 2005 308 ORGANIZATION "IETF Distributed Management Working Group" 309 CONTACT-INFO "Ramanathan Kavasseri 310 Cisco Systems, Inc. 311 170 West Tasman Drive, 312 San Jose CA 95134-1706. 313 Phone: +1 408 526 4527 314 Email: ramk@cisco.com 316 Benoit Claise 317 Cisco Systems, Inc. 318 Pegasus Parc 319 7 De Kleetlan Diegem 320 Brabant, Belgium 1831. 321 Phone: +32 (0)2 704 5622 323 Kavasseri and Claise Standard Track 7 324 Email: bclaise@cisco.com 325 " 326 DESCRIPTION 327 " The MIB module for defining Managed Triggered Event (MTE) 328 and actions for network management purposes. 330 Copyright (C) The Internet Society 2005. This version of this 331 MIB module is part of RFC yyyy; see the RFC itself for full 332 legal notices." 333 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 334 -- Revision History 335 REVISION "200506030000Z" -- 03 June 2005 336 DESCRIPTION "Correction for StorageType." 338 REVISION "200408270000Z" -- 27 August 2004 339 DESCRIPTION "Updated contact info, copyright statement to 340 the MIB module description." 342 REVISION "200306130000Z" -- 13 June 2003 343 DESCRIPTION "Added copyright statement to the MIB module 344 description." 346 REVISION "200111140000Z" -- 14 November 2001 347 DESCRIPTION "Updated the DESCRIPTION clauses of 348 mteEventEntryStatus, mteTriggerEnabled and 349 mteTriggerEntryStatus." 351 REVISION "200010160000Z" -- 16 October 2000 352 DESCRIPTION "This is the initial version of this MIB. 353 Published as RFC 2981" 354 ::= { mib-2 88 } 356 dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 } 358 -- Management Triggered Event (MTE) objects 360 mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 } 361 mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 } 362 mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 } 363 mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 } 365 -- 366 -- Textual Conventions 367 -- 369 Kavasseri and Claise Standard Track 8 370 FailureReason ::= TEXTUAL-CONVENTION 371 STATUS current 372 DESCRIPTION 373 "Reasons for failures in an attempt to perform a management 374 request. 376 The first group of errors, numbered less than 0, are related 377 to problems in sending the request. The existence of a 378 particular error code here does not imply that all 379 implementations are capable of sensing that error and 380 returning that code. 382 The second group, numbered greater than 0, are copied 383 directly from SNMP protocol operations and are intended to 384 carry exactly the meanings defined for the protocol as returned 385 in an SNMP response. 387 localResourceLack some local resource such as memory 388 lacking or 389 mteResourceSampleInstanceMaximum 390 exceeded 391 badDestination unrecognized domain name or otherwise 392 invalid destination address 393 destinationUnreachable can't get to destination address 394 noResponse no response to SNMP request 395 badType the data syntax of a retrieved object 396 as not as expected 397 sampleOverrun another sample attempt occurred before 398 the previous one completed" 400 SYNTAX INTEGER { sampleOverrun(-6), 401 badType(-5), 402 noResponse(-4), 403 destinationUnreachable(-3), 404 badDestination(-2), 405 localResourceLack(-1), 407 noError(0), 409 tooBig(1), 410 noSuchName(2), 411 badValue(3), 412 readOnly(4), 413 genErr(5), 414 noAccess(6), 416 Kavasseri and Claise Standard Track 9 417 wrongType(7), 418 wrongLength(8), 419 wrongEncoding(9), 420 wrongValue(10), 421 noCreation(11), 422 inconsistentValue(12), 423 resourceUnavailable(13), 424 commitFailed(14), 425 undoFailed(15), 426 authorizationError(16), 427 notWritable(17), 428 inconsistentName(18) } 429 -- 430 -- Resource Control Section 431 -- 433 mteResourceSampleMinimum OBJECT-TYPE 434 SYNTAX Integer32 (1..2147483647) 435 UNITS "seconds" 436 MAX-ACCESS read-write 437 STATUS current 438 DESCRIPTION 439 "The minimum mteTriggerFrequency this system will 440 accept. A system may use the larger values of this minimum to 441 lessen the impact of constant sampling. For larger 442 sampling intervals the system samples less often and 443 suffers less overhead. This object provides a way to enforce 444 such lower overhead for all triggers created after it is 445 set. 447 Unless explicitly resource limited, a system's value for 448 this object SHOULD be 1, allowing as small as a 1 second 449 interval for ongoing trigger sampling. 451 Changing this value will not invalidate an existing setting 452 of mteTriggerFrequency." 453 ::= { mteResource 1 } 455 mteResourceSampleInstanceMaximum OBJECT-TYPE 456 SYNTAX Unsigned32 457 UNITS "instances" 458 MAX-ACCESS read-write 459 STATUS current 460 DESCRIPTION 461 "The maximum number of instance entries this system will 463 Kavasseri and Claise Standard Track 10 464 support for sampling. 466 These are the entries that maintain state, one for each 467 instance of each sampled object as selected by 468 mteTriggerValueID. Note that wildcarded objects result 469 in multiple instances of this state. 471 A value of 0 indicates no preset limit, that is, the limit 472 is dynamic based on system operation and resources. 474 Unless explicitly resource limited, a system's value for 475 this object SHOULD be 0. 477 Changing this value will not eliminate or inhibit existing 478 sample state but could prevent allocation of additional state 479 information." 480 ::= { mteResource 2 } 482 mteResourceSampleInstances OBJECT-TYPE 483 SYNTAX Gauge32 484 UNITS "instances" 485 MAX-ACCESS read-only 486 STATUS current 487 DESCRIPTION 488 "The number of currently active instance entries as 489 defined for mteResourceSampleInstanceMaximum." 490 ::= { mteResource 3 } 492 mteResourceSampleInstancesHigh OBJECT-TYPE 493 SYNTAX Gauge32 494 UNITS "instances" 495 MAX-ACCESS read-only 496 STATUS current 497 DESCRIPTION 498 "The highest value of mteResourceSampleInstances that has 499 occurred since initialization of the management system." 500 ::= { mteResource 4 } 502 mteResourceSampleInstanceLacks OBJECT-TYPE 503 SYNTAX Counter32 504 UNITS "instances" 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "The number of times this system could not take a new sample 510 Kavasseri and Claise Standard Track 11 511 because that allocation would have exceeded the limit set by 512 mteResourceSampleInstanceMaximum." 513 ::= { mteResource 5 } 515 -- 516 -- Trigger Section 517 -- 519 -- Counters 521 mteTriggerFailures OBJECT-TYPE 522 SYNTAX Counter32 523 UNITS "failures" 524 MAX-ACCESS read-only 525 STATUS current 526 DESCRIPTION 527 "The number of times an attempt to check for a trigger 528 condition has failed. This counts individually for each 529 attempt in a group of targets or each attempt for a 530 wildcarded object." 531 ::= { mteTrigger 1 } 533 -- 534 -- Trigger Table 535 -- 537 mteTriggerTable OBJECT-TYPE 538 SYNTAX SEQUENCE OF MteTriggerEntry 539 MAX-ACCESS not-accessible 540 STATUS current 541 DESCRIPTION 542 "A table of management event trigger information." 543 ::= { mteTrigger 2 } 545 mteTriggerEntry OBJECT-TYPE 546 SYNTAX MteTriggerEntry 547 MAX-ACCESS not-accessible 548 STATUS current 549 DESCRIPTION 550 "Information about a single trigger. Applications create and 551 delete entries using mteTriggerEntryStatus." 552 INDEX { mteOwner, IMPLIED mteTriggerName } 553 ::= { mteTriggerTable 1 } 555 MteTriggerEntry ::= SEQUENCE { 557 Kavasseri and Claise Standard Track 12 558 mteOwner SnmpAdminString, 559 mteTriggerName SnmpAdminString, 560 mteTriggerComment SnmpAdminString, 561 mteTriggerTest BITS, 562 mteTriggerSampleType INTEGER, 563 mteTriggerValueID OBJECT IDENTIFIER, 564 mteTriggerValueIDWildcard TruthValue, 565 mteTriggerTargetTag SnmpTagValue, 566 mteTriggerContextName SnmpAdminString, 567 mteTriggerContextNameWildcard TruthValue, 568 mteTriggerFrequency Unsigned32, 569 mteTriggerObjectsOwner SnmpAdminString, 570 mteTriggerObjects SnmpAdminString, 571 mteTriggerEnabled TruthValue, 572 mteTriggerEntryStatus RowStatus, 573 mteTriggerEntryStorageType StorageType 574 } 576 mteOwner OBJECT-TYPE 577 SYNTAX SnmpAdminString (SIZE(0..32)) 578 MAX-ACCESS not-accessible 579 STATUS current 580 DESCRIPTION 581 "The owner of this entry. The exact semantics of this 582 string are subject to the security policy defined by the 583 security administrator." 584 ::= { mteTriggerEntry 1 } 586 mteTriggerName OBJECT-TYPE 587 SYNTAX SnmpAdminString (SIZE (1..32)) 588 MAX-ACCESS not-accessible 589 STATUS current 590 DESCRIPTION 591 "A locally-unique, administratively assigned name for the 592 trigger within the scope of mteOwner." 593 ::= { mteTriggerEntry 2 } 595 mteTriggerComment OBJECT-TYPE 596 SYNTAX SnmpAdminString 597 MAX-ACCESS read-create 598 STATUS current 599 DESCRIPTION 600 "A description of the trigger's function and use." 601 DEFVAL { ''H } 602 ::= { mteTriggerEntry 3 } 604 Kavasseri and Claise Standard Track 13 605 mteTriggerTest OBJECT-TYPE 606 SYNTAX BITS { existence(0), boolean(1), threshold(2) } 607 MAX-ACCESS read-create 608 STATUS current 609 DESCRIPTION 610 "The type of trigger test to perform. For 'boolean' and 611 'threshold' tests, the object at mteTriggerValueID MUST 612 evaluate to an integer, that is, anything that ends up encoded 613 for transmission (that is, in BER, not ASN.1) as an integer. 615 For 'existence', the specific test is as selected by 616 mteTriggerExistenceTest. When an object appears, vanishes 617 or changes value, the trigger fires. If the object's 618 appearance caused the trigger firing, the object MUST 619 vanish before the trigger can be fired again for it, and 620 vice versa. If the trigger fired due to a change in the 621 object's value, it will be fired again on every successive 622 value change for that object. 624 For 'boolean', the specific test is as selected by 625 mteTriggerBooleanTest. If the test result is true the trigger 626 fires. The trigger will not fire again until the value has 627 become false and come back to true. 629 For 'threshold' the test works as described below for 630 mteTriggerThresholdStartup, mteTriggerThresholdRising, and 631 mteTriggerThresholdFalling. 633 Note that combining 'boolean' and 'threshold' tests on the 634 same object may be somewhat redundant." 635 DEFVAL { { boolean } } 636 ::= { mteTriggerEntry 4 } 638 mteTriggerSampleType OBJECT-TYPE 639 SYNTAX INTEGER { absoluteValue(1), deltaValue(2) } 640 MAX-ACCESS read-create 641 STATUS current 642 DESCRIPTION 643 "The type of sampling to perform. 645 An 'absoluteValue' sample requires only a single sample to be 646 meaningful, and is exactly the value of the object at 647 mteTriggerValueID at the sample time. 649 Kavasseri and Claise Standard Track 14 650 A 'deltaValue' requires two samples to be meaningful and is 651 thus not available for testing until the second and subsequent 652 samples after the object at mteTriggerValueID is first found 653 to exist. It is the difference between the two samples. For 654 unsigned values it is always positive, based on unsigned 655 arithmetic. For signed values it can be positive or negative. 657 For SNMP counters to be meaningful they should be sampled as a 658 'deltaValue'. 660 For 'deltaValue' mteTriggerDeltaTable contains further 661 parameters. 663 If only 'existence' is set in mteTriggerTest this object has 664 no meaning." 665 DEFVAL { absoluteValue } 666 ::= { mteTriggerEntry 5 } 668 mteTriggerValueID OBJECT-TYPE 669 SYNTAX OBJECT IDENTIFIER 670 MAX-ACCESS read-create 671 STATUS current 672 DESCRIPTION 673 "The object identifier of the MIB object to sample to see 674 if the trigger should fire. 676 This may be wildcarded by truncating all or part of the 677 instance portion, in which case the value is obtained 678 as if with a GetNext function, checking multiple values 679 if they exist. If such wildcarding is applied, 680 mteTriggerValueIDWildcard must be 'true' and if not it must 681 be 'false'. 683 Bad object identifiers or a mismatch between truncating the 684 identifier and the value of mteTriggerValueIDWildcard result 685 in operation as one would expect when providing the wrong 686 identifier to a Get or GetNext operation. The Get will fail 687 or get the wrong object. The GetNext will indeed get whatever 688 is next, proceeding until it runs past the initial part of the 689 identifier and perhaps many unintended objects for confusing 690 results. If the value syntax of those objects is not usable, 691 that results in a 'badType' error that terminates the scan. 693 Each instance that fills the wildcard is independent of any 694 additional instances, that is, wildcarded objects operate 696 Kavasseri and Claise Standard Track 15 697 as if there were a separate table entry for each instance 698 that fills the wildcard without having to actually predict 699 all possible instances ahead of time." 700 DEFVAL { zeroDotZero } 701 ::= { mteTriggerEntry 6 } 703 mteTriggerValueIDWildcard OBJECT-TYPE 704 SYNTAX TruthValue 705 MAX-ACCESS read-create 706 STATUS current 707 DESCRIPTION 708 "Control for whether mteTriggerValueID is to be treated as 709 fully-specified or wildcarded, with 'true' indicating 710 wildcard." 711 DEFVAL { false } 712 ::= { mteTriggerEntry 7 } 714 mteTriggerTargetTag OBJECT-TYPE 715 SYNTAX SnmpTagValue 716 MAX-ACCESS read-create 717 STATUS current 718 DESCRIPTION 719 "The tag for the target(s) from which to obtain the condition 720 for a trigger check. 722 A length of 0 indicates the local system. In this case, 723 access to the objects indicated by mteTriggerValueID is under 724 the security credentials of the requester that set 725 mteTriggerEntryStatus to 'active'. Those credentials are the 726 input parameters for isAccessAllowed from the Architecture for 727 Describing SNMP Management Frameworks. 729 Otherwise access rights are checked according to the security 730 parameters resulting from the tag." 731 DEFVAL { ''H } 732 ::= { mteTriggerEntry 8 } 734 mteTriggerContextName OBJECT-TYPE 735 SYNTAX SnmpAdminString 736 MAX-ACCESS read-create 737 STATUS current 738 DESCRIPTION 739 "The management context from which to obtain mteTriggerValueID. 741 This may be wildcarded by leaving characters off the end. For 743 Kavasseri and Claise Standard Track 16 744 example use 'Repeater' to wildcard to 'Repeater1', 745 'Repeater2', 'Repeater-999.87b', and so on. To indicate such 746 wildcarding is intended, mteTriggerContextNameWildcard must 747 be 'true'. 749 Each instance that fills the wildcard is independent of any 750 additional instances, that is, wildcarded objects operate 751 as if there were a separate table entry for each instance 752 that fills the wildcard without having to actually predict 753 all possible instances ahead of time. 755 Operation of this feature assumes that the local system has a 756 list of available contexts against which to apply the 757 wildcard. If the objects are being read from the local 758 system, this is clearly the system's own list of contexts. 759 For a remote system a local version of such a list is not 760 defined by any current standard and may not be available, so 761 this function MAY not be supported." 762 DEFVAL { ''H } 763 ::= { mteTriggerEntry 9 } 765 mteTriggerContextNameWildcard OBJECT-TYPE 766 SYNTAX TruthValue 767 MAX-ACCESS read-create 768 STATUS current 769 DESCRIPTION 770 "Control for whether mteTriggerContextName is to be treated as 771 fully-specified or wildcarded, with 'true' indicating 772 wildcard." 773 DEFVAL { false } 774 ::= { mteTriggerEntry 10 } 776 mteTriggerFrequency OBJECT-TYPE 777 SYNTAX Unsigned32 778 UNITS "seconds" 779 MAX-ACCESS read-create 780 STATUS current 781 DESCRIPTION 782 "The number of seconds to wait between trigger samples. To 783 encourage consistency in sampling, the interval is measured 784 from the beginning of one check to the beginning of the next 785 and the timer is restarted immediately when it expires, not 786 when the check completes. 788 If the next sample begins before the previous one completed the 790 Kavasseri and Claise Standard Track 17 791 system may either attempt to make the check or treat this as an 792 error condition with the error 'sampleOverrun'. 794 A frequency of 0 indicates instantaneous recognition of the 795 condition. This is not possible in many cases, but may 796 be supported in cases where it makes sense and the system is 797 able to do so. This feature allows the MIB to be used in 798 implementations where such interrupt-driven behavior is 799 possible and is not likely to be supported for all MIB objects 800 even then since such sampling generally has to be tightly 801 integrated into low-level code. 803 Systems that can support this SHOULD document those cases 804 where it can be used. In cases where it can not, setting this 805 object to 0 should be disallowed." 806 DEFVAL { 600 } 807 ::= { mteTriggerEntry 11 } 809 mteTriggerObjectsOwner OBJECT-TYPE 810 SYNTAX SnmpAdminString (SIZE (0..32)) 811 MAX-ACCESS read-create 812 STATUS current 813 DESCRIPTION 814 "To go with mteTriggerObjects, the mteOwner of a group of 815 objects from mteObjectsTable." 816 DEFVAL { ''H } 817 ::= { mteTriggerEntry 12 } 819 mteTriggerObjects OBJECT-TYPE 820 SYNTAX SnmpAdminString (SIZE (0..32)) 821 MAX-ACCESS read-create 822 STATUS current 823 DESCRIPTION 824 "The mteObjectsName of a group of objects from 825 mteObjectsTable. These objects are to be added to any 826 Notification resulting from the firing of this trigger. 828 A list of objects may also be added based on the event or on 829 the value of mteTriggerTest. 831 A length of 0 indicates no additional objects." 832 DEFVAL { ''H } 833 ::= { mteTriggerEntry 13 } 835 mteTriggerEnabled OBJECT-TYPE 837 Kavasseri and Claise Standard Track 18 838 SYNTAX TruthValue 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "A control to allow a trigger to be configured but not used. 843 When the value is 'false' the trigger is not sampled. 845 Whenever the value goes from 'false' to 'true', the trigger 846 is treated as being initialized. That is, no history is kept 847 of any trigger sample values from previous times when this 848 control may have been enabled. 850 If this object is set to 'true' when its value 851 is already 'true', the operation has no effect; 852 that is, the trigger is not re-initialized, and 853 there is no error." 854 DEFVAL { false } 855 ::= { mteTriggerEntry 14 } 857 mteTriggerEntryStatus OBJECT-TYPE 858 SYNTAX RowStatus 859 MAX-ACCESS read-create 860 STATUS current 861 DESCRIPTION 862 "The control that allows creation and deletion of entries. 863 Once made active an entry may not be modified except to 864 modify the value of mteTriggerEnabled or to delete the 865 entry." 866 ::= { mteTriggerEntry 15 } 868 mteTriggerEntryStorageType OBJECT-TYPE 869 SYNTAX StorageType 870 MAX-ACCESS read-create 871 STATUS current 872 DESCRIPTION "The storage type for this conceptual row. 873 Conceptual rows having the value 'permanent' need not 874 allow write-access to any columnar objects in the row, 875 except for mteTriggerEnabled. 876 " 877 DEFVAL { nonVolatile } 878 ::= { mteTriggerEntry 16 } 880 -- 881 -- Trigger Delta Table 882 -- 884 Kavasseri and Claise Standard Track 19 885 mteTriggerDeltaTable OBJECT-TYPE 886 SYNTAX SEQUENCE OF MteTriggerDeltaEntry 887 MAX-ACCESS not-accessible 888 STATUS current 889 DESCRIPTION 890 "A table of management event trigger information for delta 891 sampling." 892 ::= { mteTrigger 3 } 894 mteTriggerDeltaEntry OBJECT-TYPE 895 SYNTAX MteTriggerDeltaEntry 896 MAX-ACCESS not-accessible 897 STATUS current 898 DESCRIPTION 899 "Information about a single trigger's delta sampling. Entries 900 automatically exist in this this table for each mteTriggerEntry 901 that has mteTriggerSampleType set to 'deltaValue'." 902 INDEX { mteOwner, IMPLIED mteTriggerName } 903 ::= { mteTriggerDeltaTable 1 } 905 MteTriggerDeltaEntry ::= SEQUENCE { 906 mteTriggerDeltaDiscontinuityID OBJECT IDENTIFIER, 907 mteTriggerDeltaDiscontinuityIDWildcard TruthValue, 908 mteTriggerDeltaDiscontinuityIDType INTEGER 909 } 911 sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 } 913 mteTriggerDeltaDiscontinuityID OBJECT-TYPE 914 SYNTAX OBJECT IDENTIFIER 915 MAX-ACCESS read-write 916 STATUS current 917 DESCRIPTION 918 "The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or 919 DateAndTime object that indicates a discontinuity in the value 920 at mteTriggerValueID. 922 The OID may be for a leaf object (e.g. sysUpTime.0) or may 923 be wildcarded to match mteTriggerValueID. 925 This object supports normal checking for a discontinuity in a 926 counter. Note that if this object does not point to sysUpTime 927 discontinuity checking MUST still check sysUpTime for an 928 overall discontinuity. 930 Kavasseri and Claise Standard Track 20 931 If the object identified is not accessible the sample attempt 932 is in error, with the error code as from an SNMP request. 934 Bad object identifiers or a mismatch between truncating the 935 identifier and the value of mteDeltaDiscontinuityIDWildcard 936 result in operation as one would expect when providing the 937 wrong identifier to a Get operation. The Get will fail or get 938 the wrong object. If the value syntax of those objects is not 939 usable, that results in an error that terminates the sample 940 with a 'badType' error code." 941 DEFVAL { sysUpTimeInstance } 942 ::= { mteTriggerDeltaEntry 1 } 944 mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE 945 SYNTAX TruthValue 946 MAX-ACCESS read-write 947 STATUS current 948 DESCRIPTION 949 "Control for whether mteTriggerDeltaDiscontinuityID is to be 950 treated as fully-specified or wildcarded, with 'true' 951 indicating wildcard. Note that the value of this object will 952 be the same as that of the corresponding instance of 953 mteTriggerValueIDWildcard when the corresponding 954 mteTriggerSampleType is 'deltaValue'." 955 DEFVAL { false } 956 ::= { mteTriggerDeltaEntry 2 } 958 mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE 959 SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) } 960 MAX-ACCESS read-write 961 STATUS current 962 DESCRIPTION 963 "The value 'timeTicks' indicates the 964 mteTriggerDeltaDiscontinuityID of this row is of syntax 965 TimeTicks. The value 'timeStamp' indicates syntax TimeStamp. 966 The value 'dateAndTime' indicates syntax DateAndTime." 967 DEFVAL { timeTicks } 968 ::= { mteTriggerDeltaEntry 3 } 970 -- 971 -- Trigger Existence Table 972 -- 974 mteTriggerExistenceTable OBJECT-TYPE 976 Kavasseri and Claise Standard Track 21 977 SYNTAX SEQUENCE OF MteTriggerExistenceEntry 978 MAX-ACCESS not-accessible 979 STATUS current 980 DESCRIPTION 981 "A table of management event trigger information for existence 982 triggers." 983 ::= { mteTrigger 4 } 985 mteTriggerExistenceEntry OBJECT-TYPE 986 SYNTAX MteTriggerExistenceEntry 987 MAX-ACCESS not-accessible 988 STATUS current 989 DESCRIPTION 990 "Information about a single existence trigger. Entries 991 automatically exist in this this table for each mteTriggerEntry 992 that has 'existence' set in mteTriggerTest." 993 INDEX { mteOwner, IMPLIED mteTriggerName } 994 ::= { mteTriggerExistenceTable 1 } 996 MteTriggerExistenceEntry ::= SEQUENCE { 997 mteTriggerExistenceTest BITS, 998 mteTriggerExistenceStartup BITS, 999 mteTriggerExistenceObjectsOwner SnmpAdminString, 1000 mteTriggerExistenceObjects SnmpAdminString, 1001 mteTriggerExistenceEventOwner SnmpAdminString, 1002 mteTriggerExistenceEvent SnmpAdminString 1003 } 1005 mteTriggerExistenceTest OBJECT-TYPE 1006 SYNTAX BITS { present(0), absent(1), changed(2) } 1007 MAX-ACCESS read-write 1008 STATUS current 1009 DESCRIPTION 1010 "The type of existence test to perform. The trigger fires 1011 when the object at mteTriggerValueID is seen to go from 1012 present to absent, from absent to present, or to have it's 1013 value changed, depending on which tests are selected: 1015 present(0) - when this test is selected, the trigger fires 1016 when the mteTriggerValueID object goes from absent to present. 1018 absent(1) - when this test is selected, the trigger fires 1019 when the mteTriggerValueID object goes from present to absent. 1020 changed(2) - when this test is selected, the trigger fires 1021 the mteTriggerValueID object value changes. 1023 Kavasseri and Claise Standard Track 22 1024 Once the trigger has fired for either presence or absence it 1025 will not fire again for that state until the object has been 1026 to the other state. " 1027 DEFVAL { { present, absent } } 1028 ::= { mteTriggerExistenceEntry 1 } 1030 mteTriggerExistenceStartup OBJECT-TYPE 1031 SYNTAX BITS { present(0), absent(1) } 1032 MAX-ACCESS read-write 1033 STATUS current 1034 DESCRIPTION 1035 "Control for whether an event may be triggered when this entry 1036 is first set to 'active' and the test specified by 1037 mteTriggerExistenceTest is true. Setting an option causes 1038 that trigger to fire when its test is true." 1039 DEFVAL { { present, absent } } 1040 ::= { mteTriggerExistenceEntry 2 } 1042 mteTriggerExistenceObjectsOwner OBJECT-TYPE 1043 SYNTAX SnmpAdminString (SIZE (0..32)) 1044 MAX-ACCESS read-write 1045 STATUS current 1046 DESCRIPTION 1047 "To go with mteTriggerExistenceObjects, the mteOwner of a 1048 group of objects from mteObjectsTable." 1049 DEFVAL { ''H } 1050 ::= { mteTriggerExistenceEntry 3 } 1052 mteTriggerExistenceObjects OBJECT-TYPE 1053 SYNTAX SnmpAdminString (SIZE (0..32)) 1054 MAX-ACCESS read-write 1055 STATUS current 1056 DESCRIPTION 1057 "The mteObjectsName of a group of objects from 1058 mteObjectsTable. These objects are to be added to any 1059 Notification resulting from the firing of this trigger for 1060 this test. 1062 A list of objects may also be added based on the overall 1063 trigger, the event or other settings in mteTriggerTest. 1065 A length of 0 indicates no additional objects." 1066 DEFVAL { ''H } 1067 ::= { mteTriggerExistenceEntry 4 } 1069 Kavasseri and Claise Standard Track 23 1070 mteTriggerExistenceEventOwner OBJECT-TYPE 1071 SYNTAX SnmpAdminString (SIZE (0..32)) 1072 MAX-ACCESS read-write 1073 STATUS current 1074 DESCRIPTION 1075 "To go with mteTriggerExistenceEvent, the mteOwner of an event 1076 entry from the mteEventTable." 1077 DEFVAL { ''H } 1078 ::= { mteTriggerExistenceEntry 5 } 1080 mteTriggerExistenceEvent OBJECT-TYPE 1081 SYNTAX SnmpAdminString (SIZE (0..32)) 1082 MAX-ACCESS read-write 1083 STATUS current 1084 DESCRIPTION 1085 "The mteEventName of the event to invoke when mteTriggerType is 1086 'existence' and this trigger fires. A length of 0 indicates no 1087 event." 1088 DEFVAL { ''H } 1089 ::= { mteTriggerExistenceEntry 6 } 1091 -- 1092 -- Trigger Boolean Table 1093 -- 1095 mteTriggerBooleanTable OBJECT-TYPE 1096 SYNTAX SEQUENCE OF MteTriggerBooleanEntry 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "A table of management event trigger information for boolean 1101 triggers." 1102 ::= { mteTrigger 5 } 1104 mteTriggerBooleanEntry OBJECT-TYPE 1105 SYNTAX MteTriggerBooleanEntry 1106 MAX-ACCESS not-accessible 1107 STATUS current 1108 DESCRIPTION 1109 "Information about a single boolean trigger. Entries 1110 automatically exist in this this table for each mteTriggerEntry 1111 that has 'boolean' set in mteTriggerTest." 1112 INDEX { mteOwner, IMPLIED mteTriggerName } 1113 ::= { mteTriggerBooleanTable 1 } 1115 Kavasseri and Claise Standard Track 24 1116 MteTriggerBooleanEntry ::= SEQUENCE { 1117 mteTriggerBooleanComparison INTEGER, 1118 mteTriggerBooleanValue Integer32, 1119 mteTriggerBooleanStartup TruthValue, 1120 mteTriggerBooleanObjectsOwner SnmpAdminString, 1121 mteTriggerBooleanObjects SnmpAdminString, 1122 mteTriggerBooleanEventOwner SnmpAdminString, 1123 mteTriggerBooleanEvent SnmpAdminString 1124 } 1126 mteTriggerBooleanComparison OBJECT-TYPE 1127 SYNTAX INTEGER { unequal(1), equal(2), 1128 less(3), lessOrEqual(4), 1129 greater(5), greaterOrEqual(6) } 1130 MAX-ACCESS read-write 1131 STATUS current 1132 DESCRIPTION 1133 "The type of boolean comparison to perform. 1135 The value at mteTriggerValueID is compared to 1136 mteTriggerBooleanValue, so for example if 1137 mteTriggerBooleanComparison is 'less' the result would be true 1138 if the value at mteTriggerValueID is less than the value of 1139 mteTriggerBooleanValue." 1140 DEFVAL { unequal } 1141 ::= { mteTriggerBooleanEntry 1 } 1143 mteTriggerBooleanValue OBJECT-TYPE 1144 SYNTAX Integer32 1145 MAX-ACCESS read-write 1146 STATUS current 1147 DESCRIPTION 1148 "The value to use for the test specified by 1149 mteTriggerBooleanTest." 1150 DEFVAL { 0 } 1151 ::= { mteTriggerBooleanEntry 2 } 1153 mteTriggerBooleanStartup OBJECT-TYPE 1154 SYNTAX TruthValue 1155 MAX-ACCESS read-write 1156 STATUS current 1157 DESCRIPTION 1158 "Control for whether an event may be triggered when this entry 1159 is first set to 'active' or a new instance of the object at 1161 Kavasseri and Claise Standard Track 25 1162 mteTriggerValueID is found and the test specified by 1163 mteTriggerBooleanComparison is true. In that case an event is 1164 triggered if mteTriggerBooleanStartup is 'true'." 1165 DEFVAL { true } 1166 ::= { mteTriggerBooleanEntry 3 } 1168 mteTriggerBooleanObjectsOwner OBJECT-TYPE 1169 SYNTAX SnmpAdminString (SIZE (0..32)) 1170 MAX-ACCESS read-write 1171 STATUS current 1172 DESCRIPTION 1173 "To go with mteTriggerBooleanObjects, the mteOwner of a group 1174 of objects from mteObjectsTable." 1175 DEFVAL { ''H } 1176 ::= { mteTriggerBooleanEntry 4 } 1178 mteTriggerBooleanObjects OBJECT-TYPE 1179 SYNTAX SnmpAdminString (SIZE (0..32)) 1180 MAX-ACCESS read-write 1181 STATUS current 1182 DESCRIPTION 1183 "The mteObjectsName of a group of objects from 1184 mteObjectsTable. These objects are to be added to any 1185 Notification resulting from the firing of this trigger for 1186 this test. 1188 A list of objects may also be added based on the overall 1189 trigger, the event or other settings in mteTriggerTest. 1191 A length of 0 indicates no additional objects." 1192 DEFVAL { ''H } 1193 ::= { mteTriggerBooleanEntry 5 } 1195 mteTriggerBooleanEventOwner OBJECT-TYPE 1196 SYNTAX SnmpAdminString (SIZE (0..32)) 1197 MAX-ACCESS read-write 1198 STATUS current 1199 DESCRIPTION 1200 "To go with mteTriggerBooleanEvent, the mteOwner of an event 1201 entry from mteEventTable." 1202 DEFVAL { ''H } 1203 ::= { mteTriggerBooleanEntry 6 } 1205 mteTriggerBooleanEvent OBJECT-TYPE 1206 SYNTAX SnmpAdminString (SIZE (0..32)) 1208 Kavasseri and Claise Standard Track 26 1209 MAX-ACCESS read-write 1210 STATUS current 1211 DESCRIPTION 1212 "The mteEventName of the event to invoke when mteTriggerType is 1213 'boolean' and this trigger fires. A length of 0 indicates no 1214 event." 1215 DEFVAL { ''H } 1216 ::= { mteTriggerBooleanEntry 7 } 1218 -- 1219 -- Trigger Threshold Table 1220 -- 1222 mteTriggerThresholdTable OBJECT-TYPE 1223 SYNTAX SEQUENCE OF MteTriggerThresholdEntry 1224 MAX-ACCESS not-accessible 1225 STATUS current 1226 DESCRIPTION 1227 "A table of management event trigger information for threshold 1228 triggers." 1229 ::= { mteTrigger 6 } 1231 mteTriggerThresholdEntry OBJECT-TYPE 1232 SYNTAX MteTriggerThresholdEntry 1233 MAX-ACCESS not-accessible 1234 STATUS current 1235 DESCRIPTION 1236 "Information about a single threshold trigger. Entries 1237 automatically exist in this table for each mteTriggerEntry 1238 that has 'threshold' set in mteTriggerTest." 1239 INDEX { mteOwner, IMPLIED mteTriggerName } 1240 ::= { mteTriggerThresholdTable 1 } 1242 MteTriggerThresholdEntry ::= SEQUENCE { 1243 mteTriggerThresholdStartup INTEGER, 1244 mteTriggerThresholdRising Integer32, 1245 mteTriggerThresholdFalling Integer32, 1246 mteTriggerThresholdDeltaRising Integer32, 1247 mteTriggerThresholdDeltaFalling Integer32, 1248 mteTriggerThresholdObjectsOwner SnmpAdminString, 1249 mteTriggerThresholdObjects SnmpAdminString, 1250 mteTriggerThresholdRisingEventOwner SnmpAdminString, 1251 mteTriggerThresholdRisingEvent SnmpAdminString, 1252 mteTriggerThresholdFallingEventOwner SnmpAdminString, 1253 mteTriggerThresholdFallingEvent SnmpAdminString, 1255 Kavasseri and Claise Standard Track 27 1256 mteTriggerThresholdDeltaRisingEventOwner SnmpAdminString, 1257 mteTriggerThresholdDeltaRisingEvent SnmpAdminString, 1258 mteTriggerThresholdDeltaFallingEventOwner SnmpAdminString, 1259 mteTriggerThresholdDeltaFallingEvent SnmpAdminString 1260 } 1262 mteTriggerThresholdStartup OBJECT-TYPE 1263 SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } 1264 MAX-ACCESS read-write 1265 STATUS current 1266 DESCRIPTION 1267 "The event that may be triggered when this entry is first 1268 set to 'active' and a new instance of the object at 1269 mteTriggerValueID is found. If the first sample after this 1270 instance becomes active is greater than or equal to 1271 mteTriggerThresholdRising and mteTriggerThresholdStartup is 1272 equal to 'rising' or 'risingOrFalling', then one 1273 mteTriggerThresholdRisingEvent is triggered for that instance. 1274 If the first sample after this entry becomes active is less 1275 than or equal to mteTriggerThresholdFalling and 1276 mteTriggerThresholdStartup is equal to 'falling' or 1277 'risingOrFalling', then one mteTriggerThresholdRisingEvent is 1278 triggered for that instance." 1279 DEFVAL { risingOrFalling } 1280 ::= { mteTriggerThresholdEntry 1 } 1282 mteTriggerThresholdRising OBJECT-TYPE 1283 SYNTAX Integer32 1284 MAX-ACCESS read-write 1285 STATUS current 1286 DESCRIPTION 1287 "A threshold value to check against if mteTriggerType is 1288 'threshold'. 1290 When the current sampled value is greater than or equal to 1291 this threshold, and the value at the last sampling interval 1292 was less than this threshold, one 1293 mteTriggerThresholdRisingEvent is triggered. That event is 1294 also triggered if the first sample after this entry becomes 1295 active is greater than or equal to this threshold and 1296 mteTriggerThresholdStartup is equal to 'rising' or 1297 'risingOrFalling'. 1299 After a rising event is generated, another such event is not 1300 triggered until the sampled value falls below this threshold 1302 Kavasseri and Claise Standard Track 28 1303 and reaches mteTriggerThresholdFalling." 1304 DEFVAL { 0 } 1305 ::= { mteTriggerThresholdEntry 2 } 1307 mteTriggerThresholdFalling OBJECT-TYPE 1308 SYNTAX Integer32 1309 MAX-ACCESS read-write 1310 STATUS current 1311 DESCRIPTION 1312 "A threshold value to check against if mteTriggerType is 1313 'threshold'. 1315 When the current sampled value is less than or equal to this 1316 threshold, and the value at the last sampling interval was 1317 greater than this threshold, one 1318 mteTriggerThresholdFallingEvent is triggered. That event is 1319 also triggered if the first sample after this entry becomes 1320 active is less than or equal to this threshold and 1321 mteTriggerThresholdStartup is equal to 'falling' or 1322 'risingOrFalling'. 1324 After a falling event is generated, another such event is not 1325 triggered until the sampled value rises above this threshold 1326 and reaches mteTriggerThresholdRising." 1327 DEFVAL { 0 } 1328 ::= { mteTriggerThresholdEntry 3 } 1330 mteTriggerThresholdDeltaRising OBJECT-TYPE 1331 SYNTAX Integer32 1332 MAX-ACCESS read-write 1333 STATUS current 1334 DESCRIPTION 1335 "A threshold value to check against if mteTriggerType is 1336 'threshold'. 1338 When the delta value (difference) between the current sampled 1339 value (value(n)) and the previous sampled value (value(n-1)) 1340 is greater than or equal to this threshold, 1341 and the delta value calculated at the last sampling interval 1342 (i.e. value(n-1) - value(n-2)) was less than this threshold, 1343 one mteTriggerThresholdDeltaRisingEvent is triggered. That 1344 event is also triggered if the first delta value calculated 1345 after this entry becomes active, i.e. value(2) - value(1), 1346 where value(1) is the first sample taken of that instance, is 1347 greater than or equal to this threshold. 1349 Kavasseri and Claise Standard Track 29 1350 After a rising event is generated, another such event is not 1351 triggered until the delta value falls below this threshold and 1352 reaches mteTriggerThresholdDeltaFalling." 1353 DEFVAL { 0 } 1354 ::= { mteTriggerThresholdEntry 4 } 1356 mteTriggerThresholdDeltaFalling OBJECT-TYPE 1357 SYNTAX Integer32 1358 MAX-ACCESS read-write 1359 STATUS current 1360 DESCRIPTION 1361 "A threshold value to check against if mteTriggerType is 1362 'threshold'. 1364 When the delta value (difference) between the current sampled 1365 value (value(n)) and the previous sampled value (value(n-1)) 1366 is less than or equal to this threshold, 1367 and the delta value calculated at the last sampling interval 1368 (i.e. value(n-1) - value(n-2)) was greater than this threshold, 1369 one mteTriggerThresholdDeltaFallingEvent is triggered. That 1370 event is also triggered if the first delta value calculated 1371 after this entry becomes active, i.e. value(2) - value(1), 1372 where value(1) is the first sample taken of that instance, is 1373 less than or equal to this threshold. 1375 After a falling event is generated, another such event is not 1376 triggered until the delta value falls below this threshold and 1377 reaches mteTriggerThresholdDeltaRising." 1378 DEFVAL { 0 } 1379 ::= { mteTriggerThresholdEntry 5 } 1381 mteTriggerThresholdObjectsOwner OBJECT-TYPE 1382 SYNTAX SnmpAdminString (SIZE (0..32)) 1383 MAX-ACCESS read-write 1384 STATUS current 1385 DESCRIPTION 1386 "To go with mteTriggerThresholdObjects, the mteOwner of a group 1387 of objects from mteObjectsTable." 1388 DEFVAL { ''H } 1389 ::= { mteTriggerThresholdEntry 6 } 1391 mteTriggerThresholdObjects OBJECT-TYPE 1392 SYNTAX SnmpAdminString (SIZE (0..32)) 1393 MAX-ACCESS read-write 1395 Kavasseri and Claise Standard Track 30 1396 STATUS current 1397 DESCRIPTION 1398 "The mteObjectsName of a group of objects from 1399 mteObjectsTable. These objects are to be added to any 1400 Notification resulting from the firing of this trigger for 1401 this test. 1403 A list of objects may also be added based on the overall 1404 trigger, the event or other settings in mteTriggerTest. 1406 A length of 0 indicates no additional objects." 1407 DEFVAL { ''H } 1408 ::= { mteTriggerThresholdEntry 7 } 1410 mteTriggerThresholdRisingEventOwner OBJECT-TYPE 1411 SYNTAX SnmpAdminString (SIZE (0..32)) 1412 MAX-ACCESS read-write 1413 STATUS current 1414 DESCRIPTION 1415 "To go with mteTriggerThresholdRisingEvent, the mteOwner of an 1416 event entry from mteEventTable." 1417 DEFVAL { ''H } 1418 ::= { mteTriggerThresholdEntry 8 } 1420 mteTriggerThresholdRisingEvent OBJECT-TYPE 1421 SYNTAX SnmpAdminString (SIZE (0..32)) 1422 MAX-ACCESS read-write 1423 STATUS current 1424 DESCRIPTION 1425 "The mteEventName of the event to invoke when mteTriggerType is 1426 'threshold' and this trigger fires based on 1427 mteTriggerThresholdRising. A length of 0 indicates no event." 1428 DEFVAL { ''H } 1429 ::= { mteTriggerThresholdEntry 9 } 1431 mteTriggerThresholdFallingEventOwner OBJECT-TYPE 1432 SYNTAX SnmpAdminString (SIZE (0..32)) 1433 MAX-ACCESS read-write 1434 STATUS current 1435 DESCRIPTION 1436 "To go with mteTriggerThresholdFallingEvent, the mteOwner of an 1437 event entry from mteEventTable." 1438 DEFVAL { ''H } 1439 ::= { mteTriggerThresholdEntry 10 } 1441 Kavasseri and Claise Standard Track 31 1442 mteTriggerThresholdFallingEvent OBJECT-TYPE 1443 SYNTAX SnmpAdminString (SIZE (0..32)) 1444 MAX-ACCESS read-write 1445 STATUS current 1446 DESCRIPTION 1447 "The mteEventName of the event to invoke when mteTriggerType is 1448 'threshold' and this trigger fires based on 1449 mteTriggerThresholdFalling. A length of 0 indicates no event." 1450 DEFVAL { ''H } 1451 ::= { mteTriggerThresholdEntry 11 } 1453 mteTriggerThresholdDeltaRisingEventOwner OBJECT-TYPE 1454 SYNTAX SnmpAdminString (SIZE (0..32)) 1455 MAX-ACCESS read-write 1456 STATUS current 1457 DESCRIPTION 1458 "To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner 1459 of an event entry from mteEventTable." 1460 DEFVAL { ''H } 1461 ::= { mteTriggerThresholdEntry 12 } 1463 mteTriggerThresholdDeltaRisingEvent OBJECT-TYPE 1464 SYNTAX SnmpAdminString (SIZE (0..32)) 1465 MAX-ACCESS read-write 1466 STATUS current 1467 DESCRIPTION 1468 "The mteEventName of the event to invoke when mteTriggerType is 1469 'threshold' and this trigger fires based on 1470 mteTriggerThresholdDeltaRising. A length of 0 indicates 1471 no event." 1472 DEFVAL { ''H } 1473 ::= { mteTriggerThresholdEntry 13 } 1475 mteTriggerThresholdDeltaFallingEventOwner OBJECT-TYPE 1476 SYNTAX SnmpAdminString (SIZE (0..32)) 1477 MAX-ACCESS read-write 1478 STATUS current 1479 DESCRIPTION 1480 "To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner 1481 of an event entry from mteEventTable." 1482 DEFVAL { ''H } 1483 ::= { mteTriggerThresholdEntry 14 } 1485 mteTriggerThresholdDeltaFallingEvent OBJECT-TYPE 1486 SYNTAX SnmpAdminString (SIZE (0..32)) 1488 Kavasseri and Claise Standard Track 32 1489 MAX-ACCESS read-write 1490 STATUS current 1491 DESCRIPTION 1492 "The mteEventName of the event to invoke when mteTriggerType is 1493 'threshold' and this trigger fires based on 1494 mteTriggerThresholdDeltaFalling. A length of 0 indicates 1495 no event." 1496 DEFVAL { ''H } 1497 ::= { mteTriggerThresholdEntry 15 } 1499 -- 1500 -- Objects Table 1501 -- 1503 mteObjectsTable OBJECT-TYPE 1504 SYNTAX SEQUENCE OF MteObjectsEntry 1505 MAX-ACCESS not-accessible 1506 STATUS current 1507 DESCRIPTION 1508 "A table of objects that can be added to notifications based 1509 on the trigger, trigger test, or event, as pointed to by 1510 entries in those tables." 1511 ::= { mteObjects 1 } 1513 mteObjectsEntry OBJECT-TYPE 1514 SYNTAX MteObjectsEntry 1515 MAX-ACCESS not-accessible 1516 STATUS current 1517 DESCRIPTION 1518 "A group of objects. Applications create and delete entries 1519 using mteObjectsEntryStatus. 1521 When adding objects to a notification they are added in the 1522 lexical order of their index in this table. Those associated 1523 with a trigger come first, then trigger test, then event." 1524 INDEX { mteOwner, mteObjectsName, mteObjectsIndex } 1525 ::= { mteObjectsTable 1 } 1527 MteObjectsEntry ::= SEQUENCE { 1528 mteObjectsName SnmpAdminString, 1529 mteObjectsIndex Unsigned32, 1530 mteObjectsID OBJECT IDENTIFIER, 1531 mteObjectsIDWildcard TruthValue, 1532 mteObjectsEntryStatus RowStatus, 1533 mteObjectsEntryStorageType StorageType 1535 Kavasseri and Claise Standard Track 33 1536 } 1538 mteObjectsName OBJECT-TYPE 1539 SYNTAX SnmpAdminString (SIZE (1..32)) 1540 MAX-ACCESS not-accessible 1541 STATUS current 1542 DESCRIPTION 1543 "A locally-unique, administratively assigned name for a group 1544 of objects." 1545 ::= { mteObjectsEntry 1 } 1547 mteObjectsIndex OBJECT-TYPE 1548 SYNTAX Unsigned32 (1..4294967295) 1549 MAX-ACCESS not-accessible 1550 STATUS current 1551 DESCRIPTION 1552 "An arbitrary integer for the purpose of identifying 1553 individual objects within a mteObjectsName group. 1555 Objects within a group are placed in the notification in the 1556 numerical order of this index. 1558 Groups are placed in the notification in the order of the 1559 selections for overall trigger, trigger test, and event. 1560 Within trigger test they are in the same order as the 1561 numerical values of the bits defined for mteTriggerTest. 1563 Bad object identifiers or a mismatch between truncating the 1564 identifier and the value of mteDeltaDiscontinuityIDWildcard 1565 result in operation as one would expect when providing the 1566 wrong identifier to a Get operation. The Get will fail or get 1567 the wrong object. If the object is not available it is omitted 1568 from the notification." 1569 ::= { mteObjectsEntry 2 } 1571 mteObjectsID OBJECT-TYPE 1572 SYNTAX OBJECT IDENTIFIER 1573 MAX-ACCESS read-create 1574 STATUS current 1575 DESCRIPTION 1576 "The object identifier of a MIB object to add to a 1577 Notification that results from the firing of a trigger. 1579 This may be wildcarded by truncating all or part of the 1580 instance portion, in which case the instance portion of the 1582 Kavasseri and Claise Standard Track 34 1583 OID for obtaining this object will be the same as that used 1584 in obtaining the mteTriggerValueID that fired. If such 1585 wildcarding is applied, mteObjectsIDWildcard must be 1586 'true' and if not it must be 'false'. 1588 Each instance that fills the wildcard is independent of any 1589 additional instances, that is, wildcarded objects operate 1590 as if there were a separate table entry for each instance 1591 that fills the wildcard without having to actually predict 1592 all possible instances ahead of time." 1593 DEFVAL { zeroDotZero } 1594 ::= { mteObjectsEntry 3 } 1596 mteObjectsIDWildcard OBJECT-TYPE 1597 SYNTAX TruthValue 1598 MAX-ACCESS read-create 1599 STATUS current 1600 DESCRIPTION 1601 "Control for whether mteObjectsID is to be treated as 1602 fully-specified or wildcarded, with 'true' indicating 1603 wildcard." 1604 DEFVAL { false } 1605 ::= { mteObjectsEntry 4 } 1607 mteObjectsEntryStatus OBJECT-TYPE 1608 SYNTAX RowStatus 1609 MAX-ACCESS read-create 1610 STATUS current 1611 DESCRIPTION 1612 "The control that allows creation and deletion of entries. 1613 Once made active an entry MAY not be modified except to 1614 delete it." 1615 ::= { mteObjectsEntry 5 } 1617 mteObjectsEntryStorageType OBJECT-TYPE 1618 SYNTAX StorageType 1619 MAX-ACCESS read-create 1620 STATUS current 1621 DESCRIPTION "The storage type for this conceptual row. 1622 Conceptual rows having the value 'permanent' need not 1623 allow write-access to any columnar objects in the row. 1624 " 1625 DEFVAL { nonVolatile } 1626 ::= { mteObjectsEntry 6 } 1628 Kavasseri and Claise Standard Track 35 1629 -- 1630 -- Event Section 1631 -- 1633 -- Counters 1635 mteEventFailures OBJECT-TYPE 1636 SYNTAX Counter32 1637 MAX-ACCESS read-only 1638 STATUS current 1639 DESCRIPTION 1640 "The number of times an attempt to invoke an event 1641 has failed. This counts individually for each 1642 attempt in a group of targets or each attempt for a 1643 wildcarded trigger object." 1644 ::= { mteEvent 1 } 1646 -- 1647 -- Event Table 1648 -- 1650 mteEventTable OBJECT-TYPE 1651 SYNTAX SEQUENCE OF MteEventEntry 1652 MAX-ACCESS not-accessible 1653 STATUS current 1654 DESCRIPTION 1655 "A table of management event action information." 1656 ::= { mteEvent 2 } 1658 mteEventEntry OBJECT-TYPE 1659 SYNTAX MteEventEntry 1660 MAX-ACCESS not-accessible 1661 STATUS current 1662 DESCRIPTION 1663 "Information about a single event. Applications create and 1664 delete entries using mteEventEntryStatus." 1665 INDEX { mteOwner, IMPLIED mteEventName } 1666 ::= { mteEventTable 1 } 1668 MteEventEntry ::= SEQUENCE { 1669 mteEventName SnmpAdminString, 1670 mteEventComment SnmpAdminString, 1671 mteEventActions BITS, 1672 mteEventEnabled TruthValue, 1673 mteEventEntryStatus RowStatus, 1675 Kavasseri and Claise Standard Track 36 1676 mteEventEntryStorageType StorageType 1677 } 1679 mteEventName OBJECT-TYPE 1680 SYNTAX SnmpAdminString (SIZE (1..32)) 1681 MAX-ACCESS not-accessible 1682 STATUS current 1683 DESCRIPTION 1684 "A locally-unique, administratively assigned name for the 1685 event." 1686 ::= { mteEventEntry 1 } 1688 mteEventComment OBJECT-TYPE 1689 SYNTAX SnmpAdminString 1690 MAX-ACCESS read-create 1691 STATUS current 1692 DESCRIPTION 1693 "A description of the event's function and use." 1694 DEFVAL { ''H } 1695 ::= { mteEventEntry 2 } 1697 mteEventActions OBJECT-TYPE 1698 SYNTAX BITS { notification(0), set(1) } 1699 MAX-ACCESS read-create 1700 STATUS current 1701 DESCRIPTION 1702 "The actions to perform when this event occurs. 1704 For 'notification', Traps and/or Informs are sent according 1705 to the configuration in the SNMP Notification MIB. 1707 For 'set', an SNMP Set operation is performed according to 1708 control values in this entry." 1709 DEFVAL { {} } -- No bits set. 1710 ::= { mteEventEntry 3 } 1712 mteEventEnabled OBJECT-TYPE 1713 SYNTAX TruthValue 1714 MAX-ACCESS read-create 1715 STATUS current 1716 DESCRIPTION 1717 "A control to allow an event to be configured but not used. 1718 When the value is 'false' the event does not execute even if 1719 triggered." 1720 DEFVAL { false } 1722 Kavasseri and Claise Standard Track 37 1723 ::= { mteEventEntry 4 } 1725 mteEventEntryStatus OBJECT-TYPE 1726 SYNTAX RowStatus 1727 MAX-ACCESS read-create 1728 STATUS current 1729 DESCRIPTION 1730 "The control that allows creation and deletion of entries. 1731 Once made active an entry MAY not be modified except to 1732 modify the value of mteEventEnabled or to delete the entry." 1733 ::= { mteEventEntry 5 } 1735 mteEventEntryStorageType OBJECT-TYPE 1736 SYNTAX StorageType 1737 MAX-ACCESS read-create 1738 STATUS current 1739 DESCRIPTION "The storage type for this conceptual row. 1740 Conceptual rows having the value 'permanent' need not 1741 allow write-access to any columnar objects in the row. 1742 " 1743 DEFVAL { nonVolatile } 1744 ::= { mteEventEntry 6 } 1746 -- 1747 -- Event Notification Table 1748 -- 1750 mteEventNotificationTable OBJECT-TYPE 1751 SYNTAX SEQUENCE OF MteEventNotificationEntry 1752 MAX-ACCESS not-accessible 1753 STATUS current 1754 DESCRIPTION 1755 "A table of information about notifications to be sent as a 1756 consequence of management events." 1757 ::= { mteEvent 3 } 1759 mteEventNotificationEntry OBJECT-TYPE 1760 SYNTAX MteEventNotificationEntry 1761 MAX-ACCESS not-accessible 1762 STATUS current 1763 DESCRIPTION 1764 "Information about a single event's notification. Entries 1765 automatically exist in this this table for each mteEventEntry 1766 that has 'notification' set in mteEventActions." 1768 Kavasseri and Claise Standard Track 38 1769 INDEX { mteOwner, IMPLIED mteEventName } 1770 ::= { mteEventNotificationTable 1 } 1772 MteEventNotificationEntry ::= SEQUENCE { 1773 mteEventNotification OBJECT IDENTIFIER, 1774 mteEventNotificationObjectsOwner SnmpAdminString, 1775 mteEventNotificationObjects SnmpAdminString 1776 } 1778 mteEventNotification OBJECT-TYPE 1779 SYNTAX OBJECT IDENTIFIER 1780 MAX-ACCESS read-write 1781 STATUS current 1782 DESCRIPTION 1783 "The object identifier from the NOTIFICATION-TYPE for the 1784 notification to use if mteEventActions has 'notification' set." 1785 DEFVAL { zeroDotZero } 1786 ::= { mteEventNotificationEntry 1 } 1788 mteEventNotificationObjectsOwner OBJECT-TYPE 1789 SYNTAX SnmpAdminString (SIZE (0..32)) 1790 MAX-ACCESS read-write 1791 STATUS current 1792 DESCRIPTION 1793 "To go with mteEventNotificationObjects, the mteOwner of a 1794 group of objects from mteObjectsTable." 1795 DEFVAL { ''H } 1796 ::= { mteEventNotificationEntry 2 } 1798 mteEventNotificationObjects OBJECT-TYPE 1799 SYNTAX SnmpAdminString (SIZE (0..32)) 1800 MAX-ACCESS read-write 1801 STATUS current 1802 DESCRIPTION 1803 "The mteObjectsName of a group of objects from 1804 mteObjectsTable if mteEventActions has 'notification' set. 1805 These objects are to be added to any Notification generated by 1806 this event. 1808 Objects may also be added based on the trigger that stimulated 1809 the event. 1811 A length of 0 indicates no additional objects." 1812 DEFVAL { ''H } 1813 ::= { mteEventNotificationEntry 3 } 1815 Kavasseri and Claise Standard Track 39 1816 -- 1817 -- Event Set Table 1818 -- 1820 mteEventSetTable OBJECT-TYPE 1821 SYNTAX SEQUENCE OF MteEventSetEntry 1822 MAX-ACCESS not-accessible 1823 STATUS current 1824 DESCRIPTION 1825 "A table of management event action information." 1826 ::= { mteEvent 4 } 1828 mteEventSetEntry OBJECT-TYPE 1829 SYNTAX MteEventSetEntry 1830 MAX-ACCESS not-accessible 1831 STATUS current 1832 DESCRIPTION 1833 "Information about a single event's set option. Entries 1834 automatically exist in this this table for each mteEventEntry 1835 that has 'set' set in mteEventActions." 1836 INDEX { mteOwner, IMPLIED mteEventName } 1837 ::= { mteEventSetTable 1 } 1839 MteEventSetEntry ::= SEQUENCE { 1840 mteEventSetObject OBJECT IDENTIFIER, 1841 mteEventSetObjectWildcard TruthValue, 1842 mteEventSetValue Integer32, 1843 mteEventSetTargetTag SnmpTagValue, 1844 mteEventSetContextName SnmpAdminString, 1845 mteEventSetContextNameWildcard TruthValue 1846 } 1848 mteEventSetObject OBJECT-TYPE 1849 SYNTAX OBJECT IDENTIFIER 1850 MAX-ACCESS read-write 1851 STATUS current 1852 DESCRIPTION 1853 "The object identifier from the MIB object to set if 1854 mteEventActions has 'set' set. 1856 This object identifier may be wildcarded by leaving 1857 sub-identifiers off the end, in which case 1858 nteEventSetObjectWildCard must be 'true'. 1860 Kavasseri and Claise Standard Track 40 1861 If mteEventSetObject is wildcarded the instance used to set the 1862 object to which it points is the same as the instance from the 1863 value of mteTriggerValueID that triggered the event. 1865 Each instance that fills the wildcard is independent of any 1866 additional instances, that is, wildcarded objects operate 1867 as if there were a separate table entry for each instance 1868 that fills the wildcard without having to actually predict 1869 all possible instances ahead of time. 1871 Bad object identifiers or a mismatch between truncating the 1872 identifier and the value of mteSetObjectWildcard 1873 result in operation as one would expect when providing the 1874 wrong identifier to a Set operation. The Set will fail or set 1875 the wrong object. If the value syntax of the destination 1876 object is not correct, the Set fails with the normal SNMP 1877 error code." 1878 DEFVAL { zeroDotZero } 1879 ::= { mteEventSetEntry 1 } 1881 mteEventSetObjectWildcard OBJECT-TYPE 1882 SYNTAX TruthValue 1883 MAX-ACCESS read-write 1884 STATUS current 1885 DESCRIPTION 1886 "Control over whether mteEventSetObject is to be treated as 1887 fully-specified or wildcarded, with 'true' indicating wildcard 1888 if mteEventActions has 'set' set." 1889 DEFVAL { false } 1890 ::= { mteEventSetEntry 2 } 1892 mteEventSetValue OBJECT-TYPE 1893 SYNTAX Integer32 1894 MAX-ACCESS read-write 1895 STATUS current 1896 DESCRIPTION 1897 "The value to which to set the object at mteEventSetObject 1898 if mteEventActions has 'set' set." 1899 DEFVAL { 0 } 1900 ::= { mteEventSetEntry 3 } 1902 mteEventSetTargetTag OBJECT-TYPE 1903 SYNTAX SnmpTagValue 1904 MAX-ACCESS read-write 1905 STATUS current 1907 Kavasseri and Claise Standard Track 41 1908 DESCRIPTION 1909 "The tag for the target(s) at which to set the object at 1910 mteEventSetObject to mteEventSetValue if mteEventActions 1911 has 'set' set. 1913 Systems limited to self management MAY reject a non-zero 1914 length for the value of this object. 1916 A length of 0 indicates the local system. In this case, 1917 access to the objects indicated by mteEventSetObject is under 1918 the security credentials of the requester that set 1919 mteTriggerEntryStatus to 'active'. Those credentials are the 1920 input parameters for isAccessAllowed from the Architecture for 1921 Describing SNMP Management Frameworks. 1923 Otherwise access rights are checked according to the security 1924 parameters resulting from the tag." 1925 DEFVAL { ''H } 1926 ::= { mteEventSetEntry 4 } 1928 mteEventSetContextName OBJECT-TYPE 1929 SYNTAX SnmpAdminString 1930 MAX-ACCESS read-write 1931 STATUS current 1932 DESCRIPTION 1933 "The management context in which to set mteEventObjectID. 1934 if mteEventActions has 'set' set. 1936 This may be wildcarded by leaving characters off the end. To 1937 indicate such wildcarding mteEventSetContextNameWildcard must 1938 be 'true'. 1940 If this context name is wildcarded the value used to complete 1941 the wildcarding of mteTriggerContextName will be appended." 1942 DEFVAL { ''H } 1943 ::= { mteEventSetEntry 5 } 1945 mteEventSetContextNameWildcard OBJECT-TYPE 1946 SYNTAX TruthValue 1947 MAX-ACCESS read-write 1948 STATUS current 1949 DESCRIPTION 1950 "Control for whether mteEventSetContextName is to be treated as 1951 fully-specified or wildcarded, with 'true' indicating wildcard 1952 if mteEventActions has 'set' set." 1954 Kavasseri and Claise Standard Track 42 1955 DEFVAL { false } 1956 ::= { mteEventSetEntry 6 } 1958 -- 1959 -- Notifications 1960 -- 1962 dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::= 1963 { dismanEventMIB 2 } 1964 dismanEventMIBNotifications OBJECT IDENTIFIER ::= 1965 { dismanEventMIBNotificationPrefix 0 } 1966 dismanEventMIBNotificationObjects OBJECT IDENTIFIER 1967 ::= { dismanEventMIBNotificationPrefix 1 } 1969 -- 1970 -- Notification Objects 1971 -- 1973 mteHotTrigger OBJECT-TYPE 1974 SYNTAX SnmpAdminString 1975 MAX-ACCESS accessible-for-notify 1976 STATUS current 1977 DESCRIPTION 1978 "The name of the trigger causing the notification." 1979 ::= { dismanEventMIBNotificationObjects 1 } 1981 mteHotTargetName OBJECT-TYPE 1982 SYNTAX SnmpAdminString 1983 MAX-ACCESS accessible-for-notify 1984 STATUS current 1985 DESCRIPTION 1986 "The SNMP Target MIB's snmpTargetAddrName related to the 1987 notification." 1988 ::= { dismanEventMIBNotificationObjects 2 } 1990 mteHotContextName OBJECT-TYPE 1991 SYNTAX SnmpAdminString 1992 MAX-ACCESS accessible-for-notify 1993 STATUS current 1994 DESCRIPTION 1995 "The context name related to the notification. This MUST be as 1996 fully-qualified as possible, including filling in wildcard 1997 information determined in processing." 1998 ::= { dismanEventMIBNotificationObjects 3 } 2000 Kavasseri and Claise Standard Track 43 2001 mteHotOID OBJECT-TYPE 2002 SYNTAX OBJECT IDENTIFIER 2003 MAX-ACCESS accessible-for-notify 2004 STATUS current 2005 DESCRIPTION 2006 "The object identifier of the destination object related to the 2007 notification. This MUST be as fully-qualified as possible, 2008 including filling in wildcard information determined in 2009 processing. 2011 For a trigger-related notification this is from 2012 mteTriggerValueID. 2014 For a set failure this is from mteEventSetObject." 2015 ::= { dismanEventMIBNotificationObjects 4 } 2017 mteHotValue OBJECT-TYPE 2018 SYNTAX Integer32 2019 MAX-ACCESS accessible-for-notify 2020 STATUS current 2021 DESCRIPTION 2022 "The value of the object at mteTriggerValueID when a 2023 trigger fired." 2024 ::= { dismanEventMIBNotificationObjects 5 } 2026 mteFailedReason OBJECT-TYPE 2027 SYNTAX FailureReason 2028 MAX-ACCESS accessible-for-notify 2029 STATUS current 2030 DESCRIPTION 2031 "The reason for the failure of an attempt to check for a 2032 trigger condition or set an object in response to an event." 2033 ::= { dismanEventMIBNotificationObjects 6 } 2035 -- 2036 -- Notifications 2037 -- 2039 mteTriggerFired NOTIFICATION-TYPE 2040 OBJECTS { mteHotTrigger, 2041 mteHotTargetName, 2042 mteHotContextName, 2043 mteHotOID, 2044 mteHotValue } 2045 STATUS current 2047 Kavasseri and Claise Standard Track 44 2048 DESCRIPTION 2049 "Notification that the trigger indicated by the object 2050 instances has fired, for triggers with mteTriggerType 2051 'boolean' or 'existence'." 2052 ::= { dismanEventMIBNotifications 1 } 2054 mteTriggerRising NOTIFICATION-TYPE 2055 OBJECTS { mteHotTrigger, 2056 mteHotTargetName, 2057 mteHotContextName, 2058 mteHotOID, 2059 mteHotValue } 2060 STATUS current 2061 DESCRIPTION 2062 "Notification that the rising threshold was met for triggers 2063 with mteTriggerType 'threshold'." 2064 ::= { dismanEventMIBNotifications 2 } 2066 mteTriggerFalling NOTIFICATION-TYPE 2067 OBJECTS { mteHotTrigger, 2068 mteHotTargetName, 2069 mteHotContextName, 2070 mteHotOID, 2071 mteHotValue } 2072 STATUS current 2073 DESCRIPTION 2074 "Notification that the falling threshold was met for triggers 2075 with mteTriggerType 'threshold'." 2076 ::= { dismanEventMIBNotifications 3 } 2078 mteTriggerFailure NOTIFICATION-TYPE 2079 OBJECTS { mteHotTrigger, 2080 mteHotTargetName, 2081 mteHotContextName, 2082 mteHotOID, 2083 mteFailedReason } 2084 STATUS current 2085 DESCRIPTION 2086 "Notification that an attempt to check a trigger has failed. 2088 The network manager must enable this notification only with 2089 a certain fear and trembling, as it can easily crowd out more 2090 important information. It should be used only to help diagnose 2091 a problem that has appeared in the error counters and can not 2092 be found otherwise." 2094 Kavasseri and Claise Standard Track 45 2095 ::= { dismanEventMIBNotifications 4 } 2097 mteEventSetFailure NOTIFICATION-TYPE 2098 OBJECTS { mteHotTrigger, 2099 mteHotTargetName, 2100 mteHotContextName, 2101 mteHotOID, 2102 mteFailedReason } 2103 STATUS current 2104 DESCRIPTION 2105 "Notification that an attempt to do a set in response to an 2106 event has failed. 2108 The network manager must enable this notification only with 2109 a certain fear and trembling, as it can easily crowd out more 2110 important information. It should be used only to help diagnose 2111 a problem that has appeared in the error counters and can not 2112 be found otherwise." 2113 ::= { dismanEventMIBNotifications 5 } 2115 -- 2116 -- Conformance 2117 -- 2119 dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 } 2120 dismanEventMIBCompliances OBJECT IDENTIFIER ::= 2121 { dismanEventMIBConformance 1 } 2122 dismanEventMIBGroups OBJECT IDENTIFIER ::= 2123 { dismanEventMIBConformance 2 } 2125 -- Compliance 2127 dismanEventMIBCompliance MODULE-COMPLIANCE 2128 STATUS current 2129 DESCRIPTION 2130 "The compliance statement for entities which implement 2131 the Event MIB." 2132 MODULE -- this module 2133 MANDATORY-GROUPS { 2134 dismanEventResourceGroup, 2135 dismanEventTriggerGroup, 2136 dismanEventObjectsGroup, 2137 dismanEventEventGroup, 2138 dismanEventNotificationObjectGroup, 2139 dismanEventNotificationGroup 2141 Kavasseri and Claise Standard Track 46 2142 } 2144 OBJECT mteTriggerTargetTag 2145 MIN-ACCESS read-only 2146 DESCRIPTION 2147 "Write access is not required, thus limiting 2148 monitoring to the local system or pre- 2149 configured remote systems." 2151 OBJECT mteEventSetTargetTag 2152 MIN-ACCESS read-only 2153 DESCRIPTION 2154 "Write access is not required, thus limiting 2155 setting to the local system or pre-configured 2156 remote systems." 2158 OBJECT mteTriggerValueIDWildcard 2159 MIN-ACCESS read-only 2160 DESCRIPTION 2161 "Write access is not required, thus allowing 2162 the system not to implement wildcarding." 2164 OBJECT mteTriggerContextNameWildcard 2165 MIN-ACCESS read-only 2166 DESCRIPTION 2167 "Write access is not required, thus allowing 2168 the system not to implement wildcarding." 2170 OBJECT mteObjectsIDWildcard 2171 MIN-ACCESS read-only 2172 DESCRIPTION 2173 "Write access is not required, thus allowing 2174 the system not to implement wildcarding." 2176 OBJECT mteEventSetContextNameWildcard 2177 MIN-ACCESS read-only 2178 DESCRIPTION 2179 "Write access is not required, thus allowing 2180 the system not to implement wildcarding." 2182 ::= { dismanEventMIBCompliances 1 } 2184 -- Units of Conformance 2186 Kavasseri and Claise Standard Track 47 2187 dismanEventResourceGroup OBJECT-GROUP 2188 OBJECTS { 2189 mteResourceSampleMinimum, 2190 mteResourceSampleInstanceMaximum, 2191 mteResourceSampleInstances, 2192 mteResourceSampleInstancesHigh, 2193 mteResourceSampleInstanceLacks 2194 } 2195 STATUS current 2196 DESCRIPTION 2197 "Event resource status and control objects." 2198 ::= { dismanEventMIBGroups 1 } 2200 dismanEventTriggerGroup OBJECT-GROUP 2201 OBJECTS { 2202 mteTriggerFailures, 2204 mteTriggerComment, 2205 mteTriggerTest, 2206 mteTriggerSampleType, 2207 mteTriggerValueID, 2208 mteTriggerValueIDWildcard, 2209 mteTriggerTargetTag, 2210 mteTriggerContextName, 2211 mteTriggerContextNameWildcard, 2212 mteTriggerFrequency, 2213 mteTriggerObjectsOwner, 2214 mteTriggerObjects, 2215 mteTriggerEnabled, 2216 mteTriggerEntryStatus, 2217 mteTriggerEntryStorageType, 2219 mteTriggerDeltaDiscontinuityID, 2220 mteTriggerDeltaDiscontinuityIDWildcard, 2221 mteTriggerDeltaDiscontinuityIDType, 2222 mteTriggerExistenceTest, 2223 mteTriggerExistenceStartup, 2224 mteTriggerExistenceObjectsOwner, 2225 mteTriggerExistenceObjects, 2226 mteTriggerExistenceEventOwner, 2227 mteTriggerExistenceEvent, 2229 mteTriggerBooleanComparison, 2230 mteTriggerBooleanValue, 2231 mteTriggerBooleanStartup, 2233 Kavasseri and Claise Standard Track 48 2234 mteTriggerBooleanObjectsOwner, 2235 mteTriggerBooleanObjects, 2236 mteTriggerBooleanEventOwner, 2237 mteTriggerBooleanEvent, 2239 mteTriggerThresholdStartup, 2240 mteTriggerThresholdObjectsOwner, 2241 mteTriggerThresholdObjects, 2242 mteTriggerThresholdRising, 2243 mteTriggerThresholdFalling, 2244 mteTriggerThresholdDeltaRising, 2245 mteTriggerThresholdDeltaFalling, 2246 mteTriggerThresholdRisingEventOwner, 2247 mteTriggerThresholdRisingEvent, 2248 mteTriggerThresholdFallingEventOwner, 2249 mteTriggerThresholdFallingEvent, 2250 mteTriggerThresholdDeltaRisingEventOwner, 2251 mteTriggerThresholdDeltaRisingEvent, 2252 mteTriggerThresholdDeltaFallingEventOwner, 2253 mteTriggerThresholdDeltaFallingEvent 2254 } 2255 STATUS current 2256 DESCRIPTION 2257 "Event triggers." 2258 ::= { dismanEventMIBGroups 2 } 2260 dismanEventObjectsGroup OBJECT-GROUP 2261 OBJECTS { 2262 mteObjectsID, 2263 mteObjectsIDWildcard, 2264 mteObjectsEntryStatus, 2265 mteObjectsEntryStorageType 2267 } 2268 STATUS current 2269 DESCRIPTION 2270 "Supplemental objects." 2271 ::= { dismanEventMIBGroups 3 } 2273 dismanEventEventGroup OBJECT-GROUP 2274 OBJECTS { 2275 mteEventFailures, 2277 mteEventComment, 2278 mteEventActions, 2280 Kavasseri and Claise Standard Track 49 2281 mteEventEnabled, 2282 mteEventEntryStatus, 2283 mteEventEntryStorageType, 2285 mteEventNotification, 2286 mteEventNotificationObjectsOwner, 2287 mteEventNotificationObjects, 2289 mteEventSetObject, 2290 mteEventSetObjectWildcard, 2291 mteEventSetValue, 2292 mteEventSetTargetTag, 2293 mteEventSetContextName, 2294 mteEventSetContextNameWildcard 2295 } 2296 STATUS current 2297 DESCRIPTION 2298 "Events." 2299 ::= { dismanEventMIBGroups 4 } 2301 dismanEventNotificationObjectGroup OBJECT-GROUP 2302 OBJECTS { 2303 mteHotTrigger, 2304 mteHotTargetName, 2305 mteHotContextName, 2306 mteHotOID, 2307 mteHotValue, 2308 mteFailedReason 2309 } 2310 STATUS current 2311 DESCRIPTION 2312 "Notification objects." 2313 ::= { dismanEventMIBGroups 5 } 2315 dismanEventNotificationGroup NOTIFICATION-GROUP 2316 NOTIFICATIONS { 2317 mteTriggerFired, 2318 mteTriggerRising, 2319 mteTriggerFalling, 2320 mteTriggerFailure, 2321 mteEventSetFailure 2322 } 2323 STATUS current 2324 DESCRIPTION 2325 "Notifications." 2327 Kavasseri and Claise Standard Track 50 2328 ::= { dismanEventMIBGroups 6 } 2330 END 2332 8. Security Considerations 2334 Security issues are discussed in the Security section and in the 2335 DESCRIPTION clauses of relevant objects. 2337 9. IANA Considerations 2339 This document has no actions for IANA. 2341 10. References 2343 10.1 Informative References 2345 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2346 J., Rose, M. and S. Waldbusser, "Structure of Management 2347 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2348 1999. 2350 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2351 J., Rose, M. and S. Waldbusser, "Textual Conventions for 2352 SMIv2", STD 58, RFC 2579, April 1999. 2354 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2355 J., Rose, M. and S. Waldbusser, "Conformance Statements 2356 for SMIv2", STD 58, RFC 2580, April 1999. 2358 [RFC3416] Presuhn, R., "Version 2 of the Protocol Operations for 2359 the Simple Network Management Protocol (SNMP) ", STD 62, 2360 RFC 3416, December 2002. 2362 10.2 Informative References 2364 [RFC1451] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 2365 "Manager-to- Manager Management Information Base", RFC 2366 1451, April 1993. 2368 [RFC2819] Waldbusser, S., "Remote Network Monitoring Management 2369 Information Base", RFC 2819, May 2000. 2371 [RFC2981] Stewart, B., "Event MIB", RFC 2981, October 2000. 2373 [RFC2982] Stewart, B., "Distributed Management Expression MIB", 2374 RFC 2982, October 2000. 2376 Kavasseri and Claise Standard Track 51 2378 [RFC3014] Kavasseri, R., "Notification Log MIB", RFC 3014, 2379 November 2000 2381 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2382 "Introduction and Applicability Statements for Internet- 2383 Standard Management Framework", RFC 3410, December 2002. 2385 [RFC3413] Levi, D., Meyer, P. and B. Stewart, "Simple Network 2386 Management Protocol (SNMP) Applications", RFC 3413, 2387 December 2002. 2389 [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 2390 Access Control Model (VACM) for the Simple Network 2391 Management Protocol (SNMP)", RFC 3415, December 2002. 2393 11. Acknowledgements 2395 This MIB contains considerable contributions from the RMON MIB, the 2396 Distributed Management Design Team (Andy Bierman, Maria Greene, Bob 2397 Stewart, and Steve Waldbusser), the Distributed Management Working 2398 Group, and colleagues at Cisco. 2400 Authors' Addresses 2402 Bob Stewart 2403 Cisco Systems, Inc. 2404 170 West Tasman Drive 2405 San Jose, CA 95134-1706 2406 U.S.A. 2408 Editors' Addresses 2410 Ramanathan Kavasseri 2411 Cisco Systems, Inc. 2412 170 West Tasman Drive 2413 San Jose, CA 95134-1706 2414 U.S.A. 2416 Phone: +1 408 527 2446 2417 EMail: ramk@cisco.com 2419 Benoit Claise 2420 Cisco Systems, Inc. 2421 Pegasus Parc 2422 7 De Kleetlan Diegem 2423 Brabant, Belgium 1831. 2425 Phone: +32 (0)2 704 5622 2427 Kavasseri and Claise Standard Track 52 2428 Email: bclaise@cisco.com 2430 Intellectual Property Statement 2432 The IETF takes no position regarding the validity or scope of any 2433 Intellectual Property Rights or other rights that might be claimed 2434 to pertain to the implementation or use of the technology described 2435 in this document or the extent to which any license under such 2436 rights might or might not be available; nor does it represent that 2437 it has made any independent effort to identify any such rights. 2438 Information on the procedures with respect to rights in RFC 2439 documents can be found in BCP 78 and BCP 79. 2441 Copies of IPR disclosures made to the IETF Secretariat and any 2442 assurances of licenses to be made available, or the result of an 2443 attempt made to obtain a general license or permission for the use 2444 of such proprietary rights by implementers or users of this 2445 specification can be obtained from the IETF on-line IPR repository 2446 at http://www.ietf.org/ipr. 2448 The IETF invites any interested party to bring to its attention any 2449 copyrights, patents or patent applications, or other proprietary 2450 rights that may cover technology that may be required to implement 2451 this standard. Please address the information to the IETF at ietf- 2452 ipr@ietf.org. 2454 The IETF has been notified of intellectual property rights claimed 2455 in regard to some or all of the specification contained in this 2456 document. For more information consult the online list of claimed 2457 rights. 2459 Disclaimer of Validity 2461 This document and the information contained herein are provided on 2462 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 2463 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 2464 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 2465 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2466 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2467 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2469 Copyright Statement 2471 Copyright (C) The Internet Society (2005). This document is subject 2472 to the rights, licenses and restrictions contained in BCP 78, and 2473 except as set forth therein, the authors retain all their rights. 2475 Kavasseri and Claise Standard Track 53 2476 Acknowledgment 2478 Funding for the RFC Editor function is currently provided by the 2479 Internet Society. 2481 Kavasseri and Claise Standard Track 54