Use the link aggregation feature to aggregate one or more Ethernet interfaces to form a logical point-to-point link, known as a LAG, virtual link, or bundle. We would like to add LACP Ether channels to one of my 2960 switches to connect VMWare ESXi (vSphere 6.5) host’s via teamed NIC.
Does enabling Route based on IP hash without 802.ad aggregation or vise-versa disrupt networking?
Yes, if you must enable 802.ad Static mode ON and configure the vSwitch to route based on IP Hash, configure route based on IP hash inside ESX/ESXi first, then enable the LAG on the physical network. You will loose connectivity to the ESX/ESXi host temporarily until you configure the physical side.
How many Ether channels exist per vSwitch or vSphere Distributed Switch (vDS)?
One and only one Ether channel per vSwitch or vDS.
What is the difference between Active and Passive Mode for LACP configuration?
Active - The port will actively negotiate the link state by initiating negotiation and send LACP frames.
Passive - The port is passive state and will respond to LACP frames sent during LACP negotiation.
Does VMware support any other algorithm other than IP HASH when using Ether channel?
No, only route based on IP hash is supported when configuring based on Ether channel.
Can I configure standby or unused up-links while using IP Hash?
No. Do not configure standby or unused up-links with IP Hash. IEEE 802.3ad dynamic: Only supported in ESXi 5.1 vDS. Pior to ESXi 5.1 VMware only supported static link aggregation. With ESXi 5.1 Dynamic LACP is supported only vSphere Distributed Switches (vDS). Static LAG are still supported on vSwithes and vDS. Dynamic LACP provides additional support for Plug and Play automatic configuration and negotiation between host and physical switch. Dynamic LACP will detect link failures and cabling errors and automatically reconfigure the links.
Can I use beacon probing with IP Hash load balancing?
No. Beacon probing with IP Hash load balancing is not supported. Beacon probing is most useful in detecting networking failures which do not result in a link down condition. This could be a mis-configuration resulting in link that is still up, but not operating as expected.
