vSphere ESXi: NIC Teaming based on switch port ID

NIC Teaming Policy: Route based on the originating virtual switch port ID
Choose an uplink based on the virtual port where the traffic entered the virtual switch. This is the default configuration and the one most commonly deployed.
When you see this setting, traffic from a given virtual Ethernet adapter is consistently sent to the same physical adapter unless there is a failover to another adapter in the NIC team.
Replies are received on the same physical adapter as the physical switch learns the port association.
This setting provides an even distribution of traffic if the number of virtual Ethernet adapters is greater than the number of physical adapters.
Note: If you select either srcPortID or srcMAC hash, you should not configure the physical switch ports as any type of team or bonded group.
-- VMware Virtual Networking Concepts

We have NIC1 connected to Switch1 and NIC2 connected to switch2. The two switches are trunked together. Although we have Spanning Tree enabled, we had ProCurve support review our switches and they determined that STP is not blocking any ports. Using the NIC Teaming policy based on port ID, does this mean that there will be no network loop?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If HP have reviewed your switches and given you the OKAY, then No.

Did you check that teaming is working, if you power off one of the switches?
On VMware vSwitches, packets received via one of the uplink ports are never forwarded to other uplinks.  This prevents forwarding loops without having to utilize something like spanning tree.

Broadcasts or multicasts from a guest are sent to other guests on the same port group internally, and through only one of the uplink ports.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.