How does hp nic teaming work

In the New Team dialog box, we have several options to choose from:. This can be anything you want, we chosed EthernetTeam. Then we have to select the members of the team. Then we have Additional properties. Which means, it would be enough to just click OK after you selected the NICs and everything would be fine. Teaming Mode is the mode the team will work on. We have several options:. We have one which is switch independent and we have two which are switch dependent.

The switch independent options mean that we do not have to make any configuration changes on the switch side. Once we are done with the above configuration, we click OK and wait for the teaming to come online. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. Rate this article: 0. Imagine, this still runs as a top find in Google when searched.

I understand why. Clear, succinct and worth the read Thank you for this…. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account.

You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. Blog at WordPress. HP generally provides following NIC teaming capabilities and algorithms: 1. Regards Ramazan. Rate this:. You want to share this? Email Facebook Twitter. Like this: Like Loading Any further thoughts?

Let me know here Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public. Name required. Follow Following. Join 64 other followers. Sign me up.

Already have a WordPress. Log in now. You should not use Depending on the switch configuration mode and the load distribution algorithm, NIC teaming presents either the smallest number of available and supported queues by any adapter in the team Min-Queues mode or the total number of queues available across all team members Sum-of-Queues mode.

If the team is in Switch-Independent teaming mode and you set the load distribution to Hyper-V Port mode or Dynamic mode, the number of queues reported is the sum of all the queues available from the team members Sum-of-Queues mode. Otherwise, the number of queues reported is the smallest number of queues supported by any member of the team Min-Queues mode.

When the switch-independent team is in Hyper-V Port mode or Dynamic mode the inbound traffic for a Hyper-V switch port VM always arrives on the same team member. When the team is in any switch dependent mode static teaming or LACP teaming , the switch that the team is connected to controls the inbound traffic distribution.

The host's NIC Teaming software can't predict which team member gets the inbound traffic for a VM and it may be that the switch distributes the traffic for a VM across all team members. When the team is in switch-independent mode and uses address hash load balancing, the inbound traffic always comes in on one NIC the primary team member - all of it on just one team member.

Since other team members aren't dealing with inbound traffic, they get programmed with the same queues as the primary member so that if the primary member fails, any other team member can be used to pick up the inbound traffic, and the queues are already in place.

Following are a few VMQ settings that provide better system performance. The first physical processor, Core 0 logical processors 0 and 1 , typically does most of the system processing so the network processing should steer away from this physical processor.

Some machine architectures don't have two logical processors per physical processor, so for such machines, the base processor should be greater than or equal to 1. If in doubt assume your host is using a 2 logical processor per physical processor architecture.

If the team is in Sum-of-Queues mode the team members' processors should be non-overlapping. For example, in a 4-core host 8 logical processors with a team of 2 10Gbps NICs, you could set the first one to use the base processor of 2 and to use 4 cores; the second would be set to use base processor 6 and use 2 cores.

Configure your environment using the following guidelines:. Before you enable NIC Teaming, configure the physical switch ports connected to the teaming host to use trunk promiscuous mode. The physical switch should pass all traffic to the host for filtering without modifying the traffic. Never team these ports in the VM because doing so causes network communication problems. It's easily possible to configure the different VFs to be on different VLANs and doing so causes network communication problems.