Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I thought I could figure this out but can't.

I'm trying to take vmnic2 and vmnic3 and create a vSwitch for just the VM's to use.

I can do this part just fine.

But I can't seem to team them together. I was told that I should create the teaming on the switch (an Extreme Networks x450 switch) but when I do so (whether as L2 or L3 team) I can no longer route outside the switch.

Without the switch teaming on the network switch everything routes fine (from my workstation for example to the VM). Once I enable port sharing/teaming though I can no longer get to the VM from my workstation or vice versa.

Any ideas?

share|improve this question

Make sure you're not configuring your switch for LACP teaming. It needs to be "hard set" to a team. VMware does not support LACP teams.

share|improve this answer
ESX 3.x does support 802.3ad and LACP in STATIC configurations. – Joseph Jun 5 '09 at 22:57
No, it's basic L2 address-based teaming. If I do it for a physical server with 2 nics it works but the same teaming doesn't seem to work for vmware. Is there something to configure in the vswitch settings as well? – TheCleaner Jun 6 '09 at 12:43
up vote 2 down vote accepted

I figured it out.

In an Extreme Networks switch the proper command is:

enable sharing grouping algorithm address-based L3

This will ensure it uses IP based port sharing.

Then in the Virtual Switch properties, set the Load Balancing setting to "Route based on ip hash".

That took care of it and allows for both inbound and outbound load balancing.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.