Hi all,
I was trying to configure vMotion properly in my new environment and cant seem to get it right, or working for that matter.
I have 3 hosts, each are using 2 x fibre channels (lets call them Fibre A and Fibre B) and 1 x copper port. I have a DVSwitch and various port groups in there; management, iSCSI A, iSCSI B and vMotion all with correct vLans assigned.
I created a vmkernel adapter for vMotion for each host (ticked vMotion box), which is uplinking to Fibre A only. Fibre B and copper are not being used for this.
However, vMotion does not work! I cannot do live migrations. So I Googled through and came across an article saying I'd have to create additional TCP/IP stack for vMotion.
So I created it via CLI esxcli network ip netstack add -N="vMotion"
Then I created new vmkernel adapter and select the new stack and as soon as I do that, all the available options become greyed out, thus vMotion still does not work.
What am I missing here? Any ideas?
