VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
Testing Virtual SAN functionality - deploying VMs
One strong recommendation from VMware is to verify that virtual machines can be
successfully deployed on the Virtual SAN datastore once the cluster has been
created.
diagnostics.vm_create
RVC provides a command to do this test. It attempts to create a virtual machine on
each host participating in the Virtual SAN cluster. A successful VM creation suggests
that the cluster is functioning correctly. If the command fails, useful diagnostic
information is displayed which might help determine the root cause. Here is a
successful output from the command:
/localhost/vsan-dc/computers> diagnostics.vm_create --
datastore ../datastores/vsanDatastore --vm-folder ../vms/Discovered\ virtual\ machine 0
Creating one VM per host ... (timeout = 180 sec)
Success
/localhost/vsan-dc/computers>
In the vSphere web client, the newly created VMs will be temporarily visible in the
folder selected, with the name VM-on--XXX:
The VMs are removed automatically once the operation completes.
diagnostics.vm_create failure – clomd not running
Here is the output from an unsuccessful attempt at creating a VM, with an
informative error message. In this example, clomd, one of the Virtual SAN daemons,
was not running on the host in question, and thus the command could not create a
VM on that host.
/localhost/vsan-dc/computers> diagnostics.vm_create --
datastore ../datastores/vsanDatastore --vm-folder ../vms/Discovered\ virtual\ machine 0
Creating one VM per host ... (timeout = 180 sec)
Failed to create VM on host cs-ie-h03.ie.local (in cluster vsan): CannotCreateFile:
Cannot complete file creation operation.
vob.vsanprovider.object.creation.failed: Failed to create object.
vob.vsan.dom.noclomattached: A CLOM is not attached. This could indicate that the
clomd daemon is not running.
/localhost/vsan-dc/computers>
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 1 5 2