ITD_One
Contributor
Contributor

NMP Warnings in ESXI log.

Hi,

I'm using ESXi-6.5.0-4564106-standard on my Dell PowereEdge R730 Server.

Can anyone tell me why am i getting these Warnings/Error messages in vmware ESXI Log:

vmkwarning.log

2019-01-24T12:51:49.971Z cpu3:65588)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:51:52.019Z cpu3:65588)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:51:54.067Z cpu3:65588)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:51:56.115Z cpu3:65588)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:51:58.163Z cpu3:65588)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:52:00.211Z cpu3:65588)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:52:02.259Z cpu3:65588)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:52:04.307Z cpu3:65588)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:52:06.355Z cpu3:65588)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:52:08.403Z cpu3:65588)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

vmkernel.log

2019-01-24T12:52:58.433Z cpu12:65597)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x4a (0x43950e5913c0, 69096) to dev "mpx.vmhba2:C0:T5:L0" on path "vmhba2:C0:T5:L0" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-01-24T12:52:58.448Z cpu12:65597)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x4a (0x43950e5913c0, 69096) to dev "mpx.vmhba2:C0:T5:L0" on path "vmhba2:C0:T5:L0" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-01-24T12:53:11.443Z cpu2:65587)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x4a (0x439d0080d2c0, 70989) to dev "mpx.vmhba2:C0:T5:L0" on path "vmhba2:C0:T5:L0" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-01-24T12:53:11.443Z cpu2:65587)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:53:11.443Z cpu2:65587)ScsiDeviceIO: 2927: Cmd(0x439d0080d2c0) 0x4a, CmdSN 0x41e745c from world 70989 to dev "mpx.vmhba2:C0:T5:L0" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

2019-01-24T12:53:19.422Z cpu2:65587)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x4a (0x439500e042c0, 70863) to dev "mpx.vmhba2:C0:T5:L0" on path "vmhba2:C0:T5:L0" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-01-24T12:53:19.422Z cpu2:65587)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "mpx.vmhba2:C0:T5:L0" state in doubt; requested fast path state update...

2019-01-24T12:53:19.422Z cpu2:65587)ScsiDeviceIO: 2927: Cmd(0x439500e042c0) 0x4a, CmdSN 0x41e74ae from world 70863 to dev "mpx.vmhba2:C0:T5:L0" failed H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.

2019-01-24T12:53:19.436Z cpu2:65587)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x4a (0x439500e042c0, 70863) to dev "mpx.vmhba2:C0:T5:L0" on path "vmhba2:C0:T5:L0" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

2019-01-24T12:53:19.450Z cpu2:65587)NMP: nmp_ThrottleLogForDevice:3617: Cmd 0x4a (0x439500e042c0, 70863) to dev "mpx.vmhba2:C0:T5:L0" on path "vmhba2:C0:T5:L0" Failed: H:0x2 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. Act:EVAL

0 Kudos
5 Replies
bryanvaneeden
Hot Shot
Hot Shot

It seems it's one device: mpx.vmhba2:C0:T5:L0

How is this device configured? Does it have all paths that it should have?

Checking the config on the cli can be done with: esxcli storage core device list -d mpx.vmhba2:C0:T5:L0

Please let us know.

Visit my blog at https://vcloudvision.com!
0 Kudos
ITD_One
Contributor
Contributor

Hi bryan,

Thank you for your reply.
When i checked from cli with the command you provided, i got following result. It seems like mpx.vmhba2:C0:T5:L0 is a CD-ROM?

Any suggestion?

esxcli.JPG

0 Kudos
bryanvaneeden
Hot Shot
Hot Shot

Are you by any chance using that physical CD-ROM for a virtual machine at the moment? Or have you done this in the past?

You can get the VM's with connected CDROMs with the following PowerCLI command:

Get-VM | Get-CDDrive | ?{$_.Connectionstate.Connected -eq "true"} | Select Parent, IsoPath

Visit my blog at https://vcloudvision.com!
0 Kudos
ITD_One
Contributor
Contributor

Hi bryan,

It don't think we are using CD-ROM in any ,currently.

Also this command didn't work:
Get-VM | Get-CDDrive | ?{$_.Connectionstate.Connected -eq "true"} | Select Parent, IsoPath

0 Kudos
bryanvaneeden
Hot Shot
Hot Shot

It didn't? What error are you receiving on that?

If I execute it I receive the following output;

PS C:\Users\Bryan> Get-VM | Get-CDDrive | ?{$_.Connectionstate.Connected -eq "true"} | Select Parent, IsoPath

Parent         IsoPath

------         -------

VM-1     [] /usr/lib/vmware/isoimages/linux.iso

And in regards to the CD-ROM, I would advise you to check with the above script just to be sure. If it's not beeing used I will have to look around what it could possibly be.

Visit my blog at https://vcloudvision.com!
0 Kudos