NetXMS Support Forum

И в 4.4.3 добавили несколько макросов:
-  New event processing macros %d (DCI description), %D (DCI comments), %L (object alias), and %C (object comments)

The option to get older release on Debian is to compile from sources, but this might be a bit complicated.

What about the first option - can you upgrade your current installation of netxms and migrate the database then?

Yes, we need same version of NetXMS to migrate db.
To summarize the possible ways:

- upgrade the "old" netxms first, then export the database and import into same version.

- install older NetXMS on the new system - for Debian/Ubuntu repository actually stores a number of previous versions, you can check with:
apt-cache policy netxms-server

Then you can install specific version, but you need to specify the version also for all netxms packages which server depends upon. E.g. for to install agent there's two more packages, for server there are a bit more:
apt install netxms-base=4.3.4-1 netxms-dbdrv-sqlite3=4.3.4-1 netxms-agent=4.3.4-1

- export file produced by nxdbmgr is actually sqlite database. So you can specify that file in netxmsd.conf:
DBDriver=sqlite.ddr
DBName=/path/to/your/file/netxms.db
and start the server. It will upgrade the sql file to the latest version, then you can stop the server and use nxdbmgr to perform import.

The logic is that if "Samples" is set to 3, then all last three collected values should be "1" to trigger the threshold. If just one non "1" value comes, this means "last 3 values should be equal to 1" becomes false and it instantly generates threshold recovery event.

You can use script threshold, there you can use https://www.netxms.org/documentation/nxsl-latest/#func-getdcivalues function to get a number of last values and make the decision in the script. Drop a line if you need an example for such script.

This view was just forgotten to move to the new UI, thanks for reminding.

Central server is typically can handle thousands of nodes on it's own, so there's no much need in offloading it, but yes, proxies can be used that way. More interestingly - with cache mode on proxy can collect data even if there's no connection to central server. You can have several proxies on a zone - in this case they will be in HA mode, exchange hearthbeat messages and data collection will move to one if another one goes down

nxmc-light is the name of visual theme. In the legacy UI we had a few of these, in the new one there's only one so far.

First thing needed is Java 17

Port 161 is probably not needed - is there anything inside the container that listens to it? Anyways, if there is - agent should be able to work as a proxy for the node where it is running.

For proxying - you need to have:
EnableProxy=yes
EnableSNMPProxy=yes
SubAgent=ping
SubAgent=ssh            # optional, only if you want to use ssh monitoring
in configuration of the agent

Is agent able to send ICMP requests - you can try collecting Icmp.Ping(1.2.3.4) metric from that agent

You can also try operation without network discovery - by adding a node for a device in that zone and manually specifying that proxy in properties of the node.

Yes, correct, since devices in your management network are directly accessible from NetXMS server, there is no need for zoning to monitor them.

In the scripting language it's different then in SQL. When the script (you probably use script threshold) is invoked, DCI value is contained in $1 variable. Any operation with this variable will take it as a whole thing.

We will increase the limit, fix will be in a patch release that should be out in a few days.

Yes, to communication from server to agent you need just one port - 4700 on agent side. So yes, if you have several agent nodes behind a firewall, you can forward e.g. 4700, 4701, etc to these agents. Check "Communication through external gateway" checkbox in node properties - this is for the server to allow several nodes with same IP and to build topology information correctly.

However, this approach is not very convenient, as you need to specify port number for each node. Alternatives are:
- if you have a machine behind the NAT that is running all the time (or several machines and at least one of them running) you can configure netxms agent there as proxy. In this case communication to other systems will happen through that proxy, you don't need to open any more ports, network discovery will work
- netxms agent can establish tunnel connection to the server - in this case you don't need any port forwarding


Proxy agent is specifically netxms agent (with a few params in it's config - EnableProxy=yes, EnableSNMPProxy=yes...). For your router to act as a proxy you need to have a way to install netxms agent there. It's possible to build netxms agent for openwrt, or it can work on mikrotik routers that support docker.


If you specify some address as proxy for a zone, that agent should be configured to work as proxy. For your approach with port forwarding there's no need to create a zone or specify proxy (buy anyways you can create a zone to group the nodes or to add a proxy in the future)

What is the maximum length that you are encountering?

We will add option to specify authentication method in a future release, but currently that's not possible. Meanwhile you can use "shell" notification channel and call some script that would invoke curl from command line