Creating and using vsphere ha clusters

VSphere ha runs in an ESXI host cluster environment. You must create the cluster, then have the host populate the cluster, and configure the vsphere ha settings to establish failover protection. Vsphere HA can be enabled for the cluster. A cluster with vsphere ha enabled is a prerequisite for fault tolerance. You can create an empty cluster first. After you have planned your cluster's resources and network architecture, you can add the host to the cluster through vsphere client and specify the vsphere ha settings for the cluster.

I. Creating a vsphere HA Cluster

Step 1 Create an empty cluster, and then add the host to the cluster. Complete the new Cluster Wizard by right-clicking the data center of the inventory tree and clicking New Cluster on the shortcut menu that appears, and do not enable vsphere HA (or DRS) at this time. Click the Finish button to close the wizard and create the cluster. An empty cluster is created at this time. The host is then added to the cluster using vsphere client.

Step 2 After you create an empty cluster, open vsphere HA. Right-click the cluster, and then, in the shortcut menu that pops up, select Edit settings. In the cluster's Settings dialog box, you can modify the vsphere ha or other settings for the cluster.

Step 3 Right-click the cluster, select Edit settings, and the first panel in the New Cluster Wizard can be used as the basic option specified for the cluster. In this panel, you can specify the cluster name and select one or two cluster features. After selecting Open ha, configure the vsphere ha settings for the cluster as needed, including host monitoring status, access control, virtual machine options, virtual machine monitoring, data storage heartbeat, etc.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/54/46/wKiom1R9rNSTsYZrAAPLmZBf82k982.jpg "title=" Qq20141201192057.png "alt=" wkiom1r9rnstsyzraaplmzbf82k982.jpg "/> Step 4 in the host monitoring state, if you choose to enable host monitoring, each host in the cluster is checked to ensure that it is running. If a host fails, the virtual machine is restarted on another host row. Host monitoring is also required for the vsphere Fault tolerance recovery process to function properly,

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/54/45/wKioL1R9rpTzzyz4AAP-C-rV1uE885.jpg "title=" Qq20141201192237.png "alt=" Wkiol1r9rptzzyz4aap-c-rv1ue885.jpg "/> In Access control, you can enable or disable access control for a vsphere ha cluster.

• Enable: Prohibit open virtual machine power operations that violate availability restrictions enable access control and enforce availability limits while preserving failover capacity. Do not allow any operations on the virtual to reduce the unreserved resources within the cluster and violate the availability limit.

• Disabled: Allows access control to be disabled for open virtual machine power operations that violate availability restrictions. For example, you can still perform this operation even if the power to the virtual machine is turned off and the failover capacity is insufficient. When you do this, no warnings are displayed, and the cluster does not turn red. If the failover capacity of the cluster is insufficient, VSphere ha can still perform a failover and use the virtual machine Restart priority setting to determine which virtual machine to turn on power first.

In the access control policy, if access control is enabled, VSphere HA provides 3 mandatory access control policies: The number of host failures allowed by the cluster, the percentage of cluster resources retained as failover space capacity, and the specified failover host.

Step 5 The default virtual machine settings control the restart order (virtual machine Restart order priority) of the virtual machine and how vsphere ha responds to loss of network connectivity between hosts (host isolation response). These settings apply to all virtual machines in the cluster when a host failure or host isolation occurs. In addition, you can configure exceptions for specific virtual machines,

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/54/46/wKiom1R9rkeBYRGyAAMWfTlXXZk219.jpg "title=" Qq20141201192319.png "alt=" wkiom1r9rkebyrgyaamwftlxxzk219.jpg "/> Step 6 If you do not receive a VMware tools heartbeat for a single virtual machine within the set time, Virtual machine monitoring will restart the virtual machine. Similarly, if you do not receive a heartbeat for the application that the virtual machine is running, application monitoring also restarts the virtual machine. You can enable the Virtual machine monitoring feature and configure the sensitivity of vsphere ha monitoring when it is unresponsive.

You can configure the level of monitoring sensitivity in the default cluster settings. High-sensitivity monitoring allows for faster conclusion of failures. However, if a monitored virtual machine or application is actually still running, but because of resource constraints and other factors that do not receive a heartbeat, high-sensitivity monitoring may incorrectly assume that this virtual machine has failed, and low-sensitivity monitoring will prolong the time between actual failures and service outages between virtual machine resets. After a failure is detected, VSphere ha resets the virtual machine and resets it to ensure that the services are still available. To prevent non-transient errors from repeatedly resetting the virtual machine, the virtual machine will be reset only 3 times over a configurable time interval by default. After 3 resets to the virtual machine, VSphere ha does not attempt to reset the virtual machine further after a subsequent failure occurs until the specified time has ended. You can configure the number of resets by using the maximum number of resets per virtual machine custom setting.

When the monitoring sensitivity is high, the fault interval is 30 seconds, the reset period is 1 hours, in the monitoring sensitivity, the fault interval is 60 seconds, the reset time is 24 hours, when the monitoring sensitivity is low, the fault interval is 120 seconds, the reset time is 7 days, in "Default cluster Settings", Adjust the adjustment button to control the monitoring sensitivity,

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/54/46/wKiom1R9rmuDwXsHAAOqtcyc-u4261.jpg "title=" Qq20141201192348.png "alt=" wkiom1r9rmudwxshaaoqtcyc-u4261.jpg "/> Step 7 when the preferred host in the vsphere ha cluster is unable to communicate with the subordinate host through the Management Network, The preferred host uses a data store heartbeat to determine whether the subordinate host is faulted, is in a network partition, or is isolated from the network. The number of heartbeat data stores selected by VCenter server for each host, with a default value of 2 and a maximum valid value of 5. Finally, click the OK button to complete the setup and creation of vsphere ha.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/54/46/wKiom1R9rsDz2gHwAANgVi-K804689.jpg "title=" Qq20141201192417.png "alt=" Wkiom1r9rsdz2ghwaangvi-k804689.jpg "/> (ii) using a vsphere ha cluster

There are currently two hosts in the cluster, using two shared iSCSI storage LUNs, and vsphere HA has been turned on. The virtual machine Linux Ftpserver runs on 10.128.114.74, and the virtual machine files are on one LUN in the shared iSCSI storage,

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/54/45/wKioL1R9r4LwhlYZAANmsMfEsfI466.jpg "title=" Qq20141201203953.png "alt=" Wkiol1r9r4lwhlyzaanmsmfesfi466.jpg "/> Now perform an artificial reboot to mimic the 10.128.114.74 host failure,

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/54/46/wKiom1R9ryXSdHKvAAUTG_ch5gU059.jpg "title=" Qq20141202184149.png "alt=" wkiom1r9ryxsdhkvaautg_ch5gu059.jpg "/> through ha, virtual machine Linux ftpserver ( Standby) is automatically switched to the 10.128.114.76 host. After the failure of the host, the HA is invalid and therefore cannot meet the HA requirements.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/54/46/wKiom1R9rzSwhJ0MAAVD26__xtk953.jpg "title=" Qq20141202200646.png "alt=" Wkiom1r9rzswhj0maavd26__xtk953.jpg "/>

This article is from the "Zhong blog" blog, make sure to keep this source http://capfzgs.blog.51cto.com/7729146/1585682

Creating and using vsphere ha clusters