NetXMS Support Forum

Seems fine. Make sure you have "LogFailedSQLQueries=yes" in netxmsd.conf (it's enabled by default) and check log file for failed queries.

Выложил ipk: https://www.netxms.org/download/ar71xx/, проверьте пожалуйста.

Выложил ipk: https://www.netxms.org/download/ar71xx/, проверьте пожалуйста.

It should save in both cases. All data is saved into DB by separate thread (so server can collect and process data) — check value of "Database writer's ..." DCIs on the server node, if it's too high — your DB can' handle load.

Hello.

No, you need to restore DB from backup.

It's generated internally, when server can't reach node via any allowed channel (ICMP, Agent, SNMP)

Easiest way is to have a rule in a event processing policy which silently ignores SYS_NODE_DOWN during off-hours.
Check attached screenshot for sample configuration.

Please note that this EPP is processed from top to bottom and by default all rules are processed (unlike "first-match-win" in thresholds), so this rule should be above any other SYS_NODE_DOWN related rules.

Description of "TIME" structure (returned by localtime()): http://wiki.netxms.org/wiki/NXSL:TIME

Update: script should be like "if (now->hour >= 20 || now->hour <= 8) ..."

Quote from: Dani@M3T on January 27, 2014, 01:48:55 PM
For me the question is, what triggers the SYS_NODE_DOWN event. The default DCI 'status' has no threshold configured.

Сложно сказать. Я советую заменить субагент portCheck на netsvc и использовать Service.Check(https://inside.test.ru/,^HTTP/1\.[01] 200.*). Если субагента netsvc нет, проверьте, что стоит пакет libcurl-dev и пересоберите агента.

P.S. регексп "^HTTP/1\.[01] 200.*" можно не указывать, это значение по умолчанию.

Currently there are no out of the box solution for that. We plan to make new new object class - "Management Board", but it's yet to be implemented.
As partial workaround, you can create second node for iLO, unbind it from "Infrastructure Services" (it will be visible only in "Entire Network", and then create iLO-related DCIs on the server node, using a proxy. Sample configuration is attached.

To make this work (proxy), you need either add server node to the list of trusted on iLO, or disable trust check completely.
To add it, open iLO properties, select "Trusted Nodes", click "Add" and select Server node.
To disable it completely, open Server Configuration and set parameter "CheckTrustedNodes" to 0.
Some info about "Trusted Nodes": http://wiki.netxms.org/wiki/SG:Security_Issues

Right click on the template, select "unbind", and then select node(s) you want to remove.

Could you please describe ways you've tried, so we can analyse them and possibly implement in future releases?

Мой ответ был больше про промежуточный сислог; по изначальному вопросу — я бы проверил tcpdump-ом, возможно там что-то не стыкуется в адресах, или еще что-то.

Check that you have data for both DCIs (inbound / outbound traffic) on "gw...": select "Object Details" -> Last Values -> right click on item and select "History". Make sure that timestamp is correct.

Hello.

It's already in progress and we plan to release it in version 1.2.12 — somewhere around mid-february.

Нормальных способов мне в голову не приходит, только накручивать какие-то костыли вокруг ssh тунелей или connection proxy (если на ноде с агентом есть sshd). Неплохая статья (и линки в начале статьи): http://mikelococo.com/2008/01/multihop-ssh/

Постараюсь выложить в ближайшие несколько дней

Судя по документации, rsyslog умеет спуфить адрес для UDP: http://www.rsyslog.com/doc/omudpspoof.html