Yes. For example, I have some routers that have an interface on our
private network and an interface on the public internet. I would like
to be able to ping both of these interfaces, to make sure that the
internet connection is still working. If I only ping the management
IP address (the private one) I can't verify that. This would only
double the number of interfaces that would be pinged.'
Added a ticket to track this feature http://dev.zenoss.org/trac/
ticket/288
I thought this was the whole purpose of the zPingInterfaceName
zProperty? Can I re-enable this somehow, or does it need to be
totally redone? It seems like if you just set this property on the
specific device, it will only ping the extra interface on that one
device and not on all devices.
Also, after upgrading the VMware appliance to version 22.1, I have a
couple problems. One is that if a device is "down," once it is back
up the device still shows a critical error on the dashboard. If I
browse to the device and click on the "Events" tab, the top row is in
red and says <devicename> ip xxx.xxx.xxx.xxx is up. The row below
shows the event when the device was down. Shouldn't this event clear?
I receive a "CLEAR" alert, and the top row has a very high count of
the device being up, but it still shows as down on the dashboard and
device Status tab.
You have a red event that says up? That's totally wrong!
-EAD
After looking at this a few more times, here is what I found:
Before upgrading the VM to 22.1, when a server was down it would send
an event like:
<device> ip 192.168.x.x is down 2006/09/08 09:53:13.178 2006/09/08
09:54:10.229 2
When the server was up again it would clear the event:
[CLEARED] <device> ip 192.168.x.x is down 2006/09/08 09:53:13.178
2006/09/08 09:54:10.229 2
After the upgrade to 22.1, when a server went down it would send the
device down event (same as above). When the server was back up,
instead of clearing the down event it would send an "up" event:
<device> ip 192.168.x.x is up 2006/09/08 09:53:13.178 2006/09/08 09:54:10.229 2
This is a red (critical) event, so the device appears to be down. Is
this just a problem with upgrading (i.e. the device was added when
using the old version, and now with the new version things are handled
differently)? It seems to happen only on our servers, but I'm not sure
if any other types of devices have been down since then.
Thanks!
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
