Make it a script threshold. Then compare the value to the result of time() function. https://wiki.netxms.org/wiki/NXSL:time

Hello, You can solve issue by: unbind template with SLA DCI from node delete SLA custom attributes from node on node create DCI described Status collecting Status parameter from origin Internal apply template with SLA DCI to node or: manually populate SLA custom attributes with values on node create DCI described Status collecting Status parameter from origin Internal Br, A

Hi Victor It seems as if it was the agent on the node. I moved DCI's to another node and it worked again. I suspect it is something to do with the server node. Regards

Hi, currently not. You can fill feature request for that. Best regards, Victor

You can't use them in script without node context when CheckTrustedNodes is on. Best regards, Victor

Hi, we will check. You can report issues at https://track.radensolutions.com Best regards, Victor

Then NetXMS server cannot match it to correct device - there are just no enough information. You can setup syslog proxy on agent behind NAT so it will receive syslog messages from original addresses and forward to NetXMS server. Best regards, Victor

Hi, default ordering is currently hard-coded. Feel free to add feature request for that. Best regards, Victor

Hi, currently answer to both questions in "no". Feel free to register feature requests in our ticket system though For polling time change could be quite easy - server can measure and store polling time for last status poll, which can be made available through internal DCI. Having this value exposed you'll be able to do usual stuff like set thresholds and generate alarms. Possible workaround cold be to create script DCI which will do SNMP request on any OID and measure time taken by that request. Best regards, Victor

Yes, %* formatter was added much layter then original topic was discussed. Now it is better to collect value as is and use formatters to display in K/M/G. Best regards, Victor

Hi, most likely problem caused by trusted node check. You should either add current node (where script is being executed) to list of trusted nodes on node sw, or disable trusted nodes check completely by setting server configuration parameter CheckTrustedNodes to 0 and restart server. Best regards, Victor

Hello, I'm trying to run a powershell script when became a certain event. The script turn-on access list on HP-switch via SSH.  The script works fine from PS-console or CMD, but doesnt start from "Actions configuration" on the NXMS server.. ( ..that's part of the log: [17-Feb-2017 16:29:20.104] [DEBUG] *actions* Executing action 37 (Disable K22) of type EXEC [17-Feb-2017 16:29:20.104] [DEBUG] *actions* Executing command "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -File "C:\SCRIPT\disable_K22.ps1"" ..but nothing happens upon! Is anyone can tell me what I'm doing wrong? Thanks a lot in advance!

Try to check server log on debug lvl 6.

If Ping DCI is polled once per minute you can set "Samples" to 5(1min*5 = 5min). This means: if last 5 values returned collection error - generate Event. Same as last 5 min offline.

Thanks , works fine

What version of NetXMS do you use? Any object that is added to NetXMS should be shown in object tree. Have you tryed to serach in using object tree filter IP address search like: ">10.5.0.27" PS. May be connected https://www.netxms.org/forum/general-support/ip-conflict-with-deletedchanged-node/?topicseen

Fix is not yet released. It will be included in 2.0.9 and 2.1-M3. Now it is available only in development branch (bug was in UI so if anyonle will make buld form development is is required to rebuild console).

Related: https://www.netxms.org/forum/general-support/presets-greater-than-12-hour/?nowap

As you have selected Passive network discovery only, you do not need to set anything in the Active Discovery Targets section, but otherwise it looks correct.

Was able to reproduce. Thank you.