How to detect MSSQL cluster failover?

[Anthony Montibello]

NC_net as well as some other plugins also offer WMI query capability.
NC_net can do this through Active checks, using check_nc_net instead of
check_nt.
(Check_nc_net is compatible with all windows plugins that use check_nt).


Tony (Author of NC_Net)

On Mon, Aug 17, 2009 at 10:38 AM, Marco Tirado <marco.tirado at gmail.com>wrote:

> Hello Jon:
>
> Thank you for the information, I guess the snmp option is the quick and
> dirty way to go. I have never worked with WMI before, however I it is never
> late to start.
>
> Is it possible to access the MSCluster namespace using NSClient++?
>
> We use NSClient++ for accessing performance counters at the moment but we
> have not experimented with WMI yet.
>
> Regards
>
> Marco
>
> On Fri, Aug 14, 2009 at 6:51 AM, Jon Angliss <jon at netdork.net> wrote:
>
>> On Wed, 12 Aug 2009 15:08:56 +0200, Marco Tirado
>> <marco.tirado at gmail.com> wrote:
>>
>> >Hello users:
>> >
>> >I would like to know what is the easiest way to detect when a failover
>> >occurs in an MSSQL cluster. I need a simple check that tells me when our
>> >database cluster fails from physical node "X" to node physical node "Y"
>> >
>> >Has anybody done this? Maybe with a passive check?
>>
>> I used to do a quick and dirty way and use the SNMP sysName, and look
>> for a specific value.  If it changed from one name to another, it had
>> failed over...
>>
>> ./check_snmp -H host -v 1 -c public -o .1.3.6.1.2.1.1.5.0 -s
>> "expectedname"
>>
>> Or, if you've had experience with WMI, you can hit the MSCluster
>> namespace...
>>
>>  http://technet.microsoft.com/en-us/library/cc780572(WS.10).aspx<http://technet.microsoft.com/en-us/library/cc780572%28WS.10%29.aspx>
>>
>> Enjoy :)
>> --
>> Jonathan Angliss
>> <jon at netdork.net>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090817/5bed064b/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
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
-------------- next part --------------
_______________________________________________
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