vmkping -S vxlan -s 1460 -I vmkX -c 100 <Remote-Host-TEP-IP>#pktcap-uw --vmk vmk11 --dir 2 -o - | tcpdump-uw -enr - | grep -i <remote TEP IP> | grep -i <Local TEP IP>
#pktcap-uw --uplink vmnicX --capture UplinkSndKernel -o - | tcpdump-uw -enr - | grep -i <remote TEP IP> | grep -i <Local TEP IP>
vmkping -S vxlan -s 1460 -I vmkX -c 100 <Remote-Host-TEP-gateway-IP>VMware NSX
#pktcap-uw --uplink vmnicX --capture UplinkSndKernel,UplinkRcvKernel -o - | tcpdump-uw -enr - | grep -i <Remote-Host-TEP-gateway-IP>Since the packet drop is identified as occurring outside the ESXi host on the physical network, the issue must be resolved by the physical network team.
Engage the physical network team.
Request the team to check the physical network configuration (e.g., VLAN settings, switch port configuration, spanning tree) relevant to the two ESXi hosts' uplinks.
Instruct the team to trace the packets in the physical network infrastructure to precisely identify the drop point and correct the misconfiguration.