NetXMS Support Forum

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

Oops, that's my failure Prior to 1.1.5 DCI values only accessible via $1, $2, etc. variables. Array $values also was added in 1.1.5. I suggest to do upgrade first

Best regards,
Victor

This is because you use array instead of referencing it's elements. Correct version should looks like this:


for(i=0; $values[i] != null; i++)
{
  trace(0,"+++" . $values[i] . "+++");

  minTime = min(minTime, $values[i]);
  maxTime = max(minTime, $values[i]);
}


Best regards,
Victor

You miss "conditions" in documentation because it is not documented

Working with the conditions is as follows:

1. Create condition object somewhere in the infrastructure (services) tree.
2. Open properties, and on "Data" page, add DCIs
3. The, on "Script" page, write checking script. DCIs can be referred using variables $1, $2, etc., or via $values array. Script should return true if condition is active, and false otherwise. On status change, appropriate event being generated (configured on "Events and Status" page).

Starting with version 1.1.5, you can use foreach operator for enumerating DCIs, for example:


sum = 0;
foreach(v : $values)
{
trace(1, "+++ value = " . v . " +++");
sum += v;
}
trace(1, "+++ sum = " . sum . " +++");


Best regards,
Victor

Hi!

1. Server uses unicast communication with agents. For each agent separate TCP session is opened and reused when possible.

2. Agent only replies to requests from server. There are various different polls performed at different times: status poll (every minute by default), configuration poll (every hour by default), network topology poll, discovery poll. They all scheduled by poll manager.

Best regards,
Victor

Hi all!

NetXMS version 1.1.5 is out. It's mostly a bugfix release. Changes from previous version:

- Added "foreach" operator in NXSL
- New NXSL functions: GetDCIValueByName, GetDCIValueByDescription
- New attribute "comments" in NXSL classes "Node" and "NetObj"
- Dashboard configuration in console improved
- Database upgrade bug fixed
- Solaris support improved
- Many small improvements in management console

Best regards,
Victor

Hi!

You can create a condition object, add DCIs collecting current time from different servers, and write a script which will calculate deviation.

Best regards,
Victor

Hi!

Yes, it looks like 32bit applications cannot access counters provided by 64bit DLLs and vise versa: http://support.microsoft.com/kb/891238. This problem also seems very similar: http://btsc.webapps.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB21534. You can test it by running 32-bit agent on machine with AOS and check available objects with nxget.

Best regards,
Victor

Hi!

It's hard to tell anything without additional tests. I have found the following MS KB article: http://support.microsoft.com/kb/957841 but I'm not sure that this is the case. If I understand this article correctly, there is a bug when you can see counters, but cannot add them for collection. You wrote that you can see counters in perfmon - but can they be really added and data can be collected?
Also, try to run from server's command line:

nxget -w 30 -l windows_server_ip PDH.Objects

you should get list of PDH objects, with Microsoft Dynamics AX Object Server among them. Then, try to run

nxget -w 30 -l windows_server_ip "PDH.ObjectInstances(Microsoft Dynamics AX Object Server)" 

You should see the instance. And then

nxget -w 30 -l windows_server_ip "PDH.ObjectCounters(Microsoft Dynamics AX Object Server)"

Should show you list of counters.

Best regards,
Victor

Hi!

You can use this topic as reference: https://www.netxms.org/forum/configuration/calculated-dci/, just change expression in last example from sum to percentage calculation.

Best regards,
Victor

Server hranit vremja kak UNIX timestamp - kolichestvo sekund s 01.01.1970 00:00:00 UTC. Pri pokaze vremja perevoditsja v time zone klienta. Raznica v 1 chas obichno bivaet pri nesovpadajuschih time zonah ili nepravil'no vistavlennom letnem/zimnem vremeni.

Added.

Best regards,
Victor