NetXMS Support Forum

Hi,

currently it's not configurable. Feel free to enter appropriate feature request into our tracker.

Best regards,
Victor

Hi all!

NetXMS version 2.0.8 is out. It is final patch release for 2.0 branch. Changes since 2.0.7:

- Fixed response parsing in MyMobile SMS driver
- Improved HP ProCurve driver
- Fixed high CPU load on FreeBSD
- Event sending by agent do not restricted to master servers only anymore
- Default RADIUS authentication method set to PAP to maintain compatibility with older versions
- Fixed issues: #1258, #1311, #1314, #1351, #1352, #1357, #1376

Best regards,
Victor

Hi,

agent installer is build using InnoSetup. There is MSI wrapper that can wrap installer exe into MSI suitable for GPO deployment - http://www.exemsi.com/inno-setup-and-msi, although I didn't try it myself. You may need to specify installer options for unattended installation - they described here: https://wiki.netxms.org/wiki/Agent_Installation_Guide#Unattended_installation_of_NetXMS_Agent_on_Windows.

Best regards,
Victor

Hi,

in map options (map object properties -> "Map Options" page) turn on "Include end nodes" checkbox.

Best regards,
Victor

Hi,

simplest way is to define instance discovery DCI with SNMP based discovery:

1. use parameter name .1.3.6.1.4.1.14988.1.1.3.8.{instance}
2. set origin to SNMP
3. set instance discovery method to "SNMP Walk - OIDs"
4. set base SNMP OID to .1.3.6.1.4.1.14988.1.1.3.8
5. leave filter script empty

Such instance discovery DCI will create single instance .1.3.6.1.4.1.14988.1.1.3.8.0 when it is supported and will not create anything when it is not supported.

As for .1.3.6.1.4.1.14988.1.1.1.4 - you should use .1.3.6.1.4.1.14988.1.1.1.4.0 as parameter name (you can see full OID in walk result).

Best regards,
Victor

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