ESXi hosts enter into non-responsive state, and VMs appear disconnected in the vCenter UI.
ESXcli commands fail to execute on affected hosts.
In the vCenter UI, warnings such as "Path redundancy to storage device naa.########################### degraded" are observed.
From ESXi, /var/log/vobd.log there is an event for "Path state changes indicating storage connectivity issues"
2025-05-31T06:03:30.536Z: [scsiCorrelator] 12246182344412us: [vob.scsi.scsipath.pathstate.dead] scsiPath vmhba2:C0:T6:L1 changed state from on2025-05-31T06:03:30.538Z: [scsiCorrelator] 12246182344611us: [vob.scsi.scsipath.remove] Remove path: vmhba2:C0:T6:L12025-05-31T06:03:30.538Z: [scsiCorrelator] 12246182345421us: [vob.scsi.scsipath.pathstate.dead] scsiPath vmhba2:C0:T6:L2 changed state from on
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x
The message "returning IO as LUN is inactive or tport is NULL" indicates that the ESXi host is unable to process I/O requests because the target port is unavailable or the LUN is inactive.
From ESXI, var/run/log/vmkernel.log, error triggered as "LUN is inactive or the storage target port is in a null state"
2025-05-31T06:03:30.520Z cpu12:2098805)nfnic: <1>: INFO: fnic_queuecommand: 733: returning IO as lun is inactive or tport is NULL. driverIO:02025-05-31T06:03:30.520Z cpu12:2098805)nfnic: <1>: INFO: fnic_queuecommand: 733: returning IO as lun is inactive or tport is NULL. driverIO:02025-05-31T06:03:30.523Z cpu84:2098695)nfnic: <1>: INFO: fnic_queuecommand: 733: returning IO as lun is inactive or tport is NULL. driverIO:0
2025-05-31T06:03:30.622Z cpu48:2098298)nfnic: <1>: INFO: fnic_unclaim_lunlist: 222: FNIC unclaim lunlist: targetid:9, lun:1 start_time_ns:122461824323722512025-05-31T06:03:30.622Z cpu106:2097827)nfnic: <1>: INFO: fnic_queuecommand: 733: returning IO as lun is inactive or tport is NULL. driverIO:0
Engage the storage vendor support to investigate the cause of the LUN or target port being temporarily unavailable.