VSAN-Troubleshooting-Reference-Manual

Diagnostics and Troubleshooting Reference Manual – Virtual SAN
Symptoms of MTU misconfiguration: Cannot complete file creation
This is one of the possible symptoms of having mismatched MTU sizes in your
environment. The cluster formed successfully and reported that the network status
was normal. However on attempting to deploy a virtual machine on the Virtual SAN
datastore, an error reported that it “cannot complete file creation operation”.
This is the error that popped up when the VM was being provisioned on the Virtual
SAN datastore:
Note also the ‘Failed to connect to component host” message.
In this case, the customer wanted to use jumbo frames with Virtual SAN in their
environment. An MTU of 9000 (jumbo frames) was configured on the physical
switch. However in this setup, it seems that an MTU of 9000 on the physical switch
(DELL PowerConnect) wasn’t large enough to match the MTU of 9000 required on
the ESXi configuration due to additional overhead requirements on the switch. The
switch actually required an MTU of 9124 (9 * 1024) to allow successful
communication using jumbo frames on the Virtual SAN network.
Once this change was made on the physical switch ports used by Virtual SAN, virtual
machines could be successfully provisioned on the Virtual SAN datastore.
Again, with jumbo frames, ensure that all nodes in the cluster can be pinged with the
larger packet size of 9000 as seen earlier.
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 1 9