VMKernel: nmp_DeviceRequestFastDeviceProbe


I am currently testing ESXi 4 by adding one ESXi 4 host to a VMware production cluster of a customer. The ESXi 4 host seems to run fine but i noticed the following kernel warnings in the system log:

Jul 18 17:00:27 vmkernel: 2:07:08:24.308 cpu7:40478)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4100021b8480) to NMP device "naa.600508b4000554df00007000034a0000" failed on physical path "vmhba1:C0:T0:L11" H:0×2 D:0×0 P:0×0 Possible sense data: Jul 18 17:00:27 0×0 0×0 0×0.

Jul 18 17:00:27 vmkernel: 2:07:08:24.308 cpu7:40478)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device "naa.600508b4000554df00007000034a0000" state in doubt; requested fast path state update…

Jul 18 17:00:27 vmkernel: 2:07:08:24.308 cpu7:40478)ScsiDeviceIO: 747: Command 0x2a to device "naa.600508b4000554df00007000034a0000" failed H:0×2 D:0×0 P:0×0 Possible sense data: 0×0 0×0 0×0.

The log message above contains the following codes:

failed H:0×2 D:0×0 P:0×0

The interesting section here is the code starting with "H" (H stands for "Host status"). Host status 0×2 means "HOST BUSY"

Vmware support gives the following explanation for this:


I checked with our bug database and as I had thought previously, H:0×2 D:0×0 P:0×0 translates to hba busy. The driver for whatever reason failed the i/o with a busy status. These can occur for any number of reasons. These failures are automatically retried by ESX.

Jul 18 17:00:27 vmkernel: 2:07:08:24.308 cpu7:40478)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device "naa.600508b4000554df00007000034a0000" state in doubt; requested fast path state update…"

This messaging will initially indicate that a NMP command was not responsive on a device, thus the NMP plugin ‘doubted’ the sate of the lun, i.e was it busy, was it on a path, was it responsive. This could be a driver problem or spurious logging. A bug for this message has been logged, and as yet is not an issue, unless followed by failing I/O or VM failures.


So it looks like a bug, but as yet is not an issue. Hope this gives some clarification!

About these ads

4 Responses to VMKernel: nmp_DeviceRequestFastDeviceProbe

  1. Chris says:

    Have you received any response to see if this has been escalated from a “bug” to and “issue”?

    I see this in my logs as well, but do not see references to the error.. just

    Nov 12 10:55:56 vm02 vmkernel: 1:09:14:46.197 cpu1:5711)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device “naa.6090a04830382d0f37ac64590e00403d” state in doubt; requested fast path state update…
    Nov 12 10:57:13 vm02 vmkernel: 1:09:16:03.950 cpu3:5711)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device “naa.6090a04830388d1237ac34d70e00a060″ state in doubt; requested fast path state update…
    Nov 12 10:57:14 vm02 vmkernel: 1:09:16:03.962 cpu3:5711)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device “naa.6090a04830382d0f37ac64590e00403d” state in doubt; requested fast path state update…

    Over and over and over….

  2. Ted Steenvoorden says:

    I am still seeing these messages on ESXi 4 update 1 on all kind of different storage systems (e.g. HP EVA 6000, HP EVA 8000, TMS RamSan-620). So it seems this issue has something to do with HBA drivers or ESXi.

  3. Habibalby says:

    Hello,
    I’m still seeing this warning on ESX4 Update 1 build 4.0.0, 208167 connected to hp MSA1000.

    Any help?

    Jun 6 06:32:22 esx03 vmkernel: 72:19:59:32.720 cpu0:9430)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device “eui.77ed48fa8d53566f” state in doubt; requested fast path state update…
    Jun 6 06:32:27 esx03 vmkernel: 72:19:59:37.787 cpu0:9430)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device “eui.77ed48fa8d53566f” state in doubt; requested fast path state update…

  4. Bob says:

    We are seeing these errors ALOT in our warnings log, I opened a call with vmware and below is their response.

    Basically they say to ignore them.

    Bob

    —— From Vmware
    As per our telephonic information I am sending the information about the warning you are getting in the vmkernel logs:

    vmkernel: 11:00:07:02.228 cpu0:4103)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device “naa.60a98000486e5933683457734752374c” state in doubt; requested fast path state update…”

    These messages appear as the Qlogic driver aborts a command because, the command took longer than the timeout period of 5 seconds.
    When a command is aborted, our mid-layer issues a TUR or TEST_UNIT_READY command down the path where the command did not complete to ensure that this path is still good to use. A TUR is issued every 300 seconds down each path as part of the path evaluation code (Disk.PathEvalTime), however in this instance a TUR is issued immediately due to the failed command.

    If we check the esxcfg-mpath -l output there are no issues with the Storage on the hosts.

    To resolve this:

    1. Right click on the host again and enable Alarms.
    2. Select the host then click on the Alarms tab.
    3. Then select Definitions and look for the alarm name “Cannot connect to storage”
    4. Double click on it.
    5. Uncheck the box “Enable this alarm” to disable this one in specific.
    6. Select the Triggers tab and see each of the Alarms defined, here you can remove the “Degraded Storage Path Redundancy” which is the one that’s generated.
    7. You can also see that in the Actions tab the alarm gets sent every five minutes, and that is the interval you are seeing and getting them.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: