I've done a couple of such upgrades lately, and never had any issues with vMotion.
What's vMotion complaining about, i.e. do you see any error messages?
What error do you get?
Can you ping from one vMotion interface to another?
Yes am able to ping the ip's. Can we suspect update issue in the host?
Only one host affected with the vMotion issue? Or more hosts?
Did you use vmkping to ping the IPs?
No know issues as such with Host upgrades,
@VPXA Can u share your hosts and cluster details.
a. Please provide the Source host, and Destination host details and vSphere versions.?
b. VM for migration in Question ?
c. Is the migration within the cluster or across ?
d. Do we have vMotion defined on a separate vmk instance or shared along with the Mgmt vmk instance ?
Is there any error message observed while vMotion ? what percentage does the migrations fail ?
I'm open for further discussions
migration could be avoieded due to any missing pre-requisites such as mounted CD-rom device on VM, VM using local datastore datastore not shared between hosts, unconfigred vmotion ports. You get error explaination in validation page of migration wizard, please post that snippet.