Skip to main content
NetApp Knowledge Base

ATTO FibreBridge is unresponsive despite power cycling

Last Updated:

Applies to

  • FAS/AFF systems
  • ONTAP 9
  • Fabric-Attached MetroCluster
  • ATTO 7500N bridges


  • ATTO bridge unreachable alerts are reported in the event logs:

[Node-01: dsbridge_admin: bridge.removed:info]: FC-to-SAS bridge MCC-sw1:8.126L0 [ATTO  FibreBridge7500N 2.96] S/N [FB7500N119XXX] was removed.
[Node-01: schmd: hm.alert.raised:alert]: Alert Id = StorageBridgeUnreachable_Alert , Alerting Resource = 20000010XXXXXX00 raised by monitor system-connect

  • The nodes transition to a "Mixed-Path" configuration:

::> system node run -node <node> sysconfig -a

NetApp Release 9.5P6: Wed Jul 10 19:00:56 EDT 2019
    System ID: 053XXXXXXX (Node-01)
    System Serial Number: 72XXXXXXXXXX4 (lNode-01)
    System Rev: A4
    System Storage Configuration: Mixed-Path


  • The bridge is missing from sysconfig -a output:

FC-to-SAS Bridge:
MCC-sw2:10.126L0      : ATTO     FibreBridge7500N 2.96  FB7500N110XXX
MCC-sw2:8.126L0       : ATTO     FibreBridge7500N 2.96  FB7500N108XXX
MCC-sw1:10.126L0      : ATTO     FibreBridge7500N 2.96  FB7500N112XXX   >>>>>> Reported ATTO bridge is missing

  • The ATTO bridge is unresponsive to Telnet and serial console access.
  • The bridge does not boot even after a power cycle.

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.