NIC flapping and storage lost on host

Products

• VMware vSphere ESXi

Issue/Introduction

Errors seen:

/var/run/log/vmkernel.log

2025-10-14T09:29:00.856Z cpu54:2098257)qfle3: qfle3_attn_int_deasserted:18652: [vmnic2] Parity Error Occurred
2025-10-14T09:29:00.856Z cpu61:2098317)WARNING: qfle3: qfle3_parity_attn:16915: [vmnic6] Parity errors detected in blocks:
2025-10-14T09:29:00.856Z cpu61:2098317)qfle3: qfle3_parity_attn:16938: [vmnic6]
2025-10-14T09:29:00.856Z cpu61:2098317)qfle3: qfle3_attn_int_deasserted:18652: [vmnic6] Parity Error Occurred
2025-10-14T09:29:00.866Z cpu53:2098287)WARNING: qfle3: qfle3_parity_attn:16915: [vmnic4] Parity errors detected in blocks:
2025-10-14T09:29:00.866Z cpu53:2098287)qfle3: qfle3_parity_attn:16938: [vmnic4]
2025-10-14T09:29:00.866Z cpu53:2098287)qfle3: qfle3_attn_int_deasserted:18652: [vmnic4] Parity Error Occurred
2025-10-14T09:29:00.876Z cpu78:2098159)WARNING: qfle3: qfle3_parity_attn:16915: [vmnic0] Parity errors detected in blocks:
2025-10-14T09:29:00.876Z cpu78:2098159)qfle3: qfle3_parity_attn:16938: [vmnic0]
2025-10-14T09:29:00.876Z cpu78:2098159)qfle3: qfle3_attn_int_deasserted:18652: [vmnic0] Parity Error Occurred

/var/run/log/vobd.log

2025-10-14T09:29:02.825Z: [netCorrelator] 637813345861us: [vob.net.dvport.uplink.transition.down] Uplink: vmnic0 is down. Affected dvPort: 99/50 11 1f ea 9d 0c 9b 61-76 57 b5 35 96 93 1f 2e. 1 uplinks up. Failed criteria: 128

Environment

7.x

Cause

• Adapter hang/firmware failure detected with one or more HBA/NICs:

• Network adapter is down or fails with a failed criteria code 128.

 

 

 

Resolution

• For adapter hang/firmware failure:

  • Nic is possibly in a bad state or has outdated firmware

  • In cases this scenario might also result is momentary host not responding state due to device re-initialization

  • Please check for latest firmware/driver combination for the adapter in question.

  • If you see repeated failures, replacing the adapter might help.

• As per the Network adapter (vmnic) is down or fails with a Failed Criteria Code KB:

  • Failed Criteria 128 is the driver reporting a link state down.

  • This can be caused by unplugging the network cable or administratively shutting down 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.

  • Check the driver by following the Determining Network/Storage firmware and driver version in ESXi KB, and contact the host hardware vendor for further troubleshooting when failed criteria 128s are seen in the vobd log.