This is a known issue impacting VMware NSX.
You can use any one of the methods listed below to workaround the issue:
- Disable VTEP HA feature and then confirm reproducibility of the issue. If the issue still persists, power the impacted VMs off and on to resolve the issue.
or
- Disable Network I/O Control or NUMA reservations for VMs on overlay segments. If the issue still persists, power the impacted VMs off and on to resolve the issue.
or
- Change uplink profile to use two vTEPs for overlay with TEP HA and Network I/O control enabled for the overlay VMs.
Note: If there are no overlay VMs with Network I/O Control, or NUMA configured on the host, then customer need not disable TEP HA.