The upstream physical switch does not process or blocks Gratuitous ARP (GARP) and Reverse ARP (RARP) packets transmitted by ESXi upon migration.
Consequently, the physical switch continues forwarding traffic to the source ESXi host's physical switch port rather than relearning the VM MAC address on the destination host's switch port.
This issue can also occur if the upstream switch port lacks Spanning Tree Protocol (STP) PortFast/Edge Port configuration, causing port blocking during topology transitions.
1. Verify vMotion State on Destination ESXi Host
Confirm that the virtualization layer completed the migration successfully:
grep "MigrateSetStateFinished"/vmfs/volumes/<datastore>/<vm_name>/vmware.logMigrateSetStateFinished: type=2 new state=MIGRATE_FROM_VMX_FINISHED2. Verify Distributed Port Group "Notify Switches" Setting
3. Verify Physical Switch Configuration
Coordinate with your network engineering team to validate the following physical switch settings:
4. Monitor MAC Address Learning
Diagnostic Procedures
If the issue persists, capture network traffic on the destination ESXi host to verify packet transmission.
Identify VM Switchport ID and Uplink
net-stats -l | grep "<VM_Name>"Capture VM vNIC Traffic
Run pktcap-uw to capture ingress and egress traffic at the virtual NIC level:
pktcap-uw --switchport <Switchport_ID> --capture VnicTx,VnicRx --mac <VM_MAC_Address> --ng -o /tmp/vm_vnic_arp.pcapng
Capture Uplink RARP Broadcasts
Verify that ESXi successfully generates and transmits the RARP announcement out of the physical adapter:
pktcap-uw --uplink <vmnic_name> --capture UplinkSndKernel --mac <VM_MAC_Address> --ng -o /tmp/uplink_vmnic_rarp.pcapng
Review the resulting .pcapng files in Wireshark to confirm packet egress from the ESXi host.
For more information on troubleshooting steps, see Troubleshooting virtual machine network connection issues.
For further information on packet captures on ESXi, see Packet capture on ESXi using the pktcap-uw tool.
To perform packet captures with pktcap-uw:
Identify the VM Switchport and Uplink:
Locate the VM's active Switchport ID and the physical vmnic it utilizes on the destination host:net-stats -l | grep <VM_Name>
Capture VM ARPs (VnicTx/VnicRx):pktcap-uw --switchport <Switchport_ID> --capture VnicTx,VnicRx --mac <VM_MAC_Address> --ng -o /tmp/vm_vnic_arp.pcapng
Capture Uplink RARPs (UplinkSndKernel):
After a vMotion operation, the receiving host sends a RARP packet on behalf of the VM to update the rest of the network of the VM's new location.
Identify which uplink is used by the VM:
Type esxtop and press n for network.
Capture directly on the uplink to verify this egress traffic:pktcap-uw --uplink <vmnic_name> --capture UplinkSndKernel --mac <VM_MAC_Address> --ng -o /tmp/uplink_vmnic_rarp.pcapng