NetXMS Support Forum

This is done by alarm keys. When you create "problem" alarm, you create event processing policy rule that do "generate alarm" and here you can set the key. For terminating you create another rule that handles recovery event and do "terminate alarm" with the given key. You can look at rules for SYS_NODE_DOWN and SYS_NODE_UP events.

Best regards,
Victor

P.S. Questions like this have much more chances to be responded quickly if placed into correct section on forum. "Development" section is intended for developing of product itself or using it's APIs, so many users simply never look at posts there.

Это баг в NXSL интерпретаторе, уже починили. В следующем релизе будет работать.

https://adoptopenjdk.net

Can you get lsof output before and after action execution and check for possible new entries? And if there will be new entries, please post them.

Are you using TCP proxy functionality?

I was unable to reproduce this issue so far. What kind of actions and/or external parameters you are using? Can you share your agent configuration file?

Best regards,
Victor

Starting with version 3.7 Java 11 is required for both desktop and web console.

Best regards,
Victor

Hi,

log viewer has also limit on number of records retrieved in one request. You can press "get more data" icon in log viewer to get next batch. Unfortunately this limit is hard coded and cannot be changed.

Best regards,
Victor

Quote from: Denis on January 26, 2021, 04:00:17 PM
Добрый день sergey_t. Удалось починить отображение VLAN?
У меня схожая проблема, коммутатор 3Com 4210 26-Port, ставлю 78 vlan на 1 порт, в интерфейсах 78 vlan появляется на 8 порту.
Драйвер H3C.

А если поставить на второй порт, он не появится на 7? Возможно битовая маска зеркальная на каких-то моделях, или же драйвер ее некорректно обрабатывает.

Еще если у кого-то есть возможность дать мне удаленный доступ по SNMP к такому коммутаторы это бы сильно помогло в отладке.

It looks like pipes are not closed ater command execution (maybe if certain conditions are met). We will investigate it further.

Best regards,
Victor

Hi all!

We just published NetXMS server version 3.7.145. It fixes single bug in interface and subnet hook scripts processing. Only server is affected.

Best regards,
Victor

Hi,

NetXMS version 3.7.144 is just published. This is patch release that provide few fixes and improvements. Only server and UI components are affected. Full change log:

- Target for event processing policy remote action can be given as node object ID
- Added agent parameters Agent.TCPProxy.IsEnabled and Agent.TCPProxy.ConnectionRequests
- Fixed bug in agent action execution from event processing policy
- Fixed incorrect boolean values handling in NXSL
- Fixed bug in "Find switch port" tool
- Fixed server crash when connection to agent is slow or unstable

Best regards,
Victor

Also, please enable debug level 4 for tag obj.poll.node and show log file during discovery (there should be lines started with text AcceptNewNode).

Best regards,
Victor

Hi,

you can develop custom notification channel driver or order one from us. I didn't check their APIs but likely can also use command actions to call their HTTP API via curl or something similar.

Best regards,
Victor

Hi,

we have TOTP authentication planned, should be added in one of next releases.

Best regards,
Victor