Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - komj

#1
Yes, I do similar thing.

As far as I could see from all different devices that we have in our network, correct counter values are never above 10 digit number, and incorrect counter values are always above the 14 digit number, therefore I compare the actual counter value to number with 12 digits and workaround seems to work fine until now.
#2
First of all, thank you for your reply.

Secondly,
what do you recommend as a workaround until you implement what you described?

I already mentioned workaround with the transformation script, is that a good solution?
#3
Hello all,
firstly, I want to say that netXMS is a great product. Thank you for that :)

Secondly,
In the company I work we are in transition period from other monitoring tools to netXMS. At the moment we are still testing if netXMS is fulfilling our needs and we have a problem that I will describe below.
This happens on multiple devices (different vendors, operating systems, etc.), below I will use only one device as an example.

We configured the monitoring of network interfaces via SNMP as you can see in the attached image (nic-mon-conf.jpg). This is working fine most of the time.

The problem arises after some time network interface is being monitored. Problem is that the traffic reported is in hundreds of terabytes as you can see in the attached image (nic-mon-incorrect.jpg).

I also attached an image where traffic monitoring looks ok (nic-min-ok.jpg).

Also attached the image of the value history for one of the DCI (nic-mon-value-history.jpg). It seems that is the time when problems happens.

I assume that this is not related to the netXMS in any way since the netXMS is just getting the the value from the device. But on the other hand I don't see this behavior with other network monitoring tools, for example The Dude, check attached image (nic-mon-dude.jpg). All these graphs from The Dude and netXMS are from the same device and same time interval.

I know that this problem can be mitigated with transformation script, but I would like to know the root cause of the issue.

With all said, my questions are:
1. Anybody else have this problem?
2. Any ideas why this happens?

Thanks to anybody taking time to read this and to respond.