Messages relating to mpx.vmhba devices in the vmkernel or messages log are displayed after rescanning the storage
search cancel

Messages relating to mpx.vmhba devices in the vmkernel or messages log are displayed after rescanning the storage

book

Article ID: 344745

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • After performing a rescan on all storage, you see similar messages in the vmkernel (ESX) or messages (ESXi) log files:

    10:05:01 isdesx01 vmkernel: 8:16:20:00.875 cpu16:4112)NMP: nmp_CompleteCommandForPath: Command 0x12 (0x41000212cf80) to NMP device "mpx.vmhba5:C0:T0:L0" failed on physical path "vmhba5:C0:T0:L0" H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
     
  • Some LSI local controllers use naa disk identifiers instead of mpx disk identifiers. In this case you see similar messages in the vmkernel (ESX) or messages (ESXi) log files:

    T11:08:33.425Z cpu15:4111)ScsiDeviceIO: 2322: Cmd(0x41244169cd80) 0x4d, CmdSN 0x42d3 from world 0 to dev "naa.600508e00000000047831fb9c5e9ef0f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
    T11:08:33.426Z cpu15:4111)ScsiDeviceIO: 2322: Cmd(0x41244169cd80) 0x1a, CmdSN 0x42d4 from world 0 to dev "naa.600508e00000000047831fb9c5e9ef0f" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

     
  • You see similar messages when restarting management agents as hostd perform a rescan of HBA during restart.


Environment

VMware vSphere ESXi 5.5
VMware ESXi 4.0.x Embedded
VMware ESX 4.1.x
VMware vSphere ESXi 5.1
VMware ESX 4.0.x
VMware vSphere ESXi 5.0
VMware ESXi 4.1.x Installable
VMware ESXi 4.1.x Embedded
VMware ESXi 4.0.x Installable
VMware vSphere ESXi 6.0

Cause

These messages occur when devices such as a CD-ROM/DVD-ROM Drive or local LSI controller(s) do not support a rescan.

Resolution

These messages are normal and can be safely ignored.

In vSphere 4.0 and later, rescan events trigger failure messages for local devices, vmkernel logs this event every 5 minutes during the mini rescan, and whenever a rescan is triggered.
 
To view the vmkernel log and filter out these messages, run this command:
 
grep -ve " 0x85" -e " 0x4d" -e " 0x1a" -e " 0x12" <vmkernel file> | less


Additional Information

 

Filtering logs in VMware vSphere ESXi