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.
Parsed from file DISMAN-EVENT-MIB.mib
Module: DISMAN-EVENT-MIB
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.
mteTriggerValueID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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 rue and if not it must
be
alse.
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 adType 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."
DEFVAL { zeroDotZero }
View at oid-info.com
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.
Parsed from file rfc2981-Event.mib.txt
Company: None
Module: DISMAN-EVENT-MIB
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.
mteTriggerValueID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { zeroDotZero } ::= { mteTriggerEntry 6 }
mteTriggerValueID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-write STATUS mandatory DESCRIPTION "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." DEFVAL { {0 0} } ::= { mteTriggerEntry 6 }
Automatically extracted from RFC2981
mteTriggerValueID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { zeroDotZero } ::= { mteTriggerEntry 6 }
mteTriggerValueID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { zeroDotZero } ::= { mteTriggerEntry 6 }
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.4 | mteTriggerTest | 0 | 0 | The type of trigger test to perform. For 'boolean' and 'threshold' tests, the object at mteTriggerValueID MUST evaluate to an i… |
| 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.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. |