Host side HPE blade seeing VMware disconnects and abort commands seen at ONTAP
Applies to
- ONTAP 9.X
- SAN FCP
- HPE Server
Issue
- VMware seeing pathing loss:
2025-07-23T15:39:24.359Z In(182) vmkernel: cpu56:2097298)NMP: nmp_ThrottleLogForDevice:3898: H:0x7 D:0x0 P:0x0 . Act:EVAL. cmdId.initiator=0x4309ed64dd80 CmdSN 0x42a2c9
2025-07-23T15:39:24.359Z Wa(180) vmkwarning: cpu56:2097298)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:235: NMP device "naa.600a0980383138553524555648352044" state in doubt; requested fast path state update...
2025-07-23T15:40:32.881Z In(182) vmkernel: cpu4:2097244)NMP: nmp_ThrottleLogForDevice:3893: Cmd 0x28 (0x45b9c0146600, 2098142) to dev "naa.600a09803831434f4524514135447452" on path "vmhba65:C0:T0:L0" Failed:
2025-07-23T15:40:32.881Z In(182) vmkernel: cpu4:2097244)NMP: nmp_ThrottleLogForDevice:3898: H:0x7 D:0x0 P:0x0 . Act:EVAL. cmdId.initiator=0x4309ed57aec0 CmdSN 0x8e
2025-07-23T15:40:32.881Z Wa(180) vmkwarning: cpu4:2097244)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:235: NMP device "naa.600a09803831434f4524514135447452" stateONTAP SAN seeing aborts and state=5 behavior
- ONTAP seeing Ext_status 0x16 and State=5
- ext_status 0x16 is host sending an abort
- A
state=5indicates that the FC target (storage) is waiting for a response from the host after accepting a write request.
[Node: fct_tpd_work_thread_0: fcp.io.status:debug]: STIO Adapter:0g IO WQE failure, Handle 0x0, Type 8, S_ID: 6A0212, VPI: 3, OX_ID: 315, Status 0x3 Ext_Status 0x16
[Node: fct_tpd_thread_0: fcp.io.status:debug]: STIO Adapter:0g, found hung cmd:0xfffff809bbbde7c0(state=5, flags=0x0, ctio_sent=1/1,RecvExAddr=0x268, OX_ID=0x5d9, RX_ID=0xffff,SID=0x6a020f, Cmd[93], req_q_free:0)