We have a similar problem here: Some of our servers have multiple network interfaces. Not all of them can be reached from the Zenoss server. For example: Zenoss learns from SNMP that SSH is listening on 192.168.0.1 and 10.0.0.1. Only 192.168.0.1 can be reached from Zenoss. When Zenoss checks the service it tries to connect to 10.0.0.1 too, which fails, and Zenoss reports the service as down.
-------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=32732#32732 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
