Skip to main content
NetApp Knowledge Base

MetroCluster IP CRC errors on node network port

  1. Last updated
  2. Save as PDF
Views:
73
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster IP
  • ONTAP 9
  • Cisco switches

Issue

  • CRC errors are incrementing on a MetroCluster IP intercluster port:

Node CL01-N01
-- interface e0c (4 days, 15 hours, 18 minutes, 34 seconds) --

RECEIVE
Total frames: 15053m | Frames/second: 37566 | Total bytes: 28732g
Bytes/second: 71704k |Total errors: 17| Errors/minute: 0
Total discards: 0 | Discards/minute: 0 | Multi/broadcast: 807k
Non-primary u/c: 0 | Errored frames: 0 | Unsupported Op: 0
CRC errors: 17| Runt frames: 0 | Fragment: 0
Long frames: 0 | Jabber: 0 | Length errors: 0
Alignment errors: 0 | No buffer: 0 | Pause: 21920
Jumbo: 3464m | Error symbol: 0 | Bus overruns: 474k
Queue drops: 0 | LRO segments: 5452m | LRO bytes: 28012g
LRO6 segments: 0 | LRO6 bytes: 0 | Bad UDP cksum: 0
Bad UDP6 cksum: 0 | Bad TCP cksum: 0 | Bad TCP6 cksum: 0
Mcast v6 solicit: 0 | Lagg errors: 0 | Lacp errors: 0
Lacp PDU errors: 0

  • MCDC output shows no reason for the CRC errors

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.