Maybe Michael should go away more often. I seem to get a lot more done when he’s out.
Today, I added the third node to the Hyper-V R2 cluster we’re currently testing. When I did, VMM freaked out and all of the guests on the other two nodes went into a warning state. The error they displayed:
Warning (13921)
Highly available virtual machine <INSERT NAME> is not supported by VMM because one or more of its network adapters is not configured correctly.
Recommended Action
Ensure that all of the virtual network adapters are either disconnected or connected to highly available virtual networks.
So, how do we fix this issue? You use Google, of course. A quick Google-ing gave the following information (edited for grammar):
For a VN [Virtual Network] to be marked as HA, the location and tag of the VN in all nodes must be the same. For each VN in the cluster[, be sure that]:
Our problem, specifically, was related to the network tagging. To fix the tag, do the following:
- Open VMM, and navigate to the “Hosts” view.
- Right click on one of the hosts and select “Properties.”
- Navigate to the “Networking” tab.
- Once, there, you’ll need to click each network (in this case, we have two) and add text to the “Network tag:” field. Keep in mind that these tags will need to be the same across all your hosts in order to make them highly available.
- Rinse and repeat for the rest of your hosts.
- Once you finish tagging, you’ll need to refresh the cluster node in VMM.
That fixed our problem. Maybe it will help you.
More information here in the “Troubleshoot ‘Unsupported Cluster Configuration’ Status for a Highly Available Virtual Machine” section.
