-> From command prompt, execute below command to generate cluster.log in C:\Windows\Cluster\Reports.
Cluster log /g
-> From command prompt, execute below command to generate a verbose cluster.log in location C:\Windows\Cluster\Reports.
Cluster log /g /Level:5
-> Cluster.log generated from command prompt will be using Coordinated Universal Time (UTC) and not local time.
-> From powershell, execute below command to generate cluster.log of all nodes to one destination directory with local time stamp.
Get-ClusterLog -UseLocalTime -Destination .
-> We cannot specify level of details in Cluster.log if generated from powershell.
-> Sometimes, level of details while generating cluster.log can be important during troubleshooting. Always On Availability group can be a good example. This can be solved by changing “VerboseLogging” property of Availability Group resource in Cluster Administrator from default value 0 to 2. The resource should be made offline and online or wait till next failover to have this take effect and then generate the cluster log again.
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.