SCALAR OBJECTS

Name	Type	Access	OID	Description
1 mteResourceSampleMinimum	INTEGER32 Legal values: 1 .. 2147483647	ReadWrite	.1.3.6.1.2.1.88.1.1.1	The minimum mteTriggerFrequency this system will accept. A system may use the larger values of this minimum to lessen the impact of constant sampling. For larger sampling intervals the system samples less often and suffers less overhead. This object provides a way to enforce such lower overhead for all triggers created after it is set. Unless explicitly resource limited, a system's value for this object SHOULD be 1, allowing as small as a 1 second interval for ongoing trigger sampling. Changing this value will not invalidate an existing setting of mteTriggerFrequency.
2 mteResourceSampleInstanceMaximum	UNSIGNED32	ReadWrite	.1.3.6.1.2.1.88.1.1.2	The maximum number of instance entries this system will support for sampling. These are the entries that maintain state, one for each instance of each sampled object as selected by mteTriggerValueID. Note that wildcarded objects result in multiple instances of this state. A value of 0 indicates no preset limit, that is, the limit is dynamic based on system operation and resources. Unless explicitly resource limited, a system's value for this object SHOULD be 0. Changing this value will not eliminate or inhibit existing sample state but could prevent allocation of additional state information.
3 mteResourceSampleInstances	GAUGE	ReadOnly	.1.3.6.1.2.1.88.1.1.3	The number of currently active instance entries as defined for mteResourceSampleInstanceMaximum.
4 mteResourceSampleInstancesHigh	GAUGE	ReadOnly	.1.3.6.1.2.1.88.1.1.4	The highest value of mteResourceSampleInstances that has occurred since initialization of the management system.
5 mteResourceSampleInstanceLacks	COUNTER	ReadOnly	.1.3.6.1.2.1.88.1.1.5	The number of times this system could not take a new sample because that allocation would have exceeded the limit set by mteResourceSampleInstanceMaximum.
1 mteTriggerFailures	COUNTER	ReadOnly	.1.3.6.1.2.1.88.1.2.1	The number of times an attempt to check for a trigger condition has failed. This counts individually for each attempt in a group of targets or each attempt for a wildcarded object.
1 mteEventFailures	COUNTER	ReadOnly	.1.3.6.1.2.1.88.1.4.1	The number of times an attempt to invoke an event has failed. This counts individually for each attempt in a group of targets or each attempt for a wildcarded trigger object.

TABLE OBJECTS

Table mteTriggerTable

Table Name	mteTriggerTable
In MIB	DISMAN-EVENT-MIB
Registered at OID	.1.3.6.1.2.1.88.1.2.2
Table Description	A table of management event trigger information.
Row Description	Information about a single trigger. Applications create and delete entries using mteTriggerEntryStatus.

mteTriggerTable Indexes:

Name	Type	Access	Description
1 mteOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
2 mteTriggerName	OCTETSTR Legal Lengths: 1 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A locally-unique, administratively assigned name for the trigger within the scope of mteOwner.

Other mteTriggerTable Columns:

