Unfortunately the new driver didn't help. I just lost network connectivity again. Again while watching youtube on my Apple TV going through a virtual Sophos UTM. I was able to collect the logging using the commands earlier in this thread. So if you're interested I can upload them. The vmkernel.log reports this at the moment of loss of network connectivity:
2017-05-27T01:23:14.379Z cpu6:142894)NetLB: 2242: Driver claims supporting 0 TX queues, and 0 queues are accepted.
2017-05-27T01:23:14.379Z cpu6:142894)NetLB: 2246: Driver claims supporting 0 RX queues, and 0 queues are accepted.
2017-05-27T01:23:14.380Z cpu6:142894)NetLB: 2242: Driver claims supporting 0 TX queues, and 0 queues are accepted.
2017-05-27T01:23:14.380Z cpu6:142894)NetLB: 2246: Driver claims supporting 0 RX queues, and 0 queues are accepted.
2017-05-27T01:23:14.380Z cpu6:142894)NetLB: 2242: Driver claims supporting 0 TX queues, and 0 queues are accepted.
2017-05-27T01:23:14.380Z cpu6:142894)NetLB: 2246: Driver claims supporting 0 RX queues, and 0 queues are accepted.
2017-05-27T01:23:14.381Z cpu6:142894)NetLB: 2242: Driver claims supporting 0 TX queues, and 0 queues are accepted.
2017-05-27T01:23:14.381Z cpu6:142894)NetLB: 2246: Driver claims supporting 0 RX queues, and 0 queues are accepted.
2017-05-27T01:23:14.382Z cpu6:142894)WARNING: Tcpip_Vmk: 781: vmk_get_gateway failed with error = 0x2d, status = 0xbad0105
2017-05-27T01:23:14.382Z cpu6:142894)WARNING: Tcpip_Vmk: 781: vmk_get_gateway failed with error = 0x2d, status = 0xbad0105
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 129: get connection pkt trace failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 129: get connection pkt trace failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 96: get connection stats failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 129: get connection pkt trace failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 129: get connection pkt trace failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 96: get connection stats failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 129: get connection pkt trace failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 129: get connection pkt trace failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 96: get connection stats failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 129: get connection pkt trace failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 129: get connection pkt trace failed with error code 195887136
2017-05-27T01:23:14.383Z cpu6:142894)Tcpip_Vmk: 96: get connection stats failed with error code 195887136
I have the correct driver installed:
[root@esxi:~] vmkload_mod -s ntg3 | grep Version
Version: 4.1.2.0-1vmw.650.0.0.4598673
I'm running vSphere 6.5 on an HP Proliant DL360p gen8
Franc.