well, hopefully VMware get a working QA given that we needed switch to the vmklinux drivers to get our networks back on HP DL360 Gen9, the reasn is that VMware got the drivers for the routine-patch-update from HP and both sdies thought someone will test them
not what i expect from a HCL as well as "we do not have that card in our labs" and not what i expect with a incldued driver for the *onboard* NIC of HP DL360 servers
This patch updates the ntg3
VIB to resolve the following issue:
- PR 2151342: Oversize packets might cause NICs using the ntg3 driver to temporarily stop sending packets
In rare occasions, NICs using the ntg3 driver, such as the Broadcom BCM5719 and 5720 GbE NICs, might temporarily stop sending packets after a failed attempt to send an oversize packet. The ntg3 driver version 4.1.3.2 resolves this problem.
This issue is resolved in this release
[root@esx2:~] esxcli software vib update --depot=/vmfs/volumes/nfs/updates/ESXi650-201811002.zip
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMW_bootbank_ne1000_0.8.3-8vmw.650.2.75.10884925, VMW_bootbank_ntg3_4.1.3.2-1vmw.650.2.75.1088492
yes, it was resolved by kill the network completly even without a working failover to the second NIC which is a different one to avoid exactly situations like this
after more than a whole month VMware came with this solution:
On the ESXi command line, run these commands to disable the ntg3 driver and enable the tg3 driver:
# esxcfg-module -d ntg3
# esxcfg-module -e tg3