A Microsoft Cluster Troubleshooting Guide
Posted by Philip Elder on 21 April 2014 01:02 PM
Here are some of the tools we can use when troubleshooting a cluster, Scale-Out File Server, Hyper-V, and other cluster issues:
Failover Cluster Manager
The FCM gives us the ability to dig into the various Windows Logs and delimit them by time, node, and log type.
We set up a few different queries out of the box. One with everything Cluster, Failover Clustering, and Hyper-V related. We then create a subset of queries. The various queries get saved to a local folder on the management DC/RSAT system.
The Get-ClusterLog PowerShell commandlet allows us to pull the full log set from one or all nodes. Note that the default output folder is NODEC$WindowsClusterCluster.LOG (C:WindowsClusterCluster.LOG) unless specified in the command.
This log can be very busy and a bit of a challenge to work through. If one has a good idea of what to look for then the log can be quite informative.
EDIT: The Default cluster log location is C:WindowsClusterReportsCluster.log
Microsoft Message Analyzer
This is an in-depth tool. There is no way around it. Thus, a learning curve is required.
However, there is an amazing amount of information that we can then have at our fingertips and not only that colour coded!
One can use a series of filters under the log file settings to delimit by time period among others.
We can set up our columns:
Once we have our Cluster column, for example when looking for a problematic cluster component, we can set up a filter:
And that is just the tip of the iceberg. One will need to spend some time with this tool to really get into its abilities such as colour coding source node, information levels, and so much more!
Please check the Message Analyzer Blog for more information.
Note that an absence of System Centre and its components is deliberate. We find, at least at this time, that Failover Cluster Manager provides a far superior cluster management experience.
Chef de partie in the SMBKitchen ASP Project