Post the migration of a Virtual Machine (VM) via vMotion, a network connectivity drop lasting 5-10 seconds occurs. Simultaneous network packet captures from both the source and destination ESXi hosts reveal the following:
Destination Host: Upon completing the migration, the destination ESXi host successfully transmitted a Reverse ARP (RARP) broadcast. This is the standard mechanism used to update the physical switch's MAC address table with the VM's new location. We can see the VM successfully transmitting outbound traffic; however, the capture logs "No response found" for the incoming gateway replies.
Source Host: Even after the VM migrated to the new host and the RARP was sent, the reply packets from the 192.168.x.x gateway were still arriving at the source host's physical uplink. Because the VM no longer resided on this host, these packets were naturally dropped.
VMware vSphere ESXi
VMware vCenter Server
A stale MAC address table (CAM table) within the physical switch fabric delays or drops the Reverse ARP (RARP) packet from the destination host, causing return traffic to route to the source host instead of the new destination host.
This is not VMware/ Broadcom network stack issue. This is purely physical switch related issue. In order to resolve, following should be verified at physical switch fabric.