Hi guys, We noticed a problem since we upgraded our zenoss core to 2.3.2 with level 3 dependency.
When a router goes down, the dependent devices used to move to state down and so we only got few alerts : once for ipservices and once for the server itself. Since upgrading to 2.3.2, when a router goes down, the dependent devices stay "up" (so no alert) but ipservices continue to complain about being down. Here is an example we do have right now. Router for Lille is down, server FIDJI in Lille is up but ipservices are down are count increase. device;component;eventClass;summary;firstTime;lastTime;count rtrsite.net.lill.fr.sopra;;/Status/Ping;ip 172.30.160.1 is down;2009/01/07 07:00:56.000;2009/01/07;08:24:09.000;256 fidji.lill.fr.sopra;ncp;/Status/IpService;IP Service ncp is down;2009/01/07 07:01:23.000;2009/01/07 08:23:54.000;75 fidji.lill.fr.sopra;http;/Status/IpService;IP Service http is down;2009/01/07 07:01:23.000;2009/01/07 08:23:54.000;75 fidji.lill.fr.sopra;mysql;/Status/IpService;IP Service mysql is down;2009/01/07 07:01:23.000;2009/01/07 08:23:54.000;75 -- Florian Deckert SopraGroup - France -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=29734#29734 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
