NetXMS Support Forum

Try

if ($node->sysDescription ~= ".*2003.*")
  println("matches");


"~=" is a regex comparison.

Try to enclose the DB password in "".

Does that work?

apt-get install netxms-agent
apt-get install netxms-server
apt-get install netxms-dbdrv-mysql


I recommend checking out the video tutorials if you are new to NetXMS
https://www.netxms.org/forum/general-support/netxms-video-tutorial-series/

Try to map the share to a network drive, and then poll the file count from there.

Just as an addition, its also fully documented in the Administrator Guide here:
https://www.netxms.org/documentation/adminguide/agent-management.html#agent-external-parameter

Actions are for, well, running actions on nodes. This means they are one-time things, initiated by you.

What you want is ExternalParameter and ExternalParameterProvider.
These can be used to execute arbitrary commands on the OS, and their results will be presented as an NetXMS Agent Parameter, which you can use in a DCI.

There is a good debate on ExternalParameter here:
https://www.netxms.org/forum/configuration/agent-config-(action-externalparam)/msg3136/#msg3136

You can see an example of how to use an ExternalParameterProvider here:
https://wiki.netxms.org/wiki/Bind9

Use a Script DCI, and create the script to walk the appropriate OID tree and return a different value when the series occurs from when it doesnt accur.

Then use a standard threshold to create threshold violation events.

What version of NetXMS are you running?

I remember in old version (pre 1.2.17), auto-bind remove would remove the templates from nodes.
This was however fixed.

IP address uniqueness is one of the basic concepts in NetXMS... I am pretty sure internally the code also relies on single IP = single device a lot.
Victor will however have to comment more on this.

Simply put a Raspberry Pi, or similar $30 Linux machine into the network, and use it as a proxy.

You have 2 opions:
1) if this is multiple customers/sites separate them into zones.
You can research how zones work and what they are used for in the documentation.

2) If you dont want to use Zoning, simply place a proxy in the network, and proxy SNMP over that proxy to all local devices.

Its the same issue.

You need to compile the management console from sources to have the newest version which is compatible with the newest version of the server you compiled.

There is multiple topics on the forum regarding the Console compilation, example:
https://www.netxms.org/forum/windows/compilation-of-a-netxms-console-in-eclipse/

If you built the server from the dev snapshot (which means its newest dev code), you also need to build the client from the snapshot.

You simply have a too new version of server for what your client can support.
(which makes sense since you built the newest server from dev, but you are using the release client)

You have GetCustomAttribute(), SetCustomAttribute() and DeleteCustomAttribute() NXSL functions available.

Create a script that iterates over all the nodes in your system, and manipulates the custom attributes as needed.
You can then schedule this script to run using the internal NetXMS scheduler.

Here is an example of bind9 monitoring using an ExternalParametersProvider script.
https://wiki.netxms.org/wiki/Bind9

There is also a link to a git repo containg the actual TCL script that collects the data.