At some point external parameters started to capture STDERR in addition to STDOUT. Most probably your script produces some sort of textual error that is being captured. Then NetXMS tries to interpret it as integer and this way it becomes 0. You can check with nxget nxget IP_ADDRESS_OF_AGENT name_of_the_parameter

Hi, it could be access control issue - maybe account you are using don't have access to those nodes. Discovered nodes will appear in "Entire Network" tree under appropriate subnet. You can try to login with user "system" and check - this user always has access to all objects, so you should see them or be able to find. Best regards, Victor

So agent is built for older MySQL client library. What Linux distribution you are using? If it is Debian or Ubuntu, I highly recommend using deb packages for installation. For RedHat we also provide separate binary package. If none of the above, then you either have to install required libmysqlclient or build agent from sources. Best regards, Victor

Awesome, thank you very much!

You should be able to use internal parameters ICMP.PacketLoss and ICMP.ResponseTime.Last. Usually you'll need variants without instance - they will return data for primary IP address. Variants with instance should be used when you have configured additional ping targets on a node and want to get information for those targets. Best regards, Victor

Thank you, works perfectly.

I think that it could be good idea to ignore notPresent interfaces by default on the server level. We will discuss that internally and likely add as configurable option. But for now hook script is a way to go. Best regards, Victor

Script-based DCI will be the best soluion here, I think. Script should be something like (pseudo code): value = null; if (CURRENT_NAME@$node != null) { // custom attribute CURRENT_NAME on current node value = $node->readAgentParameter("..." . CURRENT_NAME@$node); } if (value == null) { for (item : $node->readAgentList("...")) { if (item match "...") { // correct element found $node->setCustomAttribute(CURRENT_NAME, item); } } if (CURRENT_NAME@$node != null) { // custom attribute CURRENT_NAME on current node value = $node->readAgentParameter("..." . CURRENT_NAME@$node); } } return value;

Perfect - Thank you for the quick solution ! Best regards, Thomas

Hello I am looking for Juniper Srx router snmp oids to monitor. Perhaps someone has working template that they feel like sharing ? Egert

Address filter is empty, just filtering on SNMP/SSH/agent protocol. Following hints in this thread https://www.netxms.org/forum/general-support/discovery-through-proxy/15/ I increased ThreadPool.Discovery.BaseSize from 1 to 4 and enabled parallel processing, then restarted the service. The expected node was then discovered by the next day [as with the other system, log level is such that they were rotated away so I don't know exactly when]. I am going to assume that other things I wasn't specifically looking for have been discovered as well. [image: ksnip_20220705-090618.png]

When interface is down, we have two contradicting requirements: one is to show what was connected to that interface before it went down, and other is to show actual connectivity. First requires to keep showing link between disconnected interfaces, second requires to delete that link immediately after interface goes down. As NetXMS server has no way of knowing if disconnect is permanent or temporary, and there are seems to be more requests to provide access to last known connection information, NetXMS server keeps that connection until it will know that topology was changed (for example, one of previously connected interfaces will go up and LLDP will report different peer). One possible solution could be configurable topology expiration time - i.e. if interface is down for N days, remove any known topology information from it. Currently as a workaround you can delete interface that is disconnected - configuration poll will find it and re-create, but peer information will be erased. Best regards, Victor

Collector is there, but we didn't get to actually processing flow data. I still want to add this functionality, it is question of available resources and priorities. Best regards, Victor

Hi, do you mean database lock in the DB so server complains that database is locked by another instance? If yes, you should list peer IP address in netxmsd.conf on cluster nodes. For example, if you have cluster nodes with addresses 10.0.0.1 and 10.0.0.2 (with whatever VIP moving between them), on node 10.0.0.1 you should add PeerNode = 10.0.0.2 to netxmsd.conf and on node 10.0.0.2 add PeerNode = 10.0.0.1 That way server will read the lock, check if server is running on peer node (by attempting to connect to agent and check running processes and by connecting to port 4701), and remove stalled lock if netxmsd is not running on peer node. Best regards, Victor

I can confirm that changing server is not implemented yet in new web UI. Best regards, Victor

Asterisk subagent is being built in .deb packages, but in generic Linux build it's not included. So it your platform is not .deb compatible, the only option is to build from sources.

Figured it out, needed to install Windows (x64) installer netxms-legacy-gui-4.1.380-x64.exe.

Thanks for the guidance! I corrected that error, and found about 4 more, plus another line that was commented out that it required. I passed all this info along to EnGenius so hopefully they can fix their MIB generator.

Thank you!!  We actually decided to go w/ Zabbix.

Your writing is precise. For agent to server tunnel industry-standard TLS connection is established. Also you can install netxms proxy in a remote office. That proxy will be the only node that communicates to the server directly. Proxy would communicate to all other machines at that location.