Hello,
The state of one of our "Cluster Node" objects (Windows Cluster Management Monitoring MP) changed from "Healthy" to "Warning" as a result of its Node State Monitor detecting a state of '3' more than 5 days ago (looks like a WMI query similar to 'SELECT * FROM MSCluster_Node' in the ROOT\MSCLUSTER namespace). A check of the server clearly showed that it was healthy and part of the cluster. Curiously, its operational state remained unchanged despite the fact that the monitor's polling interval appears to be set to 60 seconds (i.e. no overrides are set for this mornitor).
I had to manually perform a "Recalculate Health" for the node's state to return to "Healthy".
Any ideas what could have caused the issue and how I might prevent it from happening again?
Thanks,
Larry
The state of one of our "Cluster Node" objects (Windows Cluster Management Monitoring MP) changed from "Healthy" to "Warning" as a result of its Node State Monitor detecting a state of '3' more than 5 days ago (looks like a WMI query similar to 'SELECT * FROM MSCluster_Node' in the ROOT\MSCLUSTER namespace). A check of the server clearly showed that it was healthy and part of the cluster. Curiously, its operational state remained unchanged despite the fact that the monitor's polling interval appears to be set to 60 seconds (i.e. no overrides are set for this mornitor).
I had to manually perform a "Recalculate Health" for the node's state to return to "Healthy".
Any ideas what could have caused the issue and how I might prevent it from happening again?
Thanks,
Larry