nmp_DeviceRequestFastDeviceProbe - H:0x8 D:0x0 P:0x0

[kopper27]

hi guys

I getting some warning on the ESX 4.0 and 4.0 u1

I found this for Emulex but mine are Qlogic

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102945...

Anyway something I found is the code for my warning is H:0x8 D:0x0 P:0x0

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102903...

According to the page above H:0x8 means

This status is returned when the HBA driver has aborted the I/O. It can also occur if the HBA does a reset of the target.

what should I do? update something? ESX? Firmware?

Nov 22 17:01:52 shotsxe vmkernel: 150:07:11:00.234 cpu17:4244)<6>qla2xxx 0000:0c:00.0: scsi(3:0:0): Abort command issued -- 1 6550e005 2002.

Nov 22 17:01:52 shotsxe vmkernel: 150:07:11:00.234 cpu17:4113)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x4100020fe300) to NMP device "naa.600a0b

8000504064000005364bb1ba1e" failed on physical path "vmhba1:C0:T0:L0" H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

Nov 22 17:01:52 shotsxe vmkernel: 150:07:11:00.234 cpu17:4113)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device "naa.600a0b800050406400000536

4bb1ba1e" state in doubt; requested fast path state update...

Nov 19 17:01:44 shotsxe2 vmkernel: 14:04:11:11.205 cpu10:4277)<6>qla2xxx 0000:0c:00.0: scsi(3:0:3): Abort command issued -- 1 dcbbd8f 2002.

Nov 19 17:01:44 shotsxe2 vmkernel: 14:04:11:11.205 cpu10:4106)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x410002134140) to NMP device "naa.600a0b8

000504064000005394bbaf2e7" failed on physical path "vmhba1:C0:T0:L3" H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

Nov 19 17:01:44 shotsxe2 vmkernel: 14:04:11:11.205 cpu10:4106)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device "naa.600a0b8000504064000005394

bbaf2e7" state in doubt; requested fast path state update...

thanks a lot

[Xeonel]

Try having a look at the storage system. We've had this in the past and in the end it narrowed down to a controller issue on our array.

Also, an upgrade to U2 wouldn't hurt... And make sure you also open a support request to VMware so you have everything covered.

[kopper27]

thanks a lot Xeonel

what do you mean by controller issue? firmware? faulty controller?

[Xeonel · Accepted solution]

Ok, I managed to get a bit more information. The issue I was telling you about happened on a vmware environment in a different location. I just had a quick talk with my colleagues and got an update.

Digging through the logs on all hosts, it was noticed that the issue appeared on all hosts in the cluster. According to vmware technical support, this indicated a storage related issue (SAN fabric or array itself). As a consequence, one of the array controllers was replaced (it was an IBM DS 4200).

However, my colleagues reported that the issue did not stop there and resurfaced a bit later. If I get any more information on the topic, I'll let you know asap. At this point I'd recommend opening a support case with vmware immediately so they can also look into this.

[tadsmith]

Xeonel - were you able to find any further information on this? I have the same issue with a IBM DS4800. I've had an open ticket with both IBM and VMware for weeks, but we are having problems making progress.

[zomx]

I know this thread is old, but did either of you ever find a resolution. Having this problem on ESXi 4.1 U2 (latest build).

tia

[Xeonel]

I am currently out of the office, with only limited access to my e-mail.

I will be returning on Tuesday, the 24th of July 2012.

Best regards,

Andrei Neagoe