NetXMS Support Forum

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

Hi!

In fact, if you change discovery settings from old console via Control Panel -> Network Discovery dialog, not directly by changing server's parameters, you don't need to restart the server - it will reconfigure and restart required internal processes automatically. I'll add similar discovery configurator to new console as well.

Best regards,
Victor

Hi!

It looks like it is system-wide parameter in Windows. At least Eclipse does not provide any API for controlling balloon timeout.

Best regards,
Victor

Hi!

It's fixed now.

Best regards,
Victor

I have added those options. Parity should be specified as N, E, or O. So fully specified string will be

Device = 0:"COM1:,9600,8,N,1":BCMXCP

Default speed is driver-dependent (i.e. 19200 for BCMXCP and 2400 for APC), default data bits is 8, default parity is N (none), and default stop bits is 1.

Best regards,
Victor