Warning "Cannot get LBA: cmd xa0 lba x0" repeats in vmkernel.log every 5 minutes.

Products

• VMware vSphere ESXi

Issue/Introduction

In vmkernel logs, we see below warnings :

Wa(180) vmkwarning: cpu28:2099816)WARNING: lpfc : vmhba4 lpfc_scsi_get_lba:1519: 9071 Cannot get LBA: cmd xa0 lba x0
Wa(180) vmkwarning: cpu28:2099816)WARNING: lpfc : vmhba4 lpfc_scsi_get_lba:1519: 9071 Cannot get LBA: cmd xa0 lba x0
Wa(180) vmkwarning: cpu28:2099816)WARNING: lpfc : vmhba4 lpfc_scsi_get_lba:1519: 9071 Cannot get LBA: cmd xa0 lba x0
Wa(180) vmkwarning: cpu39:2099812)WARNING: lpfc : vmhba4 lpfc_scsi_get_lba:1519: 9071 Cannot get LBA: cmd xa0 lba x0
Wa(180) vmkwarning: cpu18:2099820)WARNING: lpfc : vmhba5 lpfc_scsi_get_lba:1519: 9071 Cannot get LBA: cmd xa0 lba x0
Wa(180) vmkwarning: cpu18:2099820)WARNING: lpfc : vmhba5 lpfc_scsi_get_lba:1519: 9071 Cannot get LBA: cmd xa0 lba x0
Wa(180) vmkwarning: cpu18:2099820)WARNING: lpfc : vmhba5 lpfc_scsi_get_lba:1519: 9071 Cannot get LBA: cmd xa0 lba x0
Wa(180) vmkwarning: cpu18:2099820)WARNING: lpfc : vmhba5 lpfc_scsi_get_lba:1519: 9071 Cannot get LBA: cmd xa0 lba x0

Environment

ESXi 8.x

Cause

The 0xA0 (REPORT LUNS) SCSI command is used for device discovery. ESXi performs periodic LUN discovery and path validation every five minutes; during this process, the 'Cannot get LBA' warning may be triggered by several factors, including but not limited to:

• Storage-side issues
• Zoning issue replicated on both fabrics
• Stale target WWPN
• Removed controller port still zoned

Resolution

Involve the storage hardware vendor to perform a comprehensive audit of the SAN zoning and LUN presentation.