Issues encountered during the creation of the VMware vSphere Cluster cluster

Working environment: VMware VSphere 5.5,vcenter Server 5.5, ESXI 5.5,dell eqlogic Storage

This host does not currently have management network redundancy

In a normal environment, you need a dual network card, in the configuration-network-vswitch0 Properties-Network adapter-add redundant network card.

After adding two physical network cards, right-click on the host > select reconfigure ha to dismiss the alarm status.

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/7F/E7/wKiom1cxVmGR0CX9AABrkTGAZ9c062.png "title=" QQ picture 20160510112546.png "alt=" Wkiom1cxvmgr0cx9aabrktgaz9c062.png "/>

VMware vSphere 5.5 configuration completed cluster ha in the summary bar of the host prompt "This host does not currently manage network redundancy", the test environment in the server if it is a single NIC, also did not do redundant management network. Had to be solved by the following methods.
1. Right-click Cluster to select Edit settings.
2. Select VSphere HA and click Advanced Options.
3. Double-click in the option to enter "Das.ignoreredundantnetwarning" and double-click in the value to enter "true".
4. Click OK to exit.
5. Right-click on the host in cluster and select Reconfigure Vsphere HA.

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M01/7F/E5/wKioL1cxX3KRgAg3AABXtCQyYdA489.png "title=" QQ picture 20160510120419.png "alt=" Wkiol1cxx3krgag3aabxtcqyyda489.png "/>

This warning disappears when the reconfiguration is complete.

The number of vsphere ha heartbeat data stores for this host is 0, less than the required number: 2

In a normal environment, 2 or more shared data stores are required. My official environment is 4 2T volumes.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/7F/E7/wKiom1cxXsfyKf73AABI-7i5g1Y200.png "title=" QQ picture 20160510120631.png "alt=" Wkiom1cxxsfykf73aabi-7i5g1y200.png "/>

Starting with vSphere5.0, a data storage detection signal has been added to the HA function. The management network and storage network in a test environment if you are using the same physical network card, it makes no sense to configure the storage heartbeat. This error occurs if you do not configure it. Fortunately, this feature can be turned off in advanced options. The method is:
1. Right-click Cluster to select Edit settings.
2. Select VSphere HA and click Advanced Options.
3. Double-click in the option to enter "Das.ignoreinsufficienthbdatastore" and double-click in the value to enter "true".
4. Click OK to exit.
5. No need to reconfigure HA, the warning will automatically disappear.

The data store's heartbeat is useful if you have a separate storage network. There are a few options for configuring the configuration:
1. File System format
When using VMFS3, the maximum usage is approximately 2 GB and the typical usage is approximately 3 MB.
When using VMFS5, the maximum usage and typical usage is approximately 3 MB.
VSphere HA uses data storage to add less overhead and has no impact on the performance of other data storage operations.
2. Number of heartbeat data stores per host
Add this item "Das.heartbeatdsperhost" to the advanced HA option to modify the number of heartbeat data stores, and the valid range is 2~5, the default value is 2.
When configured, you will find a folder named ". Vsphere-ha" in the root directory of the data store. Be careful not to attempt to modify or delete this folder.

Note: Data storage heartbeat
When a preferred host in a vSphere HA cluster cannot communicate with a subordinate host through the management network, the preferred host uses the data store heartbeat to determine whether the subordinate host is faulted, is in a network partition, or is isolated from the network. If the secondary host has stopped the data store heartbeat, the dependent host is considered to be faulty and its virtual machine has been restarted elsewhere.

This article is from the "Technical Achievement Dream" blog, please be sure to keep this source http://pizibaidu.blog.51cto.com/1361909/1771716

Issues encountered during the creation of the VMware vSphere Cluster cluster