NetXMS Support Forum

Hi!

First, you should create DCI for ifSpeed. Let's assume that it's description will be "Interface speed" (without quotes). After that, create DCI for ifInOctets, and create transformation script for it:


(($1 * 8) / GetDCIValue($node, FindDCIByDescription($node, "Interface speed"))) * 100


If you will use different DCI description for ifSpeed parameter, change call to FindDCIByDescription accordingly.

You can also take a look at the following topic:

https://www.netxms.org/forum/index.php/topic,292.msg1495.html#msg1495

Best regards,
Victor

Hello!

Please try to upgrade to 0.2.21 - it's available already at https://www.netxms.org/download/netxms-0.2.21.exe but not announced yet - we do some final testing. You problem looks very similar to one solved in 0.2.21, related to SNMP data collection.

Best regards,
Victor

List of available parameters populated by server during configuration polls, which is every 1 hour by default. You can start configuration poll manually by right-clicking on node object and selecting Poll -> Configuration.

Best regards,
Victor

You mean to notify when new updates are available for Windows but not installed yet? Why not to use WSUS for it - as far as I know it's free.

Hello!

It's intended for centrally stored configs. If you start agent with option -M management_server_address, then agent tries to connect to management server and get configuration file from there. In agent configuration manager you can define these configs and filters to decide which agent takes which config.

Best regards,
Victor

I agree, it can be useful feature.

For now, it potentially could be done on UNIX with combination of procmail and nxevent (or nxpush). Maybe it is also possible to run procmail on Windows under cygwin.

Best regards,
Victor

Yes, screenshots will be helpful

Похоже что сервер не может прочитать файл netxms.mib. Он должен быть в каталоге <install_prefix>/share/netxms/mibs.

Node status calculated based on two sources - active alarms for that node and status of child objects (usually interfaces). If you wish that node remains in NORMAL status event if some or all interfaces goes down, you should change status propagation algorithm for child objects of that node. You can select "fixed value" propagation algorithm for interface objects and set value to NORMAL.

Best regards,
Victor

It can be a problem for NetXMS, because if during status poll it determines that node is down, data collection will not be scheduled for that node. But, if there are no status polls, NetXMS will try to establish TCP connection for each parameter to be collected. With connection timeout about 1 minute, it can easily cause long data collection queues.

What is the reason for disabling status polls? If you don't want alarms, mails, etc. for SYS_NODE_DOWN events, you can just block them in the first rule of event processing policy.

Best regards,
Victor

Hello!

It's fixed in 0.2.21.

Best regards,
Victor

If you take a look at node object representing NetXMS server itself, you'll find some automatically created DCIs. There are queue length for status poller, configuration poller, data collector, and database writer, as well as average time to queue DCI for polling. You can setup thresholds on these parameters as for any other DCI and generate alarms, etc. General rule is that any of this parameters is higher than 0 for long period of time, you have a problem and should do something.

Best regards,
Victor

Very interesting information... Thank you for reporting!

Best regards,
Victor

Hi!

Further increase of data collectors will not help - we have similar problem at one of our customer's site, and it's related to SNMP. I'll publish updated version of NetXMS server today, it may help.

Best regards,
Victor

Quote from: xenth on May 05, 2008, 10:27:55 AM
I just noticed something very disturbing, the polling isn't going properly.

My set intervals aren't being listened to, I'll give you an example, this is one of my workstations.
I have set the interval to 60 seconds, yet it does NOT poll every 60 seconds 

It should poll every 60 seconds, yet when I view the history:

This is a VERY big problem as well, is it related to my other problem? 

Yes, most likely they are related. If you take a look at a result of "show queues" console command, you can see quite big number (330) in data collector queue. This means that at the moment when you type this command 330 requests for collecting data was waiting for processing, because all data collectors was busy. You can try to increase number of data collectors to 40 or 50 (by changing server's parameter NumberOfDataCollectors), this may help a bit, but will not remove the problem completely.

Some additional questions: do you have SNMP on the nodes? Do you use SNMP for data collection?

Best regards,
Victor