NetXMS Support Forum

Hi,

it's already fixed in version 2.1-M1. This fix is also included into upcoming 2.0.8 patch release.

Best regards,
Victor

What version of NetXMS you are using? At some point there was a bug when IP address was inverted. Just in case, try to specify destination server address as 42.228.19.172.

Best regards,
Victor

Hi,

make sure that destination server listen on port 4702 and that port is reachable from source server (not blocked by firewall, etc.). "Connect failed" indicates that source server was unable to establish TCP connection.

Best regards,
Victor

Зависит от того, где находятся нужные данные. Можно вызвать скрипт через макро %[], и в скрипте считать необходимые данные например. Если что-то выставлено в custom attributes у ноды, то значение атрибута можно подставить через макро %{}.

Just one comment: code block


if (found_process == true) {
  return true; // process has been found
} else {
  return false; // process has not been found
}


could be replaced with simple


return found_process;


Best regards,
Victor

Fixed in version 2.1-M2.

Best regards,
Victor

Hi,

yes, default auth method changed from PAP (the only one supported before) to CHAP. You can change it back by setting server configuration parameter RADIUSAuthMethod to value PAP.

Best regards,
Victor

Ну результатом все равно является событие. Вот в шаблоне этого события и можно использовать скрипт через %[] для подстановки текста вместо цифрового значения.

Можно сделать скрипт - либо трансформации, если это значение DCI, либо в библиотеке скриптов и вызывать через макрос %[] для подстановки в текст сообщения.

Another note on having external IP address from router set as primary address for proxy node - you can try to set option "This is address of remote management node" in communications options for proxy node. That way server will not consider primary IP part of proxy node.

Best regards,
Victor

This option intended for direct receiving of syslog messages and SNMP traps from nodes in other zones. When it is on, server ignores zone ID provided by proxy and do match only based on source IP address. This option can only be turned on if you have unique IP addresses of trap/syslog senders across all zones. For non-unique addresses you have to use zone proxies.

Best regards,
Victor

Hi,

currently the only way is to use transformation script to filter out impossible values (usually they happen when counter is reset). We plan to improve this in one of next releases.

Best regards,
Victor

Also, could you please post complete agent config (from proxy node)? And what is server version?

Just in case - please check that server parameter TrapSourcesInAllZones is set to 0.

Best regards,
Victor

Hi,

"Force poll" for push DCI is meaningless, but it definitely should not change state to "not supported". I've registered it as a bug (https://dev.raden.solutions/issues/1366).

Best regards,
Victor