Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
Sign In Create an Account Premier Sign In Partner Program Sign In

ScaleIO: Error while running the script during ScaleIO Deployment "Could not complete network copy for file /vmfs/volume/"

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms



Customer trying to run the ps1 script from a windows host, selects option 3 to Create SVM Template, and provides the list of datastores on which the templates will be created.

It successfully creates the template EMC ScaleIO SVM Template on one of the datastore but fails on the next with the following error:-

Cannot create template EMC ScaleIO SVM Template <v2.0.11000.174> 2 from the temporary SVM
Error
The operation for the entity "EMC ScaleIO SVM Template <v2.0.11000.174> 1" failed with the following message: "Could not complete network copy for file /vmfs/volume/5849af5d-xxxxxxxx-xxxx-xxxxxxxxxxxx/EMC ScaleIO SVM Template <v2.0.11000.174> 1/EMC ScaleIO SVM Template <v2.0.11000.174> 1.vmdk"


kA2j0000000RHVICA4_3_0

Cause

This issue can occur due to high network latency or packet loss in the environment.

Resolution

ESX Connectivity Check

This article assumes two data networks, configured with 192.168.152.x and 192.168.154.x subnets.

Find out which vmknic is on which subnet, as well as MTU:

[root@server1-101:~] 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%:

vmkping -d -s 8972 -I vmk1 192.168.152.101 vmkping -d -s 8972 -I vmk2 192.168.154.101

 

Try without jumbo frames:

vmkping -d -s 1472 -I vmk1 192.168.152.101 vmkping -d -s 1472 -I vmk2 192.168.154.101

or

vmkping -I vmk1 192.168.152.101 vmkping -I vmk2 192.168.154.101

 

 

Ping the subnet gateways:

Jumbo:

vmkping -d -s 8972 -I vmk1 192.168.152.1 vmkping -d -s 8972 -I vmk2 192.168.154.1


Normal:

vmkping -I vmk1 192.168.152.1 vmkping -I vmk2 192.168.154.1 or vmkping -d -s 1472 -I vmk1 192.168.152.1 vmkping -d -s 1472 -I vmk2 192.168.154.1 In case you are able to ping with packet size 1472 i.e. without Jumbo frames, that means somewhere in the network stack, MTU size of 9000 is missing. In case you want you can set the MTU size to 1500 everywhere and proceed with deoplyment. Once the deployment is done, you can investigate and set MTU size of 9000 on all the network equipment and also in the SVMs. Please note: all network equipment should support Jumbo Frames and should be enabled from end to end.

Article Properties
Article Number: 000167055
Article Type: Solution
Last Modified: 30 May 2024
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.