Has anyone had any thoughts on this? It is really the only thing lacking in our Windows monitoring environment.
Simply re-introducing the optional hostname directive in bbwin and running two instances on each host seems like it would work. Bbwin would first check the .cfg, then the registry, then default to the machine hostname.
Aaron Zink Manager, Corporate IT eHarmony.com 626.795.4814
-----Original Message----- From: Aaron Zink [mailto:AaronZink at eharmony.com] Sent: Thursday, June 12, 2008 17:06 To: hobbit at hswn.dk Subject: RE: RE: [hobbit] Windows Cluster Monitoring Advice
Hello,
I too am using bbwin extensively to monitor our windows environment, and we have several clusters. In a windows cluster, monitoring some services per-client will work (especially for tcp monitors), but it is not an ideal solution for several reasons:
Active-passive clusters have services and ports that will be running on one node but not the other, making these impossible to monitor. Bbcombotest can sort of be used, but it does not work very well for this.
Checking a file on a shared drive wouldn't work.
externals.exe to monitor the cluster is nice but there are times when the cluster is "fine" according to cluster manager, but a shared disk is not accessible.
I had an idea to monitor clusters, and was wondering about the feasibility: Re-add the HOSTNAME configuration entry into the bbwin.cfg file, and run two instances of bbwin.exe on the client. One would be the default (reading the hostname from the machine), and the other would be manually configured in the .cfg to the cluster name. This is currently not possible because the hostname can only be overridden in the registry, where both bbwin instances reference.
I don't have a development environment set up to test this myself, but in theory it should work.
Aaron Zink Corporate IT Manager eHarmony.com 626.795.4814
- Aaron Zink
-----Original Message----- From: Lennon, Padraig [mailto:Padraig.Lennon at pioneerinvestments.com] Sent: Thursday, June 12, 2008 03:50 To: hobbit at hswn.dk Subject: RE: [hobbit] Windows Cluster Monitoring Advice
Thanks Etienne,
Padraig Lennon Senior Systems Engineer Production Services Pioneer Global Investments (Dublin) 5th Floor Georges Quay Plaza, Dublin 2 ext: 2081 Direct dial: 00353 1 480 2081
-----Original Message----- From: Etienne Grignon [mailto:etienne.grignon at gmail.com] Sent: 11 June 2008 10:09 To: hobbit at hswn.dk Subject: Re: [hobbit] Windows Cluster Monitoring Advice
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
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk