You have Only with 2 ESXI hosts and wants to configure shared storage via vSAN, it was not possible when vSAN was released a two-node configuration was not supported. Minimum three hosts were required for your hyper-converged infrastructure (HCI) to start with. In this post, we'll have a look at the VMware vSAN 2 Node configuration.
vSAN 2 Node Cluster needs a Witness Host. While in three-node (and more) clusters, vSAN Witness objects are stored and spread across all nodes within the cluster; however, the 2 Node configuration has the Witness objects stored only on the Witness Host. The two data hosts store the VM objects.
Communication between nodes and the Witness Host needs a Witness Traffic Separation. Witness Traffic Separation is actually a separation of the communication of vSAN data and vSAN metadata to the vSAN Witness Host. The communication to the vSAN Witness Host is done via a different VMkernel interface than the interface used to communicate between vSAN data nodes.
Lets walkthrough the process of configuring vSAN 7.
1.Navigate to the cluster in the vSphere Client.
2.Click the Configure tab, and select Configuration > Quickstart.
3.Go to Configure Cluster
You can uncheck the Configure networking settings later- and press Next
4. Choose deployment type Two host vSAN Cluster and follow the assistance as shown above.
5. Claim disks as you do for 3hosts vSAN cluster.
6. vSAN Support insight- By default, vSAN Support Insight is ON. vSAN Support collects some anonymous data to provide improved support experience and performance analytics. You can disable it, if you wish to.
7. Perform the proxy settings.(Optional)
8. Select a host to use as a witness host. The witness host cannot be not part of the stretched cluster, and it can have only one VMkernel adapter configured for vSAN data traffic.
Before you configure the witness host, verify that it is empty and does not contain any components. A two-node cluster can share a witness with other two-node clusters.
9.Claim disks for witness host
10. Review and Finish.
For more details refer VMware Documentation guide.
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-7DC2815D-4D38-43B6-8551-43B2FFB68ACF.html
Comments