Sensors in Windows failover cluster environment

Hello,

I'm afraid that can't be changed, due to the way the inner workings of WMI are implemented. The reason is, if the cluster switches, then even though the IP stays the same, the MAC address changes, and unfortunately WMI connections are linked to the MAC-Address. PRTG establishes a new connection every 60 minutes, and this is probably the time you had to wait. But this time will most likely not be changed, as establishing a WMI Connection is unfortunately horribly slow (over 20s), so we can't do that before every sensor scan.
We would recommend to monitor with "hardware-near" sensors directly on the physical nodes (not via the cluster-IP), and then use service-sensors (HTTP, SMB-Sensors, etc..) to check the clustered service.

Best regards.

Hello Torsten, i unfortunately can´t do that. Means I can not monitor the hardware itself because there are a couple of sql server instances and belonging windows services running. Each SQL server instance has an own ip address and an own hostname of course. So when the mentioned services are stopped on the first node and started on the second then ia have to monitor these processses on the second. and i can do this only by monitoring the ip address of the cluster services.

if i would use sensors to monitor these services on the machine itself i would get failures on that machine that is currently NOT hosting that services.

@Torsten:

FYI: i just performed another failover and see that all services are monitored correctly but my "hardisk-usage-sensor" is still erroneous.

The suggestion was, to monitor services, like the SQL via the Cluster IP, with SQL-Sensors (not WMI SQL Sensors, because they will face the same issue), and then all hardware sensors, like harddisk-usage on the physical nodes. With WMI, there is no other way, sorry. But that is not PRTGs fault.

I can not cover the harddisk-usage on the physikal disk because that disk is not part of that node anymore...

as you wrote PRTG establishes a new connection every 60 minutes. i was waiting almost 120 minutes but the status of that sensor ist sill "erroneous"

any ideas? Thank you!

the funny thing is when i replace the configured hostname with the cluster ip address all service states show errors again. placing the hostname again everything is green but the harddisk-sensor...

OK, i got it. As mentioned in PRTG i had to use the drivletter and not the ID. Everything is working fine now :-)

Changing the Hostname/IP actually also creates a new WMI Connection.