<![CDATA[Fake node used as container for aggregate values]]>I have a node used as a "fake" switch to collect all the traffic generated from a group of virtual machines. That node is configured with the IP 0.0.0.0 so it has no interface. Everything works fine in the data collection, except that the node persists in the "Unknown" status.
Is there a way to force its status to "Normal"? I'm not interested in its "real" state since it hasn't a real state: is just a container for the aggregated values computed from other nodes.

Maybe I'm just using the worst approach to solve this problem, any other suggestion is welcome! 🙂

Best regards,
Marco

fake-switch.PNG

fake-switch-lastvalues.PNG

]]>https://forum.netxms.org/topic/2564/fake-node-used-as-container-for-aggregate-valuesRSS for NodeFri, 13 Nov 2026 15:21:35 GMTMon, 26 Aug 2013 15:15:46 GMT60<![CDATA[Reply to Fake node used as container for aggregate values on Tue, 27 Aug 2013 14:25:27 GMT]]>Just answered same question in another thread, seems as common problem 🙂 Currently the only workaround is to keep active alarm of "Normal" priority on that node. You can create rule to create alarm for that node and post required event from the script using PostEvent function.

Best regards,
Victor

]]>https://forum.netxms.org/post/11127https://forum.netxms.org/post/11127Tue, 27 Aug 2013 14:25:27 GMT