<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thank you Jeremy!<div class=""><br class=""></div><div class="">Yes, the issues is that I have been asked to figure out is how Xymon handle monitoring activities with Xymon Clients.</div><div class=""><br class=""></div><div class="">And the reason being is that we have one Xymon server with over 3,000 Xymon clients on it. And we keep getting thousands of alert emails every day from Xymon clients.</div><div class=""><br class=""></div><div class="">Therefore, the Upper Management would like to move some servers to Tivoli and they want to understand what Xymon does, and how it actually communicate with Clients. So that when we finally move some servers to Tivoli, we will not be missing anything that Xymon has been monitoring.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Agege<br class=""><div><blockquote type="cite" class=""><div class="">On Mar 15, 2016, at 6:08 PM, Jeremy Laidman <<a href="mailto:jlaidman@rebel-it.com.au" class="">jlaidman@rebel-it.com.au</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" style="font-size: 12pt; background-color: rgb(255, 255, 255); font-family: Calibri, Arial, Helvetica, sans-serif;" class=""><div style="word-wrap:break-word" class=""><div class=""><div class="">Please what script trigger the SSH tests that are built into the services that Xymon uses.</div></div></div></div></blockquote><div class=""><br class=""></div><div class="">The SSH test, and all of the other network-probe tests (ping, http, etc) are performed by the xymonnet program. This is launched by the xymonlaunch supervisor process, by default once every 5 minutes. The execution parameters are defined in the tasks.cfg file, in the [xymonnet] section.</div><div class=""><br class=""></div><div class="">The way it works is this. When xymonnet runs, it looks in protocols.cfg and builts up its suite of TCP tests from there, such as "smtp" and "ssh". It also has built-in the three special non-TCP tests "ping", "dns" (or "dig") and "ntp". Next, xymonnet scans the hosts file for any host with a tag matching any of these defined test names. And then it runs through each test for each host having that test.</div><div class=""><br class=""></div><div class="">It's actually slightly more complicated than that, but it's functionally equivalent to how I've explained it. For more of the details, refer to the man page for xymonnet, and read the "XYMONNET INTERNALS" section.</div><div class=""><br class=""></div><div class="">The "ssh" test is defined in protocols.cfg as follows:</div><div class=""><br class=""></div><div class=""><div class="">[ssh|ssh1|ssh2]</div><div class=""> send "SSH-2.0-OpenSSH_4.1\r\n"</div><div class=""> expect "SSH"</div><div class=""> options banner</div><div class=""> port 22</div></div><div class=""><br class=""></div><div class="">This defines the port (which can be overridden per host in hosts.cfg) and whether the status page should show the response received after sending the "send" string. The "send" string gets sent to the remote server being subjected to the test. The "expect" string is matched against the response (banner) and if successful, the status goes green, otherwise red. Or if the TCP socket fails to connect, the status goes red.</div><div class=""><br class=""></div><div class="">Is there a particular problem you're trying to solve? If you would like some more relevant help, perhaps you could explain what you're trying to do, and what you are expecting to happen but is not.</div><div class=""><br class=""></div><div class="">Cheers</div><div class="">Jeremy</div></div></div>
</div></blockquote></div><br class=""></div></body></html>