<html> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 10 (filtered)"> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Hi – We have a large SiteScope installation (we monitor several thousand servers with about 20 SiteScope machines) and are considering Nagios as a replacement. One of the issues we have is that we cannot, for various (mostly political) reasons, install an agent on the hosts we monitor. We have successfully tested agentless monitoring by using Perl plugins that SSH to the remote host and run a command, parsing the output. However, we cannot run as many monitors per server as in our SiteScope installation because of the latency incurred by setting up and breaking down the SSH connection for EACH monitor. So my question is, does anyone know of a reasonable approach to agentless monitoring using Nagios? We are planning to try SSH4, which automatically keeps SSH connections open for later use, and forcing Nagios to run several scripts sequentlially against the same host. But this has the problem that a host which is down, or busy, could delay checking other hosts. We would like, for many reasons (not just $$$, although that’s a factor), to use Nagios, but having to install twice or three times as many servers to support it is out of the question. Any advice gratefully accepted. Thanks, <div> Steve Keller (<a href="mailto:skeller@ea.com">skeller@ea.com</a>) Manager, Tools and ESM Group Global Infrastructure Services </div> </div> </body> </html>