How to troubleshoot Hyper-V cluster issues

Case



You need to check the operational health of a Hyper-V server or Hyper-V cluster. You need to perform a technical audit of the Hyper-V operations to determine the root cause of slow performance issues or cluster errors. This article provides high-level guidance on how to troubleshoot Hyper-V cluster issues.





Solution



Carry out the steps below to troubleshoot Hyper-V cluster issues:



- Check all Hyper-V cluster logs. You can either use Powershell or the Windows Failover Cluster mmc console.



- Investigate all operating system event logs on the machines running the Hyper-V server role.

- Check all Hyper-V host hardware vendor's logs and overall health status in the out-of-band management console (IPMI).

- In the case of a Hyper-V cluster, run the Microsoft Hyper-V best practices analyzer. The Best Practices Analyzer scans your computer using rules based on Microsoft Hyper-V WFC best practices and reports the results. Each best practice rule includes details about how to comply with the rule. To run the Best Practices Analyzer for Hyper-V on Windows server, execute the following cmdlets in an elevated Powershell window.

#First detect the name of the BPA model ID(s) you are interested to run a scan for.

Get-BPAModel

#Pipe the modelID into the Invoke cmdlet.

Get-BPAModel -ModelID | Invoke-BPAModel

#Get the BPA results for your model ID(s)

Get-BpaResult -ModelId "Microsoft/Windows/Hyper-V" | Out-File -FilePath C:ScriptsHyperV-BPA.txt

- Audit the status of all associated networking devices (firewall, router, switch) and storage devices (SAN, NAS).

- Examine all software-defined features you have configured in your Hyper-V cluster environment. These include VMQ, RDMA, RSS, SET and SRV-IO.

- Create a Hyper-V health report, which is created by a free Powershell script provided by Altaro.

- For performance issues, review the recommendations in the free Hyper-V performance e-book provided by Altaro.

- You can make use of additional Hyper-V cluster management and troubleshooting tools, a list of which is provided by Altaro.

- Follow along the Altaro Hyper-V networking best practices article.

For a more comprehensive troubleshooting approach when dealing with Windows Failover Cluster (WFC) issues, including failover clusters with Hyper-V, you can refer to my e-book entitled "Windows Failover Clustering Design Handbook". Remember that in all cases, it is better to spend time planning for a proper best practice design, instead of spending time troubleshooting Windows Failover Clustering issues.




https://stefanos.cloud/kb/how-to-troubleshoot-hyper-v-cluster-issues/

Comments

Post a Comment

Popular posts from this blog

How to perform hardware health checks in Windows

Image
Case You need to perform an overall hardware health check in a Windows machine, running either a Windows client or a Windows Server operating system. This article provides guidance on the steps to carry out to perform hardware health checks in Windows. Solution Carry out the steps below. - Thoroughly check all Windows event logs (Application, System, Security) for any warnings or errors which may be related to issues you are experiencing with your Windows machine. - Check the device management mmc console by running devmgmt.msc. Ensure that you choose to show all hidden devices from the View menu. If you notice any exclamation marks next to any device, you will need to re-install its driver from the respective manufacturer to ensure that there afterwards no warnings in the device management console. - Check the health of all your disks , either HDD or SSD. Follow instructions in the following KB article for steps to follow to check your disk health: https://stefanos.cloud/kb/how-to-ch...
Read more

How to resolve Group Policy error codes 8007071a and 800706ba

Image
Case You are running "Group Policy Update" on an OU inside the Group Policy Management Console in Active Directory but you are receiving RPC errors from your servers or domain-joined workstations, as shown in the example below. After a Group Policy Update, you come across Group Policy error codes 8007071a and 800706ba. This means that the local Windows Firewall is not configured properly to allow Group Policy (GPO) traffic. GPO traffic an be either remote GPO update or remote GP Resultant Set of Policy (RSOP) operations. Solution Option 1 Run gpedit.msc and create a new local group policy object which implements the following policies under Local Computer Policy --> Computer Configuration --> Windows Settings --> Security Settings --> Windows Defender Firewall --> Inbound Rules : The full configuration is shown below. After the above local group policies are configured on each domain server and workstation, you can start applying group policy objects to the dom...
Read more

FsLogix 2201 Public Preview release

Image
The FsLogix 2201 Public Preview release is now available for download from Microsoft. The change log is as follows: - Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service. - The OfficeFileCache folder located at %LOCALAPPDATA%MicrosoftOffice16.0OfficeFileCache is now machine specific and encrypted so we now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update. - Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server. - Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems. - FSLogix now correctly handles cases where...
Read more