Convert a vSan stretched cluster to 3 node and above

Stretched cluster to multi node vSan cluster    I assume most of you are aware about stretched cluster and how the component splits between the hosts/witness appliance. In this blog, I am going to walk you through the steps to convert a 2 vSan stretched cluster to a 3 node vSan cluster. What

Convert multi node vsan cluster to one node vsan cluster

One node vSan cluster:    Have you tried building a one node vsan cluster ? or convert exiting multi node cluster to one node. Though its not recommended by VMware, it is possible to have one node vsan cluster but with limitations like no data protection as the single node cluster is

clomd value change in all hosts

CLOMD:  CLOMD value can be changed in multiple ways, here I am showing two ways i.e., powershell or cli   CLI: Take ssh to hosts in cluster and use below commands (6.x version) to fetch the clomd values and change the values:                      esxcfg-advcfg --get /VSAN/ClomRepairDelay    

Change vsan network subnet for hosts in vSan enabled cluster

When working on lab environment, I got an idea of changing the complete vSan subnet for hosts and immediately started working on it without waiting a minute, with paper work first , before implementing it and finally ended with a success..   Here is my lab environment details: No of hosts in

Convert multi node vsan cluster to 2 node stretched cluster

Recently I have got a request to convert the multi node vsan cluster (3 hosts) to stretched cluster (2 hosts + 1 witness). Since this is for a production environment with FTT 1, I planned this in two phases: Phase 1:   1. Deploy the witness appliance with all necessary licensing, networking, routing

VSAN troubleshooting commands

Here are some of the important commands that can be used while troubleshooting vSan:  Please note this is for quick ref if you are looking for commands and detailed explanation will be given in posts. Get the total number of hosts that are part of vsan cluster: esxcli vsan cluster get Manually join

snapshot vmem file in vSan data store

Recently I got a request from one of the VSAN customers to provide the memory dump of a vm. To generate the same, we will have to take the snapshot of specific vm with memory box checked. Pick the vm  > right click > snapshot > take snapshot > give a

vSan object checksum

VSAN Object Checksum: VSAN 6.2 introduced a new feature called object checksum which is enabled by default, but may be enabled or disabled on per virtual machine/object basis via VM storage policies and this policy does end-to-end software checksum to avoid data integrity issues arising due to problems on the underlying storage