NetXMS Support Forum

Hi,

I just created clean system, added new zone, single node as proxy in it, and passive discovery works as expected. Below are screenshots from my configuration (and you can see object tree in zone "Test" being populated with devices).
Could you please make clean system again, set debug level to 6 on both agent and server, add only proxy node, enable passive discovery, and send me server an agent logs?

Best regards,
Victor

Hello!

Currently log parser cannot expand single <file> entry into multiple files. You can use timestamp macros or external scripts to monitor files with changing names, but not changing set of files simultaneously.
You can safely ignore <logName> tag. It is purely cosmetic issue - instead of omitting it altogether if not set (as with other tags) code that generates XML always put it. This tag can be used to specify Windows event log name to filter by specific log (useful for Windows event synchronization).
Macros section moving to the bottom is a bug - we will fix it.

Best regards,
Victor

Hi!

I will try to reproduce this on my test system tomorrow - but it definitely looks wrong. Passive discovery should go in a same way as for local zone. Can proxy agent read local ARP cache and is there anything to be used for discovery? You can check that by selecting "Execute server script" on proxy node in UI and running the following script:

for(line : $node->readAgentList("Net.ArpCache"))
   println(line);

It should print some lines with ARP entries.
Am I understood correctly that proxy node is in zone 1, not in default zone (it is how it should be)?

Best regards,
Victor

Yes, that's actually a problem - executeSSHCommand uses SSH settings from node it is called on, and it is actually not possible to set SSH port for node.
In NXSL workaround is to use agentReadList - all that executeSSHCommand does is reading agent list with necessary arguments (properly escaped). But it has to be fixed anyway - SSH port for node definitely should be configurable, and maybe optional port number, login, and password arguments can be added to executeSSHCommand.

Best regards,
Victor

Hi,

port can be specified as part of host name after : character. This is relevant piece of code from SSH subagent: https://github.com/netxms/netxms/blob/819a9418773ce2fe4b5589397a70716d736c652e/src/agent/subagents/ssh/handlers.cpp#L39

Best regards,
Victor

Quote from: Zebble on December 28, 2020, 08:14:28 PM
Before I forget to ask, are passive discoveries possible through a proxy as well?

Yes, but you have to enable SNMP proxy in agent (by adding EnableSNMPProxy = yes to core section) and you must use zoning, with this agent set as zone proxy.

Best regards,
Victor

Hi,

try to check with lsof how many file descriptors actually open. It could be descriptor leak. Also, are you sure that your changes in open file limit actually reflected on nxagentd process? If it is being started with systemd you may need to make changes to unit file.

Best regards,
Victor

Hi,

there is open change request for that: https://track.radensolutions.com/issue/NX-1826. Hopefully will fix it soon.

Best regards,
Victor

Can you please provide agent log on debug level 7 (after initiating active discovery range scan)?

Best regards,
Victor

Hi,

latest agent versions do store syslog records and SNMP traps in local database (since version 3.4).

Best regards,
Victor

Hi,

this is a bug that cannot be solved easily. Object tool filtering for displaying in context menu is done on client side. If client application does not have access to templates it cannot check if node is in that template or not. This can be solved by sending filtering request to the server, but that will require round trip to server on each right click on object (possibly combined with some sort of caching and push notifications from server when template membership changes) - this can significantly slow down UI.
Alternative approach for such filtering could be by using custom attributes - you can use configuration poll hook to set custom attribute for each parent template and then in object tool check for those custom attributes.

Best regards,
Victor

Most likely it is caused by bug we have fixed recently in development branch. Fix should be included into upcoming 3.7 release.

Best regards,
Victor

Currently client does not have built-in terminal emulation to run interactive command line tools like putty inside GUI. It is quite complex task to implement (especially on Windows).

Best regards,
Victor

Looks like the following query fails silently:

ALTER TABLE event_log RENAME TO event_log_v35_2;

Which is very strange. You can try to run nxdbmgr upgrade with -t option, it will print all SQL statements being executed. This particular upgrade procedure is indeed TimescaleDB specific.

Best regards,
Victor

Скорее всего устройство просто отдает интерфейсы в таком виде. Попробуйте сделать SNMP walk на ветки .1.3.6.1.2.1.2.2.1 и .1.3.6.1.2.1.31.1.1.1 - какой будет вывод? Можно сделать командой nxsnmpwalk или в GUI открыть MIB explorer на ноде и сделать walk оттуда.