vMotion fails after dvSwitch upgrade

I upgraded my vMotion switch and turned on enhanched LACP, somehow this “failed”. Didn’t think more about it right then, but DRS/vMotion started to generate alot of errors saying:

Migration [-1062718448:1458298954171534] failed to connect to remote host <192.168.52.11> from host <192.168.52.16>: Host is down.
vMotion migration [-1062718448:1458298954171534] failed to create a connection with remote host <192.168.52.11>: The ESX hosts failed to connect over the VMotion network
The vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network. Check the vMotion network settings and physical network configuration.
The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct.

What I had to do was to go in to the switch, assign old adapters to the newly created LAG interfaces and configure them as the only uplinks.
And off we go! 🙂
This change didn’t cause any network interruptions for me.