NetXMS Support Forum

Oops, there was indeed a syntax error.

Fixed the script in the original post, please try it.

Both of the issues you mention were mentioned multiple times here on the forums, and I think there are also bug-tracker feature requests for them.

I definatelly agree this needs addressing, +1 from me

Here is the script I use:

cpuCount = AgentReadParameter($node, "System.CPU.Count");

if (cpuCount == null || cpuCount == 1)
  return null;

array cpuArray;

for (i = 0; i < cpuCount; i++)
  cpuArray[i] = i;

return cpuArray;


Ok, this will probably be much faster in person.

Feel free to add me on Skype at t.kirnak[at]atris[dot]sk.

Are you sure you have the portcheck SubAgent enabled on your NetXMS server?

2) To make the tutorial shorter and more generic-oriented, I chose just custom port check.
Feel free to use actual HTTP service checking (and setup the DCI accordingly).

3) Its not redundant. We need this 2nd DCI for node status calculation.
The DCI used for node status calc must return values consistent with object status codes.
This is why it has the transform script, and has the "Use for status calculation" checked.

We cant use the ServiceResponseTime DCI, because we want to have actual historic values of the response time.
So this one we dont want to / cant use for status calc.

As mentioned, this would not be needed if the node responded to ICMP, and status poll would just use ICMP for status calculation.

It a bit more complicated for "netxms.org", because it doesnt respond to ping.

I created a step-by-step tutorial for you:
https://wiki.netxms.org/wiki/Step_by_step_service_monitoring

Please note, that for a website that responds to ping, it would be much simpler

As for 2), you need to create the DCI on the "netxms.org" node, but set the source node to the server.
You will find this option in the DCI configuration.

This mean your NetXMS server will poll the data, but the DCI will display correctly on the "netxms.org" node.

There is a feature request for this on the dev tracker:
https://dev.raden.solutions/issues/874

Its sadly too common that vendors provide broken MIBs.
I would expect that is the case here as well.

I suggest you post the MIBs here, and ask Victor for help fixing them

Are you running 2.0.4?

There are known issues in 2.0.2 and 2.0.3 with this.

I created a ticket for this:
https://dev.raden.solutions/issues/1246

Is it working correctly for you now and importing all the nodes?

Sounds like a bug.

But you can turn if off - right click and uncheck "Use multipliers".

After consulting with Victor, we found a potential issue when containers for imported nodes have name duplicities with other objects in NetXMS.
(internally, code could have chosen a non-container object to attempt to bind a node to)

I fixed it and released a newer version:
https://github.com/tomaskir/NetXMS-csv-importer/releases

Please try and let me know if it works now.