Name	Type	Access	Description
3 mteTriggerComment	OCTETSTR Legal Lengths: 0 .. 255 SnmpAdminString	Create	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A description of the trigger's function and use.
4 mteTriggerTest	BITS Value Label/Meaning 0 existence 1 boolean 2 threshold	Create	The type of trigger test to perform. For 'boolean' and 'threshold' tests, the object at mteTriggerValueID MUST evaluate to an integer, that is, anything that ends up encoded for transmission (that is, in BER, not ASN.1) as an integer. For 'existence', the specific test is as selected by mteTriggerExistenceTest. When an object appears, vanishes or changes value, the trigger fires. If the object's appearance caused the trigger firing, the object MUST vanish before the trigger can be fired again for it, and vice versa. If the trigger fired due to a change in the object's value, it will be fired again on every successive value change for that object. For 'boolean', the specific test is as selected by mteTriggerBooleanTest. If the test result is true the trigger fires. The trigger will not fire again until the value has become false and come back to true. For 'threshold' the test works as described below for mteTriggerThresholdStartup, mteTriggerThresholdRising, and mteTriggerThresholdFalling. Note that combining 'boolean' and 'threshold' tests on the same object may be somewhat redundant.
5 mteTriggerSampleType	INTEGER Value Label/Meaning 1 absoluteValue 2 deltaValue	Create	The type of sampling to perform. An 'absoluteValue' sample requires only a single sample to be meaningful, and is exactly the value of the object at mteTriggerValueID at the sample time. A 'deltaValue' requires two samples to be meaningful and is thus not available for testing until the second and subsequent samples after the object at mteTriggerValueID is first found to exist. It is the difference between the two samples. For unsigned values it is always positive, based on unsigned arithmetic. For signed values it can be positive or negative. For SNMP counters to be meaningful they should be sampled as a 'deltaValue'. For 'deltaValue' mteTriggerDeltaTable contains further parameters. If only 'existence' is set in mteTriggerTest this object has no meaning.
6 mteTriggerValueID	OBJECTID	Create	The object identifier of the MIB object to sample to see if the trigger should fire. This may be wildcarded by truncating all or part of the instance portion, in which case the value is obtained as if with a GetNext function, checking multiple values if they exist. If such wildcarding is applied, mteTriggerValueIDWildcard must be 'true' and if not it must be 'false'. Bad object identifiers or a mismatch between truncating the identifier and the value of mteTriggerValueIDWildcard result in operation as one would expect when providing the wrong identifier to a Get or GetNext operation. The Get will fail or get the wrong object. The GetNext will indeed get whatever is next, proceeding until it runs past the initial part of the identifier and perhaps many unintended objects for confusing results. If the value syntax of those objects is not usable, that results in a 'badType' error that terminates the scan. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time.
7 mteTriggerValueIDWildcard	INTEGER TruthValue (ENUM list below)	Create	Note: this object is based on the TruthValue TEXTUAL-CONVENTION. Control for whether mteTriggerValueID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard.
8 mteTriggerTargetTag	OCTETSTR Legal Lengths: 0 .. 255 SnmpTagValue	Create	Note: this object is based on the SnmpTagValue TEXTUAL-CONVENTION. The tag for the target(s) from which to obtain the condition for a trigger check. A length of 0 indicates the local system. In this case, access to the objects indicated by mteTriggerValueID is under the security credentials of the requester that set mteTriggerEntryStatus to 'active'. Those credentials are the input parameters for isAccessAllowed from the Architecture for Describing SNMP Management Frameworks. Otherwise access rights are checked according to the security parameters resulting from the tag.
9 mteTriggerContextName	OCTETSTR Legal Lengths: 0 .. 255 SnmpAdminString	Create	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The management context from which to obtain mteTriggerValueID. This may be wildcarded by leaving characters off the end. For example use 'Repeater' to wildcard to 'Repeater1', 'Repeater2', 'Repeater-999.87b', and so on. To indicate such wildcarding is intended, mteTriggerContextNameWildcard must be 'true'. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time. Operation of this feature assumes that the local system has a list of available contexts against which to apply the wildcard. If the objects are being read from the local system, this is clearly the system's own list of contexts. For a remote system a local version of such a list is not defined by any current standard and may not be available, so this function MAY not be supported.
10 mteTriggerContextNameWildcard	INTEGER TruthValue (ENUM list below)	Create	Note: this object is based on the TruthValue TEXTUAL-CONVENTION. Control for whether mteTriggerContextName is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard.
11 mteTriggerFrequency	UNSIGNED32	Create	The number of seconds to wait between trigger samples. To encourage consistency in sampling, the interval is measured from the beginning of one check to the beginning of the next and the timer is restarted immediately when it expires, not when the check completes. If the next sample begins before the previous one completed the system may either attempt to make the check or treat this as an error condition with the error 'sampleOverrun'. A frequency of 0 indicates instantaneous recognition of the condition. This is not possible in many cases, but may be supported in cases where it makes sense and the system is able to do so. This feature allows the MIB to be used in implementations where such interrupt-driven behavior is possible and is not likely to be supported for all MIB objects even then since such sampling generally has to be tightly integrated into low-level code. Systems that can support this SHOULD document those cases where it can be used. In cases where it can not, setting this object to 0 should be disallowed.
12 mteTriggerObjectsOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	Create	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteTriggerObjects, the mteOwner of a group of objects from mteObjectsTable.
13 mteTriggerObjects	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	Create	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger. A list of objects may also be added based on the event or on the value of mteTriggerTest. A length of 0 indicates no additional objects.
14 mteTriggerEnabled	INTEGER TruthValue (ENUM list below)	Create	Note: this object is based on the TruthValue TEXTUAL-CONVENTION. A control to allow a trigger to be configured but not used. When the value is 'false' the trigger is not sampled.
15 mteTriggerEntryStatus	INTEGER RowStatus (ENUM list below)	Create	Note: this object is based on the RowStatus TEXTUAL-CONVENTION. The control that allows creation and deletion of entries. Once made active an entry may not be modified except to delete it.

