- Get-ClusterLog dumps the events to a text file
- Location: C:\Windows\Clsuter\Reports\Cluster.log
- It captures last 72 hours log
- Cluster log is in GMT (because of geographically spanned multi-site clusters)
- Usage: Get-ClusterLog -timespan (which gives last "x" minutes logs)
- You can also set the levels of logs
- Set-ClusterLog -Level 3 (level 3 is default)
- It can be from level 0 to level 5 (increasing level of logging has performance impact)
- Level 5 will provide the highest level of detail
- Log format:
[ProcessID] [ThreadID] [Date/Time] [INFO/WARN/ERR/DBG] [RescouceType] [ResourceName] [Description]
Showing posts with label cluster log. Show all posts
Showing posts with label cluster log. Show all posts
Saturday, July 9, 2016
Anatomy of Hyper-V cluster debug log
Troubleshooting Live Migration issues on Hyper-V
- Check whether enough resources (CPU, RAM) are available at the destination host
- Make sure all nodes in the cluster follow same naming standard for vSwitches
- Check NUMA spanning is enabled or not. If NUMA spanning is disabled, VM must fit entirely within a single physical NUMA node or the VM will not start or be restored or migrated
- Constrained delegation should be configured for all servers in the cluster if you are using Kerberos authentication protocol for live migration
- Check live migration setting is enabled on Hyper-V settings
- Verify Hyper-V-High-Availability logs in event viewer
- Finally check cluster debug log (Get-Clusterlog -timespan) in C:\Windows\Cluster\Reports\Cluster.log
Subscribe to:
Posts (Atom)