Marcel, I am having the same problem, I am also using the vmware appliance running 2.0.3, sorry I don't know why this is happening.
I have not seen this strange behavior before on previous vmware images. I think there must be something wrong with the vmware image. I don't understand why I am constantly getting a severity 5 event saying the device is up which is then cleared by a severity 0 event that says the exact same thing. This is affecting multiple devices that I know are responding to ping perfectly. The only thing I see in the event log for zenping is that it says the device network is not in the topology, but I can see the subnet in Networks: 2007-07-30 18:38:05 WARNING zen.ZenStatus: device 'DCDOM01' network '172.26.20.0/24' not in topology Very frustrating - is anyone else experiencing the same problems with the 2.0.3 vmware image? Can anyone from development investigate, I can provide whatever info is required? Thanks Steve This is my zenping log: 2007-07-30 17:58:05 INFO zen.ZenPing: building pingtree from localhost.localdomain 2007-07-30 17:58:05 WARNING zen.ZenStatus: device 'DCDOM01' network '172.26.20.0/24' not in topology 2007-07-30 17:58:05 WARNING zen.ZenStatus: device 'DCCLA01' network '172.26.10.0/24' not in topology 2007-07-30 17:58:05 WARNING zen.ZenStatus: device 'DCCLA02' network '172.26.10.0/24' not in topology 2007-07-30 17:58:05 WARNING zen.ZenStatus: device 'dcswc01.xdss.blah.uk' network '172.26.9.0/24' not in topology 2007-07-30 17:58:05 WARNING zen.ZenStatus: device 'DCDOM02' network '172.26.20.0/24' not in topology 2007-07-30 17:58:05 WARNING zen.ZenStatus: device 'fw-dss-ns5-vc.n3.xdss.blah.uk' network '10.197.169.0/26' not in topology 2007-07-30 17:58:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 17:59:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.02 seconds 2007-07-30 18:00:45 INFO zen.ZenPing: Finished pinging 7 jobs in 0.02 seconds 2007-07-30 18:01:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:02:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:03:45 INFO zen.ZenPing: Finished pinging 10 jobs in 0.03 seconds 2007-07-30 18:04:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.02 seconds 2007-07-30 18:05:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:06:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:07:45 INFO zen.ZenPing: Finished pinging 10 jobs in 0.03 seconds 2007-07-30 18:08:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.02 seconds 2007-07-30 18:09:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.03 seconds 2007-07-30 18:10:45 INFO zen.ZenPing: Finished pinging 10 jobs in 0.02 seconds 2007-07-30 18:11:45 INFO zen.ZenPing: Finished pinging 10 jobs in 0.02 seconds 2007-07-30 18:12:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.03 seconds 2007-07-30 18:13:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.03 seconds 2007-07-30 18:14:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.03 seconds 2007-07-30 18:15:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:16:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.03 seconds 2007-07-30 18:17:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:18:05 INFO zen.ZenPing: building pingtree from localhost.localdomain 2007-07-30 18:18:05 WARNING zen.ZenStatus: device 'DCDOM01' network '172.26.20.0/24' not in topology 2007-07-30 18:18:05 WARNING zen.ZenStatus: device 'DCCLA01' network '172.26.10.0/24' not in topology 2007-07-30 18:18:05 WARNING zen.ZenStatus: device 'DCCLA02' network '172.26.10.0/24' not in topology 2007-07-30 18:18:05 WARNING zen.ZenStatus: device 'dcswc01.xdss.blah.uk' network '172.26.9.0/24' not in topology 2007-07-30 18:18:05 WARNING zen.ZenStatus: device 'DCDOM02' network '172.26.20.0/24' not in topology 2007-07-30 18:18:05 WARNING zen.ZenStatus: device 'fw-dss-ns5-vc.n3.xdss.blah.uk' network '10.197.169.0/26' not in topology 2007-07-30 18:18:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:19:45 INFO zen.ZenPing: Finished pinging 10 jobs in 0.03 seconds 2007-07-30 18:20:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:21:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.03 seconds 2007-07-30 18:22:45 INFO zen.ZenPing: Finished pinging 7 jobs in 0.02 seconds 2007-07-30 18:23:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:24:45 INFO zen.ZenPing: Finished pinging 7 jobs in 0.03 seconds 2007-07-30 18:25:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:26:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:27:45 INFO zen.ZenPing: Finished pinging 7 jobs in 0.02 seconds 2007-07-30 18:28:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.02 seconds 2007-07-30 18:29:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.03 seconds 2007-07-30 18:30:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:31:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:32:45 WARNING zen.ZenPing: DCCLA01 ip 172.26.10.3 is up 2007-07-30 18:32:45 INFO zen.ZenPing: Finished pinging 10 jobs in 0.04 seconds 2007-07-30 18:33:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.03 seconds 2007-07-30 18:34:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.02 seconds 2007-07-30 18:35:45 WARNING zen.ZenPing: DCDOM01 ip 172.26.20.1 is up 2007-07-30 18:35:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:36:45 WARNING zen.ZenPing: DCDOM01 ip 172.26.20.1 is up 2007-07-30 18:36:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.02 seconds 2007-07-30 18:37:45 WARNING zen.ZenPing: DCDOM01 ip 172.26.20.1 is up 2007-07-30 18:37:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.03 seconds 2007-07-30 18:38:05 INFO zen.ZenPing: building pingtree from localhost.localdomain 2007-07-30 18:38:05 WARNING zen.ZenStatus: device 'DCDOM01' network '172.26.20.0/24' not in topology 2007-07-30 18:38:05 WARNING zen.ZenStatus: device 'DCCLA01' network '172.26.10.0/24' not in topology 2007-07-30 18:38:05 WARNING zen.ZenStatus: device 'DCCLA02' network '172.26.10.0/24' not in topology 2007-07-30 18:38:05 WARNING zen.ZenStatus: device 'dcswc01.xdss.blah.uk' network '172.26.9.0/24' not in topology 2007-07-30 18:38:05 WARNING zen.ZenStatus: device 'DCDOM02' network '172.26.20.0/24' not in topology 2007-07-30 18:38:05 WARNING zen.ZenStatus: device 'fw-dss-ns5-vc.n3.xdss.blah.uk' network '10.197.169.0/26' not in topology -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mars Sent: 31 July 2007 11:55 To: [email protected] Subject: [zenoss-users] Re: lots of up/cleared reports No one? So everybody is getting perfect reports (without lots of ip is up messages)? It surely must be something very simple but I can't find it. I've now turned off Zenoss because all the mail I'm getting from Zenoss. ------------------------ Marcel Engels -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=9339#9339 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users DISCLAIMER - This email and any file transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions expressed are those of the author and do not represent the views of Derwent Shared Services, unless otherwise explicitly stated. The information contained in this email may be subject to public disclosure under the Freedom of Information Act 2000. Unless the information is legally exempt from disclosure, the confidentiality of this email cannot be guaranteed. Derwent Shared Services is an NHS Shared Services Organisation. _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
