{"id":18784,"date":"2016-11-07T10:00:28","date_gmt":"2016-11-07T09:00:28","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=18784"},"modified":"2018-03-13T07:53:07","modified_gmt":"2018-03-13T06:53:07","slug":"virtual-san-2-node-cluster-installtion-robo-pt1","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/virtual-san-2-node-cluster-installtion-robo-pt1\/","title":{"rendered":"Virtual SAN 2-node cluster installation for ROBO - pt.1"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-18787 size-full\" title=\"vsan2nodeclustersetup01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup01.jpg\" alt=\"vsan2nodeclustersetup01\" width=\"602\" height=\"202\" \/><\/p>\n<p>Virtual SAN for ROBO is a solution designed for smaller Remote Office, Branch Office (ROBO) that want the benefits provided by\u00a0a traditional Virtual SAN cluster implementation without the minimum <strong>requirement of three nodes<\/strong>.<\/p>\n<p>Feature introduced with VSAN 6.1, it has been improved in version 6.2 in terms of QoS, Performance Service and Metrics.<!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>Blog series<\/h2>\n<p>Virtual SAN 2-node cluster installation for ROBO - pt.1<br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/virtual-san-2-node-cluster-configuration-pt2\/\">Virtual SAN 2-node cluster configuration\u00a0- pt.2<\/a><\/p>\n<p>&nbsp;<\/p>\n<h2>Virtual SAN for ROBO edition<\/h2>\n<p>This solution built on the foundations of <strong>Fault Domains <\/strong>concept, is based on three nodes for the failure zones:<\/p>\n<ul>\n<li>Two physical nodes (hosts equipped with at least one HDD and one SSD)<\/li>\n<li>One <a href=\"https:\/\/my.vmware.com\/web\/vmware\/details?downloadGroup=WITNESS_OVA_62&amp;productId=564\" target=\"_blank\" rel=\"noopener\">Witness virtual appliance<\/a><\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18788 size-full\" title=\"vsan2nodeclustersetup02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup02.jpg\" alt=\"vsan2nodeclustersetup02\" width=\"425\" height=\"490\" \/><\/p>\n<p>Using the Witness VA\u00a0eliminates the requirement of a third physical node allowing the ROBO to <strong>lower the costs<\/strong> of the implementation.<\/p>\n<p>&nbsp;<\/p>\n<h2>Witness Virtual Appliance<\/h2>\n<p>The Witness VA is required to provide the\u00a0<strong>cluster quorum services<\/strong> during failure events and to <strong>store witness objects<\/strong> and cluster <strong>metadata<\/strong> information.<\/p>\n<p>&nbsp;<\/p>\n<h4>Witness VA limitations<\/h4>\n<ul>\n<li>One Witness VA is required per Virtual SAN ROBO cluster.<\/li>\n<li>The appliance does not contribute <strong>compute nor storage resources<\/strong> to the cluster and it is not able to host virtual machines.<\/li>\n<li>The Witness VA is <strong>supported and available<\/strong> only for Virtual SAN Stretched Clusters and Virtual SAN ROBO edition.<\/li>\n<li>The Virtual SAN ROBO edition is only capable of supporting a <strong>single failure<\/strong> within the cluster (FTT=1) due to the support of only three fault domains.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h4>Witness VA deployment<\/h4>\n<p>Access VMware vSphere Web Client and right click the configured cluster. Select <strong>Deploy OVF Template<\/strong> option to start the wizard.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18789 size-full\" title=\"vsan2nodeclustersetup03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup03.jpg\" alt=\"vsan2nodeclustersetup03\" width=\"594\" height=\"358\" \/><\/p>\n<p>Click <strong>Browse<\/strong> and select the Witness appliance <strong>.ova file<\/strong>\u00a0downloaded from VMware website. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18790 size-large\" title=\"vsan2nodeclustersetup04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup04-600x351.jpg\" alt=\"vsan2nodeclustersetup04\" width=\"600\" height=\"351\" \/><\/p>\n<p>Click <strong>Next<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18791 size-large\" title=\"vsan2nodeclustersetup05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup05-600x351.jpg\" alt=\"vsan2nodeclustersetup05\" width=\"600\" height=\"351\" \/><\/p>\n<p>Accept the EULA then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18792 size-large\" title=\"vsan2nodeclustersetup06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup06-600x351.jpg\" alt=\"vsan2nodeclustersetup06\" width=\"600\" height=\"351\" \/><\/p>\n<p>Enter the appliance <strong>Name<\/strong> and select the desired folder. Click <strong>Next<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18793 size-large\" title=\"vsan2nodeclustersetup07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup07-600x351.jpg\" alt=\"vsan2nodeclustersetup07\" width=\"600\" height=\"351\" \/><\/p>\n<p>Depending on the size of your network, select the <strong>Configuration<\/strong> that best fits your environment.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18794 size-large\" title=\"vsan2nodeclustersetup08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup08-600x351.jpg\" alt=\"vsan2nodeclustersetup08\" width=\"600\" height=\"351\" \/><\/p>\n<p>Select the disk format and the location\u00a0to store the VA then click <strong>Next<\/strong>.\u00a0There is <strong>no requirement<\/strong> to use a flash device in the appliance.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18795 size-large\" title=\"vsan2nodeclustersetup09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup09-600x351.jpg\" alt=\"vsan2nodeclustersetup09\" width=\"600\" height=\"351\" \/><\/p>\n<p><strong>Static IPs<\/strong> should be used in the VA network configuration. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18796 size-large\" title=\"vsan2nodeclustersetup10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup10-600x351.jpg\" alt=\"vsan2nodeclustersetup10\" width=\"600\" height=\"351\" \/><\/p>\n<p>Set the <strong>Password<\/strong> for the\u00a0<strong>root account<\/strong> then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18797 size-large\" title=\"vsan2nodeclustersetup11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup11-600x351.jpg\" alt=\"vsan2nodeclustersetup11\" width=\"600\" height=\"351\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to start the deployment.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18798 size-large\" title=\"vsan2nodeclustersetup12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup12-600x351.jpg\" alt=\"vsan2nodeclustersetup12\" width=\"600\" height=\"351\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Configure the Management Network<\/h4>\n<p>Power on the VA and access the console.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18800 size-large\" title=\"vsan2nodeclustersetup13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup13-600x450.jpg\" alt=\"vsan2nodeclustersetup13\" width=\"600\" height=\"450\" \/><\/p>\n<p>Insert the <strong>root credentials<\/strong> to access the configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18801 size-large\" title=\"vsan2nodeclustersetup14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup14-600x450.jpg\" alt=\"vsan2nodeclustersetup14\" width=\"600\" height=\"450\" \/><\/p>\n<p>Assign a <strong>static IP<\/strong> to the Management Network\u00a0and apply the configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18802 size-large\" title=\"vsan2nodeclustersetup15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup15-600x450.jpg\" alt=\"vsan2nodeclustersetup15\" width=\"600\" height=\"450\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Add Witness VA to vCenter Server<\/h4>\n<p>Once\u00a0the Witness virtual appliance has been deployed e configured with a static IP, it\u00a0should be added to vCenter as an ESXi host. Right click the Datacenter and select <strong>Add Host<\/strong> option.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18803 size-full\" title=\"vsan2nodeclustersetup16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup16.jpg\" alt=\"vsan2nodeclustersetup16\" width=\"594\" height=\"360\" \/><\/p>\n<p>Type the <strong>Host name or IP address<\/strong> and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18804 size-large\" title=\"vsan2nodeclustersetup17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup17-600x351.jpg\" alt=\"vsan2nodeclustersetup17\" width=\"600\" height=\"351\" \/><\/p>\n<p>Enter the credentials to connect to the host and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18805 size-large\" title=\"vsan2nodeclustersetup18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup18-600x351.jpg\" alt=\"vsan2nodeclustersetup18\" width=\"600\" height=\"351\" \/><\/p>\n<p>Click <strong>Yes<\/strong> to accept the certificate.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18806 size-full\" title=\"vsan2nodeclustersetup19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup19.jpg\" alt=\"vsan2nodeclustersetup19\" width=\"414\" height=\"272\" \/><\/p>\n<p>Click <strong>Next<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18807 size-large\" title=\"vsan2nodeclustersetup20\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup20-600x351.jpg\" alt=\"vsan2nodeclustersetup20\" width=\"600\" height=\"351\" \/><\/p>\n<p>The Witness appliance comes with <strong>per-configured license<\/strong> so already installed licenses are not consumed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18809 size-large\" title=\"vsan2nodeclustersetup21\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup21-600x351.jpg\" alt=\"vsan2nodeclustersetup21\" width=\"600\" height=\"351\" \/><\/p>\n<p>If you need to restrict the access to the appliance, enable the <strong>Lockdown mode<\/strong>. Leave default value <strong>Disabled<\/strong> and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18810 size-large\" title=\"vsan2nodeclustersetup22\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup22-600x351.jpg\" alt=\"vsan2nodeclustersetup22\" width=\"600\" height=\"351\" \/><\/p>\n<p>Specify the <strong>VM location<\/strong> and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18811 size-large\" title=\"vsan2nodeclustersetup23\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup23-600x351.jpg\" alt=\"vsan2nodeclustersetup23\" width=\"600\" height=\"351\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to save\u00a0the configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18812 size-large\" title=\"vsan2nodeclustersetup24\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup24-600x351.jpg\" alt=\"vsan2nodeclustersetup24\" width=\"600\" height=\"351\" \/><\/p>\n<p>The Witness VA has been added to the Datacenter. Note that the <strong>Witness\u00a0appliance is\u00a0in blue<\/strong> to distinguish it from other ESXi hosts in the cluster.\u00a0In addition there is a <em>No datastores have been configured<\/em>\u00a0warning on the host because the nested ESXi host doesn't have any <strong>VMFS datastores configured<\/strong>. This warning can be ignored.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18842 size-large\" title=\"vsan2nodeclustersetup25\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup25-600x401.jpg\" alt=\"vsan2nodeclustersetup25\" width=\"600\" height=\"401\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Configure the VSAN network<\/h4>\n<p>From the VMware vSphere Web Client select the Witness VA and access the <strong>Manage &gt; Networking &gt; Virtual switches<\/strong> tab. By default\u00a0the appliance\u00a0comes with two\u00a0virtual standard switches with configured uplinks:<\/p>\n<ul>\n<li><strong>vSwitch0<\/strong>\u00a0-\u00a0used\u00a0for the management network<\/li>\n<li><strong> witnessSwitch<\/strong>\u00a0-\u00a0used\u00a0for the VSAN network<\/li>\n<\/ul>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18843 size-large\" title=\"vsan2nodeclustersetup26\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup26-600x355.jpg\" alt=\"vsan2nodeclustersetup26\" width=\"600\" height=\"355\" \/><\/p>\n<p>Since the VSAN network on the witness site needs to communicate to the <strong>VSAN network<\/strong>, edit the <strong>witnessSwitch <\/strong>and add a VLAN for the VSAN network.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18844 size-large\" title=\"vsan2nodeclustersetup27\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup27-600x481.jpg\" alt=\"vsan2nodeclustersetup27\" width=\"600\" height=\"481\" \/><\/p>\n<p>Set the correct <strong>VLAN ID<\/strong> used for the VSAN communication and click <strong>OK<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18845 size-large\" title=\"vsan2nodeclustersetup28\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup28-600x349.jpg\" alt=\"vsan2nodeclustersetup28\" width=\"600\" height=\"349\" \/><\/p>\n<p>In the<strong> VMKernel adapters<\/strong> tab, highlight the <strong>witnessPg<\/strong>\u00a0portgroup and click the <strong>pen icon<\/strong> to edit the parameters. <strong>Don't remove<\/strong> this port group because\u00a0it is\u00a0configured so that the virtual machine network adapters MAC addresses matches the vmnic MAC address of the <strong>nested ESXi host<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18846 size-large\" title=\"vsan2nodeclustersetup29\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup29-600x258.jpg\" alt=\"vsan2nodeclustersetup29\" width=\"600\" height=\"258\" \/><\/p>\n<p>In the <strong>Port properties<\/strong>\u00a0you find a <strong>VMKernel port<\/strong>\u00a0already configured with the <strong>Virtual SAN traffic<\/strong> option enabled.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18847 size-large\" title=\"vsan2nodeclustersetup30\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup30-600x349.jpg\" alt=\"vsan2nodeclustersetup30\" width=\"600\" height=\"349\" \/><\/p>\n<p>In the <strong>IPv4 settings<\/strong> you can specify a static IP address. Click <strong>OK<\/strong> to save the configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-18848 size-large\" title=\"vsan2nodeclustersetup31\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/10\/vsan2nodeclustersetup31-600x349.jpg\" alt=\"vsan2nodeclustersetup31\" width=\"600\" height=\"349\" \/><\/p>\n<p>In <a href=\"https:\/\/nolabnoparty.com\/en\/virtual-san-2-node-cluster-configuration-pt2\/\">part 2<\/a> the configuration will be completed with the creation of the <strong>Fault Domains<\/strong>\u00a0and the <strong>VSAN cluster<\/strong> setup.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Virtual SAN for ROBO is a solution designed for smaller Remote Office, Branch Office (ROBO) that want the benefits provided by\u00a0a traditional Virtual SAN cluster implementation without the minimum requirement of three nodes. Feature introduced with VSAN 6.1, it has been improved in version 6.2 in terms of QoS, Performance Service and Metrics.<\/p>\n","protected":false},"author":3,"featured_media":18787,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,1853],"tags":[28,1047,963,699,1664],"class_list":["post-18784","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsan-en","tag-cluster","tag-fault-domains","tag-storage-en","tag-vmware-en","tag-vsan","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/18784","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=18784"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/18784\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/18787"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=18784"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=18784"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=18784"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}