<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000099"> One of our admins is actively migrating us from Server 2003 to Server 2008 and using the built-in clustering capabilities of '08 to enable service-level failover. So far, he's done so with Exchange, print server services, and SQL. I'm wondering how to best monitor shares resources on Windows hosts from Nagios. At present, we use nsclient++ to watch the physical servers. This is good for basic checks of load average, memory, local disk consumption, etc. I can even monitor services that are running. No, I know I can monitor anything that's accessible from an IP and port, but I'm somwhat stumped on other resources... For example, we have two physical Exchange servers. They're in a cluster and the various Exchange services are only active on one node at a time. I can watch OWA as its accessible from an IP and port, but the Exchange services themselves will stop on one server and start on the other if a server fails. Nagios can't dynamically adjust to watch this service on the new node. It will only yell that's its down on the failed node. Clustered file storage is another example. Again, I can watch the local CPU, memory, and local C: drive, etc. But let's say its sharing a large volume as drive F:. I can watch this fine on the primary node, but if it fails over, its no longer accessible from that node as its being shared on the new active node. I'm curious if any Nagios users are using clustered resources on the Windows side and how you handle service failover of services that aren't necessarily accessible by IP and port... <pre class="moz-signature" cols="72">-- A. Davis Email: <a class="moz-txt-link-abbreviated" href="mailto:nccomp@gmail.com">nccomp@gmail.com</a> "There is no limit to what a man can accomplish if he doesn't care who gets the credit." - Ronald Reagan </pre> </body> </html>