Hello,

 I've been asked to check whether members of a number of sun clusters we have 
here have 'failed over' from primary to secondary. The clustered machines are 
all Oracle Databases. The idea is that if one node goes down then the secondary 
in the node becomes the primary Database. Apparently this is all achieved 
through Sun Cluster, which I have to admit I'm not well versed on.
 
 I did find a plugin in the nagios exchange that checks the components of Sun 
Cluster - things such as IPMP, resource groups and quorum. But what I don't 
think it offers is to tell if one node fails over to another. It could just be 
that I don't know enough about Sun Cluster to correlate the options in the 
check. 

Here's the usage for the check:

[db07-dc2:~] root% /opt/nagios/libexec/check_suncluster -h

Usage: check_suncluster [-t, -q, -g, -G resource-group, -r, -R resource, -i]
Usage: check_suncluster --help

Sun Cluster check plugin for Nagios

-t: check transport paths
-q: check quorum
-g: check resource groups
-G: check one individual resource group
-r: check all resources
-R: check one individual resources
-i: check IPMP groups

Does anyone out there have any suggestions on how I may get this check or 
perhaps another one you may know of to indicate whether a Sun Cluster 
(Database) node fails over and a secondary becomes primary?


Thanks in advance,
Tim

------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Reply via email to