How to cleanup disk previously used by vSAN 6.x

In the VCSA Web Client, there is a function called Erase partitions under Storage Devices, that allows you to erase and remove all partitions on the local hard disk(s). However, sometimes when you try to erase partitions, you are presented with the error “Cannot change the host configuration“, and the partitions are not removed. One of the options was to boot up the server using gParted utility and erase partitions. However, this can be done using partedUtil utility on the ESXi host. Continue reading “How to cleanup disk previously used by vSAN 6.x”

Both parent and child virtual disks are root links – error while powering the VM

In the variety of different errors related to VM snapshots, while powering up a VM, this one is nowhere described. The VMware article KB 1007969 covers most of the similar errors and symptoms. However, the recovery procedure is more or less the same. I will cover simple 2 minutes solution that will get you up and running. Continue reading “Both parent and child virtual disks are root links – error while powering the VM”

How to deploy 2 node direct connect vSAN cluster.

Begining with v6.1 VMware supports direct connect for ESXi hosts when using vSAN. You just need to simply cross-connect your ESXi hosts using either cross UTP cable or 10 Gb SFP+ cable. This way you can save that expensive 10 Gb switch you would normally use for you vSAN and vMotion network. Please, do not proceed with the article before you have tested your direct connection! Ensure to use IP addresses that reflect your environment. Continue reading “How to deploy 2 node direct connect vSAN cluster.”

How to bootstrap VMware vCenter Server Appliance (VCSA) onto a single vSAN node

Previously it was a bit difficult to install VMware vCenter onto vSAN since you had to enable vSAN prior vCenter installation, and as you are aware, vSAN is a vCenter feature. VMware finally gave us the possibility to bootstrap VCSA onto a single vSAN node. In other words, you can enable vSAN feature under VCSA deployment. Once deployed, your VCSA will reside on fully functional vSAN. Of course, you must add additional hosts contributing storage to the vSAN cluster. Continue reading “How to bootstrap VMware vCenter Server Appliance (VCSA) onto a single vSAN node”

ESXi syslog – A general system error occurred: Internal error

I’ve run into this error a few times now while configuring syslog settings on an ESXi server. Since there is not much description, one does not know where to look for a solution. This error can appear regardless if one is using local datastore or remote log host. There is, however, a hidden log file that holds descriptive error regarding problems with the syslog settings. Continue reading “ESXi syslog – A general system error occurred: Internal error”

How to manually register storage providers in vSAN enabled cluster

One of the common problems when using vSAN is the missing VASA storage providers registration in the VMware vCenter. There is a number of possible reason for this, but if your network is segmented, and you are using separate VLANs for vCenter and ESXi hosts, then the most common issue is the firewall between the management VLAN (vCenter) and ESXi VLAN. Continue reading “How to manually register storage providers in vSAN enabled cluster”