NetXMS Support Forum

Есть два пути - собирать из исходников или скачать уже собранные бинарники.
В документации по NetXMS описан первый путь, давайте по нему и пойдем https://www.netxms.org/documentation/adminguide/installation.html#id9

Скачиваем архив с исходниками - https://www.netxms.org/download/releases/3.0/netxms-3.0.2305.tar.gz
Разархивируем в любую директорию - когда мы соберем бинарники, исходники можно стереть, так что не важно где они находятся
Для ./configure и make рут не нужен - эти операции происходят в нашей временной директории, не затрагивая системные директории

Если столкнетесь с ошибкой, процитируйте полностью текст ошибки.

Hi!

Looks like a bug when formatting texts drawn on links on that map. Could you please check what ID that map has - it's visible in Object Details when you click the map in Object browser and share output of the following SQL query:
select * from network_map_links where map_id = 123;
where 123 is the id of your map.

Hi!

Yes, paid support is provided. Please send a request to [email protected]

There we changes with internal parameters - in version 3 PingTime was deprecated and a number of ICMS.ResponseTime. parameters were introduced that provide much more options.
Please try to replace PingTime with ICMP.ResponseTime.Last in your template.

You can clone NetXMS repository on github: https://github.com/netxms/netxms

What NetXMS version are you using?
In 3.0 there is Prevent automatic SNMP configuration changes checkbox in SNMP communication properties that should prevent NetXMS from trying the default port.

Since version 3.0 macros can be used in threshold's Value field. Particularly, this allows to use scripts in thresholds by creating a script and referencing it with %[script_name] macro. This way you can do all the customization in your script.
UPD:
More correct way would be to set threshold Function = Script and use a script this way. If script returns "true" it means, that threshold will get activated. Contents of "Value" field can be accessed from the  script. 

Currently, as of 3.0, it works that way, that as soon as you create a node, Full configuration poll is being done. If server is not able to ping AND connect to agent, the node will be marked at unreachable and the only thing that will remove unreachable flag and initiate communications is to manually run Full configuration poll  again.
The thing is that after node creation, while user goes to properties of a zone to set that node as a proxy, the node gets unreachable. There is a way to create a node in a zone and set it as proxy for that zone in one step - in new node creation there's a checkbox "Create as zone proxy for selected zone". It's among other checkboxes and is easy to overlook. There are thoughts to improve user-friendliness of all this.

As for ZoneUIN parameter - as far as I know, it's related to SNMP Traps and Syslog monitoring; also it's used when tunneling agent connects to server so that server could auto-assign node to correct zone. Proxy should work without this parameter configured.

Hi!

I was not able to reproduce this. What kind of communication are you using with the proxing agent - direct connection to it from the server or agent tunnel (agent to server communication)?
When you moved the agent from zone 1 to zone 2, did you do Status poll or tried Full Configuration poll?

Это скрипт на языке NXSL, который используется в NetXMS в качестве внутренного скриптового языка.
Если щелкнуть правой кнопкой по любой ноде, там будет пункт "Execute server script". Туда закопипаcтить код и нажать F2.