kingpin wrote: > For the sake of testing the layer 3 dependencies properly I have connected a > test router to our network, created some subnets on that routers and put some > devices in those subnets. Zenoss did load all information from the routing > tables correctly and the network map was accurate. > > I then shut down the test router and Zenoss created a Status/Ping ip is down > event for the router and all devices connected to that router. > > It seems like the layer 3 dependencies do not work at all. Zenoss could of > known that if the router goes down all devices in at least the directly > connected subnets will be down as well and suppress those events. > > This is rather disappointing, can anyone shed some light on this. > > The Zenoss core product page states : > Dependency Tracking > * Intelligently suppress tests and alerts based on layer 3 network > dependencies
Can you unplug the router for a while? It could be that the devices behind are generating down events but only a few times, (so the count wouldn't be updated) This is because it's possible then zenoss sees the devices after the router down before zenoss sees the router down I have notifications for a count higher then 3 and mostlly this is not causing problems -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=29892#29892 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
