Skip to main content
NetApp Knowledge Base

FC paths down to one node after MetroCluster switchback

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

Applies to

  • ONTAP 9.14.1P9
  • FCP
  • 4-node MetroCluster
  • VMware ESXi 7

Issue

  • ESXi hosts have dead paths to LIFs of one node after MetroCluster switchback
  • Rescan or reboot of the host does not resolve the situation
  • After rescan/reboot the paths go from dead to no longer being shown at the host
  • FC ping from ONTAP shows initiator is not reachable from LIF without path:

::> fcp ping-initiator show -wwpn 51:40:2e:c0:12:34:56:78 -vserver svm_example
  (vserver fcp ping-initiator show)
                            Node       Logical   Ping        Extended
Vserver   WWPN              Name       Interface Status      Status
--------- ----------------- ---------- --------- ----------- -----------------
svm_example
[...]
          51:40:2e:c0:12:34:56:78
                            node1   lif_fcp01_node1_2c
                                                 not-reachable
                                                             -

  • Storage attached switch can ping storage and host:

fabA_switch2:FID128:admin> fcping 20:10:d0:39:ea:12:34:56 51:40:2e:c0:12:34:56:78 
Source:         20:10:d0:39:ea:12:34:56
Destination:    51:40:2e:c0:12:34:56:78
Zone Check:     Zoned

Pinging 20:10:d0:39:ea:12:34:56 [0x650b01] with 12 bytes of data:
received reply from 20:10:d0:39:ea:12:34:56: 12 bytes time:489 usec
received reply from 20:10:d0:39:ea:12:34:56: 12 bytes time:355 usec
received reply from 20:10:d0:39:ea:12:34:56: 12 bytes time:358 usec
received reply from 20:10:d0:39:ea:12:34:56: 12 bytes time:338 usec
received reply from 20:10:d0:39:ea:12:34:56: 12 bytes time:377 usec
5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout
Round-trip min/avg/max = 338/383/489 usec

Pinging 51:40:2e:c0:12:34:56:78 [0x022a00] with 12 bytes of data:
received reply from 51:40:2e:c0:12:34:56:78: 12 bytes time:761 usec
received reply from 51:40:2e:c0:12:34:56:78: 12 bytes time:696 usec
received reply from 51:40:2e:c0:12:34:56:78: 12 bytes time:744 usec
received reply from 51:40:2e:c0:12:34:56:78: 12 bytes time:764 usec
received reply from 51:40:2e:c0:12:34:56:78: 12 bytes time:755 usec
5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout
Round-trip min/avg/max = 696/744/764 usec

  • Host attached switch cannot ping the storage:

fabA_switch1:admin>  fcping  20:10:d0:39:ea:12:34:56 51:40:2e:c0:12:34:56:78 
fcping: Error source wwn invalid

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.