idnits 2.17.1 draft-ietf-disman-event-mib-06.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 9 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 296 has weird spacing: '...achable can't...' == Line 2130 has weird spacing: '...for the purpo...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (22 February 1999) is 9194 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '15') (Obsoleted by RFC 2575) ** Obsolete normative reference: RFC 1757 (ref. '16') (Obsoleted by RFC 2819) ** Downref: Normative reference to an Historic RFC: RFC 1451 (ref. '17') -- Possible downref: Non-RFC (?) normative reference: ref. '18' -- Possible downref: Non-RFC (?) normative reference: ref. '19' Summary: 23 errors (**), 0 flaws (~~), 5 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft Distributed Management Event MIB 22 February 1999 4 Event MIB 6 22 February 1999 8 draft-ietf-disman-event-mib-06.txt 10 Bob Stewart 11 Cisco Systems, Inc. 12 bstewart@cisco.com 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with all 17 provisions of Section 10 of RFC2026. 19 Internet-Drafts are working documents of the Internet Engineering Task 20 Force (IETF), its areas, and its working groups. Note that other groups 21 may also distribute working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet- Drafts as reference material 26 or to cite them other than as ``work in progress.'' 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 Distribution of this document is unlimited. Please send comments to the 32 Distributed Management Working Group, . 34 Copyright Notice 36 Copyright (C) The Internet Society (1999). All Rights Reserved. 38 1. Abstract 40 This memo defines an experimental portion of the Management Information 41 Base (MIB) for use with network management protocols in the Internet 42 community. In particular, it describes managed objects used for 43 managing monitoring of MIB objects and taking action through events. 45 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 46 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 47 document are to be interpreted as described in RFC 2119. 49 2. The SNMP Management Framework 51 The SNMP Management Framework presently consists of five major 52 components: 54 o An overall architecture, described in RFC 2271 [1]. 56 o Mechanisms for describing and naming objects and events for the 57 purpose of management. The first version of this Structure of 58 Management Information (SMI) is called SMIv1 and described in 59 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 60 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 61 1904 [7]. 63 o Message protocols for transferring management information. The 64 first version of the SNMP message protocol is called SNMPv1 and 65 described in RFC 1157 [8]. A second version of the SNMP message 66 protocol, which is not an Internet standards track protocol, is 67 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 68 The third version of the message protocol is called SNMPv3 and 69 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 71 o Protocol operations for accessing management information. The 72 first set of protocol operations and associated PDU formats is 73 described in RFC 1157 [8]. A second set of protocol operations 74 and associated PDU formats is described in RFC 1905 [13]. 76 o A set of fundamental applications described in RFC 2273 [14] and 77 the view-based access control mechanism described in RFC 2275 78 [15]. 80 Managed objects are accessed via a virtual information store, termed the 81 Management Information Base or MIB. Objects in the MIB are defined 82 using the mechanisms defined in the SMI. 84 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 85 conforming to the SMIv1 can be produced through the appropriate 86 translations. The resulting translated MIB must be semantically 87 equivalent, except where objects or events are omitted because no 88 translation is possible (use of Counter64). Some machine readable 89 information in SMIv2 will be converted into textual descriptions in 90 SMIv1 during the translation process. However, this loss of machine 91 readable information is not considered to change the semantics of the 92 MIB. 94 3. Overview 96 With network sizes well beyond the ability of people to management them 97 directly, automated, distributed management is vital. An important 98 aspect of such management is the ability of a system to monitor itself 99 or for some other system to monitor it. 101 The Event MIB provides the ability to monitor MIB objects on the local 102 system or on a remote system and take simple action when a trigger 103 condition is met. 105 The MIB is intended to suit either a relatively powerful manager or 106 mid-level manager, as well as a somewhat more limited self-managing 107 system. 109 4. Relationship to Other MIBs 111 The Event MIB is based on extensive experience with the RMON MIB [16] 112 and its alarm and event groups and is intended as a replacement for 113 those groups. The Event MIB calls "triggers" what the RMON MIB called 114 "alarms," but the concepts are the same. Event MIB triggers maintain 115 the RMON handling of thresholds and add the concept of booleans. Event 116 MIB events maintain the RMON concept of sending an SNMP notification in 117 response to a trigger and add the concept of setting a MIB object. 119 The Event MIB is the successor and update to SNMPv2's Manager-to-Manager 120 MIB [17] which was declared Historic pending this work. 122 The Event MIB depends on the services of the SNMPv3 Management Target 123 and Notification MIBs [14]. 125 The Event MIB is nicely complemented by the Distributed Management 126 Expression MIB [18], which is the expected source of boolean objects to 127 monitor. Note that there is considerable overlap between the wildcard 128 and delta sample capabilities of the Event and Expression MIBs. A 129 carefully-planned implementation might well use common code to provide 130 the overlapping functions. 132 5. MIB Sections 134 The MIB has four sections: triggers, objects, events, and notifications. 135 Triggers define the conditions that lead to events. Events may cause 136 notifications. 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 for 141 the trigger. 143 The objects table lists objects that can be added to notifications based 144 on the trigger, the trigger test type, or the event that resulted in the 145 notification. 147 The event table defines what happens when an event is triggered, sending 148 a notification, setting a MIB object or both. It has supplementary, 149 companion tables for additional objects that depend on the action taken. 151 The notification section defines a set of generic notifications to go 152 with the events and for Event MIB error handling, and it defines a set 153 of objects to put in those notifications. 155 6. Operation 157 The Event MIB is instrumentation for a distributed management 158 application that monitors MIB objects. In its simplest form this 159 application monitors individual, local MIB objects, just as an RMON 160 probe fulfills the functions implied by RMON's alarm and event 161 operation. Additionally the application can monitor remote objects and 162 wildcarded groups of objects. 164 Remote monitoring uses the tag service of the Management Target MIB to 165 select and access remote systems as an ordinary SNMP-based management 166 application. Local monitoring may be via a more intimate, local 167 interface which may, for example, bypass SNMP encoding but otherwise is 168 functionally identical to remote SNMP operation, including the 169 application of access control. A self-management only system may not 170 implement remote monitoring. 172 Wildcards indicate that the application should use a GetNext-type 173 operation to find the zero or more instances implied by a truncated 174 object identifier, just like an ordinary SNMP-based management 175 application. Each instance of a wildcard is treated as if it were a 176 separate entry, that is the instances of a wildcarded object are 177 independent of one another. For example, a wild-carded object may 178 trigger an event and result in the setting of another wildcarded object. 179 The instance that satisfied the trigger function is used to perform the 180 set function. All of this takes place independently of any additional 181 instances that may fill the wildcard. 183 Error handling is by notification, which at first thought violates the 184 principle that notifications may be lost or become a crippling burden, 185 but the intent is that such error notifications be enabled only for the 186 diagnosis of problems indicated by error counters and if the 187 notifications are being lost they be directed to the log as described in 188 the Notification Log MIB [19]. Note that this does not mean the 189 Notification Log MIB is required, since in fact notifications usually 190 are not lost, but that the Notification Log MIB can be helpful with this 191 as well as other MIBs that include notifications. 193 7. Security 195 Security of Event MIB entries depends on SNMPv3 access control for the 196 entire MIB or for subsets based on substrings of trigger and event 197 names. 199 Security of monitored objects for remote access depends on the 200 Management Target MIB. Security for local access can depend on the 201 Management Target MIB or on recording appropriate security credentials 202 of the creator of an entry and using those to access the local objects. 203 These security credentials are the parameters necessary as inputs to 204 isAccessAllowed from the Architecture for Describing SNMP Management 205 Frameworks. When accessing local objects without using a local target 206 tag, the system must (conceptually) use isAccessAllowed to ensure that 207 it does not violate security. 209 To facilitate the provisioning of access control by a security 210 administrator for this MIB itself using the View-Based Access Control 211 Model (VACM) defined in RFC 2275 [15] for tables in which multiple users 212 may need to independently create or modify entries, the initial index is 213 used as an "owner index". Such an initial index has a syntax of 214 SnmpAdminString, and can thus be trivially mapped to a securityName or 215 groupName as defined in VACM, in accordance with a security policy. 217 All entries in related tables belonging to a particular user will have 218 the same value for this initial index. For a given user's entries in a 219 particular table, the object identifiers for the information in these 220 entries will have the same subidentifiers (except for the "column" 221 subidentifier) up to the end of the encoded owner index. To configure 222 VACM to permit access to this portion of the table, one would create 223 vacmViewTreeFamilyTable entries with the value of 224 vacmViewTreeFamilySubtree including the owner index portion, and 225 vacmViewTreeFamilyMask "wildcarding" the column subidentifier. More 226 elaborate configurations are possible. 228 8. Definitions 230 DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN 232 IMPORTS 233 MODULE-IDENTITY, OBJECT-TYPE, 234 experimental, Integer32, Unsigned32, 235 NOTIFICATION-TYPE, Counter32, 236 Gauge32 FROM SNMPv2-SMI 237 TEXTUAL-CONVENTION, RowStatus, 238 TruthValue FROM SNMPv2-TC 239 MODULE-COMPLIANCE, OBJECT-GROUP, 240 NOTIFICATION-GROUP FROM SNMPv2-CONF 241 sysUpTime FROM SNMPv2-MIB 242 SnmpTagValue FROM SNMP-TARGET-MIB 243 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 245 dismanEventMIB MODULE-IDENTITY 246 LAST-UPDATED "9902221700Z" 247 ORGANIZATION "IETF Distributed Management Working Group" 248 CONTACT-INFO "Bob Stewart 249 Cisco Systems, Inc. 250 170 West Tasman Drive, 251 San Jose CA 95134-1706. 252 Phone: +1 408 526 4527 253 Email: bstewart@cisco.com" 254 DESCRIPTION 255 "The MIB module for defining event triggers and actions 256 for network management purposes." 257 ::= { experimental xx } 259 dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 } 261 mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 } 262 mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 } 263 mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 } 264 mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 } 266 -- For use as a default OID: 268 zeroDotZero OBJECT IDENTIFIER ::= { 0 0 } 270 -- 271 -- Textual Conventions 272 -- 274 FailureReason ::= TEXTUAL-CONVENTION 275 STATUS current 276 DESCRIPTION 277 "Reasons for failures in an attempt to perform a management 278 request. 280 The first group of errors, numbered less than 0, are related 281 to problems in sending the request. The existence of a 282 particular error code here does not imply that all 283 implementations are capable of sensing that error and 284 returning that code. 286 The second group, numbered greater than 0, are copied 287 directly from SNMP protocol operations and are intended to carry 288 exactly the meanings defined for the protocol as returned in 289 an SNMP response. 291 localResourceLack some local resource such as memory lacking 292 or mteResourceSampleInstanceMaximum 293 exceeded 294 badDestination unrecognized domain name or otherwise 295 invalid destination address 296 destinationUnreachable can't get to destination address 297 noResponse no response to SNMP request 298 badType the data syntax of a retrieved object 299 as not as expected 300 sampleOverrun another sample attempt occurred before 301 the previous one completed" 303 SYNTAX INTEGER { localResourceLack(-1), 304 badDestination(-2), 305 destinationUnreachable(-3), 306 noResponse(-4), 307 badType(-5), 308 sampleOverrun(-6), 310 noError(0), 312 tooBig(1), 313 noSuchName(2), 314 badValue(3), 315 readOnly(4), 316 genErr(5), 317 noAccess(6), 318 wrongType(7), 319 wrongLength(8), 320 wrongEncoding(9), 321 wrongValue(10), 322 noCreation(11), 323 inconsistentValue(12), 324 resourceUnavailable(13), 325 commitFailed(14), 326 undoFailed(15), 327 authorizationError(16), 328 notWritable(17), 329 inconsistentName(18) } 330 -- 331 -- Resource Control Section 332 -- 334 mteResourceSampleMinimum OBJECT-TYPE 335 SYNTAX Integer32 (-1 | 1..600) 336 UNITS "seconds" 337 MAX-ACCESS read-write 338 STATUS current 339 DESCRIPTION 341 "The minimum mteTriggerFrequency this system will accept. A 342 system may use the larger values of this minimum to lessen the 343 impact of sampling. 345 Unless explicitly resource limited, a system's value for 346 this object should be 1. 348 Changing this value will not invalidate an existing setting 349 of mteTriggerFrequency." 350 ::= { mteResource 1 } 352 mteResourceSampleInstanceMaximum OBJECT-TYPE 353 SYNTAX Unsigned32 354 UNITS "instances" 355 MAX-ACCESS read-write 356 STATUS current 357 DESCRIPTION 358 "The maximum number of instance entries this system will 359 support for sampling. 361 These are the entries that maintain state, one for each 362 instance of each sampled object as selected by 363 mteTriggerValueID. Note that wildcarded objects result 364 in multiple instances of this state. 366 A value of 0 indicates no preset limit, that is, the limit 367 is dynamic based on system operation and resources. 369 Unless explicitly resource limited, a system's value for 370 this object should be 0. 372 Changing this value will not eliminate or inhibit existing sample 373 state but could prevent allocation of additional state 374 information." 375 ::= { mteResource 2 } 377 mteResourceSampleInstances OBJECT-TYPE 378 SYNTAX Gauge32 379 UNITS "instances" 380 MAX-ACCESS read-only 381 STATUS current 382 DESCRIPTION 383 "The number of currently active instance entries as 384 defined for mteResourceSampleInstanceMaximum." 385 ::= { mteResource 3 } 387 mteResourceSampleInstancesHigh OBJECT-TYPE 388 SYNTAX Gauge32 389 UNITS "instances" 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The highest value of mteResourceSampleInstances that has 394 occurred since initialization of the management system." 395 ::= { mteResource 4 } 397 mteResourceSampleInstanceLacks OBJECT-TYPE 398 SYNTAX Counter32 399 UNITS "instances" 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "The number of times this system could not take a new sample 404 because that allocation would have exceeded the limit set by 405 mteResourceSampleInstanceMaximum." 406 ::= { mteResource 5 } 408 -- 409 -- Trigger Section 410 -- 412 -- Counters 414 mteTriggerFailures OBJECT-TYPE 415 SYNTAX Counter32 416 MAX-ACCESS read-only 417 STATUS current 418 DESCRIPTION 419 "The number of times an attempt to check for a trigger 420 condition has failed. This counts individually for each 421 attempt in a group of targets or each attempt for a 422 wildcarded object." 423 ::= { mteTrigger 1 } 425 -- 426 -- Trigger Table 427 -- 429 mteTriggerTable OBJECT-TYPE 430 SYNTAX SEQUENCE OF MteTriggerEntry 431 MAX-ACCESS not-accessible 432 STATUS current 433 DESCRIPTION 434 "A table of management event trigger information." 435 ::= { mteTrigger 2 } 437 mteTriggerEntry OBJECT-TYPE 438 SYNTAX MteTriggerEntry 439 MAX-ACCESS not-accessible 440 STATUS current 441 DESCRIPTION 442 "Information about a single trigger. Applications create and 443 delete entries using mteTriggerEntryStatus." 444 INDEX { mteOwner, IMPLIED mteTriggerName } 445 ::= { mteTriggerTable 1 } 447 MteTriggerEntry ::= SEQUENCE { 448 mteOwner SnmpAdminString, 449 mteTriggerName SnmpAdminString, 450 mteTriggerComment SnmpAdminString, 451 mteTriggerTest BITS, 452 mteTriggerSampleType INTEGER, 453 mteTriggerValueID OBJECT IDENTIFIER, 454 mteTriggerValueIDWildcard TruthValue, 455 mteTriggerTargetTag SnmpTagValue, 456 mteTriggerContextName SnmpAdminString, 457 mteTriggerContextNameWildcard TruthValue, 458 mteTriggerFrequency Unsigned32, 459 mteTriggerObjectsOwner SnmpAdminString, 460 mteTriggerObjects SnmpAdminString, 461 mteTriggerEnabled TruthValue, 462 mteTriggerEntryStatus RowStatus 463 } 465 mteOwner OBJECT-TYPE 466 SYNTAX SnmpAdminString (SIZE(0..32)) 467 MAX-ACCESS not-accessible 468 STATUS current 469 DESCRIPTION 470 "The owner of this entry. The exact semantics of this 471 string are subject to the security policy defined by the 472 security administrator." 473 ::= { mteTriggerEntry 1 } 475 mteTriggerName OBJECT-TYPE 476 SYNTAX SnmpAdminString (SIZE (1..32)) 477 MAX-ACCESS not-accessible 478 STATUS current 479 DESCRIPTION 480 "A locally-unique, administratively assigned name for the 481 trigger within the scope of mteOwner." 482 ::= { mteTriggerEntry 2 } 484 mteTriggerComment OBJECT-TYPE 485 SYNTAX SnmpAdminString 486 MAX-ACCESS read-create 487 STATUS current 488 DESCRIPTION 489 "A description of the trigger's function and use." 490 DEFVAL { ''H } 491 ::= { mteTriggerEntry 3 } 493 mteTriggerTest OBJECT-TYPE 494 SYNTAX BITS { existence(0), boolean(1), threshold(2) } 495 MAX-ACCESS read-create 496 STATUS current 497 DESCRIPTION 498 "The type of trigger test to perform. For 'boolean' and 499 'threshold' tests, the object at mteTriggerValueID must 500 evaluate to an integer, that is, anything that ends up encoded 501 for transmission as an integer. 503 For 'existence', the specific test is as selected by 504 mteTriggerExistenceTest. When an object appears or vanishes 505 the trigger fires. The trigger will not fire again until the 506 object has changed states. 508 For 'boolean', the specific test is as selected by 509 mteTriggerBooleanTest. If the test result is true the trigger 510 fires. The trigger will not fire again until the value has 511 become false and come back to true. 513 For 'threshold' the test works as described below for 514 mteTriggerThresholdStartup, mteTriggerThresholdRising, and 515 mteTriggerThresholdFalling. 517 Note that combining 'boolean' and 'threshold' tests on the 518 same object may be somewhat redundant." 519 DEFVAL { boolean } 520 ::= { mteTriggerEntry 4 } 522 mteTriggerSampleType OBJECT-TYPE 523 SYNTAX INTEGER { absoluteValue(1), deltaValue(2) } 524 MAX-ACCESS read-create 525 STATUS current 526 DESCRIPTION 527 "The type of sampling to perform. 529 An 'absoluteValue' sample requires only a single sample to be 530 meaningful, and is exactly the value of the object at 531 mteTriggerValueID at the sample time. 533 A 'deltaValue' requires two samples to be meaningful and is 534 thus not available for testing until the second and subsequent 535 samples after the object at mteTriggerValueID is first found 536 to exist. It is the difference between the two samples. For 537 unsigned values it is always positive, based on unsigned 538 arithmetic. For signed values it can be positive or negative. 540 For SNMP counters to be meaningful they must be sampled as a 541 'deltaValue'. 543 For 'deltaValue' mteTriggerDeltaTable contains further 544 parameters. 546 If only 'existence' is set in mteTriggerTest this object has 547 no meaning." 548 DEFVAL { absoluteValue } 549 ::= { mteTriggerEntry 5 } 551 mteTriggerValueID OBJECT-TYPE 552 SYNTAX OBJECT IDENTIFIER 553 MAX-ACCESS read-create 554 STATUS current 555 DESCRIPTION 556 "The object identifier of the MIB object to sample to see 557 if the trigger should fire. 559 This may be wildcarded by truncating all or part of the 560 instance portion, in which case the value is obtained 561 as if with a GetNext function, checking multiple values 562 if they exist. If such wildcarding is applied, 563 mteTriggerValueIDWildcard must be 'true' and if not it must 564 be 'false'. 566 Bad object identifiers or a mismatch between truncating the 567 identifier and the value of mteTriggerValueIDWildcard result 568 in operation as one would expect when providing the wrong 569 identifier to a Get or GetNext operation. The Get will fail 570 or get the wrong object. The GetNext will indeed get whatever 571 is next, proceeding until it runs past the initial part of the 572 identifier and perhaps many unintended objects for confusing 573 results. If the value syntax of those objects is not usable, 574 that results in a 'badType' error that terminates the scan. 576 Each instance that fills the wildcard is independent of any 577 additional instances, that is, wildcarded objects operate 578 as if there were a separate table entry for each instance 579 that fills the wildcard without having to actually predict 580 all possible instances ahead of time." 581 DEFVAL { zeroDotZero } 582 ::= { mteTriggerEntry 6 } 584 mteTriggerValueIDWildcard OBJECT-TYPE 585 SYNTAX TruthValue 586 MAX-ACCESS read-create 587 STATUS current 588 DESCRIPTION 589 "Control for whether mteTriggerValueID is to be treated as 590 fully-specified or wildcarded, with 'true' indicating wildcard." 591 DEFVAL { false } 592 ::= { mteTriggerEntry 7 } 594 mteTriggerTargetTag OBJECT-TYPE 595 SYNTAX SnmpTagValue 596 MAX-ACCESS read-create 597 STATUS current 598 DESCRIPTION 599 "The tag for the target(s) from which to obtain the condition 600 for a trigger check. 602 A length of 0 indicates the local system. In this case, 603 access to the objects indicated by mteTriggerValueID is under 604 the security credentials of the requester that set 605 mteTriggerEntryStatus to 'active'. Those credentials are the 606 input parameters for isAccessAllowed from the Architecture for 607 Describing SNMP Management Frameworks. 609 Otherwise access rights are checked according to the security 610 parameters resulting from the tag." 611 DEFVAL { ''H } 612 ::= { mteTriggerEntry 8 } 614 mteTriggerContextName OBJECT-TYPE 615 SYNTAX SnmpAdminString 616 MAX-ACCESS read-create 617 STATUS current 618 DESCRIPTION 619 "The management context from which to obtain mteTriggerValueID. 621 This may be wildcarded by leaving characters off the end. For 622 example use 'Repeater' to wildcard to 'Repeater1', 623 'Repeater2', 'Repeater-999.87b', and so on. To indicate such 624 wildcarding is intended, mteTriggerContextNameWildcard must 625 be 'true'. 627 Each instance that fills the wildcard is independent of any 628 additional instances, that is, wildcarded objects operate 629 as if there were a separate table entry for each instance 630 that fills the wildcard without having to actually predict 631 all possible instances ahead of time. 633 Operation of this feature assumes that the local system has a 634 list of available contexts against which to apply the 635 wildcard. If the objects are being read from the local 636 system, this is clearly the system's own list of contexts. 637 For a remote system a local version of such a list is not 638 defined by any current standard and may not be available, so 639 this function may not be supported." 640 DEFVAL { ''H } 641 ::= { mteTriggerEntry 9 } 643 mteTriggerContextNameWildcard OBJECT-TYPE 644 SYNTAX TruthValue 645 MAX-ACCESS read-create 646 STATUS current 647 DESCRIPTION 648 "Control for whether mteTriggerContextName is to be treated as 649 fully-specified or wildcarded, with 'true' indicating wildcard." 650 DEFVAL { false } 651 ::= { mteTriggerEntry 10 } 653 mteTriggerFrequency OBJECT-TYPE 654 SYNTAX Unsigned32 655 UNITS "seconds" 656 MAX-ACCESS read-create 657 STATUS current 658 DESCRIPTION 659 "The number of seconds to wait between trigger samples. To 660 encourage consistency in sampling, the interval is measured 661 from the beginning of one check to the beginning of the next 662 and the timer is restarted immediately when it expires, not 663 when the check completes. 665 If the next sample begins before the previous one completed the 666 system may either attempt to make the check or treat this as an 667 error condition with the error 'sampleOverrun'. 669 A frequency of 0 indicates instantaneous recognition of the 670 condition. This is not possible in many cases, but may 671 be supported in cases where it makes sense and the system is 672 able to do so. This feature allows the MIB to be used in 673 implementations where such interrupt-driven behavior is 674 possible and is not likely to be supported for all MIB objects 675 even then since such sampling generally has to be tightly 676 integrated into low-level code. 678 Systems that can support this should document those cases 679 where it can be used. In cases where it can not, setting this 680 object to 0 simply returns a bad value error." 681 DEFVAL { 600 } 682 ::= { mteTriggerEntry 11 } 684 mteTriggerObjectsOwner OBJECT-TYPE 685 SYNTAX SnmpAdminString (SIZE (0..32)) 686 MAX-ACCESS read-create 687 STATUS current 688 DESCRIPTION 689 "To go with mteTriggerObjects, the mteOwner of a group of 690 objects from mteObjectsTable." 691 DEFVAL { ''H } 692 ::= { mteTriggerEntry 12 } 694 mteTriggerObjects OBJECT-TYPE 695 SYNTAX SnmpAdminString (SIZE (0..32)) 696 MAX-ACCESS read-create 697 STATUS current 698 DESCRIPTION 699 "The mteObjectsName of a group of objects from 700 mteObjectsTable. These objects are to be added to any 701 Notification resulting from the firing of this trigger. 703 A list of objects may also be added based on the event or on 704 the value of mteTriggerTest. 706 A length of 0 indicates no additional objects." 707 DEFVAL { ''H } 708 ::= { mteTriggerEntry 13 } 710 mteTriggerEnabled OBJECT-TYPE 711 SYNTAX TruthValue 712 MAX-ACCESS read-create 713 STATUS current 714 DESCRIPTION 715 "A control to allow a trigger to be configured but not used. 716 When the value is 'false' the trigger is not sampled." 717 DEFVAL { false } 718 ::= { mteTriggerEntry 14 } 720 mteTriggerEntryStatus OBJECT-TYPE 721 SYNTAX RowStatus 722 MAX-ACCESS read-create 723 STATUS current 724 DESCRIPTION 725 "The control that allows creation and deletion of entries. 726 Once made active an entry may not be modified except to 727 delete it." 728 ::= { mteTriggerEntry 15 } 730 -- 731 -- Trigger Delta Table 732 -- 734 mteTriggerDeltaTable OBJECT-TYPE 735 SYNTAX SEQUENCE OF MteTriggerDeltaEntry 736 MAX-ACCESS not-accessible 737 STATUS current 738 DESCRIPTION 739 "A table of management event trigger information for delta 740 sampling." 741 ::= { mteTrigger 3 } 743 mteTriggerDeltaEntry OBJECT-TYPE 744 SYNTAX MteTriggerDeltaEntry 745 MAX-ACCESS not-accessible 746 STATUS current 747 DESCRIPTION 748 "Information about a single trigger's delta sampling. Entries 749 automatically exist in this this table for each mteTriggerEntry 750 that has mteTriggerSampleType set to 'deltaValue'." 751 INDEX { mteOwner, IMPLIED mteTriggerName } 752 ::= { mteTriggerDeltaTable 1 } 754 MteTriggerDeltaEntry ::= SEQUENCE { 755 mteTriggerDeltaDiscontinuityID OBJECT IDENTIFIER, 756 mteTriggerDeltaDiscontinuityIDWildcard TruthValue, 757 mteTriggerDeltaDiscontinuityIDType INTEGER 758 } 760 sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 } 762 mteTriggerDeltaDiscontinuityID OBJECT-TYPE 763 SYNTAX OBJECT IDENTIFIER 764 MAX-ACCESS read-write 765 STATUS current 766 DESCRIPTION 767 "The OBJECT IDENTIFIER (OID) of a TimeTicks or TimeStamp object 768 that indicates a discontinuity in the value at 769 mteTriggerValueID. 771 The OID may be for a leaf object (e.g. sysUpTime.0) or may 772 be wildcarded to match mteTriggerValueID. 774 This object supports normal checking for a discontinuity in a 775 counter. Note that if this object does not point to sysUpTime 776 discontinuity checking must still check sysUpTime for an overall 777 discontinuity. 779 If the object identified is not accessible the sample attempt 780 is in error, with the error code as from an SNMP request. 782 Bad object identifiers or a mismatch between truncating the 783 identifier and the value of mteDeltaDiscontinuityIDWildcard 784 result in operation as one would expect when providing the 785 wrong identifier to a Get operation. The Get will fail or get 786 the wrong object. If the value syntax of those objects is not 787 usable, that results in an error that terminates the sample 788 with a 'badType' error code." 789 DEFVAL { sysUpTimeInstance } 790 ::= { mteTriggerDeltaEntry 1 } 792 mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE 793 SYNTAX TruthValue 794 MAX-ACCESS read-write 795 STATUS current 796 DESCRIPTION 797 "Control for whether mteTriggerDeltaDiscontinuityID is to be 798 treated as fully-specified or wildcarded, with 'true' 799 indicating wildcard." 800 DEFVAL { false } 801 ::= { mteTriggerDeltaEntry 2 } 803 mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE 804 SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) } 805 MAX-ACCESS read-write 806 STATUS current 807 DESCRIPTION 808 "The value 'timeTicks' indicates the 809 mteTriggerDeltaDiscontinuityID of this row is of syntax 810 TimeTicks. The value 'timeStamp' indicates syntax TimeStamp. 812 The value 'dateAndTime' indicates syntax DateAndTime." 813 DEFVAL { timeTicks } 814 ::= { mteTriggerDeltaEntry 3 } 816 -- 817 -- Trigger Existence Table 818 -- 820 mteTriggerExistenceTable OBJECT-TYPE 821 SYNTAX SEQUENCE OF MteTriggerExistenceEntry 822 MAX-ACCESS not-accessible 823 STATUS current 824 DESCRIPTION 825 "A table of management event trigger information for existence 826 triggers." 827 ::= { mteTrigger 4 } 829 mteTriggerExistenceEntry OBJECT-TYPE 830 SYNTAX MteTriggerExistenceEntry 831 MAX-ACCESS not-accessible 832 STATUS current 833 DESCRIPTION 834 "Information about a single existence trigger. Entries 835 automatically exist in this this table for each mteTriggerEntry 836 that has 'existence' set in mteTriggerTest." 837 INDEX { mteOwner, IMPLIED mteTriggerName } 838 ::= { mteTriggerExistenceTable 1 } 840 MteTriggerExistenceEntry ::= SEQUENCE { 841 mteTriggerExistenceTest INTEGER, 842 mteTriggerExistenceStartup TruthValue, 843 mteTriggerExistenceObjectsOwner SnmpAdminString, 844 mteTriggerExistenceObjects SnmpAdminString, 845 mteTriggerExistenceEventOwner SnmpAdminString, 846 mteTriggerExistenceEvent SnmpAdminString 847 } 849 mteTriggerExistenceTest OBJECT-TYPE 850 SYNTAX BITS { present(0), absent(1), changed(2) } 851 MAX-ACCESS read-write 852 STATUS current 853 DESCRIPTION 854 "The type of existence test to perform. The trigger fires 855 when the object at mteTriggerValueID is seen to go from 856 present to absent, from absent to present, or to have it's 857 value changed, depending on which tests are selected. 859 Once the trigger has fired for either presence or absence it 860 will not fire again for that state until the object has been 861 to the other state." 862 DEFVAL { { present, absent } } 863 ::= { mteTriggerExistenceEntry 1 } 865 mteTriggerExistenceStartup OBJECT-TYPE 866 SYNTAX BITS { present(0), absent(1), changed(2) } 867 MAX-ACCESS read-write 868 STATUS current 869 DESCRIPTION 870 "Control for whether an event may be triggered when this entry 871 is first set to 'active' and the test specified by 872 mteTriggerExistenceTest is true. Setting an option causes 873 that trigger to fire when its test is true." 874 DEFVAL { { present, absent } } 875 ::= { mteTriggerExistenceEntry 2 } 877 mteTriggerExistenceObjectsOwner OBJECT-TYPE 878 SYNTAX SnmpAdminString (SIZE (0..32)) 879 MAX-ACCESS read-write 880 STATUS current 881 DESCRIPTION 882 "To go with mteTriggerExistenceObjects, the mteOwner of a 883 group of objects from mteObjectsTable." 884 DEFVAL { ''H } 885 ::= { mteTriggerExistenceEntry 3 } 887 mteTriggerExistenceObjects OBJECT-TYPE 888 SYNTAX SnmpAdminString (SIZE (0..32)) 889 MAX-ACCESS read-write 890 STATUS current 891 DESCRIPTION 892 "The mteObjectsName of a group of objects from 893 mteObjectsTable. These objects are to be added to any 894 Notification resulting from the firing of this trigger for 895 this test. 897 A list of objects may also be added based on the overall 898 trigger, the event or other settings in mteTriggerTest. 900 A length of 0 indicates no additional objects." 902 DEFVAL { ''H } 903 ::= { mteTriggerExistenceEntry 4 } 905 mteTriggerExistenceEventOwner OBJECT-TYPE 906 SYNTAX SnmpAdminString (SIZE (0..32)) 907 MAX-ACCESS read-write 908 STATUS current 909 DESCRIPTION 910 "To go with mteTriggerExistenceEvent, the mteOwner of a group 911 of objects from mteObjectsTable." 912 DEFVAL { ''H } 913 ::= { mteTriggerExistenceEntry 5 } 915 mteTriggerExistenceEvent OBJECT-TYPE 916 SYNTAX SnmpAdminString (SIZE (0..32)) 917 MAX-ACCESS read-write 918 STATUS current 919 DESCRIPTION 920 "The mteEventName of the event to invoke when mteTriggerType is 921 'existence' and this trigger fires. A length of 0 indicates no 922 event." 923 DEFVAL { ''H } 924 ::= { mteTriggerExistenceEntry 6 } 926 -- 927 -- Trigger Boolean Table 928 -- 930 mteTriggerBooleanTable OBJECT-TYPE 931 SYNTAX SEQUENCE OF MteTriggerBooleanEntry 932 MAX-ACCESS not-accessible 933 STATUS current 934 DESCRIPTION 935 "A table of management event trigger information for boolean 936 triggers." 937 ::= { mteTrigger 5 } 939 mteTriggerBooleanEntry OBJECT-TYPE 940 SYNTAX MteTriggerBooleanEntry 941 MAX-ACCESS not-accessible 942 STATUS current 943 DESCRIPTION 944 "Information about a single boolean trigger. Entries 945 automatically exist in this this table for each mteTriggerEntry 946 that has 'boolean' set in mteTriggerTest." 947 INDEX { mteOwner, IMPLIED mteTriggerName } 948 ::= { mteTriggerBooleanTable 1 } 950 MteTriggerBooleanEntry ::= SEQUENCE { 951 mteTriggerBooleanComparison INTEGER, 952 mteTriggerBooleanValue Integer32, 953 mteTriggerBooleanStartup TruthValue, 954 mteTriggerBooleanObjectsOwner SnmpAdminString, 955 mteTriggerBooleanObjects SnmpAdminString, 956 mteTriggerBooleanEventOwner SnmpAdminString, 957 mteTriggerBooleanEvent SnmpAdminString 958 } 960 mteTriggerBooleanComparison OBJECT-TYPE 961 SYNTAX INTEGER { unequal(1), equal(2), 962 less(3), lessOrEqual(4), 963 greater(5), greaterOrEqual(6) } 964 MAX-ACCESS read-write 965 STATUS current 966 DESCRIPTION 967 "The type of boolean comparison to perform. 969 The value at mteTriggerValueID is compared to 970 mteTriggerBooleanValue, so for example if 971 mteTriggerBooleanComparison is 'less' the result would be true 972 if the value at mteTriggerValueID is less than the value of 973 mteTriggerBooleanValue." 974 DEFVAL { unequal } 975 ::= { mteTriggerBooleanEntry 1 } 977 mteTriggerBooleanValue OBJECT-TYPE 978 SYNTAX Integer32 979 MAX-ACCESS read-write 980 STATUS current 981 DESCRIPTION 982 "The value to use for the test specified by 983 mteTriggerBooleanTest." 984 DEFVAL { 0 } 985 ::= { mteTriggerBooleanEntry 2 } 987 mteTriggerBooleanStartup OBJECT-TYPE 988 SYNTAX TruthValue 989 MAX-ACCESS read-write 990 STATUS current 991 DESCRIPTION 992 "Control for whether an event may be triggered when this entry 993 is first set to 'active' or a new instance of the object at 994 mteTriggerValueID is found and the test specified by 995 mteTriggerBooleanComparison is true. In that case an event is 996 triggered if mteTriggerBooleanStartup is 'true'." 997 DEFVAL { true } 998 ::= { mteTriggerBooleanEntry 3 } 1000 mteTriggerBooleanObjectsOwner OBJECT-TYPE 1001 SYNTAX SnmpAdminString (SIZE (0..32)) 1002 MAX-ACCESS read-write 1003 STATUS current 1004 DESCRIPTION 1005 "To go with mteTriggerBooleanObjects, the mteOwner of a group 1006 of objects from mteObjectsTable." 1007 DEFVAL { ''H } 1008 ::= { mteTriggerBooleanEntry 4 } 1010 mteTriggerBooleanObjects 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 ::= { mteTriggerBooleanEntry 5 } 1027 mteTriggerBooleanEventOwner OBJECT-TYPE 1028 SYNTAX SnmpAdminString (SIZE (0..32)) 1029 MAX-ACCESS read-write 1030 STATUS current 1031 DESCRIPTION 1032 "To go with mteTriggerBooleanEvent, the mteOwner of an event 1033 entry from mteEventTable." 1034 DEFVAL { ''H } 1035 ::= { mteTriggerBooleanEntry 6 } 1037 mteTriggerBooleanEvent 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 'boolean' and this trigger fires. A length of 0 indicates no 1044 event." 1045 DEFVAL { ''H } 1046 ::= { mteTriggerBooleanEntry 7 } 1048 -- 1049 -- Trigger Threshold Table 1050 -- 1052 mteTriggerThresholdTable OBJECT-TYPE 1053 SYNTAX SEQUENCE OF MteTriggerThresholdEntry 1054 MAX-ACCESS not-accessible 1055 STATUS current 1056 DESCRIPTION 1057 "A table of management event trigger information for threshold 1058 triggers." 1059 ::= { mteTrigger 6 } 1061 mteTriggerThresholdEntry OBJECT-TYPE 1062 SYNTAX MteTriggerThresholdEntry 1063 MAX-ACCESS not-accessible 1064 STATUS current 1065 DESCRIPTION 1066 "Information about a single threshold trigger. Entries 1067 automatically exist in this table for each mteTriggerEntry 1068 that has 'threshold' set in mteTriggerTest." 1069 INDEX { mteOwner, IMPLIED mteTriggerName } 1070 ::= { mteTriggerThresholdTable 1 } 1072 MteTriggerThresholdEntry ::= SEQUENCE { 1073 mteTriggerThresholdValue Integer32, 1074 mteTriggerThresholdStartup INTEGER, 1075 mteTriggerThresholdRising Integer32, 1076 mteTriggerThresholdFalling Integer32, 1077 mteTriggerThresholdObjectsOwner SnmpAdminString, 1078 mteTriggerThresholdObjects SnmpAdminString, 1079 mteTriggerThresholdRisingEventOwner SnmpAdminString, 1080 mteTriggerThresholdRisingEvent SnmpAdminString, 1081 mteTriggerThresholdFallingEventOwner SnmpAdminString, 1082 mteTriggerThresholdFallingEvent SnmpAdminString 1083 } 1085 mteTriggerThresholdValue OBJECT-TYPE 1086 SYNTAX Integer32 1087 MAX-ACCESS read-write 1088 STATUS current 1089 DESCRIPTION 1090 "The value to use for the threshold test." 1091 DEFVAL { 0 } 1092 ::= { mteTriggerThresholdEntry 1 } 1094 mteTriggerThresholdStartup OBJECT-TYPE 1095 SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } 1096 MAX-ACCESS read-write 1097 STATUS current 1098 DESCRIPTION 1099 "The event that may be triggered when this entry is first 1100 set to 'active' and a new instance of the object at 1101 mteTriggerValueID is found. If the first sample after this 1102 instance becomes active is greater than or equal to 1103 mteTriggerThresholdRising and mteTriggerThresholdStartup is 1104 equal to 'rising' or 'risingOrFalling', then one 1105 mteTriggerThresholdRisingEvent is triggered for that instance. 1106 If the first sample after this entry becomes active is less than 1107 or equal to mteTriggerThresholdFalling and 1108 mteTriggerThresholdStartup is equal to 'falling' or 1109 'risingOrFalling', then one mteTriggerThresholdRisingEvent is 1110 triggered for that instance." 1111 DEFVAL { risingOrFalling } 1112 ::= { mteTriggerThresholdEntry 2 } 1114 mteTriggerThresholdRising OBJECT-TYPE 1115 SYNTAX Integer32 1116 MAX-ACCESS read-write 1117 STATUS current 1118 DESCRIPTION 1119 "A threshold value to check against if mteTriggerType is 1120 'threshold'. 1122 When the current sampled value is greater than or equal to 1123 this threshold, and the value at the last sampling interval 1124 was less than this threshold, one 1125 mteTriggerThresholdRisingEvent is triggered. That event is 1126 also triggered if the first sample afer this entry bcomes 1127 active is greater than or equal to this threshold and 1128 mteTriggerThresholdStartup is equal to 'rising' or 1129 'risingOrFalling'. 1131 After a rising event is generated, another such event is not 1132 triggered until the sampled value falls below this threshold and 1133 reaches mteTriggerThresholdFalling." 1134 DEFVAL { 0 } 1135 ::= { mteTriggerThresholdEntry 3 } 1137 mteTriggerThresholdFalling OBJECT-TYPE 1138 SYNTAX Integer32 1139 MAX-ACCESS read-write 1140 STATUS current 1141 DESCRIPTION 1142 "A threshold value to check against if mteTriggerType is 1143 'threshold'. 1145 When the current sampled value is less than or equal to this 1146 threshold, and the value at the last sampling interval was 1147 greater than this threshold, one 1148 mteTriggerThresholdFallingEvent is triggered. That event is 1149 also triggered if the first sample afer this entry bcomes 1150 active is less than or equal to this threshold and 1151 mteTriggerThresholdStartup is equal to 'falling' or 1152 'risingOrFalling'. 1154 After a falling event is generated, another such event is not 1155 triggered until the sampled value rises above this threshold and 1156 reaches mteTriggerThresholdRising." 1157 DEFVAL { 0 } 1158 ::= { mteTriggerThresholdEntry 4 } 1160 mteTriggerThresholdObjectsOwner OBJECT-TYPE 1161 SYNTAX SnmpAdminString (SIZE (0..32)) 1162 MAX-ACCESS read-write 1163 STATUS current 1164 DESCRIPTION 1165 "To go with mteTriggerThresholdObjects, the mteOwner of a group 1166 of objects from mteObjectsTable." 1167 DEFVAL { ''H } 1168 ::= { mteTriggerThresholdEntry 5 } 1170 mteTriggerThresholdObjects OBJECT-TYPE 1171 SYNTAX SnmpAdminString (SIZE (0..32)) 1172 MAX-ACCESS read-write 1173 STATUS current 1174 DESCRIPTION 1175 "The mteObjectsName of a group of objects from 1176 mteObjectsTable. These objects are to be added to any 1177 Notification resulting from the firing of this trigger for 1178 this test. 1180 A list of objects may also be added based on the overall 1181 trigger, the event or other settings in mteTriggerTest. 1183 A length of 0 indicates no additional objects." 1184 DEFVAL { ''H } 1185 ::= { mteTriggerThresholdEntry 6 } 1187 mteTriggerThresholdRisingEventOwner OBJECT-TYPE 1188 SYNTAX SnmpAdminString (SIZE (0..32)) 1189 MAX-ACCESS read-write 1190 STATUS current 1191 DESCRIPTION 1192 "To go with mteTriggerThresholdRisingEvent, the mteOwner of an 1193 event entry from mteEventTable." 1194 DEFVAL { ''H } 1195 ::= { mteTriggerThresholdEntry 7 } 1197 mteTriggerThresholdRisingEvent OBJECT-TYPE 1198 SYNTAX SnmpAdminString (SIZE (0..32)) 1199 MAX-ACCESS read-write 1200 STATUS current 1201 DESCRIPTION 1202 "The mteEventName of the event to invoke when mteTriggerType is 1203 'threshold' and this trigger fires based on 1204 mteTriggerThresholdRising. A length of 0 indicates no event." 1205 DEFVAL { ''H } 1206 ::= { mteTriggerThresholdEntry 8 } 1208 mteTriggerThresholdFallingEventOwner OBJECT-TYPE 1209 SYNTAX SnmpAdminString (SIZE (0..32)) 1210 MAX-ACCESS read-write 1211 STATUS current 1212 DESCRIPTION 1213 "To go with mteTriggerThresholdFallingEvent, the mteOwner of an 1214 event entry from mteEventTable." 1215 DEFVAL { ''H } 1216 ::= { mteTriggerThresholdEntry 9 } 1218 mteTriggerThresholdFallingEvent OBJECT-TYPE 1219 SYNTAX SnmpAdminString (SIZE (0..32)) 1220 MAX-ACCESS read-write 1221 STATUS current 1222 DESCRIPTION 1223 "The mteEventName of the event to invoke when mteTriggerType is 1224 'threshold' and this trigger fires based on 1225 mteTriggerThresholdFalling. A length of 0 indicates no event." 1226 DEFVAL { ''H } 1227 ::= { mteTriggerThresholdEntry 10 } 1229 -- 1230 -- Objects Table 1231 -- 1233 mteObjectsTable OBJECT-TYPE 1234 SYNTAX SEQUENCE OF MteObjectsEntry 1235 MAX-ACCESS not-accessible 1236 STATUS current 1237 DESCRIPTION 1238 "A table of objects that can be added to notifications based 1239 on the trigger, trigger test, or event, as pointed to by 1240 entries in those tables." 1241 ::= { mteObjects 1 } 1243 mteObjectsEntry OBJECT-TYPE 1244 SYNTAX MteObjectsEntry 1245 MAX-ACCESS not-accessible 1246 STATUS current 1247 DESCRIPTION 1248 "A group of objects. Applications create and delete entries 1249 using mteObjectsEntryStatus." 1250 INDEX { mteOwner, mteObjectsName, mteObjecsIndex } 1251 ::= { mteObjectsTable 1 } 1253 MteObjectsEntry ::= SEQUENCE { 1254 mteObjectsName SnmpAdminString, 1255 mteObjectsIndex Unsigned32, 1256 mteObjectsID OBJECT IDENTIFIER, 1257 mteObjectsIDWildcard TruthValue, 1258 mteObjectsEntryStatus RowStatus 1259 } 1261 mteObjectsName OBJECT-TYPE 1262 SYNTAX SnmpAdminString (SIZE (1..32)) 1263 MAX-ACCESS not-accessible 1264 STATUS current 1265 DESCRIPTION 1266 "A locally-unique, administratively assigned name for a group of 1267 objects." 1268 ::= { mteObjectsEntry 1 } 1270 mteObjectsIndex OBJECT-TYPE 1271 SYNTAX Unsigned32 (1..4294967295) 1272 MAX-ACCESS not-accessible 1273 STATUS current 1274 DESCRIPTION 1275 "An arbitrary small integer for the purpose of identifying 1276 individual objects within a mteObjectsName group. 1278 Objects within a group are placed in the notification in the 1279 numerical order of this index. 1281 Groups are placed in the notification in the order of the 1282 selections for overall trigger, trigger test, and event. 1283 Within trigger test they are in the same order as the 1284 numerical values of the bits defined for mteTriggerTest. 1286 Bad object identifiers or a mismatch between truncating the 1287 identifier and the value of mteDeltaDiscontinuityIDWildcard 1288 result in operation as one would expect when providing the 1289 wrong identifier to a Get operation. The Get will fail or get 1290 the wrong object. If the object is not available it is omitted 1291 from the notification." 1292 ::= { mteObjectsEntry 2 } 1294 mteObjectsID OBJECT-TYPE 1295 SYNTAX OBJECT IDENTIFIER 1296 MAX-ACCESS read-create 1297 STATUS current 1298 DESCRIPTION 1299 "The object identifier of a MIB object to add to a 1300 Notification that results from the firing of a trigger. 1302 This may be wildcarded by truncating all or part of the 1303 instance portion, in which case the instance portion of the 1304 OID for obtaining this object will be the same as that used 1305 in obtaining the mteTriggerValueID that fired. If such 1306 wildcarding is applied, mteObjectsIDWildcard must be 1307 'true' and if not it must be 'false'. 1309 Each instance that fills the wildcard is independent of any 1310 additional instances, that is, wildcarded objects operate 1311 as if there were a separate table entry for each instance 1312 that fills the wildcard without having to actually predict 1313 all possible instances ahead of time." 1314 DEFVAL { zeroDotZero } 1315 ::= { mteObjectsEntry 3 } 1317 mteObjectsIDWildcard OBJECT-TYPE 1318 SYNTAX TruthValue 1319 MAX-ACCESS read-create 1320 STATUS current 1321 DESCRIPTION 1322 "Control for whether mteObjectsID is to be treated as 1323 fully-specified or wildcarded, with 'true' indicating wildcard." 1324 DEFVAL { false } 1325 ::= { mteObjectsEntry 4 } 1327 mteObjectsEntryStatus OBJECT-TYPE 1328 SYNTAX RowStatus 1329 MAX-ACCESS read-create 1330 STATUS current 1331 DESCRIPTION 1332 "The control that allows creation and deletion of entries. 1333 Once made active an entry may not be modified except to 1334 delete it." 1335 ::= { mteObjectsEntry 5 } 1337 -- 1338 -- Event Section 1339 -- 1341 -- Counters 1343 mteEventFailures OBJECT-TYPE 1344 SYNTAX Counter32 1345 MAX-ACCESS read-only 1346 STATUS current 1347 DESCRIPTION 1348 "The number of times an attempt to invoke an event 1349 has failed. This counts individually for each 1350 attempt in a group of targets or each attempt for a 1351 wildcarded trigger object." 1352 ::= { mteEvent 1 } 1354 -- 1355 -- Event Table 1356 -- 1358 mteEventTable OBJECT-TYPE 1359 SYNTAX SEQUENCE OF MteEventEntry 1360 MAX-ACCESS not-accessible 1361 STATUS current 1362 DESCRIPTION 1363 "A table of management event action information." 1364 ::= { mteEvent 2 } 1366 mteEventEntry OBJECT-TYPE 1367 SYNTAX MteEventEntry 1368 MAX-ACCESS not-accessible 1369 STATUS current 1370 DESCRIPTION 1371 "Information about a single event. Applications create and 1372 delete entries using mteEventEntryStatus." 1373 INDEX { mteOwner, IMPLIED mteEventName } 1374 ::= { mteEventTable 1 } 1376 MteEventEntry ::= SEQUENCE { 1377 mteEventName SnmpAdminString, 1378 mteEventComment SnmpAdminString, 1379 mteEventActions BITS, 1380 mteEventEnabled TruthValue, 1381 mteEventEntryStatus RowStatus 1382 } 1384 mteEventName OBJECT-TYPE 1385 SYNTAX SnmpAdminString (SIZE (1..32)) 1386 MAX-ACCESS not-accessible 1387 STATUS current 1388 DESCRIPTION 1389 "A locally-unique, administratively assigned name for the 1390 event." 1391 ::= { mteEventEntry 1 } 1393 mteEventComment OBJECT-TYPE 1394 SYNTAX SnmpAdminString 1395 MAX-ACCESS read-create 1396 STATUS current 1397 DESCRIPTION 1398 "A description of the event's function and use." 1399 DEFVAL { ''H } 1400 ::= { mteEventEntry 2 } 1402 mteEventActions OBJECT-TYPE 1403 SYNTAX BITS { notification(0), set(1) } 1404 MAX-ACCESS read-create 1405 STATUS current 1406 DESCRIPTION 1407 "The actions to perform when this event occurs. 1409 For 'notification', Traps and/or Informs are sent according 1410 to the configuration in the SNMP Notification MIB. 1412 For 'set', an SNMP Set operation is performed according to 1413 control values in this entry." 1414 DEFVAL { { 0 } } 1415 ::= { mteEventEntry 3 } 1417 mteEventEnabled OBJECT-TYPE 1418 SYNTAX TruthValue 1419 MAX-ACCESS read-create 1420 STATUS current 1421 DESCRIPTION 1422 "A control to allow an event to be configured but not used. 1423 When the value is 'false' the event does not execute even if 1424 triggered." 1425 DEFVAL { false } 1426 ::= { mteEventEntry 4 } 1428 mteEventEntryStatus OBJECT-TYPE 1429 SYNTAX RowStatus 1430 MAX-ACCESS read-create 1431 STATUS current 1432 DESCRIPTION 1433 "The control that allows creation and deletion of entries. 1434 Once made active an entry may not be modified except to 1435 delete it." 1436 ::= { mteEventEntry 5 } 1438 -- 1439 -- Event Notification Table 1440 -- 1442 mteEventNotificationTable OBJECT-TYPE 1443 SYNTAX SEQUENCE OF MteEventNotificationEntry 1444 MAX-ACCESS not-accessible 1445 STATUS current 1446 DESCRIPTION 1447 "A table of management event action notification information." 1448 ::= { mteEvent 3 } 1450 mteEventNotificationEntry OBJECT-TYPE 1451 SYNTAX MteEventNotificationEntry 1452 MAX-ACCESS not-accessible 1453 STATUS current 1454 DESCRIPTION 1455 "Information about a single event's notification. Entries 1456 automatically exist in this this table for each mteTriggerEntry 1457 that has 'notification' set in mteEventAction." 1458 INDEX { mteOwner, IMPLIED mteTriggerName } 1459 ::= { mteEventNotificationTable 1 } 1461 MteEventNotificationEntry ::= SEQUENCE { 1462 mteEventNotification OBJECT IDENTIFIER, 1463 mteEventNotificationObjectsOwner SnmpAdminString, 1464 mteEventNotificationObjects SnmpAdminString 1465 } 1467 mteEventNotification OBJECT-TYPE 1468 SYNTAX OBJECT IDENTIFIER 1469 MAX-ACCESS read-write 1470 STATUS current 1471 DESCRIPTION 1472 "The object identifier from the NOTIFICATION-TYPE for the 1473 notification to use if metEventActions has 'notification' set." 1474 DEFVAL { zeroDotZero } 1475 ::= { mteEventNotificationEntry 1 } 1477 mteEventNotificationObjectsOwner OBJECT-TYPE 1478 SYNTAX SnmpAdminString (SIZE (0..32)) 1479 MAX-ACCESS read-write 1480 STATUS current 1481 DESCRIPTION 1482 "To go with mteEventNotificationObjects, the mteOwner of a 1483 group of objects from mteObjectsTable." 1484 DEFVAL { ''H } 1485 ::= { mteEventNotificationEntry 2 } 1487 mteEventNotificationObjects OBJECT-TYPE 1488 SYNTAX SnmpAdminString (SIZE (0..32)) 1489 MAX-ACCESS read-write 1490 STATUS current 1491 DESCRIPTION 1492 "The mteObjectsName of a group of objects from 1493 mteObjectsTable if mteEventActions has 'notification' set. 1494 These objects are to be added to any Notification generated by 1495 this event. 1497 Objects may also be added based on the trigger that stimulated 1498 the event. 1500 A length of 0 indicates no additional objects." 1501 DEFVAL { ''H } 1502 ::= { mteEventNotificationEntry 3 } 1504 -- 1505 -- Event Set Table 1506 -- 1508 mteEventSetTable OBJECT-TYPE 1509 SYNTAX SEQUENCE OF MteEventSetEntry 1510 MAX-ACCESS not-accessible 1511 STATUS current 1512 DESCRIPTION 1513 "A table of management event action information." 1514 ::= { mteEvent 4 } 1516 mteEventSetEntry OBJECT-TYPE 1517 SYNTAX MteEventSetEntry 1518 MAX-ACCESS not-accessible 1519 STATUS current 1520 DESCRIPTION 1521 "Information about a single event's set option. Entries 1522 automatically exist in this this table for each mteTriggerEntry 1523 that has 'set' set in mteEventAction." 1524 INDEX { mteOwner, IMPLIED mteTriggerName } 1525 ::= { mteEventSetTable 1 } 1527 MteEventSetEntry ::= SEQUENCE { 1528 mteEventSetObject OBJECT IDENTIFIER, 1529 mteEventSetObjectWildcard TruthValue, 1530 mteEventSetValue Integer32, 1531 mteEventSetTargetTag SnmpTagValue, 1532 mteEventSetContextName SnmpAdminString, 1533 mteEventSetContextNameWildcard TruthValue 1534 } 1536 mteEventSetObject OBJECT-TYPE 1537 SYNTAX OBJECT IDENTIFIER 1538 MAX-ACCESS read-write 1539 STATUS current 1540 DESCRIPTION 1541 "The object identifier from the MIB object to set if 1542 mteEventActions has 'set' set. 1544 This object identifier may be wildcarded by leaving 1545 sub-identifiers off the end, in which case 1546 nteEventSetObjectWildCard must be 'true'. 1548 If mteEventSetObject is wildcarded the instance used to set the 1549 object to which it points is the same as the instance from the 1550 value of mteTriggerValueID that triggered the event. 1552 Each instance that fills the wildcard is independent of any 1553 additional instances, that is, wildcarded objects operate 1554 as if there were a separate table entry for each instance 1555 that fills the wildcard without having to actually predict 1556 all possible instances ahead of time. 1558 Bad object identifiers or a mismatch between truncating the 1559 identifier and the value of mteSetObjectWildcard 1560 result in operation as one would expect when providing the 1561 wrong identifier to a Set operation. The Set will fail or set 1562 the wrong object. If the value syntax of the destination 1563 object is not correct, the Set fails with the normal SNMP 1564 error code." 1565 DEFVAL { zeroDotZero } 1566 ::= { mteEventSetEntry 1 } 1568 mteEventSetObjectWildcard OBJECT-TYPE 1569 SYNTAX TruthValue 1570 MAX-ACCESS read-write 1571 STATUS current 1572 DESCRIPTION 1573 "Control over whether mteEventSetObject is to be treated as 1574 fully-specified or wildcarded, with 'true' indicating wildcard 1575 if mteEventActions has 'set' set." 1576 DEFVAL { false } 1577 ::= { mteEventSetEntry 2 } 1579 mteEventSetValue OBJECT-TYPE 1580 SYNTAX Integer32 1581 MAX-ACCESS read-write 1582 STATUS current 1583 DESCRIPTION 1584 "The value to which to set the object at mteEventSetObject 1585 if mteEventActions has 'set' set." 1586 DEFVAL { 0 } 1587 ::= { mteEventSetEntry 3 } 1589 mteEventSetTargetTag OBJECT-TYPE 1590 SYNTAX SnmpTagValue 1591 MAX-ACCESS read-write 1592 STATUS current 1593 DESCRIPTION 1594 "The tag for the target(s) at which to set the object at 1595 mteEventSetObject to mteEventSetValue if mteEventActions 1596 has 'set' set. 1598 Systems limited to self management may not accept a non-zero 1599 length for the value of this object. 1601 A length of 0 indicates the local system. In this case, 1602 access to the objects indicated by mteEventSetObject is under 1603 the security credentials of the requester that set 1604 mteTriggerEntryStatus to 'active'. Those credentials are the 1605 input parameters for isAccessAllowed from the Architecture for 1606 Describing SNMP Management Frameworks. 1608 Otherwise access rights are checked according to the security 1609 parameters resulting from the tag." 1610 DEFVAL { ''H } 1611 ::= { mteEventSetEntry 4 } 1613 mteEventSetContextName OBJECT-TYPE 1614 SYNTAX SnmpAdminString 1615 MAX-ACCESS read-write 1616 STATUS current 1617 DESCRIPTION 1618 "The management context in which to set mteEventObjectID. 1619 if mteEventActions has 'set' set. 1621 This may be wildcarded by leaving characters off the end. To 1622 indicate such wildcarding mteEventSetContextNameWildcard must 1623 be 'true'. 1625 If this context name is wildcarded the value used to complete 1626 the wildcarding of mteTriggerContextName will be appended." 1627 DEFVAL { ''H } 1628 ::= { mteEventSetEntry 5 } 1630 mteEventSetContextNameWildcard OBJECT-TYPE 1631 SYNTAX TruthValue 1632 MAX-ACCESS read-write 1633 STATUS current 1634 DESCRIPTION 1635 "Control for whether mteEventSetContextName is to be treated as 1636 fully-specified or wildcarded, with 'true' indicating wildcard 1637 if mteEventActions has 'set' set." 1638 DEFVAL { false } 1639 ::= { mteEventSetEntry 6 } 1641 -- 1642 -- Notifications 1643 -- 1645 dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::= { dismanEventMIB 2 } 1646 dismanEventMIBNotifications OBJECT IDENTIFIER ::= 1647 { dismanEventMIBNotificationPrefix 0 } 1648 dismanEventMIBNotificationObjects OBJECT IDENTIFIER 1649 ::= { dismanEventMIBNotificationPrefix 1 } 1651 -- 1652 -- Notification Objects 1653 -- 1655 mteHotTrigger OBJECT-TYPE 1656 SYNTAX SnmpAdminString 1657 MAX-ACCESS accessible-for-notify 1658 STATUS current 1659 DESCRIPTION 1660 "The name of the trigger causing the notification." 1662 ::= { dismanEventMIBNotificationObjects 1 } 1664 mteHotTargetName OBJECT-TYPE 1665 SYNTAX SnmpAdminString 1666 MAX-ACCESS accessible-for-notify 1667 STATUS current 1668 DESCRIPTION 1669 "The SNMP Target MIB's snmpTargetAddrName related to the 1670 notification." 1671 ::= { dismanEventMIBNotificationObjects 2 } 1673 mteHotContextName OBJECT-TYPE 1674 SYNTAX SnmpAdminString 1675 MAX-ACCESS accessible-for-notify 1676 STATUS current 1677 DESCRIPTION 1678 "The context name related to the notification. This must be as 1679 fully-qualified as possible, including filling in wildcard 1680 information determined in processing." 1681 ::= { dismanEventMIBNotificationObjects 3 } 1683 mteHotOID OBJECT-TYPE 1684 SYNTAX OBJECT IDENTIFIER 1685 MAX-ACCESS accessible-for-notify 1686 STATUS current 1687 DESCRIPTION 1688 "The object identifier of the destination object related to the 1689 notification. This must be as fully-qualified as possible, 1690 inluding filling in wildcard informaation determined in 1691 processing. 1693 For a trigger-related notification this is from 1694 mteTriggerValueID. 1696 For a set failure this is from mteEventSetObject." 1697 ::= { dismanEventMIBNotificationObjects 4 } 1699 mteHotValue OBJECT-TYPE 1700 SYNTAX Integer32 1701 MAX-ACCESS accessible-for-notify 1702 STATUS current 1703 DESCRIPTION 1704 "The value of the object at mteTriggerValueID when a 1705 trigger fired." 1706 ::= { dismanEventMIBNotificationObjects 5 } 1708 mteFailedReason OBJECT-TYPE 1709 SYNTAX FailureReason 1710 MAX-ACCESS accessible-for-notify 1711 STATUS current 1712 DESCRIPTION 1713 "The reason for the failure of an attempt to check for a 1714 trigger condition or set an object in response to an event." 1715 ::= { dismanEventMIBNotificationObjects 6 } 1717 -- 1718 -- Notifications 1719 -- 1721 mteTriggerFired NOTIFICATION-TYPE 1722 OBJECTS { mteHotTrigger, 1723 mteHotTargetName, 1724 mteHotContextName, 1725 mteHotOID, 1726 mteHotValue } 1727 STATUS current 1728 DESCRIPTION 1729 "Notification that the trigger indicated by the object 1730 instances has fired, for triggers with mteTriggerType 1731 'boolean'." 1732 ::= { dismanEventMIBNotifications 1 } 1734 mteTriggerRising NOTIFICATION-TYPE 1735 OBJECTS { mteHotTrigger, 1736 mteHotTargetName, 1737 mteHotContextName, 1738 mteHotOID, 1739 mteHotValue } 1740 STATUS current 1741 DESCRIPTION 1742 "Notification that the rising threshold was met for triggers 1743 with mteTriggerType 'threshold'." 1744 ::= { dismanEventMIBNotifications 2 } 1746 mteTriggerFalling NOTIFICATION-TYPE 1747 OBJECTS { mteHotTrigger, 1748 mteHotTargetName, 1749 mteHotContextName, 1750 mteHotOID, 1751 mteHotValue } 1752 STATUS current 1753 DESCRIPTION 1754 "Notification that the falling threshold was met for triggers 1755 with mteTriggerType 'threshold'." 1756 ::= { dismanEventMIBNotifications 3 } 1758 mteTriggerFailure NOTIFICATION-TYPE 1759 OBJECTS { mteHotTrigger, 1760 mteHotTargetName, 1761 mteHotContextName, 1762 mteHotOID, 1763 mteFailedReason } 1764 STATUS current 1765 DESCRIPTION 1766 "Notification that an attempt to check a trigger has failed. 1768 The network manager must enable this notification only with 1769 a certain fear and trembling, as it can easily crowd out more 1770 important information. It should be used only to help diagnose 1771 a problem that has appeared in the error counters and can not 1772 be found otherwise." 1773 ::= { dismanEventMIBNotifications 4 } 1775 mteEventSetFailure NOTIFICATION-TYPE 1776 OBJECTS { mteHotTrigger, 1777 mteHotTargetName, 1778 mteHotContextName, 1779 mteHotOID, 1780 mteFailedReason } 1781 STATUS current 1782 DESCRIPTION 1783 "Notification that an attempt to do a set in response to an 1784 event has failed. 1786 The network manager must enable this notification only with 1787 a certain fear and trembling, as it can easily crowd out more 1788 important information. It should be used only to help diagnose 1789 a problem that has appeared in the error counters and can not 1790 be found otherwise." 1791 ::= { dismanEventMIBNotifications 5 } 1793 -- 1794 -- Conformance 1795 -- 1796 dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 } 1797 dismanEventMIBCompliances OBJECT IDENTIFIER ::= { dismanEventMIBConformance 1 } 1798 dismanEventMIBGroups OBJECT IDENTIFIER ::= { dismanEventMIBConformance 2 } 1800 -- Compliance 1802 dismanEventMIBCompliance MODULE-COMPLIANCE 1803 STATUS current 1804 DESCRIPTION 1805 "The compliance statement for entities which implement 1806 the Event MIB." 1807 MODULE -- this module 1808 MANDATORY-GROUPS { 1809 dismanEventResourceGroup, 1810 dismanEventTriggerGroup, 1811 dismanEventObjectsGroup, 1812 dismanEventEventGroup, 1813 dismanEventNotificationObjectGroup, 1814 dismanEventNotificationGroup 1815 } 1817 OBJECT mteTriggerTargetTag 1818 MIN-ACCESS read-only 1819 DESCRIPTION 1820 "Write access is not required, thus limiting 1821 monitoring to the local system or preconfigured 1822 remote systems." 1824 OBJECT mteEventSetTargetTag 1825 MIN-ACCESS read-only 1826 DESCRIPTION 1827 "Write access is not required, thus limiting 1828 setting to the local system or preconfigured 1829 remote systems." 1831 OBJECT mteTriggerValueIDWildcard 1832 MIN-ACCESS read-only 1833 DESCRIPTION 1834 "Write access is not required, thus allowing 1835 the system not to implement wildcarding." 1837 OBJECT mteTriggerContextNameWildcard 1838 MIN-ACCESS read-only 1839 DESCRIPTION 1840 "Write access is not required, thus allowing 1841 the system not to implement wildcarding." 1843 OBJECT mteObjectsIDWildcard 1844 MIN-ACCESS read-only 1845 DESCRIPTION 1846 "Write access is not required, thus allowing 1847 the system not to implement wildcarding." 1849 OBJECT mteEventSetContextNameWildcard 1850 MIN-ACCESS read-only 1851 DESCRIPTION 1852 "Write access is not required, thus allowing 1853 the system not to implement wildcarding." 1855 ::= { dismanEventMIBCompliances 1 } 1857 -- Units of Conformance 1859 dismanEventResourceGroup OBJECT-GROUP 1860 OBJECTS { 1861 mteResourceSampleMinimum, 1862 mteResourceSampleInstanceMaximum, 1863 mteResourceSampleInstances, 1864 mteResourceSampleInstancesHigh, 1865 mteResourceSampleInstanceLacks 1866 } 1867 STATUS current 1868 DESCRIPTION 1869 "Event resource status and control objects." 1870 ::= { dismanEventMIBGroups 1 } 1872 dismanEventTriggerGroup OBJECT-GROUP 1873 OBJECTS { 1874 mteTriggerFailures, 1876 mteTriggerComment, 1877 mteTriggerTest, 1878 mteTriggerSampleType, 1879 mteTriggerValueID, 1880 mteTriggerValueIDWildcard, 1881 mteTriggerTargetTag, 1882 mteTriggerContextName, 1883 mteTriggerContextNameWildcard, 1884 mteTriggerFrequency, 1885 mteTriggerObjectsOwner, 1886 mteTriggerObjects, 1887 mteTriggerEnabled, 1888 mteTriggerEntryStatus, 1890 mteTriggerDeltaDiscontinuityID, 1891 mteTriggerDeltaDiscontinuityIDWildcard, 1892 mteTriggerDeltaDiscontinuityIDType, 1894 mteTriggerExistenceTest, 1895 mteTriggerExistenceStartup, 1896 mteTriggerExistenceObjectsOwner, 1897 mteTriggerExistenceObjects, 1898 mteTriggerExistenceEventOwner, 1899 mteTriggerExistenceEvent, 1901 mteTriggerBooleanComparison, 1902 mteTriggerBooleanValue, 1903 mteTriggerBooleanStartup, 1904 mteTriggerBooleanObjectsOwner, 1905 mteTriggerBooleanObjects, 1906 mteTriggerBooleanEventOwner, 1907 mteTriggerBooleanEvent, 1909 mteTriggerThresholdValue, 1910 mteTriggerThresholdStartup, 1911 mteTriggerThresholdObjectsOwner, 1912 mteTriggerThresholdObjects, 1913 mteTriggerThresholdRising, 1914 mteTriggerThresholdFalling, 1915 mteTriggerThresholdRisingEventOwner, 1916 mteTriggerThresholdRisingEvent, 1917 mteTriggerThresholdFallingEventOwner, 1918 mteTriggerThresholdFallingEvent 1919 } 1920 STATUS current 1921 DESCRIPTION 1922 "Event triggers." 1923 ::= { dismanEventMIBGroups 2 } 1925 dismanEventObjectsGroup OBJECT-GROUP 1926 OBJECTS { 1927 mteObjectsID, 1928 mteObjectsIDWildcard, 1929 mteObjectsEntryStatus 1930 } 1931 STATUS current 1932 DESCRIPTION 1933 "Supplemental objects." 1934 ::= { dismanEventMIBGroups 3 } 1936 dismanEventEventGroup OBJECT-GROUP 1937 OBJECTS { 1938 mteEventFailures, 1940 mteEventComment, 1941 mteEventActions, 1942 mteEventEnabled, 1943 mteEventEntryStatus, 1945 mteEventNotification, 1946 mteEventNotificationObjectsOwner, 1947 mteEventNotificationObjects, 1949 mteEventSetObject, 1950 mteEventSetObjectWildcard, 1951 mteEventSetValue, 1952 mteEventSetTargetTag, 1953 mteEventSetContextName, 1954 mteEventSetContextNameWildcard 1955 } 1956 STATUS current 1957 DESCRIPTION 1958 "Events." 1959 ::= { dismanEventMIBGroups 4 } 1961 dismanEventNotificationObjectGroup OBJECT-GROUP 1962 OBJECTS { 1963 mteHotTrigger, 1964 mteHotTargetName, 1965 mteHotContextName, 1966 mteHotOID, 1967 mteHotValue, 1968 mteFailedReason 1969 } 1970 STATUS current 1971 DESCRIPTION 1972 "Notification objects." 1974 ::= { dismanEventMIBGroups 5 } 1976 dismanEventNotificationGroup NOTIFICATION-GROUP 1977 OBJECTS { 1978 mteTriggerFired, 1979 mteTriggerRising, 1980 mteTriggerFalling, 1981 mteTriggerFailure, 1982 mteEventSetFailure 1983 } 1984 STATUS current 1985 DESCRIPTION 1986 "Notifications." 1987 ::= { dismanEventMIBGroups 6 } 1989 END 1990 9. Intellectual Property 1992 The IETF takes no position regarding the validity or scope of any 1993 intellectual property or other rights that might be claimed to pertain 1994 to the implementation or use of the technology described in this 1995 document or the extent to which any license under such rights might or 1996 might not be available; neither does it represent that it has made any 1997 effort to identify any such rights. Information on the IETF's 1998 procedures with respect to rights in standards-track and standards- 1999 related documentation can be found in BCP-11. Copies of claims of 2000 rights made available for publication and any assurances of licenses to 2001 be made available, or the result of an attempt made to obtain a general 2002 license or permission for the use of such proprietary rights by 2003 implementors or users of this specification can be obtained from the 2004 IETF Secretariat. 2006 10. Acknowledgements 2008 This MIB contains considerable contributions from the RMON MIB, the 2009 Distributed Management Design Team (Andy Bierman, Maria Greene, Bob 2010 Stewart, and Steve Waldbusser), the Distributed Management Working 2011 Group, and colleagues at Cisco. 2013 11. References 2015 [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for 2016 Describing SNMP Management Frameworks", RFC 2271, Cabletron 2017 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 2018 January 1998. 2020 [2] Rose, M. and K. McCloghrie, "Structure and Identification of 2021 Management Information for TCP/IP-based Internets", RFC 1155, 2022 Performance Systems International, Hughes LAN Systems, May 1990. 2024 [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 2025 Performance Systems International, Hughes LAN Systems, March 1991. 2027 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 2028 RFC 1215, Performance Systems International, March 1991. 2030 [5] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of 2031 Management Information for Version 2 of the Simple Network 2032 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 2033 Systems, Inc., Dover Beach Consulting, Inc., International Network 2034 Services, January 1996. 2036 [6] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual 2037 Conventions for Version 2 of the Simple Network Management Protocol 2038 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 2039 Dover Beach Consulting, Inc., International Network Services, 2040 January 1996. 2042 [7] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Conformance 2043 Statements for Version 2 of the Simple Network Management Protocol 2044 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 2045 Dover Beach Consulting, Inc., International Network Services, 2046 January 1996. 2048 [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network 2049 Management Protocol", RFC 1157, SNMP Research, Performance Systems 2050 International, Performance Systems International, MIT Laboratory 2051 for Computer Science, May 1990. 2053 [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction 2054 to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco 2055 Systems, Inc., Dover Beach Consulting, Inc., International Network 2056 Services, January 1996. 2058 [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport 2059 Mappings for Version 2 of the Simple Network Management Protocol 2060 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 2061 Dover Beach Consulting, Inc., International Network Services, 2062 January 1996. 2064 [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 2065 Processing and Dispatching for the Simple Network Management 2066 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 2067 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 2069 [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for 2070 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2071 2274, IBM T. J. Watson Research, January 1998. 2073 [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol 2074 Operations for Version 2 of the Simple Network Management Protocol 2075 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 2076 Dover Beach Consulting, Inc., International Network Services, 2077 January 1996. 2079 [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2080 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 2081 Systems, January 1998. 2083 [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 2084 Control Model (VACM) for the Simple Network Management Protocol 2085 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 2086 Cisco Systems, Inc., January 1998. 2088 [16] Waldbusser, S., "Remote Network Monitoring Management Information 2089 Base", RFC 1757, International Network Services, February 1995. 2091 [17] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to- 2092 Manager Management Information Base", RFC 1451, SNMP Research, 2093 Inc., Cisco SYSTEMS< Inc., Dover Beach Consulting, Inc., 2094 International Network Services, April 1993. 2096 [18] Stewart, B., "Expression MIB", RFC ????, Cisco Systems, Inc., 2097 ?Month? 1998. 2099 [19] Stewart, B., "Notification Log MIB", RFC ????, Cisco Systems, Inc., 2100 ?Month? 1998. 2102 12. Security Considerations 2104 Security issues are discussed in the Overview section and in the 2105 DESCRIPTION clauses of relevant objects. 2107 13. Author's Address 2109 Bob Stewart 2110 Cisco Systems, Inc. 2111 170 West Tasman Drive 2112 San Jose, CA 95134-1706 2113 U.S.A. 2115 Phone: +1 408 526 4527 2116 Email: bstewart@cisco.com 2118 14. Full Copyright Statement 2120 Copyright (C) The Internet Society (1999). All Rights Reserved. 2122 This document and translations of it may be copied and furnished to 2123 others, and derivative works that comment on or otherwise explain it or 2124 assist in its implementation may be prepared, copied, published and 2125 distributed, in whole or in part, without restriction of any kind, 2126 provided that the above copyright notice and this paragraph are included 2127 on all such copies and derivative works. However, this document itself 2128 may not be modified in any way, such as by removing the copyright notice 2129 or references to the Internet Society or other Internet organizations, 2130 except as needed for the purpose of developing Internet standards in 2131 which case the procedures for copyrights defined in the Internet 2132 Standards process must be followed, or as required to translate it into 2133 languages other than English. 2135 The limited permissions granted above are perpetual and will not be 2136 revoked by the Internet Society or its successors or assigns. 2138 This document and the information contained herein is provided on an "AS 2139 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2140 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2141 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 2142 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 2143 FITNESS FOR A PARTICULAR PURPOSE. 2145 Table of Contents 2147 1 Abstract ........................................................ 2 2148 2 The SNMP Management Framework ................................... 2 2149 3 Overview ........................................................ 4 2150 4 Relationship to Other MIBs ...................................... 4 2151 5 MIB Sections .................................................... 4 2152 6 Operation ....................................................... 5 2153 7 Security ........................................................ 6 2154 8 Definitions ..................................................... 7 2155 9 Intellectual Property ........................................... 47 2156 10 Acknowledgements ............................................... 48 2157 11 References ..................................................... 49 2158 12 Security Considerations ........................................ 51 2159 13 Author's Address ............................................... 51 2160 14 Full Copyright Statement ....................................... 52