Table mteTriggerDeltaTable

Table Name	mteTriggerDeltaTable
In MIB	DISMAN-EVENT-MIB
Registered at OID	.1.3.6.1.2.1.88.1.2.3
Table Description	A table of management event trigger information for delta sampling.
Row Description	Information about a single trigger's delta sampling. Entries automatically exist in this this table for each mteTriggerEntry that has mteTriggerSampleType set to 'deltaValue'.

mteTriggerDeltaTable Indexes:

Name	Type	Access	Description
1 mteOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
2 mteTriggerName	OCTETSTR Legal Lengths: 1 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A locally-unique, administratively assigned name for the trigger within the scope of mteOwner.

Other mteTriggerDeltaTable Columns:

Name	Type	Access	Description
1 mteTriggerDeltaDiscontinuityID	OBJECTID	ReadWrite	The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or DateAndTime object that indicates a discontinuity in the value at mteTriggerValueID. The OID may be for a leaf object (e.g. sysUpTime.0) or may be wildcarded to match mteTriggerValueID. This object supports normal checking for a discontinuity in a counter. Note that if this object does not point to sysUpTime discontinuity checking MUST still check sysUpTime for an overall discontinuity. If the object identified is not accessible the sample attempt is in error, with the error code as from an SNMP request. Bad object identifiers or a mismatch between truncating the identifier and the value of mteDeltaDiscontinuityIDWildcard result in operation as one would expect when providing the wrong identifier to a Get operation. The Get will fail or get the wrong object. If the value syntax of those objects is not usable, that results in an error that terminates the sample with a 'badType' error code.
2 mteTriggerDeltaDiscontinuityIDWildcard	INTEGER TruthValue (ENUM list below)	ReadWrite	Note: this object is based on the TruthValue TEXTUAL-CONVENTION. Control for whether mteTriggerDeltaDiscontinuityID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard. Note that the value of this object will be the same as that of the corresponding instance of mteTriggerValueIDWildcard when the corresponding mteTriggerSampleType is 'deltaValue'.
3 mteTriggerDeltaDiscontinuityIDType	INTEGER Value Label/Meaning 1 timeTicks 2 timeStamp 3 dateAndTime	ReadWrite	The value 'timeTicks' indicates the mteTriggerDeltaDiscontinuityID of this row is of syntax TimeTicks. The value 'timeStamp' indicates syntax TimeStamp. The value 'dateAndTime' indicates syntax DateAndTime.

Table mteTriggerExistenceTable

Table Name	mteTriggerExistenceTable
In MIB	DISMAN-EVENT-MIB
Registered at OID	.1.3.6.1.2.1.88.1.2.4
Table Description	A table of management event trigger information for existence triggers.
Row Description	Information about a single existence trigger. Entries automatically exist in this this table for each mteTriggerEntry that has 'existence' set in mteTriggerTest.

