vMotion breaks vCenter connection to cluser

[Huntermaz]

We have recently moved to from a Windows vCenter 5.5 to a new 6.5 appliance. We are having problems with every time vCenter decides to vMotion itself the ESXi hosts in the cluster that it is in turn to not responding. The other cluster we have is fine. The only way it comes back it is to reboot the vCenter appliance. I know I can limit the movement of the vCenter appliance but we didn't have this problem with 5.5. Has anyone else seen this? Does anyone have any ideas?

[rcporto]

Besides the vCenter migration, did you make any change on the hosts and/or network for that particular host that stops to responding after the vCenter migration? And, after the host stops to responding to the vCenter, did you tested the network connectivity between the host and the vCenter VM?