First a bit about my environment:
- Dell PowerEdge 2970
- Intel Quad-port I340-T4 10/100/1000 Ethernet HBA
- Intel driver version: 12.7.28.0 (installed drivers and PROSet using PROWinx64.exe, v. 18.3)
- Microsoft Windows Server 2008 R2 Datacenter w/SP1 (Core, with Hyper-V role)
- Cisco (Linksys) SRW2016 16-port full GbE (10/100/1000) switch
I used PROSetCL.exe and the SRW2016 web management interface to configure a 3-port LAG (in LACP mode). The NIC team comes up fine and I'm able to use it for "normal" network stuff. The teamed interface is used by the virtual servers / guests for network connectivity. I'm not doing anything with VMDq yet, although I'm interested in exploring it after I get VLANs working with teaming. Here is the output for PROSetcl.exe Team_GetTeamInfo 1:
1) TEAM : VMNetwork
Team Information:
Team GUID - '{305A7788-9AFC-4DD4-9B47-2CF0CF70412B}'
Team MAC - '001B21AEB9A5'
Team Mode - 'IEEE 802.3ad Dynamic Link Aggregation'
Team Name - 'VMNetwork'
And the output for PROSetcl.exe Team_EnumerateAdaptersInTeam 1:
1) TEAM : VMNetwork
Number of adapters currently present: 3
4) TEAM : VMNetwork - Intel(R) Ethernet Server Adapter I340-T4
3) TEAM : VMNetwork - Intel(R) Ethernet Server Adapter I340-T4 #4
2) TEAM : VMNetwork - Intel(R) Ethernet Server Adapter I340-T4 #3
On the SRW2016, the LAG corresponding to these 3 network interfaces is configured for VLAN trunking, untagged in VLAN 1 and tagged in all other VLANs. Somewhere in my explorations, I stumbled on a suggestion to also configure individual ports for VLANs, but when I tried this on the SRW2016, it wouldn't let me add the ports to a LAG. So, I can configure VLANs on a LAG, but the individual ports (apparently in trunk mode) are excluded from all VLANs.
I haven't set any VLAN configuration (using PROSetCL.exe) on the team (or individual NICs) in Hyper-V, and the related documentation I've read suggests that not only is it unnecessary, doing so is undesirable. My understanding is that if I set any VLAN configuration at the Hyper-V host level, then I must configure all VLANs I wish to be used by Hyper-V guests.
See:
http://www.intel.com/support/network/sb/cs-030993.htm
http://social.technet.microsoft.com/wiki/contents/articles/151.hyper-v-virtual-networking-survival-guide.aspx#Understanding_Hyper-V_VLANs
http://www.aidanfinn.com/?p=10164
For Hyper-V host management, I'm using a separate / dedicated NIC (not the teamed NIC interface) not involving VLANs. So, in Hyper-V's virtual switch connected to the teamed network interface, the option Allow management operating system to share this network adapter is unchecked, and there are no VLAN settings at that level.
One Hyper-V guest (running Windows Server 2008 R2 Standard) is multi-homed (two hybrid virtual network adapters). One of the adapters is configured for VLAN identification (in Hyper-V's settings, not inside the guest OS). Inside the guest OS, an appropriate IP address is assigned to the adapter, but the guest cannot communicate with other hosts on the VLAN it is configured for.
I'm just now beginning to think I should be using VMLB instead of LACP...? Am I correct in thinking that with VMLB, teaming is one-sided, meaning the physical switch knows nothing of the team configuration, and physical switch ports are configured individually? Or do I need a physical switch that understands / supports VMLB?
I would appreciate any suggestions on troubleshooting or getting this to work.
Thank you!