mteTriggerExistenceTable Indexes:

Name	Type	Access	Description
1 mteOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
2 mteTriggerName	OCTETSTR Legal Lengths: 1 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A locally-unique, administratively assigned name for the trigger within the scope of mteOwner.

Other mteTriggerExistenceTable Columns:

Name	Type	Access	Description
1 mteTriggerExistenceTest	BITS Value Label/Meaning 0 present 1 absent 2 changed	ReadWrite	The type of existence test to perform. The trigger fires when the object at mteTriggerValueID is seen to go from present to absent, from absent to present, or to have it's value changed, depending on which tests are selected: present(0) - when this test is selected, the trigger fires when the mteTriggerValueID object goes from absent to present. absent(1) - when this test is selected, the trigger fires when the mteTriggerValueID object goes from present to absent. changed(2) - when this test is selected, the trigger fires the mteTriggerValueID object value changes. Once the trigger has fired for either presence or absence it will not fire again for that state until the object has been to the other state.
2 mteTriggerExistenceStartup	BITS Value Label/Meaning 0 present 1 absent	ReadWrite	Control for whether an event may be triggered when this entry is first set to 'active' and the test specified by mteTriggerExistenceTest is true. Setting an option causes that trigger to fire when its test is true.
3 mteTriggerExistenceObjectsOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteTriggerExistenceObjects, the mteOwner of a group of objects from mteObjectsTable.
4 mteTriggerExistenceObjects	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger for this test. A list of objects may also be added based on the overall trigger, the event or other settings in mteTriggerTest. A length of 0 indicates no additional objects.
5 mteTriggerExistenceEventOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteTriggerExistenceEvent, the mteOwner of an event entry from the mteEventTable.
6 mteTriggerExistenceEvent	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteEventName of the event to invoke when mteTriggerType is 'existence' and this trigger fires. A length of 0 indicates no event.

Table mteTriggerBooleanTable

Table Name	mteTriggerBooleanTable
In MIB	DISMAN-EVENT-MIB
Registered at OID	.1.3.6.1.2.1.88.1.2.5
Table Description	A table of management event trigger information for boolean triggers.
Row Description	Information about a single boolean trigger. Entries automatically exist in this this table for each mteTriggerEntry that has 'boolean' set in mteTriggerTest.

mteTriggerBooleanTable Indexes:

Name	Type	Access	Description
1 mteOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
2 mteTriggerName	OCTETSTR Legal Lengths: 1 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A locally-unique, administratively assigned name for the trigger within the scope of mteOwner.

Other mteTriggerBooleanTable Columns:

Name	Type	Access	Description
1 mteTriggerBooleanComparison	INTEGER Value Label/Meaning 1 unequal 2 equal 3 less 4 lessOrEqual 5 greater 6 greaterOrEqual	ReadWrite	The type of boolean comparison to perform. The value at mteTriggerValueID is compared to mteTriggerBooleanValue, so for example if mteTriggerBooleanComparison is 'less' the result would be true if the value at mteTriggerValueID is less than the value of mteTriggerBooleanValue.
2 mteTriggerBooleanValue	INTEGER32	ReadWrite	The value to use for the test specified by mteTriggerBooleanTest.
3 mteTriggerBooleanStartup	INTEGER TruthValue (ENUM list below)	ReadWrite	Note: this object is based on the TruthValue TEXTUAL-CONVENTION. Control for whether an event may be triggered when this entry is first set to 'active' or a new instance of the object at mteTriggerValueID is found and the test specified by mteTriggerBooleanComparison is true. In that case an event is triggered if mteTriggerBooleanStartup is 'true'.
4 mteTriggerBooleanObjectsOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteTriggerBooleanObjects, the mteOwner of a group of objects from mteObjectsTable.
5 mteTriggerBooleanObjects	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger for this test. A list of objects may also be added based on the overall trigger, the event or other settings in mteTriggerTest. A length of 0 indicates no additional objects.
6 mteTriggerBooleanEventOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteTriggerBooleanEvent, the mteOwner of an event entry from mteEventTable.
7 mteTriggerBooleanEvent	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteEventName of the event to invoke when mteTriggerType is 'boolean' and this trigger fires. A length of 0 indicates no event.

