Skip to main content
NetApp Knowledge Base

After DWDM issues MetroCluster IP Switch ISL did not come up again

Views:
51
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster IP
  • Cisco back-end switches

Issue

  • After DWDM issues, MetroCluster IP Switch ISL did not come up again
  • ISCSI Initiators are down as per the command output:

cluster01A::*> set advanced
cluster01A::*> storage iscsi-initiator show -status-oper down
                                                                       Status
Node Type Label    Target Portal      Target Name                      Admin/Op
---- ---- -------- ------------------ -------------------------------- --------
cluster01A-01
     dr_auxiliary
          mccip-aux-a-initiator
                   10.1.1.4:65200     iqn.2016-02.com.netapp:abcd1234efgh5678ijkl91011mnop1213
                                                                         up/down
              Failure Reason:  Operation timed out
          mccip-aux-a-initiator2
                   10.1.1.4:65200     iqn.2016-03.com.netapp:abcd1234efgh5678ijkl91011mnop1214
                                                                         up/down
              Failure Reason:  Operation timed out
     dr_partner
          mccip-pri-a-initiator
                   10.1.1.3:65200     iqn.2016-04.com.netapp:abcd1234efgh5678ijkl91011mnop1215
                                                                         up/down
              Failure Reason:  Operation timed out
          mccip-pri-a-initiator2
                   10.1.1.3:65200     iqn.2016-05.com.netapp:abcd1234efgh5678ijkl91011mnop121316
                                                                         up/down
              Failure Reason:  Operation timed out
cluster01A-02
     dr_auxiliary
          mccip-aux-a-initiator
                   10.1.1.3:65200     iqn.2016-08.com.netapp:abcd1234efgh5678ijkl91011mnop1217
                                                                         up/down
              Failure Reason:  Operation timed out
          mccip-aux-a-initiator2
                   10.1.1.3:65200     iqn.2016-09.com.netapp:abcd1234efgh5678ijkl91011mnop1218
                                                                         up/down
              Failure Reason:  Operation timed out
     dr_partner
          mccip-pri-a-initiator
                   10.1.1.4:65200     iqn.2016-10.com.netapp:abcd1234efgh5678ijkl91011mnop1219
                                                                         up/down
              Failure Reason:  Operation timed out
          mccip-pri-a-initiator2
                   10.1.1.4:65200     iqn.2016-11.com.netapp:abcd1234efgh5678ijkl91011mnop1220
                                                                         up/down
              Failure Reason:  Operation timed out
cluster01A::*> set admin

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.