Skip to main content
NetApp Knowledge Base

Brocade FC port flapped with multiple errors due to SFP not seated properly

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

Applies to

  • Brocade switch
  • FCP

Issue

  • Brocade FC port is online and in In_Sync state as per switchshow output.

Index Slot Port Address Media  Speed        State    Proto
============================================================
233   11   25   6vxcxc   id    N32   Online      FC  F-Port  1 N Port + 1 NPIV public 

 

  • In porterrshow, disc c3 and c3timeout tx errors are seen along with link fail and loss sync for this port.

/fabos/cliexec/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
233:   42.2g   52.2g    0       0       0       0       0       0       0       1.4k    6       4       0       0       0       1.4k    0       0       0    

  • Rx & Tx values are in optimal range as per sfpshow output.

Slot 11/Port 25:
=============
Identifier:  3    SFP
Connector:   7    LC
[..]
Vendor Name: BROCADE         
Vendor OUI:  00:05:1e
Vendor PN:   57-1000333-01   
[...]
RX Power:    -0.9    dBm (807.10uW) 
TX Power:    0.4     dBm (1087.50 uW) 

  • As per fabric logs port went offline & online also lot of Link resets, LR_IN & LR_OUT are seen as well.

Switch 0; Wed Dec 18 02:17:35 2024 IST (GMT+5:30)
23:42:40.741146 SCN LR_PORT(0);g=0x0 LR_IN                  D0,P0  D0,P0  233   NA    
23:42:50.725148 SCN LR_PORT(0);g=0x0 LR_IN                  D0,P0  D0,P0  233   NA    
23:44:54.098248 SCN LR_PORT(0);g=0x0 LR_OUT                 D0,P0  D0,P0  233   NA    
23:54:41.867639 SCN LR_PORT(0);g=0x0 LR_OUT                 D0,P0  D0,P0  233   NA    
02:43:35.902334 SCN Port Offline;rsn=0x4,g=0x454            D0,P0  D0,P0  233   NA    
02:43:35.902340 *Removing all nodes from port               D0,P0  D0,P0  233   NA    
02:43:35.934603 SCN LR_PORT(0);g=0x454                      D0,P0  D0,P0  233   NA    
02:43:40.879145 SCN LR_PORT(0);g=0x454                      D0,P0  D0,P0  233   NA    
02:43:40.942477 SCN Port Online; g=0x454,isolated=0         D0,P0  D0,P1  233   NA    
02:43:40.942550 Port Elp engaged                            D0,P1  D0,P0  233   NA    
02:43:40.942562 *Removing all nodes from port               D0,P0  D0,P0  233   NA    

  • As per errdump logs, port encountered frame timeout detected errors and and C3timeout Tx C3TXTO errors, along with these IO_FRAME_LOSS and IO_LATENCY_CLEAR are also seen.

2024/12/18-23:43:10 (IST), [MAPS-1001], 745461, SLOT 2 | FID 128 | PORT 11/25, CRITICAL, switch1, VSP_xcxcx_S0xcxcxR07_xcx-7x, F-Port 11/25, Condition=ALL_TARGET_PORTS(C3TXTO/min>3), Current Value:[C3TXTO, 12 Timeouts], RuleName=defALL_TARGET_PORTSC3TXTO_3, Dashboard Category=Port Health, Quiet Time=None.
2024/12/18-23:43:11 (IST), [AN-1014], 745462, SLOT 2 | FID 128, INFO, switch1, Frame timeout detected, tx port 11/25 rx port 11/20, sid 6xxdd0, did 6xxss1, timestamp 2024-12-18 23:43:11 .
2024/12/18-23:43:17 (IST), [MAPS-1001], 745560, SLOT 2 | FID 128 | PORT 11/25, CRITICAL, switch1, VSP_xcxcx_S0xcxcxR07_xcx-7x, F-Port 11/25, Condition=ALL_PORTS(DEV_LATENCY_IMPACT/NONE==IO_FRAME_LOSS), Current Value:[DEV_LATENCY_IMPACT, IO_FRAME_LOSS, (138 C3TX Timeouts) ], RuleName=defALL_PORTS_IO_FRAME_LOSS_UNQUAR, Dashboard Category=Fabric Performance Impact, Quiet Time=15 min.
2024/12/18-23:59:17 (IST), [MAPS-1005], 745890, SLOT 2 | FID 128 | PORT 11/25, WARNING, switch1, VSP_xcxcx_S0xcxcxR07_xcx-7x, F-Port 11/25, Condition=ALL_PORTS(DEV_LATENCY_IMPACT/NONE==IO_LATENCY_CLEAR), Current Value:[DEV_LATENCY_IMPACT, IO_LATENCY_CLEAR], Rule defALL_PORTS_IO_LATENCY_CLEAR triggered 6 times in 15 min and last trigger time Wed Dec 18 23:55:07 2024, Dashboard Category=Fabric Performance Impact.

  • Below troubleshooting steps can be followed to isolate the issue and before proceeding with solution.
    • Clean the connectors on either ends and reseat the cable.
    • Check the patch panel as well.
    • Check if cable passes the fluke meter test successfully.

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.