Currently the only way to make this work is to create a separate node for each slot. In configuration for each node you have to specify corresponding community string. To avoid issues with one and the same IP address for several nodes set checkbox "This is address of remote management node" for all these nodes. And disable configuration polls for these nodes. If you have a big network of such devices, you can contact Raden Solutions, they can develop a custom driver for such devices within sponsored development.

Added some info into documentation. Feel free to comment if anything else should be added.

@victor said in Problem creating tunnel between server and agent: What is debug level? You should see lines like "Adding CA certificate ..." on level 3 and more on level 5. I have started a clean new attempt in DebugLevel 5 with SSLTrace switched on. The agent sees the certificate of the server, and receives new certificates from server... I have attached the agent log for your reference. It shows the "clean" start until the bind to node fails and a restart of agent after that... Regards Detlev agent.log

This is sort of debug menu that has a list of all possible windows that management console can open. The thing is that some of windows only work when opened in some context, e.g. when executing some command using object tools. This debug menu will be removed in a future version.

Some info is present in admin documentation https://www.netxms.org/documentation/adminguide/advanced.html#web-api-rest-api REST API is work in progress and may change a lot in future, documenting of it waits until it get's more or less finalized. So currently the only way is to read source code.

What version are you using?

@alk said in NETXMS Password Recovery: Are you trying to login as "admin" or "system"? Whole procedure should be like this: stop netxmsd run "nxdbmgr reset-system-account" to unlock "system" account start netxmsd login as "system" / "netxms" In user manager change password any admin user login as admin user and disabled "system" user Hello Alex, glad to hear about you again. I followed your procedure and it worked, thank you. I didn't know there was a "system" user for netxms, as I tried to login with the default "admin" user given on installation guide. Also I found on the old releases the nxmc-2.1-M3-win32-x86 that matches with my 2017's NetXMS-VM version, so I can resume again my netxms path. Regards.

Just an update I downloaded CentOS 7 and was able to successfully build and install using the latest netxms source and postgres 12.    However i did run into  an initial issues when trying to nxdb init Unable to connect to database netxms_db@localhost as netxms (FATAL:  Ident authentication failed for user "netxms") i believe this is because the pg_hba.conf does not have an entry for netxms after changing to the following i was able to initialize via nxbmgr init local  all            postgres                                trust # IPv4 local connections: host    netxms_db netxms        127.0.0.1/32            md5 # IPv6 local connections: host    netxms_db netxms        ::1/128                  md5 using pqsql i created a db of netxms_db and  user netxms with password of netxms for testing    hope this helps

Registered it as a bug https://track.radensolutions.com/issue/NX-1880. We will fix it in next patch release. Best regards, Victor

Try installing this runtime - it's required for Postgres client but is not currently included in the installer. https://support.microsoft.com/en-us/help/3138367/update-for-visual-c-2013-and-visual-c-redistributable-package

Cancel that ! - Just found it 

Hi, Was Firewall on Linux machine  - for some reason although the rule was set for both directions it wasnt working inbound - created two seperate rules inbound and outbound and it started working !!.

Ok thanks so much ! 

Looks like currently this is not implemented.

Looks like coincidence - we didn't make any specific changes in graphs. But let's hope it will stay fixed. Best regards, Victor

With postgres or mysql there's a problem of housekeeping - deleting old datapoints when storage time elapses. This process may create big load on the database, especially if it's big. For timescale deletion is very optimal - a whole chunk of data for one day is deleted. There are a few sets of chunks - one for "Default" retention time and a few other sets <7 days, 7..30, 30..90, 90..180, >180 days. But the trick is that it's not possible to delete a daily chunk, if it contains data for at least one DCI that retention time has not elapsed yet. As the result, timescale database might take more storage space. Currently there's an issue when changing DCI retention time - https://track.radensolutions.com/issue/NX-1795 Can you give more details, what exactly you are doing in nxmc when you get disconnected? Does it replicates reliably, or randomly?

You can use DCI with origin "Script". For that you need to create a script in the script library and confgure that script name in properties of a DCI. Then in the script you can read parameters directly from agent     $node->readAgentParameter(name) ($node will be the object of node, to which the DCI belongs. You can also use this method on other nodes). You can also get last collected value of any DCI - https://www.netxms.org/documentation/nxsl-latest/#func-getdcivalue You can use "abort" operator in the script - if it's called, the script will terminate and no new datapoint will be generated at this time. Some examples of NXSL scripts are available here: https://wiki.netxms.org/wiki/SG:Script_Examples

Hi, I've got a router with a /64 IPv6 prefix and a Linux host connected to it. The linux kernel obtains an address using SLAAC and says it's a /64 (e.g. fd11:1111:1111:1111:abcd:abff:fecd:abcd/64). If I try to add both machines as nodes to NetXMS, the first works fine, but for the second I get an "ip conflict with node xxx" error. What's the best solution for this setup? Thanks,   Hendrik

Yes, this should solve the issue. Duplicate records are definitely a bug, but keeping them will not help in debugging it anyway. Best regards, Victor

Hello. Yes, you need to install agent on each machine (or enable SNMP, but I highly recommend to install agent).