This questions is for the optimal configuration required for Vsphere virtual switch's Network Load balancing. consider this environment:
2 Nexus 5010 switches (all supporting 10 GB ports)
Virtual switch which is used for VMport group and virtual machine port groups using two 10 GB uplinks using VLAN tagging
Each 10 GB uplink on the Vswitch is connected individually to the two Nexus switches
Nexus switches are uplinked using 2 x 10 GB port channel
The question are the following:
1 How should be the end port for the Uplinks used on the vSwitch be configured as on the physical switch? should that be configured as an " access port", " Trunk". As in this scenario each 10 GB uplink from the virtual switch would be connected to the two different switches.
2 If both the uplinks are connected to a single physical switch, how should they be configured on the phyiscal switch ? should they be configured as "Trunk", "Access" or "LACP" or "etherchannel"
3 If the ports on the physical switch are configured as "LACP" or "etherchannel" should the Network Load Balancing on the virtual switch be left to the default policy of "Port ID using the orginating port ID", would the "LACP" configured on the physical switch work without using "IP hash" policy on the virtual switch
4 Can the virtual switch be configured with "Port ID using originating port ID" and still the end ports configured for channel group in the physical switch.
5 Considering the same virtual switch configuration and a physical switch, which only has a 10 GB uplinks and no 10 GB access ports, can the uplinks used with the vSwitch be connected to the 10 GB uplink port on the physical switch. would it work with that configuration.