could not complete network copy for file vmfsvolumes

Please note: all network equipment should support Jumbo Frames and should be enabled from end to end.

Once the deployment is done, you can investigate and set MTU size of 9000 on all the network equipment and also in the SVMs.

For a complete list of rulesets: govc host.esxcli network firewall ruleset list. In case you want you can set the MTU size to 1500 everywhere and proceed with deoplyment. Usage: govc datastore.cp OPTIONS SRC DST Copy SRC to DST on DATASTORE. 3) I configured vMotion and start trying migrate VMs to this host and reciaved message: Could not complete network copy for file /vmfs/volumes/.vmdk when i reisntalled ESXi and added it to vCenter before, there are allways no problems, but this time, i migration dont whant to work. without Jumbo frames, that means somewhere in the network stack, MTU size of 9000 is missing. ESX Connectivity Check This article assumes two data networks, configured with and subnets.įind out which vmknic is on which subnet, as well as esxcfg-vmknic -l Interface Port Group/DVPort/Opaque Network IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type NetStack vmk0 sys-mgmt-krnl IPv4 192.168.105.101 255.255.255.0 192.168.105.255 00:xx:xx:xx:xx:xx 9000 65535 true STATIC defaultTcpipStack vmk3 sys-vmotion IPv4 192.168.106.101 255.255.255.0 192.168.106.255 00:xx:xx:xx:xx:xx 9000 65535 true STATIC defaultTcpipStack vmk1 sio-data1-krnl IPv4 192.168.152.121 255.255.255.0 192.168.152.255 00:xx:xx:xx:xx:xx 9000 65535 true STATIC defaultTcpipStack vmk2 sio-data2-krnl IPv4 192.168.154.141 255.255.255.0 192.168.154.255 00:xx:xx:xx:xx:xx 9000 65535 true STATIC defaultTcpipStack Ping each ESXi in the environment via each vmknic with packet size 8972: If jumbo frames are configured and this test fails, network connectivity is not 100%:

Could not complete network copy for file vmfsvolumes