<![CDATA[Node Dependencies]]>We have approximately 250 switches(nodes) that have other switches that are upstream from them. 

If we would like to verify an upstream switch is up before considering a switch to be down do we need to create 250 event processing rules that check a situation status on the upstream switch? 

Is it better to create one event processing rule that has a filter script with basically 250 if statements to check the situation status?

Is there a better way to manage dependencies?  At this point we only care about pinging switches to see if they are up or down.

Thanks for any help.

]]>https://forum.netxms.org/topic/4355/node-dependenciesRSS for NodeFri, 13 Nov 2026 12:28:04 GMTThu, 17 Mar 2016 14:22:10 GMT60<![CDATA[Reply to Node Dependencies on Fri, 18 Mar 2016 14:19:44 GMT]]>Thank you.  I will work on it from that angle.

]]>https://forum.netxms.org/post/19433https://forum.netxms.org/post/19433Fri, 18 Mar 2016 14:19:44 GMT<![CDATA[Reply to Node Dependencies on Thu, 17 Mar 2016 14:35:00 GMT]]>If the switches provide topological information (LLDP, STP MIB, etc.), NetXMS will automatically correlate event, and create an alarm only for the source event generating the outage.

]]>https://forum.netxms.org/post/19429https://forum.netxms.org/post/19429Thu, 17 Mar 2016 14:35:00 GMT