Download VMWare.PracticeDumps.2V0-620.2018-05-16.1e.107q.vcex

You can create up to 64 LAGs on a distributed switch. A host can support up to 32 LAGs. However, the number of LAGs that you can actually use depends on the capabilities of the underlying physical environment and the topology of the virtual network. For example, if the physical switch supports up to four ports in an LACP port channel, you can connect up to four physical NICs per host to a LAG. 
Reference: https://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.networking.doc%2FGUID-0D1EF5B4-7581-480B-B99D-5714B42CD7A9.html

Active Uplinks, and Unused adapter Uplinks are used with IP hash load balancing. 
Reference: https://books.google.com.pk/books?id=35TE4cSycNAC&pg=PA201&lpg=PA201&dq=IP+hash+load+balancing+active+uplinks+unused+uplinks&source=bl&ots=ggg8VOCpw4&sig=EaqvN49-p2UWQ5b6V53SkFFmJhc&hl=en&sa=X&ved=0ahUKEwiv1ruEhMbNAhVGL48KHfXaBN4Q6AEIUzAJ#v=onepage&q=IP%20hash%20load%20balancing%20active%20uplinks%20unused%20uplinks&f=false

  

Reference: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.networking.doc%2FGUID-09176C71-1748-460B-BB7B-3671AB855D7E.html

You can modify MTU values in switch settings. 
Reference: https://kb.vmware.com/selfservice/microsites/search.do%3Flanguage%3Den_US%26cmd%3DdisplayKC%26externalId%3D1010557

To manage the networking of your vSphere environment by using a vSphere Distributed Switch, you must associate hosts with the switch. You connect the physical NICs, VMkernel adapters, and virtual machine network adapters of the hosts to the distributed switch. 
Prerequisites 
Verify that enough uplinks are available on the distributed switch to assign to the physical NICs that you want to connect to the switch. 
Verify that there is at least one distributed port group on the distributed switch. 
Verify that the distributed port group have active uplinks configured in its teaming and failover policy. 
Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.networking.doc%2FGUID-E90C1B0D-82CB-4A3D-BE1B-0FDCD6575725.html

Route based on physical NIC workload was limited to vSphere Distributed switches. Now its available on vSphere standard switches with vSphere 6.x 
Reference: https://pubs.vmware.com/vsphere-60/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-60-networking-guide.pdf

There are 3 types of  tagging available in vSphere. 
Virtual Switch Tagging (VST) 
External Switch Tagging (EST) 
Virtual Guest Tagging (VGT) 
VLAN tagging is  determined by the VLAN value specified at the port group and it tells the vSwitch or Phyiscal switch or Virtual machines to how to handle the VLAN tagging. 
Reference: http://www.vmwarearena.com/vlan-tagging-vst-est-vgt-on-vmware/

You can enable services for the default TCP/IP stack on the host. Select from the available services:
vMotion traffic. Enables the VMkernel adapter to advertise itself to another host as the network connection where vMotion traffic is sent. The migration with vMotion to the selected host is not possible if the vMotion service is not enabled for any VMkernel adapter on the default TCP/IP stack, or if no adapters are using the vMotion TCP/IP stack. 
Provisioning traffic. Handles the data transferred for virtual machine cold migration, cloning, and snapshot creation. 
Fault Tolerance traffic. Enables Fault Tolerance logging on the host. You can use only one VMkernel adapter for FT traffic per host. 
Management traffic. Enables the management traffic for the host and vCenter Server. Typically, hosts have such a VMkernel adapter created when the ESXi software was installed. You can create another VMkernel adapter for management traffic on the host to provide redundancy. 
vSphere Replication traffic.Handles the outgoing replication data that is sent from the sourceESXi host to the vSphere Replication server. 
vSphere Replication NFC traffic. Handles the incoming replication data on the target replication site. 
Virtual SAN. Enables the Virtual SAN traffic on the host. Every host that is part from a Virtual SAN cluster must have such a VMkernel adapter. 
Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.networking.doc%2FGUID-1C0D8D8D-F9A5-4443-9AE7-544742630D39.html

Virtual machine portgroups and Vmkernel services can be configured on a virtual switch. 
Reference: https://www.vmware.com/files/pdf/virtual_networking_concepts.pdf

To configure Jumbo Frames on a vDS using vSphere Client on vCenter Server 5.1 and earlier:
From vCenter Server click, click Home > Inventory > Networking. 
Right-click the vDS and click Edit Settings. 
On the Properties tab, select the Advanced option. 
Change the Maximum MTU value from the default value of 1500 to 9000. This enables Jumbo Frames on all portgroups and ports. 
Reference: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1038827