Skip to main content
NetApp Knowledge Base

CLUSTER NETWORK DEGRADED CRC Errors Detected for all nodes

Views:
742
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
hw
Last Updated:

Applies to

Cluster Network Switch Cisco Nexus C3232C running NXOS version 7.0(3)I7(6)

Issue

  • All the nodes reporting high number of HW errors, continued packet loss and cluster network degraded:

[node_name-01: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e3b on node node_name-01 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
[node_name-01: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e3a on node node_name-01 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
[node_name-01: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif node_name-01_clus2 (node node_name-01) to cluster lif node_name-05_clus1 (node node_name-05).
[node_name-01: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif node_name-01_clus1 (node node_name-01) to cluster lif node_name-02_clus2 (node node_name-02).
[node_name-01: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Large MTU Packet Loss - Ping failures detected between node_name-01_clus2 ( 169.254.181.156 ) on node_name-01 and node_name-02_clus1 ( 169.254.162.103 ) on node_name-02

[node_name-02: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif node_name-02_clus1 (node node_name-02) to cluster lif node_name-05_clus1 (node node_name-05).
[node_name-02: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif node_name-02_clus2 (node node_name-02) to cluster lif node_name-01_clus1 (node node_name-01).
[node_name-02: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e3a on node node_name-02 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
[node_name-02: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e3b on node node_name-02 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
[node_name-02: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: CRC Errors Detected - High CRC errors detected on port e3a node node_name-02

[node_name-04: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e3a on node node_name-04 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
[node_name-04: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e3b on node node_name-04 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
[node_name-04: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif node_name-04_clus1 (node node_name-04) to cluster lif node_name-05_clus1 (node node_name-05).
[node_name-04: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif node_name-04_clus2 (node node_name-04) to cluster lif node_name-01_clus1 (node node_name-01).
[node_name-04: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: CRC Errors Detected - High CRC errors detected on port e3a node node_name-04

[node_name-05: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e3a on node node_name-05 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
[node_name-05: vifmgr: vifmgr.cluscheck.hwerrors:alert]: Port e3b on node node_name-05 is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
[node_name-05: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif node_name-05_clus1 (node node_name-05) to cluster lif node_name-04_clus1 (node node_name-04).
[node_name-05: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif node_name-05_clus2 (node node_name-05) to cluster lif node_name-01_clus1 (node node_name-01).
[node_name-05: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Large MTU Packet Loss - Ping failures detected between node_name-05_clus1 ( 169.254.20.13 ) on node_name-05 and node_name-02_clus1 ( 169.254.162.103 ) on node_name-02

  • No NetApp configuration in the applied Reference Configuration Files:

switch-01# show running-config
!Command: show running-config
!No configuration change since last restart
!Time: Thu Jan 26 17:48:50 2023
version 7.0(3)I7(6) Bios:version 08.38
...
vlan 1
vrf context management
  ip route 0.0.0.0/0 172.29.1.1
interface Ethernet1/1
interface Ethernet1/2
interface Ethernet1/3
...
interface Ethernet1/34
...

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.