Solved

svMotion between two different datastore limitation ?

Posted on 2016-11-27
3
76 Views
Last Modified: 2016-11-29
Hi All,

Is there any reason as to why the sVmotion from my iSCSI VMFS data store to my NFS data store is limited to just 4x VMs at the same time ?

svMotion screenshot
Is this because of the ethernet MPIO bandwidth limitation, NAS IOPS performance limitation or ESXi 6 limitation ?

How to increase it into its maximum value ?

See the screenshot below from the QNAP network traffic and each own data store network performance:
QNAP NAS traffic status
0
Comment
  • 2
3 Comments
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 41903121
Is this because of the ethernet MPIO bandwidth limitation, NAS IOPS performance limitation or ESXi 6 limitation ?

Neither.

It's - vMotion Bandwidth. (Storage vMotion Bandwidth). e.g. VMKernel Portgroups. So add more VMKernel Portgroups, e.g. up to 4 x 10-GB pNICs or 16 1-GB pNICs.

enable Jumbo Frames can make the transfer quicker.

Also the Maximum number is 8 concurrently, if using 10-GB. (per host).

It used to be 1 per host.

You can check all the stats here

Configuration Maximums vSphere 6.0

also remember that vMotion and Storage vMotion are different, and have different values.

So unless you change your networking, unlikely to change.
1
 
LVL 7

Author Closing Comment

by:Senior IT System Engineer
ID: 41905179
Thanks Andrew !
0
 
LVL 119
ID: 41905294
no pronlems
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Memory test on Esxi host 7 53
cannot remove vmnic 7 33
NAS Solution for VMware ESXi 2 80
ESXi 5.5 incompatibility when migrating VM 9 65
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to install ESXi 5.5 and configure the management network System Requirements: ESXi Installation:  Management Network Configuration: Management Network Testing:
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

828 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question