[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: "Etienne Grignon" <etienne.grignon (at) gmail.com>
- Date: Wed, 11 Jun 2008 11:09:29 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=aEoW6PpiEW4nFJ1NKQkGhIPNil7O4Irl6U5HpGatem8=; b=Fp0vBYWqHUINjEsQCZP0F0UzbdsQWEz9xEkikofPSqBzOe3hwuBKN+G1jLWXPVPWtH iBNrO/IUuJ8HUwahqHcFsTwSWBaxRRCycsgbhH6jWIwHycHPISoiMM3U/eVeKKhNaKQW uTQB6zQyFxIWex0SL7CsNr3zrjcXyeQzS6ClE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=GeArr9nZVXZC2O5hYLAC0IuQLpxNF4Y0S2qfIjpdktKFUueb7GBQfCCKOwAuXrggoi sGqcbtn0X0ja8bOrVK6Nt/J6M9cLQT575TARr1MjsBQhFX4/kTc+N8i7Dfpf3Ba/a+iN EWn2jSizukhUf+7IgMZ/7uLtk8xESSqqKaS1Y=
- References: <9F4B8A70C3E2D142AF209DB53DBC1D5101D8FB30 (at) MUN2WSP05011.global.pioneer.com> <68e737a10806031421j786acd50vd4379bab8c527383 (at) mail.gmail.com> <9F4B8A70C3E2D142AF209DB53DBC1D5101DD30F4 (at) MUN2WSP05011.global.pioneer.com>
Hi Padraig,
2008/6/5 Lennon, Padraig <Padraig.Lennon (at) pioneerinvestments.com>:
> 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?
>
You will have to comment the line in bbwin.cfg on node 2 until the
second node becomes the active node. It is a manual action which is
not a good idea I know but there are no other alternatives for that.
However, you can try to remove the specific F rule and change the
default rules in % to be sure you will always have 50g left on your F:
drive so you won't get alerts on the second node because the F: drive
is missing.
Regards,
--
Etienne GRIGNON