monitoring windows clusters

[Terry]

On Fri, Aug 28, 2009 at 1:11 PM, Jim Avery<jim at jimavery.me.uk> wrote:
> 2009/8/28 Terry <td3201 at gmail.com>:
>>The other thing
>> to consider is determining when a failover event has occurred.  I
>> imagine this can be done with eventlog monitoring but any other tricks
>> out there?
>
> For AIX HA/CMP failover, we edit the failover script so it sends a
> check to Nagios using send_nsca whenever it does the failover.
>
> ------------------------------------------------------------------------------


Another question.  Here's my check_cluster:
define service{
        use                     service-active
        host_name               omalindb02
        service_description     microsoft sql cluster
        check_command
check_service_cluster!1:1!1:1!$SERVICESTATEID:omalindb02a:microsoft
sql server service$,$SERVICESTATEID:omalindb02b:microsoft sql server
service$
        }
define command{
        command_name    check_service_cluster
        command_line    $USER1$/check_cluster --service -w $ARG1$ -c
$ARG2$ -d $ARG3$
        }

Here's the current status:
CLUSTER OK: Service cluster: 1 ok, 0 warning, 0 unknown, 1 critical

As you can see, we have 1 up and 1 down.  This is what I consider
good.  So, why would my service above be returning OK?   Doesn't the
1:1 mean that nagios will generate a CRITICAL alert if 1 or more
services in the cluster are in a non-OK state?

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Nagios-users mailing list
Nagios-users at 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