NetXMS Support Forum

Its paged information. There is a "Get more data" button in the top bar - F9 shortcut.

Or is your problem something different?

I will consult with Viktor (since the error is from the NetXMS API), and get back to you asap.

The fix for the 2nd issue is actually in 2.0.4, not 2.0.3.
(try it with 2.0.4 and let us know if it works or not)

For the first issue, there is a ticket:
https://dev.raden.solutions/issues/1232

Check your "CheckTrustedNodes" server config variable (set it to 0 and restart server).
I have a feeling we are running into an issue with security here.

https://wiki.netxms.org/wiki/SG:Security_Issues

Object ID in this case = Node ID.

It works fine for me:
nxapush -o 4535 test-param=test

Its Object ID and DCI Parameter (NOT Description).

I suggest installing the manager app on Tomcat, and checking out how things look like in the manager.
(if the nxmc app is deployed and started, what path, etc.)

Default port for Tomcat is 8080, but your OS might package it differently.
After manager is installed/deployed, it should be available at "http://server:8080/manager"

You need to specify object ID for which this data is being pushed for.

Example:

nxapush -o 1001 some_dci=2


Please run tcpdump (or wireshark or similiar) and look at the actual packets of the incoming syslog messages.

What IP address do they come from?
If you put ">that_ip_address" into the object tree filter, does it find anything (make sure to prefix the IP with ">")?

The source IP address of the syslog message packet gets looked up across all your nodes present in NetXMS.
Are you sure you have a node with the address of the syslog messages present in NetXMS?

Bonus info: are syslogs coming over IPv4 or IPv6?

I can give you RPi server packages, but I really do NOT recommend running netxmsd on RPi.

Usually when running the server on RPi, you would use sqlite DB (since you will not have a full featured DB server available).
The NetXMS team has stated multiple times that they want to deprecate sqlite, and sqlite has quite a few known bugs.

Also, unless you have a very good SDHC Card (class 10+ with read/write of 40+ MBps), it will be painfully slow.

What are your "SyslogIgnoreMessageTimestamp" and "SyslogNodeMatchingPolicy" server configuration variables configured to?

Also, did you get it working before 2.0.4, or is this the same issue persisting from 2.0.2/2.0.3?

You can actually get per-ssid client-count on MikroTik.
Check out the .1.3.6.1.4.1.14988.1.1.1.3.1.6 tree.
(each SSID has its own instance, and then client count as value)

As for per wireless card, I dont have a multi-card MirkoTik to test with, but from memory, I think you can get per-card clients as well.

To your actual request tho, you can use 'nxapush' utility from the script which generates the files for you to push the data directly into NetXMS DCIs.
Or even 'ExternalParametersProvider' to provide a whole bunch of values as DCIs through the Agent.

Documentation for both is available on the forums and/or the wiki.

Very easy with a "Script" type DCI.

Just create a script named "count_ARP_entries" in the script library, and used that for the DCI parameter.
(DCI origin will of course be "Script")

For the script, you can do this:

walk_oid = "1.3.6.1.2.1.4.22.1.2";

tube = CreateSNMPTransport($node);
if (tube == null)
  return null;

varbinds = SNMPWalk(tube, walk_oid);
if (varbinds == null)
  return null;

return varbinds->size;


Refferences:
https://wiki.netxms.org/wiki/NXSL_Function_Reference
https://wiki.netxms.org/wiki/SG:Script_Examples

Here you go
https://www.netxms.org/forum/installation/raspberry-pi-3-compile-agent/msg19784/#msg19784

Solution without new feature request would be to put a Raspberry Pi (or a similiar SBC) into the network and use it as a proxying agent.

Wish I could help in another way, but without a proxy in the network, not much can be done in this case.