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.
Parsed from file DISMAN-EVENT-MIB.mib
Module: DISMAN-EVENT-MIB
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.
mteTriggerTest OBJECT-TYPE SYNTAX BITS { existence(0), boolean(1), threshold(2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of trigger test to perform. For oolean and
hreshold 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 objects
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
objects value, it will be fired again on every successive
value change for that object.
For oolean, 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 hreshold the test works as described below for
mteTriggerThresholdStartup, mteTriggerThresholdRising, and
mteTriggerThresholdFalling.
Note that combining oolean and hreshold tests on the
same object may be somewhat redundant."
DEFVAL { { boolean } }
View at oid-info.com
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.
Parsed from file rfc2981-Event.mib.txt
Company: None
Module: DISMAN-EVENT-MIB
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.
mteTriggerTest OBJECT-TYPE SYNTAX BITS { existence(0), boolean(1), threshold(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { { boolean } } ::= { mteTriggerEntry 4 }
mteTriggerTest OBJECT-TYPE SYNTAX OCTET STRING(SIZE(1..2)) ACCESS read-write STATUS mandatory DESCRIPTION "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." DEFVAL { '40'h } ::= { mteTriggerEntry 4 }
Automatically extracted from RFC2981
mteTriggerTest OBJECT-TYPE SYNTAX BITS { existence(0), boolean(1), threshold(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { { boolean } } ::= { mteTriggerEntry 4 }
mteTriggerTest OBJECT-TYPE SYNTAX BITS { existence(0), boolean(1), threshold(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { { boolean } } ::= { mteTriggerEntry 4 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.88.1.2.2.1.1 | mteOwner | 0 | 0 | The owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administra… |
| 1.3.6.1.2.1.88.1.2.2.1.2 | mteTriggerName | 0 | 0 | A locally-unique, administratively assigned name for the trigger within the scope of mteOwner. |
| 1.3.6.1.2.1.88.1.2.2.1.3 | mteTriggerComment | 0 | 0 | A description of the trigger's function and use. |
| 1.3.6.1.2.1.88.1.2.2.1.5 | mteTriggerSampleType | 0 | 0 | The type of sampling to perform. An 'absoluteValue' sample requires only a single sample to be meaningful, and is exactly the val… |
| 1.3.6.1.2.1.88.1.2.2.1.6 | mteTriggerValueID | 0 | 0 | The object identifier of the MIB object to sample to see if the trigger should fire. This may be wildcarded by truncating all or … |
| 1.3.6.1.2.1.88.1.2.2.1.7 | mteTriggerValueIDWildcard | 0 | 0 | Control for whether mteTriggerValueID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard. |
| 1.3.6.1.2.1.88.1.2.2.1.8 | mteTriggerTargetTag | 0 | 0 | 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 t… |
| 1.3.6.1.2.1.88.1.2.2.1.9 | mteTriggerContextName | 0 | 0 | The management context from which to obtain mteTriggerValueID. This may be wildcarded by leaving characters off the end. For exa… |
| 1.3.6.1.2.1.88.1.2.2.1.10 | mteTriggerContextNameWildcard | 0 | 0 | Control for whether mteTriggerContextName is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard. |
| 1.3.6.1.2.1.88.1.2.2.1.11 | mteTriggerFrequency | 0 | 0 | The number of seconds to wait between trigger samples. To encourage consistency in sampling, the interval is measured from the b… |
| 1.3.6.1.2.1.88.1.2.2.1.12 | mteTriggerObjectsOwner | 0 | 0 | To go with mteTriggerObjects, the mteOwner of a group of objects from mteObjectsTable. |
| 1.3.6.1.2.1.88.1.2.2.1.13 | mteTriggerObjects | 0 | 0 | The mteObjectsName of a group of objects from mteObjectsTable. These objects are to be added to any Notification resulting from … |
| 1.3.6.1.2.1.88.1.2.2.1.14 | mteTriggerEnabled | 0 | 0 | A control to allow a trigger to be configured but not used. When the value is 'false' the trigger is not sampled. |
| 1.3.6.1.2.1.88.1.2.2.1.15 | mteTriggerEntryStatus | 0 | 0 | The control that allows creation and deletion of entries. Once made active an entry may not be modified except to delete it. |