Skip to main content
NetApp Knowledge Base

After ONTAP upgrade SAN hosts lost path to LUN

  1. Last updated
  2. Save as PDF
Views:
127
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
san
Last Updated:

Applies to

  • SAN
  • VMware
  • FCP

Issue

  • Below alarms seen on the host end-
NMP: vmk_*********D:1243: UID of a device (path vmhba1:C0:T11:L83) has changed from naa.6*************638 (2025-04-13T20:26:29.361Z cpu2:66080).
2025-04-13T20:19:55.263Z cpu12:24202089)WARNING: NMP: nmp_PspSet:527: Switching to claimrule PSP "V***R" for device Unregistered Device.
2025-04-13T20:19:55.263Z cpu12:24202089)WARNING: VMW_SATP_ALUA: satp_alua_getTargetPortInfo:59: Could not get page 83 INQUIRY length for path "vm*******L80" - Not supported (195887136)
  •  All the missing paths were to one particular adapter on the storage.
  • The fcp ping-initiator show output shows several FC logical interfaces in a reachable state; however, the initiator WWPN is reported as not logged in.

fcp ping-initiator show -vserver SV******400 -wwpn 10:**:**:**:**:**:**:5*
  (vserver fcp ping-initiator show)
                            Node       Logical   Ping        Extended
Vserver   WWPN              Name       Interface Status      Status
--------- ----------------- ---------- --------- ----------- -----------------
SVM_LBFLDC_A400
          10:00:00:10:9b:34:fc:5d
                            LBFL-A400-01
                                       FC02_NODE01_0F
                                                 reachable   wwpn-logged-in
          10:00:00:10:9b:34:fc:5d
                            LBFL-A400-02
                                       FC04_NODE02_0F
                                                 reachable   wwpn-not-logged_in
          10:00:00:10:9b:34:fc:5d
                            LBFL-A400-01
                                       FC06_NODE01_0F
                                                 reachable   wwpn-logged-in
          10:00:00:10:9b:34:fc:5d
                            LBFL-A400-02
                                       FC08_NODE02_0F
                                                 reachable   wwpn-not-logged_in

  • To troubleshoot and resolve the initiator login issue, perform the following isolation steps:
    • Rescan host end adapter 
    • Toggle the switch port connected to host initiator
      • portenable
      • portdisable
    • Reset the Host HBA 
    • Reset the LIFs on NetApp end using below command:
      • ::> net int modify -vserver <vserver_name> -lif <lif_name> -status-admin down
      • ::> net int modify -vserver <vserver_name> -lif <lif_name> -status-admin up
    • Toggle the storage port using below command, one at a time:
      • ::> network fcp adapter modify -node node1 -adapter <> -status-admin down
      • ::> network fcp adapter modify -node node1 -adapter <> -status-admin dup

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.