CRC Errors Detected - High CRC errors detected on cluster port due to Faulty SFP/cable

Last updated

Mar 31, 2025
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 1,720

Visibility:: Public

Votes:: 0

Category:: fabric-interconnect-and-management-switches

Specialty:: hw

Last Updated:: 3/31/2025, 12:03:27 AM

Applies to

ONTAP 9
FAS/AFF Systems
Cluster switches

Issue

One cluster network port reports, hourly, a high amount of CRC errors.

Example:

[Node-01: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e0a on node Node-01 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).

[Node-01: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: CRC Errors Detected - High CRC errors detected on port e0a node Node-01

Multiple system health alerts point to the source of the issue.

Example:

NodeIfInErrorsWarnAlert

The percentage of inbound packet errors of node "node_name-01" on interface "e0a" is above the warning threshold.

ClusterIfInErrorsWarn_Alert

The percentage of inbound packet errors of switch interface "switch_name-01/Slot: 0 Port: 2 25G - Level" is above the warning threshold.

The percentage of outbound packet errors of switch interface "switch_name-01/Slot: 0 Port: 1 25G - Level" is above the warning threshold.

The cluster LIFs of all nodes report total packet loss events to a single cluster LIF:

[Node-01: vifmgr: vifmgr.cluscheck.droppedall:alert]: Total packet loss when pinging from cluster lif Node-01_clus2 (node Node-01) to cluster lif Node-02_clus2 (node Node-02). [Node-01: vifmgr: vifmgr.cluscheck.droppedall:alert]: Total packet loss when pinging from cluster lif Node-02_clus1 (node Node-01) to cluster lif Node-02_clus2 (node Node-02).

Errors received in one port and transmitted to the other:

BES-53248 Cluster switches:

(switch_name-01)#show interface 0/1 Interface :.................................. 0/1 Packets Received Without Error................. 24203865 Packets Received With Error.................... 0 Broadcast Packets Received..................... 4279 Receive Packets Discarded...................... 375 Packets Transmitted Without Errors............. 24677379 Transmit Packets Discarded..................... 897376 Transmit Packet Errors......................... 897376 ...

(switch_name-01)#show interface 0/2 Interface :.................................. 0/2 Packets Received Without Error................. 15630167 Packets Received With Error.................... 1019693 Broadcast Packets Received..................... 2265 Receive Packets Discarded...................... 13565 Packets Transmitted Without Errors............. 15644072 Transmit Packets Discarded..................... 1156 Transmit Packet Errors......................... 0 ...

Cisco Cluster switches:

(switch_name-01)#show interface Ethernet1/12 Ethernet1/1/2 is up admin state is up, Dedicated Interface Hardware: 10000 Ethernet, address: dc0b.0919.9299 (bia dc0b.0919.9299) MTU 9216 bytes, BW 10000000 Kbit , DLY 10 usec

RX 5319553944 unicast packets 1070121 multicast packets 1179662 broadcast packets 5579105056 input packets 15897572746528 bytes 1855198116 jumbo packets 0 storm suppression bytes 0 runts 518955 giants 256782374 CRC 0 no buffer 257301329 input error 0 short frame 0 overrun 0 underrun 0 ignored 0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop 0 input with dribble 0 input discard 0 Rx pause

System health subsystem show command can can report Motherboard and/or Switch Health as 'degraded' and trigger the NodeIfInErrorsWarnAlert.