<div>
Best Practice, is to use a dedicated vSwitch, connected to, two or more physical uplinks (nics in the host), with a teaming policy.<br />
<br />
for all VMs.<br />
<br />
add more nics, if you require more bandwidth.<br />
<br />
it's common to have a vSwitch just for the purpose of VM traffic, with at least 4 nics (if they are 1GBe)<br />
<br />
see this example<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2015/08_w34/930355/10NICs-with-annotations---.jpg" target="_blank" title="nic example (151 KB)"><img alt="nic example" class="file-block lazyload" style="max-width: 674px;" data-src="https://filedb.experts-exchange.com/incoming/2015/08_w34/930355/10NICs-with-annotations---.jpg" /></a>
</div>


Best Practice, is to use a dedicated vSwitch, connected to, two or more physical uplinks (nics in the host), with a teaming policy.

for all VMs.

add more nics, if you require more bandwidth.

it's common to have a vSwitch just for the purpose of VM traffic, with at least 4 nics (if they are 1GBe)

see this example

nic examplehttps://filedb.experts-exchange.com/incoming/2015/08_w34/930355/10NICs-with-annotations---.jpg

10NICs-with-annotations---.jpg

<div>
Is this valid also for VM (ftp server) connected to a DMZ network? Should this VM_DMZ be in a separate vSwitch linked to the DMZ_network or it can be in the same vSwitch as the internal VMs but &nbsp;use a separate NIC (vmin6 - see pic). <br />
<a href="https://filedb.experts-exchange.com/incoming/2015/08_w34/930370/VMsPM.png" target="_blank" title="vclient (71 KB)"><img alt="vclient" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2015/08_w34/800_930370/VMsPM.png" /></a>
</div>


Is this valid also for VM (ftp server) connected to a DMZ network? Should this VM_DMZ be in a separate vSwitch linked to the DMZ_network or it can be in the same vSwitch as the internal VMs but  use a separate NIC (vmin6 - see pic).
vclienthttps://filedb.experts-exchange.com/incoming/2015/08_w34/930370/VMsPM.png

VMsPM.png

<div>
<div class="content wysiwyg-content">
Hello,<br />
While adding more VMs in my VMware Esxi 6.0 network, what it would be the practice: &nbsp;should I create extra vSwitch for the new VMs connected to different NICs or I can still use the same vSwith for all VMs network but adding more NICs for load balancing ? <br />
<br />
thank you
</div>
</div>


Hello,
While adding more VMs in my VMware Esxi 6.0 network, what it would be the practice:  should I create extra vSwitch for the new VMs connected to different NICs or I can still use the same vSwith for all VMs network but adding more NICs for load balancing ? 

thank you

VMs and vSwitch load balancing

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.

VMware

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.