I've been running an ESXi 4 server connected to a Promise vTrak E610f SANS connected via fiber channel and was running fine
After the upgrade to ESXi 5 I've been having problems with my logs filling up with this:
2011-10-11T22:37:29.013Z cpu1:3624)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x12 (0x4124003d4840) to dev "eui.2262000155e8917c" on path "vmhba3:C0:T0:L0" Failed: H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.Act:EVAL
2011-10-11T22:37:29.013Z cpu1:3624)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "eui.2262000155e8917c" state in doubt; requested fast path state update...
2011-10-11T22:37:29.013Z cpu1:3624)ScsiDeviceIO: 2305: Cmd(0x4124003d4840) 0x12, CmdSN 0x3fa4 to dev "eui.2262000155e8917c" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
2011-10-11T22:37:30.021Z cpu1:2049)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "eui.2262000155e8917c" state in doubt; requested fast path state update...
2011-10-11T22:37:30.021Z cpu1:2049)ScsiDeviceIO: 2316: Cmd(0x4124003d4840) 0x12, CmdSN 0x3fa4 to dev "eui.2262000155e8917c" failed H:0x7 D:0x2 P:0x0 Possible sense data: 0x5 0x24 0x0.
2011-10-11T22:37:30.222Z cpu1:2049)ScsiDeviceIO: 2305: Cmd(0x4124003d4840) 0x12, CmdSN 0x3fa4 to dev "eui.2262000155e8917c" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
2011-10-11T22:37:30.626Z cpu1:3624)ScsiDeviceIO: 2316: Cmd(0x4124003d4840) 0x12, CmdSN 0x3fa4 to dev "eui.2262000155e8917c" failed H:0x7 D:0x2 P:0x0 Possible sense data: 0x5 0x24 0x0.
2011-10-11T22:37:30.827Z cpu1:2049)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "eui.2262000155e8917c" state in doubt; requested fast path state update...
I've been experimenting with it the last few days and this is the only storage server I'm having a problem with (tried it with two Sun x4500 servers that are serving drives over FC with COMSTAR). However, no other computer is having a problem with the vTrak, only VMWare.
I only get the above errors when writing to the datastore, not reading.
If I pass the disk through to a virtual machine as a raw disk I can read and write to it without any errors and nothing in my vmkernel.log file.
I've tried combinations of different controllers and cards and pathing options. I've changed several settings on the vTrak with no effect. I've updated the firmware in my FC cards with no change.
I've read posts from others with similar error messages, but haven't been able to resolve it.
The vTrak is running the latest firmware available, too.
Any thoughts?