|
|
|
|
If you're familiar with earlier versions of Network Monitor you might recall that the alert status of one monitor could be made dependent on the alert status of another monitor assigned to the same device. With Network Monitor v5.0 this dependency feature has been expanded to include any part of the local gateway branch.
Imagine monitoring a router for a single network. If the router goes down the monitor you've set up to test that router will correctly change, first to a Failed state, then to an Alarm state. Unfortunately all the other devices on that same network depend on that same router. When the router fails to connect, those dependent devices can't help but fail to connect as well. An entire branch of the navigation tree reports monitoring failures even though the problem is really a single device. Those dependent devices are just a distraction at this point. Using dependency relationships you can prevent Network Monitor from triggering a cascade of unnecessary Alarm states when the Alarm state for a single critical monitor will serve the same purpose.
Click Edit for any node, then click the Advanced tab. Use Device dependency settings to select the monitor this node should be dependent on. All descendants of this node set to inherit will be dependent on the same monitor you select.