Table mteTriggerThresholdTable

Table Name	mteTriggerThresholdTable
In MIB	DISMAN-EVENT-MIB
Registered at OID	.1.3.6.1.2.1.88.1.2.6
Table Description	A table of management event trigger information for threshold triggers.
Row Description	Information about a single threshold trigger. Entries automatically exist in this table for each mteTriggerEntry that has 'threshold' set in mteTriggerTest.

mteTriggerThresholdTable Indexes:

Name	Type	Access	Description
1 mteOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
2 mteTriggerName	OCTETSTR Legal Lengths: 1 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A locally-unique, administratively assigned name for the trigger within the scope of mteOwner.

Other mteTriggerThresholdTable Columns:

Name	Type	Access	Description
1 mteTriggerThresholdStartup	INTEGER Value Label/Meaning 1 rising 2 falling 3 risingOrFalling	ReadWrite	The event that may be triggered when this entry is first set to 'active' and a new instance of the object at mteTriggerValueID is found. If the first sample after this instance becomes active is greater than or equal to mteTriggerThresholdRising and mteTriggerThresholdStartup is equal to 'rising' or 'risingOrFalling', then one mteTriggerThresholdRisingEvent is triggered for that instance. If the first sample after this entry becomes active is less than or equal to mteTriggerThresholdFalling and mteTriggerThresholdStartup is equal to 'falling' or 'risingOrFalling', then one mteTriggerThresholdRisingEvent is triggered for that instance.
2 mteTriggerThresholdRising	INTEGER32	ReadWrite	A threshold value to check against if mteTriggerType is 'threshold'. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, one mteTriggerThresholdRisingEvent is triggered. That event is also triggered if the first sample after this entry becomes active is greater than or equal to this threshold and mteTriggerThresholdStartup is equal to 'rising' or 'risingOrFalling'. After a rising event is generated, another such event is not triggered until the sampled value falls below this threshold and reaches mteTriggerThresholdFalling.
3 mteTriggerThresholdFalling	INTEGER32	ReadWrite	A threshold value to check against if mteTriggerType is 'threshold'. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, one mteTriggerThresholdFallingEvent is triggered. That event is also triggered if the first sample after this entry becomes active is less than or equal to this threshold and mteTriggerThresholdStartup is equal to 'falling' or 'risingOrFalling'. After a falling event is generated, another such event is not triggered until the sampled value rises above this threshold and reaches mteTriggerThresholdRising.
4 mteTriggerThresholdDeltaRising	INTEGER32	ReadWrite	A threshold value to check against if mteTriggerType is 'threshold'. When the delta value (difference) between the current sampled value (value(n)) and the previous sampled value (value(n-1)) is greater than or equal to this threshold, and the delta value calculated at the last sampling interval (i.e. value(n-1) - value(n-2)) was less than this threshold, one mteTriggerThresholdDeltaRisingEvent is triggered. That event is also triggered if the first delta value calculated after this entry becomes active, i.e. value(2) - value(1), where value(1) is the first sample taken of that instance, is greater than or equal to this threshold. After a rising event is generated, another such event is not triggered until the delta value falls below this threshold and reaches mteTriggerThresholdDeltaFalling.
5 mteTriggerThresholdDeltaFalling	INTEGER32	ReadWrite	A threshold value to check against if mteTriggerType is 'threshold'. When the delta value (difference) between the current sampled value (value(n)) and the previous sampled value (value(n-1)) is less than or equal to this threshold, and the delta value calculated at the last sampling interval (i.e. value(n-1) - value(n-2)) was greater than this threshold, one mteTriggerThresholdDeltaFallingEvent is triggered. That event is also triggered if the first delta value calculated after this entry becomes active, i.e. value(2) - value(1), where value(1) is the first sample taken of that instance, is less than or equal to this threshold. After a falling event is generated, another such event is not triggered until the delta value falls below this threshold and reaches mteTriggerThresholdDeltaRising.
6 mteTriggerThresholdObjectsOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteTriggerThresholdObjects, the mteOwner of a group of objects from mteObjectsTable.
7 mteTriggerThresholdObjects	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from the firing of this trigger for this test. A list of objects may also be added based on the overall trigger, the event or other settings in mteTriggerTest. A length of 0 indicates no additional objects.
8 mteTriggerThresholdRisingEventOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteTriggerThresholdRisingEvent, the mteOwner of an event entry from mteEventTable.
9 mteTriggerThresholdRisingEvent	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdRising. A length of 0 indicates no event.
10 mteTriggerThresholdFallingEventOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteTriggerThresholdFallingEvent, the mteOwner of an event entry from mteEventTable.
11 mteTriggerThresholdFallingEvent	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdFalling. A length of 0 indicates no event.
12 mteTriggerThresholdDeltaRisingEventOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner of an event entry from mteEventTable.
13 mteTriggerThresholdDeltaRisingEvent	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdDeltaRising. A length of 0 indicates no event.
14 mteTriggerThresholdDeltaFallingEventOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner of an event entry from mteEventTable.
15 mteTriggerThresholdDeltaFallingEvent	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdDeltaFalling. A length of 0 indicates no event.

