NetXMS Support Forum

We have this information in Audit log, but if you need it in Event Log - there's Hook::login script in script library that you can use for that. Make sure that this script returns true, otherwise it will prevent users from logging in.

To see what attributes are available in this script you can try this - it will log details to server log:

for (a : $user.__class.attributes) trace(0, "$user." .. a .. " = " .. $user.__get(a));
for (a : $session.__class.attributes) trace(0, "$session." .. a .. " = " .. $session.__get(a));
return true;

Then you can use PostEvent() or PostEventEx() to create the event (https://netxms.org/documentation/nxsl-latest/#func-postevent), drop us a line if you need more help with scripting.

Can you do a tcpdump capture with this command:
tcpdump -s 0 -w snmp-exchange.pcap host = DEVICE_IP

We are interested in querying one problematic OID - first from nxsnmpget and then from NetXMS. Command will produce a file that can be opened using Wireshark. Please share the file.

Currently not supported, but theoretically it could be implemented to choose port number from a specific range. However, this is not good approach from security standpoint as if you are opening these ports to the Internet anyone else could have access to what's exposed on these ports.

More advanced way would be to use WebSockets so that browser would open a port on localhost, but this might be complex to implement and I am note sure if this fits with current framework on which the client is based.

Have you considered using some sort of VPN to access your server instead of a forwarded port?

C контроллерами поддерживаются Cisco, Symbol WS, Aruba, Avaya, но нужно смотреть подробности, может не все модели или еще что-то.

Ubiquity, Cambium, Mikrokik - отдельностоящие девайсы, не контроллеры. Они показыватся как ноды с объектами радиоинтерфейсов.

Ruckus - была попытка читать данные с контроллера по mqtt, поддержки snmp нет.

HFCL - были эксперименты по чтению кажется через web api, поддержки snmp нет.

В целом мы, насколько ресурсы разработки позволяют, заинтересованы в поддержки разных контроллеров. Если есть возможность на месяц-другой дать доступ к системе с контроллером и парочкой физичаских AP, то можно пробовать.

Hi,

Can you clarify a bit - are you using an object tool, or something else? Is it so that firewall on your webserver machine wants outgoing connections to be from port 443?

I've checked (but on 5.2. - token survived server restart. You can check if your token appears in auth_tokens DB table.

Currently not possible, i've created a ticket here: https://track.radensolutions.com/issue/NX-2887

First thing to check is how NetXMS Core Windows service is doing. NetXMS Core is the server process to which management client connects. Does it appear as "running" in Windows services?
If it's not, you can check it's log, it's typically in C:\NetXMS\log\netxmsd.log (you can check location in C:\NetXMS\etc\netxmsd.conf server configuration file). Log should give some insight in what's happening, may be it's waiting for the database or something.

Да, спасибо, ждут пока разработчик посмотрит

Бинарник Smartmontools у агента есть в комплекте.
А агент какой версии?

Мы наконец-то обновили доку:
https://netxms.org/documentation/adminguide/appendix.html#physicaldisk-smartattr

Вот скрипт который собирает информацию о тредах netxmsd: https://github.com/netxms/netxms/blob/master/tools/capture_netxmsd_threads.sh

В системе должны стоять пакеты netxms-dbg и gdb.

Скрипт нужно запустить 3 раза и интервалом в 20-30 секунд. Он сделает файлики в /tmp, пришлите их, можно в личном сообщении.

SMTP is configured in notification channels (https://netxms.org/documentation/adminguide/event-processing.html#notification-channels). If you right-click a notification channel in the list, there's "Send notification" menu item.

NetXMS YouTube channel has a few introductory videos, you may find these useful:

https://www.youtube.com/watch?v=J7rqkxJ3m50

https://www.youtube.com/watch?v=pz1cb5k-xtg

Сервер на Windows или Линуксе?

Here's the relevant part in agent log:

2025.11.24 15:34:51.846 *D* [comm               ] Incoming connection from 10.220.59.1
2025.11.24 15:34:51.846 *D* [comm               ] Connection from 10.220.59.1 rejected

Ah, looks like
MasterServers= 127.0.0.1/32, 10.220.59.1:4700, 10.220.59.8
in agent config is wrong, there should be no port number in it:
MasterServers= 127.0.0.1/32, 10.220.59.1, 10.220.59.8