I use zones. If the proxy node for a zone is down the nodes monitored via SNMP are in Unknown Staus, which is correct state, but the nodes monitored by ping only are reported as down and they have Critical Status. What is worst that the down state of the node monitored by ping sometimes reported before the down state of the proxy, which suggests that the node is really down. Is it possible to have Unknown Status for all nodes behind a proxy and not report the nodes as down in case the proxy node is down?

Debugging is bit hard, the time it takes to run poll (about 5-10 sec) there will be 45000 lines generated. Egert

This hook is executed on every configuration poll (by default it's once an hour)

Hi, Victor. Yes your are right. it is very strange. The last week I decided to disconnect the manager console sotware from the netXMS server. I connected it again later. Then I did create a container and bind any object without problem with it. Anyway, Thanks for your interest to help me. Cheers.

That worked. Thank you!

The names of parameters changes at some point. A newer template version is shipped, but NetXMS with default settings does not overwrite the templates (with the idea that user could have changed the out of the box templates). It's Server Configuration setting "ImportConfigurationOnStartup". By default it's "Only missing elements", so you can either delete the template and restart the server (but you will loose DCI history), or you can set it to "Always" and restart the server. The third option - you can import that template manually (Tools -> Import Configuration), here's the file: https://raw.githubusercontent.com/netxms/netxms/master/contrib/templates/netxms_server.xml

The issue is fixed and will be available in 3.6 which will be released this week.

Thank You, I'll try this. Regards Stefan

Hi! It is likely bug in upgrade procedure. We've seen it on few systems but was not able to identify root cause. Just delete duplicate entries in object tool configuration. Best regards, Victor

With current API we need to set all fields related to propagation to modify anything there: node = session.findObjectByName("ttt") if node: md = NXCObjectModificationData(node.objectId) # copy existing properties md.statusPropagationMethod = node.statusPropagationMethod md.statusCalculationMethod = node.statusCalculationMethod md.fixedPropagatedStatus = node.fixedPropagatedStatus md.statusShift = node.statusShift md.statusTransformation = node.statusTransformation md.statusSingleThreshold = node.statusSingleThreshold md.statusThresholds = node.statusThresholds # new value md.statusPropagationMethod = AbstractNode.PROPAGATE_DEFAULT session.modifyObject(md) Also, it's possible to change propagation setting from NXSL, that should be easier and you can do this e.g. from interface creation hook. And it's also possible to change what the default settings are - it's set in Configuration -> Server configuration.

Thanks! I found neolog, it works nicely! I can even use event macro substitution (neolog's message part has to start with space, it's bug in that software). Regards

Dear Filipp, Thanks once more for providing the pointers. I tried some manual SNMP get requests via the CLI again, from our NetXMS server, and they were succeeding. I tried the full configuration poll once more, and it failed again. Next I started looking at the NetXMS full configuration poll and at the manual SNMP get requests in wireshark. I was filtering on the destination device IP and noticed that while the manual requests are successful, I only see the get requests when filtering my pcap on destination IP, I don't see the responses. Then it finally dawned on my: because these are L3 switches and the IP we use to manage them is in a different subnet, the L3 switches are sourcing their SNMP response from the IP they have in the NetXMS subnet. I need to solve this with some SNMP source configuration. So the last mystery was why are manual requests succeeding and NetXMS requests failing? It looks like the snmpwalk and snmpget from Net-SNMP are able to recognize the responses based on their query ID, even though the response comes from a different IP. NetXMS does not accept this, which is arguably cleaner and safer. Thanks again for helping me figure this out. This topic can be closed as the root cause is identified.

Hi, Filipp, thanks !

Thanks for the info. Currently i am trying to make few different versions of Mikrotik Winbox tool. Main difference is what user is being used and what ip is used to connect. I used to have custom attributes like username, password, winbox and externalip. That combined gave tools like winbox and winbox (external). But now i am moving to radius and i wanna use current logged in user name to connect, but for that i need to define new custom attribute like radius.

Hey, I take it back. I noticed, that UI didn't change at all and it seems, like in tomcat8 was cached old version of netxms. For future reference - removing content of tomcat/work/ resolved issue

nxdbmgr - NetXMS utility for database operations has built-in mechanism for database migration. nxdbmgr migrate <source> where source is the name of netxms configuration file that points to the database you are migrating from. There's a number of options that allow to skip DCI data, etc and it's possible to migrate DCI data afterwards after starting NetXMS with the new database. There's an outdated wiki post on that, it does not list all possible options: https://wiki.netxms.org/wiki/How_to_migrate_to_another_database

There's a big delay after "Checking SNMP..." line, which means that NetXMS is not getting any reply from the device. Try running snmpget -v 2c -c public DEVICE_IP 1.3.6.1.2.1.1.1.0 on NetXMS server - there should be some output. If there's none, please check community string and SNMP protocol versions supported by the device.

Hi! Peer manual specification is not possible now, i've created a ticket for that, but there's no exact schedule when this could be implemented. https://track.radensolutions.com/issue/NX-1973 As for adding inventory information to nodes that have no agent and no snmp - currently inventory is populated only by server and is read-only. As developer resources are limited, some manual way could be implemented only if someone requests paid developmet (or, possibly contributes a working code for this). Currently it's possible to store such information in custom attributes, but there's no way to display that information in the GUI. Or, alternatively it's possible to create a push dci on the node and use a script object tool that have input field and will update the push DCI.

Proxies should not be required, if your servers is able to communicate to these subnets directly. Passive discovery requires that there's netxms agent or SNMP agent on the remote machines - this way we are getting neighbors from arp tables (and not sure from where exactly in case of SNMP). For active scanning nodes should reply either ICMP, SNMP or netxms agent - if none is happening we can not discover a node. You can try temporarily increasing netxms server debug log nxadm -c "debug 7" and manually launching a scan of a subnet to better understand what's happening. Or, alternatively you can try capturing network traffic to that subnet with tcpdump, this can also give some insight.

Thanks for the follow up