NetXMS Support Forum

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

Quote from: Pavel on December 08, 2020, 05:37:05 PM
Доброго дня.
Подскажите, как наиболее правильно сделать такую, в общем-то простую вещь:
Когда сервер запустился - на почту отправляется письмо с текстом "сервер был запущен в такое-то время"

Можно обрабатывать событие SYS_SERVER_STARTED и отсылать почту. При помощи макросов можно добавить текущее время.

Hi all!

New patch release for NetXMS 3.7 (build 3.7.130) is just published. Changes since previous patch release:

- Per node SSH port configuration
- New user properties "email" and "phone number"
- Fixed broken reporting server connector
- Fixed issues:
        NX-1081 (Some devices are not detected correctly by CATALYST-GENERIC driver)
        NX-1663 (NXSL function GetDCIValue should read value from database if cache is not populated yet)
        NX-1965 (Inconsistencies in address range add/edit dialog)

Best regards,
Victor

At least one Nexus user reported is as fixed, so probably yes (we were unable to reproduce it locally).

Best regards,
Victor

Hello!

Probably easiest way is to create two rules in event processing policy, one for critical nodes and one for everything else, and set different severity to generated alarms. See attached screenshot for an example.

Best regards,
Victor

It's strange - there are no errors on either side, server reports normal connection closure:

2020.12.16 16:35:57.592 *D* [client.session.0   ] readSocket: connection closed

Timestamps are also quite old and not in sync between server and client - do you have correct time on server and client? If yes, are those logs latest for version 3.7? Also, are they in same time zone?

Best regards,
Victor