NetXMS Support Forum

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.

From reviewing other forum posts it seems like I need to:

1. Create a custom event such as "NODE_STILL_DOWN"
2. Create a server script that runs nxevent calling NODE_STILL_DOWN.
3. Add an action to "SYS_NODE_DOWN" that runs the above server script.
4. Create a processing policy rule for NODE_STILL_DOWN that has a filter checking for 5 and 20 minute poll intervals.


Is this the best way to do this?

If so,  how can I call nxevent from a server script? (I haven't seen any examples.  I am using Windows NetXMS).  nxevent.exe is in C:\NetXMS\bin on the server.

Thanks for any help.

We are trying to setup a configuration where if any of our nodes are down it will send an email at first poll and then at 5 minutes if it is still down and then at 20 minutes if it is still down.  We only care about icmp at this point.

Can this be setup globally so each node doesn't have to be configured individually?

Any help is appreciated.

Thanks.