Once you have discovered a TCP service you can turn on monitoring for
it on the instance associated with the device or at the "Class" level
of that service (under the /services root).
-EAD
On Feb 7, 2007, at 5:18 PM, David Carmean wrote:
On Tue, Feb 06, 2007 at 12:12:36PM -0800, David Carmean wrote:
On Mon, Feb 05, 2007 at 10:34:31PM -0700, Duncan McGreggor wrote:
I may have misinterpreted what you are asking, but maybe this will
clarify:
* the portscan functionality is for "modeling" or "discovering"
services running on your network, and shouldn't be run very
frequently (e.g., only when your network changes)
* Zenoss does not use portscan for host availability checking -- it
uses zenping for that
Ah, but you *can* use it for availability testing if you enable
monitoring for that service, globally or on a per-device basis.
Maybe
that's a side-effect or a stub that's not yet fully developed?
I'm sorry, I misspoke; "portscan" is for discovery, IP Services is
for monitoring. I guess what I need is help using only IP Services
for monitoring.
--
David Carmean Network Appliance, Inc
Infosystems Architect, 495 E. Java Drive
Java (Sunnyvale) Engineering Lab Services Sunnyvale, CA 94089
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
