Unsolved
This post is more than 5 years old
89 Posts
0
1100
SCSI op code 9e not supported error
Can anyone shed some light on why I am getting "SCSI op code 9e not supported" errors constantly on my Celerra CX3-10? I've noticed these errors when I upgraded our VMware infrastructue from 4.x to 5.x but the errors don't seem to be affecting anything and I am not experiencing any issues. I just wanted to know if I should be concern about these constant errors that only shows up on the Celerra side and if there is anything I can do to stop the errors.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 4th, 2013 08:00
Hello. Did you find a solution? I'm having exactly the same problem than you after upgrading my ESX. Thanks in advance.
christopher_ime
2K Posts
0
March 4th, 2013 21:00
All,
Firstly, keep in mind ESXi 5.x is not supported with the CX3; however, as you are experiencing supported versus working can be two different things. By upgrading from ESX/ESXi v4.x (which is a supported combination) you now risk not getting support for the new configuration. As witness to this, you won't find a match in either of the following:
1) VMware Compatibility Guide
2) EMC E-Lab Interoperability Navigator
What I'm suspecting is that the error is related to some of the VAAI primitives; in particular the ones that were introduced in ESXi v5.x since you weren't getting the error previously. Also, keep in mind even with v4.1, you would need at least FLARE 28 to get the required VAAI (v1) support from the array perspective which is only available on a CX4.
Can I also ask if maybe the error is a 93 error? This would correspond to a VAAI primitive of WRITE SAME (introduced in v4.1) and ERASE (introduced in v5.0).
Regardless, since VAAI support isn't available with the CX3 anyways, can you disable all of the hardware acceleration options in ESXi 5.x? I am of course assuming these servers are only seeing storage from the CX3. If you have a VAAI compliant array that the hosts are also seeing storage from, then do not test as you can't disable it for one array and not the other.
Refer to the following VMware KB article:
VMware KB: Disabling the VAAI functionality in ESXi/ESX
http://kb.vmware.com/kb/1033665
Specifically I would like for you to disable (set to 0) the following:
1) DataMover.HardwareAcceleratedMove
2) DataMover.HardwareAcceleratedInit
3) VMFS3.HardwareAcceleratedLocking
Now, depending on the version of ESXi 5.x you are running, the following may already be disabled, but please verify:
Disabling VAAI Thin Provisioning Block Space Reclamation (UNMAP) in ESXi 5.0
http://kb.vmware.com/kb/2007427
4) VMFS3.EnableBlockDelete
I suspect the error will disappear once you disable all of the VAAI primitives which aren't supported with a CX3.