This article explains an integer overflow error that can happen while converting TimeTicks. |
SNMP traps cannot be processed. An Integer overflow occurs while converting TimeTicks (in this case, the "time-stamp" of an snmpv1 trap).
This message is from the mkeventd.log with debug enabled Setup → Events → Event Console → Settings → Event Console: Logging & diagnose → Log level → Processing of incoming events: Debug
2020-12-10 13:35:49,501 [10] [cmk.mkeventd.EventServer.snmp] receiveMessage: <ConstraintsIntersection object at 0x7fb225b324d0 consts <ValueRangeConstraint object at 0x7fb225b32410 consts 0, 4294967295>> failed at: ValueConstraintError('<ValueRangeConstraint object at 0x7fb225b32410 consts 0, 4294967295> failed at: ValueConstraintError(-1935586285,)',) at TimeTicks |
This looks like a relatively common bug in SNMP devices when they try to encode large positive numbers; we have already seen this for "Counter" values, and this time it's "TimeTicks." |
The relevant part from the SNMP-RFCs RFC 1155 and RFC 1902 are:
TimeTicks ::= [APPLICATION 3] IMPLICIT INTEGER (0..4294967295) |
.
In a nutshell: Contact the manufacturer of your device; perhaps there is a firmware update or something like that that fixes their bug.
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|