NetXMS Support Forum

In node properties -> Communicaitons there is checkbox "Communication through external gateway". If set, NetXMS will know that this is a forwarded port.

Try opening MIB explorer on this device, expanding [root] in the three and performing walk on "iso" which is under root. Will there be any values there?

Check properties of interfaces - there is expected state which is by default it set according to how interfaces were when device was polled for the first time. If you set expected state to "ignore", alarms should not be created.

Начиная с какой-то версии ноды, к которым применен шаблон не показываются в дереве объектов под этим шаблоном (но по факту шаблон у нод остается родительским объектом и туда наследуются custom attributes например). У шаблона теперь есть закладка targets где должно быть видно, куда шаблон наложен. 
При наложении на infrastructure services видимо так кроме нод были еще какие-то другие объекты и из-за этого возникла ошибка.

А, у нас веб страница не обновлена, самую свежую версия WAR файла можно взять тут:
https://netxms.org/download/releases/4.4/

День добрый,

для начала нужно проверить, какая версия сервера, выполнив
netxmsd -v

Ну и на всякий случай перезапустить сервер
systemctl restart netxmsd
чтоб не было ситуации, чтоб бинарники уже новые, а в памяти все еще работает сервер старой версии.

Для проверки можно поставить десктопного клиента и посмотреть, можно ли подуключиться из него

You can try using https://github.com/netxms/nxmc-web-launcher - it should build one .jar that contains web UI and Jetty 10.

Just in case - how many alarms do you have on your system? (can be checked by issuing
sh st
in Tools -> Server Console

Hi!

Most convenient way to achieve this is if you have your interfaces set as Related Object ("Other options" tab in DCI's properties). Related object is automatically set, if you create your DCIs from context menu of interface(s). Or you can set it manually. Or if you use instance discovery to create your DCIs, Related Object can be set from instance discovery filter script.

Then, in Transformation script of your DCI you can use
return $1 * 8 / $dci->relatedObject->speed;and your threshold should be "last polled value > 90", samples: 5.

There is currently one drawback of this approach - to work with traffic counters, DCI type should be Counter32 or Counter64, and the resulting percentage will be integer (it will be seen as float in last values, but will be integer in history and graphs).
You can have another float DCI with push source and push values from transformation script of the first DCI.
Or just wait for this issue to get resolved: https://track.radensolutions.com/issue/NX-2371 - you can watch it in the bug tracker to get notifications.

Feel free to ask any additional questions.

Hi!

I've tried on my system, everything works as intended.

Just in case, check that there is no other rule that could be interfering with that timer.

You can check in Configuration -> Scheduled tasks. If you enable showing of system tasks (under three dots menu), during your 120 second delay an entry should be visible with correct value in "Timer key" column.

You can also set debug level 7 for debug tags
event.*
scheduler
to monitor event processing and scheduled task execution in server log

I assume you are installing on Windows.
Check NetXMS configuration file C:\NetXMS\etc\netxmsd.conf - it should contain database credentials for your database. Change these credentials is needed to match your database.

Right, I forgot about that checkbox. Actually, it's not strictly necessary, without it you can still open the dashboard from "Dashboard" menu on a node (we will rename this checkbox somehow to demonstrate that it just opens dashboard in a tab by default).

Yes, {} characters are interpreted as part of regular expression. These fields will be renamed, e.g. "DCI name regular expression" to give more understanding.

There is context dashboard functionality, added quite recently, somewhere in 4.x. It could be that it could be improved to be simpler to use, comments are welcome.


If you open data sources of dashboard element, there is button "Add template". There you can specify how to choose what DCI to display - by metric name or description.

The second step is to apply dashboard to a node. This could be done either by auto-apply script in dashboard properties, or manually in properties of a node.

I was not able to replicate this. What kind of ID do you have in m variable, is it decimal number or hex?

I'd try a few things:

- executing this script via "Execute server script" from node context menu. May be you'll see some errors there.
- you can try removing the dot from the beginning of custom attribute name - in this case custom attribute will be visible in node properties. Does setCustomAttribute actually add custom attribute to the node?