Skip to main content
NetApp Knowledge Base

Bridge Unexpected Reboot: CRIT FC Chip Error

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

Applies to

  • Fabric/Stretch MetroCluster
  • ONTAP 9
  • ATTO FibreBridge 7500N
  • ATTO Bridge Firmware v3.17/v3.20

Issue

  • One or more ATTO FB7500N devices experience unexpected reboots
  • The bridge event log shows an error similar to the below:
    CRIT FC Chip Error, Status: 0x81000000, Error1: 0x52004C6A
  • Reboot signature matches:
    INFO ST[1ba12000-1ba13000] | FP[1ba12b8c] CPSR[60000193]
    INFO 0014ba9c<-00264ce4 | SP[1ba12b90] FP[1ba12bfc]
    INFO 00264bb8<-00000584 | SP[1ba12c00] FP[1ba12c44]
    INFO 001d8cdc<-00d2844c | SP[1ba12c48] FP[1ba12f74]
    INFO 00d27f98<-00d0d3d0 | SP[1ba12f78] FP[1ba12fa4]
    INFO 00d0d33c<-00d13324 | SP[1ba12fa8] FP[1ba12fcc]
    INFO 00d130d0<-0004168c | SP[1ba12fd0] FP[1ba12ffc]
    INFO 00041530<-003ea210 | SP[1ba13000] FP[1ba13000]​​​​ 

 

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.