Shulou(Shulou.com)05/31 Report--

In this issue, the editor will bring you how to solve the "vSphere HA virtual machine failed to failover" error in vCenter Server problem. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

"vSphere HA virtual machine failed to failover" error in vCenter Server (2034571)

Today, I encountered such a problem: in VMware virtualization, there is an alarm of "vSphere HA virtual machine device failover failure", but my virtual machine is running normally. The following is the official reason and solution of the problem given by VMware:

Symptom

This error may appear on the virtual machine in a cluster where the isolation response is set to remain powered on while the host is isolated.

VSphere HA virtual machine failover failed

The virtual machine continues to run without problem.

Intention

The following information is provided:

Clears the vSphere HA virtual machine failover failure error in the virtual machine.

If an vSphere HA virtual machine failover failure error occurs, handle the error.

Reduce the occurrence of vSphere HA virtual machine failover failure errors.

Reason

This behavior occurs whenever the high availability master agent declares that the host is dead. However, the virtual machine continued to run without any events. This alert does not mean that HA has failed or stopped working. When this alert is triggered, it means that one or more virtual machines cannot be started by hosts in a cluster protected by HA.

The possible reasons for this are:

The host is still running, but has been disconnected from the network. The host isolation response for the cluster is set to remain powered on:

When a host becomes a network isolated host, the remaining hosts in the cluster do not know whether the host has crashed or has just been disconnected from the network. Therefore, the remaining hosts will attempt to power up the virtual machine that was last recorded as running on the isolated host. When the "leave" power is turned on, network-isolated hosts keep virtual machines up and running without trying to power them off, thus keeping files locked. In the case of quarantined host locked files, the remaining hosts will not be able to perform boot tasks on the virtual machine, causing an alarm to be triggered.

The host is still running, but has been disconnected from the network. The host isolation response of the cluster is set to shutdown or shutdown:

Using this host isolation response, the host will attempt to send a shutdown or shutdown command to the virtual machine it is running when it is recognized that it is quarantined. Once the virtual machine is completely shut down and the original isolated host no longer has locks on the virtual machine files, the remaining hosts in the cluster will be able to obtain the locks needed to start the virtual machine. If the virtual machine is not shut down successfully or the lock is not released, an alert is triggered.

The host failed and the virtual machine storage was degraded. The remaining hosts in the cluster cannot contact the storage device and cannot power up the virtual machine, causing an alarm to be triggered.

Resolution

This is the expected behavior in VMware vCenter Server 5.0. X 、 5.1 . X and 5.5. X, because the virtual machine continues to run without accidents, you can safely ignore this issue.

To clear alerts from a virtual machine:

1. Select the virtual machine that triggered the alarm.

two。 Click the alarm tab, and then click the trigger alarm button.

3. "right-click the vSphere HA virtual machine failover failure alert, and click clear."

Note: if this alert is on multiple virtual machines, you can select the host, cluster, data center, or vCenter Server object in the left pane and proceed to step 2 to clear the alert in fewer steps.

To reduce the likelihood of this problem, do the following:

Use multiple management networks. For more information, see vSphere High availability deployment Best practices.

Ensure that the data storage heartbeat within the vCenter Server communicates properly so that HA can run efficiently in the event of management network problems.

For example, if you are using SAN and IP-based storage, mount two SAN-based data stores to hosts in the cluster so that HA can use them instead of IP-based storage. Or, if only IP-based storage is used, consider isolating one or more networks for storage from those networks that are used to manage the network.

This is how the "vSphere HA virtual machine failed to failover" error in vCenter Server problem shared by the editor is solved. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.