NetXMS Support Forum

Да, таки в разные документы, у нас тут инфраструктура в процессе переезда.
Вот в этом коммите видно то что должно появиться в доке:
https://github.com/netxms/netxms-doc/commit/d5dc8c519edabffab11ed39965e617e597184e1f

In case of SQLite database login and password is not used. There is no need to check "Create database and database user before initialization". Just fill in "Path to database file", folders in that path should exist after installer finishes extracting files, so C:\NetXMS\server.db should be fine. NetXMS will create the database automatically.

And you don't need to run installed again, you can just put this into netxmsd.conf:

DBDriver=sqlite.ddr
DBName=C:\NetXMS\server.db

And run
nxdbmgr init
this should initialize the database.

For APs that work with a controller the process is that controller node is added to a wireless domain. Then all APs that are found on that controller should appear under that wireless domain.

Current situation is the following:

Ubiquity - only airMAX stand-alone devices are supported, these just appear as nodes.

Ruckus - there's a prototype driver which gets information from controller via mqtt, but we would be interested in development of SNMP driver.

Meraki - no support.

It looks like, in your case, new drivers would need to be developed to obtain more monitoring information. Would you be interested in a quote? We can prioritize this work within our custom development services, and it would take roughly two days. If you're interested, please send a note to [email protected]

In 5.2.7 Windows client F9 and Shift+F9 work for me for these.

Yes, shortcuts were reworked (and something still may not work). F2 is typically a "rename", so that's what it now does in object tree and all executions (script, object query and log) are on F9

Вот тут описано, есть как single value метрика, так и листы
https://netxms.org/documentation/adminguide/appendix.html#list-of-supported-metrics

Agent has a copy of unzip that gets installed into C:\NetXMS\bin and we can add this to agent's config

[ENV]
PATH=%PATH%;C:\NetXMS\bin

so that agent would be able to run this unzip binary, but then there's another issue as agent puts parameters for unzip in single quotes and unzip does not like that.

I've created a ticket for all this - https://track.radensolutions.com/issue/NX-2862.

Currently you can make a self-extracting binary and ship is as executable package. Or may be you can just put the .zip file and set it as executable and then in Command field you can put the actual unzip command, file location will be in ${file} macro.

Но этот запрос в базу нужно делать при остановленном сервере.

Попробуйте, пожалуйста, на 5.2.7, там был один фикс на тему дискавери (https://track.radensolutions.com/issue/NX-2594)

Pls try to run the agent in the foreground mode:

nxagentd -D 6

In this mode it should put it's log right to the terminal. Pls share the output

Pls try to put
DebugLevel = 6
into agent configuration file and collect logs for the moment when the package is being deployed.

There's now Package Deployment Job under Configuration.

а это время в 5 минут - оно в свойствах экшна настроено?

какая точно версия NetXMS?

можете показать для такой ситуации event log, отфильтрованный по двум нодам - прокси и какая-нибудь одна нода, которая за этой прокси? По идее события автоматически должны кореллироваться на SYS_NODE_DOWN этой прокси, но возможно что-то поломано.

Hi,

On which exactly version is this?

Pls show screenshots of
- Active discovery targets in Network Discovery
- Communication page from properties of the zone object (under Entire Network)

Yes, just do a full snmp walk starting from .1  You can upload the output to here https://cloud.radensolutions.com/s/SHniBXHz5PJKpeR (file won't be visible on the web page once upload is complete, but it will be there). Drop us a message when it's uploaded.


Also please share relevant MIB files.

можно запустить сервер на 6 уровне дебага, можно не через systemd, а просто из командной строки

netxmsd -D 6

он тогда будет лог в консоль писать.

Один из вариант почему так бывает - когда в системе очень много алармов, т.к. они все подгружаются при старте сервера. Это можно проверить и сейчас, не останавливая сервер, выполнив

sh st

в Tools->Server debug console