We're having some issues with a misbehaving Cisco 7301 which keeps updating the routing one of our critical interfaces to null (happens randomly about once in every 12 hour period). We've got a problem report in with Cisco to cover the problem, but that's not what this is about.
I'm having trouble figuring out how to set up Zenoss to monitor that interface, and trigger a critical event so that our on pager staff can reset the interface until we have a permanent solution for the problem. Is there a way to tell Zenoss to ping the sub-interface ip address in addition to the Cisco's primary ip address? I've configured a command datasource using ping to do latency and packet loss graphing on the interface, but no event is triggered when the ping command fails. Or if you have any other suggestions on how can insure that I an alert is generated when that interface goes down, it would be much appreciated. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=23069#23069 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
