This is a network issue.
So if I understand this correctly you have 3 hosts.
Host 1 is using 10.1.221.12 as its SAN vmkernel port IP, which in turn is also being used as a vMotion network.
Host 2 is using 10.1.222.13 as its SAN vmkernel port IP, also used for vMotion network.
Host 3 is most likely with a IP in the 10.1.222.X range.
So my first question:
Why is Host 1 using another IP range for the vMotion kernel as Host 2? And if that is OK (networks physically connected and no FW between them), have you tested connectivity (IP, port etc) by SSHing to host and using this KB as a starting point:http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2020669
Second question:
Everytime I see that error is because there is a second vMotion kernel that has a IP that is not connected to the vMotion kernels on the the other hosts, or the kernel have a wrong VLAN tag.
Please doublecheck if Host 1 has another vmKernel port that has the check mark for vMotion, or the VLANs between the vMotion vmk's are the same.
Hope this helps,
regards,
Larus.