Examples:
vSAN 7.0 U2 & later
The following table shows the Counters & their Thresholds used for the Network Cards (= pNic) being used for vSAN Traffic on a vSAN Host.
Metric | Warning Threshold | Critical Threshold |
---|---|---|
Rx CRC Errors | >0.1% | >1% |
Tx Carrier Errors | >0.1% | >1% |
Rx Errors | >0.1% | >1% |
Tx Errors | >0.1% | >1% |
Rx/Tx Pause | >1% | >10% |
Rx Missed Errors | >0.1% | >1% |
Rx Over Errors | >0.1% | >1% |
Rx Fifo Errors | >0.1% | >1% |
To evaluate the errors seen in the Error Message (as shown via Examples in section Issue/Introduction ), log into the vSAN Host via SSH/Putty and run the following command:
esxcli network nic stats get -n vmnic#
[root@Host:~] esxcli network nic stats get -n vmnic4
NIC statistics for vmnic4
Packets received: 17036123232
Packets sent: 1708000566
Bytes received: 2293939393939
Bytes sent: 229320239320
Receive packets dropped: 0
Transmit packets dropped: 0
Multicast packets received: 12333949
Broadcast packets received: 29343487
Multicast packets sent: 46123
Broadcast packets sent: 14599
Total receive errors: 0
Receive length errors: 0
Receive over errors: 0
Receive CRC errors: 0
Receive frame errors: 0
Receive FIFO errors: 0
Receive missed errors: 4545
Total transmit errors: 0
Transmit aborted errors: 0
Transmit carrier errors: 0
Transmit FIFO errors: 0
Transmit heartbeat errors: 0
Transmit window errors: 0
This is the information the vSAN Health Service uses to determine the error rate to alert on (or not).
All metrics monitored by this alarm describe conditions between the vmnic port and the physical switch port. If these metrics exceed the thresholds listed above, the cause for this excess should be investigated in the physical network.
Note: