The value of this object specifies the comparison
operation to be performed between the value of the
managed object indicated by checkRuleOid and the
value indicated by checkRuleValue. Some operations
cannot be applied to all the types of object. If
the value of the checkRuleOperation is inconsistent
with the type of the object indicated by checkRuleOid,
then an attempt to activate the row results in an
inconsistentValue error.
The value 0 can be configured for all the object
types and means that no operation is performed and
the rule never fails.
When the type of the object indicated by checkRuleOid
is IpAddress, BITS, OBJECT IDENTIFIER then only the value
equal(2) can be configured. For the IpAddress, the value
of the object indicated by checkRuleOid is compared byte
by byte with the value of checkRuleValue and the rule
doesn't fail if all the bytes are matched. For the
OBJECT IDENTIFIER, the rule doesn't fail if checkRuleValue
encodes an OID of the same dimension of the value of the
object indicated by checkRuleOid and the two OIDs are
equal. For the BITS, the rule doesn't fail if the
checkRuleValue encodes a bitstring long at least as the
number of the named bits and all the named bits are
matched with that bitstring.
When the type of the object indicated by checkRuleOid
is INTEGER, Integer32, Unsigned32, Counter32, Counter64,
TimeTicks, Gauge32, all the values from 1 to 6 can be
configured. These values define simple mathematical
operations: the rule doesn't fail if the the value
of the object indicated by checkRuleOid is, respectively,
!=, =, <, <=, >, >= than the value of checkRuleValue.
A value of of delta(7) can be configured only for
Counter32, Counter64, Gauge32; moreover it is permitted
only if the check including the rule is performed
automatically and thus its value of checkResultInterval
greater than 0, otherwise an inconsistentValue error is
returned. For a delta operation, each time the rule is
performed, the difference between the actual value of the
managed object and its value at the last performance is
considered and the rule doesn't fail if the difference is
<= than the value of the checkRuleValue. If the actual
value is less than the previous one, then the difference is
augmented with the value 4294967295, like as the managed
object reached its maximum value and it has been resetted.
Each time the new value of the managed object must be
stored by the device in an internal buffer. The buffer
must be handled so that when a new managed object is
controlled, a new entry is allocated for it. If no more
entries are available, then the rule fails with severity
4294967294.
If a managed object for which an entry was previously
allocated, doesn't exist when a new execution of the delta
operation is performed, its entry should be removed.
When a new entry is allocated for a new managed object,
its value is stored in the entry, but the operation is not
computed and the rule doesn't fail; the delta operation
is normally computed only from the second time. |
|
INTEGER |
noOperation(0), unequal(1), equal(2), less(3), lessOrEqual(4), greater(5), greaterOrEqual(6), delta(7) |
|