Website under construction

6.
Reinstall roles, features, and software being used on the cluster (for example, Hyper-V, SQL, and 
so on). 
7.
Test failovers. 
8.
If everything proceeded properly, repeat steps 2 through 7 on the remaining node(s). 
While some nodes are running Windows Server 2012 R2 and the others are running Windows Server 
2016, you will be running in a mixed operating system mode. Associated with this mode is your 
cluster functional level. While you are in this mixed operating system mode of your cluster, running 
the following Windows PowerShell command from a Windows Server 2016 node returns a value of 8 
for Windows Server 2012 R2 and a value of 9 for Windows Server 2016 nodes: 
Get-ClusterNode | ft -auto NodeName, MajorVersion, MinorVersion, BuildNumber, NodeHighestVersion, 
@{Expression={$_.NodeHighestVersion -shr 16}; Label="NHV.Cluster Functional Level";width=21}, 
@{Expression={$_.NodeHighestVersion -band 0xffff};Label=”NHV.Cluster Upgrade Version”;width=24}, 
NodeLowestVersion, 
@{Expression={$_.NodeLowestVersion -shr 16}; Label="NLV.Cluster Functional Level";width=21}, 
@{Expression={$_.NodeLowestVersion -band 0xffff};Label="NLV.Cluster Upgrade Version";width=24} 
For example, Figure 2-45 shows the Windows PowerShell output with just one node remaining to be 
upgraded. 
Figure 2-45:
Nodes that can be upgraded 
The output indicates the NodeHighestVersion and the NodeLowestVersion. When these two values 
match on all nodes, you can upgrade the cluster functional level by running the new Update-
ClusterFunctionalLevel cmdlet, as presented in Figure 2-46. 
Figure 2-46:
Updating the functional cluster level 
When all nodes in the cluster have been upgraded to Windows Server 2016, run the Windows 
PowerShell command again; this time you will get a value of 9, indicating that all nodes are upgraded, 
as depicted in Figure 2-47. 

---

44 
CHAPTER 2 | Software-defined datacenter