Definitely not A or B. Those options don't really make sense in the context of a simple vMotion migration. I'm going with C, the MTU mismatch, as the correct answer here.
Ha! I bet the admin forgot to update their DNS records after the migration. No wonder the VM can't be pinged - it's probably still pointing to the old IP address!
D seems like the most likely culprit to me. If the destination portgroup has an incorrect VLAN tag, that would definitely prevent the VM from being able to communicate on the network.
I think the answer is C. An MTU mismatch can definitely cause connectivity issues after a vMotion migration. The virtual machine's network settings may not have been properly updated on the destination host.
Venita
19 days agoAdelle
20 days agoBilli
21 days agoCarlton
2 months agoBrandee
2 months agoGwenn
2 months agoCecily
2 months ago