<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">As other people have suggested, you can
simply have the "shutdown" process which is responsible for
deciding whether a machine is "idle" and needs to be shutdown,
also being responsible for sending a "disable" message to xymon.
At the time this process decides that a machine needs to be
restarted, it will send an "enable" to xymon.<br>
<br>
This way xymon will monitor everything all the time, anything with
a "blue" is down and supposed to be down, anything with green is
up and OK, and anything red is.... well, is red.<br>
<br>
Regards,<br>
Adam<br>
<br>
On 08/15/2012 04:33 AM, Steven Carr wrote:<br>
</div>
<blockquote
cite="mid:CALMep07wD7m5-cwesLAvX+n5BAT+UNwJnJnOUKZG34N5yto4Bg@mail.gmail.com"
type="cite">So you could also flag the nodes with the "dialup"
flag which will allow the nodes to go down and Xymon wont complain
that they are down, but you are still going to have to write your
own server side script which determine if a host is down that
shouldn't be down and then raise an alert for it. Xymon can't do
that out of the box, and I'm not sure if any other monitoring
systems can either, the majority of monitoring solutions expect
nodes to be up 100% and only have exceptions for scheduled
downtime etc.<br>
<br>
Steve<br>
<br>
<br>
<br>
<div class="gmail_quote">On 14 August 2012 19:13, pankaj dorlikar
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:pankaj.dorlikar@gmail.com" target="_blank">pankaj.dorlikar@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">hi,<br>
<br>
thanks for reply. We have clients installed on all the nodes.
At any<br>
point of time, the nodes on which job is not running will be
powered<br>
down. if new job comes, these nodes be powered up and some
other<br>
nodes will go down which are not running any job.<br>
<div class="HOEnZb">
<div class="h5"><br>
<br>
On 8/14/12, Steven Carr <<a moz-do-not-send="true"
href="mailto:sjcarr@gmail.com">sjcarr@gmail.com</a>>
wrote:<br>
> How are you monitoring the nodes? do you have a xymon
client on each of the<br>
> nodes or are you doing a simple "ping" check to the
node?<br>
><br>
> If you are just doing a simple ping check then, off
the top of my head, I<br>
> would make all nodes "noconn" in the hosts.cfg so
Xymon doesn't actually<br>
> ping them anymore and write a script which uses the
data you have to ping<br>
> nodes and then work out if the node should be up or
not, and if the node is<br>
> down and it shouldn't be then trigger a red alarm for
that node.<br>
><br>
> Steve<br>
><br>
><br>
><br>
> On 14 August 2012 12:05, pankaj dorlikar <<a
moz-do-not-send="true"
href="mailto:pankaj.dorlikar@gmail.com">pankaj.dorlikar@gmail.com</a>>
wrote:<br>
><br>
>> ---------- Forwarded message ----------<br>
>> From: pankaj dorlikar <<a
moz-do-not-send="true"
href="mailto:pankaj.dorlikar@gmail.com">pankaj.dorlikar@gmail.com</a>><br>
>> Date: Tue, 14 Aug 2012 16:34:00 +0530<br>
>> Subject: Re: [Xymon] Green status<br>
>> To: Ryan Novosielski <<a
moz-do-not-send="true" href="mailto:novosirj@umdnj.edu">novosirj@umdnj.edu</a>><br>
>><br>
>> Hi,<br>
>><br>
>> thank you for reply.<br>
>> But at any point of time, only some of the nodes
will be down and all<br>
>> the other nodes will be up. If the server itself
goes down, the<br>
>> monitoring of rest of the working nodes will be
affected.<br>
>><br>
>> On 8/14/12, Ryan Novosielski <<a
moz-do-not-send="true" href="mailto:novosirj@umdnj.edu">novosirj@umdnj.edu</a>>
wrote:<br>
>> > -----BEGIN PGP SIGNED MESSAGE-----<br>
>> > Hash: SHA1<br>
>> ><br>
>> > What he is saying is that if there is an
event that takes place where<br>
>> > you can execute a script at the time it
happens, you can disable the<br>
>> > server by using the main binary's "disable"
function. This binary used<br>
>> > to be called "bb" but is now called "xymon"
-- take a look at its man<br>
>> > page to see how to send a disable message.<br>
>> ><br>
>> > On 08/14/2012 03:55 AM, pankaj dorlikar
wrote:<br>
>> >> Hi,<br>
>> >><br>
>> >> Thank you for proving pointers and
important clues. 1) Query<br>
>> >> regarding "server-side test" : We can
know the status of the "down"<br>
>> >> nodes which are down as per schedular's
instructions. But how this<br>
>> >> information will help in setting the
blue/green color for those<br>
>> >> nodes in xymon web page? I mean how to
send this data to xymon<br>
>> >> server? Also will it cover all the
tests?<br>
>> >><br>
>> >> 2) How client cas send to send a
"disable" command to server?<br>
>> >><br>
>> >> thank you<br>
>> >><br>
>> >> -pankaj<br>
>> >><br>
>> >><br>
>> >> On 8/14/12, <a moz-do-not-send="true"
href="mailto:cleaver@terabithia.org">cleaver@terabithia.org</a>
<<a moz-do-not-send="true"
href="mailto:cleaver@terabithia.org">cleaver@terabithia.org</a>>
wrote:<br>
>> >>>> We are using xymon-4.2.2 on rhel
5.2 server and more than 200<br>
>> >>>> clients (HPC Cluster nodes).<br>
>> >>>><br>
>> >>>> Our requirement is :<br>
>> >>>><br>
>> >>>> -> If the node is powered
down by scheduler for saving the<br>
>> >>>> power, it is required that xymon
should show its state as green<br>
>> >>>> and same for other tests of same
node.<br>
>> >>>><br>
>> >>>> Nodes powered down by scheduler
are identified by pbsnodes<br>
>> >>>> command which will show state as
power.<br>
>> >>>><br>
>> >>>> -> If the node is going down
by some other reason other that<br>
>> >>>> powering down by scheduler, it
should show red like normal<br>
>> >>>> clients.<br>
>> >>>><br>
>> >>><br>
>> >>><br>
>> >>> Assuming your scheduler can have
shell script hooks attached to<br>
>> >>> events, I'd add something to send a
"disable" command before it<br>
>> >>> brings a node down, and then
re-enable as it comes back up. If<br>
>> >>> the nodes are being powered down
without state being saved (eg,<br>
>> >>> not suspending/resuming themselves),
then just disable "until<br>
>> >>> OK", otherwise I'd use some
arbitrary future value.<br>
>> >>><br>
>> >>> Relevant tests will be blue (not
green, as requested), but that<br>
>> >>> will be handled as a non-event for
SLA purposes.<br>
>> >>><br>
>> >>> Separately, it might be a good idea
to have a separate<br>
>> >>> server-side test that sends node
state about each node to xymon<br>
>> >>> independent of the node itself. That
test is a fine place to put<br>
>> >>> logic as well.<br>
>> >>><br>
>> >>><br>
>> >>> HTH,<br>
>> >>><br>
>> >>> -jc<br>
>> >>><br>
>> >>><br>
>> >><br>
>> >><br>
>> ><br>
>> ><br>
>> > - --<br>
>> > - ---- _ _ _ _ ___ _ _ _<br>
>> > |Y#| | | |\/| | \ |\ | | |Ryan
Novosielski - Sr. Systems Programmer<br>
>> > |$&| |__| | | |__/ | \| _| |<a
moz-do-not-send="true" href="mailto:novosirj@umdnj.edu">novosirj@umdnj.edu</a>
- <a moz-do-not-send="true" href="tel:973%2F972.0922"
value="+19739720922">973/972.0922</a> (2-0922)<br>
>> > \__/ Univ. of Med. and Dent.|IST/EI-Academic
Svcs. - ADMC 450, Newark<br>
>> > -----BEGIN PGP SIGNATURE-----<br>
>> > Version: GnuPG v1.4.11 (GNU/Linux)<br>
>> > Comment: Using GnuPG with Mozilla - <a
moz-do-not-send="true"
href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
>> ><br>
>> >
iEYEARECAAYFAlAqFsEACgkQmb+gadEcsb53xACfVP9x3ThR0zKtrYFVfVhHzJoI<br>
>> > JNQAoLUaRTt3AcQmrhoArknmclS7WkPw<br>
>> > =jBNe<br>
>> > -----END PGP SIGNATURE-----<br>
>> ><br>
>><br>
>><br>
>> --<br>
>> Pankaj V. Dorlikar<br>
>><br>
>><br>
>><br>
>> --<br>
>> Pankaj V. Dorlikar<br>
>> _______________________________________________<br>
>> Xymon mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:Xymon@xymon.com">Xymon@xymon.com</a><br>
>> <a moz-do-not-send="true"
href="http://lists.xymon.com/mailman/listinfo/xymon"
target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a><br>
>><br>
><br>
<br>
<br>
</div>
</div>
<span class="HOEnZb"><font color="#888888">--<br>
Pankaj V. Dorlikar<br>
</font></span></blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Xymon mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Xymon@xymon.com">Xymon@xymon.com</a>
<a class="moz-txt-link-freetext" href="http://lists.xymon.com/mailman/listinfo/xymon">http://lists.xymon.com/mailman/listinfo/xymon</a>
</pre>
</blockquote>
<br>
</body>
</html>