NetXMS Support Forum

It's definitely a bug so it will be fixed in 1.1.6.

Best regards,
Victor

Hi!

Yes, it's a bug in NXSL interpreter. It erroneously interprets OID as floating point number. As a workaround, you can replace == with like operation:


return ($node->snmpOID like ".1.3.6.1.4.1.9.1.516");


Best regards,
Victor

I test it on my system with 1.1.5, and everything works as expected. Could you please send me configs of proxy agent and destination agent? Also, what operating system NetXMS server is running on?

Best regards,
Victor

Quote from: lindeamon on October 03, 2011, 05:33:11 PM
how can i disable the agent polling for all the switches instead of checking it 1 by 1 ?

Unfortunately it's not possible.

Best regards,
Victor

Could you please post exact script code and actual SNMP OID value? Script posted earlier looks correct, so I suppose some typo or similar error when defining OID.

Best regards,
Victor

I just tried to reproduce this issue on test server, but without success - everything work as expected. Could you please set debug level to 9 (you can do this while server is running by entering "debug 9" command on server console, either via management console or nxadm tool), try to create a new node, and send me the log?

Best regards,
Victor

Hi!

Variable $node is unset in condition scripts, because it's not a node. Currently it's not possible to access condition's custom attributes from script. I'll add some method to access them.

Best regards,
Victor

Hi!

I'll test it during a day.

Best regards,
Victor

Fixed. Thanks for reporting!

Best regards,
Victor

Hi!

Sorry, it's my failure I completely forgot about it. I'll made a patch for agent.

Best regards,
Victor

Hi!

Do you enter only IP address, only name, or both when creating node? Also, what is server operating system?

Best regards,
Victor

Hi!

Looks like agent is not running or it's configuration file is incorrect. Please check that nxagentd.conf has MasterServers record containing both 127.0.0.1 and server's interface address. You can also post your nxagentd.conf here for verification.

Best regards,
Victor

Quote from: teddymills on September 30, 2011, 11:13:42 PM

In NETXMS, is there a summary/totals of network traffic collected so far ?

What parameter name should I be using?

Should I collect every 10 minutes with a retention of 365 days sound reasonable?


I need to view the summary of network traffic on the interface.(eth0)

I have been collecting network traffic on the interfaces.

I have been using NetInterface.Bytes.In+NetInterface.Bytes.out.
This gives me bytes per second on the interface.

I can export the network traffic data, but I really do not want to manually compile millions of data samples
to get a number that I can see just by looking at my overall network graphs.

I told my manager this, but I was told I need a hard number. (not an estimate of the average from a graph)

I did enable Network.Interface.Total, however since I only enabled+applied that today, that cannot help me.

ifconfig cannot help because instance are rebooted on occasion and the RX/TX counter resets to zero when the server is rebooted.

The best solution I could think of is following:

1. Create DCI which calculates simple delta (not average per second) for network traffic.
2. Create second 64bit unsigned or floating point DCI based on internal dummy parameter, and use transformation script to add up last delta from first DCI to it. You can also reset the value each day, month, etc.

Best regards,
Victor

Quote from: teddymills on October 01, 2011, 02:26:27 AM
NetInterface.BytesIn and NetInterface.Bytesout out is an unsigned integer. 

With busy sites, should not this be an unsigned 64-bit ?

They should. The problem is that not all operating systems supports 64-bit counters on interfaces. I'll take a look at network interface counters in different OSes.

Best regards,
Victor

Hi!

Condition uses last collected value of DCIs - checking condition does not cause DCI poll. You can switch to custom schedule - if you will have schedule like * * * * *, you DCI will be collected at the beginning of each minute. Scheduler check DCI schedules once per 2 second, so you will not be able to achieve better than 2 second accuracy.

Converting conditions to something similar to nodes with DCIs makes sense. I'll think about it.

Also, I thought about another way of checking server time sync: you can collect server's system time once per minute and compare it with monitoring server's time. To check that monitoring server's time is accurate, you can check ntp status on monitoring server. That way should be easier probably while still accurate.

Best regards,
Victor