[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] Windows Cluster Monitoring Advice
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] Windows Cluster Monitoring Advice
- From: Buchan Milne <bgmilne (at) staff.telkomsa.net>
- Date: Tue, 3 Jun 2008 14:56:56 +0200
- Cc: "Lennon, Padraig" <Padraig.Lennon (at) pioneerinvestments.com>
- References: <9F4B8A70C3E2D142AF209DB53DBC1D5101D8FB30 (at) MUN2WSP05011.global.pioneer.com>
- User-agent: KMail/1.9.7
On Tuesday 03 June 2008 13:13:56 Lennon, Padraig wrote:
> 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.
How you monitor clustered nodes does not depend on the monitoring software (or
even the OS).
What we typically do is monitor the infrastructure aspects (disk, cpu, memory,
cluster middleware) on all cluster nodes, and the clustered services (e.g.
database, IP addresses, applications etc.) independently (e.g. with the
cluster group name).
I am doing this with Windows, Solaris and Linux clusters.
Regards,
Buchan