Skip to main content
NetApp Knowledge Base

ESXi hosts may lose connection to LUNs after MetroCluster switchover/switchback due to bug CSCve72490

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

​ ​

Applies to

  • ONTAP 9
  • Cisco MDS switches
  • NX-OS 6.2(19)/6.2(23)

Issue

When doing an MCC switchover or switchback, ESXi hosts may lose connection to (boot) LUNs, and need to be rebooted to recover access.

  • The LIF extended status post Switchover was seen as "FDISC error - ID could not be acquired for this virtual port".
  • event log show -messagename scsitarget.ispfct.configChanged
    • No such events could be seen.
  • Following errors could be seen on the Cisco Switch.
    • `show flogi internal event-history errors`

Event:E_DEBUG, length:115, at 289702 usecs after Tue Jun 19 15:56:40 2018
[102] NS config failed. Err 0x4025000d registration failed, interface fc1/2, vsan 100, pwwn
 

  • `show fcns internal errors`

Event:E_DEBUG, length:177, at 289527 usecs after Tue Jun 19 15:56:40 2018[825307441]  ns_reg_port_name(261): OTH: Trying to register duplicate port name for port-id 0xb20162 Existing entry's detail: pWWN , fWWN 

No Duplicate Port Id or FCID could be seen from FLOGI Database

 

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.