NetXMS Support Forum

You can try to run agent with DebugLevel = 6 in it's config - actual query and detail of execution should be visible in the log. Pls share the log part related to execution of the query.

Nice to hear that

Problems with compilation are probably because libcurl library is now used for a few things, smtp in particular. But it's better just to use packages.

You can install netxms packages right on the same system, just remove systemd unit or whatever way the old server and agent were started by.

nxagentd.conf will be in /etc, currently it's probably the same
server files, images are under /var/lib/netxms/, if compilation was with default prefix, then currently it's same location
and the database, with which new binaries will work same way and the old ones


Export-import is also possible, this will export all the configuration, without logs and collected data:

nxdbmgr -s -Z all -e hardware_inventory -e software_inventory export backup.sql

And to import on the new system:

nxdbmgr import backup.sql

And you'll need to copy conf file and folders I've mentioned above. 

Any reason why you compile it yourself? We have packages for Ubuntu.

What's exactly happened? Is the driver gone from the list? What is it's status and error message in the list?

To debug what's happening with the driver you can increase debug level: In Tools->Server Debug Console issue
debug ncd.* 7
this will enable debug for notification channel drivers. Then try to send a message and check server log

You can try setting custom attribute snmp.driver to value ARUBA-SW on the node.

Chances are that current Aruba driver does not support your devices. Pls update on the results.

I've added chapter to the docs describing it: https://netxms.org/documentation/adminguide/user-management.html#ui-access-rules

Да, возможен, из LDAP можно синхронизировать как юзеров, так и группы, просто LDAP.SearchFilter нужен такой, чтоб возвращал и то и то.
В NetXMS группы могут быть членами групп, так что это как раз правильный подход - есть локальные группы в NetXMS на которые расставляются права доступа и в эти группы добавляются LDAPные группы.

Hi,

The reasons for this are not clear for now. Can you show screenshots of Interfaces tab and VLANs table from Ports tab (you can PM this to me if needed)

Just set Server.ImportConfigurationOnStartup in Configuration->Server Configuration to Never. 

Yes, racks now have scaling limit so that units don't become too small. Looks like this is not ideal for dashboard use, I've created a ticket to improve that: https://track.radensolutions.com/issue/NX-2738

It's more a question for Mikrotik forum. Or you can also try to ask in our NetXMS support Telegram channel - may be there's someone with relevant experience.
I'd do full walk from .1 to look through all the oids. Another option could be to use ssh monitoring, if this value can be requested from Mikrotik's command line.

That's a bug, fix will be in v. 5.2 which should be out quite soon

You can try deleting 105.10.10.0/30 subnet object. Then run configuration poll on the device - subnet should be recreated again. 

In overall it's not recommended to increase Agent.CommandTimeout too much (like > then 5 seconds) because in situations when agents are slow to respond server will spend too much time waiting. 
If your query takes too long, you can use External metric provider - in this case command is executed in the backgound and agent caches values. https://netxms.org/documentation/adminguide/agent-management.html#externalmetricprovider