On some of my servers IP services pop3 and smtp are causing critical alerts even though these services are puposely blocked by a firewall and I cant find a way to prevent those false alarms from re-occurring.
These services seem to be discovered via SMTP and alerting occurs because monitoring is set to "true" globally at the IpService level. I have tried to delete the discovered services on the machine in question, set monitoring to false on them, even locked them, to no avail. The same thing happens with machines having multiple (virtual) IP addresses (VMware) where Zenoss keeps complaining that some IP services are not available on one of those addresses, which is correct, but there should be a way to tell Zenoss to accept this fact. O.K., I could disable monitoring these services globally, but it would be stupid to do so just because one out of 50 servers has some special configuration. It would be similarily stupid to create and manage a complete new service class for each of these "special" servers. So how is it intended to handle this problem? Martin geotek.de (http://geotek.de) -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=15873#15873 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