Table mteObjectsTable

Table Name	mteObjectsTable
In MIB	DISMAN-EVENT-MIB
Registered at OID	.1.3.6.1.2.1.88.1.3.1
Table Description	A table of objects that can be added to notifications based on the trigger, trigger test, or event, as pointed to by entries in those tables.
Row Description	A group of objects. Applications create and delete entries using mteObjectsEntryStatus. When adding objects to a notification they are added in the lexical order of their index in this table. Those associated with a trigger come first, then trigger test, then event.

mteObjectsTable Indexes:

Name	Type	Access	Description
1 mteOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
1 mteObjectsName	OCTETSTR Legal Lengths: 1 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A locally-unique, administratively assigned name for a group of objects.
2 mteObjectsIndex	UNSIGNED32 Legal values: 1 .. -1	NoAccess	An arbitrary integer for the purpose of identifying individual objects within a mteObjectsName group. Objects within a group are placed in the notification in the numerical order of this index. Groups are placed in the notification in the order of the selections for overall trigger, trigger test, and event. Within trigger test they are in the same order as the numerical values of the bits defined for mteTriggerTest. Bad object identifiers or a mismatch between truncating the identifier and the value of mteDeltaDiscontinuityIDWildcard result in operation as one would expect when providing the wrong identifier to a Get operation. The Get will fail or get the wrong object. If the object is not available it is omitted from the notification.

Other mteObjectsTable Columns:

Name	Type	Access	Description
3 mteObjectsID	OBJECTID	Create	The object identifier of a MIB object to add to a Notification that results from the firing of a trigger. This may be wildcarded by truncating all or part of the instance portion, in which case the instance portion of the OID for obtaining this object will be the same as that used in obtaining the mteTriggerValueID that fired. If such wildcarding is applied, mteObjectsIDWildcard must be 'true' and if not it must be 'false'. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time.
4 mteObjectsIDWildcard	INTEGER TruthValue (ENUM list below)	Create	Note: this object is based on the TruthValue TEXTUAL-CONVENTION. Control for whether mteObjectsID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard.
5 mteObjectsEntryStatus	INTEGER RowStatus (ENUM list below)	Create	Note: this object is based on the RowStatus TEXTUAL-CONVENTION. The control that allows creation and deletion of entries. Once made active an entry MAY not be modified except to delete it.

Table mteEventTable

Table Name	mteEventTable
In MIB	DISMAN-EVENT-MIB
Registered at OID	.1.3.6.1.2.1.88.1.4.2
Table Description	A table of management event action information.
Row Description	Information about a single event. Applications create and delete entries using mteEventEntryStatus.

