Skip to main content
NetApp Knowledge Base

Lost access to LUN's during ONTAP Upgrade

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

Applies to

  • Ontap 9.x
  • FC
  • ESXi

Issue

  • Lost lun access during ontap upgrade from 9.10.1.P8 to 9.13.1P18 
  • During issue time stamp, VMs went in to hung state and IO errors seen on the physical servers 
  • Multiple SCSI command failures were observed, including
    • WRITE SAME (0x89) and INQUIRY (0x12) timeouts
    • Reservation Conflict (D:0x8) 
  • Several paths were marked flaky or experienced aborts (H:0xC, H:0x5, H:0x1) during the same timeframe

2025-11-03T16:02:17.136Z Wa(180) vmkwarning: cpu58:2098372)WARNING: NMP: nmpHandleLinkEvent:3998: Marking path vmhba1:C0:T6:L5 flaky on link event 2 with timeoutMS = 20000 flakyMarkTC = 116628984042340, reEvalFlakyPathTime = 20000
2025-11-03T16:02:17.136Z Wa(180) vmkwarning: cpu58:2098372)WARNING: NMP: nmpHandleLinkEvent:3998: Marking path vmhba1:C0:T6:L4 flaky on link event 2 with timeoutMS = 20000 flakyMarkTC = 116628984065480, reEvalFlakyPathTime = 20000
2025-11-03T16:02:19.409Z Wa(180) vmkwarning: cpu56:2098298)WARNING: NMP: nmpHandleLinkEvent:3998: Marking path vmhba0:C0:T4:L5 flaky on link event 2 with timeoutMS = 20000 flakyMarkTC = 116633519689000, reEvalFlakyPathTime = 20000

  • APD events were reported during the issue time stamp:

2025-11-03T18:37:32.715Z In(182) vmkernel: cpu20:2097641)ScsiDevice: 5738: Device state of naa.600a098038305666732451xx44546 set to APD_START; token num:1
2025-11-03T18:37:32.716Z In(182) vmkernel: cpu19:2097642)ScsiDevice: 5738: Device state of naa.600a098038305666714dxx4545 set to APD_START; token num:1
2025-11-03T18:37:32.716Z In(182) vmkernel: cpu20:2097641)ScsiDevice: 5738: Device state of naa.600a09803830566673245xx44839 set to APD_START; token num:1
2025-11-03T18:37:32.716Z In(182) vmkernel: cpu19:2097642)ScsiDevice: 5738: Device state of naa.600a098038305666732xxx544 set to APD_START; token num:1

  • FPIN congestion was reported on the VMHBAs which are being shared by both IBM and NetApp
2025-11-03T16:02:17.160Z In(182) vmkernel: cpu64:2098372)StorageFPIN: 1197: Report FC FPIN Peer Congestion Credit Stall event (hostWWPN 1000b47x979c7 tgtWWPN 500507x413f5) to vobd. 85 events have occurred since last report.
2025-11-03T16:02:18.206Z In(182) vmkernel: cpu76:2098372)StorageFPIN: 1197: Report FC FPIN Peer Congestion Credit Stall event (hostWWPN 1000xf16979c7 tgtWWPN 50050x0241425) to vobd. 85 events have occurred since last report.
2025-11-03T16:02:19.409Z In(182) vmkernel: cpu56:2098298)StorageFPIN: 1197: Report FC FPIN Peer Congestion Credit Stall event (hostWWPN 1000x16979c6 tgtWWPN 500507681x238) to vobd. 5814 events have occurred since last report.

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.