How to Upgrade Failover Cluster Functional Level

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
  • 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;

Have a nice day!

How to Fix Failed While Applying Switch Port Settings ‘Ethernet Switch Port VLAN Settings’

If you get the following error when you want to make a VLAN change on your virtual server that you use on Hyperv;

"Error applying Network Adapter changes"
"The operation failed. Failed while applying switch port settings 'Ethernet Switch Port VLAN Settings' on switch 'Vs': One or more arguments are invalid (0x80070057)."

The root cause of this problem is the network mode you use on your virtual server, for example F5 virtual server appliance.
Let’s continue with the example there are more than one ethernet card over the F5 virtual server appliance, some of which are trunk and some are access mode.

You will get an error when you make the VLAN change on the Trunk mode card from the Hyper V Failover Cluster gui.

To fix this problem, you can follow the steps below;

  • First of all, we view the cards and their modes on the virtual server.
    Get-VMNetworkAdapterVlan -VMName servername
  • The tag is removed the network card with trunk mode.
    Set-VMNetworkAdapterVlan -VMName servername -VMNetworkAdapterName NIC3 -untagged
  • We define access mode and VLAN ID.
    Set-VMNetworkAdapterVlan -VMName servername -VMNetworkAdapterName NIC3 -Access -VlanId 715
  • To view the change made.
    Get-VMNetworkAdapterVlan -VMName servername

Have a nice day!


Hyper-V Virtual Switches

The structures Virtual Network and Virtual Switch, these are the components that our virtual servers running on virtualization platforms need for network communication.

Virtual switches also work exactly like physical switches ones. However, the type of your virtual switches will determine which function it will implement.

Virtual switches are very important and necessary for your virtual servers to communicate with your environment.
Therefore, all server virtualization platforms have virtual network technology.
Only the configuration parts can be different.
As a result, they all consist of 3 virtual network types.

  • External Virtual Switch
  • Internal Virtual Switch
  • Private Virtual Switch

External Virtual Switch
This switch type should be used when virtual machines are required to communicate with systems on the physical network.

It can be systems on a physical network, physical servers in your environment, virtual servers on Hyper-V or other servers & services outside.

“External Virtual Switch” are used for your virtual servers to communicate with the external environment.

In order for the External Virtual Switch you created to communicate with the physical network, it must be plugged into the physical network port.
Your virtual servers connected to Virtual Switch use your physical port as a common connection.

Internal Virtual Switch
It can only access your virtual servers in its host.
Therefore, it will only communicate with the host and other virtual servers in the host.
If you connect your virtual servers to Internal Virtual Switch, can’t communication to physical networks.
If you are going to use “Internal Virtual Switch”, you must also add a virtual network card connected to this switch on the Hyper-V host.
Your virtual servers with this type of virtual switch can run at 10Gbps.
Because communication is provided with VMBus protocol.
The existence of any physical port is not required.

Private Virtual Switch
It is used for your virtual servers on an existing host that you want to communication to only among themselves.
With Private Virtual Switches, you create a completely isolated network.
The existence of any physical port is not required.

For more information

Have a nice day!

How to Fix Hyper-V Failover Cluster Node Quarantine

In case you see quarantine status on your nodes in your Hyper-V Failover Clustering system,you should first examine the Cluster Events.

If the error code you will encounter while examining the cluster events is 1676, the action details you need to do are included in the error code. Don’t look for a different solution.

Open Windows Powershell –> Start-ClusterNode -ClearQuarantine

Check Cluster Node state –> Get-ClusterNode

Then go back to Failover Cluster Manager console and resume the paused node , taking fail roles back or don’t fail roles back.

Have a nice day!