vSphere 5.1 vSwitch: LACP & HP Trunk

We DO NOT have vSphere Distributed Switches. We only use standard vSwitches. To my understanding, LACP is only supported in vSphere 5.1 with Distributed Switches.

We also use HP ProCurve switches. Since LACP is not available to us, can we use HP Trunks instead?

My understanding is that LACP and HP Trunks are the same thing, so I'm assuming the answer is yes?
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
In answer to your question, YES - You can use static trunks on your HP Kit. NOT LACP.

HP Procurve supports LACP and Static Trunks.

Static Trunks work fine with ESXi.

When you create a trunk on a HP Procurve swtich, you can create Static or LACP trunks.

Between HP kit, e.g. Procurve to Procurve - LACP can be used, between non-HP kit, static trunks can be used.

These concepts are used in an ESXi/ESX network environment.

To accomplish network redundancy, load balancing, and fail-over, you must:

    Enable link aggregation on the physical switch.

    Note: Link aggregation is also known as Ether-Channel, Ethernet trunk, port channel, and Multi-Link Trunking.

    Set up the ESXi/ESX Virtual Switch configuration to be compatible with these concepts

see this VMware KB


ESXi 5.1 and 5.5 supports LACP on VDS only.
dipopoConnect With a Mentor Commented:
I do believe HP switches have the LACP protocol implemented, my understanding was if you create LACP the switchports are set to trunk.

Having said that, since you have standard switches would you not want to create a NIC team on the vSwitch and have the uplinks for that vSwitch connected to an Etherchannel on the physical switch, and then use load balancing via IP hash?
pzozulkaAuthor Commented:
Thanks to both.

dipopo: We have the vSwitch configured in NIC Team however the 1st NIC goes to our 1st core switch, and the 2nd NIC goes to our 2nd core switch.

Thus I think that's why we cant have link aggregation.
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

pzozulkaAuthor Commented:
hanccocka: In the article you posted, it says:
•ESXi/ESX host only supports NIC teaming on a single physical switch or stacked switches.
 •Link aggregation is never supported on disparate trunked switches.
If our vSwitch's 2 NICs are connected to two different core switches (ProCurve), and the two core switches are connected via:

trunk A14,B14,C14,C16 Trk1 Trunk

Is that considered disparate trunked switches -- meaning Link aggregation is not supported?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
are both HP Procurves the same type and configuration of switch?
pzozulkaAuthor Commented:
Both are 5304XL, and 99.9% same config.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Test your configuration to confirm working.
pzozulkaAuthor Commented:
I'm just curious about the article you suggested. What does this mean?
disparate trunked switches
Does this config: trunk A14,B14,C14,C16 Trk1 Trunk
mean that we have disparate trunked switches?
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
That configuration does not mean anything.

VMware's term of disparate trunked switches, means two different switches trunked together.

e.g. a Netgear and a Belkin!
pzozulkaAuthor Commented:
Excellent link!
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.

All Courses

From novice to tech pro — start learning today.