Ok, I am reconfiguring my networking across my 3 hosts. I did have vMotion (using VLAN50) in a dedicated vSwitch using uplink vmnic0. vMotion between hosts worked fine. It looked like this...
I want to move vMotion to a shared vSwitch with the management network. So I removed vmnic0 from vSwitch2 and added it to vSwitch4. I then created a new port group for vMotion with a new IP address. See below.
Within the properties of vSwitch4, the management network has vmnic7 as active and vmnic0 as standby. vMotion is configured opposite to this. The vSwitch is configured to load balance based on originating virtual port ID.
vMotion is not working between hosts and gets stuck at 14%. I get a timeout between 10.10.50.70 and 10.10.50.71 (other host).
I'm sure my physical switch is setup correctly. I have both ports accepting traffic on the Management and vMotion VLANs. If I switch around the vmnic allocation (so management is using vmnic0 as active and vmnic7 as standby) then I can still ping the management IP. Also, if I move vmnic0 back to vSwitch2, vMotion starts working again so I assume I am missing something on the ESXi side.
What am I missing?
Thanks in advance
