1V0-21.20 · Question #43
A vSphere administrator has migrated a virtual machine between two ESXi hosts using vSphere vMotion and notices that the VM can no longer be pinged. What caused this situation?
The correct answer is D. The destination portgroup has an incorrect VLAN tag.. Loss of network connectivity for a VM after vMotion, such as being unable to ping, is often caused by an incorrect VLAN tag configuration on the destination portgroup.
Question
A vSphere administrator has migrated a virtual machine between two ESXi hosts using vSphere vMotion and notices that the VM can no longer be pinged. What caused this situation?
Options
- AThe virtual machine has RDMs attached.
- BA different datastore is being used after the migration.
- CThere is an MTU mismatch.
- DThe destination portgroup has an incorrect VLAN tag.
How the community answered
(23 responses)- A9% (2)
- B4% (1)
- C13% (3)
- D74% (17)
Why each option
Loss of network connectivity for a VM after vMotion, such as being unable to ping, is often caused by an incorrect VLAN tag configuration on the destination portgroup.
RDMs (Raw Device Mappings) affect storage access for a VM, not its network connectivity, as long as the RDM is accessible by the destination host.
Using a different datastore after migration affects where the VM's files are stored, but not its network connectivity, assuming the datastore is accessible.
An MTU mismatch can cause network performance problems or packet drops, particularly for large packets, but typically not a complete inability to ping or communicate.
If the virtual machine's network adapter is connected to a portgroup on the destination ESXi host that has an incorrect or missing VLAN tag, the VM will be on the wrong network segment and unable to communicate with other devices, resulting in a loss of network connectivity.
Concept tested: vSphere vMotion network troubleshooting
Source: https://kb.vmware.com/s/article/1003893
Topics
Community Discussion
No community discussion yet for this question.