<![CDATA[Node with question mark on the icon of object browser]]>Hi!
On netxms, i have a node that cannot be monitored throught icmp ping. On that node, i have a dci that store the info about the status of the node and i manage the alarms depending on the value assumed by this dci.
The only problem is that appear a question mark on the icon of the node in the Object three menu; i think this is caused by the icmp polling disabled .
Is there a way to eliminate the question mark on the icon?
Thank you!

]]>https://forum.netxms.org/topic/2538/node-with-question-mark-on-the-icon-of-object-browserRSS for NodeFri, 13 Nov 2026 20:50:09 GMTWed, 14 Aug 2013 15:36:37 GMT60<![CDATA[Reply to Node with question mark on the icon of object browser on Tue, 21 Oct 2014 17:09:21 GMT]]>ok. I made my tests to this new feature:

  • node created with no interfaces (for an unmanagable device)
  • in polling properties of this node I deactivated all except 'Disbale data collection'
  • DCI created on this node which checks the status of the switch port (gives back 4 for down and 0 for up) and 'use this DCI for node status calculation' = ON

Now when I switch off the device, I get an event 'SYS_NODE_CRITICAL'. When I switch on the device again, I get a 'SYS_NODE_NORMAL' event.
But for my existing event processing policy I need 'SYS_NODE_DOWN' and 'SYS_NODE_UP' events. So I created a threshold on the DCI (!=0 -> SYS_NODE_DOWN, deactivation event SYS_NODE_UP) and everything works as expected.
I will first use it for unmanageble provider-modems and switches.
Maybe this helps someone.

]]>https://forum.netxms.org/post/15097https://forum.netxms.org/post/15097Tue, 21 Oct 2014 17:09:21 GMT<![CDATA[Reply to Node with question mark on the icon of object browser on Mon, 20 Oct 2014 16:08:11 GMT]]>Hi,

as previously noted, you can select one or more DCIs with "Use this DCI for node status calculation". Server expects such DCI to return numeric value in range 0 .. 4 which indicates status (0 =  normal, 1 = warning, 2= minor, 3 = major, 4 = critical). Most critical status of all status DCIs and active alarms will be taken as current node status.

Best regards,
Victor

]]>https://forum.netxms.org/post/15093https://forum.netxms.org/post/15093Mon, 20 Oct 2014 16:08:11 GMT<![CDATA[Reply to Node with question mark on the icon of object browser on Mon, 20 Oct 2014 14:31:00 GMT]]>@user54119 said in Node with question mark on the icon of object browser:

I see this feature is in V1.2.17. But how we can use it. I didn't found a documentation.

DCI > Options > Other Options > Use this DCI for node status calculation

What exactly does it do, I dont know 🙂

How does status calculation work if this is checked? Can it be checked for multiple DCIs? Etc...

]]>https://forum.netxms.org/post/15091https://forum.netxms.org/post/15091Mon, 20 Oct 2014 14:31:00 GMT<![CDATA[Reply to Node with question mark on the icon of object browser on Mon, 20 Oct 2014 14:11:52 GMT]]>I see this feature is in V1.2.17. But how we can use it. I didn't found a documentation.

]]>https://forum.netxms.org/post/15090https://forum.netxms.org/post/15090Mon, 20 Oct 2014 14:11:52 GMT<![CDATA[Reply to Node with question mark on the icon of object browser on Mon, 06 Oct 2014 15:35:06 GMT]]>Will be available in next release 1.2.17.

]]>https://forum.netxms.org/post/14986https://forum.netxms.org/post/14986Mon, 06 Oct 2014 15:35:06 GMT<![CDATA[Reply to Node with question mark on the icon of object browser on Tue, 27 Aug 2013 14:15:30 GMT]]>Hi!

The only workaround I've found is to generate alarm for that node with "Normal" state and keep it in outstanding or acknowledged state. I've added a feature request for adding DCI based status calculation (https://www.radensolutions.com/chiliproject/issues/324).

Best regards,
Victor

]]>https://forum.netxms.org/post/11121https://forum.netxms.org/post/11121Tue, 27 Aug 2013 14:15:30 GMT