/var/run/log/vmkernel.log shows BFD is flapping:
[nsx@6876 comp="nsx-esx" subcomp="bfd"]local: <local-ip-address>, remote: <remote-ip-address>, oldState: down, newState: up, diag: No Diagnostic, type: overlay
[nsx@6876 comp="nsx-esx" subcomp="bfd"]local: <local-ip-address>, remote: <remote-ip-address>, oldState: up, newState: down, diag: Neighbor Signaled Session Down, type: overlay
/var/run/log/vmkernel.log shows vmnic link flapping which is used for the uplink of NSX DVS:
netschedHClk: NetSchedHClkNotify:4654: vmnic4: link up notification
netschedHClk: NetSchedHClkWatchdogSysWorld:6522: vmnic4: link up event received, device running at 10000 Mbps so setting queue depth to 86460 bytes with expected 1310 bytes/us
Ipfix: IpfixPortDisableWithLock:1265: Disable non-uplink port. Uplink count: 2. Non-uplink port count: 1. Not need uplink update.
netschedHClk: NetSchedHClkNotify:4654: vmnic4: link up notification
netschedHClk: NetSchedHClkWatchdogSysWorld:6522: vmnic4: link up event received, device running at 10000 Mbps so setting queue depth to 86460 bytes with expected 1310 bytes/us
netschedHClk: NetSchedHClkNotify:4654: vmnic4: link up notificationVMware NSX 4.x
VMware NSX 3.x
This can be caused by unplugging the network cable or administratively downing the physical switchport. If this was not an intended link outage it will likely be an issue with the driver, firmware, SFP+ module, cable, and/or switchport of the physical switch.