NetXMS Support Forum

I hadn't thought of using the NetXMS Agent proxy setting for that, thanks!

For anyone who comes across this post in the future, you also need to add
EnableProxy = yes
to the agent configuration file for the proxy, and add the device that is to be pinged to the trusted nodes list if CheckTrustedNodes is enabled.

On the wiki, on the PING Subagent page, it's mentioned Icmp.Ping shouldn't be used for instant monitoring. Should I interpret this that if I want to check, say 100 nodes every minute, I'd probably better balance them a bit between several nodes with NetXMS agents?

Hello,

One of the most basic things I use NetXMS for is monitoring if a node is reachable over the network or not. Most of the times, the nodes support either a NetXMS agent or SNMP, but I have quite a few that don't either.

NetXMS is capable of detecting if these nodes are up or down by using a ICMP ping, which is good, but the only way to do anything with that information seems to be relying on the SYS_NODE_DOWN event or its effects (such as the status of the node becoming critical)

I'd find it very useful if the result of the ICMP ping could be accessed in a DCI, as for example an internal parameter (similar to the Status)

Hello,

I've noticed under the Interfaces tab in the Object Details view of a node there's a new column "Exp. State". From what I gather in the change log, this is the expected state of an interface.

This sounds like a feature I certainly could use, as at the moment all down ports on my switches are unmanaged; meaning I won't know when they come up either. Where can the expected state of an interface be set? Or is this for a future update?

Thanks in advance for your reply.

Hi,

I've been testing out a few of the new features in v1.2.0 the last days, came to an interesting discovery I thought I'd share.

Yesterday, I was playing around the the new tabular DCI's, more specifically, Filesystem.volumes.
It all worked OK, but then suddenly today, I find one of the performance related DCI's on my NetXMS server node has gone up.

More specifically, "Average time to queue DCI for polling for last minute" went from 0 with an occasional small peak to constant 12-14 with frequent peaks up to 180, exactly at the moment I added the table DCI. Likewise, it went away as soon as it was removed.

I guess the average value increasing makes some sense as it has to collect 11 parameters of in this case 17 volumes, but on the other hand, there are 902 other DCI's in NetXMS according to the Server Remote console stats command, so the average shouldn't too affected. Isn't the impact a bit high?

As for the table DCI's, they certainly have great potential. One feature I'd like is the ability to read out a value from a particular cell in NXSL. (similar to GetDCIValue) Obviously, thresholds would also be useful, but I can imagine creating a sufficiently flexible interface for configuring them is complicated work.

One last question. I've also posted a few bug reports in the bugtracker the last two weeks. Is it still in use? I couldn't find v1.2.0 in the list.

Thanks for the great software and all the effort you put into it!