Summary: A possible cause for a disconnected VM after a vMotion
Date: Around 2014
Refactor: 26 January 2025: Checked links and formatting.

Symptom: after a vMotion the network card gets disconnected, and even when the box is checked, still the VM is not getting connected.
Issue: The vSwitch gets created with 120 ports by default, if the number of VMs/NICs goes over this there are no ports left. This is not checked by vMotion/DRS/HA so no warnings will be displayed. To solve it, vMotion the VMs back, change the number of ports of the vSwitch and reboot the host.