When you add new nodes with a higher operating system to your Windows Failover cluster environment, you will receive warnings about "Functional Level"
mismatch in your failover cluster logs.
The main reason for these warnings is that the operating systems and functional levels of the clusters connected to the nodes in your environment are different from each other.
You can follow the steps below to change the functional level compatibility;
- To view the Failover Cluster Functional Level version
Get-Cluster | select ClusterFunctionalLevel
- To upgrade the Failover Cluster Functional Level version
Update-ClusterFunctionalLevel
- To view the upgrade process of the Failover Cluster Functional Level version
Get-Cluster | select ClusterFunctionalLevel
- In Windows Server 2019 the Clustering team introduced a new PowerShell cmdlet to check how many nodes of the cluster are running on which level
"Get-ClusterNodeSupportedVersion"
helps you to identify the Cluster Functional Level and the Cluster Upgrade Version.
The table below shows the values and each corresponding functional level:
For more detailed information;
- Cluster Operating System Rolling Upgrade
- In-Place Upgrade Windows Server 2016 to Windows Server 2019
- Failover Cluster In-Place Upgrade Tip & Trick
- Failover Cluster Node Quarantine Fix
Have a nice day!
Good post but I was wondering if you could write a litte more on this subject? I’d be very thankful if you could elaborate a little bit further. Thanks!
Great post. I was checking continuously this blog and I am impressed! Extremely useful information specially the last part 🙂 I care for such info much. I was seeking this particular information for a very long time. Thank you and best of luck.
Hi my family member! I want to say that this article is awesome, great written and come with approximately all vital infos. I?¦d like to peer more posts like this .
I like this site very much, Its a rattling nice place to read and find info .