Monitoring SG Status

[Mike Storms]

Is there an easy method for monitoring the various status from service guard. I'm familiar with the cmviewcl -v command, but would like a more friendly output that I could write some scripts to look at all the various status indicators. Are there some C library functions or h files to look at?

[Marco Santerre]

Actually, you might want to look into Service Guard Manager for Windows which is a graphical interface for your Cluster. You can find it at :

http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=B8341BA

[Sridhar Bhaskarla]

Can you elaborate further on what "status indicators" you are looking at?.

I use the other options provided by cmviewcl for my monitoring scripts. For ex.,

Cluster status
#cmviewcl -l cluster

Node status
#cmviewcl -l node

Package Status
#cmviewcl -l package

Individual package status
#cmviewcl -p

etc., Add -v flag to each of the above to get verbosed output.

-Sri

[Mike Storms]

I tried the -l option doesn't work on my OS... I'm pretty much interested in all the information on the cmviewcl -v.... Any easy parsing methods...

[Sridhar Bhaskarla]

You can try Event Monitoring Service. It can provide some useful information. Look at the following document on using EMS monitors.

http://docs.hp.com/hpux/onlinedocs/B5735-90001/B5735-90001.html

-Sri

[Robert True]

Here is a script I use for popping a dtterm window that displays the output from the cmclstat cmd. I keep it open on my w/s continually, it updates by running the cmcluster cmd per the parameter passed to it. My support people use it for a simple status of the cluster during off hours. It is not bullet proof, but works for the purpose I have. Feel free to use / modify it if you want.

[Robert True]

Opps, needed to attach this script, which does the cmclstat for display

[Ralph Grothe]

I don't know of an API plugin for MC/SG stuff, that's why I usually run the cmviewcl command with varying options as forked child from a Perl script and parse it's output in the parent, which I usually place in a LoL for later easy access.

Btw. probably the most simple monitor that I usually run in one term to watch the packages' start/stop is this silly oneliner:

while :;do /usr/sbin/cmviewcl -l package;sleep2;clear;done