The simplest way to monitor a Windows active / passive node is to set up a TCP Service Monitor to check the file system on the node.  When the active server becomes passive, the file systems should move on to the passive server, which then becomes active.

A TCP monitor that is configured to check the file systems (and fail when they're not detected) will suppress alerts (such as Limited Performance Data, which would be generated by a performance monitor) because the file system is not down, it has simply failed over.

When you configure a TCP monitor, enter bsdsysv in the String to Send field of the monitor template.

In the Critical field of the String to Receive option, enter a list of drives as an inverse regular expression.  For example: (C:).*(H:).*(F:).*(L:).*(Q:).*(K:).*(S:).  


Drives must be in the correct order for the monitor to work properly.

You can retrieve a list of system drives by polling the agent from within Uptime Infrastructure Monitor.  To do this, click the name of the system in My Infrastructure tab and then click the Poll Agent option in the navigation pane.  Look for output similar to the following:

bsd: 0 sysv: 0 C: bsd: 1 sysv: 1 H: bsd: 2 sysv: 2 bsd: 3 sysv: 3 F: bsd: 4 sysv: 4 L: bsd: 5 sysv: 5 Q: bsd: 6 sysv: 6 K: bsd: 7 sysv: 7 S:

Error rendering macro 'contentbylabel'

parameters should not be empty