I ran into this issue today and the fix wasn't one listed. I have a six host cluster, set up with ip hashing on the NICs used for my iSCSI traffic. Both NICs were active on the vswitch and the vm...
See more...
I ran into this issue today and the fix wasn't one listed. I have a six host cluster, set up with ip hashing on the NICs used for my iSCSI traffic. Both NICs were active on the vswitch and the vmotion kernel, but the order of the NICs, even while active, caused this issue for me. The host has been running fine for 8 months, but last night started having this issue. Swapping the NIC order, even while keeping both active, fixed the problem.