On Tue, 5 May 2009 15:05:49 -0400, Anirudh Srinivasan <srianir...@gmail.com> wrote:
>Hello Friends, > >Is it possible to monitor a service i.e "exchange service" on the clustered >environment instead of monitoring it individually on each clustered node. Sounds like you need to monitor the clustered IP instead of the individual IP addresses, and check for various services and their states there. The server will react, and respond accordingly because the cluster services will handle the requests. That being said, you'd probably still want something to monitor the cluster services themselves to see if there was a failure. >Currently "exchange services are being monitored individually on each >clustered node. >FYI : The server is a Windows clustered environment. > >Can i use check_cluster ?? > If i am not wrong check_cluster works only for Linux cluster. Is that >right?? Check cluster will take the results of several hosts/services and respond based on the thresholds defined. For example, if you have several web servers that form a web farm, each server is checked independantly. The check_cluster plugin takes the output of the service checks, and gives you back an OK, WARNING, CRITICAL based on your threshold. See: http://nagios.sourceforge.net/docs/2_0/clusters.html A similar example is provided there. >Please advice me on what plugin to use to achieve this. >Thanks -- Jonathan Angliss <j...@netdork.net> ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ 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
