ESXi host disconnected frequently from VCenter and VM's may go in hung state
search cancel

ESXi host disconnected frequently from VCenter and VM's may go in hung state

book

Article ID: 416237

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms: 

  • The ESXi host appears as Not Responding in vCenter Server.
  • The host remains accessible through DCUI.
  • Restarting the ESXi management agents restores connectivity to vCenter Server.
  • VM's may go in hung state due to constant I/O Abort

 

Environment

VMWare ESXi 8.x

Cause

The issue is caused by repeated aborts occurring on a Fibre Channel (FC) fabric switch port associated with a specific HBA adapter. Continuous command aborts from a single port can disrupt I/O operations and lead to host or datastore access instability

Cause Validation 

Verify whether multiple aborts are originating from a single HBA adapter.

Log path :  less /var/run/logvmkernel.log 

2025-10-04T03:22:46.460Z Wa(180) vmkwarning: cpu97:2098270)WARNING: lpfc : vmhba4 lpfc_abort_fcp_cmpl:7403: 3096 Abort  completion for abort cmd iotag x398 xri:0xb37req_tag x398, status x0, hwstatus x0
2025-10-04T03:22:46.460Z In(182) vmkernel: cpu0:2549315)NMP: nmp_ThrottleLogForDevice:3893: Cmd 0xc0 (0x45bb2fbc62c0, 2097272) to dev "naa.########" on path "vmhba4:C0:T0:L13" Failed:
2025-10-04T03:22:46.460Z In(182) vmkernel: cpu97:2098270)lpfc: lpfc_handle_status:4260: vmhba4 3271: FCP cmd xc0 failed <0/15> sid x024940, did x01ed40, oxid xb5b iotag xe81 Abort Requested Host Abort Req
2025-10-04T03:22:46.460Z Wa(180) vmkwarning: cpu97:2100294)WARNING: lpfc : vmhba4 lpfc_abort_fcp_cmpl:7403: 3096 Abort  completion for abort cmd iotag x397 xri:0xb5breq_tag x397, status x0, hwstatus x0
2025-10-04T03:22:46.464Z In(182) vmkernel: cpu0:2549315)NMP: nmp_ThrottleLogForDevice:3893: Cmd 0xc0 (0x45bb2fb5e4c0, 2097272) to dev "naa.#########" on path "vmhba4:C0:T0:L15" Failed:
2025-10-04T03:22:46.464Z Wa(180) vmkwarning: cpu53:2548315)WARNING: lpfc : vmhba4 lpfc_validate_fcp_abort:7544: 3111 Outstanding FCP I/O Abort Request still pending on io_buf 0x45db23f52430, xri xb83   >>>>>>>>>>>>>>>>>>>>>>>>>and usually indicates that an abort command sent to terminate a pending I/O request has not completed yet 
2025-10-04T03:22:46.465Z In(182) vmkernel: cpu97:2100294)lpfc: lpfc_handle_status:4260: vmhba4 3271: FCP cmd xc0 failed <0/17> sid x024940, did x01ed40, oxid xb83 iotag xea9 Abort Requested Host Abort Req
2025-10-04T03:22:46.465Z Wa(180) vmkwarning: cpu97:2098270)WARNING: lpfc : vmhba4 lpfc_abort_fcp_cmpl:7403: 3096 Abort  completion for abort cmd iotag x396 xri:0xb83req_tag x396, status x0, hwstatus x0
2025-10-04T03:22:46.466Z In(182) vmkernel: cpu97:2100294)lpfc: lpfc_handle_status:4260: vmhba4 3271: FCP cmd xc0 failed <0/18> sid x024940, did x01ed40, oxid xb42 iotag xe68 Abort Requested Host Abort Req

Resolution

 

  • Check the SAN switch ports for any connectivity or performance issues affecting the HBA path.

  • If a problematic or unstable port is identified, disable the affected switch port after validating the redundancy. 

  • After making the change, verify the ESXi host status and confirm that storage paths and I/O activity return to normal.

 

Powered by Wolken Software