mteEventTable Indexes:

Name	Type	Access	Description
1 mteOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
1 mteEventName	OCTETSTR Legal Lengths: 1 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A locally-unique, administratively assigned name for the event.

Other mteEventTable Columns:

Name	Type	Access	Description
2 mteEventComment	OCTETSTR Legal Lengths: 0 .. 255 SnmpAdminString	Create	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A description of the event's function and use.
3 mteEventActions	BITS Value Label/Meaning 0 notification 1 set	Create	The actions to perform when this event occurs. For 'notification', Traps and/or Informs are sent according to the configuration in the SNMP Notification MIB. For 'set', an SNMP Set operation is performed according to control values in this entry.
4 mteEventEnabled	INTEGER TruthValue (ENUM list below)	Create	Note: this object is based on the TruthValue TEXTUAL-CONVENTION. A control to allow an event to be configured but not used. When the value is 'false' the event does not execute even if triggered.
5 mteEventEntryStatus	INTEGER RowStatus (ENUM list below)	Create	Note: this object is based on the RowStatus TEXTUAL-CONVENTION. The control that allows creation and deletion of entries. Once made active an entry MAY not be modified except to delete it.

Table mteEventNotificationTable

Table Name	mteEventNotificationTable
In MIB	DISMAN-EVENT-MIB
Registered at OID	.1.3.6.1.2.1.88.1.4.3
Table Description	A table of information about notifications to be sent as a consequence of management events.
Row Description	Information about a single event's notification. Entries automatically exist in this this table for each mteEventEntry that has 'notification' set in mteEventActions.

mteEventNotificationTable Indexes:

Name	Type	Access	Description
1 mteOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
1 mteEventName	OCTETSTR Legal Lengths: 1 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A locally-unique, administratively assigned name for the event.

Other mteEventNotificationTable Columns:

Name	Type	Access	Description
1 mteEventNotification	OBJECTID	ReadWrite	The object identifier from the NOTIFICATION-TYPE for the notification to use if metEventActions has 'notification' set.
2 mteEventNotificationObjectsOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. To go with mteEventNotificationObjects, the mteOwner of a group of objects from mteObjectsTable.
3 mteEventNotificationObjects	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The mteObjectsName of a group of objects from mteObjectsTable if mteEventActions has 'notification' set. These objects are to be added to any Notification generated by this event. Objects may also be added based on the trigger that stimulated the event. A length of 0 indicates no additional objects.

Table mteEventSetTable

Table Name	mteEventSetTable
In MIB	DISMAN-EVENT-MIB
Registered at OID	.1.3.6.1.2.1.88.1.4.4
Table Description	A table of management event action information.
Row Description	Information about a single event's set option. Entries automatically exist in this this table for each mteEventEntry that has 'set' set in mteEventActions.

mteEventSetTable Indexes:

Name	Type	Access	Description
1 mteOwner	OCTETSTR Legal Lengths: 0 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator.
1 mteEventName	OCTETSTR Legal Lengths: 1 .. 32 SnmpAdminString	NoAccess	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. A locally-unique, administratively assigned name for the event.

Other mteEventSetTable Columns:

