NetXMS Support Forum

I hope that name of your config for nxagentd(NX agent) is "nxagentd.conf", not "netxmsa.conf". What does agent writes if you start it from console like: "C:\ProgramData\NetXMS\bin\nxagentd -D6"

Config file for the server should be named "netxmsd.conf" and for the agent "nxagentd.conf"

Bug have been created: https://dev.raden.solutions/issues/1288

So you don't have any agents there(I mean even SNMP)?
Steps to get debug log:
1. Set in server configuration file this parameters:
LogFile - path to server log file
DebugLevel=6
2. Restart derver
3. Run manually status poll on one of incorrectly added objects(right click object->Poll->Status)
4. Find in lines "Starting status poll for node XXX (ID: NNN)", "Finished status poll for node XXX (ID: NNN)". Send everything between them.

Also for this DCI "Use this DCI for node status calculation" should be enabled.

Now I understand where is problem.

Additional requirements:
Disable "CheckTrustedNodes" or add node1 and node2 as trusted for nodeA

I attached screenshots - how configuration should look for node1. You can so similar thing for node2. No DCI configuraiton needed for nodeA

Hi.

Can you please provide walks for this OIDs:
.1.3.6.1.2.1.17.1.4.1.2
.1.3.6.1.2.1.2.1.0
.1.3.6.1.2.1.2.2.1.1
.1.3.6.1.2.1.31.1.1.1.1
.1.3.6.1.2.1.2.2.1.2

Thank you.

Please check that correct column is used as the instance column(key). In your case it could be index.

One more note - threshold are checked once per row(if first column of second row violated threshold, then other columns of second row will not be checked).

Updated.
Also please check that "Smart status" and "Status" columns have String data type.

Fixing those two things(instance and data type) I managed to get correct behavior.

Shouldn't instance be just "10.9.61.11" not the "10.9.61.11 26 29 0 46 10.9.61.11"? Can you please provide you instance discovery configuration it looks that it is done incorrectly.

In your situation nodeA should not contain any DCI that calculate status for node1 or node2. You should create DCI on node1 and node2 setting nodeA as a shource node. Can you configure your system like this and explain what is not working using this solution.

Can you please provide:
1. Output of nxget command line tool, getting interface list from one of sutch nodes. Example: /opt/netxms/bin/nxget -l 192.168.100.5 Net.InterfaceList
2. Does all nodes in this subnet have the same same OS?
3. Network mask.
4. And server log on debug level 6 when one of thoose nodes is status polled.

Recently we had problem with subnet defenitoins for old Windows versions: https://www.netxms.org/forum/configuration/invalid-network-mask-4369/msg20773/#msg20773

You should create DCIs on node1 and node2 with DCI source nodeA. In this case data will be collected from nodeA, but thresholds will be generated for node1 and node2.

"Use this DCI for node status calculation" works for me. What exactly does not work?

Added:
There is description about this solution(note "Proxy node" was renamed to "Source node"): https://www.netxms.org/forum/feature-requests/icmp-ping-as-internal-parameter/

Found and fixed. Will be in 2.0.6.

It is possible to use DCI for status calculation. This option is enabled for each DCI separately(DCI Properties->Other options->Use this DCI for node status calculaiton).
From the documentation:
"DCI can be used to calculate object status. Such kind of DCI should return integer number from 0 till 4 representing object status. To use DCI for status calculation, there should be selected this option in it's properties (Other Options -> Use this DCI for node status calculation)."

Can you please provide:
1. output of nxget command line tool, getting interface list. Example: /opt/netxms/bin/nxget -l 192.168.100.5 Net.InterfaceList
2. Agent version
3. OS version(where the agent is installed)

Thank you

You can disable or remove event processing policy with description "Generate alarm when MAC address change detected on interface".

"Locked by the server." means that there is mark that database is locked in NetXMS database in config table. This can be in two situations - if server was stopped incorrectly or if NetXMS server is currently running. This flag is used to prevent change of the database while server is running (this action can be unsafe).