As I was looking at the compatility docs I noticed that it looks like iSCSI support for the Dell/EMC AX150i has been dropped from ESX verstion 3.5?
Is this really true? Does that meanI can't upgrade my site from 3.0.2 to 3.5 because I am using AX150i for storage? Or is it just a firmware version thing?
-mark corry
can not confirm but i can not seem to use my ax-150 iscsi san in esx 3.5 as well.
i'll try changing the esx firewall configuration and see what happens.
The storage vendors need to recertify all their storage against ESX3.5 to get it on the HCL.
Probably gonna take a while since the process can take some time.
// Joel
FYI - I just added a ESX 3.5 server to my cluster and it can see my Dell AX150i just fine.....
I just completed an in place upgrade to 3.5 and ESX can no longer see the AX150i. It is direct attached via a QLA4052c iSCSI controller. I hope that this device make it to the HCL soon.
That is good but, it doesn't support HBAs with AX150i and ESX 3.5 yet. maybe some time soon?
-mark
Only Emulex HBAs are supported according to the compatibilty guide http://www.vmware.com/pdf/vi35_san_guide.pdf.
I have the QLA4052c HBA. There is a frimware update version 3.0.1.33 from Qlogic http://support.qlogic.com/support/oem_product_vmware_iscsi.asp?&category=82&type=ISCIHBAWindows&nosi....
After an in place upgrade to VMware 3.5 the iSCSI array was detected, but the system would not boot. My configuration boots VMware from a Dell local volume using the Megaraid driver and all my vm's are on the AX150i.
For those of you who have executed an in place upgrade to 3.5 please double check that the ESX S/W ISCSI Initiator box is STILL checked under the esx-firewall settings. It no longer opened automatically under 3.5.