After much testing I am coming to the conclusion that the dependency checking in zenoss is not going cooperate with me. For example Router 192.168.100.1 goes down devices 192.168.100.2 thru whatever should NOT send an alert (email, page) Well unfortunately they ALL send alerts :-( All the devices have the correct routes, and all the devices are talking SNMP.
So what am I missing here ? What can I do to fix this ? I am assuming that so long as in the "Routes" section there is an entry for 0.0.0.0 then the dependency checking should work ? Destination NextHop InterfaceName Protocol Type 0.0.0.0/0 192.168.100.1 (router name) eth0 local Indirect My only thought as a workaround is to use a REST call/Event Command to set a particular Location into "Maintenance" when an edge router drops. So far I have been unable to figure out the correct URL to do this though. :? -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=13332#13332 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