Name	Type	Access	Description
1 mteEventSetObject	OBJECTID	ReadWrite	The object identifier from the MIB object to set if mteEventActions has 'set' set. This object identifier may be wildcarded by leaving sub-identifiers off the end, in which case nteEventSetObjectWildCard must be 'true'. If mteEventSetObject is wildcarded the instance used to set the object to which it points is the same as the instance from the value of mteTriggerValueID that triggered the event. Each instance that fills the wildcard is independent of any additional instances, that is, wildcarded objects operate as if there were a separate table entry for each instance that fills the wildcard without having to actually predict all possible instances ahead of time. Bad object identifiers or a mismatch between truncating the identifier and the value of mteSetObjectWildcard result in operation as one would expect when providing the wrong identifier to a Set operation. The Set will fail or set the wrong object. If the value syntax of the destination object is not correct, the Set fails with the normal SNMP error code.
2 mteEventSetObjectWildcard	INTEGER TruthValue (ENUM list below)	ReadWrite	Note: this object is based on the TruthValue TEXTUAL-CONVENTION. Control over whether mteEventSetObject is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard if mteEventActions has 'set' set.
3 mteEventSetValue	INTEGER32	ReadWrite	The value to which to set the object at mteEventSetObject if mteEventActions has 'set' set.
4 mteEventSetTargetTag	OCTETSTR Legal Lengths: 0 .. 255 SnmpTagValue	ReadWrite	Note: this object is based on the SnmpTagValue TEXTUAL-CONVENTION. The tag for the target(s) at which to set the object at mteEventSetObject to mteEventSetValue if mteEventActions has 'set' set. Systems limited to self management MAY reject a non-zero length for the value of this object. A length of 0 indicates the local system. In this case, access to the objects indicated by mteEventSetObject is under the security credentials of the requester that set mteTriggerEntryStatus to 'active'. Those credentials are the input parameters for isAccessAllowed from the Architecture for Describing SNMP Management Frameworks. Otherwise access rights are checked according to the security parameters resulting from the tag.
5 mteEventSetContextName	OCTETSTR Legal Lengths: 0 .. 255 SnmpAdminString	ReadWrite	Note: this object is based on the SnmpAdminString TEXTUAL-CONVENTION. The management context in which to set mteEventObjectID. if mteEventActions has 'set' set. This may be wildcarded by leaving characters off the end. To indicate such wildcarding mteEventSetContextNameWildcard must be 'true'. If this context name is wildcarded the value used to complete the wildcarding of mteTriggerContextName will be appended.
6 mteEventSetContextNameWildcard	INTEGER TruthValue (ENUM list below)	ReadWrite	Note: this object is based on the TruthValue TEXTUAL-CONVENTION. Control for whether mteEventSetContextName is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard if mteEventActions has 'set' set.

DEPRECATED OR OBSOLETE OR HISTORIC OBJECTS

NOTIFICATIONS

TEXTUAL CONVENTIONS

These TEXTUAL-CONVENTIONS are used in other parts of the document above. They are SNMP's way of defining a datatype that is used repeatedly by other MIB objects. Any implementation implementing objects that use one of these definitions must follow its DESCRIPTION clause as well as the DESCRIPTION clause of the object itself.

Name	Type	Description
SnmpTagValue	OCTETSTR	An octet string containing a tag value. Tag values are preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 character encoding scheme described in RFC 2279. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. The use of control codes should be avoided, and certain control codes are not allowed as described below. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 representation is identical to the US-ASCII encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction must be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC1905]. An object of this type contains a single tag value which is used to select a set of entries in a table. A tag value is an arbitrary string of octets, but may not contain a delimiter character. Delimiter characters are defined to be one of the following: - An ASCII space character (0x20). - An ASCII TAB character (0x09). - An ASCII carriage return (CR) character (0x0D). - An ASCII line feed (LF) character (0x0A). Delimiter characters are used to separate tag values in a tag list. An object of this type may only contain a single tag value, and so delimiter characters are not allowed in a value of this type. Note that a tag value of 0 length means that no tag is defined. In other words, a tag value of 0 length would never match anything in a tag list, and would never select any table entries. Some examples of valid tag values are: - 'acme' - 'router' - 'host' The use of a tag value to select table entries is application and MIB specific.
TruthValue	INTEGER Value Label/Meaning 1 true 2 false	Represents a boolean value.
RowStatus	INTEGER Value Label/Meaning 1 active 2 notInService 3 notReady 4 createAndGo 5 createAndWait 6 destroy	The RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status
SnmpAdminString	OCTETSTR	An octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters.

TREE VIEW

Tree view generated by running: snmptranslate -Tp DISMAN-EVENT-MIB::dismanEventMIB