NetXMS Support Forum

А какая версия сервера? Но expandString должен работать, поскольку иначе была бы ошибка в той строке.
Попробуйте еще в trace добавить результат expandString, и потом сравните в аларм логе что ключ действительно совпадает с алармом.

Похоже что аларм не находится - в этом и проблема. Покажите пожалуйста как сейчас выглядит правило.

Hi all!

NetXMS patch release 4 (version 3.2.462) is published. This patch only affects server component. It fixes single issue with thread pool manager that can cause start of excessive number of threads in thread pools. All other components can stay on version 3.2.451.

Best regards,
Victor

Hi,

could you please provide output of SNMP walk for the following OIDs for this device:

.1.3.6.1.2.1.4.20.1
.1.3.6.1.2.1.4.34.1
.1.3.6.1.2.1.4.32.1
.1.3.6.1.2.1.2.2.1

Best regards,
Victor

Ну да, я не подумал что аларм сбросится в outstanding на повторном событии. Тут два варианта решения:
1. Сделать такой-же фильтр для генерации алармов - т.е. событие будет просто игнорироваться если аларм уже есть. Тогда можно отсылку нотификации и генерацию аларма объединить в одно правило. Единственный недостаток - счетчик повторов у аларма не будет увеличиваться.
2. Использовать "sticky acknowledge" вместо "acknowledge" для аларма - sticky состояние не будет сбрасываться обратно в outstanding.

В аттаче пример правил. Первое правило отсылает сообщение если аларма с заданным ключем нет или он в состоянии "outstanding". Второе правило создает аларм с ключом (или обновляет существующий если аларм с таким клячем уже был).

One possibility is to change interface naming in netxms. You can do that either in configuration poll hook or by using interface name templates. If interface object names will match then topology builder should puck them up correctly. You can use macro that calls a script and replace ETHERNET PORT n with just PORT n.

Best regards,
Victor

Hi all!

We just published NetXMS 3.2 patch release 3 (version 3.2.451). Changes since previous patch release:

- Internal parameters for monitoring syncer performance (Syncer.RunTime.*)
- Improved notification handling in user support application
- Allow usage of chat ID as recipient address for Telegram
- Support for standard SSH configuration file in SSH subagent
- Environment variables from agent configuration file also set for user agent processes
- Improved hypervisor type detection by agent
- Tunnel option can be turned on in Windows agent installer
- Fixed issues with hardened file system permissions in Windows installer
- Added SMBIOS parameters support on FreeBSD
- Fixed issues:
        NX-1635 (Log parser can skip lines in a log file)
        NX-1737 (User Agent Startup and Recurring Notifications not working)
        NX-1810 (Server can cash if scheduled task deleted while running)
        NX-1812 (In the WebUI Filter in Alarm browser hiding column headers and first row when resized)
        NX-1814 (Values of internal parameters Server.QueueSize.Average and Server.QueueSize.Current are inconsistent)
        NX-1815 (FDB cannot be read on certain Cisco switches)
        NX-1816 (Removing node from cluster crashes server)
        NX-1817 (Log file can be read twice after rotation by log parser on Windows)
        NX-1819 (NXSL methods NetObj::bindTo() and NetObj::unbindFrom() crash server when given null as parameter)

Best regards,
Victor

Just checked that exact file - works correctly with server 3.2.400. When you are on login screen, what version is displayed in bottom right corner?

Best regards,
Victor

SSH proxy setting determines which node will establish actual SSH connection. If you are using source node then server will read SSH settings on that node, not on a node where DCI is configured (because connection goes to source node, not DCI owning node).

Currently there is no way to set different source nodes from template. What you can do it to use script DCI instead of SSH DCI, and in script code identify correct source node and call executeSSHCommand on it.

Best regards,
Victor

Hi,

make sure that other UPS software is not running when you try to monitor it via agent - otherwise COM port could be in use and agent may not be able to use it.

Best regards,
Victor

It could also be bug in deduplication (when server decides that two nodes are in fact represent same device and deletes one of them). You can try to turn deduplication off by setting configuration parameter NetworkDiscovery.MergeDuplicateNodes to false. Also, try to set debug level to 6, create node, wait for it to disappear, and show log file filtered by that node name.
Also, try to execute command on debug console

show object name

replacing nme with actual name of disappeared node.

Best regards,
Victor

Those lines won't have switch name, only "FDB" prefix.

idata_sc* tables are only needed for TimescaleDB deployment, so it definitely is export bug.

As for disappearing nodes - do you have any SQL errors in server log?

Best regards,
Victor

Hi,

most likely there is some DLL conflict. I'll try to check if all dependencies for pgsql.ddr were added to installer.

Best regards,
Victor