<![CDATA[Inbound Traffic (bit) does not work correct]]>Hi,
i have a lot of dci elements for the port traffic (bits/sec). As you can see in the picture, this does not work if the traffic is more than 2.1g. Suddenly we have negative values. The Port is a 10g port.
If I monitor byte instead of bit, everything works fine. Even if I update the mysql database (*8 to get bit) everything is still fine (and i get about 2.7-3g)
So I think that there is a Bug in the DCI bits/s with the transformation.

Here some information:

I tried:
30 an 60 seconds polling interval
Unsigned integer 64 bit and Integer 54 bit

If I take a look at the History values for the DCI in netxms I get something like:
2140082744
2130266056
-2088964288
-2087799680
2027156922

If you check the mysql Database sometimes I get values like:
18446744071578687616
18446744071621501168
and sometimes negative values.

line.PNG

]]>https://forum.netxms.org/topic/4784/inbound-traffic-bit-does-not-work-correctRSS for NodeFri, 13 Nov 2026 16:05:17 GMTFri, 04 Nov 2016 06:43:33 GMT60<![CDATA[Reply to Inbound Traffic (bit) does not work correct on Tue, 08 Nov 2016 06:20:13 GMT]]>I think the problem is the max value of integer. It´s 2.147.483.647. I don´t know why he ignores the Datatype you set at the dci.
I think you can solves this if you change the transformation script from "return $1 *8;" to "return $1 * 8.0;".
I will test this today.

]]>https://forum.netxms.org/post/21329https://forum.netxms.org/post/21329Tue, 08 Nov 2016 06:20:13 GMT