Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

CRC errors on MetroCluster IP or Cluster with BES-53248

Views:
1,028
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
metrocluster
Last Updated:

Applies to

  • ONTAP 9
  • MetroCluster IP or Cluster
  • BES-53248 
  • EFOS 3.4.3.3
  • EFOS 3.4.4.2

Issue

  • CRC errors reported on one or more cluster ports
  • May occur after ONTAP upgrade, causing poor performance on all nodes
  • Following is reported in EMS/event log: 

[cshmd: hm.alert.raised:alert]: Alert Id = SwitchIfOutErrorsWarn_Alert , Alerting Resource = switch/Slot: 0 Port: 9 25G - Level raised by monitor cluster-switch
[intr: netif.linkErrors:error]: Excessive link errors on network interface e0a. Might indicate a bad cable, switch port, or NIC, or that a cable connector is not fully inserted in a socket. On a 10/100 port, might indicate a duplex mismatch.
[vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0a on node  is reporting a high number of observed hardware errors, possibly CRC errors.

  • In Metrocluster IP environments, errors occur in conjunction with unsychronized log errors:

[monitor: monitor.globalStatus.critical:EMERGENCY]: Controller failover of affnode is not possible: unsynchronized log
[cf_main: cf.fsm.takeoverOfPartnerDisabled:error]: Failover monitor: takeover of affnode disabled (unsynchronized log).
[intr: netif.linkErrors:error]: Excessive link errors on network interface e0a. Might indicate a bad cable, switch port, or NIC, or that a cable connector is not fully inserted in a socket. On a 10/100 port, might indicate a duplex mismatch.
[vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0a on node affnode is reporting a high number of observed hardware errors, possibly CRC errors.

  • High CRC errors reported in ifstat output:

...
Non-primary u/c:     0  | CRC errors:        175k | Runt frames:         0

...

  • Interface errors reported on the switch ports connected to the cluster ports:

#show interface ethernet 0/14 output:

Total Packets Received with MAC Errors......... 4859
Jabbers Received............................... 3121
...
FCS Errors Received............................ 1738
...

Total Transmit Errors.......................... 106
...
Transmit errors................................ 106

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support