has anyone noticed that that the MD3000i is no longer on VMware HCL for hardware iSCSI under ESX 4.0 and above? This has just killed our production platform big-time!
"has anyone noticed that that the MD3000i is no longer on VMware HCL for hardware iSCSI under ESX 4.0 and above? This has just killed our production platform big-time!"
I just searched the Vmare HCL and found this in 5 seconds...
"In what was less than a 5min search I found this? "
Maybe you needed to search for 6 minutes...
You need to to click on one of the links (e.g. the 'MD3000i' in blue), change to the 'model/release details' tab and you will see a table that states that the SAN is only approved for software iSCSI. This changed on the release of vSphere 4.0.
I guess I should learn how to read more carefully. I admit I missed the part about the HARDWARE HBA in your post. My apologies.
I posted the line right from the HCL. I'll cut and paste it again just to make sure people reading don't think it's not on the HCL at all any longer. see below. I guess I am glad I use the software initiator which is greatly improved in recent versions of ESX.
"has anyone noticed that that the MD3000i is no longer on VMware HCL for hardware iSCSI under ESX 4.0 and above? This has just killed our production platform big-time!"
So what have you done? I mean it sure looks like you seen the writing on the wall. The 3000i is gone completely from ESXi 5.0 HCL. :(
Are guys going with different arrays?
"So what have you done? I mean it sure looks like you seen the writing on the wall. The 3000i is gone completely from ESXi 5.0 HCL."
We moved over at the time to using the software initiator and this has worked fine. We are generally less than happy with the capabilities of the MD3000i and have moved to using HP P2000 G3 on other projects. I had not noticed that the device will not be compatible with vSphere 5.0 and this will be a problem in due course.
JOHNADCO
2 Intern
•
847 Posts
931
0
Posted October 5th, 2010 14:00