Network Adapter Team Stops Working After ESX Server Upgrade (2201)
This situation can arise if you are running a 2.x bond in out-mac mode, and your physical switch is misconfigured with the corresponding ports as an EtherChannel. This worked with ESX Server 2.x, because no check was made by default for incoming packets on the bond. In ESX Server 3.0, the default is to accept incoming packets only on the appropriate link of the team. Reconfigure your physical switch not to create an EtherChannel for the team's ports, or reconfigure your virtual switch to use IP-based load balancing.