Shulou(Shulou.com)06/01 Report--

It is believed that many inexperienced people don't know what to do about how to update the diagnosis and troubleshooting of WSFC2016. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

WSFC2016 has also made some updates to the cluster log

First of all, the parameter-UseLocalTime is added when generating ClusterLog. The default is the time to generate GMT. In China, it seems that we need to add eight more hours, so if you can confirm that your cluster node does not have a time zone problem, then you can use the-UseLocalTime parameter to output the cluster log of the local time zone.

# dump all nodes in the current cluster, and log the last five minutes to the network path, using the local time display.

Get-ClusterLog-TimeSpan 5-UseLocalTime-Destination\\ 10.0.0.2\ log

If you open the log, you can see that the time uses the node's local time zone, that is, the Beijing time zone.

These are the first changes in 2016 log diagnostics

The second change, Lao Wang found that the diagnostic log is quite different from that of 2012R2. The log of 2012R2 is like this after it is opened, it is directly a piece of diagnostic information.

The cluster log in 2016 is more intelligent. When we use get-clusterlog to obtain the cluster log, it will actually help us list the resource information and configuration information of the cluster in front of the log.

In addition to the cluster's resources and cluster configuration information, clusterlog also displays other cluster-related event manager events at the beginning

It will help us to synthesize the events of Operational logs,CAU,admin logs,DiagnosticVerose and show them together, providing us with an overall troubleshooting in a clusterlog.

We have been introduced in 2012R2, clusterlog, the default is to get the content under diagnostic, eliminate useless data, retain useful metadata information, display in clusterlog, for these logs are displayed in clusterlog, also through this mechanism, eliminate useless data columns in XML, and only show key and useful metadata information.

Diagnostic, an event manager channel, is responsible for recording every operation performed during the operation of the cluster, including the underlying call plug-in, which is used for managers to debug and view, but because the log is growing, it is inconvenient to view in the event manager, so it can be obtained through clusterlog to get a more intuitive view. As we mentioned in 2012R2, Diagnostic defaults to level 3-level information recording. If this level does not help us locate the problem, we can collect logs at a more detailed diagnostic level by setting cluster log to 5, push it, but at that time, officials have always stressed that setting it to 5 will lead to the rapid growth of the log, which will have an impact on the operating performance of the system, so we need to set it back in time after a brief troubleshooting.

But in 2016, Microsoft optimized this, relieved the performance concern, and instead set up an event manager channel DiagnosticVerbose, which records cluster operation information according to level 5 level. If we need to perform cluster error at level 5 level, we can view this event manager channel directly. In fact, when we get clusterlog, we can also see the contents of this channel. Below this log is the cluster log from level5 in DiagnosticVerbose

The following Cluster Logs begins with logs from the Diagnostic Level 3 level

So now we don't have to change the cluster log level most of the time, because the default log has level5 and level3 levels, and Microsoft implements a parallel event manager channel, so we don't have to worry about performance!

The above is about the changes of ClusterLog in 2016, updating the long-awaited localtime function, ClusterLog has also added other channels to facilitate overall troubleshooting, and the performance problems caused by the high level of level have also been solved.

In addition to ClusterLog, Microsoft also provides another new feature for cluster troubleshooting, namely the dump mode of Dump files.

Active Memory Dump dump mode has been added, which may be a very useful function for a Hyper-V cluster. In the past, if we ran a lot of virtual machines in a Hyper-V, when we generated dump, the dump would essentially include host and virtual machine memory, and the virtual machine memory pages might not be necessary for us to debug at the host level, when we choose the active memory dump. The dump will include only the memory pages of the host, and the memory pages of the virtual machine will be filtered, and the final size will be only 10% of the full dump

After reading the above, have you mastered how to update WSFC2016 for diagnosis and troubleshooting? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.