Skip to main content
NetApp Knowledge Base

Data service interruption during MetroCluster swithover with CRC in data ports

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

Applies to

  • Metrocluster IP
  • Data Switches

Issue

  • Data service interruption during MetroCluster switchover and switchback with:
    • Datastores offline
    • Aggregates online
    • Network interfaces up
    • LUNs mappeds and online
  • CRC errors noticed on one side of the MCC array for both nodes
    • CRC errors already present in ifstat before the issue 
    • Example:

Node: Cluster01-n01

-- interface  e4a  (136 days, 19 hours, 38 minutes, 22 seconds) --

RECEIVE
 Total frames:    61123k | Frames/second:       5  | Total bytes:      9351m
 Bytes/second:      791  | Total errors:    19203  | Errors/minute:       0
 ...
 CRC errors:      19036  | Runt frames:         0  | Fragment:            0
 ...
 Jumbo:               7  | Error symbol:        0  | Bus overruns:        0
 ...

Node: Cluster01-n02

-- interface  e4a  (136 days, 19 hours, 38 minutes, 14 seconds) --

RECEIVE
 Total frames:    74898k | Frames/second:       6  | Total bytes:     14696m
 Bytes/second:     1243  | Total errors:    11610  | Errors/minute:       0
 ...
 CRC errors:      11532  | Runt frames:         0  | Fragment:            0
 ...
 Jumbo:              11  | Error symbol:        0  | Bus overruns:        0
 ...

  • ONTAP Event Messag for network errors. Example:

ALERT:  vifmgr.cluscheck.hwerrors: Port e5a-603 on node node_name is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).

  • Lost connection to LUNs from Vsphere, until switchback was completed.

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.