On Oct 14, 2008, at 12:12 PM, colletti wrote:
Thanks for your input thrope. We are int he same situation as we
would like to know which network it is that is having a problem.
public verus private, or in your case the vpn link versus the
internet connection.
I'm hoping there is a way to do this without having to add all these
machines twice. One time for each network, but it's beginning to
look as if that is the only way to do that in zenoss?
You can add a COMMAND type data source that runs check_ping against
the IP address you're interested in. You can leverage a custom
property to make this just a little bit easier on yourself.
Create the custom property:
1. Go to /Devices and choose More -> Custom Schema from the menu.
2. Add a property with the name cAltPingAddress with no default.
Override cAltPingAddress on each device:
1. Go to each device and choose More -> Custom from the menu.
2. Set the alternate IP as the cAltPingAddress
Create a AltPing template:
1. Go to /Devices and choose the Templates tab.
2. Add a template called AltPing.
3. Add a COMMAND type data source to the template called ping.
4. Set the event class to /Status/Ping and severity to critical.
5. Command template should be:
check_ping -H ${here/cAltPingAddress} -w9999,100% -c9999,100%
Now you can bind this AltPing tempalte to any device or device class
you wish to do extra pinging on.
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
