vmkernel.log:
XXXX-XX-XXTXX:XX:XX.XXXZ In(182) vmkernel: cpu36:2320994)bnxtnet: dev_dump_fw_trace:159: [vmnic5 : 0x45215eb40000] Dumping FW Trace:
XXXX-XX-XXTXX:XX:XX.XXXZ In(182) vmkernel: cpu36:2320994)bnxtnet: dev_print_fw_data:126: [vmnic5 : 0x45215eb40000] == START OF TRACE ==
XXXX-XX-XXTXX:XX:XX.XXXZIn(182) vmkernel: cpu36:2320994)bnxtnet: dev_print_fw_data:138: [vmnic5 : 0x45215eb40000] == END OF TRACE ==
XXXX-XX-XXTXX:XX:XX.XXXZ In(182) vmkernel: [00697466] <wrn> health_check: CRT HW SOFT ERROR: Code=0x11F4 Reg=te_nic_int_sts_1 Addr=0x8243001C d1=0x0 d2=0x0\
The issue is caused by a telemetry calculation anomaly in the bnxtnet driver version 236.1.128.0-1OEM. Under certain conditions, hardware queue stats reset or overflow incorrectly during device quiesce/activate operations, leading the driver to report erroneous "Bytes Received" counters to vCenter.
To resolve this issue, align the driver and firmware with the VMware Compatibility Guide (HCL) and update the driver to a below version.