A Bug in the Hyper-V Cluster

Bean was doing an experiment yesterday. After adding a new VLAN to the Hyper-V cluster and switch, he planned to use it as the designated Live Migration channel, I should have clicked Live Migration. As a result, I clicked quick migration, and an error was reported directly. The online guidance solution is very simple. Leave the entire cluster offline and click repair to fix it. Then the tragedy happened. After offline, the entire cluster was completely killed. How to fix the problem on render manager told me that there was a DNS problem.

Well, if there is a DNS problem, I will manually create the corresponding record, authorize the Full Control permission, and then restart the host. This time, the DNS error is lost, it means that the cluster name cannot be registered. After a long time, I finally found a bug in windows 2012 in a forum. It seems that exchange 2013 has the same problem, and the solution is simple:

Before creating a cluster, manually create the cluster name in AD and then disable it. Give the same name when creating the cluster, and then the corresponding DNS records will be automatically created.

Do not allow the cluster to automatically create AD records!

Do not manually create DNS records!

Solve the problem!

PS:

1. How to delete a problematic cluster:

Export VM;

Deletes a VM from a cluster;

Delete witness disk in the cluster Configuration Wizard;

Delete shared hard disks of other clusters;

Delete a cluster;

Run the following powershell command on each node server of the cluster to delete related information.

Import-module failovercluster

Clear-clusternode

2. Upgrade the firmware of SAN before creating a cluster to avoid many unexpected strange problems, such as unstable Live migration)

This article from the "Mapo tofu" blog, please be sure to keep this source http://beanxyz.blog.51cto.com/5570417/1304508