vSAN alarm "High pNic error rate detected" due to "Receive CRC errors".
Article ID: 418667
Updated On:
Products
Issue/Introduction
- vSAN alarm for "High pNic error rate detected" triggered.
- Output of "
esxcli network nic stats get –n vmnic#" ran on the ESXi host CLI shows the NIC errors are due to "Receive CRC errors".
NIC statistics for vmnic#: Packets received: 21416979733 Packets sent: 662987 Bytes received: 15230944710898 Bytes sent: 152483213 Receive packets dropped: 0 Transmit packets dropped: 0 Multicast packets received: 126740264 Broadcast packets received: 2797349323 Multicast packets sent: 662965 Broadcast packets sent: 22 Total receive errors: 5951636 Receive length errors: 0 Receive over errors: 0 Receive CRC errors: 5951636 Receive frame errors: 0 Receive FIFO errors: 0 Receive missed errors: 0 Total transmit errors: 0 Transmit aborted errors: 0 Transmit carrier errors: 0 Transmit FIFO errors: 0 Transmit heartbeat errors: 0 Transmit window errors: 0
Environment
VMware vSAN
VMware ESXi
Cause
- A cyclic redundancy check (CRC) is an error-detecting code commonly used in digital networks and storage devices to detect accidental changes to digital data.
- CRC errors are an indication of a fault in the physical networking components, most commonly a faulty network cable but also possibly a faulty SFP or, less likely, a problem in the NIC driver/firmware.
Resolution
Engage your physical network team and/or network vendor(s) to investigate the physical network components (network cable, network adapter, NIC driver/firmware) related to the affected vmnic to address the cause of the CRC errors.
Additional Information
For additional information see Virtual Machines or ESX host network interruption with “Receive CRC errors” statistics increased rapidly.
For additional details on the "High pNic error rate detected" alarm, see vSAN -- Alarm about high pNIC error rate being detected.
Feedback
