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.
Parsed from file DISMAN-EVENT-MIB.mib
Module: DISMAN-EVENT-MIB
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.
mteTriggerFrequency OBJECT-TYPE SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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."
DEFVAL { 600 }
View at oid-info.com
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.
Parsed from file rfc2981-Event.mib.txt
Company: None
Module: DISMAN-EVENT-MIB
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.
mteTriggerFrequency OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { 600 } ::= { mteTriggerEntry 11 }
mteTriggerFrequency OBJECT-TYPE SYNTAX Gauge ACCESS read-write STATUS mandatory DESCRIPTION "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." DEFVAL { 600 } ::= { mteTriggerEntry 11 }
Automatically extracted from RFC2981
mteTriggerFrequency OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { 600 } ::= { mteTriggerEntry 11 }
mteTriggerFrequency OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { 600 } ::= { mteTriggerEntry 11 }
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.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.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. |