Skip to main content
NetApp Knowledge Base

FC-VI adapter: Discarded a received frame because of a receive frame error

  1. Last updated
  2. Save as PDF
Views:
469
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
metrocluster
Last Updated:

Applies to

  • Fabric-attached MetroCluster
  • ONTAP 9

Issue

  • EMS reports Discarded a received frame because of a receive frame error.

[Node-A: ispfcvi2500_main4: fcvi.qlgc.FrameDiscardErr:error]: FC-VI adapter: Discarded a received frame because of a receive frame error. Port 0f, QP name = WAFL, QP index = 4, exchange ID 0x1a5, address offset 0xa000, remote node's system id = xxxxxxx.

  • The FCVI port may be reset due to the receive frame errors:

[Node-A: ispfcvi2500_main2: fcvi.qlgc.receive.error:error]: FC-VI adapter: Received bad frame on port 0f. Mailbox-1 = 520, Mailbox-2 = 324. Resetting the port.
[Node-A: ispfcvi2500_port2: fcvi.update.link.state:notice]: FC-VI adapter: Physical link is down on port 0f.
[Node-A: fcvi_reset_proc: callhome.mcc.fcvi.reset:notice]: Call home for METROCLUSTER FCVI RESET
[Node-A: ispfcvi2500_port2: fcvi.update.link.state:notice]: FC-VI adapter: Physical link is up on port 0f.

  • The output of porterrshow command reports a lot of enc in, enc out, crc err, crc g_eof, bad e0f and link fail errors on the ISL port:

SwitchA:admin> porterrshow

porterrshow        :
          frames        enc     crc     crc     too     too     bad     enc    disc    link    loss    loss    frjt    fbsy     c3timeout     pcs      uncor
        tx       rx      in     err     g_eof   shrt    long    eof     out    c3      fail    sync    sig                      tx      rx      err     err

40:  317.6g  404.5g    2.8k    2.5k    2.5k    1       0      56     151.2k  120       51.4k   0       3       0       0       0      51       0       0
41:  462.1g  544.0g    0       0       0       0       0       0       3.3k  298       1       0       3       0       0       0     128       0       0

 

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.