Just a question, Zenoss is supposed to handle layer 3 dependencies... if it has route info. Can you see the links for these routers in the network map? It might be a bug, but I really don't think you are supposed to need to do this sort of manual transforms for a router going down, as long as Zenoss knows about the routers and their internal routing tables... -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University
tlkhorses wrote: > Kingpin, not meaning to hijack your thread here but thought this may help you > and others and flows with the topic. Hope you don't mind. > > I looked at the device dependency using transform. How do I add more than one > since it looks like you can only do one transform? I need to add many of > these as I have a large network. > > For instance, from Zenoss, router1 is first. Router2 is second, Router3 is > third. If router1 is down via ping, I want router2 and router3 to show > unknown or some other status such as debug since Zenoss wouldn't know the > state of those. > > Thought to make them unknown but I settled on debug since there wasn't an > unknown in the available status selections. Along with that was if the > dependent router, i.e. router2 or 3, saw that the upstream router was down I > would set the evt.severity as debug so I and the techs wouldn't get emails > for them being down (critical). Got a ton of emails (since critical event) > from the downstreams today when we brought one of the upstream down for a > repair. > > Thanks, > > tk > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://forums.zenoss.com/viewtopic.php?p=27362#27362 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
