hypercat wrote:
Perhaps you can explain in more detail what you mean by it being a "small advantage."
It is a quite small advantage over the default policy called Port Id.
With the Port Id NIC teaming policy you will get a decent load balancing over the VMs, you will get fault tolerance, you have the possibility to connect to two physical switches for increased network redundancy and you need no specific Link Aggregation setup at the pSwitches.
For IP Hash the only advantage is that a single VM could, if having multiple connections with different outside IP hosts, use both vmnics (physical nic ports) at the same time, where on Port ID a single VM only uses a single vmnic. The disadvantage is that it does not allow standard based connections to more than one physical switch, it is critical that both vSwitch and physical switch are correctly configured as a static LAG.
In your case it does seems like that physical switch is not setup the way it should to work with vSphere IP Hash, making this strange connection losses happens. From that my first question was if you does in fact really need the IP Hash or if going back to Port Id would be a good enough setup.