Thanks Etienne,
I have implemented those changes.. All look good. How do you deal with
event log errors? I was thinking a combo test would work..
A few other issues:
Say I wanted to monitor a shared disk F: on the cluster. The shared
drive is 1TB in size. For the moment the disk is on node1 of the
cluster. Now I want to alert only when the disk gets to 50gb left. This
is easy to do in the bbwin.cfg file on node1.
Suppose now we have a failover of the resource to node2. It has no idea
about the 50gb limit and back on node1 it is in an alert status because
it can't find the F: drive.
How do I get around this?
Thanks for your help
Padraig Lennon
Senior Systems Engineer
Production Services
Pioneer Global Investments (Dublin)
5th Floor Georges Quay Plaza, Dublin 2
ext: XXXX
Direct dial: 00353 1 480 2081
-----Original Message-----
From: Etienne Grignon [mailto:user-87c74c1037a4@xymon.invalid]
Sent: 03 June 2008 22:21
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Windows Cluster Monitoring Advice
Hello Padraig,
2008/6/3 Lennon, Padraig <user-7738cfcc6ae0@xymon.invalid>:
Hi everyone,
I have a requirement to monitor some 2 node Windows 2003 File Clusters
. I
would like to monitor them with BBWin but I have the following
questions:
Should I install the bbwin client on both nodes and activate only one
of the
nodes for monitoring? With this setup I miss monitoring the local C/D
drives
on each node.
Is it possible to make bbwin a clustered application? (i.e. one that
would
failover using the MS clustering mechanism)
The cluster.exe supplied with the bbwin package only shows the cluster
groups, not the individual items within the groups. Has anyone written
any
extended cluster checks that they would possibly share with me? If not
I can
write my own. I'm sure I can get this information with WMI.
At the moment I setup the bbwin client on one of the nodes and then
change
the registry entry to use the cluster name (i.e I install on a node
fileclus1n1 and change the registry key to fileclus1). Is this the
correct
way to setup the monitoring? Any advice would be greatly appreciated.
I realise the question should probably be on the BBWIN mailing list,
but I
thought I would have more chance of getting a reply on this list.
This is how I monitor MSCS clusters. I install BBWin on both nodes. I
also install the cluster.exe external to be run on both nodes.
The cluster.exe external will check that every resource of the MSCS
cluster is online. If the node switch to the other node, you will get
an alarm on it until you acknowledge the alarm by deleting a temporary
file on each node.
I hope it will be enough for you.
Regards,
--
Etienne GRIGNON