Hello All,
Our new director would like to monitor EVERYTHING from BB/Hobbit. We have been monitoring our UNIX and Storage Devices for a few years now. Now that I have windows servers to monitor, I'd like to know if anyone has a decent way to monitor Windows Clusters? I had a thought to monitor by ping each node in the cluster, and the cluster name, ie:
Nodea - Application Offline Nodeb - Application Online Clustername - Application Responding @ This address
How would you set up resource (process) monitoring for an Active / Passive cluster? Or an Active / Active cluster?
This is in response to a problem that has been occurring on a new 24x7 Windows server blue screening daily, in spite of all the "fixes" that have occurred to solve the problem (more hardware, patches, reload os, etc, etc).
We'll soon be moving the application to an AIX server, but I'll have the same questions on an HACMP cluster at that point :)
TIA
Al Jeffcoat IBM Certified Support Specialist, AIX Enterprise Storage Administrator System Programmer II (321)843-1051 ajeffco at orhs.org
This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s) named above. If you are not the intended recipient, any review, use, or distribution of this e-mail message and any attached files is strictly prohibited. This communication may contain material protected by Federal privacy regulations, attorney-client work product, or other privileges. If you have received this confidential communication in error, please notify the sender immediately by reply e-mail message and permanently delete the original message. To reply to our email administrator directly, send an email to: postmaster at orlandoregional.org . If this e-mail message concerns a contract matter, be advised that no employee or agent is authorized to conclude any binding agreement on behalf of Orlando Regional Healthcare by e-mail without express written confirmation by an officer of the corporation. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Orlando Regional Healthcare.