Database Reference
In-Depth Information
VM Traffic Bandwidth Entitlement = 100 (VM Shares) / 125 (VM + vMotion) =
80%
However, if VM traffic didn't need all the bandwidth it is entitled to, then vMotion
would be free to use whatever available bandwidth remains, but would be entitled to a
minimum of 25%. Frank Denneman shows many different additional scenarios in his
control/
).
Note
Network I/O Control requires a virtual distributed switch. To learn more
about NIOC, read the “vSphere Networking for 5.5” white paper:
http://pubs.vmware.com/vsphere-
networking-guide.pdf
and
Caution
When a dependent or independent hardware iSCSI adapter or physical
Converged Network Adapter (CNA) is used for FCoE, none of the traffic will be
visible to vSphere, nor can it be managed or guaranteed by using NIOC. Physical
network-based quality of service, limits, or reservations may be needed to ensure
each type of traffic gets the bandwidth it is entitled to and that application SLAs
are met.
Multi-NIC vMotion
Multi-NIC vMotion, as the name implies, allows you to split vMotion traffic over
multiple physical NICs. This allows you to effectively load-balance any vMotion
operation, including single vMotions. This doesn't require any special physical switch
configuration or link aggregation to support because it's all built in to VMware
vSphere. This feature is available from vSphere 5.0 and above and allows vMotion to
be load-balanced across up to sixteen 1Gb Ethernet or four 10Gb Ethernet NICs. This is
particularly important when you have incredibly large memory configurations per host
(512GB and above) or where you have mega-monster VMs, because it will allow you
to migrate VMs or evacuate a host using maintenance mode much faster, while reducing
overall performance impacts.
Although Multi-NIC vMotion doesn't require a vSphere distributed switch, using it in
conjunction with a vSphere distributed switch and the Network I/O Control feature is
