Skip to main content
NetApp Stage KB

Bridge unreachable in-band

Views:
3
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

Helpful 

Applies to

  • ATTO 7500N FibreBridge
  • ATTO 7600N FibreBridge

Issue

The Bridge is unreachable in-band and is not responding to in-band commands:
 
mc1::> system health alert show
               Node: mc1-02
           Resource: ATTO_2000001086a83308

    Severity: Major
    Indication Time: Thu Aug 19 20:24:03 2021
           Suppress: false
        Acknowledge: false

Probable Cause: "ATTO_2000001086a83308" bridge is not reachable over management network.
Possible Effect: Bridge "ATTO_2000001086a83308" cannot be monitored for alerts.
 Corrective Actions: 1) If the bridge is monitored by SNMP, verify that the node management LIF is up
                     by using the "network interface show" command.
Verify that the "ATTO_2000001086a83308" bridge is alive by using the "network ping" command.

   2) If the bridge is monitored in-band, check the fabric cabling to the bridge, and then verify that the bridge is powered up.

mc1::> storage bridge run-cli -name ATTO_2000001086a83308 -command "info"
[Job 34738] Job succeeded: Bridge is currently unavailable. Wait a few minutes and then try the operation again.

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.
d9f2de46-358a-40ec-9b3d-3b6a65216ff0