NetXMS Support Forum

Hello,

I tried to reproduce this issue with latest agent, but it works as expected for me. Are you sure agent used as a proxy for SSH connection was upgraded to 4.0.2157? If yes, please try to set debug level to 8 and send me excerpt from the log around request for parameter SSH.Command.

Best regards,
Victor

Hi all!

We just published new patch release for version 4.0 - 4.0.2227. Changes since release 4.0.2157 (some were already included into 4.0.2200):

- NXSL hook script for user login
- SSH subagent metric SSH.Command returns collection error instead of "unsupported metric" if host name cannot be resolved
- Fixed bugs in IP topology map builder
- Added action to open object detalis form Business Service checks
- Alarms for unknown nodes are not included in summary e-mails
- Fixed bug with threshold recreation on any DCI change
- Fixed issues:
        NX-2214 (Agent does not report network interface speed)
        NX-2227 (Typo in message for event SYS_DUPLICATE_MAC_ADDRESS)
        NX-2235 (Object Query CSV export does not prompt to overwrite .csv file)
        NX-2236 (Option of copying of data from an Object Query in Dashboard view)

Best regards,
Victor

Можно сделать external parameter с аргументами, куда передавать IP адрес принтера например, а затем на нодах принтеров сделать нужные DCI и указать SERVER как source node.

Например:

1. агент на SERVER:

ExternalParameter = PrinterState(*):get_printer_state.sh $1


2. DCI на ноде принтера:
Name: PrinterState(10.0.0.1)
Origin: agent
Source node: SERVER

в результате сервер запустит скрипт
get_printer_state.sh 10.0.0.1
на ноде SERVER и результат поместит в DCI на принтере

Действительно не работает. Только что исправили, в следующем патч релизе будет работать.

Перепутал немного, называется "translucent":

Try using utf-8, it could be issue with character set transformation internally. Most mail clients should understand utf-8 encoded emails correctly.

Best regards,
Victor

Hi,

you can turn off automatic layout for map by right click - selecting "layout" - unchecking "enable automatic layout".

Best regards,
Victor

Hi,

try using

ActionShellExec = kill_qv:c:\NetXMS\batches\kill_qv.bat

in agent configuration file.

Best regards,
Victor

Yes, you are correct - it is interval between instance discovery polls. You can set it to larger value without missing anything else.

Best regards,
Victor

Quote from: hayarm on March 21, 2022, 03:14:42 PM
Здравствуйте, поменялись цвета в графах,  не совподает с выбранным.

Там полупрозрачная заливка, попробуйте убрать опцию "transparent" в свойствах графика.

Hi,

in version 4 SMTP was re-implemented as notification channel, and I suspect that there is a bug in configuration conversion. Could you please share configuration for SMTP channel on your system?

Best regards,
Victor

Hi,

you can create object tool that will execute NXSL script, and use SNMPSet function or set method in SNMP transport object (see reference here: https://www.netxms.org/documentation/nxsl-latest/#func-snmpset).

Best regards,
Victor

Yes, you can add element of type "object tools" - it will display button for each configured tool and execute it when button is pressed.

Best regards,
Victor

It will be there, just not moved from old UI yet.

Best regards,
Victor

Hi,

there are two independent polls that produce those two events. One is status poll, that checks node connectivity using agent, SNMP, and finally ICMP if neither SNMP agent nor NetXMS agent are responding. This poll can generate events SYS_SNMP_UNREACHABLE, SYS_AGENT_UNREACHABLE, SYS_NODE_UNREACHABLE, and SYS_NODE_DOWN. Difference between SYS_NODE_UNREACHABLE and SYS_NODE_DOWN is that "unreachable" generated when server can detect network failure between itself and target node.
Another poll is ICMP poll, it was added in version 4.0. It's main use is to do regular ICMP pings and collect response time and packet loss statistic. In addition, it will generate event SYS_ICMP_UNREACHABLE when node is not responding to ICMP. If that happen after SYS_NODE_DOWN then ICMP unreachable event will be correlated to node down event, but because those two types of poll run asynchronously it is possible that node became actually unreachable after last status poll run and before next ICMP poll run, thus generating ICMP unreachable event that cannot be correlated to node down event.
You can effectively hide those ICMP unreachable events by disabling or removing rules that generate alarms from them, and unchecking "write to event log" option in event template configuration for SYS_ICMP_UNREACHABLE and SYS_ICMP_OK.

Best regards,
Victor