/var/run/log/vmkernel.logBFD_HandleStatusChange:859:[nsx@6876 comp="nsx-esx" subcomp="bfd"]local: <local-vmk-ip>, remote: <remote-vmk-ip>, oldState: up, newState: down, diag: Neighbor Signaled Session Down, type: overlayBFD_HandleStatusChange:859:[nsx@6876 comp="nsx-esx" subcomp="bfd"]local: <local-vmk-ip>, remote: <remote-vmk-ip>, oldState: down, newState: up, diag: No Diagnostic, type: overlayBFD_HandleStatusChange:859:[nsx@6876 comp="nsx-esx" subcomp="bfd"]local: <local-vmk-ip>, remote: <remote-vmk-ip>, oldState: up, newState: down, diag: Neighbor Signaled Session Down, type: overlayBFD_HandleStatusChange:859:[nsx@6876 comp="nsx-esx" subcomp="bfd"]local: <local-vmk-ip>, remote: <remote-vmk-ip>, oldState: down, newState: up, diag: No Diagnostic, type: overlay
/var/run/log/vmkernel.log
netschedHClk: NetSchedHClkNotify:4654: vmnicX: link up notificationVMware NSX
VMware vSphere ESXi
The issue is typically caused by a faulty vmnic, which results in the corresponding vmk VTEP (Virtual Tunnel Endpoint) flapping.
Such flapping, in turn, leads to network interruptions for the VMs.
To resolve this issue, contact the hardware vendor (both for the server and the physical switch) to further troubleshoot and identify the root cause of the vmnic fault.
Faulty cable could also lead into this situation. In such situations, replacing the cable is recommended.