switch and NIC teaming in Hyper-v



  • I was looking at a system that someone else built and I have doubts as to how the network is set up due to the problems they are experiencing. It's a HP Proliant ML350 G9 running Hyper-V with 4 ports plugged in to a 3COM 3CRBSG2893.

    I don't have access to the system (yet) but is it possible that this configuration could work if they selected "Switch Independent" mode when they set up the NIC teaming?

    On one level I'm wondering if any of that was even necessary since they only have 30-40 users.



  • @Mike-Davis said in switch and NIC teaming in Hyper-v:

    On one level I'm wondering if any of that was even necessary since they only have 30-40 users.

    Good question. I've found that creating a LAGG group between switches can be a big help. Teaming mode on the server could be a good idea as well if the office is all running the same speed network connections. Question is always where the performance choke point is, disk, network, or something else.



  • @Mike-Davis

    Depends on what the problems are.

    Generally, "Switch Independent" teaming mode takes the switches out of the scenario, and Windows Server does the teaming work.

    Incoming connections to the server just use a single port, so it's more of a redundancy configuration rather than for more throughput.



  • @Mike-Davis said in switch and NIC teaming in Hyper-v:

    I was looking at a system that someone else built and I have doubts as to how the network is set up due to the problems they are experiencing. It's a HP Proliant ML350 G9 running Hyper-V with 4 ports plugged in to a 3COM 3CRBSG2893.

    I don't have access to the system (yet) but is it possible that this configuration could work if they selected "Switch Independent" mode when they set up the NIC teaming?

    On one level I'm wondering if any of that was even necessary since they only have 30-40 users.

    By default New-NetLbfoTeam uses switch independent.

    It most certainly improves bandwidth availability for outbound data.



  • I gave a more detail answer in your thread a year ago.
    https://mangolassi.it/topic/9704/nic-teaming-on-hyper-v/6



  • Good points. Now that I think about it, in this case it's pointless since they have a 1GB uplink to the main switch. Since all ports go in to one switch and there is only one 1GB uplink nothing is gained in terms or redundancy or bandwidth.



  • @Mike-Davis said in switch and NIC teaming in Hyper-v:

    Good points. Now that I think about it, in this case it's pointless since they have a 1GB uplink to the main switch. Since all ports go in to one switch and there is only one 1GB uplink nothing is gained in terms or redundancy or bandwidth.

    You always gain redundancy you can have 3 links fail.