| OID | 1.3.6.1.2.1.88.1.2.2.1.5 |
| Module | DISMAN-EVENT-MIB (CISCO) |
| Nom | mteTriggerSampleType |
| Acces | readwrite |
| Status | current |
| Description | 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. |
| Syntaxe | Enumeration (1-absoluteValue, 2-deltaValue) |
| Module | DISMAN-EVENT-MIB (ietf) |
| Nom | mteTriggerSampleType |
| Acces | readwrite |
| Status | current |
| Description | 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. |
| Syntaxe | Enumeration (1-absoluteValue, 2-deltaValue) |