what differences between Link Aggregation LACP and Teaming from vmware perspective

Hi

what differences between Link Aggregation LACP and Teaming from vmware perspective

we have 4 physical servers every server has 2 physical interfaces 10 G speed

i want to configure on of them for VSAN traffic and the other for the other traffic

so the question is

what the best configure teaming or LACP

and which configuration will provide load balance and fail over for VSAN traffic  


thanks
Sword
LVL 1
sword12Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Yogesh BansalCommented:
If you are using Switch or any other network device, that should be LACP enabled so that LACP will be up.

Teaming is another same term in windows which is a group of NIC, for that i believe you don't need to configure switch connected to the server.

You can achieve load balance in lacp by giving source and destination mac address. There are few other ways of load distribution in such combinations.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
LACP is handled by the physical switch configuration, Teaming Policies define how the Host handles the traffic.

ESXi teaming policies and configuration affect outbound traffic only!

Answer - you need both!
0
sword12Author Commented:
what really confuse me that vmware offer something called

link aggregation group (lag)

so i thought i will configure the physical switch ports as LA

then i will create on the VDS LAG and that it .

but now as i understand from Andrew

the step must be like this

1- on the physical switch level configure the ports for LA then connect them to the physical hosts interfaces
2- create VDS and assign hosts and interfaces
2- create DV port groups
3- configure teaming and fail-over policies
so if i do theses steps i will have load balance and fail-over between the VSAN traffic interface and the other traffic interface or not . if i will not get load balance no problem but fail-over very important  

so in such case i don't need to create and configure any LAG on vcenter

please check the attaches file and advice if i have to forget about link aggregation group (lag)
1.jpg
2.jpg
3.jpg
0
compdigit44Commented:
This is a great question and I to have been confused by the difference between LACP, LAG etc and the follow article has helped  

https://virtualizationreview.com/articles/2015/03/26/load-balancing-vsphere-vswitch-uplinks.aspx

In short a LAG is just a name for a grouping of NIC's and LACP is the 'protocol' they automatic negotiates a sets up a LAG if I am reading everything correctly
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.